1 menu "Core Netfilter Configuration"
2 depends on NET && INET && NETFILTER
4 config NETFILTER_NETLINK
5 tristate "Netfilter netlink interface"
7 If this option is enabled, the kernel will include support
8 for the new netfilter netlink interface.
10 config NETFILTER_NETLINK_QUEUE
11 tristate "Netfilter NFQUEUE over NFNETLINK interface"
12 depends on NETFILTER_NETLINK
14 If this option is enabled, the kernel will include support
15 for queueing packets via NFNETLINK.
17 config NETFILTER_NETLINK_LOG
18 tristate "Netfilter LOG over NFNETLINK interface"
19 depends on NETFILTER_NETLINK
21 If this option is enabled, the kernel will include support
22 for logging packets via NFNETLINK.
24 This obsoletes the existing ipt_ULOG and ebg_ulog mechanisms,
25 and is also scheduled to replace the old syslog-based ipt_LOG
28 # Rename this to NF_CONNTRACK in a 2.6.25
29 config NF_CONNTRACK_ENABLED
30 tristate "Netfilter connection tracking support"
32 Connection tracking keeps a record of what packets have passed
33 through your machine, in order to figure out how they are related
36 This is required to do Masquerading or other kinds of Network
37 Address Translation (except for Fast NAT). It can also be used to
38 enhance packet filtering (see `Connection state match support'
41 To compile it as a module, choose M here. If unsure, say N.
45 default NF_CONNTRACK_ENABLED
48 bool "Connection tracking flow accounting"
49 depends on NF_CONNTRACK
51 If this option is enabled, the connection tracking code will
52 keep per-flow packet and byte counters.
54 Those counters can be used for flow-based accounting or the
59 config NF_CONNTRACK_MARK
60 bool 'Connection mark tracking support'
61 depends on NF_CONNTRACK
63 This option enables support for connection marks, used by the
64 `CONNMARK' target and `connmark' match. Similar to the mark value
65 of packets, but this mark value is kept in the conntrack session
66 instead of the individual packets.
68 config NF_CONNTRACK_SECMARK
69 bool 'Connection tracking security mark support'
70 depends on NF_CONNTRACK && NETWORK_SECMARK
72 This option enables security markings to be applied to
73 connections. Typically they are copied to connections from
74 packets using the CONNSECMARK target and copied back from
75 connections to packets with the same target, with the packets
76 being originally labeled via SECMARK.
80 config NF_CONNTRACK_EVENTS
81 bool "Connection tracking events (EXPERIMENTAL)"
82 depends on EXPERIMENTAL && NF_CONNTRACK
84 If this option is enabled, the connection tracking code will
85 provide a notifier chain that can be used by other kernel code
86 to get notified about changes in the connection tracking state.
90 config NF_CT_PROTO_GRE
92 depends on NF_CONNTRACK
94 config NF_CT_PROTO_SCTP
95 tristate 'SCTP protocol connection tracking support (EXPERIMENTAL)'
96 depends on EXPERIMENTAL && NF_CONNTRACK
99 With this option enabled, the layer 3 independent connection
100 tracking code will be able to do state tracking on SCTP connections.
102 If you want to compile it as a module, say M here and read
103 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
105 config NF_CONNTRACK_AMANDA
106 tristate "Amanda backup protocol support"
107 depends on NF_CONNTRACK
109 select TEXTSEARCH_KMP
111 If you are running the Amanda backup package <http://www.amanda.org/>
112 on this machine or machines that will be MASQUERADED through this
113 machine, then you may want to enable this feature. This allows the
114 connection tracking and natting code to allow the sub-channels that
115 Amanda requires for communication of the backup data, messages and
118 To compile it as a module, choose M here. If unsure, say N.
120 config NF_CONNTRACK_FTP
121 tristate "FTP protocol support"
122 depends on NF_CONNTRACK
124 Tracking FTP connections is problematic: special helpers are
125 required for tracking them, and doing masquerading and other forms
126 of Network Address Translation on them.
128 This is FTP support on Layer 3 independent connection tracking.
129 Layer 3 independent connection tracking is experimental scheme
130 which generalize ip_conntrack to support other layer 3 protocols.
132 To compile it as a module, choose M here. If unsure, say N.
134 config NF_CONNTRACK_H323
135 tristate "H.323 protocol support (EXPERIMENTAL)"
136 depends on EXPERIMENTAL && NF_CONNTRACK && (IPV6 || IPV6=n)
138 H.323 is a VoIP signalling protocol from ITU-T. As one of the most
139 important VoIP protocols, it is widely used by voice hardware and
140 software including voice gateways, IP phones, Netmeeting, OpenPhone,
143 With this module you can support H.323 on a connection tracking/NAT
146 This module supports RAS, Fast Start, H.245 Tunnelling, Call
147 Forwarding, RTP/RTCP and T.120 based audio, video, fax, chat,
148 whiteboard, file transfer, etc. For more information, please
149 visit http://nath323.sourceforge.net/.
151 To compile it as a module, choose M here. If unsure, say N.
153 config NF_CONNTRACK_IRC
154 tristate "IRC protocol support"
155 depends on NF_CONNTRACK
157 There is a commonly-used extension to IRC called
158 Direct Client-to-Client Protocol (DCC). This enables users to send
159 files to each other, and also chat to each other without the need
160 of a server. DCC Sending is used anywhere you send files over IRC,
161 and DCC Chat is most commonly used by Eggdrop bots. If you are
162 using NAT, this extension will enable you to send files and initiate
163 chats. Note that you do NOT need this extension to get files or
164 have others initiate chats, or everything else in IRC.
166 To compile it as a module, choose M here. If unsure, say N.
168 config NF_CONNTRACK_NETBIOS_NS
169 tristate "NetBIOS name service protocol support (EXPERIMENTAL)"
170 depends on EXPERIMENTAL && NF_CONNTRACK
172 NetBIOS name service requests are sent as broadcast messages from an
173 unprivileged port and responded to with unicast messages to the
174 same port. This make them hard to firewall properly because connection
175 tracking doesn't deal with broadcasts. This helper tracks locally
176 originating NetBIOS name service requests and the corresponding
177 responses. It relies on correct IP address configuration, specifically
178 netmask and broadcast address. When properly configured, the output
179 of "ip address show" should look similar to this:
181 $ ip -4 address show eth0
182 4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
183 inet 172.16.2.252/24 brd 172.16.2.255 scope global eth0
185 To compile it as a module, choose M here. If unsure, say N.
187 config NF_CONNTRACK_PPTP
188 tristate "PPtP protocol support"
189 depends on NF_CONNTRACK
190 select NF_CT_PROTO_GRE
192 This module adds support for PPTP (Point to Point Tunnelling
193 Protocol, RFC2637) connection tracking and NAT.
195 If you are running PPTP sessions over a stateful firewall or NAT
196 box, you may want to enable this feature.
198 Please note that not all PPTP modes of operation are supported yet.
199 Specifically these limitations exist:
200 - Blindly assumes that control connections are always established
201 in PNS->PAC direction. This is a violation of RFC2637.
202 - Only supports a single call within each session
204 To compile it as a module, choose M here. If unsure, say N.
206 config NF_CONNTRACK_SANE
207 tristate "SANE protocol support (EXPERIMENTAL)"
208 depends on EXPERIMENTAL && NF_CONNTRACK
210 SANE is a protocol for remote access to scanners as implemented
211 by the 'saned' daemon. Like FTP, it uses separate control and
214 With this module you can support SANE on a connection tracking
217 To compile it as a module, choose M here. If unsure, say N.
219 config NF_CONNTRACK_SIP
220 tristate "SIP protocol support (EXPERIMENTAL)"
221 depends on EXPERIMENTAL && NF_CONNTRACK
223 SIP is an application-layer control protocol that can establish,
224 modify, and terminate multimedia sessions (conferences) such as
225 Internet telephony calls. With the ip_conntrack_sip and
226 the nf_nat_sip modules you can support the protocol on a connection
227 tracking/NATing firewall.
229 To compile it as a module, choose M here. If unsure, say N.
231 config NF_CONNTRACK_TFTP
232 tristate "TFTP protocol support"
233 depends on NF_CONNTRACK
235 TFTP connection tracking helper, this is required depending
236 on how restrictive your ruleset is.
237 If you are using a tftp client behind -j SNAT or -j MASQUERADING
240 To compile it as a module, choose M here. If unsure, say N.
242 config NF_CONNTRACK_RTSP
243 tristate "RTSP protocol support"
244 depends on NF_CONNTRACK
246 Support the RTSP protocol. This allows UDP transports to be setup
247 properly, including RTP and RDT.
249 If you want to compile it as a module, say 'M' here and read
250 Documentation/modules.txt. If unsure, say 'Y'.
253 tristate 'Connection tracking netlink interface (EXPERIMENTAL)'
254 depends on EXPERIMENTAL && NF_CONNTRACK && NETFILTER_NETLINK
255 depends on NF_CONNTRACK!=y || NETFILTER_NETLINK!=m
256 depends on NF_NAT=n || NF_NAT
258 This option enables support for a netlink-based userspace interface
260 config NETFILTER_XTABLES
261 tristate "Netfilter Xtables support (required for ip_tables)"
263 This is required if you intend to use any of ip_tables,
264 ip6_tables or arp_tables.
266 # alphabetically ordered list of targets
268 config NETFILTER_XT_TARGET_CLASSIFY
269 tristate '"CLASSIFY" target support'
270 depends on NETFILTER_XTABLES
272 This option adds a `CLASSIFY' target, which enables the user to set
273 the priority of a packet. Some qdiscs can use this value for
274 classification, among these are:
276 atm, cbq, dsmark, pfifo_fast, htb, prio
278 To compile it as a module, choose M here. If unsure, say N.
280 config NETFILTER_XT_TARGET_CONNMARK
281 tristate '"CONNMARK" target support'
282 depends on NETFILTER_XTABLES
283 depends on IP_NF_MANGLE || IP6_NF_MANGLE
284 depends on NF_CONNTRACK
285 select NF_CONNTRACK_MARK
287 This option adds a `CONNMARK' target, which allows one to manipulate
288 the connection mark value. Similar to the MARK target, but
289 affects the connection mark value rather than the packet mark value.
291 If you want to compile it as a module, say M here and read
292 <file:Documentation/kbuild/modules.txt>. The module will be called
293 ipt_CONNMARK.ko. If unsure, say `N'.
295 config NETFILTER_XT_TARGET_DSCP
296 tristate '"DSCP" target support'
297 depends on NETFILTER_XTABLES
298 depends on IP_NF_MANGLE || IP6_NF_MANGLE
300 This option adds a `DSCP' target, which allows you to manipulate
301 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
303 The DSCP field can have any value between 0x0 and 0x3f inclusive.
305 To compile it as a module, choose M here. If unsure, say N.
307 config NETFILTER_XT_TARGET_HL
308 tristate '"HL" hoplimit target support'
309 depends on IP_NF_MANGLE || IP6_NF_MANGLE
311 This option adds the "HL" (for IPv6) and "TTL" (for IPv4)
312 targets, which enable the user to change the
313 hoplimit/time-to-live value of the IP header.
315 While it is safe to decrement the hoplimit/TTL value, the
316 modules also allow to increment and set the hoplimit value of
317 the header to arbitrary values. This is EXTREMELY DANGEROUS
318 since you can easily create immortal packets that loop
319 forever on the network.
321 config NETFILTER_XT_TARGET_IMQ
322 tristate "IMQ target support"
323 depends on NETFILTER_XTABLES
324 depends on IP_NF_MANGLE || IP6_NF_MANGLE
328 This option adds a `IMQ' target which is used to specify if and
329 to which IMQ device packets should get enqueued/dequeued.
331 For more information visit: http://www.linuximq.net/
333 To compile it as a module, choose M here. If unsure, say N.
335 config NETFILTER_XT_TARGET_MARK
336 tristate '"MARK" target support'
337 depends on NETFILTER_XTABLES
339 This option adds a `MARK' target, which allows you to create rules
340 in the `mangle' table which alter the netfilter mark (nfmark) field
341 associated with the packet prior to routing. This can change
342 the routing method (see `Use netfilter MARK value as routing
343 key') and can also be used by other subsystems to change their
346 To compile it as a module, choose M here. If unsure, say N.
348 config NETFILTER_XT_TARGET_NFQUEUE
349 tristate '"NFQUEUE" target Support'
350 depends on NETFILTER_XTABLES
352 This target replaced the old obsolete QUEUE target.
354 As opposed to QUEUE, it supports 65535 different queues,
357 To compile it as a module, choose M here. If unsure, say N.
359 config NETFILTER_XT_TARGET_NFLOG
360 tristate '"NFLOG" target support'
361 depends on NETFILTER_XTABLES
363 This option enables the NFLOG target, which allows to LOG
364 messages through the netfilter logging API, which can use
365 either the old LOG target, the old ULOG target or nfnetlink_log
368 To compile it as a module, choose M here. If unsure, say N.
370 config NETFILTER_XT_TARGET_NOTRACK
371 tristate '"NOTRACK" target support'
372 depends on NETFILTER_XTABLES
373 depends on IP_NF_RAW || IP6_NF_RAW
374 depends on NF_CONNTRACK
376 The NOTRACK target allows a select rule to specify
377 which packets *not* to enter the conntrack/NAT
378 subsystem with all the consequences (no ICMP error tracking,
379 no protocol helpers for the selected packets).
381 If you want to compile it as a module, say M here and read
382 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
384 config NETFILTER_XT_TARGET_SECMARK
385 tristate '"SECMARK" target support'
386 depends on NETFILTER_XTABLES && NETWORK_SECMARK
388 The SECMARK target allows security marking of network
389 packets, for use with security subsystems.
391 To compile it as a module, choose M here. If unsure, say N.
393 config NETFILTER_XT_TARGET_CONNSECMARK
394 tristate '"CONNSECMARK" target support'
395 depends on NETFILTER_XTABLES && NF_CONNTRACK && NF_CONNTRACK_SECMARK
397 The CONNSECMARK target copies security markings from packets
398 to connections, and restores security markings from connections
399 to packets (if the packets are not already marked). This would
400 normally be used in conjunction with the SECMARK target.
402 To compile it as a module, choose M here. If unsure, say N.
404 config NETFILTER_XT_TARGET_TCPMSS
405 tristate '"TCPMSS" target support'
406 depends on NETFILTER_XTABLES && (IPV6 || IPV6=n)
408 This option adds a `TCPMSS' target, which allows you to alter the
409 MSS value of TCP SYN packets, to control the maximum size for that
410 connection (usually limiting it to your outgoing interface's MTU
413 This is used to overcome criminally braindead ISPs or servers which
414 block ICMP Fragmentation Needed packets. The symptoms of this
415 problem are that everything works fine from your Linux
416 firewall/router, but machines behind it can never exchange large
418 1) Web browsers connect, then hang with no data received.
419 2) Small mail works fine, but large emails hang.
420 3) ssh works fine, but scp hangs after initial handshaking.
422 Workaround: activate this option and add a rule to your firewall
425 iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
426 -j TCPMSS --clamp-mss-to-pmtu
428 To compile it as a module, choose M here. If unsure, say N.
430 config NETFILTER_XT_MATCH_COMMENT
431 tristate '"comment" match support'
432 depends on NETFILTER_XTABLES
434 This option adds a `comment' dummy-match, which allows you to put
435 comments in your iptables ruleset.
437 If you want to compile it as a module, say M here and read
438 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
440 config NETFILTER_XT_MATCH_CONNBYTES
441 tristate '"connbytes" per-connection counter match support'
442 depends on NETFILTER_XTABLES
443 depends on NF_CONNTRACK
446 This option adds a `connbytes' match, which allows you to match the
447 number of bytes and/or packets for each direction within a connection.
449 If you want to compile it as a module, say M here and read
450 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
452 config NETFILTER_XT_MATCH_CONNLIMIT
453 tristate '"connlimit" match support"'
454 depends on NETFILTER_XTABLES
456 This match allows you to match against the number of parallel
457 connections to a server per client IP address (or address block).
459 config NETFILTER_XT_MATCH_CONNMARK
460 tristate '"connmark" connection mark match support'
461 depends on NETFILTER_XTABLES
462 depends on NF_CONNTRACK
463 select NF_CONNTRACK_MARK
465 This option adds a `connmark' match, which allows you to match the
466 connection mark value previously set for the session by `CONNMARK'.
468 If you want to compile it as a module, say M here and read
469 <file:Documentation/kbuild/modules.txt>. The module will be called
470 ipt_connmark.ko. If unsure, say `N'.
472 config NETFILTER_XT_MATCH_CONNTRACK
473 tristate '"conntrack" connection tracking match support'
474 depends on NETFILTER_XTABLES
475 depends on NF_CONNTRACK
477 This is a general conntrack match module, a superset of the state match.
479 It allows matching on additional conntrack information, which is
480 useful in complex configurations, such as NAT gateways with multiple
481 internet links or tunnels.
483 To compile it as a module, choose M here. If unsure, say N.
485 config NETFILTER_XT_MATCH_DCCP
486 tristate '"DCCP" protocol match support'
487 depends on NETFILTER_XTABLES
489 With this option enabled, you will be able to use the iptables
490 `dccp' match in order to match on DCCP source/destination ports
493 If you want to compile it as a module, say M here and read
494 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
496 config NETFILTER_XT_MATCH_DSCP
497 tristate '"DSCP" match support'
498 depends on NETFILTER_XTABLES
500 This option adds a `DSCP' match, which allows you to match against
501 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
503 The DSCP field can have any value between 0x0 and 0x3f inclusive.
505 To compile it as a module, choose M here. If unsure, say N.
507 config NETFILTER_XT_MATCH_ESP
508 tristate '"ESP" match support'
509 depends on NETFILTER_XTABLES
511 This match extension allows you to match a range of SPIs
512 inside ESP header of IPSec packets.
514 To compile it as a module, choose M here. If unsure, say N.
516 config NETFILTER_XT_MATCH_HELPER
517 tristate '"helper" match support'
518 depends on NETFILTER_XTABLES
519 depends on NF_CONNTRACK
521 Helper matching allows you to match packets in dynamic connections
522 tracked by a conntrack-helper, ie. ip_conntrack_ftp
524 To compile it as a module, choose M here. If unsure, say Y.
526 config NETFILTER_XT_MATCH_HL
527 tristate '"hl" hoplimit/TTL match support'
528 depends on NETFILTER_XTABLES
530 HL matching allows you to match packets based on the hoplimit
531 in the IPv6 header, or the time-to-live field in the IPv4
532 header of the packet.
534 config NETFILTER_XT_MATCH_IPRANGE
535 tristate '"iprange" address range match support'
536 depends on NETFILTER_XTABLES
538 This option adds a "iprange" match, which allows you to match based on
539 an IP address range. (Normal iptables only matches on single addresses
540 with an optional mask.)
544 config NETFILTER_XT_MATCH_LENGTH
545 tristate '"length" match support'
546 depends on NETFILTER_XTABLES
548 This option allows you to match the length of a packet against a
549 specific value or range of values.
551 To compile it as a module, choose M here. If unsure, say N.
553 config NETFILTER_XT_MATCH_LIMIT
554 tristate '"limit" match support'
555 depends on NETFILTER_XTABLES
557 limit matching allows you to control the rate at which a rule can be
558 matched: mainly useful in combination with the LOG target ("LOG
559 target support", below) and to avoid some Denial of Service attacks.
561 To compile it as a module, choose M here. If unsure, say N.
563 config NETFILTER_XT_MATCH_MAC
564 tristate '"mac" address match support'
565 depends on NETFILTER_XTABLES
567 MAC matching allows you to match packets based on the source
568 Ethernet address of the packet.
570 To compile it as a module, choose M here. If unsure, say N.
572 config NETFILTER_XT_MATCH_MARK
573 tristate '"mark" match support'
574 depends on NETFILTER_XTABLES
576 Netfilter mark matching allows you to match packets based on the
577 `nfmark' value in the packet. This can be set by the MARK target
580 To compile it as a module, choose M here. If unsure, say N.
582 config NETFILTER_XT_MATCH_POLICY
583 tristate 'IPsec "policy" match support'
584 depends on NETFILTER_XTABLES && XFRM
586 Policy matching allows you to match packets based on the
587 IPsec policy that was used during decapsulation/will
588 be used during encapsulation.
590 To compile it as a module, choose M here. If unsure, say N.
592 config NETFILTER_XT_MATCH_MULTIPORT
593 tristate "Multiple port match support"
594 depends on NETFILTER_XTABLES
596 Multiport matching allows you to match TCP or UDP packets based on
597 a series of source or destination ports: normally a rule can only
598 match a single range of ports.
600 To compile it as a module, choose M here. If unsure, say N.
602 config NETFILTER_XT_MATCH_PHYSDEV
603 tristate '"physdev" match support'
604 depends on NETFILTER_XTABLES && BRIDGE && BRIDGE_NETFILTER
606 Physdev packet matching matches against the physical bridge ports
607 the IP packet arrived on or will leave by.
609 To compile it as a module, choose M here. If unsure, say N.
611 config NETFILTER_XT_MATCH_PKTTYPE
612 tristate '"pkttype" packet type match support'
613 depends on NETFILTER_XTABLES
615 Packet type matching allows you to match a packet by
616 its "class", eg. BROADCAST, MULTICAST, ...
619 iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG
621 To compile it as a module, choose M here. If unsure, say N.
623 config NETFILTER_XT_MATCH_QUOTA
624 tristate '"quota" match support'
625 depends on NETFILTER_XTABLES
627 This option adds a `quota' match, which allows to match on a
630 If you want to compile it as a module, say M here and read
631 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
633 config NETFILTER_XT_MATCH_REALM
634 tristate '"realm" match support'
635 depends on NETFILTER_XTABLES
638 This option adds a `realm' match, which allows you to use the realm
639 key from the routing subsystem inside iptables.
641 This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option
644 If you want to compile it as a module, say M here and read
645 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
647 config NETFILTER_XT_MATCH_RECENT
648 tristate '"recent" match support'
649 depends on NETFILTER_XTABLES
651 This match is used for creating one or many lists of recently
652 used addresses and then matching against that/those list(s).
654 Short options are available by using 'iptables -m recent -h'
655 Official Website: <http://snowman.net/projects/ipt_recent/>
657 config NETFILTER_XT_MATCH_RECENT_PROC_COMPAT
658 bool 'Enable obsolete /proc/net/ipt_recent'
659 depends on NETFILTER_XT_MATCH_RECENT && PROC_FS
661 This option enables the old /proc/net/ipt_recent interface,
662 which has been obsoleted by /proc/net/xt_recent.
664 config NETFILTER_XT_MATCH_SCTP
665 tristate '"sctp" protocol match support (EXPERIMENTAL)'
666 depends on NETFILTER_XTABLES && EXPERIMENTAL
668 With this option enabled, you will be able to use the
669 `sctp' match in order to match on SCTP source/destination ports
670 and SCTP chunk types.
672 If you want to compile it as a module, say M here and read
673 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
675 config NETFILTER_XT_MATCH_STATE
676 tristate '"state" match support'
677 depends on NETFILTER_XTABLES
678 depends on NF_CONNTRACK
680 Connection state matching allows you to match packets based on their
681 relationship to a tracked connection (ie. previous packets). This
682 is a powerful tool for packet classification.
684 To compile it as a module, choose M here. If unsure, say N.
686 config NETFILTER_XT_MATCH_LAYER7
687 tristate '"layer7" match support'
688 depends on NETFILTER_XTABLES
689 depends on EXPERIMENTAL && (IP_NF_CONNTRACK || NF_CONNTRACK)
690 depends on NF_CT_ACCT
692 Say Y if you want to be able to classify connections (and their
693 packets) based on regular expression matching of their application
694 layer data. This is one way to classify applications such as
695 peer-to-peer filesharing systems that do not always use the same
698 To compile it as a module, choose M here. If unsure, say N.
700 config NETFILTER_XT_MATCH_LAYER7_DEBUG
701 bool 'Layer 7 debugging output'
702 depends on NETFILTER_XT_MATCH_LAYER7
704 Say Y to get lots of debugging output.
707 config NETFILTER_XT_MATCH_STATISTIC
708 tristate '"statistic" match support'
709 depends on NETFILTER_XTABLES
711 This option adds a `statistic' match, which allows you to match
712 on packets periodically or randomly with a given percentage.
714 To compile it as a module, choose M here. If unsure, say N.
716 config NETFILTER_XT_MATCH_TIME
717 tristate '"time" match support'
718 depends on NETFILTER_XTABLES
720 This option adds a "time" match, which allows you to match based on
721 the packet arrival time (at the machine which netfilter is running)
722 on) or departure time/date (for locally generated packets).
724 If you say Y here, try `iptables -m time --help` for
727 To compile it as a module, choose M here. If unsure, say N.
729 config NETFILTER_XT_MATCH_STRING
730 tristate '"string" match support'
731 depends on NETFILTER_XTABLES
733 select TEXTSEARCH_KMP
735 select TEXTSEARCH_FSM
737 This option adds a `string' match, which allows you to look for
738 pattern matchings in packets.
740 To compile it as a module, choose M here. If unsure, say N.
742 config NETFILTER_XT_MATCH_WEBSTR
743 tristate '"webstr" match support'
744 depends on NETFILTER_XTABLES
746 This option adds a `webstr' match, which allows you to look for
747 pattern matchings in http stream.
749 To compile it as a module, choose M here. If unsure, say N.
751 config NETFILTER_XT_MATCH_WEB
752 tristate '"web" match support (EXPERIMENTAL)'
753 depends on EXPERIMENTAL && NETFILTER_XTABLES
755 This option adds a `web' match, which allows you to look for
756 pattern matchings in http stream.
758 To compile it as a module, choose M here. If unsure, say N.
760 config NETFILTER_XT_MATCH_TCPMSS
761 tristate '"tcpmss" match support'
762 depends on NETFILTER_XTABLES
764 This option adds a `tcpmss' match, which allows you to examine the
765 MSS value of TCP SYN packets, which control the maximum packet size
768 To compile it as a module, choose M here. If unsure, say N.
770 config NETFILTER_XT_MATCH_HASHLIMIT
771 tristate '"hashlimit" match support'
772 depends on NETFILTER_XTABLES && (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
774 This option adds a `hashlimit' match.
776 As opposed to `limit', this match dynamically creates a hash table
777 of limit buckets, based on your selection of source/destination
778 addresses and/or ports.
780 It enables you to express policies like `10kpps for any given
781 destination address' or `500pps from any given source address'
784 config NETFILTER_XT_MATCH_CONDITION
785 tristate '"condition" match support'
786 depends on NETFILTER_XTABLES
788 This option allows you to match firewall rules against condition
789 variables stored in the /proc/net/nf_condition directory.
791 N.B.: older versions used /proc/net/ipt_condition. You can
792 reenable it with "compat_dir_name".
794 If you want to compile it as a module, say M here and read
795 Documentation/modules.txt. If unsure, say `N'.
797 config NETFILTER_XT_MATCH_GEOIP
798 tristate '"geoip" match support'
799 depends on NETFILTER_XTABLES
801 This option allows you to match a packet by its source or
802 destination country. Basically, you need a country's
803 database containing all subnets and associated countries.
805 For the complete procedure and understanding, read :
806 http://people.netfilter.org/acidfu/geoip/howto/geoip-HOWTO.html
808 If you want to compile it as a module, say M here and read
809 <file:Documentation/modules.txt>. The module will be
810 called `ipt_geoip'. If unsure, say `N'.