1 menu "Core Netfilter Configuration"
2 depends on NET && INET && NETFILTER
4 config NETFILTER_NETLINK
7 config NETFILTER_NETLINK_QUEUE
8 tristate "Netfilter NFQUEUE 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 queueing packets via NFNETLINK.
15 config NETFILTER_NETLINK_LOG
16 tristate "Netfilter LOG over NFNETLINK interface"
17 default m if NETFILTER_ADVANCED=n
18 select NETFILTER_NETLINK
20 If this option is enabled, the kernel will include support
21 for logging packets via NFNETLINK.
23 This obsoletes the existing ipt_ULOG and ebg_ulog mechanisms,
24 and is also scheduled to replace the old syslog-based ipt_LOG
28 tristate "Netfilter connection tracking support"
29 default m if NETFILTER_ADVANCED=n
31 Connection tracking keeps a record of what packets have passed
32 through your machine, in order to figure out how they are related
35 This is required to do Masquerading or other kinds of Network
36 Address Translation. It can also be used to enhance packet
37 filtering (see `Connection state match support' below).
39 To compile it as a module, choose M here. If unsure, say N.
44 bool "Connection tracking flow accounting"
45 depends on NETFILTER_ADVANCED
47 If this option is enabled, the connection tracking code will
48 keep per-flow packet and byte counters.
50 Those counters can be used for flow-based accounting or the
53 Please note that currently this option only sets a default state.
54 You may change it at boot time with nf_conntrack.acct=0/1 kernel
55 parameter or by loading the nf_conntrack module with acct=0/1.
57 You may also disable/enable it on a running system with:
58 sysctl net.netfilter.nf_conntrack_acct=0/1
60 This option will be removed in 2.6.29.
64 config NF_CONNTRACK_MARK
65 bool 'Connection mark tracking support'
66 depends on NETFILTER_ADVANCED
68 This option enables support for connection marks, used by the
69 `CONNMARK' target and `connmark' match. Similar to the mark value
70 of packets, but this mark value is kept in the conntrack session
71 instead of the individual packets.
73 config NF_CONNTRACK_SECMARK
74 bool 'Connection tracking security mark support'
75 depends on NETWORK_SECMARK
76 default m if NETFILTER_ADVANCED=n
78 This option enables security markings to be applied to
79 connections. Typically they are copied to connections from
80 packets using the CONNSECMARK target and copied back from
81 connections to packets with the same target, with the packets
82 being originally labeled via SECMARK.
86 config NF_CONNTRACK_ZONES
87 bool 'Connection tracking zones'
88 depends on NETFILTER_ADVANCED
89 depends on NETFILTER_XT_TARGET_CT
91 This option enables support for connection tracking zones.
92 Normally, each connection needs to have a unique system wide
93 identity. Connection tracking zones allow to have multiple
94 connections using the same identity, as long as they are
95 contained in different zones.
99 config NF_CONNTRACK_EVENTS
100 bool "Connection tracking events"
101 depends on NETFILTER_ADVANCED
103 If this option is enabled, the connection tracking code will
104 provide a notifier chain that can be used by other kernel code
105 to get notified about changes in the connection tracking state.
109 config NF_CT_PROTO_DCCP
110 tristate 'DCCP protocol connection tracking support (EXPERIMENTAL)'
111 depends on EXPERIMENTAL
112 depends on NETFILTER_ADVANCED
115 With this option enabled, the layer 3 independent connection
116 tracking code will be able to do state tracking on DCCP connections.
120 config NF_CT_PROTO_GRE
123 config NF_CT_PROTO_SCTP
124 tristate 'SCTP protocol connection tracking support (EXPERIMENTAL)'
125 depends on EXPERIMENTAL
126 depends on NETFILTER_ADVANCED
129 With this option enabled, the layer 3 independent connection
130 tracking code will be able to do state tracking on SCTP connections.
132 If you want to compile it as a module, say M here and read
133 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
135 config NF_CT_PROTO_UDPLITE
136 tristate 'UDP-Lite protocol connection tracking support'
137 depends on NETFILTER_ADVANCED
139 With this option enabled, the layer 3 independent connection
140 tracking code will be able to do state tracking on UDP-Lite
143 To compile it as a module, choose M here. If unsure, say N.
145 config NF_CONNTRACK_AMANDA
146 tristate "Amanda backup protocol support"
147 depends on NETFILTER_ADVANCED
149 select TEXTSEARCH_KMP
151 If you are running the Amanda backup package <http://www.amanda.org/>
152 on this machine or machines that will be MASQUERADED through this
153 machine, then you may want to enable this feature. This allows the
154 connection tracking and natting code to allow the sub-channels that
155 Amanda requires for communication of the backup data, messages and
158 To compile it as a module, choose M here. If unsure, say N.
160 config NF_CONNTRACK_FTP
161 tristate "FTP protocol support"
162 default m if NETFILTER_ADVANCED=n
164 Tracking FTP connections is problematic: special helpers are
165 required for tracking them, and doing masquerading and other forms
166 of Network Address Translation on them.
168 This is FTP support on Layer 3 independent connection tracking.
169 Layer 3 independent connection tracking is experimental scheme
170 which generalize ip_conntrack to support other layer 3 protocols.
172 To compile it as a module, choose M here. If unsure, say N.
174 config NF_CONNTRACK_H323
175 tristate "H.323 protocol support"
176 depends on (IPV6 || IPV6=n)
177 depends on NETFILTER_ADVANCED
179 H.323 is a VoIP signalling protocol from ITU-T. As one of the most
180 important VoIP protocols, it is widely used by voice hardware and
181 software including voice gateways, IP phones, Netmeeting, OpenPhone,
184 With this module you can support H.323 on a connection tracking/NAT
187 This module supports RAS, Fast Start, H.245 Tunnelling, Call
188 Forwarding, RTP/RTCP and T.120 based audio, video, fax, chat,
189 whiteboard, file transfer, etc. For more information, please
190 visit http://nath323.sourceforge.net/.
192 To compile it as a module, choose M here. If unsure, say N.
194 config NF_CONNTRACK_IRC
195 tristate "IRC protocol support"
196 default m if NETFILTER_ADVANCED=n
198 There is a commonly-used extension to IRC called
199 Direct Client-to-Client Protocol (DCC). This enables users to send
200 files to each other, and also chat to each other without the need
201 of a server. DCC Sending is used anywhere you send files over IRC,
202 and DCC Chat is most commonly used by Eggdrop bots. If you are
203 using NAT, this extension will enable you to send files and initiate
204 chats. Note that you do NOT need this extension to get files or
205 have others initiate chats, or everything else in IRC.
207 To compile it as a module, choose M here. If unsure, say N.
209 config NF_CONNTRACK_NETBIOS_NS
210 tristate "NetBIOS name service protocol support"
211 depends on NETFILTER_ADVANCED
213 NetBIOS name service requests are sent as broadcast messages from an
214 unprivileged port and responded to with unicast messages to the
215 same port. This make them hard to firewall properly because connection
216 tracking doesn't deal with broadcasts. This helper tracks locally
217 originating NetBIOS name service requests and the corresponding
218 responses. It relies on correct IP address configuration, specifically
219 netmask and broadcast address. When properly configured, the output
220 of "ip address show" should look similar to this:
222 $ ip -4 address show eth0
223 4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
224 inet 172.16.2.252/24 brd 172.16.2.255 scope global eth0
226 To compile it as a module, choose M here. If unsure, say N.
228 config NF_CONNTRACK_PPTP
229 tristate "PPtP protocol support"
230 depends on NETFILTER_ADVANCED
231 select NF_CT_PROTO_GRE
233 This module adds support for PPTP (Point to Point Tunnelling
234 Protocol, RFC2637) connection tracking and NAT.
236 If you are running PPTP sessions over a stateful firewall or NAT
237 box, you may want to enable this feature.
239 Please note that not all PPTP modes of operation are supported yet.
240 Specifically these limitations exist:
241 - Blindly assumes that control connections are always established
242 in PNS->PAC direction. This is a violation of RFC2637.
243 - Only supports a single call within each session
245 To compile it as a module, choose M here. If unsure, say N.
247 config NF_CONNTRACK_SANE
248 tristate "SANE protocol support (EXPERIMENTAL)"
249 depends on EXPERIMENTAL
250 depends on NETFILTER_ADVANCED
252 SANE is a protocol for remote access to scanners as implemented
253 by the 'saned' daemon. Like FTP, it uses separate control and
256 With this module you can support SANE on a connection tracking
259 To compile it as a module, choose M here. If unsure, say N.
261 config NF_CONNTRACK_SIP
262 tristate "SIP protocol support"
263 default m if NETFILTER_ADVANCED=n
265 SIP is an application-layer control protocol that can establish,
266 modify, and terminate multimedia sessions (conferences) such as
267 Internet telephony calls. With the ip_conntrack_sip and
268 the nf_nat_sip modules you can support the protocol on a connection
269 tracking/NATing firewall.
271 To compile it as a module, choose M here. If unsure, say N.
273 config NF_CONNTRACK_TFTP
274 tristate "TFTP protocol support"
275 depends on NETFILTER_ADVANCED
277 TFTP connection tracking helper, this is required depending
278 on how restrictive your ruleset is.
279 If you are using a tftp client behind -j SNAT or -j MASQUERADING
282 To compile it as a module, choose M here. If unsure, say N.
285 tristate 'Connection tracking netlink interface'
286 select NETFILTER_NETLINK
287 default m if NETFILTER_ADVANCED=n
289 This option enables support for a netlink-based userspace interface
293 # transparent proxy support
294 config NETFILTER_TPROXY
295 tristate "Transparent proxying support (EXPERIMENTAL)"
296 depends on EXPERIMENTAL
297 depends on IP_NF_MANGLE
298 depends on NETFILTER_ADVANCED
300 This option enables transparent proxying support, that is,
301 support for handling non-locally bound IPv4 TCP and UDP sockets.
302 For it to work you will have to configure certain iptables rules
303 and use policy routing. For more information on how to set it up
304 see Documentation/networking/tproxy.txt.
306 To compile it as a module, choose M here. If unsure, say N.
308 config NETFILTER_XTABLES
309 tristate "Netfilter Xtables support (required for ip_tables)"
310 default m if NETFILTER_ADVANCED=n
312 This is required if you intend to use any of ip_tables,
313 ip6_tables or arp_tables.
317 comment "Xtables combined modules"
319 config NETFILTER_XT_MARK
320 tristate 'nfmark target and match support'
321 default m if NETFILTER_ADVANCED=n
323 This option adds the "MARK" target and "mark" match.
325 Netfilter mark matching allows you to match packets based on the
326 "nfmark" value in the packet.
327 The target allows you to create rules in the "mangle" table which alter
328 the netfilter mark (nfmark) field associated with the packet.
330 Prior to routing, the nfmark can influence the routing method (see
331 "Use netfilter MARK value as routing key") and can also be used by
332 other subsystems to change their behavior.
334 config NETFILTER_XT_CONNMARK
335 tristate 'ctmark target and match support'
336 depends on NF_CONNTRACK
337 depends on NETFILTER_ADVANCED
338 select NF_CONNTRACK_MARK
340 This option adds the "CONNMARK" target and "connmark" match.
342 Netfilter allows you to store a mark value per connection (a.k.a.
343 ctmark), similarly to the packet mark (nfmark). Using this
344 target and match, you can set and match on this mark.
346 # alphabetically ordered list of targets
348 comment "Xtables targets"
350 config NETFILTER_XT_TARGET_CLASSIFY
351 tristate '"CLASSIFY" target support'
352 depends on NETFILTER_ADVANCED
354 This option adds a `CLASSIFY' target, which enables the user to set
355 the priority of a packet. Some qdiscs can use this value for
356 classification, among these are:
358 atm, cbq, dsmark, pfifo_fast, htb, prio
360 To compile it as a module, choose M here. If unsure, say N.
362 config NETFILTER_XT_TARGET_CONNMARK
363 tristate '"CONNMARK" target support'
364 depends on NF_CONNTRACK
365 depends on NETFILTER_ADVANCED
366 select NETFILTER_XT_CONNMARK
368 This is a backwards-compat option for the user's convenience
369 (e.g. when running oldconfig). It selects
370 CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
372 config NETFILTER_XT_TARGET_CONNSECMARK
373 tristate '"CONNSECMARK" target support'
374 depends on NF_CONNTRACK && NF_CONNTRACK_SECMARK
375 default m if NETFILTER_ADVANCED=n
377 The CONNSECMARK target copies security markings from packets
378 to connections, and restores security markings from connections
379 to packets (if the packets are not already marked). This would
380 normally be used in conjunction with the SECMARK target.
382 To compile it as a module, choose M here. If unsure, say N.
384 config NETFILTER_XT_TARGET_CT
385 tristate '"CT" target support'
386 depends on NF_CONNTRACK
387 depends on IP_NF_RAW || IP6_NF_RAW
388 depends on NETFILTER_ADVANCED
390 This options adds a `CT' target, which allows to specify initial
391 connection tracking parameters like events to be delivered and
392 the helper to be used.
394 To compile it as a module, choose M here. If unsure, say N.
396 config NETFILTER_XT_TARGET_DSCP
397 tristate '"DSCP" and "TOS" target support'
398 depends on IP_NF_MANGLE || IP6_NF_MANGLE
399 depends on NETFILTER_ADVANCED
401 This option adds a `DSCP' target, which allows you to manipulate
402 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
404 The DSCP field can have any value between 0x0 and 0x3f inclusive.
406 It also adds the "TOS" target, which allows you to create rules in
407 the "mangle" table which alter the Type Of Service field of an IPv4
408 or the Priority field of an IPv6 packet, prior to routing.
410 To compile it as a module, choose M here. If unsure, say N.
412 config NETFILTER_XT_TARGET_HL
413 tristate '"HL" hoplimit target support'
414 depends on IP_NF_MANGLE || IP6_NF_MANGLE
415 depends on NETFILTER_ADVANCED
417 This option adds the "HL" (for IPv6) and "TTL" (for IPv4)
418 targets, which enable the user to change the
419 hoplimit/time-to-live value of the IP header.
421 While it is safe to decrement the hoplimit/TTL value, the
422 modules also allow to increment and set the hoplimit value of
423 the header to arbitrary values. This is EXTREMELY DANGEROUS
424 since you can easily create immortal packets that loop
425 forever on the network.
427 config NETFILTER_XT_TARGET_LED
428 tristate '"LED" target support'
429 depends on LEDS_CLASS && LEDS_TRIGGERS
430 depends on NETFILTER_ADVANCED
432 This option adds a `LED' target, which allows you to blink LEDs in
433 response to particular packets passing through your machine.
435 This can be used to turn a spare LED into a network activity LED,
436 which only flashes in response to FTP transfers, for example. Or
437 you could have an LED which lights up for a minute or two every time
438 somebody connects to your machine via SSH.
440 You will need support for the "led" class to make this work.
442 To create an LED trigger for incoming SSH traffic:
443 iptables -A INPUT -p tcp --dport 22 -j LED --led-trigger-id ssh --led-delay 1000
445 Then attach the new trigger to an LED on your system:
446 echo netfilter-ssh > /sys/class/leds/<ledname>/trigger
448 For more information on the LEDs available on your system, see
449 Documentation/leds-class.txt
451 config NETFILTER_XT_TARGET_MARK
452 tristate '"MARK" target support'
453 depends on NETFILTER_ADVANCED
454 select NETFILTER_XT_MARK
456 This is a backwards-compat option for the user's convenience
457 (e.g. when running oldconfig). It selects
458 CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
460 config NETFILTER_XT_TARGET_NFLOG
461 tristate '"NFLOG" target support'
462 default m if NETFILTER_ADVANCED=n
463 select NETFILTER_NETLINK_LOG
465 This option enables the NFLOG target, which allows to LOG
466 messages through nfnetlink_log.
468 To compile it as a module, choose M here. If unsure, say N.
470 config NETFILTER_XT_TARGET_NFQUEUE
471 tristate '"NFQUEUE" target Support'
472 depends on NETFILTER_ADVANCED
474 This target replaced the old obsolete QUEUE target.
476 As opposed to QUEUE, it supports 65535 different queues,
479 To compile it as a module, choose M here. If unsure, say N.
481 config NETFILTER_XT_TARGET_NOTRACK
482 tristate '"NOTRACK" target support'
483 depends on IP_NF_RAW || IP6_NF_RAW
484 depends on NF_CONNTRACK
485 depends on NETFILTER_ADVANCED
487 The NOTRACK target allows a select rule to specify
488 which packets *not* to enter the conntrack/NAT
489 subsystem with all the consequences (no ICMP error tracking,
490 no protocol helpers for the selected packets).
492 If you want to compile it as a module, say M here and read
493 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
495 config NETFILTER_XT_TARGET_RATEEST
496 tristate '"RATEEST" target support'
497 depends on NETFILTER_ADVANCED
499 This option adds a `RATEEST' target, which allows to measure
500 rates similar to TC estimators. The `rateest' match can be
501 used to match on the measured rates.
503 To compile it as a module, choose M here. If unsure, say N.
505 config NETFILTER_XT_TARGET_TEE
506 tristate '"TEE" - packet cloning to alternate destiantion'
507 depends on NETFILTER_ADVANCED
508 depends on (IPV6 || IPV6=n)
510 This option adds a "TEE" target with which a packet can be cloned and
511 this clone be rerouted to another nexthop.
513 config NETFILTER_XT_TARGET_TPROXY
514 tristate '"TPROXY" target support (EXPERIMENTAL)'
515 depends on EXPERIMENTAL
516 depends on NETFILTER_TPROXY
517 depends on NETFILTER_XTABLES
518 depends on NETFILTER_ADVANCED
519 select NF_DEFRAG_IPV4
521 This option adds a `TPROXY' target, which is somewhat similar to
522 REDIRECT. It can only be used in the mangle table and is useful
523 to redirect traffic to a transparent proxy. It does _not_ depend
524 on Netfilter connection tracking and NAT, unlike REDIRECT.
526 To compile it as a module, choose M here. If unsure, say N.
528 config NETFILTER_XT_TARGET_TRACE
529 tristate '"TRACE" target support'
530 depends on IP_NF_RAW || IP6_NF_RAW
531 depends on NETFILTER_ADVANCED
533 The TRACE target allows you to mark packets so that the kernel
534 will log every rule which match the packets as those traverse
535 the tables, chains, rules.
537 If you want to compile it as a module, say M here and read
538 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
540 config NETFILTER_XT_TARGET_SECMARK
541 tristate '"SECMARK" target support'
542 depends on NETWORK_SECMARK
543 default m if NETFILTER_ADVANCED=n
545 The SECMARK target allows security marking of network
546 packets, for use with security subsystems.
548 To compile it as a module, choose M here. If unsure, say N.
550 config NETFILTER_XT_TARGET_TCPMSS
551 tristate '"TCPMSS" target support'
552 depends on (IPV6 || IPV6=n)
553 default m if NETFILTER_ADVANCED=n
555 This option adds a `TCPMSS' target, which allows you to alter the
556 MSS value of TCP SYN packets, to control the maximum size for that
557 connection (usually limiting it to your outgoing interface's MTU
560 This is used to overcome criminally braindead ISPs or servers which
561 block ICMP Fragmentation Needed packets. The symptoms of this
562 problem are that everything works fine from your Linux
563 firewall/router, but machines behind it can never exchange large
565 1) Web browsers connect, then hang with no data received.
566 2) Small mail works fine, but large emails hang.
567 3) ssh works fine, but scp hangs after initial handshaking.
569 Workaround: activate this option and add a rule to your firewall
572 iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
573 -j TCPMSS --clamp-mss-to-pmtu
575 To compile it as a module, choose M here. If unsure, say N.
577 config NETFILTER_XT_TARGET_TCPOPTSTRIP
578 tristate '"TCPOPTSTRIP" target support (EXPERIMENTAL)'
579 depends on EXPERIMENTAL
580 depends on IP_NF_MANGLE || IP6_NF_MANGLE
581 depends on NETFILTER_ADVANCED
583 This option adds a "TCPOPTSTRIP" target, which allows you to strip
584 TCP options from TCP packets.
586 # alphabetically ordered list of matches
588 comment "Xtables matches"
590 config NETFILTER_XT_MATCH_CLUSTER
591 tristate '"cluster" match support'
592 depends on NF_CONNTRACK
593 depends on NETFILTER_ADVANCED
595 This option allows you to build work-load-sharing clusters of
596 network servers/stateful firewalls without having a dedicated
597 load-balancing router/server/switch. Basically, this match returns
598 true when the packet must be handled by this cluster node. Thus,
599 all nodes see all packets and this match decides which node handles
600 what packets. The work-load sharing algorithm is based on source
603 If you say Y or M here, try `iptables -m cluster --help` for
606 config NETFILTER_XT_MATCH_COMMENT
607 tristate '"comment" match support'
608 depends on NETFILTER_ADVANCED
610 This option adds a `comment' dummy-match, which allows you to put
611 comments in your iptables ruleset.
613 If you want to compile it as a module, say M here and read
614 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
616 config NETFILTER_XT_MATCH_CONNBYTES
617 tristate '"connbytes" per-connection counter match support'
618 depends on NF_CONNTRACK
619 depends on NETFILTER_ADVANCED
622 This option adds a `connbytes' match, which allows you to match the
623 number of bytes and/or packets for each direction within a connection.
625 If you want to compile it as a module, say M here and read
626 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
628 config NETFILTER_XT_MATCH_CONNLIMIT
629 tristate '"connlimit" match support"'
630 depends on NF_CONNTRACK
631 depends on NETFILTER_ADVANCED
633 This match allows you to match against the number of parallel
634 connections to a server per client IP address (or address block).
636 config NETFILTER_XT_MATCH_CONNMARK
637 tristate '"connmark" connection mark match support'
638 depends on NF_CONNTRACK
639 depends on NETFILTER_ADVANCED
640 select NETFILTER_XT_CONNMARK
642 This is a backwards-compat option for the user's convenience
643 (e.g. when running oldconfig). It selects
644 CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
646 config NETFILTER_XT_MATCH_CONNTRACK
647 tristate '"conntrack" connection tracking match support'
648 depends on NF_CONNTRACK
649 default m if NETFILTER_ADVANCED=n
651 This is a general conntrack match module, a superset of the state match.
653 It allows matching on additional conntrack information, which is
654 useful in complex configurations, such as NAT gateways with multiple
655 internet links or tunnels.
657 To compile it as a module, choose M here. If unsure, say N.
659 config NETFILTER_XT_MATCH_DCCP
660 tristate '"dccp" protocol match support'
661 depends on NETFILTER_ADVANCED
664 With this option enabled, you will be able to use the iptables
665 `dccp' match in order to match on DCCP source/destination ports
668 If you want to compile it as a module, say M here and read
669 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
671 config NETFILTER_XT_MATCH_DSCP
672 tristate '"dscp" and "tos" match support'
673 depends on NETFILTER_ADVANCED
675 This option adds a `DSCP' match, which allows you to match against
676 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
678 The DSCP field can have any value between 0x0 and 0x3f inclusive.
680 It will also add a "tos" match, which allows you to match packets
681 based on the Type Of Service fields of the IPv4 packet (which share
682 the same bits as DSCP).
684 To compile it as a module, choose M here. If unsure, say N.
686 config NETFILTER_XT_MATCH_ESP
687 tristate '"esp" match support'
688 depends on NETFILTER_ADVANCED
690 This match extension allows you to match a range of SPIs
691 inside ESP header of IPSec packets.
693 To compile it as a module, choose M here. If unsure, say N.
695 config NETFILTER_XT_MATCH_HASHLIMIT
696 tristate '"hashlimit" match support'
697 depends on (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
698 depends on NETFILTER_ADVANCED
700 This option adds a `hashlimit' match.
702 As opposed to `limit', this match dynamically creates a hash table
703 of limit buckets, based on your selection of source/destination
704 addresses and/or ports.
706 It enables you to express policies like `10kpps for any given
707 destination address' or `500pps from any given source address'
710 config NETFILTER_XT_MATCH_HELPER
711 tristate '"helper" match support'
712 depends on NF_CONNTRACK
713 depends on NETFILTER_ADVANCED
715 Helper matching allows you to match packets in dynamic connections
716 tracked by a conntrack-helper, ie. ip_conntrack_ftp
718 To compile it as a module, choose M here. If unsure, say Y.
720 config NETFILTER_XT_MATCH_HL
721 tristate '"hl" hoplimit/TTL match support'
722 depends on NETFILTER_ADVANCED
724 HL matching allows you to match packets based on the hoplimit
725 in the IPv6 header, or the time-to-live field in the IPv4
726 header of the packet.
728 config NETFILTER_XT_MATCH_IPRANGE
729 tristate '"iprange" address range match support'
730 depends on NETFILTER_ADVANCED
732 This option adds a "iprange" match, which allows you to match based on
733 an IP address range. (Normal iptables only matches on single addresses
734 with an optional mask.)
738 config NETFILTER_XT_MATCH_LENGTH
739 tristate '"length" match support'
740 depends on NETFILTER_ADVANCED
742 This option allows you to match the length of a packet against a
743 specific value or range of values.
745 To compile it as a module, choose M here. If unsure, say N.
747 config NETFILTER_XT_MATCH_LIMIT
748 tristate '"limit" match support'
749 depends on NETFILTER_ADVANCED
751 limit matching allows you to control the rate at which a rule can be
752 matched: mainly useful in combination with the LOG target ("LOG
753 target support", below) and to avoid some Denial of Service attacks.
755 To compile it as a module, choose M here. If unsure, say N.
757 config NETFILTER_XT_MATCH_MAC
758 tristate '"mac" address match support'
759 depends on NETFILTER_ADVANCED
761 MAC matching allows you to match packets based on the source
762 Ethernet address of the packet.
764 To compile it as a module, choose M here. If unsure, say N.
766 config NETFILTER_XT_MATCH_MARK
767 tristate '"mark" match support'
768 depends on NETFILTER_ADVANCED
769 select NETFILTER_XT_MARK
771 This is a backwards-compat option for the user's convenience
772 (e.g. when running oldconfig). It selects
773 CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
775 config NETFILTER_XT_MATCH_MULTIPORT
776 tristate '"multiport" Multiple port match support'
777 depends on NETFILTER_ADVANCED
779 Multiport matching allows you to match TCP or UDP packets based on
780 a series of source or destination ports: normally a rule can only
781 match a single range of ports.
783 To compile it as a module, choose M here. If unsure, say N.
785 config NETFILTER_XT_MATCH_OSF
786 tristate '"osf" Passive OS fingerprint match'
787 depends on NETFILTER_ADVANCED && NETFILTER_NETLINK
789 This option selects the Passive OS Fingerprinting match module
790 that allows to passively match the remote operating system by
791 analyzing incoming TCP SYN packets.
793 Rules and loading software can be downloaded from
794 http://www.ioremap.net/projects/osf
796 To compile it as a module, choose M here. If unsure, say N.
798 config NETFILTER_XT_MATCH_OWNER
799 tristate '"owner" match support'
800 depends on NETFILTER_ADVANCED
802 Socket owner matching allows you to match locally-generated packets
803 based on who created the socket: the user or group. It is also
804 possible to check whether a socket actually exists.
806 config NETFILTER_XT_MATCH_POLICY
807 tristate 'IPsec "policy" match support'
809 default m if NETFILTER_ADVANCED=n
811 Policy matching allows you to match packets based on the
812 IPsec policy that was used during decapsulation/will
813 be used during encapsulation.
815 To compile it as a module, choose M here. If unsure, say N.
817 config NETFILTER_XT_MATCH_PHYSDEV
818 tristate '"physdev" match support'
819 depends on BRIDGE && BRIDGE_NETFILTER
820 depends on NETFILTER_ADVANCED
822 Physdev packet matching matches against the physical bridge ports
823 the IP packet arrived on or will leave by.
825 To compile it as a module, choose M here. If unsure, say N.
827 config NETFILTER_XT_MATCH_PKTTYPE
828 tristate '"pkttype" packet type match support'
829 depends on NETFILTER_ADVANCED
831 Packet type matching allows you to match a packet by
832 its "class", eg. BROADCAST, MULTICAST, ...
835 iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG
837 To compile it as a module, choose M here. If unsure, say N.
839 config NETFILTER_XT_MATCH_QUOTA
840 tristate '"quota" match support'
841 depends on NETFILTER_ADVANCED
843 This option adds a `quota' match, which allows to match on a
846 If you want to compile it as a module, say M here and read
847 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
849 config NETFILTER_XT_MATCH_RATEEST
850 tristate '"rateest" match support'
851 depends on NETFILTER_ADVANCED
852 select NETFILTER_XT_TARGET_RATEEST
854 This option adds a `rateest' match, which allows to match on the
855 rate estimated by the RATEEST target.
857 To compile it as a module, choose M here. If unsure, say N.
859 config NETFILTER_XT_MATCH_REALM
860 tristate '"realm" match support'
861 depends on NETFILTER_ADVANCED
864 This option adds a `realm' match, which allows you to use the realm
865 key from the routing subsystem inside iptables.
867 This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option
870 If you want to compile it as a module, say M here and read
871 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
873 config NETFILTER_XT_MATCH_RECENT
874 tristate '"recent" match support'
875 depends on NETFILTER_ADVANCED
877 This match is used for creating one or many lists of recently
878 used addresses and then matching against that/those list(s).
880 Short options are available by using 'iptables -m recent -h'
881 Official Website: <http://snowman.net/projects/ipt_recent/>
883 config NETFILTER_XT_MATCH_SCTP
884 tristate '"sctp" protocol match support (EXPERIMENTAL)'
885 depends on EXPERIMENTAL
886 depends on NETFILTER_ADVANCED
889 With this option enabled, you will be able to use the
890 `sctp' match in order to match on SCTP source/destination ports
891 and SCTP chunk types.
893 If you want to compile it as a module, say M here and read
894 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
896 config NETFILTER_XT_MATCH_SOCKET
897 tristate '"socket" match support (EXPERIMENTAL)'
898 depends on EXPERIMENTAL
899 depends on NETFILTER_TPROXY
900 depends on NETFILTER_XTABLES
901 depends on NETFILTER_ADVANCED
902 depends on !NF_CONNTRACK || NF_CONNTRACK
903 select NF_DEFRAG_IPV4
905 This option adds a `socket' match, which can be used to match
906 packets for which a TCP or UDP socket lookup finds a valid socket.
907 It can be used in combination with the MARK target and policy
908 routing to implement full featured non-locally bound sockets.
910 To compile it as a module, choose M here. If unsure, say N.
912 config NETFILTER_XT_MATCH_STATE
913 tristate '"state" match support'
914 depends on NF_CONNTRACK
915 default m if NETFILTER_ADVANCED=n
917 Connection state matching allows you to match packets based on their
918 relationship to a tracked connection (ie. previous packets). This
919 is a powerful tool for packet classification.
921 To compile it as a module, choose M here. If unsure, say N.
923 config NETFILTER_XT_MATCH_STATISTIC
924 tristate '"statistic" match support'
925 depends on NETFILTER_ADVANCED
927 This option adds a `statistic' match, which allows you to match
928 on packets periodically or randomly with a given percentage.
930 To compile it as a module, choose M here. If unsure, say N.
932 config NETFILTER_XT_MATCH_STRING
933 tristate '"string" match support'
934 depends on NETFILTER_ADVANCED
936 select TEXTSEARCH_KMP
938 select TEXTSEARCH_FSM
940 This option adds a `string' match, which allows you to look for
941 pattern matchings in packets.
943 To compile it as a module, choose M here. If unsure, say N.
945 config NETFILTER_XT_MATCH_TCPMSS
946 tristate '"tcpmss" match support'
947 depends on NETFILTER_ADVANCED
949 This option adds a `tcpmss' match, which allows you to examine the
950 MSS value of TCP SYN packets, which control the maximum packet size
953 To compile it as a module, choose M here. If unsure, say N.
955 config NETFILTER_XT_MATCH_TIME
956 tristate '"time" match support'
957 depends on NETFILTER_ADVANCED
959 This option adds a "time" match, which allows you to match based on
960 the packet arrival time (at the machine which netfilter is running)
961 on) or departure time/date (for locally generated packets).
963 If you say Y here, try `iptables -m time --help` for
966 If you want to compile it as a module, say M here.
969 config NETFILTER_XT_MATCH_U32
970 tristate '"u32" match support'
971 depends on NETFILTER_ADVANCED
973 u32 allows you to extract quantities of up to 4 bytes from a packet,
974 AND them with specified masks, shift them by specified amounts and
975 test whether the results are in any of a set of specified ranges.
976 The specification of what to extract is general enough to skip over
977 headers with lengths stored in the packet, as in IP or TCP header
980 Details and examples are in the kernel module source.
982 endif # NETFILTER_XTABLES
986 source "net/netfilter/ipvs/Kconfig"