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_CT_PROTO_DCCP
128 tristate 'DCCP protocol connection tracking support (EXPERIMENTAL)'
129 depends on EXPERIMENTAL
130 depends on NETFILTER_ADVANCED
133 With this option enabled, the layer 3 independent connection
134 tracking code will be able to do state tracking on DCCP connections.
138 config NF_CT_PROTO_GRE
141 config NF_CT_PROTO_SCTP
142 tristate 'SCTP protocol connection tracking support (EXPERIMENTAL)'
143 depends on EXPERIMENTAL
144 depends on NETFILTER_ADVANCED
147 With this option enabled, the layer 3 independent connection
148 tracking code will be able to do state tracking on SCTP connections.
150 If you want to compile it as a module, say M here and read
151 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
153 config NF_CT_PROTO_UDPLITE
154 tristate 'UDP-Lite protocol connection tracking support'
155 depends on NETFILTER_ADVANCED
157 With this option enabled, the layer 3 independent connection
158 tracking code will be able to do state tracking on UDP-Lite
161 To compile it as a module, choose M here. If unsure, say N.
163 config NF_CONNTRACK_AMANDA
164 tristate "Amanda backup protocol support"
165 depends on NETFILTER_ADVANCED
167 select TEXTSEARCH_KMP
169 If you are running the Amanda backup package <http://www.amanda.org/>
170 on this machine or machines that will be MASQUERADED through this
171 machine, then you may want to enable this feature. This allows the
172 connection tracking and natting code to allow the sub-channels that
173 Amanda requires for communication of the backup data, messages and
176 To compile it as a module, choose M here. If unsure, say N.
178 config NF_CONNTRACK_FTP
179 tristate "FTP protocol support"
180 default m if NETFILTER_ADVANCED=n
182 Tracking FTP connections is problematic: special helpers are
183 required for tracking them, and doing masquerading and other forms
184 of Network Address Translation on them.
186 This is FTP support on Layer 3 independent connection tracking.
187 Layer 3 independent connection tracking is experimental scheme
188 which generalize ip_conntrack to support other layer 3 protocols.
190 To compile it as a module, choose M here. If unsure, say N.
192 config NF_CONNTRACK_H323
193 tristate "H.323 protocol support"
194 depends on (IPV6 || IPV6=n)
195 depends on NETFILTER_ADVANCED
197 H.323 is a VoIP signalling protocol from ITU-T. As one of the most
198 important VoIP protocols, it is widely used by voice hardware and
199 software including voice gateways, IP phones, Netmeeting, OpenPhone,
202 With this module you can support H.323 on a connection tracking/NAT
205 This module supports RAS, Fast Start, H.245 Tunnelling, Call
206 Forwarding, RTP/RTCP and T.120 based audio, video, fax, chat,
207 whiteboard, file transfer, etc. For more information, please
208 visit http://nath323.sourceforge.net/.
210 To compile it as a module, choose M here. If unsure, say N.
212 config NF_CONNTRACK_IRC
213 tristate "IRC protocol support"
214 default m if NETFILTER_ADVANCED=n
216 There is a commonly-used extension to IRC called
217 Direct Client-to-Client Protocol (DCC). This enables users to send
218 files to each other, and also chat to each other without the need
219 of a server. DCC Sending is used anywhere you send files over IRC,
220 and DCC Chat is most commonly used by Eggdrop bots. If you are
221 using NAT, this extension will enable you to send files and initiate
222 chats. Note that you do NOT need this extension to get files or
223 have others initiate chats, or everything else in IRC.
225 To compile it as a module, choose M here. If unsure, say N.
227 config NF_CONNTRACK_BROADCAST
230 config NF_CONNTRACK_NETBIOS_NS
231 tristate "NetBIOS name service protocol support"
232 select NF_CONNTRACK_BROADCAST
234 NetBIOS name service requests are sent as broadcast messages from an
235 unprivileged port and responded to with unicast messages to the
236 same port. This make them hard to firewall properly because connection
237 tracking doesn't deal with broadcasts. This helper tracks locally
238 originating NetBIOS name service requests and the corresponding
239 responses. It relies on correct IP address configuration, specifically
240 netmask and broadcast address. When properly configured, the output
241 of "ip address show" should look similar to this:
243 $ ip -4 address show eth0
244 4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
245 inet 172.16.2.252/24 brd 172.16.2.255 scope global eth0
247 To compile it as a module, choose M here. If unsure, say N.
249 config NF_CONNTRACK_SNMP
250 tristate "SNMP service protocol support"
251 depends on NETFILTER_ADVANCED
252 select NF_CONNTRACK_BROADCAST
254 SNMP service requests are sent as broadcast messages from an
255 unprivileged port and responded to with unicast messages to the
256 same port. This make them hard to firewall properly because connection
257 tracking doesn't deal with broadcasts. This helper tracks locally
258 originating SNMP service requests and the corresponding
259 responses. It relies on correct IP address configuration, specifically
260 netmask and broadcast address.
262 To compile it as a module, choose M here. If unsure, say N.
264 config NF_CONNTRACK_PPTP
265 tristate "PPtP protocol support"
266 depends on NETFILTER_ADVANCED
267 select NF_CT_PROTO_GRE
269 This module adds support for PPTP (Point to Point Tunnelling
270 Protocol, RFC2637) connection tracking and NAT.
272 If you are running PPTP sessions over a stateful firewall or NAT
273 box, you may want to enable this feature.
275 Please note that not all PPTP modes of operation are supported yet.
276 Specifically these limitations exist:
277 - Blindly assumes that control connections are always established
278 in PNS->PAC direction. This is a violation of RFC2637.
279 - Only supports a single call within each session
281 To compile it as a module, choose M here. If unsure, say N.
283 config NF_CONNTRACK_SANE
284 tristate "SANE protocol support (EXPERIMENTAL)"
285 depends on EXPERIMENTAL
286 depends on NETFILTER_ADVANCED
288 SANE is a protocol for remote access to scanners as implemented
289 by the 'saned' daemon. Like FTP, it uses separate control and
292 With this module you can support SANE on a connection tracking
295 To compile it as a module, choose M here. If unsure, say N.
297 config NF_CONNTRACK_SIP
298 tristate "SIP protocol support"
299 default m if NETFILTER_ADVANCED=n
301 SIP is an application-layer control protocol that can establish,
302 modify, and terminate multimedia sessions (conferences) such as
303 Internet telephony calls. With the ip_conntrack_sip and
304 the nf_nat_sip modules you can support the protocol on a connection
305 tracking/NATing firewall.
307 To compile it as a module, choose M here. If unsure, say N.
309 config NF_CONNTRACK_TFTP
310 tristate "TFTP protocol support"
311 depends on NETFILTER_ADVANCED
313 TFTP connection tracking helper, this is required depending
314 on how restrictive your ruleset is.
315 If you are using a tftp client behind -j SNAT or -j MASQUERADING
318 To compile it as a module, choose M here. If unsure, say N.
321 tristate 'Connection tracking netlink interface'
322 select NETFILTER_NETLINK
323 default m if NETFILTER_ADVANCED=n
325 This option enables support for a netlink-based userspace interface
327 config NF_CT_NETLINK_TIMEOUT
328 tristate 'Connection tracking timeout tuning via Netlink'
329 select NETFILTER_NETLINK
330 depends on NETFILTER_ADVANCED
332 This option enables support for connection tracking timeout
333 fine-grain tuning. This allows you to attach specific timeout
334 policies to flows, instead of using the global timeout policy.
338 config NF_CT_NETLINK_HELPER
339 tristate 'Connection tracking helpers in user-space via Netlink'
340 select NETFILTER_NETLINK
341 depends on NF_CT_NETLINK
342 depends on NETFILTER_NETLINK_QUEUE
343 depends on NETFILTER_NETLINK_QUEUE_CT
344 depends on NETFILTER_ADVANCED
346 This option enables the user-space connection tracking helpers
351 config NETFILTER_NETLINK_QUEUE_CT
352 bool "NFQUEUE integration with Connection Tracking"
354 depends on NETFILTER_NETLINK_QUEUE
356 If this option is enabled, NFQUEUE can include Connection Tracking
357 information together with the packet is the enqueued via NFNETLINK.
367 config NF_NAT_PROTO_DCCP
369 depends on NF_NAT && NF_CT_PROTO_DCCP
370 default NF_NAT && NF_CT_PROTO_DCCP
372 config NF_NAT_PROTO_UDPLITE
374 depends on NF_NAT && NF_CT_PROTO_UDPLITE
375 default NF_NAT && NF_CT_PROTO_UDPLITE
377 config NF_NAT_PROTO_SCTP
379 default NF_NAT && NF_CT_PROTO_SCTP
380 depends on NF_NAT && NF_CT_PROTO_SCTP
385 depends on NF_CONNTRACK && NF_NAT
386 default NF_NAT && NF_CONNTRACK_AMANDA
390 depends on NF_CONNTRACK && NF_NAT
391 default NF_NAT && NF_CONNTRACK_FTP
395 # transparent proxy support
396 config NETFILTER_TPROXY
397 tristate "Transparent proxying support (EXPERIMENTAL)"
398 depends on EXPERIMENTAL
399 depends on IP_NF_MANGLE
400 depends on NETFILTER_ADVANCED
402 This option enables transparent proxying support, that is,
403 support for handling non-locally bound IPv4 TCP and UDP sockets.
404 For it to work you will have to configure certain iptables rules
405 and use policy routing. For more information on how to set it up
406 see Documentation/networking/tproxy.txt.
408 To compile it as a module, choose M here. If unsure, say N.
410 config NETFILTER_XTABLES
411 tristate "Netfilter Xtables support (required for ip_tables)"
412 default m if NETFILTER_ADVANCED=n
414 This is required if you intend to use any of ip_tables,
415 ip6_tables or arp_tables.
419 comment "Xtables combined modules"
421 config NETFILTER_XT_MARK
422 tristate 'nfmark target and match support'
423 default m if NETFILTER_ADVANCED=n
425 This option adds the "MARK" target and "mark" match.
427 Netfilter mark matching allows you to match packets based on the
428 "nfmark" value in the packet.
429 The target allows you to create rules in the "mangle" table which alter
430 the netfilter mark (nfmark) field associated with the packet.
432 Prior to routing, the nfmark can influence the routing method (see
433 "Use netfilter MARK value as routing key") and can also be used by
434 other subsystems to change their behavior.
436 config NETFILTER_XT_CONNMARK
437 tristate 'ctmark target and match support'
438 depends on NF_CONNTRACK
439 depends on NETFILTER_ADVANCED
440 select NF_CONNTRACK_MARK
442 This option adds the "CONNMARK" target and "connmark" match.
444 Netfilter allows you to store a mark value per connection (a.k.a.
445 ctmark), similarly to the packet mark (nfmark). Using this
446 target and match, you can set and match on this mark.
448 config NETFILTER_XT_SET
449 tristate 'set target and match support'
451 depends on NETFILTER_ADVANCED
453 This option adds the "SET" target and "set" match.
455 Using this target and match, you can add/delete and match
456 elements in the sets created by ipset(8).
458 To compile it as a module, choose M here. If unsure, say N.
460 # alphabetically ordered list of targets
462 comment "Xtables targets"
464 config NETFILTER_XT_TARGET_AUDIT
465 tristate "AUDIT target support"
467 depends on NETFILTER_ADVANCED
469 This option adds a 'AUDIT' target, which can be used to create
470 audit records for packets dropped/accepted.
472 To compileit as a module, choose M here. If unsure, say N.
474 config NETFILTER_XT_TARGET_CHECKSUM
475 tristate "CHECKSUM target support"
476 depends on IP_NF_MANGLE || IP6_NF_MANGLE
477 depends on NETFILTER_ADVANCED
479 This option adds a `CHECKSUM' target, which can be used in the iptables mangle
482 You can use this target to compute and fill in the checksum in
483 a packet that lacks a checksum. This is particularly useful,
484 if you need to work around old applications such as dhcp clients,
485 that do not work well with checksum offloads, but don't want to disable
486 checksum offload in your device.
488 To compile it as a module, choose M here. If unsure, say N.
490 config NETFILTER_XT_TARGET_CLASSIFY
491 tristate '"CLASSIFY" target support'
492 depends on NETFILTER_ADVANCED
494 This option adds a `CLASSIFY' target, which enables the user to set
495 the priority of a packet. Some qdiscs can use this value for
496 classification, among these are:
498 atm, cbq, dsmark, pfifo_fast, htb, prio
500 To compile it as a module, choose M here. If unsure, say N.
502 config NETFILTER_XT_TARGET_CONNMARK
503 tristate '"CONNMARK" target support'
504 depends on NF_CONNTRACK
505 depends on NETFILTER_ADVANCED
506 select NETFILTER_XT_CONNMARK
508 This is a backwards-compat option for the user's convenience
509 (e.g. when running oldconfig). It selects
510 CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
512 config NETFILTER_XT_TARGET_CONNSECMARK
513 tristate '"CONNSECMARK" target support'
514 depends on NF_CONNTRACK && NF_CONNTRACK_SECMARK
515 default m if NETFILTER_ADVANCED=n
517 The CONNSECMARK target copies security markings from packets
518 to connections, and restores security markings from connections
519 to packets (if the packets are not already marked). This would
520 normally be used in conjunction with the SECMARK target.
522 To compile it as a module, choose M here. If unsure, say N.
524 config NETFILTER_XT_TARGET_CT
525 tristate '"CT" target support'
526 depends on NF_CONNTRACK
527 depends on IP_NF_RAW || IP6_NF_RAW
528 depends on NETFILTER_ADVANCED
530 This options adds a `CT' target, which allows to specify initial
531 connection tracking parameters like events to be delivered and
532 the helper to be used.
534 To compile it as a module, choose M here. If unsure, say N.
536 config NETFILTER_XT_TARGET_DSCP
537 tristate '"DSCP" and "TOS" target support'
538 depends on IP_NF_MANGLE || IP6_NF_MANGLE
539 depends on NETFILTER_ADVANCED
541 This option adds a `DSCP' target, which allows you to manipulate
542 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
544 The DSCP field can have any value between 0x0 and 0x3f inclusive.
546 It also adds the "TOS" target, which allows you to create rules in
547 the "mangle" table which alter the Type Of Service field of an IPv4
548 or the Priority field of an IPv6 packet, prior to routing.
550 To compile it as a module, choose M here. If unsure, say N.
552 config NETFILTER_XT_TARGET_HL
553 tristate '"HL" hoplimit target support'
554 depends on IP_NF_MANGLE || IP6_NF_MANGLE
555 depends on NETFILTER_ADVANCED
557 This option adds the "HL" (for IPv6) and "TTL" (for IPv4)
558 targets, which enable the user to change the
559 hoplimit/time-to-live value of the IP header.
561 While it is safe to decrement the hoplimit/TTL value, the
562 modules also allow to increment and set the hoplimit value of
563 the header to arbitrary values. This is EXTREMELY DANGEROUS
564 since you can easily create immortal packets that loop
565 forever on the network.
567 config NETFILTER_XT_TARGET_HMARK
568 tristate '"HMARK" target support'
569 depends on (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
570 depends on NETFILTER_ADVANCED
572 This option adds the "HMARK" target.
574 The target allows you to create rules in the "raw" and "mangle" tables
575 which set the skbuff mark by means of hash calculation within a given
576 range. The nfmark can influence the routing method (see "Use netfilter
577 MARK value as routing key") and can also be used by other subsystems to
578 change their behaviour.
580 To compile it as a module, choose M here. If unsure, say N.
582 config NETFILTER_XT_TARGET_IDLETIMER
583 tristate "IDLETIMER target support"
584 depends on NETFILTER_ADVANCED
587 This option adds the `IDLETIMER' target. Each matching packet
588 resets the timer associated with label specified when the rule is
589 added. When the timer expires, it triggers a sysfs notification.
590 The remaining time for expiration can be read via sysfs.
592 To compile it as a module, choose M here. If unsure, say N.
594 config NETFILTER_XT_TARGET_LED
595 tristate '"LED" target support'
596 depends on LEDS_CLASS && LEDS_TRIGGERS
597 depends on NETFILTER_ADVANCED
599 This option adds a `LED' target, which allows you to blink LEDs in
600 response to particular packets passing through your machine.
602 This can be used to turn a spare LED into a network activity LED,
603 which only flashes in response to FTP transfers, for example. Or
604 you could have an LED which lights up for a minute or two every time
605 somebody connects to your machine via SSH.
607 You will need support for the "led" class to make this work.
609 To create an LED trigger for incoming SSH traffic:
610 iptables -A INPUT -p tcp --dport 22 -j LED --led-trigger-id ssh --led-delay 1000
612 Then attach the new trigger to an LED on your system:
613 echo netfilter-ssh > /sys/class/leds/<ledname>/trigger
615 For more information on the LEDs available on your system, see
616 Documentation/leds/leds-class.txt
618 config NETFILTER_XT_TARGET_LOG
619 tristate "LOG target support"
620 default m if NETFILTER_ADVANCED=n
622 This option adds a `LOG' target, which allows you to create rules in
623 any iptables table which records the packet header to the syslog.
625 To compile it as a module, choose M here. If unsure, say N.
627 config NETFILTER_XT_TARGET_MARK
628 tristate '"MARK" target support'
629 depends on NETFILTER_ADVANCED
630 select NETFILTER_XT_MARK
632 This is a backwards-compat option for the user's convenience
633 (e.g. when running oldconfig). It selects
634 CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
636 config NETFILTER_XT_TARGET_NFLOG
637 tristate '"NFLOG" target support'
638 default m if NETFILTER_ADVANCED=n
639 select NETFILTER_NETLINK_LOG
641 This option enables the NFLOG target, which allows to LOG
642 messages through nfnetlink_log.
644 To compile it as a module, choose M here. If unsure, say N.
646 config NETFILTER_XT_TARGET_NFQUEUE
647 tristate '"NFQUEUE" target Support'
648 depends on NETFILTER_ADVANCED
649 select NETFILTER_NETLINK_QUEUE
651 This target replaced the old obsolete QUEUE target.
653 As opposed to QUEUE, it supports 65535 different queues,
656 To compile it as a module, choose M here. If unsure, say N.
658 config NETFILTER_XT_TARGET_NOTRACK
659 tristate '"NOTRACK" target support'
660 depends on IP_NF_RAW || IP6_NF_RAW
661 depends on NF_CONNTRACK
663 The NOTRACK target allows a select rule to specify
664 which packets *not* to enter the conntrack/NAT
665 subsystem with all the consequences (no ICMP error tracking,
666 no protocol helpers for the selected packets).
668 If you want to compile it as a module, say M here and read
669 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
671 config NETFILTER_XT_TARGET_RATEEST
672 tristate '"RATEEST" target support'
673 depends on NETFILTER_ADVANCED
675 This option adds a `RATEEST' target, which allows to measure
676 rates similar to TC estimators. The `rateest' match can be
677 used to match on the measured rates.
679 To compile it as a module, choose M here. If unsure, say N.
681 config NETFILTER_XT_TARGET_TEE
682 tristate '"TEE" - packet cloning to alternate destination'
683 depends on NETFILTER_ADVANCED
684 depends on (IPV6 || IPV6=n)
685 depends on !NF_CONNTRACK || NF_CONNTRACK
687 This option adds a "TEE" target with which a packet can be cloned and
688 this clone be rerouted to another nexthop.
690 config NETFILTER_XT_TARGET_TPROXY
691 tristate '"TPROXY" target support (EXPERIMENTAL)'
692 depends on EXPERIMENTAL
693 depends on NETFILTER_TPROXY
694 depends on NETFILTER_XTABLES
695 depends on NETFILTER_ADVANCED
696 select NF_DEFRAG_IPV4
697 select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES
699 This option adds a `TPROXY' target, which is somewhat similar to
700 REDIRECT. It can only be used in the mangle table and is useful
701 to redirect traffic to a transparent proxy. It does _not_ depend
702 on Netfilter connection tracking and NAT, unlike REDIRECT.
704 To compile it as a module, choose M here. If unsure, say N.
706 config NETFILTER_XT_TARGET_TRACE
707 tristate '"TRACE" target support'
708 depends on IP_NF_RAW || IP6_NF_RAW
709 depends on NETFILTER_ADVANCED
711 The TRACE target allows you to mark packets so that the kernel
712 will log every rule which match the packets as those traverse
713 the tables, chains, rules.
715 If you want to compile it as a module, say M here and read
716 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
718 config NETFILTER_XT_TARGET_SECMARK
719 tristate '"SECMARK" target support'
720 depends on NETWORK_SECMARK
721 default m if NETFILTER_ADVANCED=n
723 The SECMARK target allows security marking of network
724 packets, for use with security subsystems.
726 To compile it as a module, choose M here. If unsure, say N.
728 config NETFILTER_XT_TARGET_TCPMSS
729 tristate '"TCPMSS" target support'
730 depends on (IPV6 || IPV6=n)
731 default m if NETFILTER_ADVANCED=n
733 This option adds a `TCPMSS' target, which allows you to alter the
734 MSS value of TCP SYN packets, to control the maximum size for that
735 connection (usually limiting it to your outgoing interface's MTU
738 This is used to overcome criminally braindead ISPs or servers which
739 block ICMP Fragmentation Needed packets. The symptoms of this
740 problem are that everything works fine from your Linux
741 firewall/router, but machines behind it can never exchange large
743 1) Web browsers connect, then hang with no data received.
744 2) Small mail works fine, but large emails hang.
745 3) ssh works fine, but scp hangs after initial handshaking.
747 Workaround: activate this option and add a rule to your firewall
750 iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
751 -j TCPMSS --clamp-mss-to-pmtu
753 To compile it as a module, choose M here. If unsure, say N.
755 config NETFILTER_XT_TARGET_TCPOPTSTRIP
756 tristate '"TCPOPTSTRIP" target support (EXPERIMENTAL)'
757 depends on EXPERIMENTAL
758 depends on IP_NF_MANGLE || IP6_NF_MANGLE
759 depends on NETFILTER_ADVANCED
761 This option adds a "TCPOPTSTRIP" target, which allows you to strip
762 TCP options from TCP packets.
764 # alphabetically ordered list of matches
766 comment "Xtables matches"
768 config NETFILTER_XT_MATCH_ADDRTYPE
769 tristate '"addrtype" address type match support'
770 depends on NETFILTER_ADVANCED
772 This option allows you to match what routing thinks of an address,
773 eg. UNICAST, LOCAL, BROADCAST, ...
775 If you want to compile it as a module, say M here and read
776 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
778 config NETFILTER_XT_MATCH_CLUSTER
779 tristate '"cluster" match support'
780 depends on NF_CONNTRACK
781 depends on NETFILTER_ADVANCED
783 This option allows you to build work-load-sharing clusters of
784 network servers/stateful firewalls without having a dedicated
785 load-balancing router/server/switch. Basically, this match returns
786 true when the packet must be handled by this cluster node. Thus,
787 all nodes see all packets and this match decides which node handles
788 what packets. The work-load sharing algorithm is based on source
791 If you say Y or M here, try `iptables -m cluster --help` for
794 config NETFILTER_XT_MATCH_COMMENT
795 tristate '"comment" match support'
796 depends on NETFILTER_ADVANCED
798 This option adds a `comment' dummy-match, which allows you to put
799 comments in your iptables ruleset.
801 If you want to compile it as a module, say M here and read
802 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
804 config NETFILTER_XT_MATCH_CONNBYTES
805 tristate '"connbytes" per-connection counter match support'
806 depends on NF_CONNTRACK
807 depends on NETFILTER_ADVANCED
809 This option adds a `connbytes' match, which allows you to match the
810 number of bytes and/or packets for each direction within a connection.
812 If you want to compile it as a module, say M here and read
813 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
815 config NETFILTER_XT_MATCH_CONNLIMIT
816 tristate '"connlimit" match support"'
817 depends on NF_CONNTRACK
818 depends on NETFILTER_ADVANCED
820 This match allows you to match against the number of parallel
821 connections to a server per client IP address (or address block).
823 config NETFILTER_XT_MATCH_CONNMARK
824 tristate '"connmark" connection mark match support'
825 depends on NF_CONNTRACK
826 depends on NETFILTER_ADVANCED
827 select NETFILTER_XT_CONNMARK
829 This is a backwards-compat option for the user's convenience
830 (e.g. when running oldconfig). It selects
831 CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
833 config NETFILTER_XT_MATCH_CONNTRACK
834 tristate '"conntrack" connection tracking match support'
835 depends on NF_CONNTRACK
836 default m if NETFILTER_ADVANCED=n
838 This is a general conntrack match module, a superset of the state match.
840 It allows matching on additional conntrack information, which is
841 useful in complex configurations, such as NAT gateways with multiple
842 internet links or tunnels.
844 To compile it as a module, choose M here. If unsure, say N.
846 config NETFILTER_XT_MATCH_CPU
847 tristate '"cpu" match support'
848 depends on NETFILTER_ADVANCED
850 CPU matching allows you to match packets based on the CPU
851 currently handling the packet.
853 To compile it as a module, choose M here. If unsure, say N.
855 config NETFILTER_XT_MATCH_DCCP
856 tristate '"dccp" protocol match support'
857 depends on NETFILTER_ADVANCED
860 With this option enabled, you will be able to use the iptables
861 `dccp' match in order to match on DCCP source/destination ports
864 If you want to compile it as a module, say M here and read
865 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
867 config NETFILTER_XT_MATCH_DEVGROUP
868 tristate '"devgroup" match support'
869 depends on NETFILTER_ADVANCED
871 This options adds a `devgroup' match, which allows to match on the
872 device group a network device is assigned to.
874 To compile it as a module, choose M here. If unsure, say N.
876 config NETFILTER_XT_MATCH_DSCP
877 tristate '"dscp" and "tos" match support'
878 depends on NETFILTER_ADVANCED
880 This option adds a `DSCP' match, which allows you to match against
881 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
883 The DSCP field can have any value between 0x0 and 0x3f inclusive.
885 It will also add a "tos" match, which allows you to match packets
886 based on the Type Of Service fields of the IPv4 packet (which share
887 the same bits as DSCP).
889 To compile it as a module, choose M here. If unsure, say N.
891 config NETFILTER_XT_MATCH_ECN
892 tristate '"ecn" match support'
893 depends on NETFILTER_ADVANCED
895 This option adds an "ECN" match, which allows you to match against
896 the IPv4 and TCP header ECN fields.
898 To compile it as a module, choose M here. If unsure, say N.
900 config NETFILTER_XT_MATCH_ESP
901 tristate '"esp" match support'
902 depends on NETFILTER_ADVANCED
904 This match extension allows you to match a range of SPIs
905 inside ESP header of IPSec packets.
907 To compile it as a module, choose M here. If unsure, say N.
909 config NETFILTER_XT_MATCH_HASHLIMIT
910 tristate '"hashlimit" match support'
911 depends on (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
912 depends on NETFILTER_ADVANCED
914 This option adds a `hashlimit' match.
916 As opposed to `limit', this match dynamically creates a hash table
917 of limit buckets, based on your selection of source/destination
918 addresses and/or ports.
920 It enables you to express policies like `10kpps for any given
921 destination address' or `500pps from any given source address'
924 config NETFILTER_XT_MATCH_HELPER
925 tristate '"helper" match support'
926 depends on NF_CONNTRACK
927 depends on NETFILTER_ADVANCED
929 Helper matching allows you to match packets in dynamic connections
930 tracked by a conntrack-helper, ie. ip_conntrack_ftp
932 To compile it as a module, choose M here. If unsure, say Y.
934 config NETFILTER_XT_MATCH_HL
935 tristate '"hl" hoplimit/TTL match support'
936 depends on NETFILTER_ADVANCED
938 HL matching allows you to match packets based on the hoplimit
939 in the IPv6 header, or the time-to-live field in the IPv4
940 header of the packet.
942 config NETFILTER_XT_MATCH_IPRANGE
943 tristate '"iprange" address range match support'
944 depends on NETFILTER_ADVANCED
946 This option adds a "iprange" match, which allows you to match based on
947 an IP address range. (Normal iptables only matches on single addresses
948 with an optional mask.)
952 config NETFILTER_XT_MATCH_IPVS
953 tristate '"ipvs" match support'
955 depends on NETFILTER_ADVANCED
956 depends on NF_CONNTRACK
958 This option allows you to match against IPVS properties of a packet.
962 config NETFILTER_XT_MATCH_LENGTH
963 tristate '"length" match support'
964 depends on NETFILTER_ADVANCED
966 This option allows you to match the length of a packet against a
967 specific value or range of values.
969 To compile it as a module, choose M here. If unsure, say N.
971 config NETFILTER_XT_MATCH_LIMIT
972 tristate '"limit" match support'
973 depends on NETFILTER_ADVANCED
975 limit matching allows you to control the rate at which a rule can be
976 matched: mainly useful in combination with the LOG target ("LOG
977 target support", below) and to avoid some Denial of Service attacks.
979 To compile it as a module, choose M here. If unsure, say N.
981 config NETFILTER_XT_MATCH_MAC
982 tristate '"mac" address match support'
983 depends on NETFILTER_ADVANCED
985 MAC matching allows you to match packets based on the source
986 Ethernet address of the packet.
988 To compile it as a module, choose M here. If unsure, say N.
990 config NETFILTER_XT_MATCH_MARK
991 tristate '"mark" match support'
992 depends on NETFILTER_ADVANCED
993 select NETFILTER_XT_MARK
995 This is a backwards-compat option for the user's convenience
996 (e.g. when running oldconfig). It selects
997 CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
999 config NETFILTER_XT_MATCH_MULTIPORT
1000 tristate '"multiport" Multiple port match support'
1001 depends on NETFILTER_ADVANCED
1003 Multiport matching allows you to match TCP or UDP packets based on
1004 a series of source or destination ports: normally a rule can only
1005 match a single range of ports.
1007 To compile it as a module, choose M here. If unsure, say N.
1009 config NETFILTER_XT_MATCH_NFACCT
1010 tristate '"nfacct" match support'
1011 depends on NETFILTER_ADVANCED
1012 select NETFILTER_NETLINK_ACCT
1014 This option allows you to use the extended accounting through
1017 To compile it as a module, choose M here. If unsure, say N.
1019 config NETFILTER_XT_MATCH_OSF
1020 tristate '"osf" Passive OS fingerprint match'
1021 depends on NETFILTER_ADVANCED && NETFILTER_NETLINK
1023 This option selects the Passive OS Fingerprinting match module
1024 that allows to passively match the remote operating system by
1025 analyzing incoming TCP SYN packets.
1027 Rules and loading software can be downloaded from
1028 http://www.ioremap.net/projects/osf
1030 To compile it as a module, choose M here. If unsure, say N.
1032 config NETFILTER_XT_MATCH_OWNER
1033 tristate '"owner" match support'
1034 depends on NETFILTER_ADVANCED
1036 Socket owner matching allows you to match locally-generated packets
1037 based on who created the socket: the user or group. It is also
1038 possible to check whether a socket actually exists.
1040 config NETFILTER_XT_MATCH_POLICY
1041 tristate 'IPsec "policy" match support'
1043 default m if NETFILTER_ADVANCED=n
1045 Policy matching allows you to match packets based on the
1046 IPsec policy that was used during decapsulation/will
1047 be used during encapsulation.
1049 To compile it as a module, choose M here. If unsure, say N.
1051 config NETFILTER_XT_MATCH_PHYSDEV
1052 tristate '"physdev" match support'
1053 depends on BRIDGE && BRIDGE_NETFILTER
1054 depends on NETFILTER_ADVANCED
1056 Physdev packet matching matches against the physical bridge ports
1057 the IP packet arrived on or will leave by.
1059 To compile it as a module, choose M here. If unsure, say N.
1061 config NETFILTER_XT_MATCH_PKTTYPE
1062 tristate '"pkttype" packet type match support'
1063 depends on NETFILTER_ADVANCED
1065 Packet type matching allows you to match a packet by
1066 its "class", eg. BROADCAST, MULTICAST, ...
1069 iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG
1071 To compile it as a module, choose M here. If unsure, say N.
1073 config NETFILTER_XT_MATCH_QUOTA
1074 tristate '"quota" match support'
1075 depends on NETFILTER_ADVANCED
1077 This option adds a `quota' match, which allows to match on a
1080 If you want to compile it as a module, say M here and read
1081 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1083 config NETFILTER_XT_MATCH_RATEEST
1084 tristate '"rateest" match support'
1085 depends on NETFILTER_ADVANCED
1086 select NETFILTER_XT_TARGET_RATEEST
1088 This option adds a `rateest' match, which allows to match on the
1089 rate estimated by the RATEEST target.
1091 To compile it as a module, choose M here. If unsure, say N.
1093 config NETFILTER_XT_MATCH_REALM
1094 tristate '"realm" match support'
1095 depends on NETFILTER_ADVANCED
1096 select IP_ROUTE_CLASSID
1098 This option adds a `realm' match, which allows you to use the realm
1099 key from the routing subsystem inside iptables.
1101 This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option
1104 If you want to compile it as a module, say M here and read
1105 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1107 config NETFILTER_XT_MATCH_RECENT
1108 tristate '"recent" match support'
1109 depends on NETFILTER_ADVANCED
1111 This match is used for creating one or many lists of recently
1112 used addresses and then matching against that/those list(s).
1114 Short options are available by using 'iptables -m recent -h'
1115 Official Website: <http://snowman.net/projects/ipt_recent/>
1117 config NETFILTER_XT_MATCH_SCTP
1118 tristate '"sctp" protocol match support (EXPERIMENTAL)'
1119 depends on EXPERIMENTAL
1120 depends on NETFILTER_ADVANCED
1123 With this option enabled, you will be able to use the
1124 `sctp' match in order to match on SCTP source/destination ports
1125 and SCTP chunk types.
1127 If you want to compile it as a module, say M here and read
1128 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1130 config NETFILTER_XT_MATCH_SOCKET
1131 tristate '"socket" match support (EXPERIMENTAL)'
1132 depends on EXPERIMENTAL
1133 depends on NETFILTER_TPROXY
1134 depends on NETFILTER_XTABLES
1135 depends on NETFILTER_ADVANCED
1136 depends on !NF_CONNTRACK || NF_CONNTRACK
1137 select NF_DEFRAG_IPV4
1138 select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES
1140 This option adds a `socket' match, which can be used to match
1141 packets for which a TCP or UDP socket lookup finds a valid socket.
1142 It can be used in combination with the MARK target and policy
1143 routing to implement full featured non-locally bound sockets.
1145 To compile it as a module, choose M here. If unsure, say N.
1147 config NETFILTER_XT_MATCH_STATE
1148 tristate '"state" match support'
1149 depends on NF_CONNTRACK
1150 default m if NETFILTER_ADVANCED=n
1152 Connection state matching allows you to match packets based on their
1153 relationship to a tracked connection (ie. previous packets). This
1154 is a powerful tool for packet classification.
1156 To compile it as a module, choose M here. If unsure, say N.
1158 config NETFILTER_XT_MATCH_STATISTIC
1159 tristate '"statistic" match support'
1160 depends on NETFILTER_ADVANCED
1162 This option adds a `statistic' match, which allows you to match
1163 on packets periodically or randomly with a given percentage.
1165 To compile it as a module, choose M here. If unsure, say N.
1167 config NETFILTER_XT_MATCH_STRING
1168 tristate '"string" match support'
1169 depends on NETFILTER_ADVANCED
1171 select TEXTSEARCH_KMP
1172 select TEXTSEARCH_BM
1173 select TEXTSEARCH_FSM
1175 This option adds a `string' match, which allows you to look for
1176 pattern matchings in packets.
1178 To compile it as a module, choose M here. If unsure, say N.
1180 config NETFILTER_XT_MATCH_TCPMSS
1181 tristate '"tcpmss" match support'
1182 depends on NETFILTER_ADVANCED
1184 This option adds a `tcpmss' match, which allows you to examine the
1185 MSS value of TCP SYN packets, which control the maximum packet size
1186 for that connection.
1188 To compile it as a module, choose M here. If unsure, say N.
1190 config NETFILTER_XT_MATCH_TIME
1191 tristate '"time" match support'
1192 depends on NETFILTER_ADVANCED
1194 This option adds a "time" match, which allows you to match based on
1195 the packet arrival time (at the machine which netfilter is running)
1196 on) or departure time/date (for locally generated packets).
1198 If you say Y here, try `iptables -m time --help` for
1201 If you want to compile it as a module, say M here.
1204 config NETFILTER_XT_MATCH_U32
1205 tristate '"u32" match support'
1206 depends on NETFILTER_ADVANCED
1208 u32 allows you to extract quantities of up to 4 bytes from a packet,
1209 AND them with specified masks, shift them by specified amounts and
1210 test whether the results are in any of a set of specified ranges.
1211 The specification of what to extract is general enough to skip over
1212 headers with lengths stored in the packet, as in IP or TCP header
1215 Details and examples are in the kernel module source.
1217 endif # NETFILTER_XTABLES
1221 source "net/netfilter/ipset/Kconfig"
1223 source "net/netfilter/ipvs/Kconfig"