2 # IP netfilter configuration
5 menu "IPv6: Netfilter Configuration (EXPERIMENTAL)"
6 depends on INET && IPV6 && NETFILTER && EXPERIMENTAL
8 config NF_CONNTRACK_IPV6
9 tristate "IPv6 support for new connection tracking (EXPERIMENTAL)"
10 depends on EXPERIMENTAL && NF_CONNTRACK
12 Connection tracking keeps a record of what packets have passed
13 through your machine, in order to figure out how they are related
16 This is IPv6 support on Layer 3 independent connection tracking.
17 Layer 3 independent connection tracking is experimental scheme
18 which generalize ip_conntrack to support other layer 3 protocols.
20 To compile it as a module, choose M here. If unsure, say N.
23 tristate "IP6 Userspace queueing via NETLINK (OBSOLETE)"
26 This option adds a queue handler to the kernel for IPv6
27 packets which enables users to receive the filtered packets
28 with QUEUE target using libipq.
30 THis option enables the old IPv6-only "ip6_queue" implementation
31 which has been obsoleted by the new "nfnetlink_queue" code (see
32 CONFIG_NETFILTER_NETLINK_QUEUE).
34 (C) Fernando Anton 2001
35 IPv64 Project - Work based in IPv64 draft by Arturo Azcorra.
36 Universidad Carlos III de Madrid
37 Universidad Politecnica de Alcala de Henares
38 email: <fanton@it.uc3m.es>.
40 To compile it as a module, choose M here. If unsure, say N.
42 config IP6_NF_IPTABLES
43 tristate "IP6 tables support (required for filtering/masq/NAT)"
45 ip6tables is a general, extensible packet identification framework.
46 Currently only the packet filtering and packet mangling subsystem
47 for IPv6 use this, but connection tracking is going to follow.
48 Say 'Y' or 'M' here if you want to use either of those.
50 To compile it as a module, choose M here. If unsure, say N.
53 config IP6_NF_MATCH_LIMIT
54 tristate "limit match support"
55 depends on IP6_NF_IPTABLES
57 limit matching allows you to control the rate at which a rule can be
58 matched: mainly useful in combination with the LOG target ("LOG
59 target support", below) and to avoid some Denial of Service attacks.
61 To compile it as a module, choose M here. If unsure, say N.
63 config IP6_NF_MATCH_MAC
64 tristate "MAC address match support"
65 depends on IP6_NF_IPTABLES
67 mac matching allows you to match packets based on the source
68 Ethernet address of the packet.
70 To compile it as a module, choose M here. If unsure, say N.
72 config IP6_NF_MATCH_RT
73 tristate "Routing header match support"
74 depends on IP6_NF_IPTABLES
76 rt matching allows you to match packets based on the routing
79 To compile it as a module, choose M here. If unsure, say N.
81 config IP6_NF_MATCH_OPTS
82 tristate "Hop-by-hop and Dst opts header match support"
83 depends on IP6_NF_IPTABLES
85 This allows one to match packets based on the hop-by-hop
86 and destination options headers of a packet.
88 To compile it as a module, choose M here. If unsure, say N.
90 config IP6_NF_MATCH_FRAG
91 tristate "Fragmentation header match support"
92 depends on IP6_NF_IPTABLES
94 frag matching allows you to match packets based on the fragmentation
97 To compile it as a module, choose M here. If unsure, say N.
99 config IP6_NF_MATCH_HL
100 tristate "HL match support"
101 depends on IP6_NF_IPTABLES
103 HL matching allows you to match packets based on the hop
106 To compile it as a module, choose M here. If unsure, say N.
108 config IP6_NF_MATCH_MULTIPORT
109 tristate "Multiple port match support"
110 depends on IP6_NF_IPTABLES
112 Multiport matching allows you to match TCP or UDP packets based on
113 a series of source or destination ports: normally a rule can only
114 match a single range of ports.
116 To compile it as a module, choose M here. If unsure, say N.
118 config IP6_NF_MATCH_OWNER
119 tristate "Owner match support"
120 depends on IP6_NF_IPTABLES
122 Packet owner matching allows you to match locally-generated packets
123 based on who created them: the user, group, process or session.
125 To compile it as a module, choose M here. If unsure, say N.
127 config IP6_NF_MATCH_MARK
128 tristate "netfilter MARK match support"
129 depends on IP6_NF_IPTABLES
131 Netfilter mark matching allows you to match packets based on the
132 `nfmark' value in the packet. This can be set by the MARK target
135 To compile it as a module, choose M here. If unsure, say N.
137 config IP6_NF_MATCH_IPV6HEADER
138 tristate "IPv6 Extension Headers Match"
139 depends on IP6_NF_IPTABLES
141 This module allows one to match packets based upon
142 the ipv6 extension headers.
144 To compile it as a module, choose M here. If unsure, say N.
146 config IP6_NF_MATCH_AHESP
147 tristate "AH/ESP match support"
148 depends on IP6_NF_IPTABLES
150 This module allows one to match AH and ESP packets.
152 To compile it as a module, choose M here. If unsure, say N.
154 config IP6_NF_MATCH_LENGTH
155 tristate "Packet Length match support"
156 depends on IP6_NF_IPTABLES
158 This option allows you to match the length of a packet against a
159 specific value or range of values.
161 To compile it as a module, choose M here. If unsure, say N.
163 config IP6_NF_MATCH_EUI64
164 tristate "EUI64 address check"
165 depends on IP6_NF_IPTABLES
167 This module performs checking on the IPv6 source address
168 Compares the last 64 bits with the EUI64 (delivered
169 from the MAC address) address
171 To compile it as a module, choose M here. If unsure, say N.
173 config IP6_NF_MATCH_PHYSDEV
174 tristate "Physdev match support"
175 depends on IP6_NF_IPTABLES && BRIDGE_NETFILTER
177 Physdev packet matching matches against the physical bridge ports
178 the IP packet arrived on or will leave by.
180 To compile it as a module, choose M here. If unsure, say N.
184 tristate "Packet filtering"
185 depends on IP6_NF_IPTABLES
187 Packet filtering defines a table `filter', which has a series of
188 rules for simple packet filtering at local input, forwarding and
189 local output. See the man page for iptables(8).
191 To compile it as a module, choose M here. If unsure, say N.
193 config IP6_NF_TARGET_LOG
194 tristate "LOG target support"
195 depends on IP6_NF_FILTER
197 This option adds a `LOG' target, which allows you to create rules in
198 any iptables table which records the packet header to the syslog.
200 To compile it as a module, choose M here. If unsure, say N.
202 config IP6_NF_TARGET_REJECT
203 tristate "REJECT target support"
204 depends on IP6_NF_FILTER
206 The REJECT target allows a filtering rule to specify that an ICMPv6
207 error should be issued in response to an incoming packet, rather
208 than silently being dropped.
210 To compile it as a module, choose M here. If unsure, say N.
212 config IP6_NF_TARGET_NFQUEUE
213 tristate "NFQUEUE Target Support"
214 depends on IP6_NF_IPTABLES
216 This Target replaced the old obsolete QUEUE target.
218 As opposed to QUEUE, it supports 65535 different queues,
221 To compile it as a module, choose M here. If unsure, say N.
224 tristate "Packet mangling"
225 depends on IP6_NF_IPTABLES
227 This option adds a `mangle' table to iptables: see the man page for
228 iptables(8). This table is used for various packet alterations
229 which can effect how the packet is routed.
231 To compile it as a module, choose M here. If unsure, say N.
233 config IP6_NF_TARGET_MARK
234 tristate "MARK target support"
235 depends on IP6_NF_MANGLE
237 This option adds a `MARK' target, which allows you to create rules
238 in the `mangle' table which alter the netfilter mark (nfmark) field
239 associated with the packet packet prior to routing. This can change
240 the routing method (see `Use netfilter MARK value as routing
241 key') and can also be used by other subsystems to change their
244 To compile it as a module, choose M here. If unsure, say N.
246 config IP6_NF_TARGET_HL
247 tristate 'HL (hoplimit) target support'
248 depends on IP6_NF_MANGLE
250 This option adds a `HL' target, which enables the user to decrement
251 the hoplimit value of the IPv6 header or set it to a given (lower)
254 While it is safe to decrement the hoplimit value, this option also
255 enables functionality to increment and set the hoplimit value of the
256 IPv6 header to arbitrary values. This is EXTREMELY DANGEROUS since
257 you can easily create immortal packets that loop forever on the
260 To compile it as a module, choose M here. If unsure, say N.
263 tristate 'raw table support (required for TRACE)'
264 depends on IP6_NF_IPTABLES
266 This option adds a `raw' table to ip6tables. This table is the very
267 first in the netfilter framework and hooks in at the PREROUTING
270 If you want to compile it as a module, say M here and read
271 <file:Documentation/modules.txt>. If unsure, say `N'.