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 config NETFILTER_XTABLES
414 tristate "Netfilter Xtables support (required for ip_tables)"
415 default m if NETFILTER_ADVANCED=n
417 This is required if you intend to use any of ip_tables,
418 ip6_tables or arp_tables.
422 comment "Xtables combined modules"
424 config NETFILTER_XT_MARK
425 tristate 'nfmark target and match support'
426 default m if NETFILTER_ADVANCED=n
428 This option adds the "MARK" target and "mark" match.
430 Netfilter mark matching allows you to match packets based on the
431 "nfmark" value in the packet.
432 The target allows you to create rules in the "mangle" table which alter
433 the netfilter mark (nfmark) field associated with the packet.
435 Prior to routing, the nfmark can influence the routing method (see
436 "Use netfilter MARK value as routing key") and can also be used by
437 other subsystems to change their behavior.
439 config NETFILTER_XT_CONNMARK
440 tristate 'ctmark target and match support'
441 depends on NF_CONNTRACK
442 depends on NETFILTER_ADVANCED
443 select NF_CONNTRACK_MARK
445 This option adds the "CONNMARK" target and "connmark" match.
447 Netfilter allows you to store a mark value per connection (a.k.a.
448 ctmark), similarly to the packet mark (nfmark). Using this
449 target and match, you can set and match on this mark.
451 config NETFILTER_XT_SET
452 tristate 'set target and match support'
454 depends on NETFILTER_ADVANCED
456 This option adds the "SET" target and "set" match.
458 Using this target and match, you can add/delete and match
459 elements in the sets created by ipset(8).
461 To compile it as a module, choose M here. If unsure, say N.
463 # alphabetically ordered list of targets
465 comment "Xtables targets"
467 config NETFILTER_XT_TARGET_AUDIT
468 tristate "AUDIT target support"
470 depends on NETFILTER_ADVANCED
472 This option adds a 'AUDIT' target, which can be used to create
473 audit records for packets dropped/accepted.
475 To compileit as a module, choose M here. If unsure, say N.
477 config NETFILTER_XT_TARGET_CHECKSUM
478 tristate "CHECKSUM target support"
479 depends on IP_NF_MANGLE || IP6_NF_MANGLE
480 depends on NETFILTER_ADVANCED
482 This option adds a `CHECKSUM' target, which can be used in the iptables mangle
485 You can use this target to compute and fill in the checksum in
486 a packet that lacks a checksum. This is particularly useful,
487 if you need to work around old applications such as dhcp clients,
488 that do not work well with checksum offloads, but don't want to disable
489 checksum offload in your device.
491 To compile it as a module, choose M here. If unsure, say N.
493 config NETFILTER_XT_TARGET_CLASSIFY
494 tristate '"CLASSIFY" target support'
495 depends on NETFILTER_ADVANCED
497 This option adds a `CLASSIFY' target, which enables the user to set
498 the priority of a packet. Some qdiscs can use this value for
499 classification, among these are:
501 atm, cbq, dsmark, pfifo_fast, htb, prio
503 To compile it as a module, choose M here. If unsure, say N.
505 config NETFILTER_XT_TARGET_CONNMARK
506 tristate '"CONNMARK" target support'
507 depends on NF_CONNTRACK
508 depends on NETFILTER_ADVANCED
509 select NETFILTER_XT_CONNMARK
511 This is a backwards-compat option for the user's convenience
512 (e.g. when running oldconfig). It selects
513 CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
515 config NETFILTER_XT_TARGET_CONNSECMARK
516 tristate '"CONNSECMARK" target support'
517 depends on NF_CONNTRACK && NF_CONNTRACK_SECMARK
518 default m if NETFILTER_ADVANCED=n
520 The CONNSECMARK target copies security markings from packets
521 to connections, and restores security markings from connections
522 to packets (if the packets are not already marked). This would
523 normally be used in conjunction with the SECMARK target.
525 To compile it as a module, choose M here. If unsure, say N.
527 config NETFILTER_XT_TARGET_CT
528 tristate '"CT" target support'
529 depends on NF_CONNTRACK
530 depends on IP_NF_RAW || IP6_NF_RAW
531 depends on NETFILTER_ADVANCED
533 This options adds a `CT' target, which allows to specify initial
534 connection tracking parameters like events to be delivered and
535 the helper to be used.
537 To compile it as a module, choose M here. If unsure, say N.
539 config NETFILTER_XT_TARGET_DSCP
540 tristate '"DSCP" and "TOS" target support'
541 depends on IP_NF_MANGLE || IP6_NF_MANGLE
542 depends on NETFILTER_ADVANCED
544 This option adds a `DSCP' target, which allows you to manipulate
545 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
547 The DSCP field can have any value between 0x0 and 0x3f inclusive.
549 It also adds the "TOS" target, which allows you to create rules in
550 the "mangle" table which alter the Type Of Service field of an IPv4
551 or the Priority field of an IPv6 packet, prior to routing.
553 To compile it as a module, choose M here. If unsure, say N.
555 config NETFILTER_XT_TARGET_HL
556 tristate '"HL" hoplimit target support'
557 depends on IP_NF_MANGLE || IP6_NF_MANGLE
558 depends on NETFILTER_ADVANCED
560 This option adds the "HL" (for IPv6) and "TTL" (for IPv4)
561 targets, which enable the user to change the
562 hoplimit/time-to-live value of the IP header.
564 While it is safe to decrement the hoplimit/TTL value, the
565 modules also allow to increment and set the hoplimit value of
566 the header to arbitrary values. This is EXTREMELY DANGEROUS
567 since you can easily create immortal packets that loop
568 forever on the network.
570 config NETFILTER_XT_TARGET_HMARK
571 tristate '"HMARK" target support'
572 depends on (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
573 depends on NETFILTER_ADVANCED
575 This option adds the "HMARK" target.
577 The target allows you to create rules in the "raw" and "mangle" tables
578 which set the skbuff mark by means of hash calculation within a given
579 range. The nfmark can influence the routing method (see "Use netfilter
580 MARK value as routing key") and can also be used by other subsystems to
581 change their behaviour.
583 To compile it as a module, choose M here. If unsure, say N.
585 config NETFILTER_XT_TARGET_IDLETIMER
586 tristate "IDLETIMER target support"
587 depends on NETFILTER_ADVANCED
590 This option adds the `IDLETIMER' target. Each matching packet
591 resets the timer associated with label specified when the rule is
592 added. When the timer expires, it triggers a sysfs notification.
593 The remaining time for expiration can be read via sysfs.
595 To compile it as a module, choose M here. If unsure, say N.
597 config NETFILTER_XT_TARGET_LED
598 tristate '"LED" target support'
599 depends on LEDS_CLASS && LEDS_TRIGGERS
600 depends on NETFILTER_ADVANCED
602 This option adds a `LED' target, which allows you to blink LEDs in
603 response to particular packets passing through your machine.
605 This can be used to turn a spare LED into a network activity LED,
606 which only flashes in response to FTP transfers, for example. Or
607 you could have an LED which lights up for a minute or two every time
608 somebody connects to your machine via SSH.
610 You will need support for the "led" class to make this work.
612 To create an LED trigger for incoming SSH traffic:
613 iptables -A INPUT -p tcp --dport 22 -j LED --led-trigger-id ssh --led-delay 1000
615 Then attach the new trigger to an LED on your system:
616 echo netfilter-ssh > /sys/class/leds/<ledname>/trigger
618 For more information on the LEDs available on your system, see
619 Documentation/leds/leds-class.txt
621 config NETFILTER_XT_TARGET_LOG
622 tristate "LOG target support"
623 default m if NETFILTER_ADVANCED=n
625 This option adds a `LOG' target, which allows you to create rules in
626 any iptables table which records the packet header to the syslog.
628 To compile it as a module, choose M here. If unsure, say N.
630 config NETFILTER_XT_TARGET_MARK
631 tristate '"MARK" target support'
632 depends on NETFILTER_ADVANCED
633 select NETFILTER_XT_MARK
635 This is a backwards-compat option for the user's convenience
636 (e.g. when running oldconfig). It selects
637 CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
639 config NETFILTER_XT_TARGET_NETMAP
640 tristate '"NETMAP" target support'
643 NETMAP is an implementation of static 1:1 NAT mapping of network
644 addresses. It maps the network address part, while keeping the host
647 To compile it as a module, choose M here. If unsure, say N.
649 config NETFILTER_XT_TARGET_NFLOG
650 tristate '"NFLOG" target support'
651 default m if NETFILTER_ADVANCED=n
652 select NETFILTER_NETLINK_LOG
654 This option enables the NFLOG target, which allows to LOG
655 messages through nfnetlink_log.
657 To compile it as a module, choose M here. If unsure, say N.
659 config NETFILTER_XT_TARGET_NFQUEUE
660 tristate '"NFQUEUE" target Support'
661 depends on NETFILTER_ADVANCED
662 select NETFILTER_NETLINK_QUEUE
664 This target replaced the old obsolete QUEUE target.
666 As opposed to QUEUE, it supports 65535 different queues,
669 To compile it as a module, choose M here. If unsure, say N.
671 config NETFILTER_XT_TARGET_NOTRACK
672 tristate '"NOTRACK" target support (DEPRECATED)'
673 depends on NF_CONNTRACK
674 depends on IP_NF_RAW || IP6_NF_RAW
675 depends on NETFILTER_ADVANCED
676 select NETFILTER_XT_TARGET_CT
678 config NETFILTER_XT_TARGET_RATEEST
679 tristate '"RATEEST" target support'
680 depends on NETFILTER_ADVANCED
682 This option adds a `RATEEST' target, which allows to measure
683 rates similar to TC estimators. The `rateest' match can be
684 used to match on the measured rates.
686 To compile it as a module, choose M here. If unsure, say N.
688 config NETFILTER_XT_TARGET_REDIRECT
689 tristate "REDIRECT target support"
692 REDIRECT is a special case of NAT: all incoming connections are
693 mapped onto the incoming interface's address, causing the packets to
694 come to the local machine instead of passing through. This is
695 useful for transparent proxies.
697 To compile it as a module, choose M here. If unsure, say N.
699 config NETFILTER_XT_TARGET_TEE
700 tristate '"TEE" - packet cloning to alternate destination'
701 depends on NETFILTER_ADVANCED
702 depends on (IPV6 || IPV6=n)
703 depends on !NF_CONNTRACK || NF_CONNTRACK
705 This option adds a "TEE" target with which a packet can be cloned and
706 this clone be rerouted to another nexthop.
708 config NETFILTER_XT_TARGET_TPROXY
709 tristate '"TPROXY" target transparent proxying support'
710 depends on NETFILTER_XTABLES
711 depends on NETFILTER_ADVANCED
712 depends on IP_NF_MANGLE
713 select NF_DEFRAG_IPV4
714 select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES
716 This option adds a `TPROXY' target, which is somewhat similar to
717 REDIRECT. It can only be used in the mangle table and is useful
718 to redirect traffic to a transparent proxy. It does _not_ depend
719 on Netfilter connection tracking and NAT, unlike REDIRECT.
720 For it to work you will have to configure certain iptables rules
721 and use policy routing. For more information on how to set it up
722 see Documentation/networking/tproxy.txt.
724 To compile it as a module, choose M here. If unsure, say N.
726 config NETFILTER_XT_TARGET_TRACE
727 tristate '"TRACE" target support'
728 depends on IP_NF_RAW || IP6_NF_RAW
729 depends on NETFILTER_ADVANCED
731 The TRACE target allows you to mark packets so that the kernel
732 will log every rule which match the packets as those traverse
733 the tables, chains, rules.
735 If you want to compile it as a module, say M here and read
736 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
738 config NETFILTER_XT_TARGET_SECMARK
739 tristate '"SECMARK" target support'
740 depends on NETWORK_SECMARK
741 default m if NETFILTER_ADVANCED=n
743 The SECMARK target allows security marking of network
744 packets, for use with security subsystems.
746 To compile it as a module, choose M here. If unsure, say N.
748 config NETFILTER_XT_TARGET_TCPMSS
749 tristate '"TCPMSS" target support'
750 depends on (IPV6 || IPV6=n)
751 default m if NETFILTER_ADVANCED=n
753 This option adds a `TCPMSS' target, which allows you to alter the
754 MSS value of TCP SYN packets, to control the maximum size for that
755 connection (usually limiting it to your outgoing interface's MTU
758 This is used to overcome criminally braindead ISPs or servers which
759 block ICMP Fragmentation Needed packets. The symptoms of this
760 problem are that everything works fine from your Linux
761 firewall/router, but machines behind it can never exchange large
763 1) Web browsers connect, then hang with no data received.
764 2) Small mail works fine, but large emails hang.
765 3) ssh works fine, but scp hangs after initial handshaking.
767 Workaround: activate this option and add a rule to your firewall
770 iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
771 -j TCPMSS --clamp-mss-to-pmtu
773 To compile it as a module, choose M here. If unsure, say N.
775 config NETFILTER_XT_TARGET_TCPOPTSTRIP
776 tristate '"TCPOPTSTRIP" target support'
777 depends on IP_NF_MANGLE || IP6_NF_MANGLE
778 depends on NETFILTER_ADVANCED
780 This option adds a "TCPOPTSTRIP" target, which allows you to strip
781 TCP options from TCP packets.
783 # alphabetically ordered list of matches
785 comment "Xtables matches"
787 config NETFILTER_XT_MATCH_ADDRTYPE
788 tristate '"addrtype" address type match support'
789 depends on NETFILTER_ADVANCED
791 This option allows you to match what routing thinks of an address,
792 eg. UNICAST, LOCAL, BROADCAST, ...
794 If you want to compile it as a module, say M here and read
795 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
797 config NETFILTER_XT_MATCH_BPF
798 tristate '"bpf" match support'
799 depends on NETFILTER_ADVANCED
801 BPF matching applies a linux socket filter to each packet and
802 accepts those for which the filter returns non-zero.
804 To compile it as a module, choose M here. If unsure, say N.
806 config NETFILTER_XT_MATCH_CLUSTER
807 tristate '"cluster" match support'
808 depends on NF_CONNTRACK
809 depends on NETFILTER_ADVANCED
811 This option allows you to build work-load-sharing clusters of
812 network servers/stateful firewalls without having a dedicated
813 load-balancing router/server/switch. Basically, this match returns
814 true when the packet must be handled by this cluster node. Thus,
815 all nodes see all packets and this match decides which node handles
816 what packets. The work-load sharing algorithm is based on source
819 If you say Y or M here, try `iptables -m cluster --help` for
822 config NETFILTER_XT_MATCH_COMMENT
823 tristate '"comment" match support'
824 depends on NETFILTER_ADVANCED
826 This option adds a `comment' dummy-match, which allows you to put
827 comments in your iptables ruleset.
829 If you want to compile it as a module, say M here and read
830 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
832 config NETFILTER_XT_MATCH_CONNBYTES
833 tristate '"connbytes" per-connection counter match support'
834 depends on NF_CONNTRACK
835 depends on NETFILTER_ADVANCED
837 This option adds a `connbytes' match, which allows you to match the
838 number of bytes and/or packets for each direction within a connection.
840 If you want to compile it as a module, say M here and read
841 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
843 config NETFILTER_XT_MATCH_CONNLABEL
844 tristate '"connlabel" match support'
845 select NF_CONNTRACK_LABELS
846 depends on NF_CONNTRACK
847 depends on NETFILTER_ADVANCED
849 This match allows you to test and assign userspace-defined labels names
850 to a connection. The kernel only stores bit values - mapping
851 names to bits is done by userspace.
853 Unlike connmark, more than 32 flag bits may be assigned to a
854 connection simultaneously.
856 config NETFILTER_XT_MATCH_CONNLIMIT
857 tristate '"connlimit" match support"'
858 depends on NF_CONNTRACK
859 depends on NETFILTER_ADVANCED
861 This match allows you to match against the number of parallel
862 connections to a server per client IP address (or address block).
864 config NETFILTER_XT_MATCH_CONNMARK
865 tristate '"connmark" connection mark match support'
866 depends on NF_CONNTRACK
867 depends on NETFILTER_ADVANCED
868 select NETFILTER_XT_CONNMARK
870 This is a backwards-compat option for the user's convenience
871 (e.g. when running oldconfig). It selects
872 CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
874 config NETFILTER_XT_MATCH_CONNTRACK
875 tristate '"conntrack" connection tracking match support'
876 depends on NF_CONNTRACK
877 default m if NETFILTER_ADVANCED=n
879 This is a general conntrack match module, a superset of the state match.
881 It allows matching on additional conntrack information, which is
882 useful in complex configurations, such as NAT gateways with multiple
883 internet links or tunnels.
885 To compile it as a module, choose M here. If unsure, say N.
887 config NETFILTER_XT_MATCH_CPU
888 tristate '"cpu" match support'
889 depends on NETFILTER_ADVANCED
891 CPU matching allows you to match packets based on the CPU
892 currently handling the packet.
894 To compile it as a module, choose M here. If unsure, say N.
896 config NETFILTER_XT_MATCH_DCCP
897 tristate '"dccp" protocol match support'
898 depends on NETFILTER_ADVANCED
901 With this option enabled, you will be able to use the iptables
902 `dccp' match in order to match on DCCP source/destination ports
905 If you want to compile it as a module, say M here and read
906 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
908 config NETFILTER_XT_MATCH_DEVGROUP
909 tristate '"devgroup" match support'
910 depends on NETFILTER_ADVANCED
912 This options adds a `devgroup' match, which allows to match on the
913 device group a network device is assigned to.
915 To compile it as a module, choose M here. If unsure, say N.
917 config NETFILTER_XT_MATCH_DSCP
918 tristate '"dscp" and "tos" match support'
919 depends on NETFILTER_ADVANCED
921 This option adds a `DSCP' match, which allows you to match against
922 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
924 The DSCP field can have any value between 0x0 and 0x3f inclusive.
926 It will also add a "tos" match, which allows you to match packets
927 based on the Type Of Service fields of the IPv4 packet (which share
928 the same bits as DSCP).
930 To compile it as a module, choose M here. If unsure, say N.
932 config NETFILTER_XT_MATCH_ECN
933 tristate '"ecn" match support'
934 depends on NETFILTER_ADVANCED
936 This option adds an "ECN" match, which allows you to match against
937 the IPv4 and TCP header ECN fields.
939 To compile it as a module, choose M here. If unsure, say N.
941 config NETFILTER_XT_MATCH_ESP
942 tristate '"esp" match support'
943 depends on NETFILTER_ADVANCED
945 This match extension allows you to match a range of SPIs
946 inside ESP header of IPSec packets.
948 To compile it as a module, choose M here. If unsure, say N.
950 config NETFILTER_XT_MATCH_HASHLIMIT
951 tristate '"hashlimit" match support'
952 depends on (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
953 depends on NETFILTER_ADVANCED
955 This option adds a `hashlimit' match.
957 As opposed to `limit', this match dynamically creates a hash table
958 of limit buckets, based on your selection of source/destination
959 addresses and/or ports.
961 It enables you to express policies like `10kpps for any given
962 destination address' or `500pps from any given source address'
965 config NETFILTER_XT_MATCH_HELPER
966 tristate '"helper" match support'
967 depends on NF_CONNTRACK
968 depends on NETFILTER_ADVANCED
970 Helper matching allows you to match packets in dynamic connections
971 tracked by a conntrack-helper, ie. ip_conntrack_ftp
973 To compile it as a module, choose M here. If unsure, say Y.
975 config NETFILTER_XT_MATCH_HL
976 tristate '"hl" hoplimit/TTL match support'
977 depends on NETFILTER_ADVANCED
979 HL matching allows you to match packets based on the hoplimit
980 in the IPv6 header, or the time-to-live field in the IPv4
981 header of the packet.
983 config NETFILTER_XT_MATCH_IPRANGE
984 tristate '"iprange" address range match support'
985 depends on NETFILTER_ADVANCED
987 This option adds a "iprange" match, which allows you to match based on
988 an IP address range. (Normal iptables only matches on single addresses
989 with an optional mask.)
993 config NETFILTER_XT_MATCH_IPVS
994 tristate '"ipvs" match support'
996 depends on NETFILTER_ADVANCED
997 depends on NF_CONNTRACK
999 This option allows you to match against IPVS properties of a packet.
1003 config NETFILTER_XT_MATCH_LENGTH
1004 tristate '"length" match support'
1005 depends on NETFILTER_ADVANCED
1007 This option allows you to match the length of a packet against a
1008 specific value or range of values.
1010 To compile it as a module, choose M here. If unsure, say N.
1012 config NETFILTER_XT_MATCH_LIMIT
1013 tristate '"limit" match support'
1014 depends on NETFILTER_ADVANCED
1016 limit matching allows you to control the rate at which a rule can be
1017 matched: mainly useful in combination with the LOG target ("LOG
1018 target support", below) and to avoid some Denial of Service attacks.
1020 To compile it as a module, choose M here. If unsure, say N.
1022 config NETFILTER_XT_MATCH_MAC
1023 tristate '"mac" address match support'
1024 depends on NETFILTER_ADVANCED
1026 MAC matching allows you to match packets based on the source
1027 Ethernet address of the packet.
1029 To compile it as a module, choose M here. If unsure, say N.
1031 config NETFILTER_XT_MATCH_MARK
1032 tristate '"mark" match support'
1033 depends on NETFILTER_ADVANCED
1034 select NETFILTER_XT_MARK
1036 This is a backwards-compat option for the user's convenience
1037 (e.g. when running oldconfig). It selects
1038 CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
1040 config NETFILTER_XT_MATCH_MULTIPORT
1041 tristate '"multiport" Multiple port match support'
1042 depends on NETFILTER_ADVANCED
1044 Multiport matching allows you to match TCP or UDP packets based on
1045 a series of source or destination ports: normally a rule can only
1046 match a single range of ports.
1048 To compile it as a module, choose M here. If unsure, say N.
1050 config NETFILTER_XT_MATCH_NFACCT
1051 tristate '"nfacct" match support'
1052 depends on NETFILTER_ADVANCED
1053 select NETFILTER_NETLINK_ACCT
1055 This option allows you to use the extended accounting through
1058 To compile it as a module, choose M here. If unsure, say N.
1060 config NETFILTER_XT_MATCH_OSF
1061 tristate '"osf" Passive OS fingerprint match'
1062 depends on NETFILTER_ADVANCED && NETFILTER_NETLINK
1064 This option selects the Passive OS Fingerprinting match module
1065 that allows to passively match the remote operating system by
1066 analyzing incoming TCP SYN packets.
1068 Rules and loading software can be downloaded from
1069 http://www.ioremap.net/projects/osf
1071 To compile it as a module, choose M here. If unsure, say N.
1073 config NETFILTER_XT_MATCH_OWNER
1074 tristate '"owner" match support'
1075 depends on NETFILTER_ADVANCED
1077 Socket owner matching allows you to match locally-generated packets
1078 based on who created the socket: the user or group. It is also
1079 possible to check whether a socket actually exists.
1081 config NETFILTER_XT_MATCH_POLICY
1082 tristate 'IPsec "policy" match support'
1084 default m if NETFILTER_ADVANCED=n
1086 Policy matching allows you to match packets based on the
1087 IPsec policy that was used during decapsulation/will
1088 be used during encapsulation.
1090 To compile it as a module, choose M here. If unsure, say N.
1092 config NETFILTER_XT_MATCH_PHYSDEV
1093 tristate '"physdev" match support'
1094 depends on BRIDGE && BRIDGE_NETFILTER
1095 depends on NETFILTER_ADVANCED
1097 Physdev packet matching matches against the physical bridge ports
1098 the IP packet arrived on or will leave by.
1100 To compile it as a module, choose M here. If unsure, say N.
1102 config NETFILTER_XT_MATCH_PKTTYPE
1103 tristate '"pkttype" packet type match support'
1104 depends on NETFILTER_ADVANCED
1106 Packet type matching allows you to match a packet by
1107 its "class", eg. BROADCAST, MULTICAST, ...
1110 iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG
1112 To compile it as a module, choose M here. If unsure, say N.
1114 config NETFILTER_XT_MATCH_QUOTA
1115 tristate '"quota" match support'
1116 depends on NETFILTER_ADVANCED
1118 This option adds a `quota' match, which allows to match on a
1121 If you want to compile it as a module, say M here and read
1122 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1124 config NETFILTER_XT_MATCH_RATEEST
1125 tristate '"rateest" match support'
1126 depends on NETFILTER_ADVANCED
1127 select NETFILTER_XT_TARGET_RATEEST
1129 This option adds a `rateest' match, which allows to match on the
1130 rate estimated by the RATEEST target.
1132 To compile it as a module, choose M here. If unsure, say N.
1134 config NETFILTER_XT_MATCH_REALM
1135 tristate '"realm" match support'
1136 depends on NETFILTER_ADVANCED
1137 select IP_ROUTE_CLASSID
1139 This option adds a `realm' match, which allows you to use the realm
1140 key from the routing subsystem inside iptables.
1142 This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option
1145 If you want to compile it as a module, say M here and read
1146 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1148 config NETFILTER_XT_MATCH_RECENT
1149 tristate '"recent" match support'
1150 depends on NETFILTER_ADVANCED
1152 This match is used for creating one or many lists of recently
1153 used addresses and then matching against that/those list(s).
1155 Short options are available by using 'iptables -m recent -h'
1156 Official Website: <http://snowman.net/projects/ipt_recent/>
1158 config NETFILTER_XT_MATCH_SCTP
1159 tristate '"sctp" protocol match support'
1160 depends on NETFILTER_ADVANCED
1163 With this option enabled, you will be able to use the
1164 `sctp' match in order to match on SCTP source/destination ports
1165 and SCTP chunk types.
1167 If you want to compile it as a module, say M here and read
1168 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1170 config NETFILTER_XT_MATCH_SOCKET
1171 tristate '"socket" match support'
1172 depends on NETFILTER_XTABLES
1173 depends on NETFILTER_ADVANCED
1174 depends on !NF_CONNTRACK || NF_CONNTRACK
1175 select NF_DEFRAG_IPV4
1176 select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES
1178 This option adds a `socket' match, which can be used to match
1179 packets for which a TCP or UDP socket lookup finds a valid socket.
1180 It can be used in combination with the MARK target and policy
1181 routing to implement full featured non-locally bound sockets.
1183 To compile it as a module, choose M here. If unsure, say N.
1185 config NETFILTER_XT_MATCH_STATE
1186 tristate '"state" match support'
1187 depends on NF_CONNTRACK
1188 default m if NETFILTER_ADVANCED=n
1190 Connection state matching allows you to match packets based on their
1191 relationship to a tracked connection (ie. previous packets). This
1192 is a powerful tool for packet classification.
1194 To compile it as a module, choose M here. If unsure, say N.
1196 config NETFILTER_XT_MATCH_STATISTIC
1197 tristate '"statistic" match support'
1198 depends on NETFILTER_ADVANCED
1200 This option adds a `statistic' match, which allows you to match
1201 on packets periodically or randomly with a given percentage.
1203 To compile it as a module, choose M here. If unsure, say N.
1205 config NETFILTER_XT_MATCH_STRING
1206 tristate '"string" match support'
1207 depends on NETFILTER_ADVANCED
1209 select TEXTSEARCH_KMP
1210 select TEXTSEARCH_BM
1211 select TEXTSEARCH_FSM
1213 This option adds a `string' match, which allows you to look for
1214 pattern matchings in packets.
1216 To compile it as a module, choose M here. If unsure, say N.
1218 config NETFILTER_XT_MATCH_TCPMSS
1219 tristate '"tcpmss" match support'
1220 depends on NETFILTER_ADVANCED
1222 This option adds a `tcpmss' match, which allows you to examine the
1223 MSS value of TCP SYN packets, which control the maximum packet size
1224 for that connection.
1226 To compile it as a module, choose M here. If unsure, say N.
1228 config NETFILTER_XT_MATCH_TIME
1229 tristate '"time" match support'
1230 depends on NETFILTER_ADVANCED
1232 This option adds a "time" match, which allows you to match based on
1233 the packet arrival time (at the machine which netfilter is running)
1234 on) or departure time/date (for locally generated packets).
1236 If you say Y here, try `iptables -m time --help` for
1239 If you want to compile it as a module, say M here.
1242 config NETFILTER_XT_MATCH_U32
1243 tristate '"u32" match support'
1244 depends on NETFILTER_ADVANCED
1246 u32 allows you to extract quantities of up to 4 bytes from a packet,
1247 AND them with specified masks, shift them by specified amounts and
1248 test whether the results are in any of a set of specified ranges.
1249 The specification of what to extract is general enough to skip over
1250 headers with lengths stored in the packet, as in IP or TCP header
1253 Details and examples are in the kernel module source.
1255 endif # NETFILTER_XTABLES
1259 source "net/netfilter/ipset/Kconfig"
1261 source "net/netfilter/ipvs/Kconfig"