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_TIMESTAMP
107 bool 'Connection tracking timestamping'
108 depends on NETFILTER_ADVANCED
110 This option enables support for connection tracking timestamping.
111 This allows you to store the flow start-time and to obtain
112 the flow-stop time (once it has been destroyed) via Connection
117 config NF_CT_PROTO_DCCP
118 tristate 'DCCP protocol connection tracking support (EXPERIMENTAL)'
119 depends on EXPERIMENTAL
120 depends on NETFILTER_ADVANCED
123 With this option enabled, the layer 3 independent connection
124 tracking code will be able to do state tracking on DCCP connections.
128 config NF_CT_PROTO_GRE
131 config NF_CT_PROTO_SCTP
132 tristate 'SCTP protocol connection tracking support (EXPERIMENTAL)'
133 depends on EXPERIMENTAL
134 depends on NETFILTER_ADVANCED
137 With this option enabled, the layer 3 independent connection
138 tracking code will be able to do state tracking on SCTP connections.
140 If you want to compile it as a module, say M here and read
141 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
143 config NF_CT_PROTO_UDPLITE
144 tristate 'UDP-Lite protocol connection tracking support'
145 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 UDP-Lite
151 To compile it as a module, choose M here. If unsure, say N.
153 config NF_CONNTRACK_AMANDA
154 tristate "Amanda backup protocol support"
155 depends on NETFILTER_ADVANCED
157 select TEXTSEARCH_KMP
159 If you are running the Amanda backup package <http://www.amanda.org/>
160 on this machine or machines that will be MASQUERADED through this
161 machine, then you may want to enable this feature. This allows the
162 connection tracking and natting code to allow the sub-channels that
163 Amanda requires for communication of the backup data, messages and
166 To compile it as a module, choose M here. If unsure, say N.
168 config NF_CONNTRACK_FTP
169 tristate "FTP protocol support"
170 default m if NETFILTER_ADVANCED=n
172 Tracking FTP connections is problematic: special helpers are
173 required for tracking them, and doing masquerading and other forms
174 of Network Address Translation on them.
176 This is FTP support on Layer 3 independent connection tracking.
177 Layer 3 independent connection tracking is experimental scheme
178 which generalize ip_conntrack to support other layer 3 protocols.
180 To compile it as a module, choose M here. If unsure, say N.
182 config NF_CONNTRACK_H323
183 tristate "H.323 protocol support"
184 depends on (IPV6 || IPV6=n)
185 depends on NETFILTER_ADVANCED
187 H.323 is a VoIP signalling protocol from ITU-T. As one of the most
188 important VoIP protocols, it is widely used by voice hardware and
189 software including voice gateways, IP phones, Netmeeting, OpenPhone,
192 With this module you can support H.323 on a connection tracking/NAT
195 This module supports RAS, Fast Start, H.245 Tunnelling, Call
196 Forwarding, RTP/RTCP and T.120 based audio, video, fax, chat,
197 whiteboard, file transfer, etc. For more information, please
198 visit http://nath323.sourceforge.net/.
200 To compile it as a module, choose M here. If unsure, say N.
202 config NF_CONNTRACK_IRC
203 tristate "IRC protocol support"
204 default m if NETFILTER_ADVANCED=n
206 There is a commonly-used extension to IRC called
207 Direct Client-to-Client Protocol (DCC). This enables users to send
208 files to each other, and also chat to each other without the need
209 of a server. DCC Sending is used anywhere you send files over IRC,
210 and DCC Chat is most commonly used by Eggdrop bots. If you are
211 using NAT, this extension will enable you to send files and initiate
212 chats. Note that you do NOT need this extension to get files or
213 have others initiate chats, or everything else in IRC.
215 To compile it as a module, choose M here. If unsure, say N.
217 config NF_CONNTRACK_BROADCAST
220 config NF_CONNTRACK_NETBIOS_NS
221 tristate "NetBIOS name service protocol support"
222 select NF_CONNTRACK_BROADCAST
224 NetBIOS name service requests are sent as broadcast messages from an
225 unprivileged port and responded to with unicast messages to the
226 same port. This make them hard to firewall properly because connection
227 tracking doesn't deal with broadcasts. This helper tracks locally
228 originating NetBIOS name service requests and the corresponding
229 responses. It relies on correct IP address configuration, specifically
230 netmask and broadcast address. When properly configured, the output
231 of "ip address show" should look similar to this:
233 $ ip -4 address show eth0
234 4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
235 inet 172.16.2.252/24 brd 172.16.2.255 scope global eth0
237 To compile it as a module, choose M here. If unsure, say N.
239 config NF_CONNTRACK_SNMP
240 tristate "SNMP service protocol support"
241 depends on NETFILTER_ADVANCED
242 select NF_CONNTRACK_BROADCAST
244 SNMP service requests are sent as broadcast messages from an
245 unprivileged port and responded to with unicast messages to the
246 same port. This make them hard to firewall properly because connection
247 tracking doesn't deal with broadcasts. This helper tracks locally
248 originating SNMP service requests and the corresponding
249 responses. It relies on correct IP address configuration, specifically
250 netmask and broadcast address.
252 To compile it as a module, choose M here. If unsure, say N.
254 config NF_CONNTRACK_PPTP
255 tristate "PPtP protocol support"
256 depends on NETFILTER_ADVANCED
257 select NF_CT_PROTO_GRE
259 This module adds support for PPTP (Point to Point Tunnelling
260 Protocol, RFC2637) connection tracking and NAT.
262 If you are running PPTP sessions over a stateful firewall or NAT
263 box, you may want to enable this feature.
265 Please note that not all PPTP modes of operation are supported yet.
266 Specifically these limitations exist:
267 - Blindly assumes that control connections are always established
268 in PNS->PAC direction. This is a violation of RFC2637.
269 - Only supports a single call within each session
271 To compile it as a module, choose M here. If unsure, say N.
273 config NF_CONNTRACK_SANE
274 tristate "SANE protocol support (EXPERIMENTAL)"
275 depends on EXPERIMENTAL
276 depends on NETFILTER_ADVANCED
278 SANE is a protocol for remote access to scanners as implemented
279 by the 'saned' daemon. Like FTP, it uses separate control and
282 With this module you can support SANE on a connection tracking
285 To compile it as a module, choose M here. If unsure, say N.
287 config NF_CONNTRACK_SIP
288 tristate "SIP protocol support"
289 default m if NETFILTER_ADVANCED=n
291 SIP is an application-layer control protocol that can establish,
292 modify, and terminate multimedia sessions (conferences) such as
293 Internet telephony calls. With the ip_conntrack_sip and
294 the nf_nat_sip modules you can support the protocol on a connection
295 tracking/NATing firewall.
297 To compile it as a module, choose M here. If unsure, say N.
299 config NF_CONNTRACK_TFTP
300 tristate "TFTP protocol support"
301 depends on NETFILTER_ADVANCED
303 TFTP connection tracking helper, this is required depending
304 on how restrictive your ruleset is.
305 If you are using a tftp client behind -j SNAT or -j MASQUERADING
308 To compile it as a module, choose M here. If unsure, say N.
311 tristate 'Connection tracking netlink interface'
312 select NETFILTER_NETLINK
313 default m if NETFILTER_ADVANCED=n
315 This option enables support for a netlink-based userspace interface
317 config NF_CT_NETLINK_TIMEOUT
318 tristate 'Connection tracking timeout tuning via Netlink'
319 select NETFILTER_NETLINK
320 depends on NETFILTER_ADVANCED
322 This option enables support for connection tracking timeout
323 fine-grain tuning. This allows you to attach specific timeout
324 policies to flows, instead of using the global timeout policy.
330 # transparent proxy support
331 config NETFILTER_TPROXY
332 tristate "Transparent proxying support (EXPERIMENTAL)"
333 depends on EXPERIMENTAL
334 depends on IP_NF_MANGLE
335 depends on NETFILTER_ADVANCED
337 This option enables transparent proxying support, that is,
338 support for handling non-locally bound IPv4 TCP and UDP sockets.
339 For it to work you will have to configure certain iptables rules
340 and use policy routing. For more information on how to set it up
341 see Documentation/networking/tproxy.txt.
343 To compile it as a module, choose M here. If unsure, say N.
345 config NETFILTER_XTABLES
346 tristate "Netfilter Xtables support (required for ip_tables)"
347 default m if NETFILTER_ADVANCED=n
349 This is required if you intend to use any of ip_tables,
350 ip6_tables or arp_tables.
354 comment "Xtables combined modules"
356 config NETFILTER_XT_MARK
357 tristate 'nfmark target and match support'
358 default m if NETFILTER_ADVANCED=n
360 This option adds the "MARK" target and "mark" match.
362 Netfilter mark matching allows you to match packets based on the
363 "nfmark" value in the packet.
364 The target allows you to create rules in the "mangle" table which alter
365 the netfilter mark (nfmark) field associated with the packet.
367 Prior to routing, the nfmark can influence the routing method (see
368 "Use netfilter MARK value as routing key") and can also be used by
369 other subsystems to change their behavior.
371 config NETFILTER_XT_CONNMARK
372 tristate 'ctmark target and match support'
373 depends on NF_CONNTRACK
374 depends on NETFILTER_ADVANCED
375 select NF_CONNTRACK_MARK
377 This option adds the "CONNMARK" target and "connmark" match.
379 Netfilter allows you to store a mark value per connection (a.k.a.
380 ctmark), similarly to the packet mark (nfmark). Using this
381 target and match, you can set and match on this mark.
383 config NETFILTER_XT_SET
384 tristate 'set target and match support'
386 depends on NETFILTER_ADVANCED
388 This option adds the "SET" target and "set" match.
390 Using this target and match, you can add/delete and match
391 elements in the sets created by ipset(8).
393 To compile it as a module, choose M here. If unsure, say N.
395 # alphabetically ordered list of targets
397 comment "Xtables targets"
399 config NETFILTER_XT_TARGET_AUDIT
400 tristate "AUDIT target support"
402 depends on NETFILTER_ADVANCED
404 This option adds a 'AUDIT' target, which can be used to create
405 audit records for packets dropped/accepted.
407 To compileit as a module, choose M here. If unsure, say N.
409 config NETFILTER_XT_TARGET_CHECKSUM
410 tristate "CHECKSUM target support"
411 depends on IP_NF_MANGLE || IP6_NF_MANGLE
412 depends on NETFILTER_ADVANCED
414 This option adds a `CHECKSUM' target, which can be used in the iptables mangle
417 You can use this target to compute and fill in the checksum in
418 a packet that lacks a checksum. This is particularly useful,
419 if you need to work around old applications such as dhcp clients,
420 that do not work well with checksum offloads, but don't want to disable
421 checksum offload in your device.
423 To compile it as a module, choose M here. If unsure, say N.
425 config NETFILTER_XT_TARGET_CLASSIFY
426 tristate '"CLASSIFY" target support'
427 depends on NETFILTER_ADVANCED
429 This option adds a `CLASSIFY' target, which enables the user to set
430 the priority of a packet. Some qdiscs can use this value for
431 classification, among these are:
433 atm, cbq, dsmark, pfifo_fast, htb, prio
435 To compile it as a module, choose M here. If unsure, say N.
437 config NETFILTER_XT_TARGET_CONNMARK
438 tristate '"CONNMARK" target support'
439 depends on NF_CONNTRACK
440 depends on NETFILTER_ADVANCED
441 select NETFILTER_XT_CONNMARK
443 This is a backwards-compat option for the user's convenience
444 (e.g. when running oldconfig). It selects
445 CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
447 config NETFILTER_XT_TARGET_CONNSECMARK
448 tristate '"CONNSECMARK" target support'
449 depends on NF_CONNTRACK && NF_CONNTRACK_SECMARK
450 default m if NETFILTER_ADVANCED=n
452 The CONNSECMARK target copies security markings from packets
453 to connections, and restores security markings from connections
454 to packets (if the packets are not already marked). This would
455 normally be used in conjunction with the SECMARK target.
457 To compile it as a module, choose M here. If unsure, say N.
459 config NETFILTER_XT_TARGET_CT
460 tristate '"CT" target support'
461 depends on NF_CONNTRACK
462 depends on IP_NF_RAW || IP6_NF_RAW
463 depends on NETFILTER_ADVANCED
465 This options adds a `CT' target, which allows to specify initial
466 connection tracking parameters like events to be delivered and
467 the helper to be used.
469 To compile it as a module, choose M here. If unsure, say N.
471 config NETFILTER_XT_TARGET_DSCP
472 tristate '"DSCP" and "TOS" target support'
473 depends on IP_NF_MANGLE || IP6_NF_MANGLE
474 depends on NETFILTER_ADVANCED
476 This option adds a `DSCP' target, which allows you to manipulate
477 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
479 The DSCP field can have any value between 0x0 and 0x3f inclusive.
481 It also adds the "TOS" target, which allows you to create rules in
482 the "mangle" table which alter the Type Of Service field of an IPv4
483 or the Priority field of an IPv6 packet, prior to routing.
485 To compile it as a module, choose M here. If unsure, say N.
487 config NETFILTER_XT_TARGET_HL
488 tristate '"HL" hoplimit target support'
489 depends on IP_NF_MANGLE || IP6_NF_MANGLE
490 depends on NETFILTER_ADVANCED
492 This option adds the "HL" (for IPv6) and "TTL" (for IPv4)
493 targets, which enable the user to change the
494 hoplimit/time-to-live value of the IP header.
496 While it is safe to decrement the hoplimit/TTL value, the
497 modules also allow to increment and set the hoplimit value of
498 the header to arbitrary values. This is EXTREMELY DANGEROUS
499 since you can easily create immortal packets that loop
500 forever on the network.
502 config NETFILTER_XT_TARGET_IDLETIMER
503 tristate "IDLETIMER target support"
504 depends on NETFILTER_ADVANCED
507 This option adds the `IDLETIMER' target. Each matching packet
508 resets the timer associated with label specified when the rule is
509 added. When the timer expires, it triggers a sysfs notification.
510 The remaining time for expiration can be read via sysfs.
512 To compile it as a module, choose M here. If unsure, say N.
514 config NETFILTER_XT_TARGET_LED
515 tristate '"LED" target support'
516 depends on LEDS_CLASS && LEDS_TRIGGERS
517 depends on NETFILTER_ADVANCED
519 This option adds a `LED' target, which allows you to blink LEDs in
520 response to particular packets passing through your machine.
522 This can be used to turn a spare LED into a network activity LED,
523 which only flashes in response to FTP transfers, for example. Or
524 you could have an LED which lights up for a minute or two every time
525 somebody connects to your machine via SSH.
527 You will need support for the "led" class to make this work.
529 To create an LED trigger for incoming SSH traffic:
530 iptables -A INPUT -p tcp --dport 22 -j LED --led-trigger-id ssh --led-delay 1000
532 Then attach the new trigger to an LED on your system:
533 echo netfilter-ssh > /sys/class/leds/<ledname>/trigger
535 For more information on the LEDs available on your system, see
536 Documentation/leds/leds-class.txt
538 config NETFILTER_XT_TARGET_LOG
539 tristate "LOG target support"
540 default m if NETFILTER_ADVANCED=n
542 This option adds a `LOG' target, which allows you to create rules in
543 any iptables table which records the packet header to the syslog.
545 To compile it as a module, choose M here. If unsure, say N.
547 config NETFILTER_XT_TARGET_MARK
548 tristate '"MARK" target support'
549 depends on NETFILTER_ADVANCED
550 select NETFILTER_XT_MARK
552 This is a backwards-compat option for the user's convenience
553 (e.g. when running oldconfig). It selects
554 CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
556 config NETFILTER_XT_TARGET_NFLOG
557 tristate '"NFLOG" target support'
558 default m if NETFILTER_ADVANCED=n
559 select NETFILTER_NETLINK_LOG
561 This option enables the NFLOG target, which allows to LOG
562 messages through nfnetlink_log.
564 To compile it as a module, choose M here. If unsure, say N.
566 config NETFILTER_XT_TARGET_NFQUEUE
567 tristate '"NFQUEUE" target Support'
568 depends on NETFILTER_ADVANCED
569 select NETFILTER_NETLINK_QUEUE
571 This target replaced the old obsolete QUEUE target.
573 As opposed to QUEUE, it supports 65535 different queues,
576 To compile it as a module, choose M here. If unsure, say N.
578 config NETFILTER_XT_TARGET_NOTRACK
579 tristate '"NOTRACK" target support'
580 depends on IP_NF_RAW || IP6_NF_RAW
581 depends on NF_CONNTRACK
583 The NOTRACK target allows a select rule to specify
584 which packets *not* to enter the conntrack/NAT
585 subsystem with all the consequences (no ICMP error tracking,
586 no protocol helpers for the selected packets).
588 If you want to compile it as a module, say M here and read
589 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
591 config NETFILTER_XT_TARGET_RATEEST
592 tristate '"RATEEST" target support'
593 depends on NETFILTER_ADVANCED
595 This option adds a `RATEEST' target, which allows to measure
596 rates similar to TC estimators. The `rateest' match can be
597 used to match on the measured rates.
599 To compile it as a module, choose M here. If unsure, say N.
601 config NETFILTER_XT_TARGET_TEE
602 tristate '"TEE" - packet cloning to alternate destination'
603 depends on NETFILTER_ADVANCED
604 depends on (IPV6 || IPV6=n)
605 depends on !NF_CONNTRACK || NF_CONNTRACK
607 This option adds a "TEE" target with which a packet can be cloned and
608 this clone be rerouted to another nexthop.
610 config NETFILTER_XT_TARGET_TPROXY
611 tristate '"TPROXY" target support (EXPERIMENTAL)'
612 depends on EXPERIMENTAL
613 depends on NETFILTER_TPROXY
614 depends on NETFILTER_XTABLES
615 depends on NETFILTER_ADVANCED
616 select NF_DEFRAG_IPV4
617 select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES
619 This option adds a `TPROXY' target, which is somewhat similar to
620 REDIRECT. It can only be used in the mangle table and is useful
621 to redirect traffic to a transparent proxy. It does _not_ depend
622 on Netfilter connection tracking and NAT, unlike REDIRECT.
624 To compile it as a module, choose M here. If unsure, say N.
626 config NETFILTER_XT_TARGET_TRACE
627 tristate '"TRACE" target support'
628 depends on IP_NF_RAW || IP6_NF_RAW
629 depends on NETFILTER_ADVANCED
631 The TRACE target allows you to mark packets so that the kernel
632 will log every rule which match the packets as those traverse
633 the tables, chains, rules.
635 If you want to compile it as a module, say M here and read
636 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
638 config NETFILTER_XT_TARGET_SECMARK
639 tristate '"SECMARK" target support'
640 depends on NETWORK_SECMARK
641 default m if NETFILTER_ADVANCED=n
643 The SECMARK target allows security marking of network
644 packets, for use with security subsystems.
646 To compile it as a module, choose M here. If unsure, say N.
648 config NETFILTER_XT_TARGET_TCPMSS
649 tristate '"TCPMSS" target support'
650 depends on (IPV6 || IPV6=n)
651 default m if NETFILTER_ADVANCED=n
653 This option adds a `TCPMSS' target, which allows you to alter the
654 MSS value of TCP SYN packets, to control the maximum size for that
655 connection (usually limiting it to your outgoing interface's MTU
658 This is used to overcome criminally braindead ISPs or servers which
659 block ICMP Fragmentation Needed packets. The symptoms of this
660 problem are that everything works fine from your Linux
661 firewall/router, but machines behind it can never exchange large
663 1) Web browsers connect, then hang with no data received.
664 2) Small mail works fine, but large emails hang.
665 3) ssh works fine, but scp hangs after initial handshaking.
667 Workaround: activate this option and add a rule to your firewall
670 iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
671 -j TCPMSS --clamp-mss-to-pmtu
673 To compile it as a module, choose M here. If unsure, say N.
675 config NETFILTER_XT_TARGET_TCPOPTSTRIP
676 tristate '"TCPOPTSTRIP" target support (EXPERIMENTAL)'
677 depends on EXPERIMENTAL
678 depends on IP_NF_MANGLE || IP6_NF_MANGLE
679 depends on NETFILTER_ADVANCED
681 This option adds a "TCPOPTSTRIP" target, which allows you to strip
682 TCP options from TCP packets.
684 # alphabetically ordered list of matches
686 comment "Xtables matches"
688 config NETFILTER_XT_MATCH_ADDRTYPE
689 tristate '"addrtype" address type match support'
690 depends on NETFILTER_ADVANCED
692 This option allows you to match what routing thinks of an address,
693 eg. UNICAST, LOCAL, BROADCAST, ...
695 If you want to compile it as a module, say M here and read
696 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
698 config NETFILTER_XT_MATCH_CLUSTER
699 tristate '"cluster" match support'
700 depends on NF_CONNTRACK
701 depends on NETFILTER_ADVANCED
703 This option allows you to build work-load-sharing clusters of
704 network servers/stateful firewalls without having a dedicated
705 load-balancing router/server/switch. Basically, this match returns
706 true when the packet must be handled by this cluster node. Thus,
707 all nodes see all packets and this match decides which node handles
708 what packets. The work-load sharing algorithm is based on source
711 If you say Y or M here, try `iptables -m cluster --help` for
714 config NETFILTER_XT_MATCH_COMMENT
715 tristate '"comment" match support'
716 depends on NETFILTER_ADVANCED
718 This option adds a `comment' dummy-match, which allows you to put
719 comments in your iptables ruleset.
721 If you want to compile it as a module, say M here and read
722 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
724 config NETFILTER_XT_MATCH_CONNBYTES
725 tristate '"connbytes" per-connection counter match support'
726 depends on NF_CONNTRACK
727 depends on NETFILTER_ADVANCED
729 This option adds a `connbytes' match, which allows you to match the
730 number of bytes and/or packets for each direction within a connection.
732 If you want to compile it as a module, say M here and read
733 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
735 config NETFILTER_XT_MATCH_CONNLIMIT
736 tristate '"connlimit" match support"'
737 depends on NF_CONNTRACK
738 depends on NETFILTER_ADVANCED
740 This match allows you to match against the number of parallel
741 connections to a server per client IP address (or address block).
743 config NETFILTER_XT_MATCH_CONNMARK
744 tristate '"connmark" connection mark match support'
745 depends on NF_CONNTRACK
746 depends on NETFILTER_ADVANCED
747 select NETFILTER_XT_CONNMARK
749 This is a backwards-compat option for the user's convenience
750 (e.g. when running oldconfig). It selects
751 CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
753 config NETFILTER_XT_MATCH_CONNTRACK
754 tristate '"conntrack" connection tracking match support'
755 depends on NF_CONNTRACK
756 default m if NETFILTER_ADVANCED=n
758 This is a general conntrack match module, a superset of the state match.
760 It allows matching on additional conntrack information, which is
761 useful in complex configurations, such as NAT gateways with multiple
762 internet links or tunnels.
764 To compile it as a module, choose M here. If unsure, say N.
766 config NETFILTER_XT_MATCH_CPU
767 tristate '"cpu" match support'
768 depends on NETFILTER_ADVANCED
770 CPU matching allows you to match packets based on the CPU
771 currently handling the packet.
773 To compile it as a module, choose M here. If unsure, say N.
775 config NETFILTER_XT_MATCH_DCCP
776 tristate '"dccp" protocol match support'
777 depends on NETFILTER_ADVANCED
780 With this option enabled, you will be able to use the iptables
781 `dccp' match in order to match on DCCP source/destination ports
784 If you want to compile it as a module, say M here and read
785 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
787 config NETFILTER_XT_MATCH_DEVGROUP
788 tristate '"devgroup" match support'
789 depends on NETFILTER_ADVANCED
791 This options adds a `devgroup' match, which allows to match on the
792 device group a network device is assigned to.
794 To compile it as a module, choose M here. If unsure, say N.
796 config NETFILTER_XT_MATCH_DSCP
797 tristate '"dscp" and "tos" match support'
798 depends on NETFILTER_ADVANCED
800 This option adds a `DSCP' match, which allows you to match against
801 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
803 The DSCP field can have any value between 0x0 and 0x3f inclusive.
805 It will also add a "tos" match, which allows you to match packets
806 based on the Type Of Service fields of the IPv4 packet (which share
807 the same bits as DSCP).
809 To compile it as a module, choose M here. If unsure, say N.
811 config NETFILTER_XT_MATCH_ECN
812 tristate '"ecn" match support'
813 depends on NETFILTER_ADVANCED
815 This option adds an "ECN" match, which allows you to match against
816 the IPv4 and TCP header ECN fields.
818 To compile it as a module, choose M here. If unsure, say N.
820 config NETFILTER_XT_MATCH_ESP
821 tristate '"esp" match support'
822 depends on NETFILTER_ADVANCED
824 This match extension allows you to match a range of SPIs
825 inside ESP header of IPSec packets.
827 To compile it as a module, choose M here. If unsure, say N.
829 config NETFILTER_XT_MATCH_HASHLIMIT
830 tristate '"hashlimit" match support'
831 depends on (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
832 depends on NETFILTER_ADVANCED
834 This option adds a `hashlimit' match.
836 As opposed to `limit', this match dynamically creates a hash table
837 of limit buckets, based on your selection of source/destination
838 addresses and/or ports.
840 It enables you to express policies like `10kpps for any given
841 destination address' or `500pps from any given source address'
844 config NETFILTER_XT_MATCH_HELPER
845 tristate '"helper" match support'
846 depends on NF_CONNTRACK
847 depends on NETFILTER_ADVANCED
849 Helper matching allows you to match packets in dynamic connections
850 tracked by a conntrack-helper, ie. ip_conntrack_ftp
852 To compile it as a module, choose M here. If unsure, say Y.
854 config NETFILTER_XT_MATCH_HL
855 tristate '"hl" hoplimit/TTL match support'
856 depends on NETFILTER_ADVANCED
858 HL matching allows you to match packets based on the hoplimit
859 in the IPv6 header, or the time-to-live field in the IPv4
860 header of the packet.
862 config NETFILTER_XT_MATCH_IPRANGE
863 tristate '"iprange" address range match support'
864 depends on NETFILTER_ADVANCED
866 This option adds a "iprange" match, which allows you to match based on
867 an IP address range. (Normal iptables only matches on single addresses
868 with an optional mask.)
872 config NETFILTER_XT_MATCH_IPVS
873 tristate '"ipvs" match support'
875 depends on NETFILTER_ADVANCED
876 depends on NF_CONNTRACK
878 This option allows you to match against IPVS properties of a packet.
882 config NETFILTER_XT_MATCH_LENGTH
883 tristate '"length" match support'
884 depends on NETFILTER_ADVANCED
886 This option allows you to match the length of a packet against a
887 specific value or range of values.
889 To compile it as a module, choose M here. If unsure, say N.
891 config NETFILTER_XT_MATCH_LIMIT
892 tristate '"limit" match support'
893 depends on NETFILTER_ADVANCED
895 limit matching allows you to control the rate at which a rule can be
896 matched: mainly useful in combination with the LOG target ("LOG
897 target support", below) and to avoid some Denial of Service attacks.
899 To compile it as a module, choose M here. If unsure, say N.
901 config NETFILTER_XT_MATCH_MAC
902 tristate '"mac" address match support'
903 depends on NETFILTER_ADVANCED
905 MAC matching allows you to match packets based on the source
906 Ethernet address of the packet.
908 To compile it as a module, choose M here. If unsure, say N.
910 config NETFILTER_XT_MATCH_MARK
911 tristate '"mark" match support'
912 depends on NETFILTER_ADVANCED
913 select NETFILTER_XT_MARK
915 This is a backwards-compat option for the user's convenience
916 (e.g. when running oldconfig). It selects
917 CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
919 config NETFILTER_XT_MATCH_MULTIPORT
920 tristate '"multiport" Multiple port match support'
921 depends on NETFILTER_ADVANCED
923 Multiport matching allows you to match TCP or UDP packets based on
924 a series of source or destination ports: normally a rule can only
925 match a single range of ports.
927 To compile it as a module, choose M here. If unsure, say N.
929 config NETFILTER_XT_MATCH_NFACCT
930 tristate '"nfacct" match support'
931 depends on NETFILTER_ADVANCED
932 select NETFILTER_NETLINK_ACCT
934 This option allows you to use the extended accounting through
937 To compile it as a module, choose M here. If unsure, say N.
939 config NETFILTER_XT_MATCH_OSF
940 tristate '"osf" Passive OS fingerprint match'
941 depends on NETFILTER_ADVANCED && NETFILTER_NETLINK
943 This option selects the Passive OS Fingerprinting match module
944 that allows to passively match the remote operating system by
945 analyzing incoming TCP SYN packets.
947 Rules and loading software can be downloaded from
948 http://www.ioremap.net/projects/osf
950 To compile it as a module, choose M here. If unsure, say N.
952 config NETFILTER_XT_MATCH_OWNER
953 tristate '"owner" match support'
954 depends on NETFILTER_ADVANCED
956 Socket owner matching allows you to match locally-generated packets
957 based on who created the socket: the user or group. It is also
958 possible to check whether a socket actually exists.
960 config NETFILTER_XT_MATCH_POLICY
961 tristate 'IPsec "policy" match support'
963 default m if NETFILTER_ADVANCED=n
965 Policy matching allows you to match packets based on the
966 IPsec policy that was used during decapsulation/will
967 be used during encapsulation.
969 To compile it as a module, choose M here. If unsure, say N.
971 config NETFILTER_XT_MATCH_PHYSDEV
972 tristate '"physdev" match support'
973 depends on BRIDGE && BRIDGE_NETFILTER
974 depends on NETFILTER_ADVANCED
976 Physdev packet matching matches against the physical bridge ports
977 the IP packet arrived on or will leave by.
979 To compile it as a module, choose M here. If unsure, say N.
981 config NETFILTER_XT_MATCH_PKTTYPE
982 tristate '"pkttype" packet type match support'
983 depends on NETFILTER_ADVANCED
985 Packet type matching allows you to match a packet by
986 its "class", eg. BROADCAST, MULTICAST, ...
989 iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG
991 To compile it as a module, choose M here. If unsure, say N.
993 config NETFILTER_XT_MATCH_QUOTA
994 tristate '"quota" match support'
995 depends on NETFILTER_ADVANCED
997 This option adds a `quota' match, which allows to match on a
1000 If you want to compile it as a module, say M here and read
1001 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1003 config NETFILTER_XT_MATCH_RATEEST
1004 tristate '"rateest" match support'
1005 depends on NETFILTER_ADVANCED
1006 select NETFILTER_XT_TARGET_RATEEST
1008 This option adds a `rateest' match, which allows to match on the
1009 rate estimated by the RATEEST target.
1011 To compile it as a module, choose M here. If unsure, say N.
1013 config NETFILTER_XT_MATCH_REALM
1014 tristate '"realm" match support'
1015 depends on NETFILTER_ADVANCED
1016 select IP_ROUTE_CLASSID
1018 This option adds a `realm' match, which allows you to use the realm
1019 key from the routing subsystem inside iptables.
1021 This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option
1024 If you want to compile it as a module, say M here and read
1025 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1027 config NETFILTER_XT_MATCH_RECENT
1028 tristate '"recent" match support'
1029 depends on NETFILTER_ADVANCED
1031 This match is used for creating one or many lists of recently
1032 used addresses and then matching against that/those list(s).
1034 Short options are available by using 'iptables -m recent -h'
1035 Official Website: <http://snowman.net/projects/ipt_recent/>
1037 config NETFILTER_XT_MATCH_SCTP
1038 tristate '"sctp" protocol match support (EXPERIMENTAL)'
1039 depends on EXPERIMENTAL
1040 depends on NETFILTER_ADVANCED
1043 With this option enabled, you will be able to use the
1044 `sctp' match in order to match on SCTP source/destination ports
1045 and SCTP chunk types.
1047 If you want to compile it as a module, say M here and read
1048 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1050 config NETFILTER_XT_MATCH_SOCKET
1051 tristate '"socket" match support (EXPERIMENTAL)'
1052 depends on EXPERIMENTAL
1053 depends on NETFILTER_TPROXY
1054 depends on NETFILTER_XTABLES
1055 depends on NETFILTER_ADVANCED
1056 depends on !NF_CONNTRACK || NF_CONNTRACK
1057 select NF_DEFRAG_IPV4
1058 select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES
1060 This option adds a `socket' match, which can be used to match
1061 packets for which a TCP or UDP socket lookup finds a valid socket.
1062 It can be used in combination with the MARK target and policy
1063 routing to implement full featured non-locally bound sockets.
1065 To compile it as a module, choose M here. If unsure, say N.
1067 config NETFILTER_XT_MATCH_STATE
1068 tristate '"state" match support'
1069 depends on NF_CONNTRACK
1070 default m if NETFILTER_ADVANCED=n
1072 Connection state matching allows you to match packets based on their
1073 relationship to a tracked connection (ie. previous packets). This
1074 is a powerful tool for packet classification.
1076 To compile it as a module, choose M here. If unsure, say N.
1078 config NETFILTER_XT_MATCH_STATISTIC
1079 tristate '"statistic" match support'
1080 depends on NETFILTER_ADVANCED
1082 This option adds a `statistic' match, which allows you to match
1083 on packets periodically or randomly with a given percentage.
1085 To compile it as a module, choose M here. If unsure, say N.
1087 config NETFILTER_XT_MATCH_STRING
1088 tristate '"string" match support'
1089 depends on NETFILTER_ADVANCED
1091 select TEXTSEARCH_KMP
1092 select TEXTSEARCH_BM
1093 select TEXTSEARCH_FSM
1095 This option adds a `string' match, which allows you to look for
1096 pattern matchings in packets.
1098 To compile it as a module, choose M here. If unsure, say N.
1100 config NETFILTER_XT_MATCH_TCPMSS
1101 tristate '"tcpmss" match support'
1102 depends on NETFILTER_ADVANCED
1104 This option adds a `tcpmss' match, which allows you to examine the
1105 MSS value of TCP SYN packets, which control the maximum packet size
1106 for that connection.
1108 To compile it as a module, choose M here. If unsure, say N.
1110 config NETFILTER_XT_MATCH_TIME
1111 tristate '"time" match support'
1112 depends on NETFILTER_ADVANCED
1114 This option adds a "time" match, which allows you to match based on
1115 the packet arrival time (at the machine which netfilter is running)
1116 on) or departure time/date (for locally generated packets).
1118 If you say Y here, try `iptables -m time --help` for
1121 If you want to compile it as a module, say M here.
1124 config NETFILTER_XT_MATCH_U32
1125 tristate '"u32" match support'
1126 depends on NETFILTER_ADVANCED
1128 u32 allows you to extract quantities of up to 4 bytes from a packet,
1129 AND them with specified masks, shift them by specified amounts and
1130 test whether the results are in any of a set of specified ranges.
1131 The specification of what to extract is general enough to skip over
1132 headers with lengths stored in the packet, as in IP or TCP header
1135 Details and examples are in the kernel module source.
1137 endif # NETFILTER_XTABLES
1141 source "net/netfilter/ipset/Kconfig"
1143 source "net/netfilter/ipvs/Kconfig"