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 depends on NF_CONNTRACK && NF_NAT
396 default NF_NAT && NF_CONNTRACK_IRC
400 depends on NF_CONNTRACK && NF_NAT
401 default NF_NAT && NF_CONNTRACK_SIP
405 depends on NF_CONNTRACK && NF_NAT
406 default NF_NAT && NF_CONNTRACK_TFTP
410 # transparent proxy support
411 config NETFILTER_TPROXY
412 tristate "Transparent proxying support (EXPERIMENTAL)"
413 depends on EXPERIMENTAL
414 depends on IP_NF_MANGLE
415 depends on NETFILTER_ADVANCED
417 This option enables transparent proxying support, that is,
418 support for handling non-locally bound IPv4 TCP and UDP sockets.
419 For it to work you will have to configure certain iptables rules
420 and use policy routing. For more information on how to set it up
421 see Documentation/networking/tproxy.txt.
423 To compile it as a module, choose M here. If unsure, say N.
425 config NETFILTER_XTABLES
426 tristate "Netfilter Xtables support (required for ip_tables)"
427 default m if NETFILTER_ADVANCED=n
429 This is required if you intend to use any of ip_tables,
430 ip6_tables or arp_tables.
434 comment "Xtables combined modules"
436 config NETFILTER_XT_MARK
437 tristate 'nfmark target and match support'
438 default m if NETFILTER_ADVANCED=n
440 This option adds the "MARK" target and "mark" match.
442 Netfilter mark matching allows you to match packets based on the
443 "nfmark" value in the packet.
444 The target allows you to create rules in the "mangle" table which alter
445 the netfilter mark (nfmark) field associated with the packet.
447 Prior to routing, the nfmark can influence the routing method (see
448 "Use netfilter MARK value as routing key") and can also be used by
449 other subsystems to change their behavior.
451 config NETFILTER_XT_CONNMARK
452 tristate 'ctmark target and match support'
453 depends on NF_CONNTRACK
454 depends on NETFILTER_ADVANCED
455 select NF_CONNTRACK_MARK
457 This option adds the "CONNMARK" target and "connmark" match.
459 Netfilter allows you to store a mark value per connection (a.k.a.
460 ctmark), similarly to the packet mark (nfmark). Using this
461 target and match, you can set and match on this mark.
463 config NETFILTER_XT_SET
464 tristate 'set target and match support'
466 depends on NETFILTER_ADVANCED
468 This option adds the "SET" target and "set" match.
470 Using this target and match, you can add/delete and match
471 elements in the sets created by ipset(8).
473 To compile it as a module, choose M here. If unsure, say N.
475 # alphabetically ordered list of targets
477 comment "Xtables targets"
479 config NETFILTER_XT_TARGET_AUDIT
480 tristate "AUDIT target support"
482 depends on NETFILTER_ADVANCED
484 This option adds a 'AUDIT' target, which can be used to create
485 audit records for packets dropped/accepted.
487 To compileit as a module, choose M here. If unsure, say N.
489 config NETFILTER_XT_TARGET_CHECKSUM
490 tristate "CHECKSUM target support"
491 depends on IP_NF_MANGLE || IP6_NF_MANGLE
492 depends on NETFILTER_ADVANCED
494 This option adds a `CHECKSUM' target, which can be used in the iptables mangle
497 You can use this target to compute and fill in the checksum in
498 a packet that lacks a checksum. This is particularly useful,
499 if you need to work around old applications such as dhcp clients,
500 that do not work well with checksum offloads, but don't want to disable
501 checksum offload in your device.
503 To compile it as a module, choose M here. If unsure, say N.
505 config NETFILTER_XT_TARGET_CLASSIFY
506 tristate '"CLASSIFY" target support'
507 depends on NETFILTER_ADVANCED
509 This option adds a `CLASSIFY' target, which enables the user to set
510 the priority of a packet. Some qdiscs can use this value for
511 classification, among these are:
513 atm, cbq, dsmark, pfifo_fast, htb, prio
515 To compile it as a module, choose M here. If unsure, say N.
517 config NETFILTER_XT_TARGET_CONNMARK
518 tristate '"CONNMARK" target support'
519 depends on NF_CONNTRACK
520 depends on NETFILTER_ADVANCED
521 select NETFILTER_XT_CONNMARK
523 This is a backwards-compat option for the user's convenience
524 (e.g. when running oldconfig). It selects
525 CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
527 config NETFILTER_XT_TARGET_CONNSECMARK
528 tristate '"CONNSECMARK" target support'
529 depends on NF_CONNTRACK && NF_CONNTRACK_SECMARK
530 default m if NETFILTER_ADVANCED=n
532 The CONNSECMARK target copies security markings from packets
533 to connections, and restores security markings from connections
534 to packets (if the packets are not already marked). This would
535 normally be used in conjunction with the SECMARK target.
537 To compile it as a module, choose M here. If unsure, say N.
539 config NETFILTER_XT_TARGET_CT
540 tristate '"CT" target support'
541 depends on NF_CONNTRACK
542 depends on IP_NF_RAW || IP6_NF_RAW
543 depends on NETFILTER_ADVANCED
545 This options adds a `CT' target, which allows to specify initial
546 connection tracking parameters like events to be delivered and
547 the helper to be used.
549 To compile it as a module, choose M here. If unsure, say N.
551 config NETFILTER_XT_TARGET_DSCP
552 tristate '"DSCP" and "TOS" target support'
553 depends on IP_NF_MANGLE || IP6_NF_MANGLE
554 depends on NETFILTER_ADVANCED
556 This option adds a `DSCP' target, which allows you to manipulate
557 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
559 The DSCP field can have any value between 0x0 and 0x3f inclusive.
561 It also adds the "TOS" target, which allows you to create rules in
562 the "mangle" table which alter the Type Of Service field of an IPv4
563 or the Priority field of an IPv6 packet, prior to routing.
565 To compile it as a module, choose M here. If unsure, say N.
567 config NETFILTER_XT_TARGET_HL
568 tristate '"HL" hoplimit target support'
569 depends on IP_NF_MANGLE || IP6_NF_MANGLE
570 depends on NETFILTER_ADVANCED
572 This option adds the "HL" (for IPv6) and "TTL" (for IPv4)
573 targets, which enable the user to change the
574 hoplimit/time-to-live value of the IP header.
576 While it is safe to decrement the hoplimit/TTL value, the
577 modules also allow to increment and set the hoplimit value of
578 the header to arbitrary values. This is EXTREMELY DANGEROUS
579 since you can easily create immortal packets that loop
580 forever on the network.
582 config NETFILTER_XT_TARGET_HMARK
583 tristate '"HMARK" target support'
584 depends on (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
585 depends on NETFILTER_ADVANCED
587 This option adds the "HMARK" target.
589 The target allows you to create rules in the "raw" and "mangle" tables
590 which set the skbuff mark by means of hash calculation within a given
591 range. The nfmark can influence the routing method (see "Use netfilter
592 MARK value as routing key") and can also be used by other subsystems to
593 change their behaviour.
595 To compile it as a module, choose M here. If unsure, say N.
597 config NETFILTER_XT_TARGET_IDLETIMER
598 tristate "IDLETIMER target support"
599 depends on NETFILTER_ADVANCED
602 This option adds the `IDLETIMER' target. Each matching packet
603 resets the timer associated with label specified when the rule is
604 added. When the timer expires, it triggers a sysfs notification.
605 The remaining time for expiration can be read via sysfs.
607 To compile it as a module, choose M here. If unsure, say N.
609 config NETFILTER_XT_TARGET_LED
610 tristate '"LED" target support'
611 depends on LEDS_CLASS && LEDS_TRIGGERS
612 depends on NETFILTER_ADVANCED
614 This option adds a `LED' target, which allows you to blink LEDs in
615 response to particular packets passing through your machine.
617 This can be used to turn a spare LED into a network activity LED,
618 which only flashes in response to FTP transfers, for example. Or
619 you could have an LED which lights up for a minute or two every time
620 somebody connects to your machine via SSH.
622 You will need support for the "led" class to make this work.
624 To create an LED trigger for incoming SSH traffic:
625 iptables -A INPUT -p tcp --dport 22 -j LED --led-trigger-id ssh --led-delay 1000
627 Then attach the new trigger to an LED on your system:
628 echo netfilter-ssh > /sys/class/leds/<ledname>/trigger
630 For more information on the LEDs available on your system, see
631 Documentation/leds/leds-class.txt
633 config NETFILTER_XT_TARGET_LOG
634 tristate "LOG target support"
635 default m if NETFILTER_ADVANCED=n
637 This option adds a `LOG' target, which allows you to create rules in
638 any iptables table which records the packet header to the syslog.
640 To compile it as a module, choose M here. If unsure, say N.
642 config NETFILTER_XT_TARGET_MARK
643 tristate '"MARK" target support'
644 depends on NETFILTER_ADVANCED
645 select NETFILTER_XT_MARK
647 This is a backwards-compat option for the user's convenience
648 (e.g. when running oldconfig). It selects
649 CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
651 config NETFILTER_XT_TARGET_NETMAP
652 tristate '"NETMAP" target support'
655 NETMAP is an implementation of static 1:1 NAT mapping of network
656 addresses. It maps the network address part, while keeping the host
659 To compile it as a module, choose M here. If unsure, say N.
661 config NETFILTER_XT_TARGET_NFLOG
662 tristate '"NFLOG" target support'
663 default m if NETFILTER_ADVANCED=n
664 select NETFILTER_NETLINK_LOG
666 This option enables the NFLOG target, which allows to LOG
667 messages through nfnetlink_log.
669 To compile it as a module, choose M here. If unsure, say N.
671 config NETFILTER_XT_TARGET_NFQUEUE
672 tristate '"NFQUEUE" target Support'
673 depends on NETFILTER_ADVANCED
674 select NETFILTER_NETLINK_QUEUE
676 This target replaced the old obsolete QUEUE target.
678 As opposed to QUEUE, it supports 65535 different queues,
681 To compile it as a module, choose M here. If unsure, say N.
683 config NETFILTER_XT_TARGET_RATEEST
684 tristate '"RATEEST" target support'
685 depends on NETFILTER_ADVANCED
687 This option adds a `RATEEST' target, which allows to measure
688 rates similar to TC estimators. The `rateest' match can be
689 used to match on the measured rates.
691 To compile it as a module, choose M here. If unsure, say N.
693 config NETFILTER_XT_TARGET_TEE
694 tristate '"TEE" - packet cloning to alternate destination'
695 depends on NETFILTER_ADVANCED
696 depends on (IPV6 || IPV6=n)
697 depends on !NF_CONNTRACK || NF_CONNTRACK
699 This option adds a "TEE" target with which a packet can be cloned and
700 this clone be rerouted to another nexthop.
702 config NETFILTER_XT_TARGET_TPROXY
703 tristate '"TPROXY" target support (EXPERIMENTAL)'
704 depends on EXPERIMENTAL
705 depends on NETFILTER_TPROXY
706 depends on NETFILTER_XTABLES
707 depends on NETFILTER_ADVANCED
708 select NF_DEFRAG_IPV4
709 select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES
711 This option adds a `TPROXY' target, which is somewhat similar to
712 REDIRECT. It can only be used in the mangle table and is useful
713 to redirect traffic to a transparent proxy. It does _not_ depend
714 on Netfilter connection tracking and NAT, unlike REDIRECT.
716 To compile it as a module, choose M here. If unsure, say N.
718 config NETFILTER_XT_TARGET_TRACE
719 tristate '"TRACE" target support'
720 depends on IP_NF_RAW || IP6_NF_RAW
721 depends on NETFILTER_ADVANCED
723 The TRACE target allows you to mark packets so that the kernel
724 will log every rule which match the packets as those traverse
725 the tables, chains, rules.
727 If you want to compile it as a module, say M here and read
728 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
730 config NETFILTER_XT_TARGET_SECMARK
731 tristate '"SECMARK" target support'
732 depends on NETWORK_SECMARK
733 default m if NETFILTER_ADVANCED=n
735 The SECMARK target allows security marking of network
736 packets, for use with security subsystems.
738 To compile it as a module, choose M here. If unsure, say N.
740 config NETFILTER_XT_TARGET_TCPMSS
741 tristate '"TCPMSS" target support'
742 depends on (IPV6 || IPV6=n)
743 default m if NETFILTER_ADVANCED=n
745 This option adds a `TCPMSS' target, which allows you to alter the
746 MSS value of TCP SYN packets, to control the maximum size for that
747 connection (usually limiting it to your outgoing interface's MTU
750 This is used to overcome criminally braindead ISPs or servers which
751 block ICMP Fragmentation Needed packets. The symptoms of this
752 problem are that everything works fine from your Linux
753 firewall/router, but machines behind it can never exchange large
755 1) Web browsers connect, then hang with no data received.
756 2) Small mail works fine, but large emails hang.
757 3) ssh works fine, but scp hangs after initial handshaking.
759 Workaround: activate this option and add a rule to your firewall
762 iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
763 -j TCPMSS --clamp-mss-to-pmtu
765 To compile it as a module, choose M here. If unsure, say N.
767 config NETFILTER_XT_TARGET_TCPOPTSTRIP
768 tristate '"TCPOPTSTRIP" target support (EXPERIMENTAL)'
769 depends on EXPERIMENTAL
770 depends on IP_NF_MANGLE || IP6_NF_MANGLE
771 depends on NETFILTER_ADVANCED
773 This option adds a "TCPOPTSTRIP" target, which allows you to strip
774 TCP options from TCP packets.
776 # alphabetically ordered list of matches
778 comment "Xtables matches"
780 config NETFILTER_XT_MATCH_ADDRTYPE
781 tristate '"addrtype" address type match support'
782 depends on NETFILTER_ADVANCED
784 This option allows you to match what routing thinks of an address,
785 eg. UNICAST, LOCAL, BROADCAST, ...
787 If you want to compile it as a module, say M here and read
788 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
790 config NETFILTER_XT_MATCH_CLUSTER
791 tristate '"cluster" match support'
792 depends on NF_CONNTRACK
793 depends on NETFILTER_ADVANCED
795 This option allows you to build work-load-sharing clusters of
796 network servers/stateful firewalls without having a dedicated
797 load-balancing router/server/switch. Basically, this match returns
798 true when the packet must be handled by this cluster node. Thus,
799 all nodes see all packets and this match decides which node handles
800 what packets. The work-load sharing algorithm is based on source
803 If you say Y or M here, try `iptables -m cluster --help` for
806 config NETFILTER_XT_MATCH_COMMENT
807 tristate '"comment" match support'
808 depends on NETFILTER_ADVANCED
810 This option adds a `comment' dummy-match, which allows you to put
811 comments in your iptables ruleset.
813 If you want to compile it as a module, say M here and read
814 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
816 config NETFILTER_XT_MATCH_CONNBYTES
817 tristate '"connbytes" per-connection counter match support'
818 depends on NF_CONNTRACK
819 depends on NETFILTER_ADVANCED
821 This option adds a `connbytes' match, which allows you to match the
822 number of bytes and/or packets for each direction within a connection.
824 If you want to compile it as a module, say M here and read
825 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
827 config NETFILTER_XT_MATCH_CONNLIMIT
828 tristate '"connlimit" match support"'
829 depends on NF_CONNTRACK
830 depends on NETFILTER_ADVANCED
832 This match allows you to match against the number of parallel
833 connections to a server per client IP address (or address block).
835 config NETFILTER_XT_MATCH_CONNMARK
836 tristate '"connmark" connection mark match support'
837 depends on NF_CONNTRACK
838 depends on NETFILTER_ADVANCED
839 select NETFILTER_XT_CONNMARK
841 This is a backwards-compat option for the user's convenience
842 (e.g. when running oldconfig). It selects
843 CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
845 config NETFILTER_XT_MATCH_CONNTRACK
846 tristate '"conntrack" connection tracking match support'
847 depends on NF_CONNTRACK
848 default m if NETFILTER_ADVANCED=n
850 This is a general conntrack match module, a superset of the state match.
852 It allows matching on additional conntrack information, which is
853 useful in complex configurations, such as NAT gateways with multiple
854 internet links or tunnels.
856 To compile it as a module, choose M here. If unsure, say N.
858 config NETFILTER_XT_MATCH_CPU
859 tristate '"cpu" match support'
860 depends on NETFILTER_ADVANCED
862 CPU matching allows you to match packets based on the CPU
863 currently handling the packet.
865 To compile it as a module, choose M here. If unsure, say N.
867 config NETFILTER_XT_MATCH_DCCP
868 tristate '"dccp" protocol match support'
869 depends on NETFILTER_ADVANCED
872 With this option enabled, you will be able to use the iptables
873 `dccp' match in order to match on DCCP source/destination ports
876 If you want to compile it as a module, say M here and read
877 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
879 config NETFILTER_XT_MATCH_DEVGROUP
880 tristate '"devgroup" match support'
881 depends on NETFILTER_ADVANCED
883 This options adds a `devgroup' match, which allows to match on the
884 device group a network device is assigned to.
886 To compile it as a module, choose M here. If unsure, say N.
888 config NETFILTER_XT_MATCH_DSCP
889 tristate '"dscp" and "tos" match support'
890 depends on NETFILTER_ADVANCED
892 This option adds a `DSCP' match, which allows you to match against
893 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
895 The DSCP field can have any value between 0x0 and 0x3f inclusive.
897 It will also add a "tos" match, which allows you to match packets
898 based on the Type Of Service fields of the IPv4 packet (which share
899 the same bits as DSCP).
901 To compile it as a module, choose M here. If unsure, say N.
903 config NETFILTER_XT_MATCH_ECN
904 tristate '"ecn" match support'
905 depends on NETFILTER_ADVANCED
907 This option adds an "ECN" match, which allows you to match against
908 the IPv4 and TCP header ECN fields.
910 To compile it as a module, choose M here. If unsure, say N.
912 config NETFILTER_XT_MATCH_ESP
913 tristate '"esp" match support'
914 depends on NETFILTER_ADVANCED
916 This match extension allows you to match a range of SPIs
917 inside ESP header of IPSec packets.
919 To compile it as a module, choose M here. If unsure, say N.
921 config NETFILTER_XT_MATCH_HASHLIMIT
922 tristate '"hashlimit" match support'
923 depends on (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
924 depends on NETFILTER_ADVANCED
926 This option adds a `hashlimit' match.
928 As opposed to `limit', this match dynamically creates a hash table
929 of limit buckets, based on your selection of source/destination
930 addresses and/or ports.
932 It enables you to express policies like `10kpps for any given
933 destination address' or `500pps from any given source address'
936 config NETFILTER_XT_MATCH_HELPER
937 tristate '"helper" match support'
938 depends on NF_CONNTRACK
939 depends on NETFILTER_ADVANCED
941 Helper matching allows you to match packets in dynamic connections
942 tracked by a conntrack-helper, ie. ip_conntrack_ftp
944 To compile it as a module, choose M here. If unsure, say Y.
946 config NETFILTER_XT_MATCH_HL
947 tristate '"hl" hoplimit/TTL match support'
948 depends on NETFILTER_ADVANCED
950 HL matching allows you to match packets based on the hoplimit
951 in the IPv6 header, or the time-to-live field in the IPv4
952 header of the packet.
954 config NETFILTER_XT_MATCH_IPRANGE
955 tristate '"iprange" address range match support'
956 depends on NETFILTER_ADVANCED
958 This option adds a "iprange" match, which allows you to match based on
959 an IP address range. (Normal iptables only matches on single addresses
960 with an optional mask.)
964 config NETFILTER_XT_MATCH_IPVS
965 tristate '"ipvs" match support'
967 depends on NETFILTER_ADVANCED
968 depends on NF_CONNTRACK
970 This option allows you to match against IPVS properties of a packet.
974 config NETFILTER_XT_MATCH_LENGTH
975 tristate '"length" match support'
976 depends on NETFILTER_ADVANCED
978 This option allows you to match the length of a packet against a
979 specific value or range of values.
981 To compile it as a module, choose M here. If unsure, say N.
983 config NETFILTER_XT_MATCH_LIMIT
984 tristate '"limit" match support'
985 depends on NETFILTER_ADVANCED
987 limit matching allows you to control the rate at which a rule can be
988 matched: mainly useful in combination with the LOG target ("LOG
989 target support", below) and to avoid some Denial of Service attacks.
991 To compile it as a module, choose M here. If unsure, say N.
993 config NETFILTER_XT_MATCH_MAC
994 tristate '"mac" address match support'
995 depends on NETFILTER_ADVANCED
997 MAC matching allows you to match packets based on the source
998 Ethernet address of the packet.
1000 To compile it as a module, choose M here. If unsure, say N.
1002 config NETFILTER_XT_MATCH_MARK
1003 tristate '"mark" match support'
1004 depends on NETFILTER_ADVANCED
1005 select NETFILTER_XT_MARK
1007 This is a backwards-compat option for the user's convenience
1008 (e.g. when running oldconfig). It selects
1009 CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
1011 config NETFILTER_XT_MATCH_MULTIPORT
1012 tristate '"multiport" Multiple port match support'
1013 depends on NETFILTER_ADVANCED
1015 Multiport matching allows you to match TCP or UDP packets based on
1016 a series of source or destination ports: normally a rule can only
1017 match a single range of ports.
1019 To compile it as a module, choose M here. If unsure, say N.
1021 config NETFILTER_XT_MATCH_NFACCT
1022 tristate '"nfacct" match support'
1023 depends on NETFILTER_ADVANCED
1024 select NETFILTER_NETLINK_ACCT
1026 This option allows you to use the extended accounting through
1029 To compile it as a module, choose M here. If unsure, say N.
1031 config NETFILTER_XT_MATCH_OSF
1032 tristate '"osf" Passive OS fingerprint match'
1033 depends on NETFILTER_ADVANCED && NETFILTER_NETLINK
1035 This option selects the Passive OS Fingerprinting match module
1036 that allows to passively match the remote operating system by
1037 analyzing incoming TCP SYN packets.
1039 Rules and loading software can be downloaded from
1040 http://www.ioremap.net/projects/osf
1042 To compile it as a module, choose M here. If unsure, say N.
1044 config NETFILTER_XT_MATCH_OWNER
1045 tristate '"owner" match support'
1046 depends on NETFILTER_ADVANCED
1048 Socket owner matching allows you to match locally-generated packets
1049 based on who created the socket: the user or group. It is also
1050 possible to check whether a socket actually exists.
1052 config NETFILTER_XT_MATCH_POLICY
1053 tristate 'IPsec "policy" match support'
1055 default m if NETFILTER_ADVANCED=n
1057 Policy matching allows you to match packets based on the
1058 IPsec policy that was used during decapsulation/will
1059 be used during encapsulation.
1061 To compile it as a module, choose M here. If unsure, say N.
1063 config NETFILTER_XT_MATCH_PHYSDEV
1064 tristate '"physdev" match support'
1065 depends on BRIDGE && BRIDGE_NETFILTER
1066 depends on NETFILTER_ADVANCED
1068 Physdev packet matching matches against the physical bridge ports
1069 the IP packet arrived on or will leave by.
1071 To compile it as a module, choose M here. If unsure, say N.
1073 config NETFILTER_XT_MATCH_PKTTYPE
1074 tristate '"pkttype" packet type match support'
1075 depends on NETFILTER_ADVANCED
1077 Packet type matching allows you to match a packet by
1078 its "class", eg. BROADCAST, MULTICAST, ...
1081 iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG
1083 To compile it as a module, choose M here. If unsure, say N.
1085 config NETFILTER_XT_MATCH_QUOTA
1086 tristate '"quota" match support'
1087 depends on NETFILTER_ADVANCED
1089 This option adds a `quota' match, which allows to match on a
1092 If you want to compile it as a module, say M here and read
1093 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1095 config NETFILTER_XT_MATCH_RATEEST
1096 tristate '"rateest" match support'
1097 depends on NETFILTER_ADVANCED
1098 select NETFILTER_XT_TARGET_RATEEST
1100 This option adds a `rateest' match, which allows to match on the
1101 rate estimated by the RATEEST target.
1103 To compile it as a module, choose M here. If unsure, say N.
1105 config NETFILTER_XT_MATCH_REALM
1106 tristate '"realm" match support'
1107 depends on NETFILTER_ADVANCED
1108 select IP_ROUTE_CLASSID
1110 This option adds a `realm' match, which allows you to use the realm
1111 key from the routing subsystem inside iptables.
1113 This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option
1116 If you want to compile it as a module, say M here and read
1117 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1119 config NETFILTER_XT_MATCH_RECENT
1120 tristate '"recent" match support'
1121 depends on NETFILTER_ADVANCED
1123 This match is used for creating one or many lists of recently
1124 used addresses and then matching against that/those list(s).
1126 Short options are available by using 'iptables -m recent -h'
1127 Official Website: <http://snowman.net/projects/ipt_recent/>
1129 config NETFILTER_XT_MATCH_SCTP
1130 tristate '"sctp" protocol match support (EXPERIMENTAL)'
1131 depends on EXPERIMENTAL
1132 depends on NETFILTER_ADVANCED
1135 With this option enabled, you will be able to use the
1136 `sctp' match in order to match on SCTP source/destination ports
1137 and SCTP chunk types.
1139 If you want to compile it as a module, say M here and read
1140 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1142 config NETFILTER_XT_MATCH_SOCKET
1143 tristate '"socket" match support (EXPERIMENTAL)'
1144 depends on EXPERIMENTAL
1145 depends on NETFILTER_TPROXY
1146 depends on NETFILTER_XTABLES
1147 depends on NETFILTER_ADVANCED
1148 depends on !NF_CONNTRACK || NF_CONNTRACK
1149 select NF_DEFRAG_IPV4
1150 select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES
1152 This option adds a `socket' match, which can be used to match
1153 packets for which a TCP or UDP socket lookup finds a valid socket.
1154 It can be used in combination with the MARK target and policy
1155 routing to implement full featured non-locally bound sockets.
1157 To compile it as a module, choose M here. If unsure, say N.
1159 config NETFILTER_XT_MATCH_STATE
1160 tristate '"state" match support'
1161 depends on NF_CONNTRACK
1162 default m if NETFILTER_ADVANCED=n
1164 Connection state matching allows you to match packets based on their
1165 relationship to a tracked connection (ie. previous packets). This
1166 is a powerful tool for packet classification.
1168 To compile it as a module, choose M here. If unsure, say N.
1170 config NETFILTER_XT_MATCH_STATISTIC
1171 tristate '"statistic" match support'
1172 depends on NETFILTER_ADVANCED
1174 This option adds a `statistic' match, which allows you to match
1175 on packets periodically or randomly with a given percentage.
1177 To compile it as a module, choose M here. If unsure, say N.
1179 config NETFILTER_XT_MATCH_STRING
1180 tristate '"string" match support'
1181 depends on NETFILTER_ADVANCED
1183 select TEXTSEARCH_KMP
1184 select TEXTSEARCH_BM
1185 select TEXTSEARCH_FSM
1187 This option adds a `string' match, which allows you to look for
1188 pattern matchings in packets.
1190 To compile it as a module, choose M here. If unsure, say N.
1192 config NETFILTER_XT_MATCH_TCPMSS
1193 tristate '"tcpmss" match support'
1194 depends on NETFILTER_ADVANCED
1196 This option adds a `tcpmss' match, which allows you to examine the
1197 MSS value of TCP SYN packets, which control the maximum packet size
1198 for that connection.
1200 To compile it as a module, choose M here. If unsure, say N.
1202 config NETFILTER_XT_MATCH_TIME
1203 tristate '"time" match support'
1204 depends on NETFILTER_ADVANCED
1206 This option adds a "time" match, which allows you to match based on
1207 the packet arrival time (at the machine which netfilter is running)
1208 on) or departure time/date (for locally generated packets).
1210 If you say Y here, try `iptables -m time --help` for
1213 If you want to compile it as a module, say M here.
1216 config NETFILTER_XT_MATCH_U32
1217 tristate '"u32" match support'
1218 depends on NETFILTER_ADVANCED
1220 u32 allows you to extract quantities of up to 4 bytes from a packet,
1221 AND them with specified masks, shift them by specified amounts and
1222 test whether the results are in any of a set of specified ranges.
1223 The specification of what to extract is general enough to skip over
1224 headers with lengths stored in the packet, as in IP or TCP header
1227 Details and examples are in the kernel module source.
1229 endif # NETFILTER_XTABLES
1233 source "net/netfilter/ipset/Kconfig"
1235 source "net/netfilter/ipvs/Kconfig"