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.
44 bool "Connection tracking flow accounting"
45 depends on NETFILTER_ADVANCED
47 If this option is enabled, the connection tracking code will
48 keep per-flow packet and byte counters.
50 Those counters can be used for flow-based accounting or the
53 Please note that currently this option only sets a default state.
54 You may change it at boot time with nf_conntrack.acct=0/1 kernel
55 parameter or by loading the nf_conntrack module with acct=0/1.
57 You may also disable/enable it on a running system with:
58 sysctl net.netfilter.nf_conntrack_acct=0/1
60 This option will be removed in 2.6.29.
64 config NF_CONNTRACK_MARK
65 bool 'Connection mark tracking support'
66 depends on NETFILTER_ADVANCED
68 This option enables support for connection marks, used by the
69 `CONNMARK' target and `connmark' match. Similar to the mark value
70 of packets, but this mark value is kept in the conntrack session
71 instead of the individual packets.
73 config NF_CONNTRACK_SECMARK
74 bool 'Connection tracking security mark support'
75 depends on NETWORK_SECMARK
76 default m if NETFILTER_ADVANCED=n
78 This option enables security markings to be applied to
79 connections. Typically they are copied to connections from
80 packets using the CONNSECMARK target and copied back from
81 connections to packets with the same target, with the packets
82 being originally labeled via SECMARK.
86 config NF_CONNTRACK_EVENTS
87 bool "Connection tracking events"
88 depends on NETFILTER_ADVANCED
90 If this option is enabled, the connection tracking code will
91 provide a notifier chain that can be used by other kernel code
92 to get notified about changes in the connection tracking state.
96 config NF_CT_PROTO_DCCP
97 tristate 'DCCP protocol connection tracking support (EXPERIMENTAL)'
98 depends on EXPERIMENTAL
99 depends on NETFILTER_ADVANCED
102 With this option enabled, the layer 3 independent connection
103 tracking code will be able to do state tracking on DCCP connections.
107 config NF_CT_PROTO_GRE
110 config NF_CT_PROTO_SCTP
111 tristate 'SCTP protocol connection tracking support (EXPERIMENTAL)'
112 depends on EXPERIMENTAL
113 depends on NETFILTER_ADVANCED
116 With this option enabled, the layer 3 independent connection
117 tracking code will be able to do state tracking on SCTP connections.
119 If you want to compile it as a module, say M here and read
120 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
122 config NF_CT_PROTO_UDPLITE
123 tristate 'UDP-Lite protocol connection tracking support'
124 depends on NETFILTER_ADVANCED
126 With this option enabled, the layer 3 independent connection
127 tracking code will be able to do state tracking on UDP-Lite
130 To compile it as a module, choose M here. If unsure, say N.
132 config NF_CONNTRACK_AMANDA
133 tristate "Amanda backup protocol support"
134 depends on NETFILTER_ADVANCED
136 select TEXTSEARCH_KMP
138 If you are running the Amanda backup package <http://www.amanda.org/>
139 on this machine or machines that will be MASQUERADED through this
140 machine, then you may want to enable this feature. This allows the
141 connection tracking and natting code to allow the sub-channels that
142 Amanda requires for communication of the backup data, messages and
145 To compile it as a module, choose M here. If unsure, say N.
147 config NF_CONNTRACK_FTP
148 tristate "FTP protocol support"
149 default m if NETFILTER_ADVANCED=n
151 Tracking FTP connections is problematic: special helpers are
152 required for tracking them, and doing masquerading and other forms
153 of Network Address Translation on them.
155 This is FTP support on Layer 3 independent connection tracking.
156 Layer 3 independent connection tracking is experimental scheme
157 which generalize ip_conntrack to support other layer 3 protocols.
159 To compile it as a module, choose M here. If unsure, say N.
161 config NF_CONNTRACK_H323
162 tristate "H.323 protocol support"
163 depends on (IPV6 || IPV6=n)
164 depends on NETFILTER_ADVANCED
166 H.323 is a VoIP signalling protocol from ITU-T. As one of the most
167 important VoIP protocols, it is widely used by voice hardware and
168 software including voice gateways, IP phones, Netmeeting, OpenPhone,
171 With this module you can support H.323 on a connection tracking/NAT
174 This module supports RAS, Fast Start, H.245 Tunnelling, Call
175 Forwarding, RTP/RTCP and T.120 based audio, video, fax, chat,
176 whiteboard, file transfer, etc. For more information, please
177 visit http://nath323.sourceforge.net/.
179 To compile it as a module, choose M here. If unsure, say N.
181 config NF_CONNTRACK_IRC
182 tristate "IRC protocol support"
183 default m if NETFILTER_ADVANCED=n
185 There is a commonly-used extension to IRC called
186 Direct Client-to-Client Protocol (DCC). This enables users to send
187 files to each other, and also chat to each other without the need
188 of a server. DCC Sending is used anywhere you send files over IRC,
189 and DCC Chat is most commonly used by Eggdrop bots. If you are
190 using NAT, this extension will enable you to send files and initiate
191 chats. Note that you do NOT need this extension to get files or
192 have others initiate chats, or everything else in IRC.
194 To compile it as a module, choose M here. If unsure, say N.
196 config NF_CONNTRACK_NETBIOS_NS
197 tristate "NetBIOS name service protocol support"
198 depends on NETFILTER_ADVANCED
200 NetBIOS name service requests are sent as broadcast messages from an
201 unprivileged port and responded to with unicast messages to the
202 same port. This make them hard to firewall properly because connection
203 tracking doesn't deal with broadcasts. This helper tracks locally
204 originating NetBIOS name service requests and the corresponding
205 responses. It relies on correct IP address configuration, specifically
206 netmask and broadcast address. When properly configured, the output
207 of "ip address show" should look similar to this:
209 $ ip -4 address show eth0
210 4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
211 inet 172.16.2.252/24 brd 172.16.2.255 scope global eth0
213 To compile it as a module, choose M here. If unsure, say N.
215 config NF_CONNTRACK_PPTP
216 tristate "PPtP protocol support"
217 depends on NETFILTER_ADVANCED
218 select NF_CT_PROTO_GRE
220 This module adds support for PPTP (Point to Point Tunnelling
221 Protocol, RFC2637) connection tracking and NAT.
223 If you are running PPTP sessions over a stateful firewall or NAT
224 box, you may want to enable this feature.
226 Please note that not all PPTP modes of operation are supported yet.
227 Specifically these limitations exist:
228 - Blindly assumes that control connections are always established
229 in PNS->PAC direction. This is a violation of RFC2637.
230 - Only supports a single call within each session
232 To compile it as a module, choose M here. If unsure, say N.
234 config NF_CONNTRACK_SANE
235 tristate "SANE protocol support (EXPERIMENTAL)"
236 depends on EXPERIMENTAL
237 depends on NETFILTER_ADVANCED
239 SANE is a protocol for remote access to scanners as implemented
240 by the 'saned' daemon. Like FTP, it uses separate control and
243 With this module you can support SANE on a connection tracking
246 To compile it as a module, choose M here. If unsure, say N.
248 config NF_CONNTRACK_SIP
249 tristate "SIP protocol support"
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 NETFILTER_ADVANCED
264 TFTP connection tracking helper, this is required depending
265 on how restrictive your ruleset is.
266 If you are using a tftp client behind -j SNAT or -j MASQUERADING
269 To compile it as a module, choose M here. If unsure, say N.
272 tristate 'Connection tracking netlink interface'
273 select NETFILTER_NETLINK
274 default m if NETFILTER_ADVANCED=n
276 This option enables support for a netlink-based userspace interface
280 # transparent proxy support
281 config NETFILTER_TPROXY
282 tristate "Transparent proxying support (EXPERIMENTAL)"
283 depends on EXPERIMENTAL
284 depends on IP_NF_MANGLE
285 depends on NETFILTER_ADVANCED
287 This option enables transparent proxying support, that is,
288 support for handling non-locally bound IPv4 TCP and UDP sockets.
289 For it to work you will have to configure certain iptables rules
290 and use policy routing. For more information on how to set it up
291 see Documentation/networking/tproxy.txt.
293 To compile it as a module, choose M here. If unsure, say N.
295 config NETFILTER_XTABLES
296 tristate "Netfilter Xtables support (required for ip_tables)"
297 default m if NETFILTER_ADVANCED=n
299 This is required if you intend to use any of ip_tables,
300 ip6_tables or arp_tables.
304 # alphabetically ordered list of targets
306 config NETFILTER_XT_TARGET_CLASSIFY
307 tristate '"CLASSIFY" target support'
308 depends on NETFILTER_ADVANCED
310 This option adds a `CLASSIFY' target, which enables the user to set
311 the priority of a packet. Some qdiscs can use this value for
312 classification, among these are:
314 atm, cbq, dsmark, pfifo_fast, htb, prio
316 To compile it as a module, choose M here. If unsure, say N.
318 config NETFILTER_XT_TARGET_CONNMARK
319 tristate '"CONNMARK" target support'
320 depends on NF_CONNTRACK
321 depends on NETFILTER_ADVANCED
322 select NF_CONNTRACK_MARK
324 This option adds a `CONNMARK' target, which allows one to manipulate
325 the connection mark value. Similar to the MARK target, but
326 affects the connection mark value rather than the packet mark value.
328 If you want to compile it as a module, say M here and read
329 <file:Documentation/kbuild/modules.txt>. The module will be called
330 ipt_CONNMARK. If unsure, say `N'.
332 config NETFILTER_XT_TARGET_CONNSECMARK
333 tristate '"CONNSECMARK" target support'
334 depends on NF_CONNTRACK && NF_CONNTRACK_SECMARK
335 default m if NETFILTER_ADVANCED=n
337 The CONNSECMARK target copies security markings from packets
338 to connections, and restores security markings from connections
339 to packets (if the packets are not already marked). This would
340 normally be used in conjunction with the SECMARK target.
342 To compile it as a module, choose M here. If unsure, say N.
344 config NETFILTER_XT_TARGET_CT
345 tristate '"CT" target support'
346 depends on NF_CONNTRACK
347 depends on IP_NF_RAW || IP6_NF_RAW
348 depends on NETFILTER_ADVANCED
350 This options adds a `CT' target, which allows to specify initial
351 connection tracking parameters like events to be delivered and
352 the helper to be used.
354 To compile it as a module, choose M here. If unsure, say N.
356 config NETFILTER_XT_TARGET_DSCP
357 tristate '"DSCP" and "TOS" target support'
358 depends on IP_NF_MANGLE || IP6_NF_MANGLE
359 depends on NETFILTER_ADVANCED
361 This option adds a `DSCP' target, which allows you to manipulate
362 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
364 The DSCP field can have any value between 0x0 and 0x3f inclusive.
366 It also adds the "TOS" target, which allows you to create rules in
367 the "mangle" table which alter the Type Of Service field of an IPv4
368 or the Priority field of an IPv6 packet, prior to routing.
370 To compile it as a module, choose M here. If unsure, say N.
372 config NETFILTER_XT_TARGET_HL
373 tristate '"HL" hoplimit target support'
374 depends on IP_NF_MANGLE || IP6_NF_MANGLE
375 depends on NETFILTER_ADVANCED
377 This option adds the "HL" (for IPv6) and "TTL" (for IPv4)
378 targets, which enable the user to change the
379 hoplimit/time-to-live value of the IP header.
381 While it is safe to decrement the hoplimit/TTL value, the
382 modules also allow to increment and set the hoplimit value of
383 the header to arbitrary values. This is EXTREMELY DANGEROUS
384 since you can easily create immortal packets that loop
385 forever on the network.
387 config NETFILTER_XT_TARGET_LED
388 tristate '"LED" target support'
389 depends on LEDS_CLASS && LEDS_TRIGGERS
390 depends on NETFILTER_ADVANCED
392 This option adds a `LED' target, which allows you to blink LEDs in
393 response to particular packets passing through your machine.
395 This can be used to turn a spare LED into a network activity LED,
396 which only flashes in response to FTP transfers, for example. Or
397 you could have an LED which lights up for a minute or two every time
398 somebody connects to your machine via SSH.
400 You will need support for the "led" class to make this work.
402 To create an LED trigger for incoming SSH traffic:
403 iptables -A INPUT -p tcp --dport 22 -j LED --led-trigger-id ssh --led-delay 1000
405 Then attach the new trigger to an LED on your system:
406 echo netfilter-ssh > /sys/class/leds/<ledname>/trigger
408 For more information on the LEDs available on your system, see
409 Documentation/leds-class.txt
411 config NETFILTER_XT_TARGET_MARK
412 tristate '"MARK" target support'
413 default m if NETFILTER_ADVANCED=n
415 This option adds a `MARK' target, which allows you to create rules
416 in the `mangle' table which alter the netfilter mark (nfmark) field
417 associated with the packet prior to routing. This can change
418 the routing method (see `Use netfilter MARK value as routing
419 key') and can also be used by other subsystems to change their
422 To compile it as a module, choose M here. If unsure, say N.
424 config NETFILTER_XT_TARGET_NFLOG
425 tristate '"NFLOG" target support'
426 default m if NETFILTER_ADVANCED=n
427 select NETFILTER_NETLINK_LOG
429 This option enables the NFLOG target, which allows to LOG
430 messages through nfnetlink_log.
432 To compile it as a module, choose M here. If unsure, say N.
434 config NETFILTER_XT_TARGET_NFQUEUE
435 tristate '"NFQUEUE" target Support'
436 depends on NETFILTER_ADVANCED
438 This target replaced the old obsolete QUEUE target.
440 As opposed to QUEUE, it supports 65535 different queues,
443 To compile it as a module, choose M here. If unsure, say N.
445 config NETFILTER_XT_TARGET_NOTRACK
446 tristate '"NOTRACK" target support'
447 depends on IP_NF_RAW || IP6_NF_RAW
448 depends on NF_CONNTRACK
449 depends on NETFILTER_ADVANCED
451 The NOTRACK target allows a select rule to specify
452 which packets *not* to enter the conntrack/NAT
453 subsystem with all the consequences (no ICMP error tracking,
454 no protocol helpers for the selected packets).
456 If you want to compile it as a module, say M here and read
457 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
459 config NETFILTER_XT_TARGET_RATEEST
460 tristate '"RATEEST" target support'
461 depends on NETFILTER_ADVANCED
463 This option adds a `RATEEST' target, which allows to measure
464 rates similar to TC estimators. The `rateest' match can be
465 used to match on the measured rates.
467 To compile it as a module, choose M here. If unsure, say N.
469 config NETFILTER_XT_TARGET_TPROXY
470 tristate '"TPROXY" target support (EXPERIMENTAL)'
471 depends on EXPERIMENTAL
472 depends on NETFILTER_TPROXY
473 depends on NETFILTER_XTABLES
474 depends on NETFILTER_ADVANCED
475 select NF_DEFRAG_IPV4
477 This option adds a `TPROXY' target, which is somewhat similar to
478 REDIRECT. It can only be used in the mangle table and is useful
479 to redirect traffic to a transparent proxy. It does _not_ depend
480 on Netfilter connection tracking and NAT, unlike REDIRECT.
482 To compile it as a module, choose M here. If unsure, say N.
484 config NETFILTER_XT_TARGET_TRACE
485 tristate '"TRACE" target support'
486 depends on IP_NF_RAW || IP6_NF_RAW
487 depends on NETFILTER_ADVANCED
489 The TRACE target allows you to mark packets so that the kernel
490 will log every rule which match the packets as those traverse
491 the tables, chains, rules.
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_TARGET_SECMARK
497 tristate '"SECMARK" target support'
498 depends on NETWORK_SECMARK
499 default m if NETFILTER_ADVANCED=n
501 The SECMARK target allows security marking of network
502 packets, for use with security subsystems.
504 To compile it as a module, choose M here. If unsure, say N.
506 config NETFILTER_XT_TARGET_TCPMSS
507 tristate '"TCPMSS" target support'
508 depends on (IPV6 || IPV6=n)
509 default m if NETFILTER_ADVANCED=n
511 This option adds a `TCPMSS' target, which allows you to alter the
512 MSS value of TCP SYN packets, to control the maximum size for that
513 connection (usually limiting it to your outgoing interface's MTU
516 This is used to overcome criminally braindead ISPs or servers which
517 block ICMP Fragmentation Needed packets. The symptoms of this
518 problem are that everything works fine from your Linux
519 firewall/router, but machines behind it can never exchange large
521 1) Web browsers connect, then hang with no data received.
522 2) Small mail works fine, but large emails hang.
523 3) ssh works fine, but scp hangs after initial handshaking.
525 Workaround: activate this option and add a rule to your firewall
528 iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
529 -j TCPMSS --clamp-mss-to-pmtu
531 To compile it as a module, choose M here. If unsure, say N.
533 config NETFILTER_XT_TARGET_TCPOPTSTRIP
534 tristate '"TCPOPTSTRIP" target support (EXPERIMENTAL)'
535 depends on EXPERIMENTAL
536 depends on IP_NF_MANGLE || IP6_NF_MANGLE
537 depends on NETFILTER_ADVANCED
539 This option adds a "TCPOPTSTRIP" target, which allows you to strip
540 TCP options from TCP packets.
542 config NETFILTER_XT_MATCH_CLUSTER
543 tristate '"cluster" match support'
544 depends on NF_CONNTRACK
545 depends on NETFILTER_ADVANCED
547 This option allows you to build work-load-sharing clusters of
548 network servers/stateful firewalls without having a dedicated
549 load-balancing router/server/switch. Basically, this match returns
550 true when the packet must be handled by this cluster node. Thus,
551 all nodes see all packets and this match decides which node handles
552 what packets. The work-load sharing algorithm is based on source
555 If you say Y or M here, try `iptables -m cluster --help` for
558 config NETFILTER_XT_MATCH_COMMENT
559 tristate '"comment" match support'
560 depends on NETFILTER_ADVANCED
562 This option adds a `comment' dummy-match, which allows you to put
563 comments in your iptables ruleset.
565 If you want to compile it as a module, say M here and read
566 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
568 config NETFILTER_XT_MATCH_CONNBYTES
569 tristate '"connbytes" per-connection counter match support'
570 depends on NF_CONNTRACK
571 depends on NETFILTER_ADVANCED
574 This option adds a `connbytes' match, which allows you to match the
575 number of bytes and/or packets for each direction within a connection.
577 If you want to compile it as a module, say M here and read
578 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
580 config NETFILTER_XT_MATCH_CONNLIMIT
581 tristate '"connlimit" match support"'
582 depends on NF_CONNTRACK
583 depends on NETFILTER_ADVANCED
585 This match allows you to match against the number of parallel
586 connections to a server per client IP address (or address block).
588 config NETFILTER_XT_MATCH_CONNMARK
589 tristate '"connmark" connection mark match support'
590 depends on NF_CONNTRACK
591 depends on NETFILTER_ADVANCED
592 select NF_CONNTRACK_MARK
594 This option adds a `connmark' match, which allows you to match the
595 connection mark value previously set for the session by `CONNMARK'.
597 If you want to compile it as a module, say M here and read
598 <file:Documentation/kbuild/modules.txt>. The module will be called
599 ipt_connmark. If unsure, say `N'.
601 config NETFILTER_XT_MATCH_CONNTRACK
602 tristate '"conntrack" connection tracking match support'
603 depends on NF_CONNTRACK
604 default m if NETFILTER_ADVANCED=n
606 This is a general conntrack match module, a superset of the state match.
608 It allows matching on additional conntrack information, which is
609 useful in complex configurations, such as NAT gateways with multiple
610 internet links or tunnels.
612 To compile it as a module, choose M here. If unsure, say N.
614 config NETFILTER_XT_MATCH_DCCP
615 tristate '"dccp" protocol match support'
616 depends on NETFILTER_ADVANCED
619 With this option enabled, you will be able to use the iptables
620 `dccp' match in order to match on DCCP source/destination ports
623 If you want to compile it as a module, say M here and read
624 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
626 config NETFILTER_XT_MATCH_DSCP
627 tristate '"dscp" and "tos" match support'
628 depends on NETFILTER_ADVANCED
630 This option adds a `DSCP' match, which allows you to match against
631 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
633 The DSCP field can have any value between 0x0 and 0x3f inclusive.
635 It will also add a "tos" match, which allows you to match packets
636 based on the Type Of Service fields of the IPv4 packet (which share
637 the same bits as DSCP).
639 To compile it as a module, choose M here. If unsure, say N.
641 config NETFILTER_XT_MATCH_ESP
642 tristate '"esp" match support'
643 depends on NETFILTER_ADVANCED
645 This match extension allows you to match a range of SPIs
646 inside ESP header of IPSec packets.
648 To compile it as a module, choose M here. If unsure, say N.
650 config NETFILTER_XT_MATCH_HASHLIMIT
651 tristate '"hashlimit" match support'
652 depends on (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
653 depends on NETFILTER_ADVANCED
655 This option adds a `hashlimit' match.
657 As opposed to `limit', this match dynamically creates a hash table
658 of limit buckets, based on your selection of source/destination
659 addresses and/or ports.
661 It enables you to express policies like `10kpps for any given
662 destination address' or `500pps from any given source address'
665 config NETFILTER_XT_MATCH_HELPER
666 tristate '"helper" match support'
667 depends on NF_CONNTRACK
668 depends on NETFILTER_ADVANCED
670 Helper matching allows you to match packets in dynamic connections
671 tracked by a conntrack-helper, ie. ip_conntrack_ftp
673 To compile it as a module, choose M here. If unsure, say Y.
675 config NETFILTER_XT_MATCH_HL
676 tristate '"hl" hoplimit/TTL match support'
677 depends on NETFILTER_ADVANCED
679 HL matching allows you to match packets based on the hoplimit
680 in the IPv6 header, or the time-to-live field in the IPv4
681 header of the packet.
683 config NETFILTER_XT_MATCH_IPRANGE
684 tristate '"iprange" address range match support'
685 depends on NETFILTER_ADVANCED
687 This option adds a "iprange" match, which allows you to match based on
688 an IP address range. (Normal iptables only matches on single addresses
689 with an optional mask.)
693 config NETFILTER_XT_MATCH_LENGTH
694 tristate '"length" match support'
695 depends on NETFILTER_ADVANCED
697 This option allows you to match the length of a packet against a
698 specific value or range of values.
700 To compile it as a module, choose M here. If unsure, say N.
702 config NETFILTER_XT_MATCH_LIMIT
703 tristate '"limit" match support'
704 depends on NETFILTER_ADVANCED
706 limit matching allows you to control the rate at which a rule can be
707 matched: mainly useful in combination with the LOG target ("LOG
708 target support", below) and to avoid some Denial of Service attacks.
710 To compile it as a module, choose M here. If unsure, say N.
712 config NETFILTER_XT_MATCH_MAC
713 tristate '"mac" address match support'
714 depends on NETFILTER_ADVANCED
716 MAC matching allows you to match packets based on the source
717 Ethernet address of the packet.
719 To compile it as a module, choose M here. If unsure, say N.
721 config NETFILTER_XT_MATCH_MARK
722 tristate '"mark" match support'
723 default m if NETFILTER_ADVANCED=n
725 Netfilter mark matching allows you to match packets based on the
726 `nfmark' value in the packet. This can be set by the MARK target
729 To compile it as a module, choose M here. If unsure, say N.
731 config NETFILTER_XT_MATCH_MULTIPORT
732 tristate '"multiport" Multiple port match support'
733 depends on NETFILTER_ADVANCED
735 Multiport matching allows you to match TCP or UDP packets based on
736 a series of source or destination ports: normally a rule can only
737 match a single range of ports.
739 To compile it as a module, choose M here. If unsure, say N.
741 config NETFILTER_XT_MATCH_OWNER
742 tristate '"owner" match support'
743 depends on NETFILTER_ADVANCED
745 Socket owner matching allows you to match locally-generated packets
746 based on who created the socket: the user or group. It is also
747 possible to check whether a socket actually exists.
749 config NETFILTER_XT_MATCH_POLICY
750 tristate 'IPsec "policy" match support'
752 default m if NETFILTER_ADVANCED=n
754 Policy matching allows you to match packets based on the
755 IPsec policy that was used during decapsulation/will
756 be used during encapsulation.
758 To compile it as a module, choose M here. If unsure, say N.
760 config NETFILTER_XT_MATCH_PHYSDEV
761 tristate '"physdev" match support'
762 depends on BRIDGE && BRIDGE_NETFILTER
763 depends on NETFILTER_ADVANCED
765 Physdev packet matching matches against the physical bridge ports
766 the IP packet arrived on or will leave by.
768 To compile it as a module, choose M here. If unsure, say N.
770 config NETFILTER_XT_MATCH_PKTTYPE
771 tristate '"pkttype" packet type match support'
772 depends on NETFILTER_ADVANCED
774 Packet type matching allows you to match a packet by
775 its "class", eg. BROADCAST, MULTICAST, ...
778 iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG
780 To compile it as a module, choose M here. If unsure, say N.
782 config NETFILTER_XT_MATCH_QUOTA
783 tristate '"quota" match support'
784 depends on NETFILTER_ADVANCED
786 This option adds a `quota' match, which allows to match on a
789 If you want to compile it as a module, say M here and read
790 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
792 config NETFILTER_XT_MATCH_RATEEST
793 tristate '"rateest" match support'
794 depends on NETFILTER_ADVANCED
795 select NETFILTER_XT_TARGET_RATEEST
797 This option adds a `rateest' match, which allows to match on the
798 rate estimated by the RATEEST target.
800 To compile it as a module, choose M here. If unsure, say N.
802 config NETFILTER_XT_MATCH_REALM
803 tristate '"realm" match support'
804 depends on NETFILTER_ADVANCED
807 This option adds a `realm' match, which allows you to use the realm
808 key from the routing subsystem inside iptables.
810 This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option
813 If you want to compile it as a module, say M here and read
814 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
816 config NETFILTER_XT_MATCH_RECENT
817 tristate '"recent" match support'
818 depends on NETFILTER_ADVANCED
820 This match is used for creating one or many lists of recently
821 used addresses and then matching against that/those list(s).
823 Short options are available by using 'iptables -m recent -h'
824 Official Website: <http://snowman.net/projects/ipt_recent/>
826 config NETFILTER_XT_MATCH_RECENT_PROC_COMPAT
827 bool 'Enable obsolete /proc/net/ipt_recent'
828 depends on NETFILTER_XT_MATCH_RECENT && PROC_FS
830 This option enables the old /proc/net/ipt_recent interface,
831 which has been obsoleted by /proc/net/xt_recent.
833 config NETFILTER_XT_MATCH_SCTP
834 tristate '"sctp" protocol match support (EXPERIMENTAL)'
835 depends on EXPERIMENTAL
836 depends on NETFILTER_ADVANCED
839 With this option enabled, you will be able to use the
840 `sctp' match in order to match on SCTP source/destination ports
841 and SCTP chunk types.
843 If you want to compile it as a module, say M here and read
844 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
846 config NETFILTER_XT_MATCH_SOCKET
847 tristate '"socket" match support (EXPERIMENTAL)'
848 depends on EXPERIMENTAL
849 depends on NETFILTER_TPROXY
850 depends on NETFILTER_XTABLES
851 depends on NETFILTER_ADVANCED
852 depends on !NF_CONNTRACK || NF_CONNTRACK
853 select NF_DEFRAG_IPV4
855 This option adds a `socket' match, which can be used to match
856 packets for which a TCP or UDP socket lookup finds a valid socket.
857 It can be used in combination with the MARK target and policy
858 routing to implement full featured non-locally bound sockets.
860 To compile it as a module, choose M here. If unsure, say N.
862 config NETFILTER_XT_MATCH_STATE
863 tristate '"state" match support'
864 depends on NF_CONNTRACK
865 default m if NETFILTER_ADVANCED=n
867 Connection state matching allows you to match packets based on their
868 relationship to a tracked connection (ie. previous packets). This
869 is a powerful tool for packet classification.
871 To compile it as a module, choose M here. If unsure, say N.
873 config NETFILTER_XT_MATCH_STATISTIC
874 tristate '"statistic" match support'
875 depends on NETFILTER_ADVANCED
877 This option adds a `statistic' match, which allows you to match
878 on packets periodically or randomly with a given percentage.
880 To compile it as a module, choose M here. If unsure, say N.
882 config NETFILTER_XT_MATCH_STRING
883 tristate '"string" match support'
884 depends on NETFILTER_ADVANCED
886 select TEXTSEARCH_KMP
888 select TEXTSEARCH_FSM
890 This option adds a `string' match, which allows you to look for
891 pattern matchings in packets.
893 To compile it as a module, choose M here. If unsure, say N.
895 config NETFILTER_XT_MATCH_TCPMSS
896 tristate '"tcpmss" match support'
897 depends on NETFILTER_ADVANCED
899 This option adds a `tcpmss' match, which allows you to examine the
900 MSS value of TCP SYN packets, which control the maximum packet size
903 To compile it as a module, choose M here. If unsure, say N.
905 config NETFILTER_XT_MATCH_TIME
906 tristate '"time" match support'
907 depends on NETFILTER_ADVANCED
909 This option adds a "time" match, which allows you to match based on
910 the packet arrival time (at the machine which netfilter is running)
911 on) or departure time/date (for locally generated packets).
913 If you say Y here, try `iptables -m time --help` for
916 If you want to compile it as a module, say M here.
919 config NETFILTER_XT_MATCH_U32
920 tristate '"u32" match support'
921 depends on NETFILTER_ADVANCED
923 u32 allows you to extract quantities of up to 4 bytes from a packet,
924 AND them with specified masks, shift them by specified amounts and
925 test whether the results are in any of a set of specified ranges.
926 The specification of what to extract is general enough to skip over
927 headers with lengths stored in the packet, as in IP or TCP header
930 Details and examples are in the kernel module source.
932 config NETFILTER_XT_MATCH_OSF
933 tristate '"osf" Passive OS fingerprint match'
934 depends on NETFILTER_ADVANCED && NETFILTER_NETLINK
936 This option selects the Passive OS Fingerprinting match module
937 that allows to passively match the remote operating system by
938 analyzing incoming TCP SYN packets.
940 Rules and loading software can be downloaded from
941 http://www.ioremap.net/projects/osf
943 To compile it as a module, choose M here. If unsure, say N.
945 endif # NETFILTER_XTABLES
949 source "net/netfilter/ipvs/Kconfig"