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.
43 config NF_CONNTRACK_MARK
44 bool 'Connection mark tracking support'
45 depends on NETFILTER_ADVANCED
47 This option enables support for connection marks, used by the
48 `CONNMARK' target and `connmark' match. Similar to the mark value
49 of packets, but this mark value is kept in the conntrack session
50 instead of the individual packets.
52 config NF_CONNTRACK_SECMARK
53 bool 'Connection tracking security mark support'
54 depends on NETWORK_SECMARK
55 default m if NETFILTER_ADVANCED=n
57 This option enables security markings to be applied to
58 connections. Typically they are copied to connections from
59 packets using the CONNSECMARK target and copied back from
60 connections to packets with the same target, with the packets
61 being originally labeled via SECMARK.
65 config NF_CONNTRACK_ZONES
66 bool 'Connection tracking zones'
67 depends on NETFILTER_ADVANCED
68 depends on NETFILTER_XT_TARGET_CT
70 This option enables support for connection tracking zones.
71 Normally, each connection needs to have a unique system wide
72 identity. Connection tracking zones allow to have multiple
73 connections using the same identity, as long as they are
74 contained in different zones.
78 config NF_CONNTRACK_EVENTS
79 bool "Connection tracking events"
80 depends on NETFILTER_ADVANCED
82 If this option is enabled, the connection tracking code will
83 provide a notifier chain that can be used by other kernel code
84 to get notified about changes in the connection tracking state.
88 config NF_CONNTRACK_TIMESTAMP
89 bool 'Connection tracking timestamping'
90 depends on NETFILTER_ADVANCED
92 This option enables support for connection tracking timestamping.
93 This allows you to store the flow start-time and to obtain
94 the flow-stop time (once it has been destroyed) via Connection
99 config NF_CT_PROTO_DCCP
100 tristate 'DCCP protocol connection tracking support (EXPERIMENTAL)'
101 depends on EXPERIMENTAL
102 depends on NETFILTER_ADVANCED
105 With this option enabled, the layer 3 independent connection
106 tracking code will be able to do state tracking on DCCP connections.
110 config NF_CT_PROTO_GRE
113 config NF_CT_PROTO_SCTP
114 tristate 'SCTP protocol connection tracking support (EXPERIMENTAL)'
115 depends on EXPERIMENTAL
116 depends on NETFILTER_ADVANCED
119 With this option enabled, the layer 3 independent connection
120 tracking code will be able to do state tracking on SCTP connections.
122 If you want to compile it as a module, say M here and read
123 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
125 config NF_CT_PROTO_UDPLITE
126 tristate 'UDP-Lite protocol connection tracking support'
127 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 UDP-Lite
133 To compile it as a module, choose M here. If unsure, say N.
135 config NF_CONNTRACK_AMANDA
136 tristate "Amanda backup protocol support"
137 depends on NETFILTER_ADVANCED
139 select TEXTSEARCH_KMP
141 If you are running the Amanda backup package <http://www.amanda.org/>
142 on this machine or machines that will be MASQUERADED through this
143 machine, then you may want to enable this feature. This allows the
144 connection tracking and natting code to allow the sub-channels that
145 Amanda requires for communication of the backup data, messages and
148 To compile it as a module, choose M here. If unsure, say N.
150 config NF_CONNTRACK_FTP
151 tristate "FTP protocol support"
152 default m if NETFILTER_ADVANCED=n
154 Tracking FTP connections is problematic: special helpers are
155 required for tracking them, and doing masquerading and other forms
156 of Network Address Translation on them.
158 This is FTP support on Layer 3 independent connection tracking.
159 Layer 3 independent connection tracking is experimental scheme
160 which generalize ip_conntrack to support other layer 3 protocols.
162 To compile it as a module, choose M here. If unsure, say N.
164 config NF_CONNTRACK_H323
165 tristate "H.323 protocol support"
166 depends on (IPV6 || IPV6=n)
167 depends on NETFILTER_ADVANCED
169 H.323 is a VoIP signalling protocol from ITU-T. As one of the most
170 important VoIP protocols, it is widely used by voice hardware and
171 software including voice gateways, IP phones, Netmeeting, OpenPhone,
174 With this module you can support H.323 on a connection tracking/NAT
177 This module supports RAS, Fast Start, H.245 Tunnelling, Call
178 Forwarding, RTP/RTCP and T.120 based audio, video, fax, chat,
179 whiteboard, file transfer, etc. For more information, please
180 visit http://nath323.sourceforge.net/.
182 To compile it as a module, choose M here. If unsure, say N.
184 config NF_CONNTRACK_IRC
185 tristate "IRC protocol support"
186 default m if NETFILTER_ADVANCED=n
188 There is a commonly-used extension to IRC called
189 Direct Client-to-Client Protocol (DCC). This enables users to send
190 files to each other, and also chat to each other without the need
191 of a server. DCC Sending is used anywhere you send files over IRC,
192 and DCC Chat is most commonly used by Eggdrop bots. If you are
193 using NAT, this extension will enable you to send files and initiate
194 chats. Note that you do NOT need this extension to get files or
195 have others initiate chats, or everything else in IRC.
197 To compile it as a module, choose M here. If unsure, say N.
199 config NF_CONNTRACK_BROADCAST
202 config NF_CONNTRACK_NETBIOS_NS
203 tristate "NetBIOS name service protocol support"
204 depends on NETFILTER_ADVANCED
205 select NF_CONNTRACK_BROADCAST
207 NetBIOS name service requests are sent as broadcast messages from an
208 unprivileged port and responded to with unicast messages to the
209 same port. This make them hard to firewall properly because connection
210 tracking doesn't deal with broadcasts. This helper tracks locally
211 originating NetBIOS name service requests and the corresponding
212 responses. It relies on correct IP address configuration, specifically
213 netmask and broadcast address. When properly configured, the output
214 of "ip address show" should look similar to this:
216 $ ip -4 address show eth0
217 4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
218 inet 172.16.2.252/24 brd 172.16.2.255 scope global eth0
220 To compile it as a module, choose M here. If unsure, say N.
222 config NF_CONNTRACK_SNMP
223 tristate "SNMP service protocol support"
224 depends on NETFILTER_ADVANCED
225 select NF_CONNTRACK_BROADCAST
227 SNMP service requests are sent as broadcast messages from an
228 unprivileged port and responded to with unicast messages to the
229 same port. This make them hard to firewall properly because connection
230 tracking doesn't deal with broadcasts. This helper tracks locally
231 originating SNMP service requests and the corresponding
232 responses. It relies on correct IP address configuration, specifically
233 netmask and broadcast address.
235 To compile it as a module, choose M here. If unsure, say N.
237 config NF_CONNTRACK_PPTP
238 tristate "PPtP protocol support"
239 depends on NETFILTER_ADVANCED
240 select NF_CT_PROTO_GRE
242 This module adds support for PPTP (Point to Point Tunnelling
243 Protocol, RFC2637) connection tracking and NAT.
245 If you are running PPTP sessions over a stateful firewall or NAT
246 box, you may want to enable this feature.
248 Please note that not all PPTP modes of operation are supported yet.
249 Specifically these limitations exist:
250 - Blindly assumes that control connections are always established
251 in PNS->PAC direction. This is a violation of RFC2637.
252 - Only supports a single call within each session
254 To compile it as a module, choose M here. If unsure, say N.
256 config NF_CONNTRACK_SANE
257 tristate "SANE protocol support (EXPERIMENTAL)"
258 depends on EXPERIMENTAL
259 depends on NETFILTER_ADVANCED
261 SANE is a protocol for remote access to scanners as implemented
262 by the 'saned' daemon. Like FTP, it uses separate control and
265 With this module you can support SANE on a connection tracking
268 To compile it as a module, choose M here. If unsure, say N.
270 config NF_CONNTRACK_SIP
271 tristate "SIP protocol support"
272 default m if NETFILTER_ADVANCED=n
274 SIP is an application-layer control protocol that can establish,
275 modify, and terminate multimedia sessions (conferences) such as
276 Internet telephony calls. With the ip_conntrack_sip and
277 the nf_nat_sip modules you can support the protocol on a connection
278 tracking/NATing firewall.
280 To compile it as a module, choose M here. If unsure, say N.
282 config NF_CONNTRACK_TFTP
283 tristate "TFTP protocol support"
284 depends on NETFILTER_ADVANCED
286 TFTP connection tracking helper, this is required depending
287 on how restrictive your ruleset is.
288 If you are using a tftp client behind -j SNAT or -j MASQUERADING
291 To compile it as a module, choose M here. If unsure, say N.
294 tristate 'Connection tracking netlink interface'
295 select NETFILTER_NETLINK
296 default m if NETFILTER_ADVANCED=n
298 This option enables support for a netlink-based userspace interface
302 # transparent proxy support
303 config NETFILTER_TPROXY
304 tristate "Transparent proxying support (EXPERIMENTAL)"
305 depends on EXPERIMENTAL
306 depends on IP_NF_MANGLE
307 depends on NETFILTER_ADVANCED
309 This option enables transparent proxying support, that is,
310 support for handling non-locally bound IPv4 TCP and UDP sockets.
311 For it to work you will have to configure certain iptables rules
312 and use policy routing. For more information on how to set it up
313 see Documentation/networking/tproxy.txt.
315 To compile it as a module, choose M here. If unsure, say N.
317 config NETFILTER_XTABLES
318 tristate "Netfilter Xtables support (required for ip_tables)"
319 default m if NETFILTER_ADVANCED=n
321 This is required if you intend to use any of ip_tables,
322 ip6_tables or arp_tables.
326 comment "Xtables combined modules"
328 config NETFILTER_XT_MARK
329 tristate 'nfmark target and match support'
330 default m if NETFILTER_ADVANCED=n
332 This option adds the "MARK" target and "mark" match.
334 Netfilter mark matching allows you to match packets based on the
335 "nfmark" value in the packet.
336 The target allows you to create rules in the "mangle" table which alter
337 the netfilter mark (nfmark) field associated with the packet.
339 Prior to routing, the nfmark can influence the routing method (see
340 "Use netfilter MARK value as routing key") and can also be used by
341 other subsystems to change their behavior.
343 config NETFILTER_XT_CONNMARK
344 tristate 'ctmark target and match support'
345 depends on NF_CONNTRACK
346 depends on NETFILTER_ADVANCED
347 select NF_CONNTRACK_MARK
349 This option adds the "CONNMARK" target and "connmark" match.
351 Netfilter allows you to store a mark value per connection (a.k.a.
352 ctmark), similarly to the packet mark (nfmark). Using this
353 target and match, you can set and match on this mark.
355 # alphabetically ordered list of targets
357 comment "Xtables targets"
359 config NETFILTER_XT_TARGET_AUDIT
360 tristate "AUDIT target support"
362 depends on NETFILTER_ADVANCED
364 This option adds a 'AUDIT' target, which can be used to create
365 audit records for packets dropped/accepted.
367 To compileit as a module, choose M here. If unsure, say N.
369 config NETFILTER_XT_TARGET_CHECKSUM
370 tristate "CHECKSUM target support"
371 depends on IP_NF_MANGLE || IP6_NF_MANGLE
372 depends on NETFILTER_ADVANCED
374 This option adds a `CHECKSUM' target, which can be used in the iptables mangle
377 You can use this target to compute and fill in the checksum in
378 a packet that lacks a checksum. This is particularly useful,
379 if you need to work around old applications such as dhcp clients,
380 that do not work well with checksum offloads, but don't want to disable
381 checksum offload in your device.
383 To compile it as a module, choose M here. If unsure, say N.
385 config NETFILTER_XT_TARGET_CLASSIFY
386 tristate '"CLASSIFY" target support'
387 depends on NETFILTER_ADVANCED
389 This option adds a `CLASSIFY' target, which enables the user to set
390 the priority of a packet. Some qdiscs can use this value for
391 classification, among these are:
393 atm, cbq, dsmark, pfifo_fast, htb, prio
395 To compile it as a module, choose M here. If unsure, say N.
397 config NETFILTER_XT_TARGET_CONNMARK
398 tristate '"CONNMARK" target support'
399 depends on NF_CONNTRACK
400 depends on NETFILTER_ADVANCED
401 select NETFILTER_XT_CONNMARK
403 This is a backwards-compat option for the user's convenience
404 (e.g. when running oldconfig). It selects
405 CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
407 config NETFILTER_XT_TARGET_CONNSECMARK
408 tristate '"CONNSECMARK" target support'
409 depends on NF_CONNTRACK && NF_CONNTRACK_SECMARK
410 default m if NETFILTER_ADVANCED=n
412 The CONNSECMARK target copies security markings from packets
413 to connections, and restores security markings from connections
414 to packets (if the packets are not already marked). This would
415 normally be used in conjunction with the SECMARK target.
417 To compile it as a module, choose M here. If unsure, say N.
419 config NETFILTER_XT_TARGET_CT
420 tristate '"CT" target support'
421 depends on NF_CONNTRACK
422 depends on IP_NF_RAW || IP6_NF_RAW
423 depends on NETFILTER_ADVANCED
425 This options adds a `CT' target, which allows to specify initial
426 connection tracking parameters like events to be delivered and
427 the helper to be used.
429 To compile it as a module, choose M here. If unsure, say N.
431 config NETFILTER_XT_TARGET_DSCP
432 tristate '"DSCP" and "TOS" target support'
433 depends on IP_NF_MANGLE || IP6_NF_MANGLE
434 depends on NETFILTER_ADVANCED
436 This option adds a `DSCP' target, which allows you to manipulate
437 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
439 The DSCP field can have any value between 0x0 and 0x3f inclusive.
441 It also adds the "TOS" target, which allows you to create rules in
442 the "mangle" table which alter the Type Of Service field of an IPv4
443 or the Priority field of an IPv6 packet, prior to routing.
445 To compile it as a module, choose M here. If unsure, say N.
447 config NETFILTER_XT_TARGET_HL
448 tristate '"HL" hoplimit target support'
449 depends on IP_NF_MANGLE || IP6_NF_MANGLE
450 depends on NETFILTER_ADVANCED
452 This option adds the "HL" (for IPv6) and "TTL" (for IPv4)
453 targets, which enable the user to change the
454 hoplimit/time-to-live value of the IP header.
456 While it is safe to decrement the hoplimit/TTL value, the
457 modules also allow to increment and set the hoplimit value of
458 the header to arbitrary values. This is EXTREMELY DANGEROUS
459 since you can easily create immortal packets that loop
460 forever on the network.
462 config NETFILTER_XT_TARGET_IDLETIMER
463 tristate "IDLETIMER target support"
464 depends on NETFILTER_ADVANCED
467 This option adds the `IDLETIMER' target. Each matching packet
468 resets the timer associated with label specified when the rule is
469 added. When the timer expires, it triggers a sysfs notification.
470 The remaining time for expiration can be read via sysfs.
472 To compile it as a module, choose M here. If unsure, say N.
474 config NETFILTER_XT_TARGET_LED
475 tristate '"LED" target support'
476 depends on LEDS_CLASS && LEDS_TRIGGERS
477 depends on NETFILTER_ADVANCED
479 This option adds a `LED' target, which allows you to blink LEDs in
480 response to particular packets passing through your machine.
482 This can be used to turn a spare LED into a network activity LED,
483 which only flashes in response to FTP transfers, for example. Or
484 you could have an LED which lights up for a minute or two every time
485 somebody connects to your machine via SSH.
487 You will need support for the "led" class to make this work.
489 To create an LED trigger for incoming SSH traffic:
490 iptables -A INPUT -p tcp --dport 22 -j LED --led-trigger-id ssh --led-delay 1000
492 Then attach the new trigger to an LED on your system:
493 echo netfilter-ssh > /sys/class/leds/<ledname>/trigger
495 For more information on the LEDs available on your system, see
496 Documentation/leds-class.txt
498 config NETFILTER_XT_TARGET_MARK
499 tristate '"MARK" target support'
500 depends on NETFILTER_ADVANCED
501 select NETFILTER_XT_MARK
503 This is a backwards-compat option for the user's convenience
504 (e.g. when running oldconfig). It selects
505 CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
507 config NETFILTER_XT_TARGET_NFLOG
508 tristate '"NFLOG" target support'
509 default m if NETFILTER_ADVANCED=n
510 select NETFILTER_NETLINK_LOG
512 This option enables the NFLOG target, which allows to LOG
513 messages through nfnetlink_log.
515 To compile it as a module, choose M here. If unsure, say N.
517 config NETFILTER_XT_TARGET_NFQUEUE
518 tristate '"NFQUEUE" target Support'
519 depends on NETFILTER_ADVANCED
520 select NETFILTER_NETLINK_QUEUE
522 This target replaced the old obsolete QUEUE target.
524 As opposed to QUEUE, it supports 65535 different queues,
527 To compile it as a module, choose M here. If unsure, say N.
529 config NETFILTER_XT_TARGET_NOTRACK
530 tristate '"NOTRACK" target support'
531 depends on IP_NF_RAW || IP6_NF_RAW
532 depends on NF_CONNTRACK
533 depends on NETFILTER_ADVANCED
535 The NOTRACK target allows a select rule to specify
536 which packets *not* to enter the conntrack/NAT
537 subsystem with all the consequences (no ICMP error tracking,
538 no protocol helpers for the selected packets).
540 If you want to compile it as a module, say M here and read
541 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
543 config NETFILTER_XT_TARGET_RATEEST
544 tristate '"RATEEST" target support'
545 depends on NETFILTER_ADVANCED
547 This option adds a `RATEEST' target, which allows to measure
548 rates similar to TC estimators. The `rateest' match can be
549 used to match on the measured rates.
551 To compile it as a module, choose M here. If unsure, say N.
553 config NETFILTER_XT_TARGET_TEE
554 tristate '"TEE" - packet cloning to alternate destination'
555 depends on NETFILTER_ADVANCED
556 depends on (IPV6 || IPV6=n)
557 depends on !NF_CONNTRACK || NF_CONNTRACK
559 This option adds a "TEE" target with which a packet can be cloned and
560 this clone be rerouted to another nexthop.
562 config NETFILTER_XT_TARGET_TPROXY
563 tristate '"TPROXY" target support (EXPERIMENTAL)'
564 depends on EXPERIMENTAL
565 depends on NETFILTER_TPROXY
566 depends on NETFILTER_XTABLES
567 depends on NETFILTER_ADVANCED
568 select NF_DEFRAG_IPV4
569 select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES
571 This option adds a `TPROXY' target, which is somewhat similar to
572 REDIRECT. It can only be used in the mangle table and is useful
573 to redirect traffic to a transparent proxy. It does _not_ depend
574 on Netfilter connection tracking and NAT, unlike REDIRECT.
576 To compile it as a module, choose M here. If unsure, say N.
578 config NETFILTER_XT_TARGET_TRACE
579 tristate '"TRACE" target support'
580 depends on IP_NF_RAW || IP6_NF_RAW
581 depends on NETFILTER_ADVANCED
583 The TRACE target allows you to mark packets so that the kernel
584 will log every rule which match the packets as those traverse
585 the tables, chains, rules.
587 If you want to compile it as a module, say M here and read
588 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
590 config NETFILTER_XT_TARGET_SECMARK
591 tristate '"SECMARK" target support'
592 depends on NETWORK_SECMARK
593 default m if NETFILTER_ADVANCED=n
595 The SECMARK target allows security marking of network
596 packets, for use with security subsystems.
598 To compile it as a module, choose M here. If unsure, say N.
600 config NETFILTER_XT_TARGET_TCPMSS
601 tristate '"TCPMSS" target support'
602 depends on (IPV6 || IPV6=n)
603 default m if NETFILTER_ADVANCED=n
605 This option adds a `TCPMSS' target, which allows you to alter the
606 MSS value of TCP SYN packets, to control the maximum size for that
607 connection (usually limiting it to your outgoing interface's MTU
610 This is used to overcome criminally braindead ISPs or servers which
611 block ICMP Fragmentation Needed packets. The symptoms of this
612 problem are that everything works fine from your Linux
613 firewall/router, but machines behind it can never exchange large
615 1) Web browsers connect, then hang with no data received.
616 2) Small mail works fine, but large emails hang.
617 3) ssh works fine, but scp hangs after initial handshaking.
619 Workaround: activate this option and add a rule to your firewall
622 iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
623 -j TCPMSS --clamp-mss-to-pmtu
625 To compile it as a module, choose M here. If unsure, say N.
627 config NETFILTER_XT_TARGET_TCPOPTSTRIP
628 tristate '"TCPOPTSTRIP" target support (EXPERIMENTAL)'
629 depends on EXPERIMENTAL
630 depends on IP_NF_MANGLE || IP6_NF_MANGLE
631 depends on NETFILTER_ADVANCED
633 This option adds a "TCPOPTSTRIP" target, which allows you to strip
634 TCP options from TCP packets.
636 # alphabetically ordered list of matches
638 comment "Xtables matches"
640 config NETFILTER_XT_MATCH_CLUSTER
641 tristate '"cluster" match support'
642 depends on NF_CONNTRACK
643 depends on NETFILTER_ADVANCED
645 This option allows you to build work-load-sharing clusters of
646 network servers/stateful firewalls without having a dedicated
647 load-balancing router/server/switch. Basically, this match returns
648 true when the packet must be handled by this cluster node. Thus,
649 all nodes see all packets and this match decides which node handles
650 what packets. The work-load sharing algorithm is based on source
653 If you say Y or M here, try `iptables -m cluster --help` for
656 config NETFILTER_XT_MATCH_COMMENT
657 tristate '"comment" match support'
658 depends on NETFILTER_ADVANCED
660 This option adds a `comment' dummy-match, which allows you to put
661 comments in your iptables ruleset.
663 If you want to compile it as a module, say M here and read
664 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
666 config NETFILTER_XT_MATCH_CONNBYTES
667 tristate '"connbytes" per-connection counter match support'
668 depends on NF_CONNTRACK
669 depends on NETFILTER_ADVANCED
671 This option adds a `connbytes' match, which allows you to match the
672 number of bytes and/or packets for each direction within a connection.
674 If you want to compile it as a module, say M here and read
675 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
677 config NETFILTER_XT_MATCH_CONNLIMIT
678 tristate '"connlimit" match support"'
679 depends on NF_CONNTRACK
680 depends on NETFILTER_ADVANCED
682 This match allows you to match against the number of parallel
683 connections to a server per client IP address (or address block).
685 config NETFILTER_XT_MATCH_CONNMARK
686 tristate '"connmark" connection mark match support'
687 depends on NF_CONNTRACK
688 depends on NETFILTER_ADVANCED
689 select NETFILTER_XT_CONNMARK
691 This is a backwards-compat option for the user's convenience
692 (e.g. when running oldconfig). It selects
693 CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
695 config NETFILTER_XT_MATCH_CONNTRACK
696 tristate '"conntrack" connection tracking match support'
697 depends on NF_CONNTRACK
698 default m if NETFILTER_ADVANCED=n
700 This is a general conntrack match module, a superset of the state match.
702 It allows matching on additional conntrack information, which is
703 useful in complex configurations, such as NAT gateways with multiple
704 internet links or tunnels.
706 To compile it as a module, choose M here. If unsure, say N.
708 config NETFILTER_XT_MATCH_CPU
709 tristate '"cpu" match support'
710 depends on NETFILTER_ADVANCED
712 CPU matching allows you to match packets based on the CPU
713 currently handling the packet.
715 To compile it as a module, choose M here. If unsure, say N.
717 config NETFILTER_XT_MATCH_DCCP
718 tristate '"dccp" protocol match support'
719 depends on NETFILTER_ADVANCED
722 With this option enabled, you will be able to use the iptables
723 `dccp' match in order to match on DCCP source/destination ports
726 If you want to compile it as a module, say M here and read
727 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
729 config NETFILTER_XT_MATCH_DSCP
730 tristate '"dscp" and "tos" match support'
731 depends on NETFILTER_ADVANCED
733 This option adds a `DSCP' match, which allows you to match against
734 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
736 The DSCP field can have any value between 0x0 and 0x3f inclusive.
738 It will also add a "tos" match, which allows you to match packets
739 based on the Type Of Service fields of the IPv4 packet (which share
740 the same bits as DSCP).
742 To compile it as a module, choose M here. If unsure, say N.
744 config NETFILTER_XT_MATCH_ESP
745 tristate '"esp" match support'
746 depends on NETFILTER_ADVANCED
748 This match extension allows you to match a range of SPIs
749 inside ESP header of IPSec packets.
751 To compile it as a module, choose M here. If unsure, say N.
753 config NETFILTER_XT_MATCH_HASHLIMIT
754 tristate '"hashlimit" match support'
755 depends on (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
756 depends on NETFILTER_ADVANCED
758 This option adds a `hashlimit' match.
760 As opposed to `limit', this match dynamically creates a hash table
761 of limit buckets, based on your selection of source/destination
762 addresses and/or ports.
764 It enables you to express policies like `10kpps for any given
765 destination address' or `500pps from any given source address'
768 config NETFILTER_XT_MATCH_HELPER
769 tristate '"helper" match support'
770 depends on NF_CONNTRACK
771 depends on NETFILTER_ADVANCED
773 Helper matching allows you to match packets in dynamic connections
774 tracked by a conntrack-helper, ie. ip_conntrack_ftp
776 To compile it as a module, choose M here. If unsure, say Y.
778 config NETFILTER_XT_MATCH_HL
779 tristate '"hl" hoplimit/TTL match support'
780 depends on NETFILTER_ADVANCED
782 HL matching allows you to match packets based on the hoplimit
783 in the IPv6 header, or the time-to-live field in the IPv4
784 header of the packet.
786 config NETFILTER_XT_MATCH_IPRANGE
787 tristate '"iprange" address range match support'
788 depends on NETFILTER_ADVANCED
790 This option adds a "iprange" match, which allows you to match based on
791 an IP address range. (Normal iptables only matches on single addresses
792 with an optional mask.)
796 config NETFILTER_XT_MATCH_IPVS
797 tristate '"ipvs" match support'
799 depends on NETFILTER_ADVANCED
800 depends on NF_CONNTRACK
802 This option allows you to match against IPVS properties of a packet.
806 config NETFILTER_XT_MATCH_LENGTH
807 tristate '"length" match support'
808 depends on NETFILTER_ADVANCED
810 This option allows you to match the length of a packet against a
811 specific value or range of values.
813 To compile it as a module, choose M here. If unsure, say N.
815 config NETFILTER_XT_MATCH_LIMIT
816 tristate '"limit" match support'
817 depends on NETFILTER_ADVANCED
819 limit matching allows you to control the rate at which a rule can be
820 matched: mainly useful in combination with the LOG target ("LOG
821 target support", below) and to avoid some Denial of Service attacks.
823 To compile it as a module, choose M here. If unsure, say N.
825 config NETFILTER_XT_MATCH_MAC
826 tristate '"mac" address match support'
827 depends on NETFILTER_ADVANCED
829 MAC matching allows you to match packets based on the source
830 Ethernet address of the packet.
832 To compile it as a module, choose M here. If unsure, say N.
834 config NETFILTER_XT_MATCH_MARK
835 tristate '"mark" match support'
836 depends on NETFILTER_ADVANCED
837 select NETFILTER_XT_MARK
839 This is a backwards-compat option for the user's convenience
840 (e.g. when running oldconfig). It selects
841 CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
843 config NETFILTER_XT_MATCH_MULTIPORT
844 tristate '"multiport" Multiple port match support'
845 depends on NETFILTER_ADVANCED
847 Multiport matching allows you to match TCP or UDP packets based on
848 a series of source or destination ports: normally a rule can only
849 match a single range of ports.
851 To compile it as a module, choose M here. If unsure, say N.
853 config NETFILTER_XT_MATCH_OSF
854 tristate '"osf" Passive OS fingerprint match'
855 depends on NETFILTER_ADVANCED && NETFILTER_NETLINK
857 This option selects the Passive OS Fingerprinting match module
858 that allows to passively match the remote operating system by
859 analyzing incoming TCP SYN packets.
861 Rules and loading software can be downloaded from
862 http://www.ioremap.net/projects/osf
864 To compile it as a module, choose M here. If unsure, say N.
866 config NETFILTER_XT_MATCH_OWNER
867 tristate '"owner" match support'
868 depends on NETFILTER_ADVANCED
870 Socket owner matching allows you to match locally-generated packets
871 based on who created the socket: the user or group. It is also
872 possible to check whether a socket actually exists.
874 config NETFILTER_XT_MATCH_POLICY
875 tristate 'IPsec "policy" match support'
877 default m if NETFILTER_ADVANCED=n
879 Policy matching allows you to match packets based on the
880 IPsec policy that was used during decapsulation/will
881 be used during encapsulation.
883 To compile it as a module, choose M here. If unsure, say N.
885 config NETFILTER_XT_MATCH_PHYSDEV
886 tristate '"physdev" match support'
887 depends on BRIDGE && BRIDGE_NETFILTER
888 depends on NETFILTER_ADVANCED
890 Physdev packet matching matches against the physical bridge ports
891 the IP packet arrived on or will leave by.
893 To compile it as a module, choose M here. If unsure, say N.
895 config NETFILTER_XT_MATCH_PKTTYPE
896 tristate '"pkttype" packet type match support'
897 depends on NETFILTER_ADVANCED
899 Packet type matching allows you to match a packet by
900 its "class", eg. BROADCAST, MULTICAST, ...
903 iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG
905 To compile it as a module, choose M here. If unsure, say N.
907 config NETFILTER_XT_MATCH_QUOTA
908 tristate '"quota" match support'
909 depends on NETFILTER_ADVANCED
911 This option adds a `quota' match, which allows to match on a
914 If you want to compile it as a module, say M here and read
915 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
917 config NETFILTER_XT_MATCH_RATEEST
918 tristate '"rateest" match support'
919 depends on NETFILTER_ADVANCED
920 select NETFILTER_XT_TARGET_RATEEST
922 This option adds a `rateest' match, which allows to match on the
923 rate estimated by the RATEEST target.
925 To compile it as a module, choose M here. If unsure, say N.
927 config NETFILTER_XT_MATCH_REALM
928 tristate '"realm" match support'
929 depends on NETFILTER_ADVANCED
930 select IP_ROUTE_CLASSID
932 This option adds a `realm' match, which allows you to use the realm
933 key from the routing subsystem inside iptables.
935 This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option
938 If you want to compile it as a module, say M here and read
939 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
941 config NETFILTER_XT_MATCH_RECENT
942 tristate '"recent" match support'
943 depends on NETFILTER_ADVANCED
945 This match is used for creating one or many lists of recently
946 used addresses and then matching against that/those list(s).
948 Short options are available by using 'iptables -m recent -h'
949 Official Website: <http://snowman.net/projects/ipt_recent/>
951 config NETFILTER_XT_MATCH_SCTP
952 tristate '"sctp" protocol match support (EXPERIMENTAL)'
953 depends on EXPERIMENTAL
954 depends on NETFILTER_ADVANCED
957 With this option enabled, you will be able to use the
958 `sctp' match in order to match on SCTP source/destination ports
959 and SCTP chunk types.
961 If you want to compile it as a module, say M here and read
962 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
964 config NETFILTER_XT_MATCH_SOCKET
965 tristate '"socket" match support (EXPERIMENTAL)'
966 depends on EXPERIMENTAL
967 depends on NETFILTER_TPROXY
968 depends on NETFILTER_XTABLES
969 depends on NETFILTER_ADVANCED
970 depends on !NF_CONNTRACK || NF_CONNTRACK
971 select NF_DEFRAG_IPV4
972 select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES
974 This option adds a `socket' match, which can be used to match
975 packets for which a TCP or UDP socket lookup finds a valid socket.
976 It can be used in combination with the MARK target and policy
977 routing to implement full featured non-locally bound sockets.
979 To compile it as a module, choose M here. If unsure, say N.
981 config NETFILTER_XT_MATCH_STATE
982 tristate '"state" match support'
983 depends on NF_CONNTRACK
984 default m if NETFILTER_ADVANCED=n
986 Connection state matching allows you to match packets based on their
987 relationship to a tracked connection (ie. previous packets). This
988 is a powerful tool for packet classification.
990 To compile it as a module, choose M here. If unsure, say N.
992 config NETFILTER_XT_MATCH_STATISTIC
993 tristate '"statistic" match support'
994 depends on NETFILTER_ADVANCED
996 This option adds a `statistic' match, which allows you to match
997 on packets periodically or randomly with a given percentage.
999 To compile it as a module, choose M here. If unsure, say N.
1001 config NETFILTER_XT_MATCH_STRING
1002 tristate '"string" match support'
1003 depends on NETFILTER_ADVANCED
1005 select TEXTSEARCH_KMP
1006 select TEXTSEARCH_BM
1007 select TEXTSEARCH_FSM
1009 This option adds a `string' match, which allows you to look for
1010 pattern matchings in packets.
1012 To compile it as a module, choose M here. If unsure, say N.
1014 config NETFILTER_XT_MATCH_TCPMSS
1015 tristate '"tcpmss" match support'
1016 depends on NETFILTER_ADVANCED
1018 This option adds a `tcpmss' match, which allows you to examine the
1019 MSS value of TCP SYN packets, which control the maximum packet size
1020 for that connection.
1022 To compile it as a module, choose M here. If unsure, say N.
1024 config NETFILTER_XT_MATCH_TIME
1025 tristate '"time" match support'
1026 depends on NETFILTER_ADVANCED
1028 This option adds a "time" match, which allows you to match based on
1029 the packet arrival time (at the machine which netfilter is running)
1030 on) or departure time/date (for locally generated packets).
1032 If you say Y here, try `iptables -m time --help` for
1035 If you want to compile it as a module, say M here.
1038 config NETFILTER_XT_MATCH_U32
1039 tristate '"u32" match support'
1040 depends on NETFILTER_ADVANCED
1042 u32 allows you to extract quantities of up to 4 bytes from a packet,
1043 AND them with specified masks, shift them by specified amounts and
1044 test whether the results are in any of a set of specified ranges.
1045 The specification of what to extract is general enough to skip over
1046 headers with lengths stored in the packet, as in IP or TCP header
1049 Details and examples are in the kernel module source.
1051 endif # NETFILTER_XTABLES
1055 source "net/netfilter/ipvs/Kconfig"