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_ZONES
87 bool 'Connection tracking zones'
88 depends on NETFILTER_ADVANCED
89 depends on NETFILTER_XT_TARGET_CT
91 This option enables support for connection tracking zones.
92 Normally, each connection needs to have a unique system wide
93 identity. Connection tracking zones allow to have multiple
94 connections using the same identity, as long as they are
95 contained in different zones.
99 config NF_CONNTRACK_EVENTS
100 bool "Connection tracking events"
101 depends on NETFILTER_ADVANCED
103 If this option is enabled, the connection tracking code will
104 provide a notifier chain that can be used by other kernel code
105 to get notified about changes in the connection tracking state.
109 config NF_CT_PROTO_DCCP
110 tristate 'DCCP protocol connection tracking support (EXPERIMENTAL)'
111 depends on EXPERIMENTAL
112 depends on NETFILTER_ADVANCED
115 With this option enabled, the layer 3 independent connection
116 tracking code will be able to do state tracking on DCCP connections.
120 config NF_CT_PROTO_GRE
123 config NF_CT_PROTO_SCTP
124 tristate 'SCTP protocol connection tracking support (EXPERIMENTAL)'
125 depends on EXPERIMENTAL
126 depends on NETFILTER_ADVANCED
129 With this option enabled, the layer 3 independent connection
130 tracking code will be able to do state tracking on SCTP connections.
132 If you want to compile it as a module, say M here and read
133 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
135 config NF_CT_PROTO_UDPLITE
136 tristate 'UDP-Lite protocol connection tracking support'
137 depends on NETFILTER_ADVANCED
139 With this option enabled, the layer 3 independent connection
140 tracking code will be able to do state tracking on UDP-Lite
143 To compile it as a module, choose M here. If unsure, say N.
145 config NF_CONNTRACK_AMANDA
146 tristate "Amanda backup protocol support"
147 depends on NETFILTER_ADVANCED
149 select TEXTSEARCH_KMP
151 If you are running the Amanda backup package <http://www.amanda.org/>
152 on this machine or machines that will be MASQUERADED through this
153 machine, then you may want to enable this feature. This allows the
154 connection tracking and natting code to allow the sub-channels that
155 Amanda requires for communication of the backup data, messages and
158 To compile it as a module, choose M here. If unsure, say N.
160 config NF_CONNTRACK_FTP
161 tristate "FTP protocol support"
162 default m if NETFILTER_ADVANCED=n
164 Tracking FTP connections is problematic: special helpers are
165 required for tracking them, and doing masquerading and other forms
166 of Network Address Translation on them.
168 This is FTP support on Layer 3 independent connection tracking.
169 Layer 3 independent connection tracking is experimental scheme
170 which generalize ip_conntrack to support other layer 3 protocols.
172 To compile it as a module, choose M here. If unsure, say N.
174 config NF_CONNTRACK_H323
175 tristate "H.323 protocol support"
176 depends on (IPV6 || IPV6=n)
177 depends on NETFILTER_ADVANCED
179 H.323 is a VoIP signalling protocol from ITU-T. As one of the most
180 important VoIP protocols, it is widely used by voice hardware and
181 software including voice gateways, IP phones, Netmeeting, OpenPhone,
184 With this module you can support H.323 on a connection tracking/NAT
187 This module supports RAS, Fast Start, H.245 Tunnelling, Call
188 Forwarding, RTP/RTCP and T.120 based audio, video, fax, chat,
189 whiteboard, file transfer, etc. For more information, please
190 visit http://nath323.sourceforge.net/.
192 To compile it as a module, choose M here. If unsure, say N.
194 config NF_CONNTRACK_IRC
195 tristate "IRC protocol support"
196 default m if NETFILTER_ADVANCED=n
198 There is a commonly-used extension to IRC called
199 Direct Client-to-Client Protocol (DCC). This enables users to send
200 files to each other, and also chat to each other without the need
201 of a server. DCC Sending is used anywhere you send files over IRC,
202 and DCC Chat is most commonly used by Eggdrop bots. If you are
203 using NAT, this extension will enable you to send files and initiate
204 chats. Note that you do NOT need this extension to get files or
205 have others initiate chats, or everything else in IRC.
207 To compile it as a module, choose M here. If unsure, say N.
209 config NF_CONNTRACK_NETBIOS_NS
210 tristate "NetBIOS name service protocol support"
211 depends on NETFILTER_ADVANCED
213 NetBIOS name service requests are sent as broadcast messages from an
214 unprivileged port and responded to with unicast messages to the
215 same port. This make them hard to firewall properly because connection
216 tracking doesn't deal with broadcasts. This helper tracks locally
217 originating NetBIOS name service requests and the corresponding
218 responses. It relies on correct IP address configuration, specifically
219 netmask and broadcast address. When properly configured, the output
220 of "ip address show" should look similar to this:
222 $ ip -4 address show eth0
223 4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
224 inet 172.16.2.252/24 brd 172.16.2.255 scope global eth0
226 To compile it as a module, choose M here. If unsure, say N.
228 config NF_CONNTRACK_PPTP
229 tristate "PPtP protocol support"
230 depends on NETFILTER_ADVANCED
231 select NF_CT_PROTO_GRE
233 This module adds support for PPTP (Point to Point Tunnelling
234 Protocol, RFC2637) connection tracking and NAT.
236 If you are running PPTP sessions over a stateful firewall or NAT
237 box, you may want to enable this feature.
239 Please note that not all PPTP modes of operation are supported yet.
240 Specifically these limitations exist:
241 - Blindly assumes that control connections are always established
242 in PNS->PAC direction. This is a violation of RFC2637.
243 - Only supports a single call within each session
245 To compile it as a module, choose M here. If unsure, say N.
247 config NF_CONNTRACK_SANE
248 tristate "SANE protocol support (EXPERIMENTAL)"
249 depends on EXPERIMENTAL
250 depends on NETFILTER_ADVANCED
252 SANE is a protocol for remote access to scanners as implemented
253 by the 'saned' daemon. Like FTP, it uses separate control and
256 With this module you can support SANE on a connection tracking
259 To compile it as a module, choose M here. If unsure, say N.
261 config NF_CONNTRACK_SIP
262 tristate "SIP protocol support"
263 default m if NETFILTER_ADVANCED=n
265 SIP is an application-layer control protocol that can establish,
266 modify, and terminate multimedia sessions (conferences) such as
267 Internet telephony calls. With the ip_conntrack_sip and
268 the nf_nat_sip modules you can support the protocol on a connection
269 tracking/NATing firewall.
271 To compile it as a module, choose M here. If unsure, say N.
273 config NF_CONNTRACK_TFTP
274 tristate "TFTP protocol support"
275 depends on NETFILTER_ADVANCED
277 TFTP connection tracking helper, this is required depending
278 on how restrictive your ruleset is.
279 If you are using a tftp client behind -j SNAT or -j MASQUERADING
282 To compile it as a module, choose M here. If unsure, say N.
285 tristate 'Connection tracking netlink interface'
286 select NETFILTER_NETLINK
287 default m if NETFILTER_ADVANCED=n
289 This option enables support for a netlink-based userspace interface
293 # transparent proxy support
294 config NETFILTER_TPROXY
295 tristate "Transparent proxying support (EXPERIMENTAL)"
296 depends on EXPERIMENTAL
297 depends on IP_NF_MANGLE
298 depends on NETFILTER_ADVANCED
300 This option enables transparent proxying support, that is,
301 support for handling non-locally bound IPv4 TCP and UDP sockets.
302 For it to work you will have to configure certain iptables rules
303 and use policy routing. For more information on how to set it up
304 see Documentation/networking/tproxy.txt.
306 To compile it as a module, choose M here. If unsure, say N.
308 config NETFILTER_XTABLES
309 tristate "Netfilter Xtables support (required for ip_tables)"
310 default m if NETFILTER_ADVANCED=n
312 This is required if you intend to use any of ip_tables,
313 ip6_tables or arp_tables.
317 comment "Xtables combined modules"
319 config NETFILTER_XT_MARK
320 tristate 'nfmark target and match support'
321 default m if NETFILTER_ADVANCED=n
323 This option adds the "MARK" target and "mark" match.
325 Netfilter mark matching allows you to match packets based on the
326 "nfmark" value in the packet.
327 The target allows you to create rules in the "mangle" table which alter
328 the netfilter mark (nfmark) field associated with the packet.
330 Prior to routing, the nfmark can influence the routing method (see
331 "Use netfilter MARK value as routing key") and can also be used by
332 other subsystems to change their behavior.
334 config NETFILTER_XT_CONNMARK
335 tristate 'ctmark target and match support'
336 depends on NF_CONNTRACK
337 depends on NETFILTER_ADVANCED
338 select NF_CONNTRACK_MARK
340 This option adds the "CONNMARK" target and "connmark" match.
342 Netfilter allows you to store a mark value per connection (a.k.a.
343 ctmark), similarly to the packet mark (nfmark). Using this
344 target and match, you can set and match on this mark.
346 # alphabetically ordered list of targets
348 comment "Xtables targets"
350 config NETFILTER_XT_TARGET_CLASSIFY
351 tristate '"CLASSIFY" target support'
352 depends on NETFILTER_ADVANCED
354 This option adds a `CLASSIFY' target, which enables the user to set
355 the priority of a packet. Some qdiscs can use this value for
356 classification, among these are:
358 atm, cbq, dsmark, pfifo_fast, htb, prio
360 To compile it as a module, choose M here. If unsure, say N.
362 config NETFILTER_XT_TARGET_CONNMARK
363 tristate '"CONNMARK" target support'
364 depends on NF_CONNTRACK
365 depends on NETFILTER_ADVANCED
366 select NETFILTER_XT_CONNMARK
368 This is a backwards-compat option for the user's convenience
369 (e.g. when running oldconfig). It selects
370 CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
372 config NETFILTER_XT_TARGET_CONNSECMARK
373 tristate '"CONNSECMARK" target support'
374 depends on NF_CONNTRACK && NF_CONNTRACK_SECMARK
375 default m if NETFILTER_ADVANCED=n
377 The CONNSECMARK target copies security markings from packets
378 to connections, and restores security markings from connections
379 to packets (if the packets are not already marked). This would
380 normally be used in conjunction with the SECMARK target.
382 To compile it as a module, choose M here. If unsure, say N.
384 config NETFILTER_XT_TARGET_CT
385 tristate '"CT" target support'
386 depends on NF_CONNTRACK
387 depends on IP_NF_RAW || IP6_NF_RAW
388 depends on NETFILTER_ADVANCED
390 This options adds a `CT' target, which allows to specify initial
391 connection tracking parameters like events to be delivered and
392 the helper to be used.
394 To compile it as a module, choose M here. If unsure, say N.
396 config NETFILTER_XT_TARGET_DSCP
397 tristate '"DSCP" and "TOS" target support'
398 depends on IP_NF_MANGLE || IP6_NF_MANGLE
399 depends on NETFILTER_ADVANCED
401 This option adds a `DSCP' target, which allows you to manipulate
402 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
404 The DSCP field can have any value between 0x0 and 0x3f inclusive.
406 It also adds the "TOS" target, which allows you to create rules in
407 the "mangle" table which alter the Type Of Service field of an IPv4
408 or the Priority field of an IPv6 packet, prior to routing.
410 To compile it as a module, choose M here. If unsure, say N.
412 config NETFILTER_XT_TARGET_HL
413 tristate '"HL" hoplimit target support'
414 depends on IP_NF_MANGLE || IP6_NF_MANGLE
415 depends on NETFILTER_ADVANCED
417 This option adds the "HL" (for IPv6) and "TTL" (for IPv4)
418 targets, which enable the user to change the
419 hoplimit/time-to-live value of the IP header.
421 While it is safe to decrement the hoplimit/TTL value, the
422 modules also allow to increment and set the hoplimit value of
423 the header to arbitrary values. This is EXTREMELY DANGEROUS
424 since you can easily create immortal packets that loop
425 forever on the network.
427 config NETFILTER_XT_TARGET_LED
428 tristate '"LED" target support'
429 depends on LEDS_CLASS && LEDS_TRIGGERS
430 depends on NETFILTER_ADVANCED
432 This option adds a `LED' target, which allows you to blink LEDs in
433 response to particular packets passing through your machine.
435 This can be used to turn a spare LED into a network activity LED,
436 which only flashes in response to FTP transfers, for example. Or
437 you could have an LED which lights up for a minute or two every time
438 somebody connects to your machine via SSH.
440 You will need support for the "led" class to make this work.
442 To create an LED trigger for incoming SSH traffic:
443 iptables -A INPUT -p tcp --dport 22 -j LED --led-trigger-id ssh --led-delay 1000
445 Then attach the new trigger to an LED on your system:
446 echo netfilter-ssh > /sys/class/leds/<ledname>/trigger
448 For more information on the LEDs available on your system, see
449 Documentation/leds-class.txt
451 config NETFILTER_XT_TARGET_MARK
452 tristate '"MARK" target support'
453 depends on NETFILTER_ADVANCED
454 select NETFILTER_XT_MARK
456 This is a backwards-compat option for the user's convenience
457 (e.g. when running oldconfig). It selects
458 CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
460 config NETFILTER_XT_TARGET_NFLOG
461 tristate '"NFLOG" target support'
462 default m if NETFILTER_ADVANCED=n
463 select NETFILTER_NETLINK_LOG
465 This option enables the NFLOG target, which allows to LOG
466 messages through nfnetlink_log.
468 To compile it as a module, choose M here. If unsure, say N.
470 config NETFILTER_XT_TARGET_NFQUEUE
471 tristate '"NFQUEUE" target Support'
472 depends on NETFILTER_ADVANCED
474 This target replaced the old obsolete QUEUE target.
476 As opposed to QUEUE, it supports 65535 different queues,
479 To compile it as a module, choose M here. If unsure, say N.
481 config NETFILTER_XT_TARGET_NOTRACK
482 tristate '"NOTRACK" target support'
483 depends on IP_NF_RAW || IP6_NF_RAW
484 depends on NF_CONNTRACK
485 depends on NETFILTER_ADVANCED
487 The NOTRACK target allows a select rule to specify
488 which packets *not* to enter the conntrack/NAT
489 subsystem with all the consequences (no ICMP error tracking,
490 no protocol helpers for the selected packets).
492 If you want to compile it as a module, say M here and read
493 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
495 config NETFILTER_XT_TARGET_RATEEST
496 tristate '"RATEEST" target support'
497 depends on NETFILTER_ADVANCED
499 This option adds a `RATEEST' target, which allows to measure
500 rates similar to TC estimators. The `rateest' match can be
501 used to match on the measured rates.
503 To compile it as a module, choose M here. If unsure, say N.
505 config NETFILTER_XT_TARGET_TPROXY
506 tristate '"TPROXY" target support (EXPERIMENTAL)'
507 depends on EXPERIMENTAL
508 depends on NETFILTER_TPROXY
509 depends on NETFILTER_XTABLES
510 depends on NETFILTER_ADVANCED
511 select NF_DEFRAG_IPV4
513 This option adds a `TPROXY' target, which is somewhat similar to
514 REDIRECT. It can only be used in the mangle table and is useful
515 to redirect traffic to a transparent proxy. It does _not_ depend
516 on Netfilter connection tracking and NAT, unlike REDIRECT.
518 To compile it as a module, choose M here. If unsure, say N.
520 config NETFILTER_XT_TARGET_TRACE
521 tristate '"TRACE" target support'
522 depends on IP_NF_RAW || IP6_NF_RAW
523 depends on NETFILTER_ADVANCED
525 The TRACE target allows you to mark packets so that the kernel
526 will log every rule which match the packets as those traverse
527 the tables, chains, rules.
529 If you want to compile it as a module, say M here and read
530 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
532 config NETFILTER_XT_TARGET_SECMARK
533 tristate '"SECMARK" target support'
534 depends on NETWORK_SECMARK
535 default m if NETFILTER_ADVANCED=n
537 The SECMARK target allows security marking of network
538 packets, for use with security subsystems.
540 To compile it as a module, choose M here. If unsure, say N.
542 config NETFILTER_XT_TARGET_TCPMSS
543 tristate '"TCPMSS" target support'
544 depends on (IPV6 || IPV6=n)
545 default m if NETFILTER_ADVANCED=n
547 This option adds a `TCPMSS' target, which allows you to alter the
548 MSS value of TCP SYN packets, to control the maximum size for that
549 connection (usually limiting it to your outgoing interface's MTU
552 This is used to overcome criminally braindead ISPs or servers which
553 block ICMP Fragmentation Needed packets. The symptoms of this
554 problem are that everything works fine from your Linux
555 firewall/router, but machines behind it can never exchange large
557 1) Web browsers connect, then hang with no data received.
558 2) Small mail works fine, but large emails hang.
559 3) ssh works fine, but scp hangs after initial handshaking.
561 Workaround: activate this option and add a rule to your firewall
564 iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
565 -j TCPMSS --clamp-mss-to-pmtu
567 To compile it as a module, choose M here. If unsure, say N.
569 config NETFILTER_XT_TARGET_TCPOPTSTRIP
570 tristate '"TCPOPTSTRIP" target support (EXPERIMENTAL)'
571 depends on EXPERIMENTAL
572 depends on IP_NF_MANGLE || IP6_NF_MANGLE
573 depends on NETFILTER_ADVANCED
575 This option adds a "TCPOPTSTRIP" target, which allows you to strip
576 TCP options from TCP packets.
578 # alphabetically ordered list of matches
580 comment "Xtables matches"
582 config NETFILTER_XT_MATCH_CLUSTER
583 tristate '"cluster" match support'
584 depends on NF_CONNTRACK
585 depends on NETFILTER_ADVANCED
587 This option allows you to build work-load-sharing clusters of
588 network servers/stateful firewalls without having a dedicated
589 load-balancing router/server/switch. Basically, this match returns
590 true when the packet must be handled by this cluster node. Thus,
591 all nodes see all packets and this match decides which node handles
592 what packets. The work-load sharing algorithm is based on source
595 If you say Y or M here, try `iptables -m cluster --help` for
598 config NETFILTER_XT_MATCH_COMMENT
599 tristate '"comment" match support'
600 depends on NETFILTER_ADVANCED
602 This option adds a `comment' dummy-match, which allows you to put
603 comments in your iptables ruleset.
605 If you want to compile it as a module, say M here and read
606 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
608 config NETFILTER_XT_MATCH_CONNBYTES
609 tristate '"connbytes" per-connection counter match support'
610 depends on NF_CONNTRACK
611 depends on NETFILTER_ADVANCED
614 This option adds a `connbytes' match, which allows you to match the
615 number of bytes and/or packets for each direction within a connection.
617 If you want to compile it as a module, say M here and read
618 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
620 config NETFILTER_XT_MATCH_CONNLIMIT
621 tristate '"connlimit" match support"'
622 depends on NF_CONNTRACK
623 depends on NETFILTER_ADVANCED
625 This match allows you to match against the number of parallel
626 connections to a server per client IP address (or address block).
628 config NETFILTER_XT_MATCH_CONNMARK
629 tristate '"connmark" connection mark match support'
630 depends on NF_CONNTRACK
631 depends on NETFILTER_ADVANCED
632 select NETFILTER_XT_CONNMARK
634 This is a backwards-compat option for the user's convenience
635 (e.g. when running oldconfig). It selects
636 CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
638 config NETFILTER_XT_MATCH_CONNTRACK
639 tristate '"conntrack" connection tracking match support'
640 depends on NF_CONNTRACK
641 default m if NETFILTER_ADVANCED=n
643 This is a general conntrack match module, a superset of the state match.
645 It allows matching on additional conntrack information, which is
646 useful in complex configurations, such as NAT gateways with multiple
647 internet links or tunnels.
649 To compile it as a module, choose M here. If unsure, say N.
651 config NETFILTER_XT_MATCH_DCCP
652 tristate '"dccp" protocol match support'
653 depends on NETFILTER_ADVANCED
656 With this option enabled, you will be able to use the iptables
657 `dccp' match in order to match on DCCP source/destination ports
660 If you want to compile it as a module, say M here and read
661 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
663 config NETFILTER_XT_MATCH_DSCP
664 tristate '"dscp" and "tos" match support'
665 depends on NETFILTER_ADVANCED
667 This option adds a `DSCP' match, which allows you to match against
668 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
670 The DSCP field can have any value between 0x0 and 0x3f inclusive.
672 It will also add a "tos" match, which allows you to match packets
673 based on the Type Of Service fields of the IPv4 packet (which share
674 the same bits as DSCP).
676 To compile it as a module, choose M here. If unsure, say N.
678 config NETFILTER_XT_MATCH_ESP
679 tristate '"esp" match support'
680 depends on NETFILTER_ADVANCED
682 This match extension allows you to match a range of SPIs
683 inside ESP header of IPSec packets.
685 To compile it as a module, choose M here. If unsure, say N.
687 config NETFILTER_XT_MATCH_HASHLIMIT
688 tristate '"hashlimit" match support'
689 depends on (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
690 depends on NETFILTER_ADVANCED
692 This option adds a `hashlimit' match.
694 As opposed to `limit', this match dynamically creates a hash table
695 of limit buckets, based on your selection of source/destination
696 addresses and/or ports.
698 It enables you to express policies like `10kpps for any given
699 destination address' or `500pps from any given source address'
702 config NETFILTER_XT_MATCH_HELPER
703 tristate '"helper" match support'
704 depends on NF_CONNTRACK
705 depends on NETFILTER_ADVANCED
707 Helper matching allows you to match packets in dynamic connections
708 tracked by a conntrack-helper, ie. ip_conntrack_ftp
710 To compile it as a module, choose M here. If unsure, say Y.
712 config NETFILTER_XT_MATCH_HL
713 tristate '"hl" hoplimit/TTL match support'
714 depends on NETFILTER_ADVANCED
716 HL matching allows you to match packets based on the hoplimit
717 in the IPv6 header, or the time-to-live field in the IPv4
718 header of the packet.
720 config NETFILTER_XT_MATCH_IPRANGE
721 tristate '"iprange" address range match support'
722 depends on NETFILTER_ADVANCED
724 This option adds a "iprange" match, which allows you to match based on
725 an IP address range. (Normal iptables only matches on single addresses
726 with an optional mask.)
730 config NETFILTER_XT_MATCH_LENGTH
731 tristate '"length" match support'
732 depends on NETFILTER_ADVANCED
734 This option allows you to match the length of a packet against a
735 specific value or range of values.
737 To compile it as a module, choose M here. If unsure, say N.
739 config NETFILTER_XT_MATCH_LIMIT
740 tristate '"limit" match support'
741 depends on NETFILTER_ADVANCED
743 limit matching allows you to control the rate at which a rule can be
744 matched: mainly useful in combination with the LOG target ("LOG
745 target support", below) and to avoid some Denial of Service attacks.
747 To compile it as a module, choose M here. If unsure, say N.
749 config NETFILTER_XT_MATCH_MAC
750 tristate '"mac" address match support'
751 depends on NETFILTER_ADVANCED
753 MAC matching allows you to match packets based on the source
754 Ethernet address of the packet.
756 To compile it as a module, choose M here. If unsure, say N.
758 config NETFILTER_XT_MATCH_MARK
759 tristate '"mark" match support'
760 depends on NETFILTER_ADVANCED
761 select NETFILTER_XT_MARK
763 This is a backwards-compat option for the user's convenience
764 (e.g. when running oldconfig). It selects
765 CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
767 config NETFILTER_XT_MATCH_MULTIPORT
768 tristate '"multiport" Multiple port match support'
769 depends on NETFILTER_ADVANCED
771 Multiport matching allows you to match TCP or UDP packets based on
772 a series of source or destination ports: normally a rule can only
773 match a single range of ports.
775 To compile it as a module, choose M here. If unsure, say N.
777 config NETFILTER_XT_MATCH_OWNER
778 tristate '"owner" match support'
779 depends on NETFILTER_ADVANCED
781 Socket owner matching allows you to match locally-generated packets
782 based on who created the socket: the user or group. It is also
783 possible to check whether a socket actually exists.
785 config NETFILTER_XT_MATCH_POLICY
786 tristate 'IPsec "policy" match support'
788 default m if NETFILTER_ADVANCED=n
790 Policy matching allows you to match packets based on the
791 IPsec policy that was used during decapsulation/will
792 be used during encapsulation.
794 To compile it as a module, choose M here. If unsure, say N.
796 config NETFILTER_XT_MATCH_PHYSDEV
797 tristate '"physdev" match support'
798 depends on BRIDGE && BRIDGE_NETFILTER
799 depends on NETFILTER_ADVANCED
801 Physdev packet matching matches against the physical bridge ports
802 the IP packet arrived on or will leave by.
804 To compile it as a module, choose M here. If unsure, say N.
806 config NETFILTER_XT_MATCH_PKTTYPE
807 tristate '"pkttype" packet type match support'
808 depends on NETFILTER_ADVANCED
810 Packet type matching allows you to match a packet by
811 its "class", eg. BROADCAST, MULTICAST, ...
814 iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG
816 To compile it as a module, choose M here. If unsure, say N.
818 config NETFILTER_XT_MATCH_QUOTA
819 tristate '"quota" match support'
820 depends on NETFILTER_ADVANCED
822 This option adds a `quota' match, which allows to match on a
825 If you want to compile it as a module, say M here and read
826 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
828 config NETFILTER_XT_MATCH_RATEEST
829 tristate '"rateest" match support'
830 depends on NETFILTER_ADVANCED
831 select NETFILTER_XT_TARGET_RATEEST
833 This option adds a `rateest' match, which allows to match on the
834 rate estimated by the RATEEST target.
836 To compile it as a module, choose M here. If unsure, say N.
838 config NETFILTER_XT_MATCH_REALM
839 tristate '"realm" match support'
840 depends on NETFILTER_ADVANCED
843 This option adds a `realm' match, which allows you to use the realm
844 key from the routing subsystem inside iptables.
846 This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option
849 If you want to compile it as a module, say M here and read
850 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
852 config NETFILTER_XT_MATCH_RECENT
853 tristate '"recent" match support'
854 depends on NETFILTER_ADVANCED
856 This match is used for creating one or many lists of recently
857 used addresses and then matching against that/those list(s).
859 Short options are available by using 'iptables -m recent -h'
860 Official Website: <http://snowman.net/projects/ipt_recent/>
862 config NETFILTER_XT_MATCH_SCTP
863 tristate '"sctp" protocol match support (EXPERIMENTAL)'
864 depends on EXPERIMENTAL
865 depends on NETFILTER_ADVANCED
868 With this option enabled, you will be able to use the
869 `sctp' match in order to match on SCTP source/destination ports
870 and SCTP chunk types.
872 If you want to compile it as a module, say M here and read
873 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
875 config NETFILTER_XT_MATCH_SOCKET
876 tristate '"socket" match support (EXPERIMENTAL)'
877 depends on EXPERIMENTAL
878 depends on NETFILTER_TPROXY
879 depends on NETFILTER_XTABLES
880 depends on NETFILTER_ADVANCED
881 depends on !NF_CONNTRACK || NF_CONNTRACK
882 select NF_DEFRAG_IPV4
884 This option adds a `socket' match, which can be used to match
885 packets for which a TCP or UDP socket lookup finds a valid socket.
886 It can be used in combination with the MARK target and policy
887 routing to implement full featured non-locally bound sockets.
889 To compile it as a module, choose M here. If unsure, say N.
891 config NETFILTER_XT_MATCH_STATE
892 tristate '"state" match support'
893 depends on NF_CONNTRACK
894 default m if NETFILTER_ADVANCED=n
896 Connection state matching allows you to match packets based on their
897 relationship to a tracked connection (ie. previous packets). This
898 is a powerful tool for packet classification.
900 To compile it as a module, choose M here. If unsure, say N.
902 config NETFILTER_XT_MATCH_STATISTIC
903 tristate '"statistic" match support'
904 depends on NETFILTER_ADVANCED
906 This option adds a `statistic' match, which allows you to match
907 on packets periodically or randomly with a given percentage.
909 To compile it as a module, choose M here. If unsure, say N.
911 config NETFILTER_XT_MATCH_STRING
912 tristate '"string" match support'
913 depends on NETFILTER_ADVANCED
915 select TEXTSEARCH_KMP
917 select TEXTSEARCH_FSM
919 This option adds a `string' match, which allows you to look for
920 pattern matchings in packets.
922 To compile it as a module, choose M here. If unsure, say N.
924 config NETFILTER_XT_MATCH_TCPMSS
925 tristate '"tcpmss" match support'
926 depends on NETFILTER_ADVANCED
928 This option adds a `tcpmss' match, which allows you to examine the
929 MSS value of TCP SYN packets, which control the maximum packet size
932 To compile it as a module, choose M here. If unsure, say N.
934 config NETFILTER_XT_MATCH_TIME
935 tristate '"time" match support'
936 depends on NETFILTER_ADVANCED
938 This option adds a "time" match, which allows you to match based on
939 the packet arrival time (at the machine which netfilter is running)
940 on) or departure time/date (for locally generated packets).
942 If you say Y here, try `iptables -m time --help` for
945 If you want to compile it as a module, say M here.
948 config NETFILTER_XT_MATCH_U32
949 tristate '"u32" match support'
950 depends on NETFILTER_ADVANCED
952 u32 allows you to extract quantities of up to 4 bytes from a packet,
953 AND them with specified masks, shift them by specified amounts and
954 test whether the results are in any of a set of specified ranges.
955 The specification of what to extract is general enough to skip over
956 headers with lengths stored in the packet, as in IP or TCP header
959 Details and examples are in the kernel module source.
961 config NETFILTER_XT_MATCH_OSF
962 tristate '"osf" Passive OS fingerprint match'
963 depends on NETFILTER_ADVANCED && NETFILTER_NETLINK
965 This option selects the Passive OS Fingerprinting match module
966 that allows to passively match the remote operating system by
967 analyzing incoming TCP SYN packets.
969 Rules and loading software can be downloaded from
970 http://www.ioremap.net/projects/osf
972 To compile it as a module, choose M here. If unsure, say N.
974 endif # NETFILTER_XTABLES
978 source "net/netfilter/ipvs/Kconfig"