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.
42 bool "Connection tracking flow accounting"
43 depends on NETFILTER_ADVANCED
44 depends on NF_CONNTRACK
46 If this option is enabled, the connection tracking code will
47 keep per-flow packet and byte counters.
49 Those counters can be used for flow-based accounting or the
54 config NF_CONNTRACK_MARK
55 bool 'Connection mark tracking support'
56 depends on NETFILTER_ADVANCED
57 depends on NF_CONNTRACK
59 This option enables support for connection marks, used by the
60 `CONNMARK' target and `connmark' match. Similar to the mark value
61 of packets, but this mark value is kept in the conntrack session
62 instead of the individual packets.
64 config NF_CONNTRACK_SECMARK
65 bool 'Connection tracking security mark support'
66 depends on NF_CONNTRACK && NETWORK_SECMARK
67 default m if NETFILTER_ADVANCED=n
69 This option enables security markings to be applied to
70 connections. Typically they are copied to connections from
71 packets using the CONNSECMARK target and copied back from
72 connections to packets with the same target, with the packets
73 being originally labeled via SECMARK.
77 config NF_CONNTRACK_EVENTS
78 bool "Connection tracking events"
79 depends on NF_CONNTRACK
80 depends on NETFILTER_ADVANCED
82 If this option is enabled, the connection tracking code will
83 provide a notifier chain that can be used by other kernel code
84 to get notified about changes in the connection tracking state.
88 config NF_CT_PROTO_DCCP
89 tristate 'DCCP protocol connection tracking support (EXPERIMENTAL)'
90 depends on EXPERIMENTAL && NF_CONNTRACK
91 depends on NETFILTER_ADVANCED
94 With this option enabled, the layer 3 independent connection
95 tracking code will be able to do state tracking on DCCP connections.
99 config NF_CT_PROTO_GRE
101 depends on NF_CONNTRACK
103 config NF_CT_PROTO_SCTP
104 tristate 'SCTP protocol connection tracking support (EXPERIMENTAL)'
105 depends on EXPERIMENTAL && NF_CONNTRACK
106 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 SCTP connections.
112 If you want to compile it as a module, say M here and read
113 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
115 config NF_CT_PROTO_UDPLITE
116 tristate 'UDP-Lite protocol connection tracking support'
117 depends on NF_CONNTRACK
118 depends on NETFILTER_ADVANCED
120 With this option enabled, the layer 3 independent connection
121 tracking code will be able to do state tracking on UDP-Lite
124 To compile it as a module, choose M here. If unsure, say N.
126 config NF_CONNTRACK_AMANDA
127 tristate "Amanda backup protocol support"
128 depends on NF_CONNTRACK
129 depends on NETFILTER_ADVANCED
131 select TEXTSEARCH_KMP
133 If you are running the Amanda backup package <http://www.amanda.org/>
134 on this machine or machines that will be MASQUERADED through this
135 machine, then you may want to enable this feature. This allows the
136 connection tracking and natting code to allow the sub-channels that
137 Amanda requires for communication of the backup data, messages and
140 To compile it as a module, choose M here. If unsure, say N.
142 config NF_CONNTRACK_FTP
143 tristate "FTP protocol support"
144 depends on NF_CONNTRACK
145 default m if NETFILTER_ADVANCED=n
147 Tracking FTP connections is problematic: special helpers are
148 required for tracking them, and doing masquerading and other forms
149 of Network Address Translation on them.
151 This is FTP support on Layer 3 independent connection tracking.
152 Layer 3 independent connection tracking is experimental scheme
153 which generalize ip_conntrack to support other layer 3 protocols.
155 To compile it as a module, choose M here. If unsure, say N.
157 config NF_CONNTRACK_H323
158 tristate "H.323 protocol support"
159 depends on NF_CONNTRACK && (IPV6 || IPV6=n)
160 depends on NETFILTER_ADVANCED
162 H.323 is a VoIP signalling protocol from ITU-T. As one of the most
163 important VoIP protocols, it is widely used by voice hardware and
164 software including voice gateways, IP phones, Netmeeting, OpenPhone,
167 With this module you can support H.323 on a connection tracking/NAT
170 This module supports RAS, Fast Start, H.245 Tunnelling, Call
171 Forwarding, RTP/RTCP and T.120 based audio, video, fax, chat,
172 whiteboard, file transfer, etc. For more information, please
173 visit http://nath323.sourceforge.net/.
175 To compile it as a module, choose M here. If unsure, say N.
177 config NF_CONNTRACK_IRC
178 tristate "IRC protocol support"
179 depends on NF_CONNTRACK
180 default m if NETFILTER_ADVANCED=n
182 There is a commonly-used extension to IRC called
183 Direct Client-to-Client Protocol (DCC). This enables users to send
184 files to each other, and also chat to each other without the need
185 of a server. DCC Sending is used anywhere you send files over IRC,
186 and DCC Chat is most commonly used by Eggdrop bots. If you are
187 using NAT, this extension will enable you to send files and initiate
188 chats. Note that you do NOT need this extension to get files or
189 have others initiate chats, or everything else in IRC.
191 To compile it as a module, choose M here. If unsure, say N.
193 config NF_CONNTRACK_NETBIOS_NS
194 tristate "NetBIOS name service protocol support"
195 depends on NF_CONNTRACK
196 depends on NETFILTER_ADVANCED
198 NetBIOS name service requests are sent as broadcast messages from an
199 unprivileged port and responded to with unicast messages to the
200 same port. This make them hard to firewall properly because connection
201 tracking doesn't deal with broadcasts. This helper tracks locally
202 originating NetBIOS name service requests and the corresponding
203 responses. It relies on correct IP address configuration, specifically
204 netmask and broadcast address. When properly configured, the output
205 of "ip address show" should look similar to this:
207 $ ip -4 address show eth0
208 4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
209 inet 172.16.2.252/24 brd 172.16.2.255 scope global eth0
211 To compile it as a module, choose M here. If unsure, say N.
213 config NF_CONNTRACK_PPTP
214 tristate "PPtP protocol support"
215 depends on NF_CONNTRACK
216 depends on NETFILTER_ADVANCED
217 select NF_CT_PROTO_GRE
219 This module adds support for PPTP (Point to Point Tunnelling
220 Protocol, RFC2637) connection tracking and NAT.
222 If you are running PPTP sessions over a stateful firewall or NAT
223 box, you may want to enable this feature.
225 Please note that not all PPTP modes of operation are supported yet.
226 Specifically these limitations exist:
227 - Blindly assumes that control connections are always established
228 in PNS->PAC direction. This is a violation of RFC2637.
229 - Only supports a single call within each session
231 To compile it as a module, choose M here. If unsure, say N.
233 config NF_CONNTRACK_SANE
234 tristate "SANE protocol support (EXPERIMENTAL)"
235 depends on EXPERIMENTAL && NF_CONNTRACK
236 depends on NETFILTER_ADVANCED
238 SANE is a protocol for remote access to scanners as implemented
239 by the 'saned' daemon. Like FTP, it uses separate control and
242 With this module you can support SANE on a connection tracking
245 To compile it as a module, choose M here. If unsure, say N.
247 config NF_CONNTRACK_SIP
248 tristate "SIP protocol support"
249 depends on NF_CONNTRACK
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 NF_CONNTRACK
263 depends on NETFILTER_ADVANCED
265 TFTP connection tracking helper, this is required depending
266 on how restrictive your ruleset is.
267 If you are using a tftp client behind -j SNAT or -j MASQUERADING
270 To compile it as a module, choose M here. If unsure, say N.
273 tristate 'Connection tracking netlink interface'
274 depends on NF_CONNTRACK
275 select NETFILTER_NETLINK
276 depends on NF_NAT=n || NF_NAT
277 default m if NETFILTER_ADVANCED=n
279 This option enables support for a netlink-based userspace interface
281 config NETFILTER_XTABLES
282 tristate "Netfilter Xtables support (required for ip_tables)"
283 default m if NETFILTER_ADVANCED=n
285 This is required if you intend to use any of ip_tables,
286 ip6_tables or arp_tables.
288 # alphabetically ordered list of targets
290 config NETFILTER_XT_TARGET_CLASSIFY
291 tristate '"CLASSIFY" target support'
292 depends on NETFILTER_XTABLES
293 depends on NETFILTER_ADVANCED
295 This option adds a `CLASSIFY' target, which enables the user to set
296 the priority of a packet. Some qdiscs can use this value for
297 classification, among these are:
299 atm, cbq, dsmark, pfifo_fast, htb, prio
301 To compile it as a module, choose M here. If unsure, say N.
303 config NETFILTER_XT_TARGET_CONNMARK
304 tristate '"CONNMARK" target support'
305 depends on NETFILTER_XTABLES
306 depends on IP_NF_MANGLE || IP6_NF_MANGLE
307 depends on NF_CONNTRACK
308 depends on NETFILTER_ADVANCED
309 select NF_CONNTRACK_MARK
311 This option adds a `CONNMARK' target, which allows one to manipulate
312 the connection mark value. Similar to the MARK target, but
313 affects the connection mark value rather than the packet mark value.
315 If you want to compile it as a module, say M here and read
316 <file:Documentation/kbuild/modules.txt>. The module will be called
317 ipt_CONNMARK.ko. If unsure, say `N'.
319 config NETFILTER_XT_TARGET_DSCP
320 tristate '"DSCP" and "TOS" target support'
321 depends on NETFILTER_XTABLES
322 depends on IP_NF_MANGLE || IP6_NF_MANGLE
323 depends on NETFILTER_ADVANCED
325 This option adds a `DSCP' target, which allows you to manipulate
326 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
328 The DSCP field can have any value between 0x0 and 0x3f inclusive.
330 It also adds the "TOS" target, which allows you to create rules in
331 the "mangle" table which alter the Type Of Service field of an IPv4
332 or the Priority field of an IPv6 packet, prior to routing.
334 To compile it as a module, choose M here. If unsure, say N.
336 config NETFILTER_XT_TARGET_MARK
337 tristate '"MARK" target support'
338 depends on NETFILTER_XTABLES
339 default m if NETFILTER_ADVANCED=n
341 This option adds a `MARK' target, which allows you to create rules
342 in the `mangle' table which alter the netfilter mark (nfmark) field
343 associated with the packet prior to routing. This can change
344 the routing method (see `Use netfilter MARK value as routing
345 key') and can also be used by other subsystems to change their
348 To compile it as a module, choose M here. If unsure, say N.
350 config NETFILTER_XT_TARGET_NFQUEUE
351 tristate '"NFQUEUE" target Support'
352 depends on NETFILTER_XTABLES
353 depends on NETFILTER_ADVANCED
355 This target replaced the old obsolete QUEUE target.
357 As opposed to QUEUE, it supports 65535 different queues,
360 To compile it as a module, choose M here. If unsure, say N.
362 config NETFILTER_XT_TARGET_NFLOG
363 tristate '"NFLOG" target support'
364 depends on NETFILTER_XTABLES
365 default m if NETFILTER_ADVANCED=n
367 This option enables the NFLOG target, which allows to LOG
368 messages through the netfilter logging API, which can use
369 either the old LOG target, the old ULOG target or nfnetlink_log
372 To compile it as a module, choose M here. If unsure, say N.
374 config NETFILTER_XT_TARGET_NOTRACK
375 tristate '"NOTRACK" target support'
376 depends on NETFILTER_XTABLES
377 depends on IP_NF_RAW || IP6_NF_RAW
378 depends on NF_CONNTRACK
379 depends on NETFILTER_ADVANCED
381 The NOTRACK target allows a select rule to specify
382 which packets *not* to enter the conntrack/NAT
383 subsystem with all the consequences (no ICMP error tracking,
384 no protocol helpers for the selected packets).
386 If you want to compile it as a module, say M here and read
387 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
389 config NETFILTER_XT_TARGET_RATEEST
390 tristate '"RATEEST" target support'
391 depends on NETFILTER_XTABLES
392 depends on NETFILTER_ADVANCED
394 This option adds a `RATEEST' target, which allows to measure
395 rates similar to TC estimators. The `rateest' match can be
396 used to match on the measured rates.
398 To compile it as a module, choose M here. If unsure, say N.
400 config NETFILTER_XT_TARGET_TRACE
401 tristate '"TRACE" target support'
402 depends on NETFILTER_XTABLES
403 depends on IP_NF_RAW || IP6_NF_RAW
404 depends on NETFILTER_ADVANCED
406 The TRACE target allows you to mark packets so that the kernel
407 will log every rule which match the packets as those traverse
408 the tables, chains, rules.
410 If you want to compile it as a module, say M here and read
411 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
413 config NETFILTER_XT_TARGET_SECMARK
414 tristate '"SECMARK" target support'
415 depends on NETFILTER_XTABLES && NETWORK_SECMARK
416 default m if NETFILTER_ADVANCED=n
418 The SECMARK target allows security marking of network
419 packets, for use with security subsystems.
421 To compile it as a module, choose M here. If unsure, say N.
423 config NETFILTER_XT_TARGET_CONNSECMARK
424 tristate '"CONNSECMARK" target support'
425 depends on NETFILTER_XTABLES && NF_CONNTRACK && NF_CONNTRACK_SECMARK
426 default m if NETFILTER_ADVANCED=n
428 The CONNSECMARK target copies security markings from packets
429 to connections, and restores security markings from connections
430 to packets (if the packets are not already marked). This would
431 normally be used in conjunction with the SECMARK target.
433 To compile it as a module, choose M here. If unsure, say N.
435 config NETFILTER_XT_TARGET_TCPMSS
436 tristate '"TCPMSS" target support'
437 depends on NETFILTER_XTABLES && (IPV6 || IPV6=n)
438 default m if NETFILTER_ADVANCED=n
440 This option adds a `TCPMSS' target, which allows you to alter the
441 MSS value of TCP SYN packets, to control the maximum size for that
442 connection (usually limiting it to your outgoing interface's MTU
445 This is used to overcome criminally braindead ISPs or servers which
446 block ICMP Fragmentation Needed packets. The symptoms of this
447 problem are that everything works fine from your Linux
448 firewall/router, but machines behind it can never exchange large
450 1) Web browsers connect, then hang with no data received.
451 2) Small mail works fine, but large emails hang.
452 3) ssh works fine, but scp hangs after initial handshaking.
454 Workaround: activate this option and add a rule to your firewall
457 iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
458 -j TCPMSS --clamp-mss-to-pmtu
460 To compile it as a module, choose M here. If unsure, say N.
462 config NETFILTER_XT_TARGET_TCPOPTSTRIP
463 tristate '"TCPOPTSTRIP" target support (EXPERIMENTAL)'
464 depends on EXPERIMENTAL && NETFILTER_XTABLES
465 depends on IP_NF_MANGLE || IP6_NF_MANGLE
466 depends on NETFILTER_ADVANCED
468 This option adds a "TCPOPTSTRIP" target, which allows you to strip
469 TCP options from TCP packets.
471 config NETFILTER_XT_MATCH_COMMENT
472 tristate '"comment" match support'
473 depends on NETFILTER_XTABLES
474 depends on NETFILTER_ADVANCED
476 This option adds a `comment' dummy-match, which allows you to put
477 comments in your iptables ruleset.
479 If you want to compile it as a module, say M here and read
480 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
482 config NETFILTER_XT_MATCH_CONNBYTES
483 tristate '"connbytes" per-connection counter match support'
484 depends on NETFILTER_XTABLES
485 depends on NF_CONNTRACK
486 depends on NETFILTER_ADVANCED
489 This option adds a `connbytes' match, which allows you to match the
490 number of bytes and/or packets for each direction within a connection.
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_MATCH_CONNLIMIT
496 tristate '"connlimit" match support"'
497 depends on NETFILTER_XTABLES
498 depends on NF_CONNTRACK
499 depends on NETFILTER_ADVANCED
501 This match allows you to match against the number of parallel
502 connections to a server per client IP address (or address block).
504 config NETFILTER_XT_MATCH_CONNMARK
505 tristate '"connmark" connection mark match support'
506 depends on NETFILTER_XTABLES
507 depends on NF_CONNTRACK
508 depends on NETFILTER_ADVANCED
509 select NF_CONNTRACK_MARK
511 This option adds a `connmark' match, which allows you to match the
512 connection mark value previously set for the session by `CONNMARK'.
514 If you want to compile it as a module, say M here and read
515 <file:Documentation/kbuild/modules.txt>. The module will be called
516 ipt_connmark.ko. If unsure, say `N'.
518 config NETFILTER_XT_MATCH_CONNTRACK
519 tristate '"conntrack" connection tracking match support'
520 depends on NETFILTER_XTABLES
521 depends on NF_CONNTRACK
522 default m if NETFILTER_ADVANCED=n
524 This is a general conntrack match module, a superset of the state match.
526 It allows matching on additional conntrack information, which is
527 useful in complex configurations, such as NAT gateways with multiple
528 internet links or tunnels.
530 To compile it as a module, choose M here. If unsure, say N.
532 config NETFILTER_XT_MATCH_DCCP
533 tristate '"dccp" protocol match support'
534 depends on NETFILTER_XTABLES
535 depends on NETFILTER_ADVANCED
538 With this option enabled, you will be able to use the iptables
539 `dccp' match in order to match on DCCP source/destination ports
542 If you want to compile it as a module, say M here and read
543 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
545 config NETFILTER_XT_MATCH_DSCP
546 tristate '"dscp" and "tos" match support'
547 depends on NETFILTER_XTABLES
548 depends on NETFILTER_ADVANCED
550 This option adds a `DSCP' match, which allows you to match against
551 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
553 The DSCP field can have any value between 0x0 and 0x3f inclusive.
555 It will also add a "tos" match, which allows you to match packets
556 based on the Type Of Service fields of the IPv4 packet (which share
557 the same bits as DSCP).
559 To compile it as a module, choose M here. If unsure, say N.
561 config NETFILTER_XT_MATCH_ESP
562 tristate '"esp" match support'
563 depends on NETFILTER_XTABLES
564 depends on NETFILTER_ADVANCED
566 This match extension allows you to match a range of SPIs
567 inside ESP header of IPSec packets.
569 To compile it as a module, choose M here. If unsure, say N.
571 config NETFILTER_XT_MATCH_HELPER
572 tristate '"helper" match support'
573 depends on NETFILTER_XTABLES
574 depends on NF_CONNTRACK
575 depends on NETFILTER_ADVANCED
577 Helper matching allows you to match packets in dynamic connections
578 tracked by a conntrack-helper, ie. ip_conntrack_ftp
580 To compile it as a module, choose M here. If unsure, say Y.
582 config NETFILTER_XT_MATCH_IPRANGE
583 tristate '"iprange" address range match support'
584 depends on NETFILTER_XTABLES
585 depends on NETFILTER_ADVANCED
587 This option adds a "iprange" match, which allows you to match based on
588 an IP address range. (Normal iptables only matches on single addresses
589 with an optional mask.)
593 config NETFILTER_XT_MATCH_LENGTH
594 tristate '"length" match support'
595 depends on NETFILTER_XTABLES
596 depends on NETFILTER_ADVANCED
598 This option allows you to match the length of a packet against a
599 specific value or range of values.
601 To compile it as a module, choose M here. If unsure, say N.
603 config NETFILTER_XT_MATCH_LIMIT
604 tristate '"limit" match support'
605 depends on NETFILTER_XTABLES
606 depends on NETFILTER_ADVANCED
608 limit matching allows you to control the rate at which a rule can be
609 matched: mainly useful in combination with the LOG target ("LOG
610 target support", below) and to avoid some Denial of Service attacks.
612 To compile it as a module, choose M here. If unsure, say N.
614 config NETFILTER_XT_MATCH_MAC
615 tristate '"mac" address match support'
616 depends on NETFILTER_XTABLES
617 depends on NETFILTER_ADVANCED
619 MAC matching allows you to match packets based on the source
620 Ethernet address of the packet.
622 To compile it as a module, choose M here. If unsure, say N.
624 config NETFILTER_XT_MATCH_MARK
625 tristate '"mark" match support'
626 depends on NETFILTER_XTABLES
627 default m if NETFILTER_ADVANCED=n
629 Netfilter mark matching allows you to match packets based on the
630 `nfmark' value in the packet. This can be set by the MARK target
633 To compile it as a module, choose M here. If unsure, say N.
635 config NETFILTER_XT_MATCH_OWNER
636 tristate '"owner" match support'
637 depends on NETFILTER_XTABLES
638 depends on NETFILTER_ADVANCED
640 Socket owner matching allows you to match locally-generated packets
641 based on who created the socket: the user or group. It is also
642 possible to check whether a socket actually exists.
644 config NETFILTER_XT_MATCH_POLICY
645 tristate 'IPsec "policy" match support'
646 depends on NETFILTER_XTABLES && XFRM
647 default m if NETFILTER_ADVANCED=n
649 Policy matching allows you to match packets based on the
650 IPsec policy that was used during decapsulation/will
651 be used during encapsulation.
653 To compile it as a module, choose M here. If unsure, say N.
655 config NETFILTER_XT_MATCH_MULTIPORT
656 tristate '"multiport" Multiple port match support'
657 depends on NETFILTER_XTABLES
658 depends on NETFILTER_ADVANCED
660 Multiport matching allows you to match TCP or UDP packets based on
661 a series of source or destination ports: normally a rule can only
662 match a single range of ports.
664 To compile it as a module, choose M here. If unsure, say N.
666 config NETFILTER_XT_MATCH_PHYSDEV
667 tristate '"physdev" match support'
668 depends on NETFILTER_XTABLES && BRIDGE && BRIDGE_NETFILTER
669 depends on NETFILTER_ADVANCED
671 Physdev packet matching matches against the physical bridge ports
672 the IP packet arrived on or will leave by.
674 To compile it as a module, choose M here. If unsure, say N.
676 config NETFILTER_XT_MATCH_PKTTYPE
677 tristate '"pkttype" packet type match support'
678 depends on NETFILTER_XTABLES
679 depends on NETFILTER_ADVANCED
681 Packet type matching allows you to match a packet by
682 its "class", eg. BROADCAST, MULTICAST, ...
685 iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG
687 To compile it as a module, choose M here. If unsure, say N.
689 config NETFILTER_XT_MATCH_QUOTA
690 tristate '"quota" match support'
691 depends on NETFILTER_XTABLES
692 depends on NETFILTER_ADVANCED
694 This option adds a `quota' match, which allows to match on a
697 If you want to compile it as a module, say M here and read
698 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
700 config NETFILTER_XT_MATCH_RATEEST
701 tristate '"rateest" match support'
702 depends on NETFILTER_XTABLES
703 depends on NETFILTER_ADVANCED
704 select NETFILTER_XT_TARGET_RATEEST
706 This option adds a `rateest' match, which allows to match on the
707 rate estimated by the RATEEST target.
709 To compile it as a module, choose M here. If unsure, say N.
711 config NETFILTER_XT_MATCH_REALM
712 tristate '"realm" match support'
713 depends on NETFILTER_XTABLES
714 depends on NETFILTER_ADVANCED
717 This option adds a `realm' match, which allows you to use the realm
718 key from the routing subsystem inside iptables.
720 This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option
723 If you want to compile it as a module, say M here and read
724 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
726 config NETFILTER_XT_MATCH_SCTP
727 tristate '"sctp" protocol match support (EXPERIMENTAL)'
728 depends on NETFILTER_XTABLES && EXPERIMENTAL
729 depends on NETFILTER_ADVANCED
732 With this option enabled, you will be able to use the
733 `sctp' match in order to match on SCTP source/destination ports
734 and SCTP chunk types.
736 If you want to compile it as a module, say M here and read
737 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
739 config NETFILTER_XT_MATCH_STATE
740 tristate '"state" match support'
741 depends on NETFILTER_XTABLES
742 depends on NF_CONNTRACK
743 default m if NETFILTER_ADVANCED=n
745 Connection state matching allows you to match packets based on their
746 relationship to a tracked connection (ie. previous packets). This
747 is a powerful tool for packet classification.
749 To compile it as a module, choose M here. If unsure, say N.
751 config NETFILTER_XT_MATCH_STATISTIC
752 tristate '"statistic" match support'
753 depends on NETFILTER_XTABLES
754 depends on NETFILTER_ADVANCED
756 This option adds a `statistic' match, which allows you to match
757 on packets periodically or randomly with a given percentage.
759 To compile it as a module, choose M here. If unsure, say N.
761 config NETFILTER_XT_MATCH_STRING
762 tristate '"string" match support'
763 depends on NETFILTER_XTABLES
764 depends on NETFILTER_ADVANCED
766 select TEXTSEARCH_KMP
768 select TEXTSEARCH_FSM
770 This option adds a `string' match, which allows you to look for
771 pattern matchings in packets.
773 To compile it as a module, choose M here. If unsure, say N.
775 config NETFILTER_XT_MATCH_TCPMSS
776 tristate '"tcpmss" match support'
777 depends on NETFILTER_XTABLES
778 depends on NETFILTER_ADVANCED
780 This option adds a `tcpmss' match, which allows you to examine the
781 MSS value of TCP SYN packets, which control the maximum packet size
784 To compile it as a module, choose M here. If unsure, say N.
786 config NETFILTER_XT_MATCH_TIME
787 tristate '"time" match support'
788 depends on NETFILTER_XTABLES
789 depends on NETFILTER_ADVANCED
791 This option adds a "time" match, which allows you to match based on
792 the packet arrival time (at the machine which netfilter is running)
793 on) or departure time/date (for locally generated packets).
795 If you say Y here, try `iptables -m time --help` for
798 If you want to compile it as a module, say M here.
801 config NETFILTER_XT_MATCH_U32
802 tristate '"u32" match support'
803 depends on NETFILTER_XTABLES
804 depends on NETFILTER_ADVANCED
806 u32 allows you to extract quantities of up to 4 bytes from a packet,
807 AND them with specified masks, shift them by specified amounts and
808 test whether the results are in any of a set of specified ranges.
809 The specification of what to extract is general enough to skip over
810 headers with lengths stored in the packet, as in IP or TCP header
813 Details and examples are in the kernel module source.
815 config NETFILTER_XT_MATCH_HASHLIMIT
816 tristate '"hashlimit" match support'
817 depends on NETFILTER_XTABLES && (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
818 depends on NETFILTER_ADVANCED
820 This option adds a `hashlimit' match.
822 As opposed to `limit', this match dynamically creates a hash table
823 of limit buckets, based on your selection of source/destination
824 addresses and/or ports.
826 It enables you to express policies like `10kpps for any given
827 destination address' or `500pps from any given source address'