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_CT_PROTO_UDPLITE
106 tristate 'UDP-Lite protocol connection tracking support (EXPERIMENTAL)'
107 depends on EXPERIMENTAL && NF_CONNTRACK
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
119 select TEXTSEARCH_KMP
121 If you are running the Amanda backup package <http://www.amanda.org/>
122 on this machine or machines that will be MASQUERADED through this
123 machine, then you may want to enable this feature. This allows the
124 connection tracking and natting code to allow the sub-channels that
125 Amanda requires for communication of the backup data, messages and
128 To compile it as a module, choose M here. If unsure, say N.
130 config NF_CONNTRACK_FTP
131 tristate "FTP protocol support"
132 depends on NF_CONNTRACK
134 Tracking FTP connections is problematic: special helpers are
135 required for tracking them, and doing masquerading and other forms
136 of Network Address Translation on them.
138 This is FTP support on Layer 3 independent connection tracking.
139 Layer 3 independent connection tracking is experimental scheme
140 which generalize ip_conntrack to support other layer 3 protocols.
142 To compile it as a module, choose M here. If unsure, say N.
144 config NF_CONNTRACK_H323
145 tristate "H.323 protocol support (EXPERIMENTAL)"
146 depends on EXPERIMENTAL && NF_CONNTRACK && (IPV6 || IPV6=n)
148 H.323 is a VoIP signalling protocol from ITU-T. As one of the most
149 important VoIP protocols, it is widely used by voice hardware and
150 software including voice gateways, IP phones, Netmeeting, OpenPhone,
153 With this module you can support H.323 on a connection tracking/NAT
156 This module supports RAS, Fast Start, H.245 Tunnelling, Call
157 Forwarding, RTP/RTCP and T.120 based audio, video, fax, chat,
158 whiteboard, file transfer, etc. For more information, please
159 visit http://nath323.sourceforge.net/.
161 To compile it as a module, choose M here. If unsure, say N.
163 config NF_CONNTRACK_IRC
164 tristate "IRC protocol support"
165 depends on NF_CONNTRACK
167 There is a commonly-used extension to IRC called
168 Direct Client-to-Client Protocol (DCC). This enables users to send
169 files to each other, and also chat to each other without the need
170 of a server. DCC Sending is used anywhere you send files over IRC,
171 and DCC Chat is most commonly used by Eggdrop bots. If you are
172 using NAT, this extension will enable you to send files and initiate
173 chats. Note that you do NOT need this extension to get files or
174 have others initiate chats, or everything else in IRC.
176 To compile it as a module, choose M here. If unsure, say N.
178 config NF_CONNTRACK_NETBIOS_NS
179 tristate "NetBIOS name service protocol support (EXPERIMENTAL)"
180 depends on EXPERIMENTAL && NF_CONNTRACK
182 NetBIOS name service requests are sent as broadcast messages from an
183 unprivileged port and responded to with unicast messages to the
184 same port. This make them hard to firewall properly because connection
185 tracking doesn't deal with broadcasts. This helper tracks locally
186 originating NetBIOS name service requests and the corresponding
187 responses. It relies on correct IP address configuration, specifically
188 netmask and broadcast address. When properly configured, the output
189 of "ip address show" should look similar to this:
191 $ ip -4 address show eth0
192 4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
193 inet 172.16.2.252/24 brd 172.16.2.255 scope global eth0
195 To compile it as a module, choose M here. If unsure, say N.
197 config NF_CONNTRACK_PPTP
198 tristate "PPtP protocol support"
199 depends on NF_CONNTRACK
200 select NF_CT_PROTO_GRE
202 This module adds support for PPTP (Point to Point Tunnelling
203 Protocol, RFC2637) connection tracking and NAT.
205 If you are running PPTP sessions over a stateful firewall or NAT
206 box, you may want to enable this feature.
208 Please note that not all PPTP modes of operation are supported yet.
209 Specifically these limitations exist:
210 - Blindly assumes that control connections are always established
211 in PNS->PAC direction. This is a violation of RFC2637.
212 - Only supports a single call within each session
214 To compile it as a module, choose M here. If unsure, say N.
216 config NF_CONNTRACK_SANE
217 tristate "SANE protocol support (EXPERIMENTAL)"
218 depends on EXPERIMENTAL && NF_CONNTRACK
220 SANE is a protocol for remote access to scanners as implemented
221 by the 'saned' daemon. Like FTP, it uses separate control and
224 With this module you can support SANE on a connection tracking
227 To compile it as a module, choose M here. If unsure, say N.
229 config NF_CONNTRACK_SIP
230 tristate "SIP protocol support (EXPERIMENTAL)"
231 depends on EXPERIMENTAL && NF_CONNTRACK
233 SIP is an application-layer control protocol that can establish,
234 modify, and terminate multimedia sessions (conferences) such as
235 Internet telephony calls. With the ip_conntrack_sip and
236 the nf_nat_sip modules you can support the protocol on a connection
237 tracking/NATing firewall.
239 To compile it as a module, choose M here. If unsure, say N.
241 config NF_CONNTRACK_TFTP
242 tristate "TFTP protocol support"
243 depends on NF_CONNTRACK
245 TFTP connection tracking helper, this is required depending
246 on how restrictive your ruleset is.
247 If you are using a tftp client behind -j SNAT or -j MASQUERADING
250 To compile it as a module, choose M here. If unsure, say N.
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" and "TOS" 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 It also adds the "TOS" target, which allows you to create rules in
306 the "mangle" table which alter the Type Of Service field of an IPv4
307 or the Priority field of an IPv6 packet, prior to routing.
309 To compile it as a module, choose M here. If unsure, say N.
311 config NETFILTER_XT_TARGET_MARK
312 tristate '"MARK" target support'
313 depends on NETFILTER_XTABLES
315 This option adds a `MARK' target, which allows you to create rules
316 in the `mangle' table which alter the netfilter mark (nfmark) field
317 associated with the packet prior to routing. This can change
318 the routing method (see `Use netfilter MARK value as routing
319 key') and can also be used by other subsystems to change their
322 To compile it as a module, choose M here. If unsure, say N.
324 config NETFILTER_XT_TARGET_NFQUEUE
325 tristate '"NFQUEUE" target Support'
326 depends on NETFILTER_XTABLES
328 This target replaced the old obsolete QUEUE target.
330 As opposed to QUEUE, it supports 65535 different queues,
333 To compile it as a module, choose M here. If unsure, say N.
335 config NETFILTER_XT_TARGET_NFLOG
336 tristate '"NFLOG" target support'
337 depends on NETFILTER_XTABLES
339 This option enables the NFLOG target, which allows to LOG
340 messages through the netfilter logging API, which can use
341 either the old LOG target, the old ULOG target or nfnetlink_log
344 To compile it as a module, choose M here. If unsure, say N.
346 config NETFILTER_XT_TARGET_NOTRACK
347 tristate '"NOTRACK" target support'
348 depends on NETFILTER_XTABLES
349 depends on IP_NF_RAW || IP6_NF_RAW
350 depends on NF_CONNTRACK
352 The NOTRACK target allows a select rule to specify
353 which packets *not* to enter the conntrack/NAT
354 subsystem with all the consequences (no ICMP error tracking,
355 no protocol helpers for the selected packets).
357 If you want to compile it as a module, say M here and read
358 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
360 config NETFILTER_XT_TARGET_RATEEST
361 tristate '"RATEEST" target support'
362 depends on NETFILTER_XTABLES
364 This option adds a `RATEEST' target, which allows to measure
365 rates similar to TC estimators. The `rateest' match can be
366 used to match on the measured rates.
368 To compile it as a module, choose M here. If unsure, say N.
370 config NETFILTER_XT_TARGET_TRACE
371 tristate '"TRACE" target support'
372 depends on NETFILTER_XTABLES
373 depends on IP_NF_RAW || IP6_NF_RAW
375 The TRACE target allows you to mark packets so that the kernel
376 will log every rule which match the packets as those traverse
377 the tables, chains, rules.
379 If you want to compile it as a module, say M here and read
380 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
382 config NETFILTER_XT_TARGET_SECMARK
383 tristate '"SECMARK" target support'
384 depends on NETFILTER_XTABLES && NETWORK_SECMARK
386 The SECMARK target allows security marking of network
387 packets, for use with security subsystems.
389 To compile it as a module, choose M here. If unsure, say N.
391 config NETFILTER_XT_TARGET_CONNSECMARK
392 tristate '"CONNSECMARK" target support'
393 depends on NETFILTER_XTABLES && NF_CONNTRACK && NF_CONNTRACK_SECMARK
395 The CONNSECMARK target copies security markings from packets
396 to connections, and restores security markings from connections
397 to packets (if the packets are not already marked). This would
398 normally be used in conjunction with the SECMARK target.
400 To compile it as a module, choose M here. If unsure, say N.
402 config NETFILTER_XT_TARGET_TCPMSS
403 tristate '"TCPMSS" target support'
404 depends on NETFILTER_XTABLES && (IPV6 || IPV6=n)
406 This option adds a `TCPMSS' target, which allows you to alter the
407 MSS value of TCP SYN packets, to control the maximum size for that
408 connection (usually limiting it to your outgoing interface's MTU
411 This is used to overcome criminally braindead ISPs or servers which
412 block ICMP Fragmentation Needed packets. The symptoms of this
413 problem are that everything works fine from your Linux
414 firewall/router, but machines behind it can never exchange large
416 1) Web browsers connect, then hang with no data received.
417 2) Small mail works fine, but large emails hang.
418 3) ssh works fine, but scp hangs after initial handshaking.
420 Workaround: activate this option and add a rule to your firewall
423 iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
424 -j TCPMSS --clamp-mss-to-pmtu
426 To compile it as a module, choose M here. If unsure, say N.
428 config NETFILTER_XT_TARGET_TCPOPTSTRIP
429 tristate '"TCPOPTSTRIP" target support (EXPERIMENTAL)'
430 depends on EXPERIMENTAL && NETFILTER_XTABLES
431 depends on IP_NF_MANGLE || IP6_NF_MANGLE
433 This option adds a "TCPOPTSTRIP" target, which allows you to strip
434 TCP options from TCP packets.
436 config NETFILTER_XT_MATCH_COMMENT
437 tristate '"comment" match support'
438 depends on NETFILTER_XTABLES
440 This option adds a `comment' dummy-match, which allows you to put
441 comments in your iptables ruleset.
443 If you want to compile it as a module, say M here and read
444 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
446 config NETFILTER_XT_MATCH_CONNBYTES
447 tristate '"connbytes" per-connection counter match support'
448 depends on NETFILTER_XTABLES
449 depends on NF_CONNTRACK
452 This option adds a `connbytes' match, which allows you to match the
453 number of bytes and/or packets for each direction within a connection.
455 If you want to compile it as a module, say M here and read
456 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
458 config NETFILTER_XT_MATCH_CONNLIMIT
459 tristate '"connlimit" match support"'
460 depends on NETFILTER_XTABLES
461 depends on NF_CONNTRACK
463 This match allows you to match against the number of parallel
464 connections to a server per client IP address (or address block).
466 config NETFILTER_XT_MATCH_CONNMARK
467 tristate '"connmark" connection mark match support'
468 depends on NETFILTER_XTABLES
469 depends on NF_CONNTRACK
470 select NF_CONNTRACK_MARK
472 This option adds a `connmark' match, which allows you to match the
473 connection mark value previously set for the session by `CONNMARK'.
475 If you want to compile it as a module, say M here and read
476 <file:Documentation/kbuild/modules.txt>. The module will be called
477 ipt_connmark.ko. If unsure, say `N'.
479 config NETFILTER_XT_MATCH_CONNTRACK
480 tristate '"conntrack" connection tracking match support'
481 depends on NETFILTER_XTABLES
482 depends on NF_CONNTRACK
484 This is a general conntrack match module, a superset of the state match.
486 It allows matching on additional conntrack information, which is
487 useful in complex configurations, such as NAT gateways with multiple
488 internet links or tunnels.
490 To compile it as a module, choose M here. If unsure, say N.
492 config NETFILTER_XT_MATCH_DCCP
493 tristate '"dccp" protocol match support'
494 depends on NETFILTER_XTABLES
496 With this option enabled, you will be able to use the iptables
497 `dccp' match in order to match on DCCP source/destination ports
500 If you want to compile it as a module, say M here and read
501 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
503 config NETFILTER_XT_MATCH_DSCP
504 tristate '"dscp" and "tos" match support'
505 depends on NETFILTER_XTABLES
507 This option adds a `DSCP' match, which allows you to match against
508 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
510 The DSCP field can have any value between 0x0 and 0x3f inclusive.
512 It will also add a "tos" match, which allows you to match packets
513 based on the Type Of Service fields of the IPv4 packet (which share
514 the same bits as DSCP).
516 To compile it as a module, choose M here. If unsure, say N.
518 config NETFILTER_XT_MATCH_ESP
519 tristate '"esp" match support'
520 depends on NETFILTER_XTABLES
522 This match extension allows you to match a range of SPIs
523 inside ESP header of IPSec packets.
525 To compile it as a module, choose M here. If unsure, say N.
527 config NETFILTER_XT_MATCH_HELPER
528 tristate '"helper" match support'
529 depends on NETFILTER_XTABLES
530 depends on NF_CONNTRACK
532 Helper matching allows you to match packets in dynamic connections
533 tracked by a conntrack-helper, ie. ip_conntrack_ftp
535 To compile it as a module, choose M here. If unsure, say Y.
537 config NETFILTER_XT_MATCH_LENGTH
538 tristate '"length" match support'
539 depends on NETFILTER_XTABLES
541 This option allows you to match the length of a packet against a
542 specific value or range of values.
544 To compile it as a module, choose M here. If unsure, say N.
546 config NETFILTER_XT_MATCH_LIMIT
547 tristate '"limit" match support'
548 depends on NETFILTER_XTABLES
550 limit matching allows you to control the rate at which a rule can be
551 matched: mainly useful in combination with the LOG target ("LOG
552 target support", below) and to avoid some Denial of Service attacks.
554 To compile it as a module, choose M here. If unsure, say N.
556 config NETFILTER_XT_MATCH_MAC
557 tristate '"mac" address match support'
558 depends on NETFILTER_XTABLES
560 MAC matching allows you to match packets based on the source
561 Ethernet address of the packet.
563 To compile it as a module, choose M here. If unsure, say N.
565 config NETFILTER_XT_MATCH_MARK
566 tristate '"mark" match support'
567 depends on NETFILTER_XTABLES
569 Netfilter mark matching allows you to match packets based on the
570 `nfmark' value in the packet. This can be set by the MARK target
573 To compile it as a module, choose M here. If unsure, say N.
575 config NETFILTER_XT_MATCH_OWNER
576 tristate '"owner" match support'
577 depends on NETFILTER_XTABLES
579 Socket owner matching allows you to match locally-generated packets
580 based on who created the socket: the user or group. It is also
581 possible to check whether a socket actually exists.
583 config NETFILTER_XT_MATCH_POLICY
584 tristate 'IPsec "policy" match support'
585 depends on NETFILTER_XTABLES && XFRM
587 Policy matching allows you to match packets based on the
588 IPsec policy that was used during decapsulation/will
589 be used during encapsulation.
591 To compile it as a module, choose M here. If unsure, say N.
593 config NETFILTER_XT_MATCH_MULTIPORT
594 tristate '"multiport" Multiple port match support'
595 depends on NETFILTER_XTABLES
597 Multiport matching allows you to match TCP or UDP packets based on
598 a series of source or destination ports: normally a rule can only
599 match a single range of ports.
601 To compile it as a module, choose M here. If unsure, say N.
603 config NETFILTER_XT_MATCH_PHYSDEV
604 tristate '"physdev" match support'
605 depends on NETFILTER_XTABLES && BRIDGE && BRIDGE_NETFILTER
607 Physdev packet matching matches against the physical bridge ports
608 the IP packet arrived on or will leave by.
610 To compile it as a module, choose M here. If unsure, say N.
612 config NETFILTER_XT_MATCH_PKTTYPE
613 tristate '"pkttype" packet type match support'
614 depends on NETFILTER_XTABLES
616 Packet type matching allows you to match a packet by
617 its "class", eg. BROADCAST, MULTICAST, ...
620 iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG
622 To compile it as a module, choose M here. If unsure, say N.
624 config NETFILTER_XT_MATCH_QUOTA
625 tristate '"quota" match support'
626 depends on NETFILTER_XTABLES
628 This option adds a `quota' match, which allows to match on a
631 If you want to compile it as a module, say M here and read
632 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
634 config NETFILTER_XT_MATCH_RATEEST
635 tristate '"rateest" match support'
636 depends on NETFILTER_XTABLES
637 select NETFILTER_XT_TARGET_RATEEST
639 This option adds a `rateest' match, which allows to match on the
640 rate estimated by the RATEEST target.
642 To compile it as a module, choose M here. If unsure, say N.
644 config NETFILTER_XT_MATCH_REALM
645 tristate '"realm" match support'
646 depends on NETFILTER_XTABLES
649 This option adds a `realm' match, which allows you to use the realm
650 key from the routing subsystem inside iptables.
652 This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option
655 If you want to compile it as a module, say M here and read
656 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
658 config NETFILTER_XT_MATCH_SCTP
659 tristate '"sctp" protocol match support (EXPERIMENTAL)'
660 depends on NETFILTER_XTABLES && EXPERIMENTAL
662 With this option enabled, you will be able to use the
663 `sctp' match in order to match on SCTP source/destination ports
664 and SCTP chunk types.
666 If you want to compile it as a module, say M here and read
667 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
669 config NETFILTER_XT_MATCH_STATE
670 tristate '"state" match support'
671 depends on NETFILTER_XTABLES
672 depends on NF_CONNTRACK
674 Connection state matching allows you to match packets based on their
675 relationship to a tracked connection (ie. previous packets). This
676 is a powerful tool for packet classification.
678 To compile it as a module, choose M here. If unsure, say N.
680 config NETFILTER_XT_MATCH_STATISTIC
681 tristate '"statistic" match support'
682 depends on NETFILTER_XTABLES
684 This option adds a `statistic' match, which allows you to match
685 on packets periodically or randomly with a given percentage.
687 To compile it as a module, choose M here. If unsure, say N.
689 config NETFILTER_XT_MATCH_STRING
690 tristate '"string" match support'
691 depends on NETFILTER_XTABLES
693 select TEXTSEARCH_KMP
695 select TEXTSEARCH_FSM
697 This option adds a `string' match, which allows you to look for
698 pattern matchings in packets.
700 To compile it as a module, choose M here. If unsure, say N.
702 config NETFILTER_XT_MATCH_TCPMSS
703 tristate '"tcpmss" match support'
704 depends on NETFILTER_XTABLES
706 This option adds a `tcpmss' match, which allows you to examine the
707 MSS value of TCP SYN packets, which control the maximum packet size
710 To compile it as a module, choose M here. If unsure, say N.
712 config NETFILTER_XT_MATCH_TIME
713 tristate '"time" match support'
714 depends on NETFILTER_XTABLES
716 This option adds a "time" match, which allows you to match based on
717 the packet arrival time (at the machine which netfilter is running)
718 on) or departure time/date (for locally generated packets).
720 If you say Y here, try `iptables -m time --help` for
723 If you want to compile it as a module, say M here.
726 config NETFILTER_XT_MATCH_U32
727 tristate '"u32" match support'
728 depends on NETFILTER_XTABLES
730 u32 allows you to extract quantities of up to 4 bytes from a packet,
731 AND them with specified masks, shift them by specified amounts and
732 test whether the results are in any of a set of specified ranges.
733 The specification of what to extract is general enough to skip over
734 headers with lengths stored in the packet, as in IP or TCP header
737 Details and examples are in the kernel module source.
739 config NETFILTER_XT_MATCH_HASHLIMIT
740 tristate '"hashlimit" match support'
741 depends on NETFILTER_XTABLES && (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
743 This option adds a `hashlimit' match.
745 As opposed to `limit', this match dynamically creates a hash table
746 of limit buckets, based on your selection of source/destination
747 addresses and/or ports.
749 It enables you to express policies like `10kpps for any given
750 destination address' or `500pps from any given source address'