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 (EXPERIMENTAL)'
135 depends on EXPERIMENTAL
136 depends on NETFILTER_ADVANCED
139 With this option enabled, the layer 3 independent connection
140 tracking code will be able to do state tracking on DCCP connections.
144 config NF_CT_PROTO_GRE
147 config NF_CT_PROTO_SCTP
148 tristate 'SCTP protocol connection tracking support (EXPERIMENTAL)'
149 depends on EXPERIMENTAL
150 depends on NETFILTER_ADVANCED
153 With this option enabled, the layer 3 independent connection
154 tracking code will be able to do state tracking on SCTP connections.
156 If you want to compile it as a module, say M here and read
157 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
159 config NF_CT_PROTO_UDPLITE
160 tristate 'UDP-Lite protocol connection tracking support'
161 depends on NETFILTER_ADVANCED
163 With this option enabled, the layer 3 independent connection
164 tracking code will be able to do state tracking on UDP-Lite
167 To compile it as a module, choose M here. If unsure, say N.
169 config NF_CONNTRACK_AMANDA
170 tristate "Amanda backup protocol support"
171 depends on NETFILTER_ADVANCED
173 select TEXTSEARCH_KMP
175 If you are running the Amanda backup package <http://www.amanda.org/>
176 on this machine or machines that will be MASQUERADED through this
177 machine, then you may want to enable this feature. This allows the
178 connection tracking and natting code to allow the sub-channels that
179 Amanda requires for communication of the backup data, messages and
182 To compile it as a module, choose M here. If unsure, say N.
184 config NF_CONNTRACK_FTP
185 tristate "FTP protocol support"
186 default m if NETFILTER_ADVANCED=n
188 Tracking FTP connections is problematic: special helpers are
189 required for tracking them, and doing masquerading and other forms
190 of Network Address Translation on them.
192 This is FTP support on Layer 3 independent connection tracking.
193 Layer 3 independent connection tracking is experimental scheme
194 which generalize ip_conntrack to support other layer 3 protocols.
196 To compile it as a module, choose M here. If unsure, say N.
198 config NF_CONNTRACK_H323
199 tristate "H.323 protocol support"
200 depends on (IPV6 || IPV6=n)
201 depends on NETFILTER_ADVANCED
203 H.323 is a VoIP signalling protocol from ITU-T. As one of the most
204 important VoIP protocols, it is widely used by voice hardware and
205 software including voice gateways, IP phones, Netmeeting, OpenPhone,
208 With this module you can support H.323 on a connection tracking/NAT
211 This module supports RAS, Fast Start, H.245 Tunnelling, Call
212 Forwarding, RTP/RTCP and T.120 based audio, video, fax, chat,
213 whiteboard, file transfer, etc. For more information, please
214 visit http://nath323.sourceforge.net/.
216 To compile it as a module, choose M here. If unsure, say N.
218 config NF_CONNTRACK_IRC
219 tristate "IRC protocol support"
220 default m if NETFILTER_ADVANCED=n
222 There is a commonly-used extension to IRC called
223 Direct Client-to-Client Protocol (DCC). This enables users to send
224 files to each other, and also chat to each other without the need
225 of a server. DCC Sending is used anywhere you send files over IRC,
226 and DCC Chat is most commonly used by Eggdrop bots. If you are
227 using NAT, this extension will enable you to send files and initiate
228 chats. Note that you do NOT need this extension to get files or
229 have others initiate chats, or everything else in IRC.
231 To compile it as a module, choose M here. If unsure, say N.
233 config NF_CONNTRACK_BROADCAST
236 config NF_CONNTRACK_NETBIOS_NS
237 tristate "NetBIOS name service protocol support"
238 select NF_CONNTRACK_BROADCAST
240 NetBIOS name service requests are sent as broadcast messages from an
241 unprivileged port and responded to with unicast messages to the
242 same port. This make them hard to firewall properly because connection
243 tracking doesn't deal with broadcasts. This helper tracks locally
244 originating NetBIOS name service requests and the corresponding
245 responses. It relies on correct IP address configuration, specifically
246 netmask and broadcast address. When properly configured, the output
247 of "ip address show" should look similar to this:
249 $ ip -4 address show eth0
250 4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
251 inet 172.16.2.252/24 brd 172.16.2.255 scope global eth0
253 To compile it as a module, choose M here. If unsure, say N.
255 config NF_CONNTRACK_SNMP
256 tristate "SNMP service protocol support"
257 depends on NETFILTER_ADVANCED
258 select NF_CONNTRACK_BROADCAST
260 SNMP service requests are sent as broadcast messages from an
261 unprivileged port and responded to with unicast messages to the
262 same port. This make them hard to firewall properly because connection
263 tracking doesn't deal with broadcasts. This helper tracks locally
264 originating SNMP service requests and the corresponding
265 responses. It relies on correct IP address configuration, specifically
266 netmask and broadcast address.
268 To compile it as a module, choose M here. If unsure, say N.
270 config NF_CONNTRACK_PPTP
271 tristate "PPtP protocol support"
272 depends on NETFILTER_ADVANCED
273 select NF_CT_PROTO_GRE
275 This module adds support for PPTP (Point to Point Tunnelling
276 Protocol, RFC2637) connection tracking and NAT.
278 If you are running PPTP sessions over a stateful firewall or NAT
279 box, you may want to enable this feature.
281 Please note that not all PPTP modes of operation are supported yet.
282 Specifically these limitations exist:
283 - Blindly assumes that control connections are always established
284 in PNS->PAC direction. This is a violation of RFC2637.
285 - Only supports a single call within each session
287 To compile it as a module, choose M here. If unsure, say N.
289 config NF_CONNTRACK_SANE
290 tristate "SANE protocol support (EXPERIMENTAL)"
291 depends on EXPERIMENTAL
292 depends on NETFILTER_ADVANCED
294 SANE is a protocol for remote access to scanners as implemented
295 by the 'saned' daemon. Like FTP, it uses separate control and
298 With this module you can support SANE on a connection tracking
301 To compile it as a module, choose M here. If unsure, say N.
303 config NF_CONNTRACK_SIP
304 tristate "SIP protocol support"
305 default m if NETFILTER_ADVANCED=n
307 SIP is an application-layer control protocol that can establish,
308 modify, and terminate multimedia sessions (conferences) such as
309 Internet telephony calls. With the ip_conntrack_sip and
310 the nf_nat_sip modules you can support the protocol on a connection
311 tracking/NATing firewall.
313 To compile it as a module, choose M here. If unsure, say N.
315 config NF_CONNTRACK_TFTP
316 tristate "TFTP protocol support"
317 depends on NETFILTER_ADVANCED
319 TFTP connection tracking helper, this is required depending
320 on how restrictive your ruleset is.
321 If you are using a tftp client behind -j SNAT or -j MASQUERADING
324 To compile it as a module, choose M here. If unsure, say N.
327 tristate 'Connection tracking netlink interface'
328 select NETFILTER_NETLINK
329 default m if NETFILTER_ADVANCED=n
331 This option enables support for a netlink-based userspace interface
333 config NF_CT_NETLINK_TIMEOUT
334 tristate 'Connection tracking timeout tuning via Netlink'
335 select NETFILTER_NETLINK
336 depends on NETFILTER_ADVANCED
338 This option enables support for connection tracking timeout
339 fine-grain tuning. This allows you to attach specific timeout
340 policies to flows, instead of using the global timeout policy.
344 config NF_CT_NETLINK_HELPER
345 tristate 'Connection tracking helpers in user-space via Netlink'
346 select NETFILTER_NETLINK
347 depends on NF_CT_NETLINK
348 depends on NETFILTER_NETLINK_QUEUE
349 depends on NETFILTER_NETLINK_QUEUE_CT
350 depends on NETFILTER_ADVANCED
352 This option enables the user-space connection tracking helpers
357 config NETFILTER_NETLINK_QUEUE_CT
358 bool "NFQUEUE integration with Connection Tracking"
360 depends on NETFILTER_NETLINK_QUEUE
362 If this option is enabled, NFQUEUE can include Connection Tracking
363 information together with the packet is the enqueued via NFNETLINK.
373 config NF_NAT_PROTO_DCCP
375 depends on NF_NAT && NF_CT_PROTO_DCCP
376 default NF_NAT && NF_CT_PROTO_DCCP
378 config NF_NAT_PROTO_UDPLITE
380 depends on NF_NAT && NF_CT_PROTO_UDPLITE
381 default NF_NAT && NF_CT_PROTO_UDPLITE
383 config NF_NAT_PROTO_SCTP
385 default NF_NAT && NF_CT_PROTO_SCTP
386 depends on NF_NAT && NF_CT_PROTO_SCTP
391 depends on NF_CONNTRACK && NF_NAT
392 default NF_NAT && NF_CONNTRACK_AMANDA
396 depends on NF_CONNTRACK && NF_NAT
397 default NF_NAT && NF_CONNTRACK_FTP
401 depends on NF_CONNTRACK && NF_NAT
402 default NF_NAT && NF_CONNTRACK_IRC
406 depends on NF_CONNTRACK && NF_NAT
407 default NF_NAT && NF_CONNTRACK_SIP
411 depends on NF_CONNTRACK && NF_NAT
412 default NF_NAT && NF_CONNTRACK_TFTP
416 # transparent proxy support
417 config NETFILTER_TPROXY
418 tristate "Transparent proxying support (EXPERIMENTAL)"
419 depends on EXPERIMENTAL
420 depends on IP_NF_MANGLE
421 depends on NETFILTER_ADVANCED
423 This option enables transparent proxying support, that is,
424 support for handling non-locally bound IPv4 TCP and UDP sockets.
425 For it to work you will have to configure certain iptables rules
426 and use policy routing. For more information on how to set it up
427 see Documentation/networking/tproxy.txt.
429 To compile it as a module, choose M here. If unsure, say N.
431 config NETFILTER_XTABLES
432 tristate "Netfilter Xtables support (required for ip_tables)"
433 default m if NETFILTER_ADVANCED=n
435 This is required if you intend to use any of ip_tables,
436 ip6_tables or arp_tables.
440 comment "Xtables combined modules"
442 config NETFILTER_XT_MARK
443 tristate 'nfmark target and match support'
444 default m if NETFILTER_ADVANCED=n
446 This option adds the "MARK" target and "mark" match.
448 Netfilter mark matching allows you to match packets based on the
449 "nfmark" value in the packet.
450 The target allows you to create rules in the "mangle" table which alter
451 the netfilter mark (nfmark) field associated with the packet.
453 Prior to routing, the nfmark can influence the routing method (see
454 "Use netfilter MARK value as routing key") and can also be used by
455 other subsystems to change their behavior.
457 config NETFILTER_XT_CONNMARK
458 tristate 'ctmark target and match support'
459 depends on NF_CONNTRACK
460 depends on NETFILTER_ADVANCED
461 select NF_CONNTRACK_MARK
463 This option adds the "CONNMARK" target and "connmark" match.
465 Netfilter allows you to store a mark value per connection (a.k.a.
466 ctmark), similarly to the packet mark (nfmark). Using this
467 target and match, you can set and match on this mark.
469 config NETFILTER_XT_SET
470 tristate 'set target and match support'
472 depends on NETFILTER_ADVANCED
474 This option adds the "SET" target and "set" match.
476 Using this target and match, you can add/delete and match
477 elements in the sets created by ipset(8).
479 To compile it as a module, choose M here. If unsure, say N.
481 # alphabetically ordered list of targets
483 comment "Xtables targets"
485 config NETFILTER_XT_TARGET_AUDIT
486 tristate "AUDIT target support"
488 depends on NETFILTER_ADVANCED
490 This option adds a 'AUDIT' target, which can be used to create
491 audit records for packets dropped/accepted.
493 To compileit as a module, choose M here. If unsure, say N.
495 config NETFILTER_XT_TARGET_CHECKSUM
496 tristate "CHECKSUM target support"
497 depends on IP_NF_MANGLE || IP6_NF_MANGLE
498 depends on NETFILTER_ADVANCED
500 This option adds a `CHECKSUM' target, which can be used in the iptables mangle
503 You can use this target to compute and fill in the checksum in
504 a packet that lacks a checksum. This is particularly useful,
505 if you need to work around old applications such as dhcp clients,
506 that do not work well with checksum offloads, but don't want to disable
507 checksum offload in your device.
509 To compile it as a module, choose M here. If unsure, say N.
511 config NETFILTER_XT_TARGET_CLASSIFY
512 tristate '"CLASSIFY" target support'
513 depends on NETFILTER_ADVANCED
515 This option adds a `CLASSIFY' target, which enables the user to set
516 the priority of a packet. Some qdiscs can use this value for
517 classification, among these are:
519 atm, cbq, dsmark, pfifo_fast, htb, prio
521 To compile it as a module, choose M here. If unsure, say N.
523 config NETFILTER_XT_TARGET_CONNMARK
524 tristate '"CONNMARK" target support'
525 depends on NF_CONNTRACK
526 depends on NETFILTER_ADVANCED
527 select NETFILTER_XT_CONNMARK
529 This is a backwards-compat option for the user's convenience
530 (e.g. when running oldconfig). It selects
531 CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
533 config NETFILTER_XT_TARGET_CONNSECMARK
534 tristate '"CONNSECMARK" target support'
535 depends on NF_CONNTRACK && NF_CONNTRACK_SECMARK
536 default m if NETFILTER_ADVANCED=n
538 The CONNSECMARK target copies security markings from packets
539 to connections, and restores security markings from connections
540 to packets (if the packets are not already marked). This would
541 normally be used in conjunction with the SECMARK target.
543 To compile it as a module, choose M here. If unsure, say N.
545 config NETFILTER_XT_TARGET_CT
546 tristate '"CT" target support'
547 depends on NF_CONNTRACK
548 depends on IP_NF_RAW || IP6_NF_RAW
549 depends on NETFILTER_ADVANCED
551 This options adds a `CT' target, which allows to specify initial
552 connection tracking parameters like events to be delivered and
553 the helper to be used.
555 To compile it as a module, choose M here. If unsure, say N.
557 config NETFILTER_XT_TARGET_DSCP
558 tristate '"DSCP" and "TOS" target support'
559 depends on IP_NF_MANGLE || IP6_NF_MANGLE
560 depends on NETFILTER_ADVANCED
562 This option adds a `DSCP' target, which allows you to manipulate
563 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
565 The DSCP field can have any value between 0x0 and 0x3f inclusive.
567 It also adds the "TOS" target, which allows you to create rules in
568 the "mangle" table which alter the Type Of Service field of an IPv4
569 or the Priority field of an IPv6 packet, prior to routing.
571 To compile it as a module, choose M here. If unsure, say N.
573 config NETFILTER_XT_TARGET_HL
574 tristate '"HL" hoplimit target support'
575 depends on IP_NF_MANGLE || IP6_NF_MANGLE
576 depends on NETFILTER_ADVANCED
578 This option adds the "HL" (for IPv6) and "TTL" (for IPv4)
579 targets, which enable the user to change the
580 hoplimit/time-to-live value of the IP header.
582 While it is safe to decrement the hoplimit/TTL value, the
583 modules also allow to increment and set the hoplimit value of
584 the header to arbitrary values. This is EXTREMELY DANGEROUS
585 since you can easily create immortal packets that loop
586 forever on the network.
588 config NETFILTER_XT_TARGET_HMARK
589 tristate '"HMARK" target support'
590 depends on (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
591 depends on NETFILTER_ADVANCED
593 This option adds the "HMARK" target.
595 The target allows you to create rules in the "raw" and "mangle" tables
596 which set the skbuff mark by means of hash calculation within a given
597 range. The nfmark can influence the routing method (see "Use netfilter
598 MARK value as routing key") and can also be used by other subsystems to
599 change their behaviour.
601 To compile it as a module, choose M here. If unsure, say N.
603 config NETFILTER_XT_TARGET_IDLETIMER
604 tristate "IDLETIMER target support"
605 depends on NETFILTER_ADVANCED
608 This option adds the `IDLETIMER' target. Each matching packet
609 resets the timer associated with label specified when the rule is
610 added. When the timer expires, it triggers a sysfs notification.
611 The remaining time for expiration can be read via sysfs.
613 To compile it as a module, choose M here. If unsure, say N.
615 config NETFILTER_XT_TARGET_LED
616 tristate '"LED" target support'
617 depends on LEDS_CLASS && LEDS_TRIGGERS
618 depends on NETFILTER_ADVANCED
620 This option adds a `LED' target, which allows you to blink LEDs in
621 response to particular packets passing through your machine.
623 This can be used to turn a spare LED into a network activity LED,
624 which only flashes in response to FTP transfers, for example. Or
625 you could have an LED which lights up for a minute or two every time
626 somebody connects to your machine via SSH.
628 You will need support for the "led" class to make this work.
630 To create an LED trigger for incoming SSH traffic:
631 iptables -A INPUT -p tcp --dport 22 -j LED --led-trigger-id ssh --led-delay 1000
633 Then attach the new trigger to an LED on your system:
634 echo netfilter-ssh > /sys/class/leds/<ledname>/trigger
636 For more information on the LEDs available on your system, see
637 Documentation/leds/leds-class.txt
639 config NETFILTER_XT_TARGET_LOG
640 tristate "LOG target support"
641 default m if NETFILTER_ADVANCED=n
643 This option adds a `LOG' target, which allows you to create rules in
644 any iptables table which records the packet header to the syslog.
646 To compile it as a module, choose M here. If unsure, say N.
648 config NETFILTER_XT_TARGET_MARK
649 tristate '"MARK" target support'
650 depends on NETFILTER_ADVANCED
651 select NETFILTER_XT_MARK
653 This is a backwards-compat option for the user's convenience
654 (e.g. when running oldconfig). It selects
655 CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
657 config NETFILTER_XT_TARGET_NETMAP
658 tristate '"NETMAP" target support'
661 NETMAP is an implementation of static 1:1 NAT mapping of network
662 addresses. It maps the network address part, while keeping the host
665 To compile it as a module, choose M here. If unsure, say N.
667 config NETFILTER_XT_TARGET_NFLOG
668 tristate '"NFLOG" target support'
669 default m if NETFILTER_ADVANCED=n
670 select NETFILTER_NETLINK_LOG
672 This option enables the NFLOG target, which allows to LOG
673 messages through nfnetlink_log.
675 To compile it as a module, choose M here. If unsure, say N.
677 config NETFILTER_XT_TARGET_NFQUEUE
678 tristate '"NFQUEUE" target Support'
679 depends on NETFILTER_ADVANCED
680 select NETFILTER_NETLINK_QUEUE
682 This target replaced the old obsolete QUEUE target.
684 As opposed to QUEUE, it supports 65535 different queues,
687 To compile it as a module, choose M here. If unsure, say N.
689 config NETFILTER_XT_TARGET_NOTRACK
690 tristate '"NOTRACK" target support (DEPRECATED)'
691 depends on NF_CONNTRACK
692 depends on IP_NF_RAW || IP6_NF_RAW
693 depends on NETFILTER_ADVANCED
694 select NETFILTER_XT_TARGET_CT
696 config NETFILTER_XT_TARGET_RATEEST
697 tristate '"RATEEST" target support'
698 depends on NETFILTER_ADVANCED
700 This option adds a `RATEEST' target, which allows to measure
701 rates similar to TC estimators. The `rateest' match can be
702 used to match on the measured rates.
704 To compile it as a module, choose M here. If unsure, say N.
706 config NETFILTER_XT_TARGET_REDIRECT
707 tristate "REDIRECT target support"
710 REDIRECT is a special case of NAT: all incoming connections are
711 mapped onto the incoming interface's address, causing the packets to
712 come to the local machine instead of passing through. This is
713 useful for transparent proxies.
715 To compile it as a module, choose M here. If unsure, say N.
717 config NETFILTER_XT_TARGET_TEE
718 tristate '"TEE" - packet cloning to alternate destination'
719 depends on NETFILTER_ADVANCED
720 depends on (IPV6 || IPV6=n)
721 depends on !NF_CONNTRACK || NF_CONNTRACK
723 This option adds a "TEE" target with which a packet can be cloned and
724 this clone be rerouted to another nexthop.
726 config NETFILTER_XT_TARGET_TPROXY
727 tristate '"TPROXY" target support (EXPERIMENTAL)'
728 depends on EXPERIMENTAL
729 depends on NETFILTER_TPROXY
730 depends on NETFILTER_XTABLES
731 depends on NETFILTER_ADVANCED
732 select NF_DEFRAG_IPV4
733 select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES
735 This option adds a `TPROXY' target, which is somewhat similar to
736 REDIRECT. It can only be used in the mangle table and is useful
737 to redirect traffic to a transparent proxy. It does _not_ depend
738 on Netfilter connection tracking and NAT, unlike REDIRECT.
740 To compile it as a module, choose M here. If unsure, say N.
742 config NETFILTER_XT_TARGET_TRACE
743 tristate '"TRACE" target support'
744 depends on IP_NF_RAW || IP6_NF_RAW
745 depends on NETFILTER_ADVANCED
747 The TRACE target allows you to mark packets so that the kernel
748 will log every rule which match the packets as those traverse
749 the tables, chains, rules.
751 If you want to compile it as a module, say M here and read
752 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
754 config NETFILTER_XT_TARGET_SECMARK
755 tristate '"SECMARK" target support'
756 depends on NETWORK_SECMARK
757 default m if NETFILTER_ADVANCED=n
759 The SECMARK target allows security marking of network
760 packets, for use with security subsystems.
762 To compile it as a module, choose M here. If unsure, say N.
764 config NETFILTER_XT_TARGET_TCPMSS
765 tristate '"TCPMSS" target support'
766 depends on (IPV6 || IPV6=n)
767 default m if NETFILTER_ADVANCED=n
769 This option adds a `TCPMSS' target, which allows you to alter the
770 MSS value of TCP SYN packets, to control the maximum size for that
771 connection (usually limiting it to your outgoing interface's MTU
774 This is used to overcome criminally braindead ISPs or servers which
775 block ICMP Fragmentation Needed packets. The symptoms of this
776 problem are that everything works fine from your Linux
777 firewall/router, but machines behind it can never exchange large
779 1) Web browsers connect, then hang with no data received.
780 2) Small mail works fine, but large emails hang.
781 3) ssh works fine, but scp hangs after initial handshaking.
783 Workaround: activate this option and add a rule to your firewall
786 iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
787 -j TCPMSS --clamp-mss-to-pmtu
789 To compile it as a module, choose M here. If unsure, say N.
791 config NETFILTER_XT_TARGET_TCPOPTSTRIP
792 tristate '"TCPOPTSTRIP" target support (EXPERIMENTAL)'
793 depends on EXPERIMENTAL
794 depends on IP_NF_MANGLE || IP6_NF_MANGLE
795 depends on NETFILTER_ADVANCED
797 This option adds a "TCPOPTSTRIP" target, which allows you to strip
798 TCP options from TCP packets.
800 # alphabetically ordered list of matches
802 comment "Xtables matches"
804 config NETFILTER_XT_MATCH_ADDRTYPE
805 tristate '"addrtype" address type match support'
806 depends on NETFILTER_ADVANCED
808 This option allows you to match what routing thinks of an address,
809 eg. UNICAST, LOCAL, BROADCAST, ...
811 If you want to compile it as a module, say M here and read
812 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
814 config NETFILTER_XT_MATCH_BPF
815 tristate '"bpf" match support'
816 depends on NETFILTER_ADVANCED
818 BPF matching applies a linux socket filter to each packet and
819 accepts those for which the filter returns non-zero.
821 To compile it as a module, choose M here. If unsure, say N.
823 config NETFILTER_XT_MATCH_CLUSTER
824 tristate '"cluster" match support'
825 depends on NF_CONNTRACK
826 depends on NETFILTER_ADVANCED
828 This option allows you to build work-load-sharing clusters of
829 network servers/stateful firewalls without having a dedicated
830 load-balancing router/server/switch. Basically, this match returns
831 true when the packet must be handled by this cluster node. Thus,
832 all nodes see all packets and this match decides which node handles
833 what packets. The work-load sharing algorithm is based on source
836 If you say Y or M here, try `iptables -m cluster --help` for
839 config NETFILTER_XT_MATCH_COMMENT
840 tristate '"comment" match support'
841 depends on NETFILTER_ADVANCED
843 This option adds a `comment' dummy-match, which allows you to put
844 comments in your iptables ruleset.
846 If you want to compile it as a module, say M here and read
847 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
849 config NETFILTER_XT_MATCH_CONNBYTES
850 tristate '"connbytes" per-connection counter match support'
851 depends on NF_CONNTRACK
852 depends on NETFILTER_ADVANCED
854 This option adds a `connbytes' match, which allows you to match the
855 number of bytes and/or packets for each direction within a connection.
857 If you want to compile it as a module, say M here and read
858 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
860 config NETFILTER_XT_MATCH_CONNLABEL
861 tristate '"connlabel" match support'
862 select NF_CONNTRACK_LABELS
863 depends on NETFILTER_ADVANCED
865 This match allows you to test and assign userspace-defined labels names
866 to a connection. The kernel only stores bit values - mapping
867 names to bits is done by userspace.
869 Unlike connmark, more than 32 flag bits may be assigned to a
870 connection simultaneously.
872 config NETFILTER_XT_MATCH_CONNLIMIT
873 tristate '"connlimit" match support"'
874 depends on NF_CONNTRACK
875 depends on NETFILTER_ADVANCED
877 This match allows you to match against the number of parallel
878 connections to a server per client IP address (or address block).
880 config NETFILTER_XT_MATCH_CONNMARK
881 tristate '"connmark" connection mark match support'
882 depends on NF_CONNTRACK
883 depends on NETFILTER_ADVANCED
884 select NETFILTER_XT_CONNMARK
886 This is a backwards-compat option for the user's convenience
887 (e.g. when running oldconfig). It selects
888 CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
890 config NETFILTER_XT_MATCH_CONNTRACK
891 tristate '"conntrack" connection tracking match support'
892 depends on NF_CONNTRACK
893 default m if NETFILTER_ADVANCED=n
895 This is a general conntrack match module, a superset of the state match.
897 It allows matching on additional conntrack information, which is
898 useful in complex configurations, such as NAT gateways with multiple
899 internet links or tunnels.
901 To compile it as a module, choose M here. If unsure, say N.
903 config NETFILTER_XT_MATCH_CPU
904 tristate '"cpu" match support'
905 depends on NETFILTER_ADVANCED
907 CPU matching allows you to match packets based on the CPU
908 currently handling the packet.
910 To compile it as a module, choose M here. If unsure, say N.
912 config NETFILTER_XT_MATCH_DCCP
913 tristate '"dccp" protocol match support'
914 depends on NETFILTER_ADVANCED
917 With this option enabled, you will be able to use the iptables
918 `dccp' match in order to match on DCCP source/destination ports
921 If you want to compile it as a module, say M here and read
922 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
924 config NETFILTER_XT_MATCH_DEVGROUP
925 tristate '"devgroup" match support'
926 depends on NETFILTER_ADVANCED
928 This options adds a `devgroup' match, which allows to match on the
929 device group a network device is assigned to.
931 To compile it as a module, choose M here. If unsure, say N.
933 config NETFILTER_XT_MATCH_DSCP
934 tristate '"dscp" and "tos" match support'
935 depends on NETFILTER_ADVANCED
937 This option adds a `DSCP' match, which allows you to match against
938 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
940 The DSCP field can have any value between 0x0 and 0x3f inclusive.
942 It will also add a "tos" match, which allows you to match packets
943 based on the Type Of Service fields of the IPv4 packet (which share
944 the same bits as DSCP).
946 To compile it as a module, choose M here. If unsure, say N.
948 config NETFILTER_XT_MATCH_ECN
949 tristate '"ecn" match support'
950 depends on NETFILTER_ADVANCED
952 This option adds an "ECN" match, which allows you to match against
953 the IPv4 and TCP header ECN fields.
955 To compile it as a module, choose M here. If unsure, say N.
957 config NETFILTER_XT_MATCH_ESP
958 tristate '"esp" match support'
959 depends on NETFILTER_ADVANCED
961 This match extension allows you to match a range of SPIs
962 inside ESP header of IPSec packets.
964 To compile it as a module, choose M here. If unsure, say N.
966 config NETFILTER_XT_MATCH_HASHLIMIT
967 tristate '"hashlimit" match support'
968 depends on (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
969 depends on NETFILTER_ADVANCED
971 This option adds a `hashlimit' match.
973 As opposed to `limit', this match dynamically creates a hash table
974 of limit buckets, based on your selection of source/destination
975 addresses and/or ports.
977 It enables you to express policies like `10kpps for any given
978 destination address' or `500pps from any given source address'
981 config NETFILTER_XT_MATCH_HELPER
982 tristate '"helper" match support'
983 depends on NF_CONNTRACK
984 depends on NETFILTER_ADVANCED
986 Helper matching allows you to match packets in dynamic connections
987 tracked by a conntrack-helper, ie. ip_conntrack_ftp
989 To compile it as a module, choose M here. If unsure, say Y.
991 config NETFILTER_XT_MATCH_HL
992 tristate '"hl" hoplimit/TTL match support'
993 depends on NETFILTER_ADVANCED
995 HL matching allows you to match packets based on the hoplimit
996 in the IPv6 header, or the time-to-live field in the IPv4
997 header of the packet.
999 config NETFILTER_XT_MATCH_IPRANGE
1000 tristate '"iprange" address range match support'
1001 depends on NETFILTER_ADVANCED
1003 This option adds a "iprange" match, which allows you to match based on
1004 an IP address range. (Normal iptables only matches on single addresses
1005 with an optional mask.)
1009 config NETFILTER_XT_MATCH_IPVS
1010 tristate '"ipvs" match support'
1012 depends on NETFILTER_ADVANCED
1013 depends on NF_CONNTRACK
1015 This option allows you to match against IPVS properties of a packet.
1019 config NETFILTER_XT_MATCH_LENGTH
1020 tristate '"length" match support'
1021 depends on NETFILTER_ADVANCED
1023 This option allows you to match the length of a packet against a
1024 specific value or range of values.
1026 To compile it as a module, choose M here. If unsure, say N.
1028 config NETFILTER_XT_MATCH_LIMIT
1029 tristate '"limit" match support'
1030 depends on NETFILTER_ADVANCED
1032 limit matching allows you to control the rate at which a rule can be
1033 matched: mainly useful in combination with the LOG target ("LOG
1034 target support", below) and to avoid some Denial of Service attacks.
1036 To compile it as a module, choose M here. If unsure, say N.
1038 config NETFILTER_XT_MATCH_MAC
1039 tristate '"mac" address match support'
1040 depends on NETFILTER_ADVANCED
1042 MAC matching allows you to match packets based on the source
1043 Ethernet address of the packet.
1045 To compile it as a module, choose M here. If unsure, say N.
1047 config NETFILTER_XT_MATCH_MARK
1048 tristate '"mark" match support'
1049 depends on NETFILTER_ADVANCED
1050 select NETFILTER_XT_MARK
1052 This is a backwards-compat option for the user's convenience
1053 (e.g. when running oldconfig). It selects
1054 CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
1056 config NETFILTER_XT_MATCH_MULTIPORT
1057 tristate '"multiport" Multiple port match support'
1058 depends on NETFILTER_ADVANCED
1060 Multiport matching allows you to match TCP or UDP packets based on
1061 a series of source or destination ports: normally a rule can only
1062 match a single range of ports.
1064 To compile it as a module, choose M here. If unsure, say N.
1066 config NETFILTER_XT_MATCH_NFACCT
1067 tristate '"nfacct" match support'
1068 depends on NETFILTER_ADVANCED
1069 select NETFILTER_NETLINK_ACCT
1071 This option allows you to use the extended accounting through
1074 To compile it as a module, choose M here. If unsure, say N.
1076 config NETFILTER_XT_MATCH_OSF
1077 tristate '"osf" Passive OS fingerprint match'
1078 depends on NETFILTER_ADVANCED && NETFILTER_NETLINK
1080 This option selects the Passive OS Fingerprinting match module
1081 that allows to passively match the remote operating system by
1082 analyzing incoming TCP SYN packets.
1084 Rules and loading software can be downloaded from
1085 http://www.ioremap.net/projects/osf
1087 To compile it as a module, choose M here. If unsure, say N.
1089 config NETFILTER_XT_MATCH_OWNER
1090 tristate '"owner" match support'
1091 depends on NETFILTER_ADVANCED
1093 Socket owner matching allows you to match locally-generated packets
1094 based on who created the socket: the user or group. It is also
1095 possible to check whether a socket actually exists.
1097 config NETFILTER_XT_MATCH_POLICY
1098 tristate 'IPsec "policy" match support'
1100 default m if NETFILTER_ADVANCED=n
1102 Policy matching allows you to match packets based on the
1103 IPsec policy that was used during decapsulation/will
1104 be used during encapsulation.
1106 To compile it as a module, choose M here. If unsure, say N.
1108 config NETFILTER_XT_MATCH_PHYSDEV
1109 tristate '"physdev" match support'
1110 depends on BRIDGE && BRIDGE_NETFILTER
1111 depends on NETFILTER_ADVANCED
1113 Physdev packet matching matches against the physical bridge ports
1114 the IP packet arrived on or will leave by.
1116 To compile it as a module, choose M here. If unsure, say N.
1118 config NETFILTER_XT_MATCH_PKTTYPE
1119 tristate '"pkttype" packet type match support'
1120 depends on NETFILTER_ADVANCED
1122 Packet type matching allows you to match a packet by
1123 its "class", eg. BROADCAST, MULTICAST, ...
1126 iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG
1128 To compile it as a module, choose M here. If unsure, say N.
1130 config NETFILTER_XT_MATCH_QUOTA
1131 tristate '"quota" match support'
1132 depends on NETFILTER_ADVANCED
1134 This option adds a `quota' match, which allows to match on a
1137 If you want to compile it as a module, say M here and read
1138 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1140 config NETFILTER_XT_MATCH_RATEEST
1141 tristate '"rateest" match support'
1142 depends on NETFILTER_ADVANCED
1143 select NETFILTER_XT_TARGET_RATEEST
1145 This option adds a `rateest' match, which allows to match on the
1146 rate estimated by the RATEEST target.
1148 To compile it as a module, choose M here. If unsure, say N.
1150 config NETFILTER_XT_MATCH_REALM
1151 tristate '"realm" match support'
1152 depends on NETFILTER_ADVANCED
1153 select IP_ROUTE_CLASSID
1155 This option adds a `realm' match, which allows you to use the realm
1156 key from the routing subsystem inside iptables.
1158 This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option
1161 If you want to compile it as a module, say M here and read
1162 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1164 config NETFILTER_XT_MATCH_RECENT
1165 tristate '"recent" match support'
1166 depends on NETFILTER_ADVANCED
1168 This match is used for creating one or many lists of recently
1169 used addresses and then matching against that/those list(s).
1171 Short options are available by using 'iptables -m recent -h'
1172 Official Website: <http://snowman.net/projects/ipt_recent/>
1174 config NETFILTER_XT_MATCH_SCTP
1175 tristate '"sctp" protocol match support (EXPERIMENTAL)'
1176 depends on EXPERIMENTAL
1177 depends on NETFILTER_ADVANCED
1180 With this option enabled, you will be able to use the
1181 `sctp' match in order to match on SCTP source/destination ports
1182 and SCTP chunk types.
1184 If you want to compile it as a module, say M here and read
1185 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1187 config NETFILTER_XT_MATCH_SOCKET
1188 tristate '"socket" match support (EXPERIMENTAL)'
1189 depends on EXPERIMENTAL
1190 depends on NETFILTER_TPROXY
1191 depends on NETFILTER_XTABLES
1192 depends on NETFILTER_ADVANCED
1193 depends on !NF_CONNTRACK || NF_CONNTRACK
1194 select NF_DEFRAG_IPV4
1195 select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES
1197 This option adds a `socket' match, which can be used to match
1198 packets for which a TCP or UDP socket lookup finds a valid socket.
1199 It can be used in combination with the MARK target and policy
1200 routing to implement full featured non-locally bound sockets.
1202 To compile it as a module, choose M here. If unsure, say N.
1204 config NETFILTER_XT_MATCH_STATE
1205 tristate '"state" match support'
1206 depends on NF_CONNTRACK
1207 default m if NETFILTER_ADVANCED=n
1209 Connection state matching allows you to match packets based on their
1210 relationship to a tracked connection (ie. previous packets). This
1211 is a powerful tool for packet classification.
1213 To compile it as a module, choose M here. If unsure, say N.
1215 config NETFILTER_XT_MATCH_STATISTIC
1216 tristate '"statistic" match support'
1217 depends on NETFILTER_ADVANCED
1219 This option adds a `statistic' match, which allows you to match
1220 on packets periodically or randomly with a given percentage.
1222 To compile it as a module, choose M here. If unsure, say N.
1224 config NETFILTER_XT_MATCH_STRING
1225 tristate '"string" match support'
1226 depends on NETFILTER_ADVANCED
1228 select TEXTSEARCH_KMP
1229 select TEXTSEARCH_BM
1230 select TEXTSEARCH_FSM
1232 This option adds a `string' match, which allows you to look for
1233 pattern matchings in packets.
1235 To compile it as a module, choose M here. If unsure, say N.
1237 config NETFILTER_XT_MATCH_TCPMSS
1238 tristate '"tcpmss" match support'
1239 depends on NETFILTER_ADVANCED
1241 This option adds a `tcpmss' match, which allows you to examine the
1242 MSS value of TCP SYN packets, which control the maximum packet size
1243 for that connection.
1245 To compile it as a module, choose M here. If unsure, say N.
1247 config NETFILTER_XT_MATCH_TIME
1248 tristate '"time" match support'
1249 depends on NETFILTER_ADVANCED
1251 This option adds a "time" match, which allows you to match based on
1252 the packet arrival time (at the machine which netfilter is running)
1253 on) or departure time/date (for locally generated packets).
1255 If you say Y here, try `iptables -m time --help` for
1258 If you want to compile it as a module, say M here.
1261 config NETFILTER_XT_MATCH_U32
1262 tristate '"u32" match support'
1263 depends on NETFILTER_ADVANCED
1265 u32 allows you to extract quantities of up to 4 bytes from a packet,
1266 AND them with specified masks, shift them by specified amounts and
1267 test whether the results are in any of a set of specified ranges.
1268 The specification of what to extract is general enough to skip over
1269 headers with lengths stored in the packet, as in IP or TCP header
1272 Details and examples are in the kernel module source.
1274 endif # NETFILTER_XTABLES
1278 source "net/netfilter/ipset/Kconfig"
1280 source "net/netfilter/ipvs/Kconfig"