1 menu "Core Netfilter Configuration"
2 depends on NET && INET && NETFILTER
4 config NETFILTER_NETLINK
7 config NETFILTER_NETLINK_ACCT
8 tristate "Netfilter NFACCT 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 extended accounting via NFNETLINK.
15 config NETFILTER_NETLINK_QUEUE
16 tristate "Netfilter NFQUEUE over NFNETLINK interface"
17 depends on NETFILTER_ADVANCED
18 select NETFILTER_NETLINK
20 If this option is enabled, the kernel will include support
21 for queueing packets via NFNETLINK.
23 config NETFILTER_NETLINK_LOG
24 tristate "Netfilter LOG over NFNETLINK interface"
25 default m if NETFILTER_ADVANCED=n
26 select NETFILTER_NETLINK
28 If this option is enabled, the kernel will include support
29 for logging packets via NFNETLINK.
31 This obsoletes the existing ipt_ULOG and ebg_ulog mechanisms,
32 and is also scheduled to replace the old syslog-based ipt_LOG
36 tristate "Netfilter connection tracking support"
37 default m if NETFILTER_ADVANCED=n
39 Connection tracking keeps a record of what packets have passed
40 through your machine, in order to figure out how they are related
43 This is required to do Masquerading or other kinds of Network
44 Address Translation. It can also be used to enhance packet
45 filtering (see `Connection state match support' below).
47 To compile it as a module, choose M here. If unsure, say N.
51 config NF_CONNTRACK_MARK
52 bool 'Connection mark tracking support'
53 depends on NETFILTER_ADVANCED
55 This option enables support for connection marks, used by the
56 `CONNMARK' target and `connmark' match. Similar to the mark value
57 of packets, but this mark value is kept in the conntrack session
58 instead of the individual packets.
60 config NF_CONNTRACK_SECMARK
61 bool 'Connection tracking security mark support'
62 depends on NETWORK_SECMARK
63 default m if NETFILTER_ADVANCED=n
65 This option enables security markings to be applied to
66 connections. Typically they are copied to connections from
67 packets using the CONNSECMARK target and copied back from
68 connections to packets with the same target, with the packets
69 being originally labeled via SECMARK.
73 config NF_CONNTRACK_ZONES
74 bool 'Connection tracking zones'
75 depends on NETFILTER_ADVANCED
76 depends on NETFILTER_XT_TARGET_CT
78 This option enables support for connection tracking zones.
79 Normally, each connection needs to have a unique system wide
80 identity. Connection tracking zones allow to have multiple
81 connections using the same identity, as long as they are
82 contained in different zones.
86 config NF_CONNTRACK_PROCFS
87 bool "Supply CT list in procfs (OBSOLETE)"
91 This option enables for the list of known conntrack entries
92 to be shown in procfs under net/netfilter/nf_conntrack. This
93 is considered obsolete in favor of using the conntrack(8)
94 tool which uses Netlink.
96 config NF_CONNTRACK_EVENTS
97 bool "Connection tracking events"
98 depends on NETFILTER_ADVANCED
100 If this option is enabled, the connection tracking code will
101 provide a notifier chain that can be used by other kernel code
102 to get notified about changes in the connection tracking state.
106 config NF_CONNTRACK_TIMEOUT
107 bool 'Connection tracking timeout'
108 depends on NETFILTER_ADVANCED
110 This option enables support for connection tracking timeout
111 extension. This allows you to attach timeout policies to flow
116 config NF_CONNTRACK_TIMESTAMP
117 bool 'Connection tracking timestamping'
118 depends on NETFILTER_ADVANCED
120 This option enables support for connection tracking timestamping.
121 This allows you to store the flow start-time and to obtain
122 the flow-stop time (once it has been destroyed) via Connection
127 config NF_CONNTRACK_LABELS
130 This option enables support for assigning user-defined flag bits
131 to connection tracking entries. It selected by the connlabel match.
133 config NF_CT_PROTO_DCCP
134 tristate 'DCCP protocol connection tracking support'
135 depends on NETFILTER_ADVANCED
138 With this option enabled, the layer 3 independent connection
139 tracking code will be able to do state tracking on DCCP connections.
143 config NF_CT_PROTO_GRE
146 config NF_CT_PROTO_SCTP
147 tristate 'SCTP protocol connection tracking support'
148 depends on NETFILTER_ADVANCED
151 With this option enabled, the layer 3 independent connection
152 tracking code will be able to do state tracking on SCTP connections.
154 If you want to compile it as a module, say M here and read
155 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
157 config NF_CT_PROTO_UDPLITE
158 tristate 'UDP-Lite protocol connection tracking support'
159 depends on NETFILTER_ADVANCED
161 With this option enabled, the layer 3 independent connection
162 tracking code will be able to do state tracking on UDP-Lite
165 To compile it as a module, choose M here. If unsure, say N.
167 config NF_CONNTRACK_AMANDA
168 tristate "Amanda backup protocol support"
169 depends on NETFILTER_ADVANCED
171 select TEXTSEARCH_KMP
173 If you are running the Amanda backup package <http://www.amanda.org/>
174 on this machine or machines that will be MASQUERADED through this
175 machine, then you may want to enable this feature. This allows the
176 connection tracking and natting code to allow the sub-channels that
177 Amanda requires for communication of the backup data, messages and
180 To compile it as a module, choose M here. If unsure, say N.
182 config NF_CONNTRACK_FTP
183 tristate "FTP protocol support"
184 default m if NETFILTER_ADVANCED=n
186 Tracking FTP connections is problematic: special helpers are
187 required for tracking them, and doing masquerading and other forms
188 of Network Address Translation on them.
190 This is FTP support on Layer 3 independent connection tracking.
191 Layer 3 independent connection tracking is experimental scheme
192 which generalize ip_conntrack to support other layer 3 protocols.
194 To compile it as a module, choose M here. If unsure, say N.
196 config NF_CONNTRACK_H323
197 tristate "H.323 protocol support"
198 depends on (IPV6 || IPV6=n)
199 depends on NETFILTER_ADVANCED
201 H.323 is a VoIP signalling protocol from ITU-T. As one of the most
202 important VoIP protocols, it is widely used by voice hardware and
203 software including voice gateways, IP phones, Netmeeting, OpenPhone,
206 With this module you can support H.323 on a connection tracking/NAT
209 This module supports RAS, Fast Start, H.245 Tunnelling, Call
210 Forwarding, RTP/RTCP and T.120 based audio, video, fax, chat,
211 whiteboard, file transfer, etc. For more information, please
212 visit http://nath323.sourceforge.net/.
214 To compile it as a module, choose M here. If unsure, say N.
216 config NF_CONNTRACK_IRC
217 tristate "IRC protocol support"
218 default m if NETFILTER_ADVANCED=n
220 There is a commonly-used extension to IRC called
221 Direct Client-to-Client Protocol (DCC). This enables users to send
222 files to each other, and also chat to each other without the need
223 of a server. DCC Sending is used anywhere you send files over IRC,
224 and DCC Chat is most commonly used by Eggdrop bots. If you are
225 using NAT, this extension will enable you to send files and initiate
226 chats. Note that you do NOT need this extension to get files or
227 have others initiate chats, or everything else in IRC.
229 To compile it as a module, choose M here. If unsure, say N.
231 config NF_CONNTRACK_BROADCAST
234 config NF_CONNTRACK_NETBIOS_NS
235 tristate "NetBIOS name service protocol support"
236 select NF_CONNTRACK_BROADCAST
238 NetBIOS name service requests are sent as broadcast messages from an
239 unprivileged port and responded to with unicast messages to the
240 same port. This make them hard to firewall properly because connection
241 tracking doesn't deal with broadcasts. This helper tracks locally
242 originating NetBIOS name service requests and the corresponding
243 responses. It relies on correct IP address configuration, specifically
244 netmask and broadcast address. When properly configured, the output
245 of "ip address show" should look similar to this:
247 $ ip -4 address show eth0
248 4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
249 inet 172.16.2.252/24 brd 172.16.2.255 scope global eth0
251 To compile it as a module, choose M here. If unsure, say N.
253 config NF_CONNTRACK_SNMP
254 tristate "SNMP service protocol support"
255 depends on NETFILTER_ADVANCED
256 select NF_CONNTRACK_BROADCAST
258 SNMP service requests are sent as broadcast messages from an
259 unprivileged port and responded to with unicast messages to the
260 same port. This make them hard to firewall properly because connection
261 tracking doesn't deal with broadcasts. This helper tracks locally
262 originating SNMP service requests and the corresponding
263 responses. It relies on correct IP address configuration, specifically
264 netmask and broadcast address.
266 To compile it as a module, choose M here. If unsure, say N.
268 config NF_CONNTRACK_PPTP
269 tristate "PPtP protocol support"
270 depends on NETFILTER_ADVANCED
271 select NF_CT_PROTO_GRE
273 This module adds support for PPTP (Point to Point Tunnelling
274 Protocol, RFC2637) connection tracking and NAT.
276 If you are running PPTP sessions over a stateful firewall or NAT
277 box, you may want to enable this feature.
279 Please note that not all PPTP modes of operation are supported yet.
280 Specifically these limitations exist:
281 - Blindly assumes that control connections are always established
282 in PNS->PAC direction. This is a violation of RFC2637.
283 - Only supports a single call within each session
285 To compile it as a module, choose M here. If unsure, say N.
287 config NF_CONNTRACK_SANE
288 tristate "SANE protocol support"
289 depends on NETFILTER_ADVANCED
291 SANE is a protocol for remote access to scanners as implemented
292 by the 'saned' daemon. Like FTP, it uses separate control and
295 With this module you can support SANE on a connection tracking
298 To compile it as a module, choose M here. If unsure, say N.
300 config NF_CONNTRACK_SIP
301 tristate "SIP protocol support"
302 default m if NETFILTER_ADVANCED=n
304 SIP is an application-layer control protocol that can establish,
305 modify, and terminate multimedia sessions (conferences) such as
306 Internet telephony calls. With the ip_conntrack_sip and
307 the nf_nat_sip modules you can support the protocol on a connection
308 tracking/NATing firewall.
310 To compile it as a module, choose M here. If unsure, say N.
312 config NF_CONNTRACK_TFTP
313 tristate "TFTP protocol support"
314 depends on NETFILTER_ADVANCED
316 TFTP connection tracking helper, this is required depending
317 on how restrictive your ruleset is.
318 If you are using a tftp client behind -j SNAT or -j MASQUERADING
321 To compile it as a module, choose M here. If unsure, say N.
324 tristate 'Connection tracking netlink interface'
325 select NETFILTER_NETLINK
326 default m if NETFILTER_ADVANCED=n
328 This option enables support for a netlink-based userspace interface
330 config NF_CT_NETLINK_TIMEOUT
331 tristate 'Connection tracking timeout tuning via Netlink'
332 select NETFILTER_NETLINK
333 depends on NETFILTER_ADVANCED
335 This option enables support for connection tracking timeout
336 fine-grain tuning. This allows you to attach specific timeout
337 policies to flows, instead of using the global timeout policy.
341 config NF_CT_NETLINK_HELPER
342 tristate 'Connection tracking helpers in user-space via Netlink'
343 select NETFILTER_NETLINK
344 depends on NF_CT_NETLINK
345 depends on NETFILTER_NETLINK_QUEUE
346 depends on NETFILTER_NETLINK_QUEUE_CT
347 depends on NETFILTER_ADVANCED
349 This option enables the user-space connection tracking helpers
354 config NETFILTER_NETLINK_QUEUE_CT
355 bool "NFQUEUE integration with Connection Tracking"
357 depends on NETFILTER_NETLINK_QUEUE
359 If this option is enabled, NFQUEUE can include Connection Tracking
360 information together with the packet is the enqueued via NFNETLINK.
370 config NF_NAT_PROTO_DCCP
372 depends on NF_NAT && NF_CT_PROTO_DCCP
373 default NF_NAT && NF_CT_PROTO_DCCP
375 config NF_NAT_PROTO_UDPLITE
377 depends on NF_NAT && NF_CT_PROTO_UDPLITE
378 default NF_NAT && NF_CT_PROTO_UDPLITE
380 config NF_NAT_PROTO_SCTP
382 default NF_NAT && NF_CT_PROTO_SCTP
383 depends on NF_NAT && NF_CT_PROTO_SCTP
388 depends on NF_CONNTRACK && NF_NAT
389 default NF_NAT && NF_CONNTRACK_AMANDA
393 depends on NF_CONNTRACK && NF_NAT
394 default NF_NAT && NF_CONNTRACK_FTP
398 depends on NF_CONNTRACK && NF_NAT
399 default NF_NAT && NF_CONNTRACK_IRC
403 depends on NF_CONNTRACK && NF_NAT
404 default NF_NAT && NF_CONNTRACK_SIP
408 depends on NF_CONNTRACK && NF_NAT
409 default NF_NAT && NF_CONNTRACK_TFTP
411 config NETFILTER_SYNPROXY
417 depends on NETFILTER_NETLINK
418 tristate "Netfilter nf_tables support"
422 tristate "Netfilter nf_tables IPv6 exthdr module"
426 tristate "Netfilter nf_tables meta module"
430 depends on NF_CONNTRACK
431 tristate "Netfilter nf_tables conntrack module"
435 tristate "Netfilter nf_tables rbtree set module"
439 tristate "Netfilter nf_tables hash set module"
443 tristate "Netfilter nf_tables counter module"
447 tristate "Netfilter nf_tables log module"
451 tristate "Netfilter nf_tables limit module"
455 depends on NF_CONNTRACK
457 tristate "Netfilter nf_tables nat module"
461 depends on NETFILTER_XTABLES
462 tristate "Netfilter x_tables over nf_tables module"
464 This is required if you intend to use any of existing
465 x_tables match/target extensions over the nf_tables
468 config NETFILTER_XTABLES
469 tristate "Netfilter Xtables support (required for ip_tables)"
470 default m if NETFILTER_ADVANCED=n
472 This is required if you intend to use any of ip_tables,
473 ip6_tables or arp_tables.
477 comment "Xtables combined modules"
479 config NETFILTER_XT_MARK
480 tristate 'nfmark target and match support'
481 default m if NETFILTER_ADVANCED=n
483 This option adds the "MARK" target and "mark" match.
485 Netfilter mark matching allows you to match packets based on the
486 "nfmark" value in the packet.
487 The target allows you to create rules in the "mangle" table which alter
488 the netfilter mark (nfmark) field associated with the packet.
490 Prior to routing, the nfmark can influence the routing method (see
491 "Use netfilter MARK value as routing key") and can also be used by
492 other subsystems to change their behavior.
494 config NETFILTER_XT_CONNMARK
495 tristate 'ctmark target and match support'
496 depends on NF_CONNTRACK
497 depends on NETFILTER_ADVANCED
498 select NF_CONNTRACK_MARK
500 This option adds the "CONNMARK" target and "connmark" match.
502 Netfilter allows you to store a mark value per connection (a.k.a.
503 ctmark), similarly to the packet mark (nfmark). Using this
504 target and match, you can set and match on this mark.
506 config NETFILTER_XT_SET
507 tristate 'set target and match support'
509 depends on NETFILTER_ADVANCED
511 This option adds the "SET" target and "set" match.
513 Using this target and match, you can add/delete and match
514 elements in the sets created by ipset(8).
516 To compile it as a module, choose M here. If unsure, say N.
518 # alphabetically ordered list of targets
520 comment "Xtables targets"
522 config NETFILTER_XT_TARGET_AUDIT
523 tristate "AUDIT target support"
525 depends on NETFILTER_ADVANCED
527 This option adds a 'AUDIT' target, which can be used to create
528 audit records for packets dropped/accepted.
530 To compileit as a module, choose M here. If unsure, say N.
532 config NETFILTER_XT_TARGET_CHECKSUM
533 tristate "CHECKSUM target support"
534 depends on IP_NF_MANGLE || IP6_NF_MANGLE
535 depends on NETFILTER_ADVANCED
537 This option adds a `CHECKSUM' target, which can be used in the iptables mangle
540 You can use this target to compute and fill in the checksum in
541 a packet that lacks a checksum. This is particularly useful,
542 if you need to work around old applications such as dhcp clients,
543 that do not work well with checksum offloads, but don't want to disable
544 checksum offload in your device.
546 To compile it as a module, choose M here. If unsure, say N.
548 config NETFILTER_XT_TARGET_CLASSIFY
549 tristate '"CLASSIFY" target support'
550 depends on NETFILTER_ADVANCED
552 This option adds a `CLASSIFY' target, which enables the user to set
553 the priority of a packet. Some qdiscs can use this value for
554 classification, among these are:
556 atm, cbq, dsmark, pfifo_fast, htb, prio
558 To compile it as a module, choose M here. If unsure, say N.
560 config NETFILTER_XT_TARGET_CONNMARK
561 tristate '"CONNMARK" target support'
562 depends on NF_CONNTRACK
563 depends on NETFILTER_ADVANCED
564 select NETFILTER_XT_CONNMARK
566 This is a backwards-compat option for the user's convenience
567 (e.g. when running oldconfig). It selects
568 CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
570 config NETFILTER_XT_TARGET_CONNSECMARK
571 tristate '"CONNSECMARK" target support'
572 depends on NF_CONNTRACK && NF_CONNTRACK_SECMARK
573 default m if NETFILTER_ADVANCED=n
575 The CONNSECMARK target copies security markings from packets
576 to connections, and restores security markings from connections
577 to packets (if the packets are not already marked). This would
578 normally be used in conjunction with the SECMARK target.
580 To compile it as a module, choose M here. If unsure, say N.
582 config NETFILTER_XT_TARGET_CT
583 tristate '"CT" target support'
584 depends on NF_CONNTRACK
585 depends on IP_NF_RAW || IP6_NF_RAW
586 depends on NETFILTER_ADVANCED
588 This options adds a `CT' target, which allows to specify initial
589 connection tracking parameters like events to be delivered and
590 the helper to be used.
592 To compile it as a module, choose M here. If unsure, say N.
594 config NETFILTER_XT_TARGET_DSCP
595 tristate '"DSCP" and "TOS" target support'
596 depends on IP_NF_MANGLE || IP6_NF_MANGLE
597 depends on NETFILTER_ADVANCED
599 This option adds a `DSCP' target, which allows you to manipulate
600 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
602 The DSCP field can have any value between 0x0 and 0x3f inclusive.
604 It also adds the "TOS" target, which allows you to create rules in
605 the "mangle" table which alter the Type Of Service field of an IPv4
606 or the Priority field of an IPv6 packet, prior to routing.
608 To compile it as a module, choose M here. If unsure, say N.
610 config NETFILTER_XT_TARGET_HL
611 tristate '"HL" hoplimit target support'
612 depends on IP_NF_MANGLE || IP6_NF_MANGLE
613 depends on NETFILTER_ADVANCED
615 This option adds the "HL" (for IPv6) and "TTL" (for IPv4)
616 targets, which enable the user to change the
617 hoplimit/time-to-live value of the IP header.
619 While it is safe to decrement the hoplimit/TTL value, the
620 modules also allow to increment and set the hoplimit value of
621 the header to arbitrary values. This is EXTREMELY DANGEROUS
622 since you can easily create immortal packets that loop
623 forever on the network.
625 config NETFILTER_XT_TARGET_HMARK
626 tristate '"HMARK" target support'
627 depends on (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
628 depends on NETFILTER_ADVANCED
630 This option adds the "HMARK" target.
632 The target allows you to create rules in the "raw" and "mangle" tables
633 which set the skbuff mark by means of hash calculation within a given
634 range. The nfmark can influence the routing method (see "Use netfilter
635 MARK value as routing key") and can also be used by other subsystems to
636 change their behaviour.
638 To compile it as a module, choose M here. If unsure, say N.
640 config NETFILTER_XT_TARGET_IDLETIMER
641 tristate "IDLETIMER target support"
642 depends on NETFILTER_ADVANCED
645 This option adds the `IDLETIMER' target. Each matching packet
646 resets the timer associated with label specified when the rule is
647 added. When the timer expires, it triggers a sysfs notification.
648 The remaining time for expiration can be read via sysfs.
650 To compile it as a module, choose M here. If unsure, say N.
652 config NETFILTER_XT_TARGET_LED
653 tristate '"LED" target support'
654 depends on LEDS_CLASS && LEDS_TRIGGERS
655 depends on NETFILTER_ADVANCED
657 This option adds a `LED' target, which allows you to blink LEDs in
658 response to particular packets passing through your machine.
660 This can be used to turn a spare LED into a network activity LED,
661 which only flashes in response to FTP transfers, for example. Or
662 you could have an LED which lights up for a minute or two every time
663 somebody connects to your machine via SSH.
665 You will need support for the "led" class to make this work.
667 To create an LED trigger for incoming SSH traffic:
668 iptables -A INPUT -p tcp --dport 22 -j LED --led-trigger-id ssh --led-delay 1000
670 Then attach the new trigger to an LED on your system:
671 echo netfilter-ssh > /sys/class/leds/<ledname>/trigger
673 For more information on the LEDs available on your system, see
674 Documentation/leds/leds-class.txt
676 config NETFILTER_XT_TARGET_LOG
677 tristate "LOG target support"
678 default m if NETFILTER_ADVANCED=n
680 This option adds a `LOG' target, which allows you to create rules in
681 any iptables table which records the packet header to the syslog.
683 To compile it as a module, choose M here. If unsure, say N.
685 config NETFILTER_XT_TARGET_MARK
686 tristate '"MARK" target support'
687 depends on NETFILTER_ADVANCED
688 select NETFILTER_XT_MARK
690 This is a backwards-compat option for the user's convenience
691 (e.g. when running oldconfig). It selects
692 CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
694 config NETFILTER_XT_TARGET_NETMAP
695 tristate '"NETMAP" target support'
698 NETMAP is an implementation of static 1:1 NAT mapping of network
699 addresses. It maps the network address part, while keeping the host
702 To compile it as a module, choose M here. If unsure, say N.
704 config NETFILTER_XT_TARGET_NFLOG
705 tristate '"NFLOG" target support'
706 default m if NETFILTER_ADVANCED=n
707 select NETFILTER_NETLINK_LOG
709 This option enables the NFLOG target, which allows to LOG
710 messages through nfnetlink_log.
712 To compile it as a module, choose M here. If unsure, say N.
714 config NETFILTER_XT_TARGET_NFQUEUE
715 tristate '"NFQUEUE" target Support'
716 depends on NETFILTER_ADVANCED
717 select NETFILTER_NETLINK_QUEUE
719 This target replaced the old obsolete QUEUE target.
721 As opposed to QUEUE, it supports 65535 different queues,
724 To compile it as a module, choose M here. If unsure, say N.
726 config NETFILTER_XT_TARGET_NOTRACK
727 tristate '"NOTRACK" target support (DEPRECATED)'
728 depends on NF_CONNTRACK
729 depends on IP_NF_RAW || IP6_NF_RAW
730 depends on NETFILTER_ADVANCED
731 select NETFILTER_XT_TARGET_CT
733 config NETFILTER_XT_TARGET_RATEEST
734 tristate '"RATEEST" target support'
735 depends on NETFILTER_ADVANCED
737 This option adds a `RATEEST' target, which allows to measure
738 rates similar to TC estimators. The `rateest' match can be
739 used to match on the measured rates.
741 To compile it as a module, choose M here. If unsure, say N.
743 config NETFILTER_XT_TARGET_REDIRECT
744 tristate "REDIRECT target support"
747 REDIRECT is a special case of NAT: all incoming connections are
748 mapped onto the incoming interface's address, causing the packets to
749 come to the local machine instead of passing through. This is
750 useful for transparent proxies.
752 To compile it as a module, choose M here. If unsure, say N.
754 config NETFILTER_XT_TARGET_TEE
755 tristate '"TEE" - packet cloning to alternate destination'
756 depends on NETFILTER_ADVANCED
757 depends on (IPV6 || IPV6=n)
758 depends on !NF_CONNTRACK || NF_CONNTRACK
760 This option adds a "TEE" target with which a packet can be cloned and
761 this clone be rerouted to another nexthop.
763 config NETFILTER_XT_TARGET_TPROXY
764 tristate '"TPROXY" target transparent proxying support'
765 depends on NETFILTER_XTABLES
766 depends on NETFILTER_ADVANCED
767 depends on IP_NF_MANGLE
768 select NF_DEFRAG_IPV4
769 select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES
771 This option adds a `TPROXY' target, which is somewhat similar to
772 REDIRECT. It can only be used in the mangle table and is useful
773 to redirect traffic to a transparent proxy. It does _not_ depend
774 on Netfilter connection tracking and NAT, unlike REDIRECT.
775 For it to work you will have to configure certain iptables rules
776 and use policy routing. For more information on how to set it up
777 see Documentation/networking/tproxy.txt.
779 To compile it as a module, choose M here. If unsure, say N.
781 config NETFILTER_XT_TARGET_TRACE
782 tristate '"TRACE" target support'
783 depends on IP_NF_RAW || IP6_NF_RAW
784 depends on NETFILTER_ADVANCED
786 The TRACE target allows you to mark packets so that the kernel
787 will log every rule which match the packets as those traverse
788 the tables, chains, rules.
790 If you want to compile it as a module, say M here and read
791 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
793 config NETFILTER_XT_TARGET_SECMARK
794 tristate '"SECMARK" target support'
795 depends on NETWORK_SECMARK
796 default m if NETFILTER_ADVANCED=n
798 The SECMARK target allows security marking of network
799 packets, for use with security subsystems.
801 To compile it as a module, choose M here. If unsure, say N.
803 config NETFILTER_XT_TARGET_TCPMSS
804 tristate '"TCPMSS" target support'
805 depends on (IPV6 || IPV6=n)
806 default m if NETFILTER_ADVANCED=n
808 This option adds a `TCPMSS' target, which allows you to alter the
809 MSS value of TCP SYN packets, to control the maximum size for that
810 connection (usually limiting it to your outgoing interface's MTU
813 This is used to overcome criminally braindead ISPs or servers which
814 block ICMP Fragmentation Needed packets. The symptoms of this
815 problem are that everything works fine from your Linux
816 firewall/router, but machines behind it can never exchange large
818 1) Web browsers connect, then hang with no data received.
819 2) Small mail works fine, but large emails hang.
820 3) ssh works fine, but scp hangs after initial handshaking.
822 Workaround: activate this option and add a rule to your firewall
825 iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
826 -j TCPMSS --clamp-mss-to-pmtu
828 To compile it as a module, choose M here. If unsure, say N.
830 config NETFILTER_XT_TARGET_TCPOPTSTRIP
831 tristate '"TCPOPTSTRIP" target support'
832 depends on IP_NF_MANGLE || IP6_NF_MANGLE
833 depends on NETFILTER_ADVANCED
835 This option adds a "TCPOPTSTRIP" target, which allows you to strip
836 TCP options from TCP packets.
838 # alphabetically ordered list of matches
840 comment "Xtables matches"
842 config NETFILTER_XT_MATCH_ADDRTYPE
843 tristate '"addrtype" address type match support'
844 depends on NETFILTER_ADVANCED
846 This option allows you to match what routing thinks of an address,
847 eg. UNICAST, LOCAL, BROADCAST, ...
849 If you want to compile it as a module, say M here and read
850 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
852 config NETFILTER_XT_MATCH_BPF
853 tristate '"bpf" match support'
854 depends on NETFILTER_ADVANCED
856 BPF matching applies a linux socket filter to each packet and
857 accepts those for which the filter returns non-zero.
859 To compile it as a module, choose M here. If unsure, say N.
861 config NETFILTER_XT_MATCH_CGROUP
862 tristate '"control group" match support'
863 depends on NETFILTER_ADVANCED
865 select CGROUP_NET_CLASSID
867 Socket/process control group matching allows you to match locally
868 generated packets based on which net_cls control group processes
871 config NETFILTER_XT_MATCH_CLUSTER
872 tristate '"cluster" match support'
873 depends on NF_CONNTRACK
874 depends on NETFILTER_ADVANCED
876 This option allows you to build work-load-sharing clusters of
877 network servers/stateful firewalls without having a dedicated
878 load-balancing router/server/switch. Basically, this match returns
879 true when the packet must be handled by this cluster node. Thus,
880 all nodes see all packets and this match decides which node handles
881 what packets. The work-load sharing algorithm is based on source
884 If you say Y or M here, try `iptables -m cluster --help` for
887 config NETFILTER_XT_MATCH_COMMENT
888 tristate '"comment" match support'
889 depends on NETFILTER_ADVANCED
891 This option adds a `comment' dummy-match, which allows you to put
892 comments in your iptables ruleset.
894 If you want to compile it as a module, say M here and read
895 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
897 config NETFILTER_XT_MATCH_CONNBYTES
898 tristate '"connbytes" per-connection counter match support'
899 depends on NF_CONNTRACK
900 depends on NETFILTER_ADVANCED
902 This option adds a `connbytes' match, which allows you to match the
903 number of bytes and/or packets for each direction within a connection.
905 If you want to compile it as a module, say M here and read
906 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
908 config NETFILTER_XT_MATCH_CONNLABEL
909 tristate '"connlabel" match support'
910 select NF_CONNTRACK_LABELS
911 depends on NF_CONNTRACK
912 depends on NETFILTER_ADVANCED
914 This match allows you to test and assign userspace-defined labels names
915 to a connection. The kernel only stores bit values - mapping
916 names to bits is done by userspace.
918 Unlike connmark, more than 32 flag bits may be assigned to a
919 connection simultaneously.
921 config NETFILTER_XT_MATCH_CONNLIMIT
922 tristate '"connlimit" match support'
923 depends on NF_CONNTRACK
924 depends on NETFILTER_ADVANCED
926 This match allows you to match against the number of parallel
927 connections to a server per client IP address (or address block).
929 config NETFILTER_XT_MATCH_CONNMARK
930 tristate '"connmark" connection mark match support'
931 depends on NF_CONNTRACK
932 depends on NETFILTER_ADVANCED
933 select NETFILTER_XT_CONNMARK
935 This is a backwards-compat option for the user's convenience
936 (e.g. when running oldconfig). It selects
937 CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
939 config NETFILTER_XT_MATCH_CONNTRACK
940 tristate '"conntrack" connection tracking match support'
941 depends on NF_CONNTRACK
942 default m if NETFILTER_ADVANCED=n
944 This is a general conntrack match module, a superset of the state match.
946 It allows matching on additional conntrack information, which is
947 useful in complex configurations, such as NAT gateways with multiple
948 internet links or tunnels.
950 To compile it as a module, choose M here. If unsure, say N.
952 config NETFILTER_XT_MATCH_CPU
953 tristate '"cpu" match support'
954 depends on NETFILTER_ADVANCED
956 CPU matching allows you to match packets based on the CPU
957 currently handling the packet.
959 To compile it as a module, choose M here. If unsure, say N.
961 config NETFILTER_XT_MATCH_DCCP
962 tristate '"dccp" protocol match support'
963 depends on NETFILTER_ADVANCED
966 With this option enabled, you will be able to use the iptables
967 `dccp' match in order to match on DCCP source/destination ports
970 If you want to compile it as a module, say M here and read
971 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
973 config NETFILTER_XT_MATCH_DEVGROUP
974 tristate '"devgroup" match support'
975 depends on NETFILTER_ADVANCED
977 This options adds a `devgroup' match, which allows to match on the
978 device group a network device is assigned to.
980 To compile it as a module, choose M here. If unsure, say N.
982 config NETFILTER_XT_MATCH_DSCP
983 tristate '"dscp" and "tos" match support'
984 depends on NETFILTER_ADVANCED
986 This option adds a `DSCP' match, which allows you to match against
987 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
989 The DSCP field can have any value between 0x0 and 0x3f inclusive.
991 It will also add a "tos" match, which allows you to match packets
992 based on the Type Of Service fields of the IPv4 packet (which share
993 the same bits as DSCP).
995 To compile it as a module, choose M here. If unsure, say N.
997 config NETFILTER_XT_MATCH_ECN
998 tristate '"ecn" match support'
999 depends on NETFILTER_ADVANCED
1001 This option adds an "ECN" match, which allows you to match against
1002 the IPv4 and TCP header ECN fields.
1004 To compile it as a module, choose M here. If unsure, say N.
1006 config NETFILTER_XT_MATCH_ESP
1007 tristate '"esp" match support'
1008 depends on NETFILTER_ADVANCED
1010 This match extension allows you to match a range of SPIs
1011 inside ESP header of IPSec packets.
1013 To compile it as a module, choose M here. If unsure, say N.
1015 config NETFILTER_XT_MATCH_HASHLIMIT
1016 tristate '"hashlimit" match support'
1017 depends on (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
1018 depends on NETFILTER_ADVANCED
1020 This option adds a `hashlimit' match.
1022 As opposed to `limit', this match dynamically creates a hash table
1023 of limit buckets, based on your selection of source/destination
1024 addresses and/or ports.
1026 It enables you to express policies like `10kpps for any given
1027 destination address' or `500pps from any given source address'
1030 config NETFILTER_XT_MATCH_HELPER
1031 tristate '"helper" match support'
1032 depends on NF_CONNTRACK
1033 depends on NETFILTER_ADVANCED
1035 Helper matching allows you to match packets in dynamic connections
1036 tracked by a conntrack-helper, ie. ip_conntrack_ftp
1038 To compile it as a module, choose M here. If unsure, say Y.
1040 config NETFILTER_XT_MATCH_HL
1041 tristate '"hl" hoplimit/TTL match support'
1042 depends on NETFILTER_ADVANCED
1044 HL matching allows you to match packets based on the hoplimit
1045 in the IPv6 header, or the time-to-live field in the IPv4
1046 header of the packet.
1048 config NETFILTER_XT_MATCH_IPCOMP
1049 tristate '"ipcomp" match support'
1050 depends on NETFILTER_ADVANCED
1052 This match extension allows you to match a range of CPIs(16 bits)
1053 inside IPComp header of IPSec packets.
1055 To compile it as a module, choose M here. If unsure, say N.
1057 config NETFILTER_XT_MATCH_IPRANGE
1058 tristate '"iprange" address range match support'
1059 depends on NETFILTER_ADVANCED
1061 This option adds a "iprange" match, which allows you to match based on
1062 an IP address range. (Normal iptables only matches on single addresses
1063 with an optional mask.)
1067 config NETFILTER_XT_MATCH_IPVS
1068 tristate '"ipvs" match support'
1070 depends on NETFILTER_ADVANCED
1071 depends on NF_CONNTRACK
1073 This option allows you to match against IPVS properties of a packet.
1077 config NETFILTER_XT_MATCH_LENGTH
1078 tristate '"length" match support'
1079 depends on NETFILTER_ADVANCED
1081 This option allows you to match the length of a packet against a
1082 specific value or range of values.
1084 To compile it as a module, choose M here. If unsure, say N.
1086 config NETFILTER_XT_MATCH_LIMIT
1087 tristate '"limit" match support'
1088 depends on NETFILTER_ADVANCED
1090 limit matching allows you to control the rate at which a rule can be
1091 matched: mainly useful in combination with the LOG target ("LOG
1092 target support", below) and to avoid some Denial of Service attacks.
1094 To compile it as a module, choose M here. If unsure, say N.
1096 config NETFILTER_XT_MATCH_MAC
1097 tristate '"mac" address match support'
1098 depends on NETFILTER_ADVANCED
1100 MAC matching allows you to match packets based on the source
1101 Ethernet address of the packet.
1103 To compile it as a module, choose M here. If unsure, say N.
1105 config NETFILTER_XT_MATCH_MARK
1106 tristate '"mark" match support'
1107 depends on NETFILTER_ADVANCED
1108 select NETFILTER_XT_MARK
1110 This is a backwards-compat option for the user's convenience
1111 (e.g. when running oldconfig). It selects
1112 CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
1114 config NETFILTER_XT_MATCH_MULTIPORT
1115 tristate '"multiport" Multiple port match support'
1116 depends on NETFILTER_ADVANCED
1118 Multiport matching allows you to match TCP or UDP packets based on
1119 a series of source or destination ports: normally a rule can only
1120 match a single range of ports.
1122 To compile it as a module, choose M here. If unsure, say N.
1124 config NETFILTER_XT_MATCH_NFACCT
1125 tristate '"nfacct" match support'
1126 depends on NETFILTER_ADVANCED
1127 select NETFILTER_NETLINK_ACCT
1129 This option allows you to use the extended accounting through
1132 To compile it as a module, choose M here. If unsure, say N.
1134 config NETFILTER_XT_MATCH_OSF
1135 tristate '"osf" Passive OS fingerprint match'
1136 depends on NETFILTER_ADVANCED && NETFILTER_NETLINK
1138 This option selects the Passive OS Fingerprinting match module
1139 that allows to passively match the remote operating system by
1140 analyzing incoming TCP SYN packets.
1142 Rules and loading software can be downloaded from
1143 http://www.ioremap.net/projects/osf
1145 To compile it as a module, choose M here. If unsure, say N.
1147 config NETFILTER_XT_MATCH_OWNER
1148 tristate '"owner" match support'
1149 depends on NETFILTER_ADVANCED
1151 Socket owner matching allows you to match locally-generated packets
1152 based on who created the socket: the user or group. It is also
1153 possible to check whether a socket actually exists.
1155 config NETFILTER_XT_MATCH_POLICY
1156 tristate 'IPsec "policy" match support'
1158 default m if NETFILTER_ADVANCED=n
1160 Policy matching allows you to match packets based on the
1161 IPsec policy that was used during decapsulation/will
1162 be used during encapsulation.
1164 To compile it as a module, choose M here. If unsure, say N.
1166 config NETFILTER_XT_MATCH_PHYSDEV
1167 tristate '"physdev" match support'
1168 depends on BRIDGE && BRIDGE_NETFILTER
1169 depends on NETFILTER_ADVANCED
1171 Physdev packet matching matches against the physical bridge ports
1172 the IP packet arrived on or will leave by.
1174 To compile it as a module, choose M here. If unsure, say N.
1176 config NETFILTER_XT_MATCH_PKTTYPE
1177 tristate '"pkttype" packet type match support'
1178 depends on NETFILTER_ADVANCED
1180 Packet type matching allows you to match a packet by
1181 its "class", eg. BROADCAST, MULTICAST, ...
1184 iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG
1186 To compile it as a module, choose M here. If unsure, say N.
1188 config NETFILTER_XT_MATCH_QUOTA
1189 tristate '"quota" match support'
1190 depends on NETFILTER_ADVANCED
1192 This option adds a `quota' match, which allows to match on a
1195 If you want to compile it as a module, say M here and read
1196 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1198 config NETFILTER_XT_MATCH_RATEEST
1199 tristate '"rateest" match support'
1200 depends on NETFILTER_ADVANCED
1201 select NETFILTER_XT_TARGET_RATEEST
1203 This option adds a `rateest' match, which allows to match on the
1204 rate estimated by the RATEEST target.
1206 To compile it as a module, choose M here. If unsure, say N.
1208 config NETFILTER_XT_MATCH_REALM
1209 tristate '"realm" match support'
1210 depends on NETFILTER_ADVANCED
1211 select IP_ROUTE_CLASSID
1213 This option adds a `realm' match, which allows you to use the realm
1214 key from the routing subsystem inside iptables.
1216 This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option
1219 If you want to compile it as a module, say M here and read
1220 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1222 config NETFILTER_XT_MATCH_RECENT
1223 tristate '"recent" match support'
1224 depends on NETFILTER_ADVANCED
1226 This match is used for creating one or many lists of recently
1227 used addresses and then matching against that/those list(s).
1229 Short options are available by using 'iptables -m recent -h'
1230 Official Website: <http://snowman.net/projects/ipt_recent/>
1232 config NETFILTER_XT_MATCH_SCTP
1233 tristate '"sctp" protocol match support'
1234 depends on NETFILTER_ADVANCED
1237 With this option enabled, you will be able to use the
1238 `sctp' match in order to match on SCTP source/destination ports
1239 and SCTP chunk types.
1241 If you want to compile it as a module, say M here and read
1242 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1244 config NETFILTER_XT_MATCH_SOCKET
1245 tristate '"socket" match support'
1246 depends on NETFILTER_XTABLES
1247 depends on NETFILTER_ADVANCED
1248 depends on !NF_CONNTRACK || NF_CONNTRACK
1249 depends on (IPV6 || IPV6=n)
1250 select NF_DEFRAG_IPV4
1251 select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES
1253 This option adds a `socket' match, which can be used to match
1254 packets for which a TCP or UDP socket lookup finds a valid socket.
1255 It can be used in combination with the MARK target and policy
1256 routing to implement full featured non-locally bound sockets.
1258 To compile it as a module, choose M here. If unsure, say N.
1260 config NETFILTER_XT_MATCH_STATE
1261 tristate '"state" match support'
1262 depends on NF_CONNTRACK
1263 default m if NETFILTER_ADVANCED=n
1265 Connection state matching allows you to match packets based on their
1266 relationship to a tracked connection (ie. previous packets). This
1267 is a powerful tool for packet classification.
1269 To compile it as a module, choose M here. If unsure, say N.
1271 config NETFILTER_XT_MATCH_STATISTIC
1272 tristate '"statistic" match support'
1273 depends on NETFILTER_ADVANCED
1275 This option adds a `statistic' match, which allows you to match
1276 on packets periodically or randomly with a given percentage.
1278 To compile it as a module, choose M here. If unsure, say N.
1280 config NETFILTER_XT_MATCH_STRING
1281 tristate '"string" match support'
1282 depends on NETFILTER_ADVANCED
1284 select TEXTSEARCH_KMP
1285 select TEXTSEARCH_BM
1286 select TEXTSEARCH_FSM
1288 This option adds a `string' match, which allows you to look for
1289 pattern matchings in packets.
1291 To compile it as a module, choose M here. If unsure, say N.
1293 config NETFILTER_XT_MATCH_TCPMSS
1294 tristate '"tcpmss" match support'
1295 depends on NETFILTER_ADVANCED
1297 This option adds a `tcpmss' match, which allows you to examine the
1298 MSS value of TCP SYN packets, which control the maximum packet size
1299 for that connection.
1301 To compile it as a module, choose M here. If unsure, say N.
1303 config NETFILTER_XT_MATCH_TIME
1304 tristate '"time" match support'
1305 depends on NETFILTER_ADVANCED
1307 This option adds a "time" match, which allows you to match based on
1308 the packet arrival time (at the machine which netfilter is running)
1309 on) or departure time/date (for locally generated packets).
1311 If you say Y here, try `iptables -m time --help` for
1314 If you want to compile it as a module, say M here.
1317 config NETFILTER_XT_MATCH_U32
1318 tristate '"u32" match support'
1319 depends on NETFILTER_ADVANCED
1321 u32 allows you to extract quantities of up to 4 bytes from a packet,
1322 AND them with specified masks, shift them by specified amounts and
1323 test whether the results are in any of a set of specified ranges.
1324 The specification of what to extract is general enough to skip over
1325 headers with lengths stored in the packet, as in IP or TCP header
1328 Details and examples are in the kernel module source.
1330 endif # NETFILTER_XTABLES
1334 source "net/netfilter/ipset/Kconfig"
1336 source "net/netfilter/ipvs/Kconfig"