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 paramater 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_EVENTS
87 bool "Connection tracking events"
88 depends on NETFILTER_ADVANCED
90 If this option is enabled, the connection tracking code will
91 provide a notifier chain that can be used by other kernel code
92 to get notified about changes in the connection tracking state.
96 config NF_CT_PROTO_DCCP
97 tristate 'DCCP protocol connection tracking support (EXPERIMENTAL)'
98 depends on EXPERIMENTAL
99 depends on NETFILTER_ADVANCED
102 With this option enabled, the layer 3 independent connection
103 tracking code will be able to do state tracking on DCCP connections.
107 config NF_CT_PROTO_GRE
110 config NF_CT_PROTO_SCTP
111 tristate 'SCTP protocol connection tracking support (EXPERIMENTAL)'
112 depends on EXPERIMENTAL
113 depends on NETFILTER_ADVANCED
116 With this option enabled, the layer 3 independent connection
117 tracking code will be able to do state tracking on SCTP connections.
119 If you want to compile it as a module, say M here and read
120 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
122 config NF_CT_PROTO_UDPLITE
123 tristate 'UDP-Lite protocol connection tracking support'
124 depends on NETFILTER_ADVANCED
126 With this option enabled, the layer 3 independent connection
127 tracking code will be able to do state tracking on UDP-Lite
130 To compile it as a module, choose M here. If unsure, say N.
132 config NF_CONNTRACK_AMANDA
133 tristate "Amanda backup protocol support"
134 depends on NETFILTER_ADVANCED
136 select TEXTSEARCH_KMP
138 If you are running the Amanda backup package <http://www.amanda.org/>
139 on this machine or machines that will be MASQUERADED through this
140 machine, then you may want to enable this feature. This allows the
141 connection tracking and natting code to allow the sub-channels that
142 Amanda requires for communication of the backup data, messages and
145 To compile it as a module, choose M here. If unsure, say N.
147 config NF_CONNTRACK_FTP
148 tristate "FTP protocol support"
149 default m if NETFILTER_ADVANCED=n
151 Tracking FTP connections is problematic: special helpers are
152 required for tracking them, and doing masquerading and other forms
153 of Network Address Translation on them.
155 This is FTP support on Layer 3 independent connection tracking.
156 Layer 3 independent connection tracking is experimental scheme
157 which generalize ip_conntrack to support other layer 3 protocols.
159 To compile it as a module, choose M here. If unsure, say N.
161 config NF_CONNTRACK_H323
162 tristate "H.323 protocol support"
163 depends on (IPV6 || IPV6=n)
164 depends on NETFILTER_ADVANCED
166 H.323 is a VoIP signalling protocol from ITU-T. As one of the most
167 important VoIP protocols, it is widely used by voice hardware and
168 software including voice gateways, IP phones, Netmeeting, OpenPhone,
171 With this module you can support H.323 on a connection tracking/NAT
174 This module supports RAS, Fast Start, H.245 Tunnelling, Call
175 Forwarding, RTP/RTCP and T.120 based audio, video, fax, chat,
176 whiteboard, file transfer, etc. For more information, please
177 visit http://nath323.sourceforge.net/.
179 To compile it as a module, choose M here. If unsure, say N.
181 config NF_CONNTRACK_IRC
182 tristate "IRC protocol support"
183 default m if NETFILTER_ADVANCED=n
185 There is a commonly-used extension to IRC called
186 Direct Client-to-Client Protocol (DCC). This enables users to send
187 files to each other, and also chat to each other without the need
188 of a server. DCC Sending is used anywhere you send files over IRC,
189 and DCC Chat is most commonly used by Eggdrop bots. If you are
190 using NAT, this extension will enable you to send files and initiate
191 chats. Note that you do NOT need this extension to get files or
192 have others initiate chats, or everything else in IRC.
194 To compile it as a module, choose M here. If unsure, say N.
196 config NF_CONNTRACK_NETBIOS_NS
197 tristate "NetBIOS name service protocol support"
198 depends on NETFILTER_ADVANCED
200 NetBIOS name service requests are sent as broadcast messages from an
201 unprivileged port and responded to with unicast messages to the
202 same port. This make them hard to firewall properly because connection
203 tracking doesn't deal with broadcasts. This helper tracks locally
204 originating NetBIOS name service requests and the corresponding
205 responses. It relies on correct IP address configuration, specifically
206 netmask and broadcast address. When properly configured, the output
207 of "ip address show" should look similar to this:
209 $ ip -4 address show eth0
210 4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
211 inet 172.16.2.252/24 brd 172.16.2.255 scope global eth0
213 To compile it as a module, choose M here. If unsure, say N.
215 config NF_CONNTRACK_PPTP
216 tristate "PPtP protocol support"
217 depends on NETFILTER_ADVANCED
218 select NF_CT_PROTO_GRE
220 This module adds support for PPTP (Point to Point Tunnelling
221 Protocol, RFC2637) connection tracking and NAT.
223 If you are running PPTP sessions over a stateful firewall or NAT
224 box, you may want to enable this feature.
226 Please note that not all PPTP modes of operation are supported yet.
227 Specifically these limitations exist:
228 - Blindly assumes that control connections are always established
229 in PNS->PAC direction. This is a violation of RFC2637.
230 - Only supports a single call within each session
232 To compile it as a module, choose M here. If unsure, say N.
234 config NF_CONNTRACK_SANE
235 tristate "SANE protocol support (EXPERIMENTAL)"
236 depends on EXPERIMENTAL
237 depends on NETFILTER_ADVANCED
239 SANE is a protocol for remote access to scanners as implemented
240 by the 'saned' daemon. Like FTP, it uses separate control and
243 With this module you can support SANE on a connection tracking
246 To compile it as a module, choose M here. If unsure, say N.
248 config NF_CONNTRACK_SIP
249 tristate "SIP protocol support"
250 default m if NETFILTER_ADVANCED=n
252 SIP is an application-layer control protocol that can establish,
253 modify, and terminate multimedia sessions (conferences) such as
254 Internet telephony calls. With the ip_conntrack_sip and
255 the nf_nat_sip modules you can support the protocol on a connection
256 tracking/NATing firewall.
258 To compile it as a module, choose M here. If unsure, say N.
260 config NF_CONNTRACK_TFTP
261 tristate "TFTP protocol support"
262 depends on NETFILTER_ADVANCED
264 TFTP connection tracking helper, this is required depending
265 on how restrictive your ruleset is.
266 If you are using a tftp client behind -j SNAT or -j MASQUERADING
269 To compile it as a module, choose M here. If unsure, say N.
272 tristate 'Connection tracking netlink interface'
273 select NETFILTER_NETLINK
274 depends on NF_NAT=n || NF_NAT
275 default m if NETFILTER_ADVANCED=n
277 This option enables support for a netlink-based userspace interface
279 # transparent proxy support
280 config NETFILTER_TPROXY
281 tristate "Transparent proxying support (EXPERIMENTAL)"
282 depends on EXPERIMENTAL
283 depends on IP_NF_MANGLE
284 depends on NETFILTER_ADVANCED
286 This option enables transparent proxying support, that is,
287 support for handling non-locally bound IPv4 TCP and UDP sockets.
288 For it to work you will have to configure certain iptables rules
289 and use policy routing. For more information on how to set it up
290 see Documentation/networking/tproxy.txt.
292 To compile it as a module, choose M here. If unsure, say N.
296 config NETFILTER_XTABLES
297 tristate "Netfilter Xtables support (required for ip_tables)"
298 default m if NETFILTER_ADVANCED=n
300 This is required if you intend to use any of ip_tables,
301 ip6_tables or arp_tables.
305 # alphabetically ordered list of targets
307 config NETFILTER_XT_TARGET_CLASSIFY
308 tristate '"CLASSIFY" target support'
309 depends on NETFILTER_ADVANCED
311 This option adds a `CLASSIFY' target, which enables the user to set
312 the priority of a packet. Some qdiscs can use this value for
313 classification, among these are:
315 atm, cbq, dsmark, pfifo_fast, htb, prio
317 To compile it as a module, choose M here. If unsure, say N.
319 config NETFILTER_XT_TARGET_CONNMARK
320 tristate '"CONNMARK" target support'
321 depends on IP_NF_MANGLE || IP6_NF_MANGLE
322 depends on NF_CONNTRACK
323 depends on NETFILTER_ADVANCED
324 select NF_CONNTRACK_MARK
326 This option adds a `CONNMARK' target, which allows one to manipulate
327 the connection mark value. Similar to the MARK target, but
328 affects the connection mark value rather than the packet mark value.
330 If you want to compile it as a module, say M here and read
331 <file:Documentation/kbuild/modules.txt>. The module will be called
332 ipt_CONNMARK.ko. If unsure, say `N'.
334 config NETFILTER_XT_TARGET_CONNSECMARK
335 tristate '"CONNSECMARK" target support'
336 depends on NF_CONNTRACK && NF_CONNTRACK_SECMARK
337 default m if NETFILTER_ADVANCED=n
339 The CONNSECMARK target copies security markings from packets
340 to connections, and restores security markings from connections
341 to packets (if the packets are not already marked). This would
342 normally be used in conjunction with the SECMARK target.
344 To compile it as a module, choose M here. If unsure, say N.
346 config NETFILTER_XT_TARGET_DSCP
347 tristate '"DSCP" and "TOS" target support'
348 depends on IP_NF_MANGLE || IP6_NF_MANGLE
349 depends on NETFILTER_ADVANCED
351 This option adds a `DSCP' target, which allows you to manipulate
352 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
354 The DSCP field can have any value between 0x0 and 0x3f inclusive.
356 It also adds the "TOS" target, which allows you to create rules in
357 the "mangle" table which alter the Type Of Service field of an IPv4
358 or the Priority field of an IPv6 packet, prior to routing.
360 To compile it as a module, choose M here. If unsure, say N.
362 config NETFILTER_XT_TARGET_MARK
363 tristate '"MARK" target support'
364 default m if NETFILTER_ADVANCED=n
366 This option adds a `MARK' target, which allows you to create rules
367 in the `mangle' table which alter the netfilter mark (nfmark) field
368 associated with the packet prior to routing. This can change
369 the routing method (see `Use netfilter MARK value as routing
370 key') and can also be used by other subsystems to change their
373 To compile it as a module, choose M here. If unsure, say N.
375 config NETFILTER_XT_TARGET_NFLOG
376 tristate '"NFLOG" target support'
377 default m if NETFILTER_ADVANCED=n
379 This option enables the NFLOG target, which allows to LOG
380 messages through the netfilter logging API, which can use
381 either the old LOG target, the old ULOG target or nfnetlink_log
384 To compile it as a module, choose M here. If unsure, say N.
386 config NETFILTER_XT_TARGET_NFQUEUE
387 tristate '"NFQUEUE" target Support'
388 depends on NETFILTER_ADVANCED
390 This target replaced the old obsolete QUEUE target.
392 As opposed to QUEUE, it supports 65535 different queues,
395 To compile it as a module, choose M here. If unsure, say N.
397 config NETFILTER_XT_TARGET_NOTRACK
398 tristate '"NOTRACK" target support'
399 depends on IP_NF_RAW || IP6_NF_RAW
400 depends on NF_CONNTRACK
401 depends on NETFILTER_ADVANCED
403 The NOTRACK target allows a select rule to specify
404 which packets *not* to enter the conntrack/NAT
405 subsystem with all the consequences (no ICMP error tracking,
406 no protocol helpers for the selected packets).
408 If you want to compile it as a module, say M here and read
409 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
411 config NETFILTER_XT_TARGET_RATEEST
412 tristate '"RATEEST" target support'
413 depends on NETFILTER_ADVANCED
415 This option adds a `RATEEST' target, which allows to measure
416 rates similar to TC estimators. The `rateest' match can be
417 used to match on the measured rates.
419 To compile it as a module, choose M here. If unsure, say N.
421 config NETFILTER_XT_TARGET_TPROXY
422 tristate '"TPROXY" target support (EXPERIMENTAL)'
423 depends on EXPERIMENTAL
424 depends on NETFILTER_TPROXY
425 depends on NETFILTER_XTABLES
426 depends on NETFILTER_ADVANCED
427 select NF_DEFRAG_IPV4
429 This option adds a `TPROXY' target, which is somewhat similar to
430 REDIRECT. It can only be used in the mangle table and is useful
431 to redirect traffic to a transparent proxy. It does _not_ depend
432 on Netfilter connection tracking and NAT, unlike REDIRECT.
434 To compile it as a module, choose M here. If unsure, say N.
436 config NETFILTER_XT_TARGET_TRACE
437 tristate '"TRACE" target support'
438 depends on IP_NF_RAW || IP6_NF_RAW
439 depends on NETFILTER_ADVANCED
441 The TRACE target allows you to mark packets so that the kernel
442 will log every rule which match the packets as those traverse
443 the tables, chains, rules.
445 If you want to compile it as a module, say M here and read
446 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
448 config NETFILTER_XT_TARGET_SECMARK
449 tristate '"SECMARK" target support'
450 depends on NETWORK_SECMARK
451 default m if NETFILTER_ADVANCED=n
453 The SECMARK target allows security marking of network
454 packets, for use with security subsystems.
456 To compile it as a module, choose M here. If unsure, say N.
458 config NETFILTER_XT_TARGET_TCPMSS
459 tristate '"TCPMSS" target support'
460 depends on (IPV6 || IPV6=n)
461 default m if NETFILTER_ADVANCED=n
463 This option adds a `TCPMSS' target, which allows you to alter the
464 MSS value of TCP SYN packets, to control the maximum size for that
465 connection (usually limiting it to your outgoing interface's MTU
468 This is used to overcome criminally braindead ISPs or servers which
469 block ICMP Fragmentation Needed packets. The symptoms of this
470 problem are that everything works fine from your Linux
471 firewall/router, but machines behind it can never exchange large
473 1) Web browsers connect, then hang with no data received.
474 2) Small mail works fine, but large emails hang.
475 3) ssh works fine, but scp hangs after initial handshaking.
477 Workaround: activate this option and add a rule to your firewall
480 iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
481 -j TCPMSS --clamp-mss-to-pmtu
483 To compile it as a module, choose M here. If unsure, say N.
485 config NETFILTER_XT_TARGET_TCPOPTSTRIP
486 tristate '"TCPOPTSTRIP" target support (EXPERIMENTAL)'
487 depends on EXPERIMENTAL
488 depends on IP_NF_MANGLE || IP6_NF_MANGLE
489 depends on NETFILTER_ADVANCED
491 This option adds a "TCPOPTSTRIP" target, which allows you to strip
492 TCP options from TCP packets.
494 config NETFILTER_XT_MATCH_COMMENT
495 tristate '"comment" match support'
496 depends on NETFILTER_ADVANCED
498 This option adds a `comment' dummy-match, which allows you to put
499 comments in your iptables ruleset.
501 If you want to compile it as a module, say M here and read
502 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
504 config NETFILTER_XT_MATCH_CONNBYTES
505 tristate '"connbytes" per-connection counter match support'
506 depends on NF_CONNTRACK
507 depends on NETFILTER_ADVANCED
510 This option adds a `connbytes' match, which allows you to match the
511 number of bytes and/or packets for each direction within a connection.
513 If you want to compile it as a module, say M here and read
514 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
516 config NETFILTER_XT_MATCH_CONNLIMIT
517 tristate '"connlimit" match support"'
518 depends on NF_CONNTRACK
519 depends on NETFILTER_ADVANCED
521 This match allows you to match against the number of parallel
522 connections to a server per client IP address (or address block).
524 config NETFILTER_XT_MATCH_CONNMARK
525 tristate '"connmark" connection mark match support'
526 depends on NF_CONNTRACK
527 depends on NETFILTER_ADVANCED
528 select NF_CONNTRACK_MARK
530 This option adds a `connmark' match, which allows you to match the
531 connection mark value previously set for the session by `CONNMARK'.
533 If you want to compile it as a module, say M here and read
534 <file:Documentation/kbuild/modules.txt>. The module will be called
535 ipt_connmark.ko. If unsure, say `N'.
537 config NETFILTER_XT_MATCH_CONNTRACK
538 tristate '"conntrack" connection tracking match support'
539 depends on NF_CONNTRACK
540 default m if NETFILTER_ADVANCED=n
542 This is a general conntrack match module, a superset of the state match.
544 It allows matching on additional conntrack information, which is
545 useful in complex configurations, such as NAT gateways with multiple
546 internet links or tunnels.
548 To compile it as a module, choose M here. If unsure, say N.
550 config NETFILTER_XT_MATCH_DCCP
551 tristate '"dccp" protocol match support'
552 depends on NETFILTER_ADVANCED
555 With this option enabled, you will be able to use the iptables
556 `dccp' match in order to match on DCCP source/destination ports
559 If you want to compile it as a module, say M here and read
560 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
562 config NETFILTER_XT_MATCH_DSCP
563 tristate '"dscp" and "tos" match support'
564 depends on NETFILTER_ADVANCED
566 This option adds a `DSCP' match, which allows you to match against
567 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
569 The DSCP field can have any value between 0x0 and 0x3f inclusive.
571 It will also add a "tos" match, which allows you to match packets
572 based on the Type Of Service fields of the IPv4 packet (which share
573 the same bits as DSCP).
575 To compile it as a module, choose M here. If unsure, say N.
577 config NETFILTER_XT_MATCH_ESP
578 tristate '"esp" match support'
579 depends on NETFILTER_ADVANCED
581 This match extension allows you to match a range of SPIs
582 inside ESP header of IPSec packets.
584 To compile it as a module, choose M here. If unsure, say N.
586 config NETFILTER_XT_MATCH_HASHLIMIT
587 tristate '"hashlimit" match support'
588 depends on (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
589 depends on NETFILTER_ADVANCED
591 This option adds a `hashlimit' match.
593 As opposed to `limit', this match dynamically creates a hash table
594 of limit buckets, based on your selection of source/destination
595 addresses and/or ports.
597 It enables you to express policies like `10kpps for any given
598 destination address' or `500pps from any given source address'
601 config NETFILTER_XT_MATCH_HELPER
602 tristate '"helper" match support'
603 depends on NF_CONNTRACK
604 depends on NETFILTER_ADVANCED
606 Helper matching allows you to match packets in dynamic connections
607 tracked by a conntrack-helper, ie. ip_conntrack_ftp
609 To compile it as a module, choose M here. If unsure, say Y.
611 config NETFILTER_XT_MATCH_IPRANGE
612 tristate '"iprange" address range match support'
613 depends on NETFILTER_ADVANCED
615 This option adds a "iprange" match, which allows you to match based on
616 an IP address range. (Normal iptables only matches on single addresses
617 with an optional mask.)
621 config NETFILTER_XT_MATCH_LENGTH
622 tristate '"length" match support'
623 depends on NETFILTER_ADVANCED
625 This option allows you to match the length of a packet against a
626 specific value or range of values.
628 To compile it as a module, choose M here. If unsure, say N.
630 config NETFILTER_XT_MATCH_LIMIT
631 tristate '"limit" match support'
632 depends on NETFILTER_ADVANCED
634 limit matching allows you to control the rate at which a rule can be
635 matched: mainly useful in combination with the LOG target ("LOG
636 target support", below) and to avoid some Denial of Service attacks.
638 To compile it as a module, choose M here. If unsure, say N.
640 config NETFILTER_XT_MATCH_MAC
641 tristate '"mac" address match support'
642 depends on NETFILTER_ADVANCED
644 MAC matching allows you to match packets based on the source
645 Ethernet address of the packet.
647 To compile it as a module, choose M here. If unsure, say N.
649 config NETFILTER_XT_MATCH_MARK
650 tristate '"mark" match support'
651 default m if NETFILTER_ADVANCED=n
653 Netfilter mark matching allows you to match packets based on the
654 `nfmark' value in the packet. This can be set by the MARK target
657 To compile it as a module, choose M here. If unsure, say N.
659 config NETFILTER_XT_MATCH_MULTIPORT
660 tristate '"multiport" Multiple port match support'
661 depends on NETFILTER_ADVANCED
663 Multiport matching allows you to match TCP or UDP packets based on
664 a series of source or destination ports: normally a rule can only
665 match a single range of ports.
667 To compile it as a module, choose M here. If unsure, say N.
669 config NETFILTER_XT_MATCH_OWNER
670 tristate '"owner" match support'
671 depends on NETFILTER_ADVANCED
673 Socket owner matching allows you to match locally-generated packets
674 based on who created the socket: the user or group. It is also
675 possible to check whether a socket actually exists.
677 config NETFILTER_XT_MATCH_POLICY
678 tristate 'IPsec "policy" match support'
680 default m if NETFILTER_ADVANCED=n
682 Policy matching allows you to match packets based on the
683 IPsec policy that was used during decapsulation/will
684 be used during encapsulation.
686 To compile it as a module, choose M here. If unsure, say N.
688 config NETFILTER_XT_MATCH_PHYSDEV
689 tristate '"physdev" match support'
690 depends on BRIDGE && BRIDGE_NETFILTER
691 depends on NETFILTER_ADVANCED
693 Physdev packet matching matches against the physical bridge ports
694 the IP packet arrived on or will leave by.
696 To compile it as a module, choose M here. If unsure, say N.
698 config NETFILTER_XT_MATCH_PKTTYPE
699 tristate '"pkttype" packet type match support'
700 depends on NETFILTER_ADVANCED
702 Packet type matching allows you to match a packet by
703 its "class", eg. BROADCAST, MULTICAST, ...
706 iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG
708 To compile it as a module, choose M here. If unsure, say N.
710 config NETFILTER_XT_MATCH_QUOTA
711 tristate '"quota" match support'
712 depends on NETFILTER_ADVANCED
714 This option adds a `quota' match, which allows to match on a
717 If you want to compile it as a module, say M here and read
718 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
720 config NETFILTER_XT_MATCH_RATEEST
721 tristate '"rateest" match support'
722 depends on NETFILTER_ADVANCED
723 select NETFILTER_XT_TARGET_RATEEST
725 This option adds a `rateest' match, which allows to match on the
726 rate estimated by the RATEEST target.
728 To compile it as a module, choose M here. If unsure, say N.
730 config NETFILTER_XT_MATCH_REALM
731 tristate '"realm" match support'
732 depends on NETFILTER_ADVANCED
735 This option adds a `realm' match, which allows you to use the realm
736 key from the routing subsystem inside iptables.
738 This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option
741 If you want to compile it as a module, say M here and read
742 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
744 config NETFILTER_XT_MATCH_RECENT
745 tristate '"recent" match support'
746 depends on NETFILTER_ADVANCED
748 This match is used for creating one or many lists of recently
749 used addresses and then matching against that/those list(s).
751 Short options are available by using 'iptables -m recent -h'
752 Official Website: <http://snowman.net/projects/ipt_recent/>
754 config NETFILTER_XT_MATCH_RECENT_PROC_COMPAT
755 bool 'Enable obsolete /proc/net/ipt_recent'
756 depends on NETFILTER_XT_MATCH_RECENT && PROC_FS
758 This option enables the old /proc/net/ipt_recent interface,
759 which has been obsoleted by /proc/net/xt_recent.
761 config NETFILTER_XT_MATCH_SCTP
762 tristate '"sctp" protocol match support (EXPERIMENTAL)'
763 depends on EXPERIMENTAL
764 depends on NETFILTER_ADVANCED
767 With this option enabled, you will be able to use the
768 `sctp' match in order to match on SCTP source/destination ports
769 and SCTP chunk types.
771 If you want to compile it as a module, say M here and read
772 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
774 config NETFILTER_XT_MATCH_SOCKET
775 tristate '"socket" match support (EXPERIMENTAL)'
776 depends on EXPERIMENTAL
777 depends on NETFILTER_TPROXY
778 depends on NETFILTER_XTABLES
779 depends on NETFILTER_ADVANCED
780 select NF_DEFRAG_IPV4
782 This option adds a `socket' match, which can be used to match
783 packets for which a TCP or UDP socket lookup finds a valid socket.
784 It can be used in combination with the MARK target and policy
785 routing to implement full featured non-locally bound sockets.
787 To compile it as a module, choose M here. If unsure, say N.
789 config NETFILTER_XT_MATCH_STATE
790 tristate '"state" match support'
791 depends on NF_CONNTRACK
792 default m if NETFILTER_ADVANCED=n
794 Connection state matching allows you to match packets based on their
795 relationship to a tracked connection (ie. previous packets). This
796 is a powerful tool for packet classification.
798 To compile it as a module, choose M here. If unsure, say N.
800 config NETFILTER_XT_MATCH_STATISTIC
801 tristate '"statistic" match support'
802 depends on NETFILTER_ADVANCED
804 This option adds a `statistic' match, which allows you to match
805 on packets periodically or randomly with a given percentage.
807 To compile it as a module, choose M here. If unsure, say N.
809 config NETFILTER_XT_MATCH_STRING
810 tristate '"string" match support'
811 depends on NETFILTER_ADVANCED
813 select TEXTSEARCH_KMP
815 select TEXTSEARCH_FSM
817 This option adds a `string' match, which allows you to look for
818 pattern matchings in packets.
820 To compile it as a module, choose M here. If unsure, say N.
822 config NETFILTER_XT_MATCH_TCPMSS
823 tristate '"tcpmss" match support'
824 depends on NETFILTER_ADVANCED
826 This option adds a `tcpmss' match, which allows you to examine the
827 MSS value of TCP SYN packets, which control the maximum packet size
830 To compile it as a module, choose M here. If unsure, say N.
832 config NETFILTER_XT_MATCH_TIME
833 tristate '"time" match support'
834 depends on NETFILTER_ADVANCED
836 This option adds a "time" match, which allows you to match based on
837 the packet arrival time (at the machine which netfilter is running)
838 on) or departure time/date (for locally generated packets).
840 If you say Y here, try `iptables -m time --help` for
843 If you want to compile it as a module, say M here.
846 config NETFILTER_XT_MATCH_U32
847 tristate '"u32" match support'
848 depends on NETFILTER_ADVANCED
850 u32 allows you to extract quantities of up to 4 bytes from a packet,
851 AND them with specified masks, shift them by specified amounts and
852 test whether the results are in any of a set of specified ranges.
853 The specification of what to extract is general enough to skip over
854 headers with lengths stored in the packet, as in IP or TCP header
857 Details and examples are in the kernel module source.
859 endif # NETFILTER_XTABLES