1 menu "Core Netfilter Configuration"
2 depends on NET && INET && NETFILTER
4 config NETFILTER_NETLINK
7 config NETFILTER_NETLINK_QUEUE
8 tristate "Netfilter NFQUEUE over NFNETLINK interface"
9 depends on NETFILTER_ADVANCED
10 select NETFILTER_NETLINK
12 If this option is enabled, the kernel will include support
13 for queueing packets via NFNETLINK.
15 config NETFILTER_NETLINK_LOG
16 tristate "Netfilter LOG over NFNETLINK interface"
17 default m if NETFILTER_ADVANCED=n
18 select NETFILTER_NETLINK
20 If this option is enabled, the kernel will include support
21 for logging packets via NFNETLINK.
23 This obsoletes the existing ipt_ULOG and ebg_ulog mechanisms,
24 and is also scheduled to replace the old syslog-based ipt_LOG
28 tristate "Netfilter connection tracking support"
29 default m if NETFILTER_ADVANCED=n
31 Connection tracking keeps a record of what packets have passed
32 through your machine, in order to figure out how they are related
35 This is required to do Masquerading or other kinds of Network
36 Address Translation. It can also be used to enhance packet
37 filtering (see `Connection state match support' below).
39 To compile it as a module, choose M here. If unsure, say N.
44 bool "Connection tracking flow accounting"
45 depends on NETFILTER_ADVANCED
47 If this option is enabled, the connection tracking code will
48 keep per-flow packet and byte counters.
50 Those counters can be used for flow-based accounting or the
53 Please note that currently this option only sets a default state.
54 You may change it at boot time with nf_conntrack.acct=0/1 kernel
55 paramater or by loading the nf_conntrack module with acct=0/1.
57 You may also disable/enable it on a running system with:
58 sysctl net.netfilter.nf_conntrack_acct=0/1
60 This option will be removed in 2.6.29.
64 config NF_CONNTRACK_MARK
65 bool 'Connection mark tracking support'
66 depends on NETFILTER_ADVANCED
68 This option enables support for connection marks, used by the
69 `CONNMARK' target and `connmark' match. Similar to the mark value
70 of packets, but this mark value is kept in the conntrack session
71 instead of the individual packets.
73 config NF_CONNTRACK_SECMARK
74 bool 'Connection tracking security mark support'
75 depends on NETWORK_SECMARK
76 default m if NETFILTER_ADVANCED=n
78 This option enables security markings to be applied to
79 connections. Typically they are copied to connections from
80 packets using the CONNSECMARK target and copied back from
81 connections to packets with the same target, with the packets
82 being originally labeled via SECMARK.
86 config NF_CONNTRACK_EVENTS
87 bool "Connection tracking events"
88 depends on NETFILTER_ADVANCED
90 If this option is enabled, the connection tracking code will
91 provide a notifier chain that can be used by other kernel code
92 to get notified about changes in the connection tracking state.
96 config NF_CT_PROTO_DCCP
97 tristate 'DCCP protocol connection tracking support (EXPERIMENTAL)'
98 depends on EXPERIMENTAL
99 depends on NETFILTER_ADVANCED
102 With this option enabled, the layer 3 independent connection
103 tracking code will be able to do state tracking on DCCP connections.
107 config NF_CT_PROTO_GRE
110 config NF_CT_PROTO_SCTP
111 tristate 'SCTP protocol connection tracking support (EXPERIMENTAL)'
112 depends on EXPERIMENTAL
113 depends on NETFILTER_ADVANCED
116 With this option enabled, the layer 3 independent connection
117 tracking code will be able to do state tracking on SCTP connections.
119 If you want to compile it as a module, say M here and read
120 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
122 config NF_CT_PROTO_UDPLITE
123 tristate 'UDP-Lite protocol connection tracking support'
124 depends on NETFILTER_ADVANCED
126 With this option enabled, the layer 3 independent connection
127 tracking code will be able to do state tracking on UDP-Lite
130 To compile it as a module, choose M here. If unsure, say N.
132 config NF_CONNTRACK_AMANDA
133 tristate "Amanda backup protocol support"
134 depends on NETFILTER_ADVANCED
136 select TEXTSEARCH_KMP
138 If you are running the Amanda backup package <http://www.amanda.org/>
139 on this machine or machines that will be MASQUERADED through this
140 machine, then you may want to enable this feature. This allows the
141 connection tracking and natting code to allow the sub-channels that
142 Amanda requires for communication of the backup data, messages and
145 To compile it as a module, choose M here. If unsure, say N.
147 config NF_CONNTRACK_FTP
148 tristate "FTP protocol support"
149 default m if NETFILTER_ADVANCED=n
151 Tracking FTP connections is problematic: special helpers are
152 required for tracking them, and doing masquerading and other forms
153 of Network Address Translation on them.
155 This is FTP support on Layer 3 independent connection tracking.
156 Layer 3 independent connection tracking is experimental scheme
157 which generalize ip_conntrack to support other layer 3 protocols.
159 To compile it as a module, choose M here. If unsure, say N.
161 config NF_CONNTRACK_H323
162 tristate "H.323 protocol support"
163 depends on (IPV6 || IPV6=n)
164 depends on NETFILTER_ADVANCED
166 H.323 is a VoIP signalling protocol from ITU-T. As one of the most
167 important VoIP protocols, it is widely used by voice hardware and
168 software including voice gateways, IP phones, Netmeeting, OpenPhone,
171 With this module you can support H.323 on a connection tracking/NAT
174 This module supports RAS, Fast Start, H.245 Tunnelling, Call
175 Forwarding, RTP/RTCP and T.120 based audio, video, fax, chat,
176 whiteboard, file transfer, etc. For more information, please
177 visit http://nath323.sourceforge.net/.
179 To compile it as a module, choose M here. If unsure, say N.
181 config NF_CONNTRACK_IRC
182 tristate "IRC protocol support"
183 default m if NETFILTER_ADVANCED=n
185 There is a commonly-used extension to IRC called
186 Direct Client-to-Client Protocol (DCC). This enables users to send
187 files to each other, and also chat to each other without the need
188 of a server. DCC Sending is used anywhere you send files over IRC,
189 and DCC Chat is most commonly used by Eggdrop bots. If you are
190 using NAT, this extension will enable you to send files and initiate
191 chats. Note that you do NOT need this extension to get files or
192 have others initiate chats, or everything else in IRC.
194 To compile it as a module, choose M here. If unsure, say N.
196 config NF_CONNTRACK_NETBIOS_NS
197 tristate "NetBIOS name service protocol support"
198 depends on NETFILTER_ADVANCED
200 NetBIOS name service requests are sent as broadcast messages from an
201 unprivileged port and responded to with unicast messages to the
202 same port. This make them hard to firewall properly because connection
203 tracking doesn't deal with broadcasts. This helper tracks locally
204 originating NetBIOS name service requests and the corresponding
205 responses. It relies on correct IP address configuration, specifically
206 netmask and broadcast address. When properly configured, the output
207 of "ip address show" should look similar to this:
209 $ ip -4 address show eth0
210 4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
211 inet 172.16.2.252/24 brd 172.16.2.255 scope global eth0
213 To compile it as a module, choose M here. If unsure, say N.
215 config NF_CONNTRACK_PPTP
216 tristate "PPtP protocol support"
217 depends on NETFILTER_ADVANCED
218 select NF_CT_PROTO_GRE
220 This module adds support for PPTP (Point to Point Tunnelling
221 Protocol, RFC2637) connection tracking and NAT.
223 If you are running PPTP sessions over a stateful firewall or NAT
224 box, you may want to enable this feature.
226 Please note that not all PPTP modes of operation are supported yet.
227 Specifically these limitations exist:
228 - Blindly assumes that control connections are always established
229 in PNS->PAC direction. This is a violation of RFC2637.
230 - Only supports a single call within each session
232 To compile it as a module, choose M here. If unsure, say N.
234 config NF_CONNTRACK_SANE
235 tristate "SANE protocol support (EXPERIMENTAL)"
236 depends on EXPERIMENTAL
237 depends on NETFILTER_ADVANCED
239 SANE is a protocol for remote access to scanners as implemented
240 by the 'saned' daemon. Like FTP, it uses separate control and
243 With this module you can support SANE on a connection tracking
246 To compile it as a module, choose M here. If unsure, say N.
248 config NF_CONNTRACK_SIP
249 tristate "SIP protocol support"
250 default m if NETFILTER_ADVANCED=n
252 SIP is an application-layer control protocol that can establish,
253 modify, and terminate multimedia sessions (conferences) such as
254 Internet telephony calls. With the ip_conntrack_sip and
255 the nf_nat_sip modules you can support the protocol on a connection
256 tracking/NATing firewall.
258 To compile it as a module, choose M here. If unsure, say N.
260 config NF_CONNTRACK_TFTP
261 tristate "TFTP protocol support"
262 depends on NETFILTER_ADVANCED
264 TFTP connection tracking helper, this is required depending
265 on how restrictive your ruleset is.
266 If you are using a tftp client behind -j SNAT or -j MASQUERADING
269 To compile it as a module, choose M here. If unsure, say N.
272 tristate 'Connection tracking netlink interface'
273 select NETFILTER_NETLINK
274 default m if NETFILTER_ADVANCED=n
276 This option enables support for a netlink-based userspace interface
278 # transparent proxy support
279 config NETFILTER_TPROXY
280 tristate "Transparent proxying support (EXPERIMENTAL)"
281 depends on EXPERIMENTAL
282 depends on IP_NF_MANGLE
283 depends on NETFILTER_ADVANCED
285 This option enables transparent proxying support, that is,
286 support for handling non-locally bound IPv4 TCP and UDP sockets.
287 For it to work you will have to configure certain iptables rules
288 and use policy routing. For more information on how to set it up
289 see Documentation/networking/tproxy.txt.
291 To compile it as a module, choose M here. If unsure, say N.
295 config NETFILTER_XTABLES
296 tristate "Netfilter Xtables support (required for ip_tables)"
297 default m if NETFILTER_ADVANCED=n
299 This is required if you intend to use any of ip_tables,
300 ip6_tables or arp_tables.
304 # alphabetically ordered list of targets
306 config NETFILTER_XT_TARGET_CLASSIFY
307 tristate '"CLASSIFY" target support'
308 depends on NETFILTER_ADVANCED
310 This option adds a `CLASSIFY' target, which enables the user to set
311 the priority of a packet. Some qdiscs can use this value for
312 classification, among these are:
314 atm, cbq, dsmark, pfifo_fast, htb, prio
316 To compile it as a module, choose M here. If unsure, say N.
318 config NETFILTER_XT_TARGET_CONNMARK
319 tristate '"CONNMARK" target support'
320 depends on NF_CONNTRACK
321 depends on NETFILTER_ADVANCED
322 select NF_CONNTRACK_MARK
324 This option adds a `CONNMARK' target, which allows one to manipulate
325 the connection mark value. Similar to the MARK target, but
326 affects the connection mark value rather than the packet mark value.
328 If you want to compile it as a module, say M here and read
329 <file:Documentation/kbuild/modules.txt>. The module will be called
330 ipt_CONNMARK.ko. If unsure, say `N'.
332 config NETFILTER_XT_TARGET_CONNSECMARK
333 tristate '"CONNSECMARK" target support'
334 depends on NF_CONNTRACK && NF_CONNTRACK_SECMARK
335 default m if NETFILTER_ADVANCED=n
337 The CONNSECMARK target copies security markings from packets
338 to connections, and restores security markings from connections
339 to packets (if the packets are not already marked). This would
340 normally be used in conjunction with the SECMARK target.
342 To compile it as a module, choose M here. If unsure, say N.
344 config NETFILTER_XT_TARGET_DSCP
345 tristate '"DSCP" and "TOS" target support'
346 depends on IP_NF_MANGLE || IP6_NF_MANGLE
347 depends on NETFILTER_ADVANCED
349 This option adds a `DSCP' target, which allows you to manipulate
350 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
352 The DSCP field can have any value between 0x0 and 0x3f inclusive.
354 It also adds the "TOS" target, which allows you to create rules in
355 the "mangle" table which alter the Type Of Service field of an IPv4
356 or the Priority field of an IPv6 packet, prior to routing.
358 To compile it as a module, choose M here. If unsure, say N.
360 config NETFILTER_XT_TARGET_HL
361 tristate '"HL" hoplimit target support'
362 depends on IP_NF_MANGLE || IP6_NF_MANGLE
363 depends on NETFILTER_ADVANCED
365 This option adds the "HL" (for IPv6) and "TTL" (for IPv4)
366 targets, which enable the user to change the
367 hoplimit/time-to-live value of the IP header.
369 While it is safe to decrement the hoplimit/TTL value, the
370 modules also allow to increment and set the hoplimit value of
371 the header to arbitrary values. This is EXTREMELY DANGEROUS
372 since you can easily create immortal packets that loop
373 forever on the network.
375 config NETFILTER_XT_TARGET_LED
376 tristate '"LED" target support'
377 depends on LEDS_CLASS && LED_TRIGGERS
378 depends on NETFILTER_ADVANCED
380 This option adds a `LED' target, which allows you to blink LEDs in
381 response to particular packets passing through your machine.
383 This can be used to turn a spare LED into a network activity LED,
384 which only flashes in response to FTP transfers, for example. Or
385 you could have an LED which lights up for a minute or two every time
386 somebody connects to your machine via SSH.
388 You will need support for the "led" class to make this work.
390 To create an LED trigger for incoming SSH traffic:
391 iptables -A INPUT -p tcp --dport 22 -j LED --led-trigger-id ssh --led-delay 1000
393 Then attach the new trigger to an LED on your system:
394 echo netfilter-ssh > /sys/class/leds/<ledname>/trigger
396 For more information on the LEDs available on your system, see
397 Documentation/leds-class.txt
399 config NETFILTER_XT_TARGET_MARK
400 tristate '"MARK" target support'
401 default m if NETFILTER_ADVANCED=n
403 This option adds a `MARK' target, which allows you to create rules
404 in the `mangle' table which alter the netfilter mark (nfmark) field
405 associated with the packet prior to routing. This can change
406 the routing method (see `Use netfilter MARK value as routing
407 key') and can also be used by other subsystems to change their
410 To compile it as a module, choose M here. If unsure, say N.
412 config NETFILTER_XT_TARGET_NFLOG
413 tristate '"NFLOG" target support'
414 default m if NETFILTER_ADVANCED=n
415 select NETFILTER_NETLINK_LOG
417 This option enables the NFLOG target, which allows to LOG
418 messages through nfnetlink_log.
420 To compile it as a module, choose M here. If unsure, say N.
422 config NETFILTER_XT_TARGET_NFQUEUE
423 tristate '"NFQUEUE" target Support'
424 depends on NETFILTER_ADVANCED
426 This target replaced the old obsolete QUEUE target.
428 As opposed to QUEUE, it supports 65535 different queues,
431 To compile it as a module, choose M here. If unsure, say N.
433 config NETFILTER_XT_TARGET_NOTRACK
434 tristate '"NOTRACK" target support'
435 depends on IP_NF_RAW || IP6_NF_RAW
436 depends on NF_CONNTRACK
437 depends on NETFILTER_ADVANCED
439 The NOTRACK target allows a select rule to specify
440 which packets *not* to enter the conntrack/NAT
441 subsystem with all the consequences (no ICMP error tracking,
442 no protocol helpers for the selected packets).
444 If you want to compile it as a module, say M here and read
445 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
447 config NETFILTER_XT_TARGET_RATEEST
448 tristate '"RATEEST" target support'
449 depends on NETFILTER_ADVANCED
451 This option adds a `RATEEST' target, which allows to measure
452 rates similar to TC estimators. The `rateest' match can be
453 used to match on the measured rates.
455 To compile it as a module, choose M here. If unsure, say N.
457 config NETFILTER_XT_TARGET_TPROXY
458 tristate '"TPROXY" target support (EXPERIMENTAL)'
459 depends on EXPERIMENTAL
460 depends on NETFILTER_TPROXY
461 depends on NETFILTER_XTABLES
462 depends on NETFILTER_ADVANCED
463 select NF_DEFRAG_IPV4
465 This option adds a `TPROXY' target, which is somewhat similar to
466 REDIRECT. It can only be used in the mangle table and is useful
467 to redirect traffic to a transparent proxy. It does _not_ depend
468 on Netfilter connection tracking and NAT, unlike REDIRECT.
470 To compile it as a module, choose M here. If unsure, say N.
472 config NETFILTER_XT_TARGET_TRACE
473 tristate '"TRACE" target support'
474 depends on IP_NF_RAW || IP6_NF_RAW
475 depends on NETFILTER_ADVANCED
477 The TRACE target allows you to mark packets so that the kernel
478 will log every rule which match the packets as those traverse
479 the tables, chains, rules.
481 If you want to compile it as a module, say M here and read
482 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
484 config NETFILTER_XT_TARGET_SECMARK
485 tristate '"SECMARK" target support'
486 depends on NETWORK_SECMARK
487 default m if NETFILTER_ADVANCED=n
489 The SECMARK target allows security marking of network
490 packets, for use with security subsystems.
492 To compile it as a module, choose M here. If unsure, say N.
494 config NETFILTER_XT_TARGET_TCPMSS
495 tristate '"TCPMSS" target support'
496 depends on (IPV6 || IPV6=n)
497 default m if NETFILTER_ADVANCED=n
499 This option adds a `TCPMSS' target, which allows you to alter the
500 MSS value of TCP SYN packets, to control the maximum size for that
501 connection (usually limiting it to your outgoing interface's MTU
504 This is used to overcome criminally braindead ISPs or servers which
505 block ICMP Fragmentation Needed packets. The symptoms of this
506 problem are that everything works fine from your Linux
507 firewall/router, but machines behind it can never exchange large
509 1) Web browsers connect, then hang with no data received.
510 2) Small mail works fine, but large emails hang.
511 3) ssh works fine, but scp hangs after initial handshaking.
513 Workaround: activate this option and add a rule to your firewall
516 iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
517 -j TCPMSS --clamp-mss-to-pmtu
519 To compile it as a module, choose M here. If unsure, say N.
521 config NETFILTER_XT_TARGET_TCPOPTSTRIP
522 tristate '"TCPOPTSTRIP" target support (EXPERIMENTAL)'
523 depends on EXPERIMENTAL
524 depends on IP_NF_MANGLE || IP6_NF_MANGLE
525 depends on NETFILTER_ADVANCED
527 This option adds a "TCPOPTSTRIP" target, which allows you to strip
528 TCP options from TCP packets.
530 config NETFILTER_XT_MATCH_CLUSTER
531 tristate '"cluster" match support'
532 depends on NF_CONNTRACK
533 depends on NETFILTER_ADVANCED
535 This option allows you to build work-load-sharing clusters of
536 network servers/stateful firewalls without having a dedicated
537 load-balancing router/server/switch. Basically, this match returns
538 true when the packet must be handled by this cluster node. Thus,
539 all nodes see all packets and this match decides which node handles
540 what packets. The work-load sharing algorithm is based on source
543 If you say Y or M here, try `iptables -m cluster --help` for
546 config NETFILTER_XT_MATCH_COMMENT
547 tristate '"comment" match support'
548 depends on NETFILTER_ADVANCED
550 This option adds a `comment' dummy-match, which allows you to put
551 comments in your iptables ruleset.
553 If you want to compile it as a module, say M here and read
554 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
556 config NETFILTER_XT_MATCH_CONNBYTES
557 tristate '"connbytes" per-connection counter match support'
558 depends on NF_CONNTRACK
559 depends on NETFILTER_ADVANCED
562 This option adds a `connbytes' match, which allows you to match the
563 number of bytes and/or packets for each direction within a connection.
565 If you want to compile it as a module, say M here and read
566 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
568 config NETFILTER_XT_MATCH_CONNLIMIT
569 tristate '"connlimit" match support"'
570 depends on NF_CONNTRACK
571 depends on NETFILTER_ADVANCED
573 This match allows you to match against the number of parallel
574 connections to a server per client IP address (or address block).
576 config NETFILTER_XT_MATCH_CONNMARK
577 tristate '"connmark" connection mark match support'
578 depends on NF_CONNTRACK
579 depends on NETFILTER_ADVANCED
580 select NF_CONNTRACK_MARK
582 This option adds a `connmark' match, which allows you to match the
583 connection mark value previously set for the session by `CONNMARK'.
585 If you want to compile it as a module, say M here and read
586 <file:Documentation/kbuild/modules.txt>. The module will be called
587 ipt_connmark.ko. If unsure, say `N'.
589 config NETFILTER_XT_MATCH_CONNTRACK
590 tristate '"conntrack" connection tracking match support'
591 depends on NF_CONNTRACK
592 default m if NETFILTER_ADVANCED=n
594 This is a general conntrack match module, a superset of the state match.
596 It allows matching on additional conntrack information, which is
597 useful in complex configurations, such as NAT gateways with multiple
598 internet links or tunnels.
600 To compile it as a module, choose M here. If unsure, say N.
602 config NETFILTER_XT_MATCH_DCCP
603 tristate '"dccp" protocol match support'
604 depends on NETFILTER_ADVANCED
607 With this option enabled, you will be able to use the iptables
608 `dccp' match in order to match on DCCP source/destination ports
611 If you want to compile it as a module, say M here and read
612 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
614 config NETFILTER_XT_MATCH_DSCP
615 tristate '"dscp" and "tos" match support'
616 depends on NETFILTER_ADVANCED
618 This option adds a `DSCP' match, which allows you to match against
619 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
621 The DSCP field can have any value between 0x0 and 0x3f inclusive.
623 It will also add a "tos" match, which allows you to match packets
624 based on the Type Of Service fields of the IPv4 packet (which share
625 the same bits as DSCP).
627 To compile it as a module, choose M here. If unsure, say N.
629 config NETFILTER_XT_MATCH_ESP
630 tristate '"esp" match support'
631 depends on NETFILTER_ADVANCED
633 This match extension allows you to match a range of SPIs
634 inside ESP header of IPSec packets.
636 To compile it as a module, choose M here. If unsure, say N.
638 config NETFILTER_XT_MATCH_HASHLIMIT
639 tristate '"hashlimit" match support'
640 depends on (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
641 depends on NETFILTER_ADVANCED
643 This option adds a `hashlimit' match.
645 As opposed to `limit', this match dynamically creates a hash table
646 of limit buckets, based on your selection of source/destination
647 addresses and/or ports.
649 It enables you to express policies like `10kpps for any given
650 destination address' or `500pps from any given source address'
653 config NETFILTER_XT_MATCH_HELPER
654 tristate '"helper" match support'
655 depends on NF_CONNTRACK
656 depends on NETFILTER_ADVANCED
658 Helper matching allows you to match packets in dynamic connections
659 tracked by a conntrack-helper, ie. ip_conntrack_ftp
661 To compile it as a module, choose M here. If unsure, say Y.
663 config NETFILTER_XT_MATCH_HL
664 tristate '"hl" hoplimit/TTL match support'
665 depends on NETFILTER_ADVANCED
667 HL matching allows you to match packets based on the hoplimit
668 in the IPv6 header, or the time-to-live field in the IPv4
669 header of the packet.
671 config NETFILTER_XT_MATCH_IPRANGE
672 tristate '"iprange" address range match support'
673 depends on NETFILTER_ADVANCED
675 This option adds a "iprange" match, which allows you to match based on
676 an IP address range. (Normal iptables only matches on single addresses
677 with an optional mask.)
681 config NETFILTER_XT_MATCH_LENGTH
682 tristate '"length" match support'
683 depends on NETFILTER_ADVANCED
685 This option allows you to match the length of a packet against a
686 specific value or range of values.
688 To compile it as a module, choose M here. If unsure, say N.
690 config NETFILTER_XT_MATCH_LIMIT
691 tristate '"limit" match support'
692 depends on NETFILTER_ADVANCED
694 limit matching allows you to control the rate at which a rule can be
695 matched: mainly useful in combination with the LOG target ("LOG
696 target support", below) and to avoid some Denial of Service attacks.
698 To compile it as a module, choose M here. If unsure, say N.
700 config NETFILTER_XT_MATCH_MAC
701 tristate '"mac" address match support'
702 depends on NETFILTER_ADVANCED
704 MAC matching allows you to match packets based on the source
705 Ethernet address of the packet.
707 To compile it as a module, choose M here. If unsure, say N.
709 config NETFILTER_XT_MATCH_MARK
710 tristate '"mark" match support'
711 default m if NETFILTER_ADVANCED=n
713 Netfilter mark matching allows you to match packets based on the
714 `nfmark' value in the packet. This can be set by the MARK target
717 To compile it as a module, choose M here. If unsure, say N.
719 config NETFILTER_XT_MATCH_MULTIPORT
720 tristate '"multiport" Multiple port match support'
721 depends on NETFILTER_ADVANCED
723 Multiport matching allows you to match TCP or UDP packets based on
724 a series of source or destination ports: normally a rule can only
725 match a single range of ports.
727 To compile it as a module, choose M here. If unsure, say N.
729 config NETFILTER_XT_MATCH_OWNER
730 tristate '"owner" match support'
731 depends on NETFILTER_ADVANCED
733 Socket owner matching allows you to match locally-generated packets
734 based on who created the socket: the user or group. It is also
735 possible to check whether a socket actually exists.
737 config NETFILTER_XT_MATCH_POLICY
738 tristate 'IPsec "policy" match support'
740 default m if NETFILTER_ADVANCED=n
742 Policy matching allows you to match packets based on the
743 IPsec policy that was used during decapsulation/will
744 be used during encapsulation.
746 To compile it as a module, choose M here. If unsure, say N.
748 config NETFILTER_XT_MATCH_PHYSDEV
749 tristate '"physdev" match support'
750 depends on BRIDGE && BRIDGE_NETFILTER
751 depends on NETFILTER_ADVANCED
753 Physdev packet matching matches against the physical bridge ports
754 the IP packet arrived on or will leave by.
756 To compile it as a module, choose M here. If unsure, say N.
758 config NETFILTER_XT_MATCH_PKTTYPE
759 tristate '"pkttype" packet type match support'
760 depends on NETFILTER_ADVANCED
762 Packet type matching allows you to match a packet by
763 its "class", eg. BROADCAST, MULTICAST, ...
766 iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG
768 To compile it as a module, choose M here. If unsure, say N.
770 config NETFILTER_XT_MATCH_QUOTA
771 tristate '"quota" match support'
772 depends on NETFILTER_ADVANCED
774 This option adds a `quota' match, which allows to match on a
777 If you want to compile it as a module, say M here and read
778 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
780 config NETFILTER_XT_MATCH_RATEEST
781 tristate '"rateest" match support'
782 depends on NETFILTER_ADVANCED
783 select NETFILTER_XT_TARGET_RATEEST
785 This option adds a `rateest' match, which allows to match on the
786 rate estimated by the RATEEST target.
788 To compile it as a module, choose M here. If unsure, say N.
790 config NETFILTER_XT_MATCH_REALM
791 tristate '"realm" match support'
792 depends on NETFILTER_ADVANCED
795 This option adds a `realm' match, which allows you to use the realm
796 key from the routing subsystem inside iptables.
798 This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option
801 If you want to compile it as a module, say M here and read
802 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
804 config NETFILTER_XT_MATCH_RECENT
805 tristate '"recent" match support'
806 depends on NETFILTER_ADVANCED
808 This match is used for creating one or many lists of recently
809 used addresses and then matching against that/those list(s).
811 Short options are available by using 'iptables -m recent -h'
812 Official Website: <http://snowman.net/projects/ipt_recent/>
814 config NETFILTER_XT_MATCH_RECENT_PROC_COMPAT
815 bool 'Enable obsolete /proc/net/ipt_recent'
816 depends on NETFILTER_XT_MATCH_RECENT && PROC_FS
818 This option enables the old /proc/net/ipt_recent interface,
819 which has been obsoleted by /proc/net/xt_recent.
821 config NETFILTER_XT_MATCH_SCTP
822 tristate '"sctp" protocol match support (EXPERIMENTAL)'
823 depends on EXPERIMENTAL
824 depends on NETFILTER_ADVANCED
827 With this option enabled, you will be able to use the
828 `sctp' match in order to match on SCTP source/destination ports
829 and SCTP chunk types.
831 If you want to compile it as a module, say M here and read
832 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
834 config NETFILTER_XT_MATCH_SOCKET
835 tristate '"socket" match support (EXPERIMENTAL)'
836 depends on EXPERIMENTAL
837 depends on NETFILTER_TPROXY
838 depends on NETFILTER_XTABLES
839 depends on NETFILTER_ADVANCED
840 select NF_DEFRAG_IPV4
842 This option adds a `socket' match, which can be used to match
843 packets for which a TCP or UDP socket lookup finds a valid socket.
844 It can be used in combination with the MARK target and policy
845 routing to implement full featured non-locally bound sockets.
847 To compile it as a module, choose M here. If unsure, say N.
849 config NETFILTER_XT_MATCH_STATE
850 tristate '"state" match support'
851 depends on NF_CONNTRACK
852 default m if NETFILTER_ADVANCED=n
854 Connection state matching allows you to match packets based on their
855 relationship to a tracked connection (ie. previous packets). This
856 is a powerful tool for packet classification.
858 To compile it as a module, choose M here. If unsure, say N.
860 config NETFILTER_XT_MATCH_STATISTIC
861 tristate '"statistic" match support'
862 depends on NETFILTER_ADVANCED
864 This option adds a `statistic' match, which allows you to match
865 on packets periodically or randomly with a given percentage.
867 To compile it as a module, choose M here. If unsure, say N.
869 config NETFILTER_XT_MATCH_STRING
870 tristate '"string" match support'
871 depends on NETFILTER_ADVANCED
873 select TEXTSEARCH_KMP
875 select TEXTSEARCH_FSM
877 This option adds a `string' match, which allows you to look for
878 pattern matchings in packets.
880 To compile it as a module, choose M here. If unsure, say N.
882 config NETFILTER_XT_MATCH_TCPMSS
883 tristate '"tcpmss" match support'
884 depends on NETFILTER_ADVANCED
886 This option adds a `tcpmss' match, which allows you to examine the
887 MSS value of TCP SYN packets, which control the maximum packet size
890 To compile it as a module, choose M here. If unsure, say N.
892 config NETFILTER_XT_MATCH_TIME
893 tristate '"time" match support'
894 depends on NETFILTER_ADVANCED
896 This option adds a "time" match, which allows you to match based on
897 the packet arrival time (at the machine which netfilter is running)
898 on) or departure time/date (for locally generated packets).
900 If you say Y here, try `iptables -m time --help` for
903 If you want to compile it as a module, say M here.
906 config NETFILTER_XT_MATCH_U32
907 tristate '"u32" match support'
908 depends on NETFILTER_ADVANCED
910 u32 allows you to extract quantities of up to 4 bytes from a packet,
911 AND them with specified masks, shift them by specified amounts and
912 test whether the results are in any of a set of specified ranges.
913 The specification of what to extract is general enough to skip over
914 headers with lengths stored in the packet, as in IP or TCP header
917 Details and examples are in the kernel module source.
919 endif # NETFILTER_XTABLES
923 source "net/netfilter/ipvs/Kconfig"