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
413 # transparent proxy support
414 config NETFILTER_TPROXY
415 tristate "Transparent proxying support"
416 depends on IP_NF_MANGLE
417 depends on NETFILTER_ADVANCED
419 This option enables transparent proxying support, that is,
420 support for handling non-locally bound IPv4 TCP and UDP sockets.
421 For it to work you will have to configure certain iptables rules
422 and use policy routing. For more information on how to set it up
423 see Documentation/networking/tproxy.txt.
425 To compile it as a module, choose M here. If unsure, say N.
427 config NETFILTER_XTABLES
428 tristate "Netfilter Xtables support (required for ip_tables)"
429 default m if NETFILTER_ADVANCED=n
431 This is required if you intend to use any of ip_tables,
432 ip6_tables or arp_tables.
436 comment "Xtables combined modules"
438 config NETFILTER_XT_MARK
439 tristate 'nfmark target and match support'
440 default m if NETFILTER_ADVANCED=n
442 This option adds the "MARK" target and "mark" match.
444 Netfilter mark matching allows you to match packets based on the
445 "nfmark" value in the packet.
446 The target allows you to create rules in the "mangle" table which alter
447 the netfilter mark (nfmark) field associated with the packet.
449 Prior to routing, the nfmark can influence the routing method (see
450 "Use netfilter MARK value as routing key") and can also be used by
451 other subsystems to change their behavior.
453 config NETFILTER_XT_CONNMARK
454 tristate 'ctmark target and match support'
455 depends on NF_CONNTRACK
456 depends on NETFILTER_ADVANCED
457 select NF_CONNTRACK_MARK
459 This option adds the "CONNMARK" target and "connmark" match.
461 Netfilter allows you to store a mark value per connection (a.k.a.
462 ctmark), similarly to the packet mark (nfmark). Using this
463 target and match, you can set and match on this mark.
465 config NETFILTER_XT_SET
466 tristate 'set target and match support'
468 depends on NETFILTER_ADVANCED
470 This option adds the "SET" target and "set" match.
472 Using this target and match, you can add/delete and match
473 elements in the sets created by ipset(8).
475 To compile it as a module, choose M here. If unsure, say N.
477 # alphabetically ordered list of targets
479 comment "Xtables targets"
481 config NETFILTER_XT_TARGET_AUDIT
482 tristate "AUDIT target support"
484 depends on NETFILTER_ADVANCED
486 This option adds a 'AUDIT' target, which can be used to create
487 audit records for packets dropped/accepted.
489 To compileit as a module, choose M here. If unsure, say N.
491 config NETFILTER_XT_TARGET_CHECKSUM
492 tristate "CHECKSUM target support"
493 depends on IP_NF_MANGLE || IP6_NF_MANGLE
494 depends on NETFILTER_ADVANCED
496 This option adds a `CHECKSUM' target, which can be used in the iptables mangle
499 You can use this target to compute and fill in the checksum in
500 a packet that lacks a checksum. This is particularly useful,
501 if you need to work around old applications such as dhcp clients,
502 that do not work well with checksum offloads, but don't want to disable
503 checksum offload in your device.
505 To compile it as a module, choose M here. If unsure, say N.
507 config NETFILTER_XT_TARGET_CLASSIFY
508 tristate '"CLASSIFY" target support'
509 depends on NETFILTER_ADVANCED
511 This option adds a `CLASSIFY' target, which enables the user to set
512 the priority of a packet. Some qdiscs can use this value for
513 classification, among these are:
515 atm, cbq, dsmark, pfifo_fast, htb, prio
517 To compile it as a module, choose M here. If unsure, say N.
519 config NETFILTER_XT_TARGET_CONNMARK
520 tristate '"CONNMARK" target support'
521 depends on NF_CONNTRACK
522 depends on NETFILTER_ADVANCED
523 select NETFILTER_XT_CONNMARK
525 This is a backwards-compat option for the user's convenience
526 (e.g. when running oldconfig). It selects
527 CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
529 config NETFILTER_XT_TARGET_CONNSECMARK
530 tristate '"CONNSECMARK" target support'
531 depends on NF_CONNTRACK && NF_CONNTRACK_SECMARK
532 default m if NETFILTER_ADVANCED=n
534 The CONNSECMARK target copies security markings from packets
535 to connections, and restores security markings from connections
536 to packets (if the packets are not already marked). This would
537 normally be used in conjunction with the SECMARK target.
539 To compile it as a module, choose M here. If unsure, say N.
541 config NETFILTER_XT_TARGET_CT
542 tristate '"CT" target support'
543 depends on NF_CONNTRACK
544 depends on IP_NF_RAW || IP6_NF_RAW
545 depends on NETFILTER_ADVANCED
547 This options adds a `CT' target, which allows to specify initial
548 connection tracking parameters like events to be delivered and
549 the helper to be used.
551 To compile it as a module, choose M here. If unsure, say N.
553 config NETFILTER_XT_TARGET_DSCP
554 tristate '"DSCP" and "TOS" target support'
555 depends on IP_NF_MANGLE || IP6_NF_MANGLE
556 depends on NETFILTER_ADVANCED
558 This option adds a `DSCP' target, which allows you to manipulate
559 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
561 The DSCP field can have any value between 0x0 and 0x3f inclusive.
563 It also adds the "TOS" target, which allows you to create rules in
564 the "mangle" table which alter the Type Of Service field of an IPv4
565 or the Priority field of an IPv6 packet, prior to routing.
567 To compile it as a module, choose M here. If unsure, say N.
569 config NETFILTER_XT_TARGET_HL
570 tristate '"HL" hoplimit target support'
571 depends on IP_NF_MANGLE || IP6_NF_MANGLE
572 depends on NETFILTER_ADVANCED
574 This option adds the "HL" (for IPv6) and "TTL" (for IPv4)
575 targets, which enable the user to change the
576 hoplimit/time-to-live value of the IP header.
578 While it is safe to decrement the hoplimit/TTL value, the
579 modules also allow to increment and set the hoplimit value of
580 the header to arbitrary values. This is EXTREMELY DANGEROUS
581 since you can easily create immortal packets that loop
582 forever on the network.
584 config NETFILTER_XT_TARGET_HMARK
585 tristate '"HMARK" target support'
586 depends on (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
587 depends on NETFILTER_ADVANCED
589 This option adds the "HMARK" target.
591 The target allows you to create rules in the "raw" and "mangle" tables
592 which set the skbuff mark by means of hash calculation within a given
593 range. The nfmark can influence the routing method (see "Use netfilter
594 MARK value as routing key") and can also be used by other subsystems to
595 change their behaviour.
597 To compile it as a module, choose M here. If unsure, say N.
599 config NETFILTER_XT_TARGET_IDLETIMER
600 tristate "IDLETIMER target support"
601 depends on NETFILTER_ADVANCED
604 This option adds the `IDLETIMER' target. Each matching packet
605 resets the timer associated with label specified when the rule is
606 added. When the timer expires, it triggers a sysfs notification.
607 The remaining time for expiration can be read via sysfs.
609 To compile it as a module, choose M here. If unsure, say N.
611 config NETFILTER_XT_TARGET_LED
612 tristate '"LED" target support'
613 depends on LEDS_CLASS && LEDS_TRIGGERS
614 depends on NETFILTER_ADVANCED
616 This option adds a `LED' target, which allows you to blink LEDs in
617 response to particular packets passing through your machine.
619 This can be used to turn a spare LED into a network activity LED,
620 which only flashes in response to FTP transfers, for example. Or
621 you could have an LED which lights up for a minute or two every time
622 somebody connects to your machine via SSH.
624 You will need support for the "led" class to make this work.
626 To create an LED trigger for incoming SSH traffic:
627 iptables -A INPUT -p tcp --dport 22 -j LED --led-trigger-id ssh --led-delay 1000
629 Then attach the new trigger to an LED on your system:
630 echo netfilter-ssh > /sys/class/leds/<ledname>/trigger
632 For more information on the LEDs available on your system, see
633 Documentation/leds/leds-class.txt
635 config NETFILTER_XT_TARGET_LOG
636 tristate "LOG target support"
637 default m if NETFILTER_ADVANCED=n
639 This option adds a `LOG' target, which allows you to create rules in
640 any iptables table which records the packet header to the syslog.
642 To compile it as a module, choose M here. If unsure, say N.
644 config NETFILTER_XT_TARGET_MARK
645 tristate '"MARK" target support'
646 depends on NETFILTER_ADVANCED
647 select NETFILTER_XT_MARK
649 This is a backwards-compat option for the user's convenience
650 (e.g. when running oldconfig). It selects
651 CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
653 config NETFILTER_XT_TARGET_NETMAP
654 tristate '"NETMAP" target support'
657 NETMAP is an implementation of static 1:1 NAT mapping of network
658 addresses. It maps the network address part, while keeping the host
661 To compile it as a module, choose M here. If unsure, say N.
663 config NETFILTER_XT_TARGET_NFLOG
664 tristate '"NFLOG" target support'
665 default m if NETFILTER_ADVANCED=n
666 select NETFILTER_NETLINK_LOG
668 This option enables the NFLOG target, which allows to LOG
669 messages through nfnetlink_log.
671 To compile it as a module, choose M here. If unsure, say N.
673 config NETFILTER_XT_TARGET_NFQUEUE
674 tristate '"NFQUEUE" target Support'
675 depends on NETFILTER_ADVANCED
676 select NETFILTER_NETLINK_QUEUE
678 This target replaced the old obsolete QUEUE target.
680 As opposed to QUEUE, it supports 65535 different queues,
683 To compile it as a module, choose M here. If unsure, say N.
685 config NETFILTER_XT_TARGET_NOTRACK
686 tristate '"NOTRACK" target support (DEPRECATED)'
687 depends on NF_CONNTRACK
688 depends on IP_NF_RAW || IP6_NF_RAW
689 depends on NETFILTER_ADVANCED
690 select NETFILTER_XT_TARGET_CT
692 config NETFILTER_XT_TARGET_RATEEST
693 tristate '"RATEEST" target support'
694 depends on NETFILTER_ADVANCED
696 This option adds a `RATEEST' target, which allows to measure
697 rates similar to TC estimators. The `rateest' match can be
698 used to match on the measured rates.
700 To compile it as a module, choose M here. If unsure, say N.
702 config NETFILTER_XT_TARGET_REDIRECT
703 tristate "REDIRECT target support"
706 REDIRECT is a special case of NAT: all incoming connections are
707 mapped onto the incoming interface's address, causing the packets to
708 come to the local machine instead of passing through. This is
709 useful for transparent proxies.
711 To compile it as a module, choose M here. If unsure, say N.
713 config NETFILTER_XT_TARGET_TEE
714 tristate '"TEE" - packet cloning to alternate destination'
715 depends on NETFILTER_ADVANCED
716 depends on (IPV6 || IPV6=n)
717 depends on !NF_CONNTRACK || NF_CONNTRACK
719 This option adds a "TEE" target with which a packet can be cloned and
720 this clone be rerouted to another nexthop.
722 config NETFILTER_XT_TARGET_TPROXY
723 tristate '"TPROXY" target support'
724 depends on NETFILTER_TPROXY
725 depends on NETFILTER_XTABLES
726 depends on NETFILTER_ADVANCED
727 select NF_DEFRAG_IPV4
728 select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES
730 This option adds a `TPROXY' target, which is somewhat similar to
731 REDIRECT. It can only be used in the mangle table and is useful
732 to redirect traffic to a transparent proxy. It does _not_ depend
733 on Netfilter connection tracking and NAT, unlike REDIRECT.
735 To compile it as a module, choose M here. If unsure, say N.
737 config NETFILTER_XT_TARGET_TRACE
738 tristate '"TRACE" target support'
739 depends on IP_NF_RAW || IP6_NF_RAW
740 depends on NETFILTER_ADVANCED
742 The TRACE target allows you to mark packets so that the kernel
743 will log every rule which match the packets as those traverse
744 the tables, chains, rules.
746 If you want to compile it as a module, say M here and read
747 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
749 config NETFILTER_XT_TARGET_SECMARK
750 tristate '"SECMARK" target support'
751 depends on NETWORK_SECMARK
752 default m if NETFILTER_ADVANCED=n
754 The SECMARK target allows security marking of network
755 packets, for use with security subsystems.
757 To compile it as a module, choose M here. If unsure, say N.
759 config NETFILTER_XT_TARGET_TCPMSS
760 tristate '"TCPMSS" target support'
761 depends on (IPV6 || IPV6=n)
762 default m if NETFILTER_ADVANCED=n
764 This option adds a `TCPMSS' target, which allows you to alter the
765 MSS value of TCP SYN packets, to control the maximum size for that
766 connection (usually limiting it to your outgoing interface's MTU
769 This is used to overcome criminally braindead ISPs or servers which
770 block ICMP Fragmentation Needed packets. The symptoms of this
771 problem are that everything works fine from your Linux
772 firewall/router, but machines behind it can never exchange large
774 1) Web browsers connect, then hang with no data received.
775 2) Small mail works fine, but large emails hang.
776 3) ssh works fine, but scp hangs after initial handshaking.
778 Workaround: activate this option and add a rule to your firewall
781 iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
782 -j TCPMSS --clamp-mss-to-pmtu
784 To compile it as a module, choose M here. If unsure, say N.
786 config NETFILTER_XT_TARGET_TCPOPTSTRIP
787 tristate '"TCPOPTSTRIP" target support'
788 depends on IP_NF_MANGLE || IP6_NF_MANGLE
789 depends on NETFILTER_ADVANCED
791 This option adds a "TCPOPTSTRIP" target, which allows you to strip
792 TCP options from TCP packets.
794 # alphabetically ordered list of matches
796 comment "Xtables matches"
798 config NETFILTER_XT_MATCH_ADDRTYPE
799 tristate '"addrtype" address type match support'
800 depends on NETFILTER_ADVANCED
802 This option allows you to match what routing thinks of an address,
803 eg. UNICAST, LOCAL, BROADCAST, ...
805 If you want to compile it as a module, say M here and read
806 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
808 config NETFILTER_XT_MATCH_BPF
809 tristate '"bpf" match support'
810 depends on NETFILTER_ADVANCED
812 BPF matching applies a linux socket filter to each packet and
813 accepts those for which the filter returns non-zero.
815 To compile it as a module, choose M here. If unsure, say N.
817 config NETFILTER_XT_MATCH_CGROUP
818 tristate '"control group" match support'
819 depends on NETFILTER_ADVANCED
821 select CGROUP_NET_CLASSID
823 Socket/process control group matching allows you to match locally
824 generated packets based on which net_cls control group processes
827 config NETFILTER_XT_MATCH_CLUSTER
828 tristate '"cluster" match support'
829 depends on NF_CONNTRACK
830 depends on NETFILTER_ADVANCED
832 This option allows you to build work-load-sharing clusters of
833 network servers/stateful firewalls without having a dedicated
834 load-balancing router/server/switch. Basically, this match returns
835 true when the packet must be handled by this cluster node. Thus,
836 all nodes see all packets and this match decides which node handles
837 what packets. The work-load sharing algorithm is based on source
840 If you say Y or M here, try `iptables -m cluster --help` for
843 config NETFILTER_XT_MATCH_COMMENT
844 tristate '"comment" match support'
845 depends on NETFILTER_ADVANCED
847 This option adds a `comment' dummy-match, which allows you to put
848 comments in your iptables ruleset.
850 If you want to compile it as a module, say M here and read
851 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
853 config NETFILTER_XT_MATCH_CONNBYTES
854 tristate '"connbytes" per-connection counter match support'
855 depends on NF_CONNTRACK
856 depends on NETFILTER_ADVANCED
858 This option adds a `connbytes' match, which allows you to match the
859 number of bytes and/or packets for each direction within a connection.
861 If you want to compile it as a module, say M here and read
862 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
864 config NETFILTER_XT_MATCH_CONNLABEL
865 tristate '"connlabel" match support'
866 select NF_CONNTRACK_LABELS
867 depends on NF_CONNTRACK
868 depends on NETFILTER_ADVANCED
870 This match allows you to test and assign userspace-defined labels names
871 to a connection. The kernel only stores bit values - mapping
872 names to bits is done by userspace.
874 Unlike connmark, more than 32 flag bits may be assigned to a
875 connection simultaneously.
877 config NETFILTER_XT_MATCH_CONNLIMIT
878 tristate '"connlimit" match support"'
879 depends on NF_CONNTRACK
880 depends on NETFILTER_ADVANCED
882 This match allows you to match against the number of parallel
883 connections to a server per client IP address (or address block).
885 config NETFILTER_XT_MATCH_CONNMARK
886 tristate '"connmark" connection mark match support'
887 depends on NF_CONNTRACK
888 depends on NETFILTER_ADVANCED
889 select NETFILTER_XT_CONNMARK
891 This is a backwards-compat option for the user's convenience
892 (e.g. when running oldconfig). It selects
893 CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
895 config NETFILTER_XT_MATCH_CONNTRACK
896 tristate '"conntrack" connection tracking match support'
897 depends on NF_CONNTRACK
898 default m if NETFILTER_ADVANCED=n
900 This is a general conntrack match module, a superset of the state match.
902 It allows matching on additional conntrack information, which is
903 useful in complex configurations, such as NAT gateways with multiple
904 internet links or tunnels.
906 To compile it as a module, choose M here. If unsure, say N.
908 config NETFILTER_XT_MATCH_CPU
909 tristate '"cpu" match support'
910 depends on NETFILTER_ADVANCED
912 CPU matching allows you to match packets based on the CPU
913 currently handling the packet.
915 To compile it as a module, choose M here. If unsure, say N.
917 config NETFILTER_XT_MATCH_DCCP
918 tristate '"dccp" protocol match support'
919 depends on NETFILTER_ADVANCED
922 With this option enabled, you will be able to use the iptables
923 `dccp' match in order to match on DCCP source/destination ports
926 If you want to compile it as a module, say M here and read
927 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
929 config NETFILTER_XT_MATCH_DEVGROUP
930 tristate '"devgroup" match support'
931 depends on NETFILTER_ADVANCED
933 This options adds a `devgroup' match, which allows to match on the
934 device group a network device is assigned to.
936 To compile it as a module, choose M here. If unsure, say N.
938 config NETFILTER_XT_MATCH_DSCP
939 tristate '"dscp" and "tos" match support'
940 depends on NETFILTER_ADVANCED
942 This option adds a `DSCP' match, which allows you to match against
943 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
945 The DSCP field can have any value between 0x0 and 0x3f inclusive.
947 It will also add a "tos" match, which allows you to match packets
948 based on the Type Of Service fields of the IPv4 packet (which share
949 the same bits as DSCP).
951 To compile it as a module, choose M here. If unsure, say N.
953 config NETFILTER_XT_MATCH_ECN
954 tristate '"ecn" match support'
955 depends on NETFILTER_ADVANCED
957 This option adds an "ECN" match, which allows you to match against
958 the IPv4 and TCP header ECN fields.
960 To compile it as a module, choose M here. If unsure, say N.
962 config NETFILTER_XT_MATCH_ESP
963 tristate '"esp" match support'
964 depends on NETFILTER_ADVANCED
966 This match extension allows you to match a range of SPIs
967 inside ESP header of IPSec packets.
969 To compile it as a module, choose M here. If unsure, say N.
971 config NETFILTER_XT_MATCH_HASHLIMIT
972 tristate '"hashlimit" match support'
973 depends on (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
974 depends on NETFILTER_ADVANCED
976 This option adds a `hashlimit' match.
978 As opposed to `limit', this match dynamically creates a hash table
979 of limit buckets, based on your selection of source/destination
980 addresses and/or ports.
982 It enables you to express policies like `10kpps for any given
983 destination address' or `500pps from any given source address'
986 config NETFILTER_XT_MATCH_HELPER
987 tristate '"helper" match support'
988 depends on NF_CONNTRACK
989 depends on NETFILTER_ADVANCED
991 Helper matching allows you to match packets in dynamic connections
992 tracked by a conntrack-helper, ie. ip_conntrack_ftp
994 To compile it as a module, choose M here. If unsure, say Y.
996 config NETFILTER_XT_MATCH_HL
997 tristate '"hl" hoplimit/TTL match support'
998 depends on NETFILTER_ADVANCED
1000 HL matching allows you to match packets based on the hoplimit
1001 in the IPv6 header, or the time-to-live field in the IPv4
1002 header of the packet.
1004 config NETFILTER_XT_MATCH_IPRANGE
1005 tristate '"iprange" address range match support'
1006 depends on NETFILTER_ADVANCED
1008 This option adds a "iprange" match, which allows you to match based on
1009 an IP address range. (Normal iptables only matches on single addresses
1010 with an optional mask.)
1014 config NETFILTER_XT_MATCH_IPVS
1015 tristate '"ipvs" match support'
1017 depends on NETFILTER_ADVANCED
1018 depends on NF_CONNTRACK
1020 This option allows you to match against IPVS properties of a packet.
1024 config NETFILTER_XT_MATCH_LENGTH
1025 tristate '"length" match support'
1026 depends on NETFILTER_ADVANCED
1028 This option allows you to match the length of a packet against a
1029 specific value or range of values.
1031 To compile it as a module, choose M here. If unsure, say N.
1033 config NETFILTER_XT_MATCH_LIMIT
1034 tristate '"limit" match support'
1035 depends on NETFILTER_ADVANCED
1037 limit matching allows you to control the rate at which a rule can be
1038 matched: mainly useful in combination with the LOG target ("LOG
1039 target support", below) and to avoid some Denial of Service attacks.
1041 To compile it as a module, choose M here. If unsure, say N.
1043 config NETFILTER_XT_MATCH_MAC
1044 tristate '"mac" address match support'
1045 depends on NETFILTER_ADVANCED
1047 MAC matching allows you to match packets based on the source
1048 Ethernet address of the packet.
1050 To compile it as a module, choose M here. If unsure, say N.
1052 config NETFILTER_XT_MATCH_MARK
1053 tristate '"mark" match support'
1054 depends on NETFILTER_ADVANCED
1055 select NETFILTER_XT_MARK
1057 This is a backwards-compat option for the user's convenience
1058 (e.g. when running oldconfig). It selects
1059 CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
1061 config NETFILTER_XT_MATCH_MULTIPORT
1062 tristate '"multiport" Multiple port match support'
1063 depends on NETFILTER_ADVANCED
1065 Multiport matching allows you to match TCP or UDP packets based on
1066 a series of source or destination ports: normally a rule can only
1067 match a single range of ports.
1069 To compile it as a module, choose M here. If unsure, say N.
1071 config NETFILTER_XT_MATCH_NFACCT
1072 tristate '"nfacct" match support'
1073 depends on NETFILTER_ADVANCED
1074 select NETFILTER_NETLINK_ACCT
1076 This option allows you to use the extended accounting through
1079 To compile it as a module, choose M here. If unsure, say N.
1081 config NETFILTER_XT_MATCH_OSF
1082 tristate '"osf" Passive OS fingerprint match'
1083 depends on NETFILTER_ADVANCED && NETFILTER_NETLINK
1085 This option selects the Passive OS Fingerprinting match module
1086 that allows to passively match the remote operating system by
1087 analyzing incoming TCP SYN packets.
1089 Rules and loading software can be downloaded from
1090 http://www.ioremap.net/projects/osf
1092 To compile it as a module, choose M here. If unsure, say N.
1094 config NETFILTER_XT_MATCH_OWNER
1095 tristate '"owner" match support'
1096 depends on NETFILTER_ADVANCED
1098 Socket owner matching allows you to match locally-generated packets
1099 based on who created the socket: the user or group. It is also
1100 possible to check whether a socket actually exists.
1102 Conflicts with '"quota, tag, uid" match'
1104 config NETFILTER_XT_MATCH_POLICY
1105 tristate 'IPsec "policy" match support'
1107 default m if NETFILTER_ADVANCED=n
1109 Policy matching allows you to match packets based on the
1110 IPsec policy that was used during decapsulation/will
1111 be used during encapsulation.
1113 To compile it as a module, choose M here. If unsure, say N.
1115 config NETFILTER_XT_MATCH_PHYSDEV
1116 tristate '"physdev" match support'
1117 depends on BRIDGE && BRIDGE_NETFILTER
1118 depends on NETFILTER_ADVANCED
1120 Physdev packet matching matches against the physical bridge ports
1121 the IP packet arrived on or will leave by.
1123 To compile it as a module, choose M here. If unsure, say N.
1125 config NETFILTER_XT_MATCH_PKTTYPE
1126 tristate '"pkttype" packet type match support'
1127 depends on NETFILTER_ADVANCED
1129 Packet type matching allows you to match a packet by
1130 its "class", eg. BROADCAST, MULTICAST, ...
1133 iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG
1135 To compile it as a module, choose M here. If unsure, say N.
1137 config NETFILTER_XT_MATCH_QTAGUID
1138 bool '"quota, tag, owner" match and stats support'
1139 depends on NETFILTER_XT_MATCH_SOCKET
1140 depends on NETFILTER_XT_MATCH_OWNER=n
1142 This option replaces the `owner' match. In addition to matching
1143 on uid, it keeps stats based on a tag assigned to a socket.
1144 The full tag is comprised of a UID and an accounting tag.
1145 The tags are assignable to sockets from user space (e.g. a download
1146 manager can assign the socket to another UID for accounting).
1147 Stats and control are done via /proc/net/xt_qtaguid/.
1148 It replaces owner as it takes the same arguments, but should
1149 really be recognized by the iptables tool.
1153 config NETFILTER_XT_MATCH_QUOTA
1154 tristate '"quota" match support'
1155 depends on NETFILTER_ADVANCED
1157 This option adds a `quota' match, which allows to match on a
1160 If you want to compile it as a module, say M here and read
1161 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1163 config NETFILTER_XT_MATCH_QUOTA2
1164 tristate '"quota2" match support'
1165 depends on NETFILTER_ADVANCED
1167 This option adds a `quota2' match, which allows to match on a
1168 byte counter correctly and not per CPU.
1169 It allows naming the quotas.
1170 This is based on http://xtables-addons.git.sourceforge.net
1172 If you want to compile it as a module, say M here and read
1173 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1175 config NETFILTER_XT_MATCH_QUOTA2_LOG
1176 bool '"quota2" Netfilter LOG support'
1177 depends on NETFILTER_XT_MATCH_QUOTA2
1178 depends on IP_NF_TARGET_ULOG=n # not yes, not module, just no
1181 This option allows `quota2' to log ONCE when a quota limit
1182 is passed. It logs via NETLINK using the NETLINK_NFLOG family.
1183 It logs similarly to how ipt_ULOG would without data.
1187 config NETFILTER_XT_MATCH_RATEEST
1188 tristate '"rateest" match support'
1189 depends on NETFILTER_ADVANCED
1190 select NETFILTER_XT_TARGET_RATEEST
1192 This option adds a `rateest' match, which allows to match on the
1193 rate estimated by the RATEEST target.
1195 To compile it as a module, choose M here. If unsure, say N.
1197 config NETFILTER_XT_MATCH_REALM
1198 tristate '"realm" match support'
1199 depends on NETFILTER_ADVANCED
1200 select IP_ROUTE_CLASSID
1202 This option adds a `realm' match, which allows you to use the realm
1203 key from the routing subsystem inside iptables.
1205 This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option
1208 If you want to compile it as a module, say M here and read
1209 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1211 config NETFILTER_XT_MATCH_RECENT
1212 tristate '"recent" match support'
1213 depends on NETFILTER_ADVANCED
1215 This match is used for creating one or many lists of recently
1216 used addresses and then matching against that/those list(s).
1218 Short options are available by using 'iptables -m recent -h'
1219 Official Website: <http://snowman.net/projects/ipt_recent/>
1221 config NETFILTER_XT_MATCH_SCTP
1222 tristate '"sctp" protocol match support'
1223 depends on NETFILTER_ADVANCED
1226 With this option enabled, you will be able to use the
1227 `sctp' match in order to match on SCTP source/destination ports
1228 and SCTP chunk types.
1230 If you want to compile it as a module, say M here and read
1231 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1233 config NETFILTER_XT_MATCH_SOCKET
1234 tristate '"socket" match support'
1235 depends on NETFILTER_TPROXY
1236 depends on NETFILTER_XTABLES
1237 depends on NETFILTER_ADVANCED
1238 depends on !NF_CONNTRACK || NF_CONNTRACK
1239 select NF_DEFRAG_IPV4
1240 select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES
1242 This option adds a `socket' match, which can be used to match
1243 packets for which a TCP or UDP socket lookup finds a valid socket.
1244 It can be used in combination with the MARK target and policy
1245 routing to implement full featured non-locally bound sockets.
1247 To compile it as a module, choose M here. If unsure, say N.
1249 config NETFILTER_XT_MATCH_STATE
1250 tristate '"state" match support'
1251 depends on NF_CONNTRACK
1252 default m if NETFILTER_ADVANCED=n
1254 Connection state matching allows you to match packets based on their
1255 relationship to a tracked connection (ie. previous packets). This
1256 is a powerful tool for packet classification.
1258 To compile it as a module, choose M here. If unsure, say N.
1260 config NETFILTER_XT_MATCH_STATISTIC
1261 tristate '"statistic" match support'
1262 depends on NETFILTER_ADVANCED
1264 This option adds a `statistic' match, which allows you to match
1265 on packets periodically or randomly with a given percentage.
1267 To compile it as a module, choose M here. If unsure, say N.
1269 config NETFILTER_XT_MATCH_STRING
1270 tristate '"string" match support'
1271 depends on NETFILTER_ADVANCED
1273 select TEXTSEARCH_KMP
1274 select TEXTSEARCH_BM
1275 select TEXTSEARCH_FSM
1277 This option adds a `string' match, which allows you to look for
1278 pattern matchings in packets.
1280 To compile it as a module, choose M here. If unsure, say N.
1282 config NETFILTER_XT_MATCH_TCPMSS
1283 tristate '"tcpmss" match support'
1284 depends on NETFILTER_ADVANCED
1286 This option adds a `tcpmss' match, which allows you to examine the
1287 MSS value of TCP SYN packets, which control the maximum packet size
1288 for that connection.
1290 To compile it as a module, choose M here. If unsure, say N.
1292 config NETFILTER_XT_MATCH_TIME
1293 tristate '"time" match support'
1294 depends on NETFILTER_ADVANCED
1296 This option adds a "time" match, which allows you to match based on
1297 the packet arrival time (at the machine which netfilter is running)
1298 on) or departure time/date (for locally generated packets).
1300 If you say Y here, try `iptables -m time --help` for
1303 If you want to compile it as a module, say M here.
1306 config NETFILTER_XT_MATCH_U32
1307 tristate '"u32" match support'
1308 depends on NETFILTER_ADVANCED
1310 u32 allows you to extract quantities of up to 4 bytes from a packet,
1311 AND them with specified masks, shift them by specified amounts and
1312 test whether the results are in any of a set of specified ranges.
1313 The specification of what to extract is general enough to skip over
1314 headers with lengths stored in the packet, as in IP or TCP header
1317 Details and examples are in the kernel module source.
1319 endif # NETFILTER_XTABLES
1323 source "net/netfilter/ipset/Kconfig"
1325 source "net/netfilter/ipvs/Kconfig"