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 (except for Fast NAT). It can also be used to
37 enhance packet filtering (see `Connection state match support'
40 To compile it as a module, choose M here. If unsure, say N.
43 bool "Connection tracking flow accounting"
44 depends on NETFILTER_ADVANCED
45 depends on NF_CONNTRACK
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
55 config NF_CONNTRACK_MARK
56 bool 'Connection mark tracking support'
57 depends on NETFILTER_ADVANCED
58 depends on NF_CONNTRACK
60 This option enables support for connection marks, used by the
61 `CONNMARK' target and `connmark' match. Similar to the mark value
62 of packets, but this mark value is kept in the conntrack session
63 instead of the individual packets.
65 config NF_CONNTRACK_SECMARK
66 bool 'Connection tracking security mark support'
67 depends on NF_CONNTRACK && NETWORK_SECMARK
68 default m if NETFILTER_ADVANCED=n
70 This option enables security markings to be applied to
71 connections. Typically they are copied to connections from
72 packets using the CONNSECMARK target and copied back from
73 connections to packets with the same target, with the packets
74 being originally labeled via SECMARK.
78 config NF_CONNTRACK_EVENTS
79 bool "Connection tracking events (EXPERIMENTAL)"
80 depends on EXPERIMENTAL && NF_CONNTRACK
81 depends on NETFILTER_ADVANCED
83 If this option is enabled, the connection tracking code will
84 provide a notifier chain that can be used by other kernel code
85 to get notified about changes in the connection tracking state.
89 config NF_CT_PROTO_GRE
91 depends on NF_CONNTRACK
93 config NF_CT_PROTO_SCTP
94 tristate 'SCTP protocol connection tracking support (EXPERIMENTAL)'
95 depends on EXPERIMENTAL && NF_CONNTRACK
96 depends on NETFILTER_ADVANCED
98 With this option enabled, the layer 3 independent connection
99 tracking code will be able to do state tracking on SCTP connections.
101 If you want to compile it as a module, say M here and read
102 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
104 config NF_CT_PROTO_UDPLITE
105 tristate 'UDP-Lite protocol connection tracking support (EXPERIMENTAL)'
106 depends on EXPERIMENTAL && NF_CONNTRACK
107 depends on NETFILTER_ADVANCED
109 With this option enabled, the layer 3 independent connection
110 tracking code will be able to do state tracking on UDP-Lite
113 To compile it as a module, choose M here. If unsure, say N.
115 config NF_CONNTRACK_AMANDA
116 tristate "Amanda backup protocol support"
117 depends on NF_CONNTRACK
118 depends on NETFILTER_ADVANCED
120 select TEXTSEARCH_KMP
122 If you are running the Amanda backup package <http://www.amanda.org/>
123 on this machine or machines that will be MASQUERADED through this
124 machine, then you may want to enable this feature. This allows the
125 connection tracking and natting code to allow the sub-channels that
126 Amanda requires for communication of the backup data, messages and
129 To compile it as a module, choose M here. If unsure, say N.
131 config NF_CONNTRACK_FTP
132 tristate "FTP protocol support"
133 depends on NF_CONNTRACK
134 default m if NETFILTER_ADVANCED=n
136 Tracking FTP connections is problematic: special helpers are
137 required for tracking them, and doing masquerading and other forms
138 of Network Address Translation on them.
140 This is FTP support on Layer 3 independent connection tracking.
141 Layer 3 independent connection tracking is experimental scheme
142 which generalize ip_conntrack to support other layer 3 protocols.
144 To compile it as a module, choose M here. If unsure, say N.
146 config NF_CONNTRACK_H323
147 tristate "H.323 protocol support (EXPERIMENTAL)"
148 depends on EXPERIMENTAL && NF_CONNTRACK && (IPV6 || IPV6=n)
149 depends on NETFILTER_ADVANCED
151 H.323 is a VoIP signalling protocol from ITU-T. As one of the most
152 important VoIP protocols, it is widely used by voice hardware and
153 software including voice gateways, IP phones, Netmeeting, OpenPhone,
156 With this module you can support H.323 on a connection tracking/NAT
159 This module supports RAS, Fast Start, H.245 Tunnelling, Call
160 Forwarding, RTP/RTCP and T.120 based audio, video, fax, chat,
161 whiteboard, file transfer, etc. For more information, please
162 visit http://nath323.sourceforge.net/.
164 To compile it as a module, choose M here. If unsure, say N.
166 config NF_CONNTRACK_IRC
167 tristate "IRC protocol support"
168 depends on NF_CONNTRACK
169 default m if NETFILTER_ADVANCED=n
171 There is a commonly-used extension to IRC called
172 Direct Client-to-Client Protocol (DCC). This enables users to send
173 files to each other, and also chat to each other without the need
174 of a server. DCC Sending is used anywhere you send files over IRC,
175 and DCC Chat is most commonly used by Eggdrop bots. If you are
176 using NAT, this extension will enable you to send files and initiate
177 chats. Note that you do NOT need this extension to get files or
178 have others initiate chats, or everything else in IRC.
180 To compile it as a module, choose M here. If unsure, say N.
182 config NF_CONNTRACK_NETBIOS_NS
183 tristate "NetBIOS name service protocol support (EXPERIMENTAL)"
184 depends on EXPERIMENTAL && NF_CONNTRACK
185 depends on NETFILTER_ADVANCED
187 NetBIOS name service requests are sent as broadcast messages from an
188 unprivileged port and responded to with unicast messages to the
189 same port. This make them hard to firewall properly because connection
190 tracking doesn't deal with broadcasts. This helper tracks locally
191 originating NetBIOS name service requests and the corresponding
192 responses. It relies on correct IP address configuration, specifically
193 netmask and broadcast address. When properly configured, the output
194 of "ip address show" should look similar to this:
196 $ ip -4 address show eth0
197 4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
198 inet 172.16.2.252/24 brd 172.16.2.255 scope global eth0
200 To compile it as a module, choose M here. If unsure, say N.
202 config NF_CONNTRACK_PPTP
203 tristate "PPtP protocol support"
204 depends on NF_CONNTRACK
205 depends on NETFILTER_ADVANCED
206 select NF_CT_PROTO_GRE
208 This module adds support for PPTP (Point to Point Tunnelling
209 Protocol, RFC2637) connection tracking and NAT.
211 If you are running PPTP sessions over a stateful firewall or NAT
212 box, you may want to enable this feature.
214 Please note that not all PPTP modes of operation are supported yet.
215 Specifically these limitations exist:
216 - Blindly assumes that control connections are always established
217 in PNS->PAC direction. This is a violation of RFC2637.
218 - Only supports a single call within each session
220 To compile it as a module, choose M here. If unsure, say N.
222 config NF_CONNTRACK_SANE
223 tristate "SANE protocol support (EXPERIMENTAL)"
224 depends on EXPERIMENTAL && NF_CONNTRACK
225 depends on NETFILTER_ADVANCED
227 SANE is a protocol for remote access to scanners as implemented
228 by the 'saned' daemon. Like FTP, it uses separate control and
231 With this module you can support SANE on a connection tracking
234 To compile it as a module, choose M here. If unsure, say N.
236 config NF_CONNTRACK_SIP
237 tristate "SIP protocol support (EXPERIMENTAL)"
238 depends on EXPERIMENTAL && NF_CONNTRACK
239 default m if NETFILTER_ADVANCED=n
241 SIP is an application-layer control protocol that can establish,
242 modify, and terminate multimedia sessions (conferences) such as
243 Internet telephony calls. With the ip_conntrack_sip and
244 the nf_nat_sip modules you can support the protocol on a connection
245 tracking/NATing firewall.
247 To compile it as a module, choose M here. If unsure, say N.
249 config NF_CONNTRACK_TFTP
250 tristate "TFTP protocol support"
251 depends on NF_CONNTRACK
252 depends on NETFILTER_ADVANCED
254 TFTP connection tracking helper, this is required depending
255 on how restrictive your ruleset is.
256 If you are using a tftp client behind -j SNAT or -j MASQUERADING
259 To compile it as a module, choose M here. If unsure, say N.
262 tristate 'Connection tracking netlink interface (EXPERIMENTAL)'
263 depends on EXPERIMENTAL && NF_CONNTRACK
264 select NETFILTER_NETLINK
265 depends on NF_NAT=n || NF_NAT
266 default m if NETFILTER_ADVANCED=n
268 This option enables support for a netlink-based userspace interface
270 config NETFILTER_XTABLES
271 tristate "Netfilter Xtables support (required for ip_tables)"
272 default m if NETFILTER_ADVANCED=n
274 This is required if you intend to use any of ip_tables,
275 ip6_tables or arp_tables.
277 # alphabetically ordered list of targets
279 config NETFILTER_XT_TARGET_CLASSIFY
280 tristate '"CLASSIFY" target support'
281 depends on NETFILTER_XTABLES
282 depends on NETFILTER_ADVANCED
284 This option adds a `CLASSIFY' target, which enables the user to set
285 the priority of a packet. Some qdiscs can use this value for
286 classification, among these are:
288 atm, cbq, dsmark, pfifo_fast, htb, prio
290 To compile it as a module, choose M here. If unsure, say N.
292 config NETFILTER_XT_TARGET_CONNMARK
293 tristate '"CONNMARK" target support'
294 depends on NETFILTER_XTABLES
295 depends on IP_NF_MANGLE || IP6_NF_MANGLE
296 depends on NF_CONNTRACK
297 depends on NETFILTER_ADVANCED
298 select NF_CONNTRACK_MARK
300 This option adds a `CONNMARK' target, which allows one to manipulate
301 the connection mark value. Similar to the MARK target, but
302 affects the connection mark value rather than the packet mark value.
304 If you want to compile it as a module, say M here and read
305 <file:Documentation/kbuild/modules.txt>. The module will be called
306 ipt_CONNMARK.ko. If unsure, say `N'.
308 config NETFILTER_XT_TARGET_DSCP
309 tristate '"DSCP" and "TOS" target support'
310 depends on NETFILTER_XTABLES
311 depends on IP_NF_MANGLE || IP6_NF_MANGLE
312 depends on NETFILTER_ADVANCED
314 This option adds a `DSCP' target, which allows you to manipulate
315 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
317 The DSCP field can have any value between 0x0 and 0x3f inclusive.
319 It also adds the "TOS" target, which allows you to create rules in
320 the "mangle" table which alter the Type Of Service field of an IPv4
321 or the Priority field of an IPv6 packet, prior to routing.
323 To compile it as a module, choose M here. If unsure, say N.
325 config NETFILTER_XT_TARGET_MARK
326 tristate '"MARK" target support'
327 depends on NETFILTER_XTABLES
328 default m if NETFILTER_ADVANCED=n
330 This option adds a `MARK' target, which allows you to create rules
331 in the `mangle' table which alter the netfilter mark (nfmark) field
332 associated with the packet prior to routing. This can change
333 the routing method (see `Use netfilter MARK value as routing
334 key') and can also be used by other subsystems to change their
337 To compile it as a module, choose M here. If unsure, say N.
339 config NETFILTER_XT_TARGET_NFQUEUE
340 tristate '"NFQUEUE" target Support'
341 depends on NETFILTER_XTABLES
342 depends on NETFILTER_ADVANCED
344 This target replaced the old obsolete QUEUE target.
346 As opposed to QUEUE, it supports 65535 different queues,
349 To compile it as a module, choose M here. If unsure, say N.
351 config NETFILTER_XT_TARGET_NFLOG
352 tristate '"NFLOG" target support'
353 depends on NETFILTER_XTABLES
354 default m if NETFILTER_ADVANCED=n
356 This option enables the NFLOG target, which allows to LOG
357 messages through the netfilter logging API, which can use
358 either the old LOG target, the old ULOG target or nfnetlink_log
361 To compile it as a module, choose M here. If unsure, say N.
363 config NETFILTER_XT_TARGET_NOTRACK
364 tristate '"NOTRACK" target support'
365 depends on NETFILTER_XTABLES
366 depends on IP_NF_RAW || IP6_NF_RAW
367 depends on NF_CONNTRACK
368 depends on NETFILTER_ADVANCED
370 The NOTRACK target allows a select rule to specify
371 which packets *not* to enter the conntrack/NAT
372 subsystem with all the consequences (no ICMP error tracking,
373 no protocol helpers for the selected packets).
375 If you want to compile it as a module, say M here and read
376 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
378 config NETFILTER_XT_TARGET_RATEEST
379 tristate '"RATEEST" target support'
380 depends on NETFILTER_XTABLES
382 This option adds a `RATEEST' target, which allows to measure
383 rates similar to TC estimators. The `rateest' match can be
384 used to match on the measured rates.
386 To compile it as a module, choose M here. If unsure, say N.
388 config NETFILTER_XT_TARGET_TRACE
389 tristate '"TRACE" target support'
390 depends on NETFILTER_XTABLES
391 depends on IP_NF_RAW || IP6_NF_RAW
392 depends on NETFILTER_ADVANCED
394 The TRACE target allows you to mark packets so that the kernel
395 will log every rule which match the packets as those traverse
396 the tables, chains, rules.
398 If you want to compile it as a module, say M here and read
399 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
401 config NETFILTER_XT_TARGET_SECMARK
402 tristate '"SECMARK" target support'
403 depends on NETFILTER_XTABLES && NETWORK_SECMARK
404 default m if NETFILTER_ADVANCED=n
406 The SECMARK target allows security marking of network
407 packets, for use with security subsystems.
409 To compile it as a module, choose M here. If unsure, say N.
411 config NETFILTER_XT_TARGET_CONNSECMARK
412 tristate '"CONNSECMARK" target support'
413 depends on NETFILTER_XTABLES && NF_CONNTRACK && NF_CONNTRACK_SECMARK
414 default m if NETFILTER_ADVANCED=n
416 The CONNSECMARK target copies security markings from packets
417 to connections, and restores security markings from connections
418 to packets (if the packets are not already marked). This would
419 normally be used in conjunction with the SECMARK target.
421 To compile it as a module, choose M here. If unsure, say N.
423 config NETFILTER_XT_TARGET_TCPMSS
424 tristate '"TCPMSS" target support'
425 depends on NETFILTER_XTABLES && (IPV6 || IPV6=n)
426 default m if NETFILTER_ADVANCED=n
428 This option adds a `TCPMSS' target, which allows you to alter the
429 MSS value of TCP SYN packets, to control the maximum size for that
430 connection (usually limiting it to your outgoing interface's MTU
433 This is used to overcome criminally braindead ISPs or servers which
434 block ICMP Fragmentation Needed packets. The symptoms of this
435 problem are that everything works fine from your Linux
436 firewall/router, but machines behind it can never exchange large
438 1) Web browsers connect, then hang with no data received.
439 2) Small mail works fine, but large emails hang.
440 3) ssh works fine, but scp hangs after initial handshaking.
442 Workaround: activate this option and add a rule to your firewall
445 iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
446 -j TCPMSS --clamp-mss-to-pmtu
448 To compile it as a module, choose M here. If unsure, say N.
450 config NETFILTER_XT_TARGET_TCPOPTSTRIP
451 tristate '"TCPOPTSTRIP" target support (EXPERIMENTAL)'
452 depends on EXPERIMENTAL && NETFILTER_XTABLES
453 depends on IP_NF_MANGLE || IP6_NF_MANGLE
454 depends on NETFILTER_ADVANCED
456 This option adds a "TCPOPTSTRIP" target, which allows you to strip
457 TCP options from TCP packets.
459 config NETFILTER_XT_MATCH_COMMENT
460 tristate '"comment" match support'
461 depends on NETFILTER_XTABLES
462 depends on NETFILTER_ADVANCED
464 This option adds a `comment' dummy-match, which allows you to put
465 comments in your iptables ruleset.
467 If you want to compile it as a module, say M here and read
468 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
470 config NETFILTER_XT_MATCH_CONNBYTES
471 tristate '"connbytes" per-connection counter match support'
472 depends on NETFILTER_XTABLES
473 depends on NF_CONNTRACK
474 depends on NETFILTER_ADVANCED
477 This option adds a `connbytes' match, which allows you to match the
478 number of bytes and/or packets for each direction within a connection.
480 If you want to compile it as a module, say M here and read
481 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
483 config NETFILTER_XT_MATCH_CONNLIMIT
484 tristate '"connlimit" match support"'
485 depends on NETFILTER_XTABLES
486 depends on NF_CONNTRACK
487 depends on NETFILTER_ADVANCED
489 This match allows you to match against the number of parallel
490 connections to a server per client IP address (or address block).
492 config NETFILTER_XT_MATCH_CONNMARK
493 tristate '"connmark" connection mark match support'
494 depends on NETFILTER_XTABLES
495 depends on NF_CONNTRACK
496 depends on NETFILTER_ADVANCED
497 select NF_CONNTRACK_MARK
499 This option adds a `connmark' match, which allows you to match the
500 connection mark value previously set for the session by `CONNMARK'.
502 If you want to compile it as a module, say M here and read
503 <file:Documentation/kbuild/modules.txt>. The module will be called
504 ipt_connmark.ko. If unsure, say `N'.
506 config NETFILTER_XT_MATCH_CONNTRACK
507 tristate '"conntrack" connection tracking match support'
508 depends on NETFILTER_XTABLES
509 depends on NF_CONNTRACK
510 default m if NETFILTER_ADVANCED=n
512 This is a general conntrack match module, a superset of the state match.
514 It allows matching on additional conntrack information, which is
515 useful in complex configurations, such as NAT gateways with multiple
516 internet links or tunnels.
518 To compile it as a module, choose M here. If unsure, say N.
520 config NETFILTER_XT_MATCH_DCCP
521 tristate '"dccp" protocol match support'
522 depends on NETFILTER_XTABLES
523 depends on NETFILTER_ADVANCED
525 With this option enabled, you will be able to use the iptables
526 `dccp' match in order to match on DCCP source/destination ports
529 If you want to compile it as a module, say M here and read
530 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
532 config NETFILTER_XT_MATCH_DSCP
533 tristate '"dscp" and "tos" match support'
534 depends on NETFILTER_XTABLES
535 depends on NETFILTER_ADVANCED
537 This option adds a `DSCP' match, which allows you to match against
538 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
540 The DSCP field can have any value between 0x0 and 0x3f inclusive.
542 It will also add a "tos" match, which allows you to match packets
543 based on the Type Of Service fields of the IPv4 packet (which share
544 the same bits as DSCP).
546 To compile it as a module, choose M here. If unsure, say N.
548 config NETFILTER_XT_MATCH_ESP
549 tristate '"esp" match support'
550 depends on NETFILTER_XTABLES
551 depends on NETFILTER_ADVANCED
553 This match extension allows you to match a range of SPIs
554 inside ESP header of IPSec packets.
556 To compile it as a module, choose M here. If unsure, say N.
558 config NETFILTER_XT_MATCH_HELPER
559 tristate '"helper" match support'
560 depends on NETFILTER_XTABLES
561 depends on NF_CONNTRACK
562 depends on NETFILTER_ADVANCED
564 Helper matching allows you to match packets in dynamic connections
565 tracked by a conntrack-helper, ie. ip_conntrack_ftp
567 To compile it as a module, choose M here. If unsure, say Y.
569 config NETFILTER_XT_MATCH_LENGTH
570 tristate '"length" match support'
571 depends on NETFILTER_XTABLES
572 depends on NETFILTER_ADVANCED
574 This option allows you to match the length of a packet against a
575 specific value or range of values.
577 To compile it as a module, choose M here. If unsure, say N.
579 config NETFILTER_XT_MATCH_LIMIT
580 tristate '"limit" match support'
581 depends on NETFILTER_XTABLES
582 depends on NETFILTER_ADVANCED
584 limit matching allows you to control the rate at which a rule can be
585 matched: mainly useful in combination with the LOG target ("LOG
586 target support", below) and to avoid some Denial of Service attacks.
588 To compile it as a module, choose M here. If unsure, say N.
590 config NETFILTER_XT_MATCH_MAC
591 tristate '"mac" address match support'
592 depends on NETFILTER_XTABLES
593 depends on NETFILTER_ADVANCED
595 MAC matching allows you to match packets based on the source
596 Ethernet address of the packet.
598 To compile it as a module, choose M here. If unsure, say N.
600 config NETFILTER_XT_MATCH_MARK
601 tristate '"mark" match support'
602 depends on NETFILTER_XTABLES
603 default m if NETFILTER_ADVANCED=n
605 Netfilter mark matching allows you to match packets based on the
606 `nfmark' value in the packet. This can be set by the MARK target
609 To compile it as a module, choose M here. If unsure, say N.
611 config NETFILTER_XT_MATCH_OWNER
612 tristate '"owner" match support'
613 depends on NETFILTER_XTABLES
614 depends on NETFILTER_ADVANCED
616 Socket owner matching allows you to match locally-generated packets
617 based on who created the socket: the user or group. It is also
618 possible to check whether a socket actually exists.
620 config NETFILTER_XT_MATCH_POLICY
621 tristate 'IPsec "policy" match support'
622 depends on NETFILTER_XTABLES && XFRM
623 default m if NETFILTER_ADVANCED=n
625 Policy matching allows you to match packets based on the
626 IPsec policy that was used during decapsulation/will
627 be used during encapsulation.
629 To compile it as a module, choose M here. If unsure, say N.
631 config NETFILTER_XT_MATCH_MULTIPORT
632 tristate '"multiport" Multiple port match support'
633 depends on NETFILTER_XTABLES
634 depends on NETFILTER_ADVANCED
636 Multiport matching allows you to match TCP or UDP packets based on
637 a series of source or destination ports: normally a rule can only
638 match a single range of ports.
640 To compile it as a module, choose M here. If unsure, say N.
642 config NETFILTER_XT_MATCH_PHYSDEV
643 tristate '"physdev" match support'
644 depends on NETFILTER_XTABLES && BRIDGE && BRIDGE_NETFILTER
645 depends on NETFILTER_ADVANCED
647 Physdev packet matching matches against the physical bridge ports
648 the IP packet arrived on or will leave by.
650 To compile it as a module, choose M here. If unsure, say N.
652 config NETFILTER_XT_MATCH_PKTTYPE
653 tristate '"pkttype" packet type match support'
654 depends on NETFILTER_XTABLES
655 depends on NETFILTER_ADVANCED
657 Packet type matching allows you to match a packet by
658 its "class", eg. BROADCAST, MULTICAST, ...
661 iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG
663 To compile it as a module, choose M here. If unsure, say N.
665 config NETFILTER_XT_MATCH_QUOTA
666 tristate '"quota" match support'
667 depends on NETFILTER_XTABLES
668 depends on NETFILTER_ADVANCED
670 This option adds a `quota' match, which allows to match on a
673 If you want to compile it as a module, say M here and read
674 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
676 config NETFILTER_XT_MATCH_RATEEST
677 tristate '"rateest" match support'
678 depends on NETFILTER_XTABLES
679 select NETFILTER_XT_TARGET_RATEEST
681 This option adds a `rateest' match, which allows to match on the
682 rate estimated by the RATEEST target.
684 To compile it as a module, choose M here. If unsure, say N.
686 config NETFILTER_XT_MATCH_REALM
687 tristate '"realm" match support'
688 depends on NETFILTER_XTABLES
689 depends on NETFILTER_ADVANCED
692 This option adds a `realm' match, which allows you to use the realm
693 key from the routing subsystem inside iptables.
695 This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option
698 If you want to compile it as a module, say M here and read
699 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
701 config NETFILTER_XT_MATCH_SCTP
702 tristate '"sctp" protocol match support (EXPERIMENTAL)'
703 depends on NETFILTER_XTABLES && EXPERIMENTAL
704 depends on NETFILTER_ADVANCED
706 With this option enabled, you will be able to use the
707 `sctp' match in order to match on SCTP source/destination ports
708 and SCTP chunk types.
710 If you want to compile it as a module, say M here and read
711 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
713 config NETFILTER_XT_MATCH_STATE
714 tristate '"state" match support'
715 depends on NETFILTER_XTABLES
716 depends on NF_CONNTRACK
717 default m if NETFILTER_ADVANCED=n
719 Connection state matching allows you to match packets based on their
720 relationship to a tracked connection (ie. previous packets). This
721 is a powerful tool for packet classification.
723 To compile it as a module, choose M here. If unsure, say N.
725 config NETFILTER_XT_MATCH_STATISTIC
726 tristate '"statistic" match support'
727 depends on NETFILTER_XTABLES
728 depends on NETFILTER_ADVANCED
730 This option adds a `statistic' match, which allows you to match
731 on packets periodically or randomly with a given percentage.
733 To compile it as a module, choose M here. If unsure, say N.
735 config NETFILTER_XT_MATCH_STRING
736 tristate '"string" match support'
737 depends on NETFILTER_XTABLES
738 depends on NETFILTER_ADVANCED
740 select TEXTSEARCH_KMP
742 select TEXTSEARCH_FSM
744 This option adds a `string' match, which allows you to look for
745 pattern matchings in packets.
747 To compile it as a module, choose M here. If unsure, say N.
749 config NETFILTER_XT_MATCH_TCPMSS
750 tristate '"tcpmss" match support'
751 depends on NETFILTER_XTABLES
752 depends on NETFILTER_ADVANCED
754 This option adds a `tcpmss' match, which allows you to examine the
755 MSS value of TCP SYN packets, which control the maximum packet size
758 To compile it as a module, choose M here. If unsure, say N.
760 config NETFILTER_XT_MATCH_TIME
761 tristate '"time" match support'
762 depends on NETFILTER_XTABLES
763 depends on NETFILTER_ADVANCED
765 This option adds a "time" match, which allows you to match based on
766 the packet arrival time (at the machine which netfilter is running)
767 on) or departure time/date (for locally generated packets).
769 If you say Y here, try `iptables -m time --help` for
772 If you want to compile it as a module, say M here.
775 config NETFILTER_XT_MATCH_U32
776 tristate '"u32" match support'
777 depends on NETFILTER_XTABLES
778 depends on NETFILTER_ADVANCED
780 u32 allows you to extract quantities of up to 4 bytes from a packet,
781 AND them with specified masks, shift them by specified amounts and
782 test whether the results are in any of a set of specified ranges.
783 The specification of what to extract is general enough to skip over
784 headers with lengths stored in the packet, as in IP or TCP header
787 Details and examples are in the kernel module source.
789 config NETFILTER_XT_MATCH_HASHLIMIT
790 tristate '"hashlimit" match support'
791 depends on NETFILTER_XTABLES && (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
792 depends on NETFILTER_ADVANCED
794 This option adds a `hashlimit' match.
796 As opposed to `limit', this match dynamically creates a hash table
797 of limit buckets, based on your selection of source/destination
798 addresses and/or ports.
800 It enables you to express policies like `10kpps for any given
801 destination address' or `500pps from any given source address'