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 config NETFILTER_XT_SET
356 tristate 'set target and match support'
358 depends on NETFILTER_ADVANCED
360 This option adds the "SET" target and "set" match.
362 Using this target and match, you can add/delete and match
363 elements in the sets created by ipset(8).
365 To compile it as a module, choose M here. If unsure, say N.
367 # alphabetically ordered list of targets
369 comment "Xtables targets"
371 config NETFILTER_XT_TARGET_AUDIT
372 tristate "AUDIT target support"
374 depends on NETFILTER_ADVANCED
376 This option adds a 'AUDIT' target, which can be used to create
377 audit records for packets dropped/accepted.
379 To compileit as a module, choose M here. If unsure, say N.
381 config NETFILTER_XT_TARGET_CHECKSUM
382 tristate "CHECKSUM target support"
383 depends on IP_NF_MANGLE || IP6_NF_MANGLE
384 depends on NETFILTER_ADVANCED
386 This option adds a `CHECKSUM' target, which can be used in the iptables mangle
389 You can use this target to compute and fill in the checksum in
390 a packet that lacks a checksum. This is particularly useful,
391 if you need to work around old applications such as dhcp clients,
392 that do not work well with checksum offloads, but don't want to disable
393 checksum offload in your device.
395 To compile it as a module, choose M here. If unsure, say N.
397 config NETFILTER_XT_TARGET_CLASSIFY
398 tristate '"CLASSIFY" target support'
399 depends on NETFILTER_ADVANCED
401 This option adds a `CLASSIFY' target, which enables the user to set
402 the priority of a packet. Some qdiscs can use this value for
403 classification, among these are:
405 atm, cbq, dsmark, pfifo_fast, htb, prio
407 To compile it as a module, choose M here. If unsure, say N.
409 config NETFILTER_XT_TARGET_CONNMARK
410 tristate '"CONNMARK" target support'
411 depends on NF_CONNTRACK
412 depends on NETFILTER_ADVANCED
413 select NETFILTER_XT_CONNMARK
415 This is a backwards-compat option for the user's convenience
416 (e.g. when running oldconfig). It selects
417 CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
419 config NETFILTER_XT_TARGET_CONNSECMARK
420 tristate '"CONNSECMARK" target support'
421 depends on NF_CONNTRACK && NF_CONNTRACK_SECMARK
422 default m if NETFILTER_ADVANCED=n
424 The CONNSECMARK target copies security markings from packets
425 to connections, and restores security markings from connections
426 to packets (if the packets are not already marked). This would
427 normally be used in conjunction with the SECMARK target.
429 To compile it as a module, choose M here. If unsure, say N.
431 config NETFILTER_XT_TARGET_CT
432 tristate '"CT" target support'
433 depends on NF_CONNTRACK
434 depends on IP_NF_RAW || IP6_NF_RAW
435 depends on NETFILTER_ADVANCED
437 This options adds a `CT' target, which allows to specify initial
438 connection tracking parameters like events to be delivered and
439 the helper to be used.
441 To compile it as a module, choose M here. If unsure, say N.
443 config NETFILTER_XT_TARGET_DSCP
444 tristate '"DSCP" and "TOS" target support'
445 depends on IP_NF_MANGLE || IP6_NF_MANGLE
446 depends on NETFILTER_ADVANCED
448 This option adds a `DSCP' target, which allows you to manipulate
449 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
451 The DSCP field can have any value between 0x0 and 0x3f inclusive.
453 It also adds the "TOS" target, which allows you to create rules in
454 the "mangle" table which alter the Type Of Service field of an IPv4
455 or the Priority field of an IPv6 packet, prior to routing.
457 To compile it as a module, choose M here. If unsure, say N.
459 config NETFILTER_XT_TARGET_HL
460 tristate '"HL" hoplimit target support'
461 depends on IP_NF_MANGLE || IP6_NF_MANGLE
462 depends on NETFILTER_ADVANCED
464 This option adds the "HL" (for IPv6) and "TTL" (for IPv4)
465 targets, which enable the user to change the
466 hoplimit/time-to-live value of the IP header.
468 While it is safe to decrement the hoplimit/TTL value, the
469 modules also allow to increment and set the hoplimit value of
470 the header to arbitrary values. This is EXTREMELY DANGEROUS
471 since you can easily create immortal packets that loop
472 forever on the network.
474 config NETFILTER_XT_TARGET_IDLETIMER
475 tristate "IDLETIMER target support"
476 depends on NETFILTER_ADVANCED
479 This option adds the `IDLETIMER' target. Each matching packet
480 resets the timer associated with label specified when the rule is
481 added. When the timer expires, it triggers a sysfs notification.
482 The remaining time for expiration can be read via sysfs.
484 To compile it as a module, choose M here. If unsure, say N.
486 config NETFILTER_XT_TARGET_LED
487 tristate '"LED" target support'
488 depends on LEDS_CLASS && LEDS_TRIGGERS
489 depends on NETFILTER_ADVANCED
491 This option adds a `LED' target, which allows you to blink LEDs in
492 response to particular packets passing through your machine.
494 This can be used to turn a spare LED into a network activity LED,
495 which only flashes in response to FTP transfers, for example. Or
496 you could have an LED which lights up for a minute or two every time
497 somebody connects to your machine via SSH.
499 You will need support for the "led" class to make this work.
501 To create an LED trigger for incoming SSH traffic:
502 iptables -A INPUT -p tcp --dport 22 -j LED --led-trigger-id ssh --led-delay 1000
504 Then attach the new trigger to an LED on your system:
505 echo netfilter-ssh > /sys/class/leds/<ledname>/trigger
507 For more information on the LEDs available on your system, see
508 Documentation/leds/leds-class.txt
510 config NETFILTER_XT_TARGET_MARK
511 tristate '"MARK" target support'
512 depends on NETFILTER_ADVANCED
513 select NETFILTER_XT_MARK
515 This is a backwards-compat option for the user's convenience
516 (e.g. when running oldconfig). It selects
517 CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
519 config NETFILTER_XT_TARGET_NFLOG
520 tristate '"NFLOG" target support'
521 default m if NETFILTER_ADVANCED=n
522 select NETFILTER_NETLINK_LOG
524 This option enables the NFLOG target, which allows to LOG
525 messages through nfnetlink_log.
527 To compile it as a module, choose M here. If unsure, say N.
529 config NETFILTER_XT_TARGET_NFQUEUE
530 tristate '"NFQUEUE" target Support'
531 depends on NETFILTER_ADVANCED
532 select NETFILTER_NETLINK_QUEUE
534 This target replaced the old obsolete QUEUE target.
536 As opposed to QUEUE, it supports 65535 different queues,
539 To compile it as a module, choose M here. If unsure, say N.
541 config NETFILTER_XT_TARGET_NOTRACK
542 tristate '"NOTRACK" target support'
543 depends on IP_NF_RAW || IP6_NF_RAW
544 depends on NF_CONNTRACK
546 The NOTRACK target allows a select rule to specify
547 which packets *not* to enter the conntrack/NAT
548 subsystem with all the consequences (no ICMP error tracking,
549 no protocol helpers for the selected packets).
551 If you want to compile it as a module, say M here and read
552 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
554 config NETFILTER_XT_TARGET_RATEEST
555 tristate '"RATEEST" target support'
556 depends on NETFILTER_ADVANCED
558 This option adds a `RATEEST' target, which allows to measure
559 rates similar to TC estimators. The `rateest' match can be
560 used to match on the measured rates.
562 To compile it as a module, choose M here. If unsure, say N.
564 config NETFILTER_XT_TARGET_TEE
565 tristate '"TEE" - packet cloning to alternate destination'
566 depends on NETFILTER_ADVANCED
567 depends on (IPV6 || IPV6=n)
568 depends on !NF_CONNTRACK || NF_CONNTRACK
570 This option adds a "TEE" target with which a packet can be cloned and
571 this clone be rerouted to another nexthop.
573 config NETFILTER_XT_TARGET_TPROXY
574 tristate '"TPROXY" target support (EXPERIMENTAL)'
575 depends on EXPERIMENTAL
576 depends on NETFILTER_TPROXY
577 depends on NETFILTER_XTABLES
578 depends on NETFILTER_ADVANCED
579 select NF_DEFRAG_IPV4
580 select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES
582 This option adds a `TPROXY' target, which is somewhat similar to
583 REDIRECT. It can only be used in the mangle table and is useful
584 to redirect traffic to a transparent proxy. It does _not_ depend
585 on Netfilter connection tracking and NAT, unlike REDIRECT.
587 To compile it as a module, choose M here. If unsure, say N.
589 config NETFILTER_XT_TARGET_TRACE
590 tristate '"TRACE" target support'
591 depends on IP_NF_RAW || IP6_NF_RAW
592 depends on NETFILTER_ADVANCED
594 The TRACE target allows you to mark packets so that the kernel
595 will log every rule which match the packets as those traverse
596 the tables, chains, rules.
598 If you want to compile it as a module, say M here and read
599 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
601 config NETFILTER_XT_TARGET_SECMARK
602 tristate '"SECMARK" target support'
603 depends on NETWORK_SECMARK
604 default m if NETFILTER_ADVANCED=n
606 The SECMARK target allows security marking of network
607 packets, for use with security subsystems.
609 To compile it as a module, choose M here. If unsure, say N.
611 config NETFILTER_XT_TARGET_TCPMSS
612 tristate '"TCPMSS" target support'
613 depends on (IPV6 || IPV6=n)
614 default m if NETFILTER_ADVANCED=n
616 This option adds a `TCPMSS' target, which allows you to alter the
617 MSS value of TCP SYN packets, to control the maximum size for that
618 connection (usually limiting it to your outgoing interface's MTU
621 This is used to overcome criminally braindead ISPs or servers which
622 block ICMP Fragmentation Needed packets. The symptoms of this
623 problem are that everything works fine from your Linux
624 firewall/router, but machines behind it can never exchange large
626 1) Web browsers connect, then hang with no data received.
627 2) Small mail works fine, but large emails hang.
628 3) ssh works fine, but scp hangs after initial handshaking.
630 Workaround: activate this option and add a rule to your firewall
633 iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
634 -j TCPMSS --clamp-mss-to-pmtu
636 To compile it as a module, choose M here. If unsure, say N.
638 config NETFILTER_XT_TARGET_TCPOPTSTRIP
639 tristate '"TCPOPTSTRIP" target support (EXPERIMENTAL)'
640 depends on EXPERIMENTAL
641 depends on IP_NF_MANGLE || IP6_NF_MANGLE
642 depends on NETFILTER_ADVANCED
644 This option adds a "TCPOPTSTRIP" target, which allows you to strip
645 TCP options from TCP packets.
647 # alphabetically ordered list of matches
649 comment "Xtables matches"
651 config NETFILTER_XT_MATCH_ADDRTYPE
652 tristate '"addrtype" address type match support'
653 depends on NETFILTER_ADVANCED
655 This option allows you to match what routing thinks of an address,
656 eg. UNICAST, LOCAL, BROADCAST, ...
658 If you want to compile it as a module, say M here and read
659 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
661 config NETFILTER_XT_MATCH_CLUSTER
662 tristate '"cluster" match support'
663 depends on NF_CONNTRACK
664 depends on NETFILTER_ADVANCED
666 This option allows you to build work-load-sharing clusters of
667 network servers/stateful firewalls without having a dedicated
668 load-balancing router/server/switch. Basically, this match returns
669 true when the packet must be handled by this cluster node. Thus,
670 all nodes see all packets and this match decides which node handles
671 what packets. The work-load sharing algorithm is based on source
674 If you say Y or M here, try `iptables -m cluster --help` for
677 config NETFILTER_XT_MATCH_COMMENT
678 tristate '"comment" match support'
679 depends on NETFILTER_ADVANCED
681 This option adds a `comment' dummy-match, which allows you to put
682 comments in your iptables ruleset.
684 If you want to compile it as a module, say M here and read
685 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
687 config NETFILTER_XT_MATCH_CONNBYTES
688 tristate '"connbytes" per-connection counter match support'
689 depends on NF_CONNTRACK
690 depends on NETFILTER_ADVANCED
692 This option adds a `connbytes' match, which allows you to match the
693 number of bytes and/or packets for each direction within a connection.
695 If you want to compile it as a module, say M here and read
696 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
698 config NETFILTER_XT_MATCH_CONNLIMIT
699 tristate '"connlimit" match support"'
700 depends on NF_CONNTRACK
701 depends on NETFILTER_ADVANCED
703 This match allows you to match against the number of parallel
704 connections to a server per client IP address (or address block).
706 config NETFILTER_XT_MATCH_CONNMARK
707 tristate '"connmark" connection mark match support'
708 depends on NF_CONNTRACK
709 depends on NETFILTER_ADVANCED
710 select NETFILTER_XT_CONNMARK
712 This is a backwards-compat option for the user's convenience
713 (e.g. when running oldconfig). It selects
714 CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
716 config NETFILTER_XT_MATCH_CONNTRACK
717 tristate '"conntrack" connection tracking match support'
718 depends on NF_CONNTRACK
719 default m if NETFILTER_ADVANCED=n
721 This is a general conntrack match module, a superset of the state match.
723 It allows matching on additional conntrack information, which is
724 useful in complex configurations, such as NAT gateways with multiple
725 internet links or tunnels.
727 To compile it as a module, choose M here. If unsure, say N.
729 config NETFILTER_XT_MATCH_CPU
730 tristate '"cpu" match support'
731 depends on NETFILTER_ADVANCED
733 CPU matching allows you to match packets based on the CPU
734 currently handling the packet.
736 To compile it as a module, choose M here. If unsure, say N.
738 config NETFILTER_XT_MATCH_DCCP
739 tristate '"dccp" protocol match support'
740 depends on NETFILTER_ADVANCED
743 With this option enabled, you will be able to use the iptables
744 `dccp' match in order to match on DCCP source/destination ports
747 If you want to compile it as a module, say M here and read
748 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
750 config NETFILTER_XT_MATCH_DEVGROUP
751 tristate '"devgroup" match support'
752 depends on NETFILTER_ADVANCED
754 This options adds a `devgroup' match, which allows to match on the
755 device group a network device is assigned to.
757 To compile it as a module, choose M here. If unsure, say N.
759 config NETFILTER_XT_MATCH_DSCP
760 tristate '"dscp" and "tos" match support'
761 depends on NETFILTER_ADVANCED
763 This option adds a `DSCP' match, which allows you to match against
764 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
766 The DSCP field can have any value between 0x0 and 0x3f inclusive.
768 It will also add a "tos" match, which allows you to match packets
769 based on the Type Of Service fields of the IPv4 packet (which share
770 the same bits as DSCP).
772 To compile it as a module, choose M here. If unsure, say N.
774 config NETFILTER_XT_MATCH_ESP
775 tristate '"esp" match support'
776 depends on NETFILTER_ADVANCED
778 This match extension allows you to match a range of SPIs
779 inside ESP header of IPSec packets.
781 To compile it as a module, choose M here. If unsure, say N.
783 config NETFILTER_XT_MATCH_HASHLIMIT
784 tristate '"hashlimit" match support'
785 depends on (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
786 depends on NETFILTER_ADVANCED
788 This option adds a `hashlimit' match.
790 As opposed to `limit', this match dynamically creates a hash table
791 of limit buckets, based on your selection of source/destination
792 addresses and/or ports.
794 It enables you to express policies like `10kpps for any given
795 destination address' or `500pps from any given source address'
798 config NETFILTER_XT_MATCH_HELPER
799 tristate '"helper" match support'
800 depends on NF_CONNTRACK
801 depends on NETFILTER_ADVANCED
803 Helper matching allows you to match packets in dynamic connections
804 tracked by a conntrack-helper, ie. ip_conntrack_ftp
806 To compile it as a module, choose M here. If unsure, say Y.
808 config NETFILTER_XT_MATCH_HL
809 tristate '"hl" hoplimit/TTL match support'
810 depends on NETFILTER_ADVANCED
812 HL matching allows you to match packets based on the hoplimit
813 in the IPv6 header, or the time-to-live field in the IPv4
814 header of the packet.
816 config NETFILTER_XT_MATCH_IPRANGE
817 tristate '"iprange" address range match support'
818 depends on NETFILTER_ADVANCED
820 This option adds a "iprange" match, which allows you to match based on
821 an IP address range. (Normal iptables only matches on single addresses
822 with an optional mask.)
826 config NETFILTER_XT_MATCH_IPVS
827 tristate '"ipvs" match support'
829 depends on NETFILTER_ADVANCED
830 depends on NF_CONNTRACK
832 This option allows you to match against IPVS properties of a packet.
836 config NETFILTER_XT_MATCH_LENGTH
837 tristate '"length" match support'
838 depends on NETFILTER_ADVANCED
840 This option allows you to match the length of a packet against a
841 specific value or range of values.
843 To compile it as a module, choose M here. If unsure, say N.
845 config NETFILTER_XT_MATCH_LIMIT
846 tristate '"limit" match support'
847 depends on NETFILTER_ADVANCED
849 limit matching allows you to control the rate at which a rule can be
850 matched: mainly useful in combination with the LOG target ("LOG
851 target support", below) and to avoid some Denial of Service attacks.
853 To compile it as a module, choose M here. If unsure, say N.
855 config NETFILTER_XT_MATCH_MAC
856 tristate '"mac" address match support'
857 depends on NETFILTER_ADVANCED
859 MAC matching allows you to match packets based on the source
860 Ethernet address of the packet.
862 To compile it as a module, choose M here. If unsure, say N.
864 config NETFILTER_XT_MATCH_MARK
865 tristate '"mark" match support'
866 depends on NETFILTER_ADVANCED
867 select NETFILTER_XT_MARK
869 This is a backwards-compat option for the user's convenience
870 (e.g. when running oldconfig). It selects
871 CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
873 config NETFILTER_XT_MATCH_MULTIPORT
874 tristate '"multiport" Multiple port match support'
875 depends on NETFILTER_ADVANCED
877 Multiport matching allows you to match TCP or UDP packets based on
878 a series of source or destination ports: normally a rule can only
879 match a single range of ports.
881 To compile it as a module, choose M here. If unsure, say N.
883 config NETFILTER_XT_MATCH_OSF
884 tristate '"osf" Passive OS fingerprint match'
885 depends on NETFILTER_ADVANCED && NETFILTER_NETLINK
887 This option selects the Passive OS Fingerprinting match module
888 that allows to passively match the remote operating system by
889 analyzing incoming TCP SYN packets.
891 Rules and loading software can be downloaded from
892 http://www.ioremap.net/projects/osf
894 To compile it as a module, choose M here. If unsure, say N.
896 config NETFILTER_XT_MATCH_OWNER
897 tristate '"owner" match support'
898 depends on NETFILTER_ADVANCED
900 Socket owner matching allows you to match locally-generated packets
901 based on who created the socket: the user or group. It is also
902 possible to check whether a socket actually exists.
904 config NETFILTER_XT_MATCH_POLICY
905 tristate 'IPsec "policy" match support'
907 default m if NETFILTER_ADVANCED=n
909 Policy matching allows you to match packets based on the
910 IPsec policy that was used during decapsulation/will
911 be used during encapsulation.
913 To compile it as a module, choose M here. If unsure, say N.
915 config NETFILTER_XT_MATCH_PHYSDEV
916 tristate '"physdev" match support'
917 depends on BRIDGE && BRIDGE_NETFILTER
918 depends on NETFILTER_ADVANCED
920 Physdev packet matching matches against the physical bridge ports
921 the IP packet arrived on or will leave by.
923 To compile it as a module, choose M here. If unsure, say N.
925 config NETFILTER_XT_MATCH_PKTTYPE
926 tristate '"pkttype" packet type match support'
927 depends on NETFILTER_ADVANCED
929 Packet type matching allows you to match a packet by
930 its "class", eg. BROADCAST, MULTICAST, ...
933 iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG
935 To compile it as a module, choose M here. If unsure, say N.
937 config NETFILTER_XT_MATCH_QUOTA
938 tristate '"quota" match support'
939 depends on NETFILTER_ADVANCED
941 This option adds a `quota' match, which allows to match on a
944 If you want to compile it as a module, say M here and read
945 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
947 config NETFILTER_XT_MATCH_RATEEST
948 tristate '"rateest" match support'
949 depends on NETFILTER_ADVANCED
950 select NETFILTER_XT_TARGET_RATEEST
952 This option adds a `rateest' match, which allows to match on the
953 rate estimated by the RATEEST target.
955 To compile it as a module, choose M here. If unsure, say N.
957 config NETFILTER_XT_MATCH_REALM
958 tristate '"realm" match support'
959 depends on NETFILTER_ADVANCED
960 select IP_ROUTE_CLASSID
962 This option adds a `realm' match, which allows you to use the realm
963 key from the routing subsystem inside iptables.
965 This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option
968 If you want to compile it as a module, say M here and read
969 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
971 config NETFILTER_XT_MATCH_RECENT
972 tristate '"recent" match support'
973 depends on NETFILTER_ADVANCED
975 This match is used for creating one or many lists of recently
976 used addresses and then matching against that/those list(s).
978 Short options are available by using 'iptables -m recent -h'
979 Official Website: <http://snowman.net/projects/ipt_recent/>
981 config NETFILTER_XT_MATCH_SCTP
982 tristate '"sctp" protocol match support (EXPERIMENTAL)'
983 depends on EXPERIMENTAL
984 depends on NETFILTER_ADVANCED
987 With this option enabled, you will be able to use the
988 `sctp' match in order to match on SCTP source/destination ports
989 and SCTP chunk types.
991 If you want to compile it as a module, say M here and read
992 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
994 config NETFILTER_XT_MATCH_SOCKET
995 tristate '"socket" match support (EXPERIMENTAL)'
996 depends on EXPERIMENTAL
997 depends on NETFILTER_TPROXY
998 depends on NETFILTER_XTABLES
999 depends on NETFILTER_ADVANCED
1000 depends on !NF_CONNTRACK || NF_CONNTRACK
1001 select NF_DEFRAG_IPV4
1002 select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES
1004 This option adds a `socket' match, which can be used to match
1005 packets for which a TCP or UDP socket lookup finds a valid socket.
1006 It can be used in combination with the MARK target and policy
1007 routing to implement full featured non-locally bound sockets.
1009 To compile it as a module, choose M here. If unsure, say N.
1011 config NETFILTER_XT_MATCH_STATE
1012 tristate '"state" match support'
1013 depends on NF_CONNTRACK
1014 default m if NETFILTER_ADVANCED=n
1016 Connection state matching allows you to match packets based on their
1017 relationship to a tracked connection (ie. previous packets). This
1018 is a powerful tool for packet classification.
1020 To compile it as a module, choose M here. If unsure, say N.
1022 config NETFILTER_XT_MATCH_STATISTIC
1023 tristate '"statistic" match support'
1024 depends on NETFILTER_ADVANCED
1026 This option adds a `statistic' match, which allows you to match
1027 on packets periodically or randomly with a given percentage.
1029 To compile it as a module, choose M here. If unsure, say N.
1031 config NETFILTER_XT_MATCH_STRING
1032 tristate '"string" match support'
1033 depends on NETFILTER_ADVANCED
1035 select TEXTSEARCH_KMP
1036 select TEXTSEARCH_BM
1037 select TEXTSEARCH_FSM
1039 This option adds a `string' match, which allows you to look for
1040 pattern matchings in packets.
1042 To compile it as a module, choose M here. If unsure, say N.
1044 config NETFILTER_XT_MATCH_TCPMSS
1045 tristate '"tcpmss" match support'
1046 depends on NETFILTER_ADVANCED
1048 This option adds a `tcpmss' match, which allows you to examine the
1049 MSS value of TCP SYN packets, which control the maximum packet size
1050 for that connection.
1052 To compile it as a module, choose M here. If unsure, say N.
1054 config NETFILTER_XT_MATCH_TIME
1055 tristate '"time" match support'
1056 depends on NETFILTER_ADVANCED
1058 This option adds a "time" match, which allows you to match based on
1059 the packet arrival time (at the machine which netfilter is running)
1060 on) or departure time/date (for locally generated packets).
1062 If you say Y here, try `iptables -m time --help` for
1065 If you want to compile it as a module, say M here.
1068 config NETFILTER_XT_MATCH_U32
1069 tristate '"u32" match support'
1070 depends on NETFILTER_ADVANCED
1072 u32 allows you to extract quantities of up to 4 bytes from a packet,
1073 AND them with specified masks, shift them by specified amounts and
1074 test whether the results are in any of a set of specified ranges.
1075 The specification of what to extract is general enough to skip over
1076 headers with lengths stored in the packet, as in IP or TCP header
1079 Details and examples are in the kernel module source.
1081 endif # NETFILTER_XTABLES
1085 source "net/netfilter/ipset/Kconfig"
1087 source "net/netfilter/ipvs/Kconfig"