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_MARK
322 tristate '"MARK" target support'
323 depends on NETFILTER_XTABLES
325 This option adds a `MARK' target, which allows you to create rules
326 in the `mangle' table which alter the netfilter mark (nfmark) field
327 associated with the packet prior to routing. This can change
328 the routing method (see `Use netfilter MARK value as routing
329 key') and can also be used by other subsystems to change their
332 To compile it as a module, choose M here. If unsure, say N.
334 config NETFILTER_XT_TARGET_NFQUEUE
335 tristate '"NFQUEUE" target Support'
336 depends on NETFILTER_XTABLES
338 This target replaced the old obsolete QUEUE target.
340 As opposed to QUEUE, it supports 65535 different queues,
343 To compile it as a module, choose M here. If unsure, say N.
345 config NETFILTER_XT_TARGET_NFLOG
346 tristate '"NFLOG" target support'
347 depends on NETFILTER_XTABLES
349 This option enables the NFLOG target, which allows to LOG
350 messages through the netfilter logging API, which can use
351 either the old LOG target, the old ULOG target or nfnetlink_log
354 To compile it as a module, choose M here. If unsure, say N.
356 config NETFILTER_XT_TARGET_NOTRACK
357 tristate '"NOTRACK" target support'
358 depends on NETFILTER_XTABLES
359 depends on IP_NF_RAW || IP6_NF_RAW
360 depends on NF_CONNTRACK
362 The NOTRACK target allows a select rule to specify
363 which packets *not* to enter the conntrack/NAT
364 subsystem with all the consequences (no ICMP error tracking,
365 no protocol helpers for the selected packets).
367 If you want to compile it as a module, say M here and read
368 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
370 config NETFILTER_XT_TARGET_SECMARK
371 tristate '"SECMARK" target support'
372 depends on NETFILTER_XTABLES && NETWORK_SECMARK
374 The SECMARK target allows security marking of network
375 packets, for use with security subsystems.
377 To compile it as a module, choose M here. If unsure, say N.
379 config NETFILTER_XT_TARGET_CONNSECMARK
380 tristate '"CONNSECMARK" target support'
381 depends on NETFILTER_XTABLES && NF_CONNTRACK && NF_CONNTRACK_SECMARK
383 The CONNSECMARK target copies security markings from packets
384 to connections, and restores security markings from connections
385 to packets (if the packets are not already marked). This would
386 normally be used in conjunction with the SECMARK target.
388 To compile it as a module, choose M here. If unsure, say N.
390 config NETFILTER_XT_TARGET_TCPMSS
391 tristate '"TCPMSS" target support'
392 depends on NETFILTER_XTABLES && (IPV6 || IPV6=n)
394 This option adds a `TCPMSS' target, which allows you to alter the
395 MSS value of TCP SYN packets, to control the maximum size for that
396 connection (usually limiting it to your outgoing interface's MTU
399 This is used to overcome criminally braindead ISPs or servers which
400 block ICMP Fragmentation Needed packets. The symptoms of this
401 problem are that everything works fine from your Linux
402 firewall/router, but machines behind it can never exchange large
404 1) Web browsers connect, then hang with no data received.
405 2) Small mail works fine, but large emails hang.
406 3) ssh works fine, but scp hangs after initial handshaking.
408 Workaround: activate this option and add a rule to your firewall
411 iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
412 -j TCPMSS --clamp-mss-to-pmtu
414 To compile it as a module, choose M here. If unsure, say N.
416 config NETFILTER_XT_MATCH_COMMENT
417 tristate '"comment" match support'
418 depends on NETFILTER_XTABLES
420 This option adds a `comment' dummy-match, which allows you to put
421 comments in your iptables ruleset.
423 If you want to compile it as a module, say M here and read
424 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
426 config NETFILTER_XT_MATCH_CONNBYTES
427 tristate '"connbytes" per-connection counter match support'
428 depends on NETFILTER_XTABLES
429 depends on NF_CONNTRACK
432 This option adds a `connbytes' match, which allows you to match the
433 number of bytes and/or packets for each direction within a connection.
435 If you want to compile it as a module, say M here and read
436 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
438 config NETFILTER_XT_MATCH_CONNLIMIT
439 tristate '"connlimit" match support"'
440 depends on NETFILTER_XTABLES
442 This match allows you to match against the number of parallel
443 connections to a server per client IP address (or address block).
445 config NETFILTER_XT_MATCH_CONNMARK
446 tristate '"connmark" connection mark match support'
447 depends on NETFILTER_XTABLES
448 depends on NF_CONNTRACK
449 select NF_CONNTRACK_MARK
451 This option adds a `connmark' match, which allows you to match the
452 connection mark value previously set for the session by `CONNMARK'.
454 If you want to compile it as a module, say M here and read
455 <file:Documentation/kbuild/modules.txt>. The module will be called
456 ipt_connmark.ko. If unsure, say `N'.
458 config NETFILTER_XT_MATCH_CONNTRACK
459 tristate '"conntrack" connection tracking match support'
460 depends on NETFILTER_XTABLES
461 depends on NF_CONNTRACK
463 This is a general conntrack match module, a superset of the state match.
465 It allows matching on additional conntrack information, which is
466 useful in complex configurations, such as NAT gateways with multiple
467 internet links or tunnels.
469 To compile it as a module, choose M here. If unsure, say N.
471 config NETFILTER_XT_MATCH_DCCP
472 tristate '"DCCP" protocol match support'
473 depends on NETFILTER_XTABLES
475 With this option enabled, you will be able to use the iptables
476 `dccp' match in order to match on DCCP source/destination ports
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_DSCP
483 tristate '"DSCP" match support'
484 depends on NETFILTER_XTABLES
486 This option adds a `DSCP' match, which allows you to match against
487 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
489 The DSCP field can have any value between 0x0 and 0x3f inclusive.
491 To compile it as a module, choose M here. If unsure, say N.
493 config NETFILTER_XT_MATCH_ESP
494 tristate '"ESP" match support'
495 depends on NETFILTER_XTABLES
497 This match extension allows you to match a range of SPIs
498 inside ESP header of IPSec packets.
500 To compile it as a module, choose M here. If unsure, say N.
502 config NETFILTER_XT_MATCH_HELPER
503 tristate '"helper" match support'
504 depends on NETFILTER_XTABLES
505 depends on NF_CONNTRACK
507 Helper matching allows you to match packets in dynamic connections
508 tracked by a conntrack-helper, ie. ip_conntrack_ftp
510 To compile it as a module, choose M here. If unsure, say Y.
512 config NETFILTER_XT_MATCH_HL
513 tristate '"hl" hoplimit/TTL match support'
514 depends on NETFILTER_XTABLES
516 HL matching allows you to match packets based on the hoplimit
517 in the IPv6 header, or the time-to-live field in the IPv4
518 header of the packet.
520 config NETFILTER_XT_MATCH_IPRANGE
521 tristate '"iprange" address range match support'
522 depends on NETFILTER_XTABLES
524 This option adds a "iprange" match, which allows you to match based on
525 an IP address range. (Normal iptables only matches on single addresses
526 with an optional mask.)
530 config NETFILTER_XT_MATCH_LENGTH
531 tristate '"length" match support'
532 depends on NETFILTER_XTABLES
534 This option allows you to match the length of a packet against a
535 specific value or range of values.
537 To compile it as a module, choose M here. If unsure, say N.
539 config NETFILTER_XT_MATCH_LIMIT
540 tristate '"limit" match support'
541 depends on NETFILTER_XTABLES
543 limit matching allows you to control the rate at which a rule can be
544 matched: mainly useful in combination with the LOG target ("LOG
545 target support", below) and to avoid some Denial of Service attacks.
547 To compile it as a module, choose M here. If unsure, say N.
549 config NETFILTER_XT_MATCH_MAC
550 tristate '"mac" address match support'
551 depends on NETFILTER_XTABLES
553 MAC matching allows you to match packets based on the source
554 Ethernet address of the packet.
556 To compile it as a module, choose M here. If unsure, say N.
558 config NETFILTER_XT_MATCH_MARK
559 tristate '"mark" match support'
560 depends on NETFILTER_XTABLES
562 Netfilter mark matching allows you to match packets based on the
563 `nfmark' value in the packet. This can be set by the MARK target
566 To compile it as a module, choose M here. If unsure, say N.
568 config NETFILTER_XT_MATCH_POLICY
569 tristate 'IPsec "policy" match support'
570 depends on NETFILTER_XTABLES && XFRM
572 Policy matching allows you to match packets based on the
573 IPsec policy that was used during decapsulation/will
574 be used during encapsulation.
576 To compile it as a module, choose M here. If unsure, say N.
578 config NETFILTER_XT_MATCH_MULTIPORT
579 tristate "Multiple port match support"
580 depends on NETFILTER_XTABLES
582 Multiport matching allows you to match TCP or UDP packets based on
583 a series of source or destination ports: normally a rule can only
584 match a single range of ports.
586 To compile it as a module, choose M here. If unsure, say N.
588 config NETFILTER_XT_MATCH_PHYSDEV
589 tristate '"physdev" match support'
590 depends on NETFILTER_XTABLES && BRIDGE && BRIDGE_NETFILTER
592 Physdev packet matching matches against the physical bridge ports
593 the IP packet arrived on or will leave by.
595 To compile it as a module, choose M here. If unsure, say N.
597 config NETFILTER_XT_MATCH_PKTTYPE
598 tristate '"pkttype" packet type match support'
599 depends on NETFILTER_XTABLES
601 Packet type matching allows you to match a packet by
602 its "class", eg. BROADCAST, MULTICAST, ...
605 iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG
607 To compile it as a module, choose M here. If unsure, say N.
609 config NETFILTER_XT_MATCH_QUOTA
610 tristate '"quota" match support'
611 depends on NETFILTER_XTABLES
613 This option adds a `quota' match, which allows to match on a
616 If you want to compile it as a module, say M here and read
617 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
619 config NETFILTER_XT_MATCH_REALM
620 tristate '"realm" match support'
621 depends on NETFILTER_XTABLES
624 This option adds a `realm' match, which allows you to use the realm
625 key from the routing subsystem inside iptables.
627 This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option
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_RECENT
634 tristate '"recent" match support'
635 depends on NETFILTER_XTABLES
637 This match is used for creating one or many lists of recently
638 used addresses and then matching against that/those list(s).
640 Short options are available by using 'iptables -m recent -h'
641 Official Website: <http://snowman.net/projects/ipt_recent/>
643 config NETFILTER_XT_MATCH_RECENT_PROC_COMPAT
644 bool 'Enable obsolete /proc/net/ipt_recent'
645 depends on NETFILTER_XT_MATCH_RECENT && PROC_FS
647 This option enables the old /proc/net/ipt_recent interface,
648 which has been obsoleted by /proc/net/xt_recent.
650 config NETFILTER_XT_MATCH_SCTP
651 tristate '"sctp" protocol match support (EXPERIMENTAL)'
652 depends on NETFILTER_XTABLES && EXPERIMENTAL
654 With this option enabled, you will be able to use the
655 `sctp' match in order to match on SCTP source/destination ports
656 and SCTP chunk types.
658 If you want to compile it as a module, say M here and read
659 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
661 config NETFILTER_XT_MATCH_STATE
662 tristate '"state" match support'
663 depends on NETFILTER_XTABLES
664 depends on NF_CONNTRACK
666 Connection state matching allows you to match packets based on their
667 relationship to a tracked connection (ie. previous packets). This
668 is a powerful tool for packet classification.
670 To compile it as a module, choose M here. If unsure, say N.
672 config NETFILTER_XT_MATCH_LAYER7
673 tristate '"layer7" match support'
674 depends on NETFILTER_XTABLES
675 depends on EXPERIMENTAL && (IP_NF_CONNTRACK || NF_CONNTRACK)
676 depends on NF_CT_ACCT
678 Say Y if you want to be able to classify connections (and their
679 packets) based on regular expression matching of their application
680 layer data. This is one way to classify applications such as
681 peer-to-peer filesharing systems that do not always use the same
684 To compile it as a module, choose M here. If unsure, say N.
686 config NETFILTER_XT_MATCH_LAYER7_DEBUG
687 bool 'Layer 7 debugging output'
688 depends on NETFILTER_XT_MATCH_LAYER7
690 Say Y to get lots of debugging output.
693 config NETFILTER_XT_MATCH_STATISTIC
694 tristate '"statistic" match support'
695 depends on NETFILTER_XTABLES
697 This option adds a `statistic' match, which allows you to match
698 on packets periodically or randomly with a given percentage.
700 To compile it as a module, choose M here. If unsure, say N.
702 config NETFILTER_XT_MATCH_TIME
703 tristate '"time" match support'
704 depends on NETFILTER_XTABLES
706 This option adds a "time" match, which allows you to match based on
707 the packet arrival time (at the machine which netfilter is running)
708 on) or departure time/date (for locally generated packets).
710 If you say Y here, try `iptables -m time --help` for
713 To compile it as a module, choose M here. If unsure, say N.
715 config NETFILTER_XT_MATCH_STRING
716 tristate '"string" match support'
717 depends on NETFILTER_XTABLES
719 select TEXTSEARCH_KMP
721 select TEXTSEARCH_FSM
723 This option adds a `string' match, which allows you to look for
724 pattern matchings in packets.
726 To compile it as a module, choose M here. If unsure, say N.
728 config NETFILTER_XT_MATCH_WEBSTR
729 tristate '"webstr" match support'
730 depends on NETFILTER_XTABLES
732 This option adds a `webstr' match, which allows you to look for
733 pattern matchings in http stream.
735 To compile it as a module, choose M here. If unsure, say N.
738 config NETFILTER_XT_MATCH_TCPMSS
739 tristate '"tcpmss" match support'
740 depends on NETFILTER_XTABLES
742 This option adds a `tcpmss' match, which allows you to examine the
743 MSS value of TCP SYN packets, which control the maximum packet size
746 To compile it as a module, choose M here. If unsure, say N.
748 config NETFILTER_XT_MATCH_HASHLIMIT
749 tristate '"hashlimit" match support'
750 depends on NETFILTER_XTABLES && (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
752 This option adds a `hashlimit' match.
754 As opposed to `limit', this match dynamically creates a hash table
755 of limit buckets, based on your selection of source/destination
756 addresses and/or ports.
758 It enables you to express policies like `10kpps for any given
759 destination address' or `500pps from any given source address'
762 config NETFILTER_XT_MATCH_CONDITION
763 tristate '"condition" match support'
764 depends on NETFILTER_XTABLES
766 This option allows you to match firewall rules against condition
767 variables stored in the /proc/net/nf_condition directory.
769 N.B.: older versions used /proc/net/ipt_condition. You can
770 reenable it with "compat_dir_name".
772 If you want to compile it as a module, say M here and read
773 Documentation/modules.txt. If unsure, say `N'.
775 config NETFILTER_XT_MATCH_GEOIP
776 tristate '"geoip" match support'
777 depends on NETFILTER_XTABLES
779 This option allows you to match a packet by its source or
780 destination country. Basically, you need a country's
781 database containing all subnets and associated countries.
783 For the complete procedure and understanding, read :
784 http://people.netfilter.org/acidfu/geoip/howto/geoip-HOWTO.html
786 If you want to compile it as a module, say M here and read
787 <file:Documentation/modules.txt>. The module will be
788 called `ipt_geoip'. If unsure, say `N'.