1 menu "Core Netfilter Configuration"
2 depends on NET && INET && NETFILTER
4 config NETFILTER_NETLINK
7 config NETFILTER_NETLINK_ACCT
8 tristate "Netfilter NFACCT 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 extended accounting via NFNETLINK.
15 config NETFILTER_NETLINK_QUEUE
16 tristate "Netfilter NFQUEUE over NFNETLINK interface"
17 depends on NETFILTER_ADVANCED
18 select NETFILTER_NETLINK
20 If this option is enabled, the kernel will include support
21 for queueing packets via NFNETLINK.
23 config NETFILTER_NETLINK_LOG
24 tristate "Netfilter LOG over NFNETLINK interface"
25 default m if NETFILTER_ADVANCED=n
26 select NETFILTER_NETLINK
28 If this option is enabled, the kernel will include support
29 for logging packets via NFNETLINK.
31 This obsoletes the existing ipt_ULOG and ebg_ulog mechanisms,
32 and is also scheduled to replace the old syslog-based ipt_LOG
36 tristate "Netfilter connection tracking support"
37 default m if NETFILTER_ADVANCED=n
39 Connection tracking keeps a record of what packets have passed
40 through your machine, in order to figure out how they are related
43 This is required to do Masquerading or other kinds of Network
44 Address Translation. It can also be used to enhance packet
45 filtering (see `Connection state match support' below).
47 To compile it as a module, choose M here. If unsure, say N.
51 config NF_CONNTRACK_MARK
52 bool 'Connection mark tracking support'
53 depends on NETFILTER_ADVANCED
55 This option enables support for connection marks, used by the
56 `CONNMARK' target and `connmark' match. Similar to the mark value
57 of packets, but this mark value is kept in the conntrack session
58 instead of the individual packets.
60 config NF_CONNTRACK_SECMARK
61 bool 'Connection tracking security mark support'
62 depends on NETWORK_SECMARK
63 default m if NETFILTER_ADVANCED=n
65 This option enables security markings to be applied to
66 connections. Typically they are copied to connections from
67 packets using the CONNSECMARK target and copied back from
68 connections to packets with the same target, with the packets
69 being originally labeled via SECMARK.
73 config NF_CONNTRACK_ZONES
74 bool 'Connection tracking zones'
75 depends on NETFILTER_ADVANCED
76 depends on NETFILTER_XT_TARGET_CT
78 This option enables support for connection tracking zones.
79 Normally, each connection needs to have a unique system wide
80 identity. Connection tracking zones allow to have multiple
81 connections using the same identity, as long as they are
82 contained in different zones.
86 config NF_CONNTRACK_EVENTS
87 bool "Connection tracking events"
88 depends on NETFILTER_ADVANCED
90 If this option is enabled, the connection tracking code will
91 provide a notifier chain that can be used by other kernel code
92 to get notified about changes in the connection tracking state.
96 config NF_CONNTRACK_TIMESTAMP
97 bool 'Connection tracking timestamping'
98 depends on NETFILTER_ADVANCED
100 This option enables support for connection tracking timestamping.
101 This allows you to store the flow start-time and to obtain
102 the flow-stop time (once it has been destroyed) via Connection
107 config NF_CT_PROTO_DCCP
108 tristate 'DCCP protocol connection tracking support (EXPERIMENTAL)'
109 depends on EXPERIMENTAL
110 depends on NETFILTER_ADVANCED
113 With this option enabled, the layer 3 independent connection
114 tracking code will be able to do state tracking on DCCP connections.
118 config NF_CT_PROTO_GRE
121 config NF_CT_PROTO_SCTP
122 tristate 'SCTP protocol connection tracking support (EXPERIMENTAL)'
123 depends on EXPERIMENTAL
124 depends on NETFILTER_ADVANCED
127 With this option enabled, the layer 3 independent connection
128 tracking code will be able to do state tracking on SCTP connections.
130 If you want to compile it as a module, say M here and read
131 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
133 config NF_CT_PROTO_UDPLITE
134 tristate 'UDP-Lite protocol connection tracking support'
135 depends on NETFILTER_ADVANCED
137 With this option enabled, the layer 3 independent connection
138 tracking code will be able to do state tracking on UDP-Lite
141 To compile it as a module, choose M here. If unsure, say N.
143 config NF_CONNTRACK_AMANDA
144 tristate "Amanda backup protocol support"
145 depends on NETFILTER_ADVANCED
147 select TEXTSEARCH_KMP
149 If you are running the Amanda backup package <http://www.amanda.org/>
150 on this machine or machines that will be MASQUERADED through this
151 machine, then you may want to enable this feature. This allows the
152 connection tracking and natting code to allow the sub-channels that
153 Amanda requires for communication of the backup data, messages and
156 To compile it as a module, choose M here. If unsure, say N.
158 config NF_CONNTRACK_FTP
159 tristate "FTP protocol support"
160 default m if NETFILTER_ADVANCED=n
162 Tracking FTP connections is problematic: special helpers are
163 required for tracking them, and doing masquerading and other forms
164 of Network Address Translation on them.
166 This is FTP support on Layer 3 independent connection tracking.
167 Layer 3 independent connection tracking is experimental scheme
168 which generalize ip_conntrack to support other layer 3 protocols.
170 To compile it as a module, choose M here. If unsure, say N.
172 config NF_CONNTRACK_H323
173 tristate "H.323 protocol support"
174 depends on (IPV6 || IPV6=n)
175 depends on NETFILTER_ADVANCED
177 H.323 is a VoIP signalling protocol from ITU-T. As one of the most
178 important VoIP protocols, it is widely used by voice hardware and
179 software including voice gateways, IP phones, Netmeeting, OpenPhone,
182 With this module you can support H.323 on a connection tracking/NAT
185 This module supports RAS, Fast Start, H.245 Tunnelling, Call
186 Forwarding, RTP/RTCP and T.120 based audio, video, fax, chat,
187 whiteboard, file transfer, etc. For more information, please
188 visit http://nath323.sourceforge.net/.
190 To compile it as a module, choose M here. If unsure, say N.
192 config NF_CONNTRACK_IRC
193 tristate "IRC protocol support"
194 default m if NETFILTER_ADVANCED=n
196 There is a commonly-used extension to IRC called
197 Direct Client-to-Client Protocol (DCC). This enables users to send
198 files to each other, and also chat to each other without the need
199 of a server. DCC Sending is used anywhere you send files over IRC,
200 and DCC Chat is most commonly used by Eggdrop bots. If you are
201 using NAT, this extension will enable you to send files and initiate
202 chats. Note that you do NOT need this extension to get files or
203 have others initiate chats, or everything else in IRC.
205 To compile it as a module, choose M here. If unsure, say N.
207 config NF_CONNTRACK_BROADCAST
210 config NF_CONNTRACK_NETBIOS_NS
211 tristate "NetBIOS name service protocol support"
212 select NF_CONNTRACK_BROADCAST
214 NetBIOS name service requests are sent as broadcast messages from an
215 unprivileged port and responded to with unicast messages to the
216 same port. This make them hard to firewall properly because connection
217 tracking doesn't deal with broadcasts. This helper tracks locally
218 originating NetBIOS name service requests and the corresponding
219 responses. It relies on correct IP address configuration, specifically
220 netmask and broadcast address. When properly configured, the output
221 of "ip address show" should look similar to this:
223 $ ip -4 address show eth0
224 4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
225 inet 172.16.2.252/24 brd 172.16.2.255 scope global eth0
227 To compile it as a module, choose M here. If unsure, say N.
229 config NF_CONNTRACK_SNMP
230 tristate "SNMP service protocol support"
231 depends on NETFILTER_ADVANCED
232 select NF_CONNTRACK_BROADCAST
234 SNMP service requests are sent as broadcast messages from an
235 unprivileged port and responded to with unicast messages to the
236 same port. This make them hard to firewall properly because connection
237 tracking doesn't deal with broadcasts. This helper tracks locally
238 originating SNMP service requests and the corresponding
239 responses. It relies on correct IP address configuration, specifically
240 netmask and broadcast address.
242 To compile it as a module, choose M here. If unsure, say N.
244 config NF_CONNTRACK_PPTP
245 tristate "PPtP protocol support"
246 depends on NETFILTER_ADVANCED
247 select NF_CT_PROTO_GRE
249 This module adds support for PPTP (Point to Point Tunnelling
250 Protocol, RFC2637) connection tracking and NAT.
252 If you are running PPTP sessions over a stateful firewall or NAT
253 box, you may want to enable this feature.
255 Please note that not all PPTP modes of operation are supported yet.
256 Specifically these limitations exist:
257 - Blindly assumes that control connections are always established
258 in PNS->PAC direction. This is a violation of RFC2637.
259 - Only supports a single call within each session
261 To compile it as a module, choose M here. If unsure, say N.
263 config NF_CONNTRACK_SANE
264 tristate "SANE protocol support (EXPERIMENTAL)"
265 depends on EXPERIMENTAL
266 depends on NETFILTER_ADVANCED
268 SANE is a protocol for remote access to scanners as implemented
269 by the 'saned' daemon. Like FTP, it uses separate control and
272 With this module you can support SANE on a connection tracking
275 To compile it as a module, choose M here. If unsure, say N.
277 config NF_CONNTRACK_SIP
278 tristate "SIP protocol support"
279 default m if NETFILTER_ADVANCED=n
281 SIP is an application-layer control protocol that can establish,
282 modify, and terminate multimedia sessions (conferences) such as
283 Internet telephony calls. With the ip_conntrack_sip and
284 the nf_nat_sip modules you can support the protocol on a connection
285 tracking/NATing firewall.
287 To compile it as a module, choose M here. If unsure, say N.
289 config NF_CONNTRACK_TFTP
290 tristate "TFTP protocol support"
291 depends on NETFILTER_ADVANCED
293 TFTP connection tracking helper, this is required depending
294 on how restrictive your ruleset is.
295 If you are using a tftp client behind -j SNAT or -j MASQUERADING
298 To compile it as a module, choose M here. If unsure, say N.
301 tristate 'Connection tracking netlink interface'
302 select NETFILTER_NETLINK
303 default m if NETFILTER_ADVANCED=n
305 This option enables support for a netlink-based userspace interface
309 # transparent proxy support
310 config NETFILTER_TPROXY
311 tristate "Transparent proxying support (EXPERIMENTAL)"
312 depends on EXPERIMENTAL
313 depends on IP_NF_MANGLE
314 depends on NETFILTER_ADVANCED
316 This option enables transparent proxying support, that is,
317 support for handling non-locally bound IPv4 TCP and UDP sockets.
318 For it to work you will have to configure certain iptables rules
319 and use policy routing. For more information on how to set it up
320 see Documentation/networking/tproxy.txt.
322 To compile it as a module, choose M here. If unsure, say N.
324 config NETFILTER_XTABLES
325 tristate "Netfilter Xtables support (required for ip_tables)"
326 default m if NETFILTER_ADVANCED=n
328 This is required if you intend to use any of ip_tables,
329 ip6_tables or arp_tables.
333 comment "Xtables combined modules"
335 config NETFILTER_XT_MARK
336 tristate 'nfmark target and match support'
337 default m if NETFILTER_ADVANCED=n
339 This option adds the "MARK" target and "mark" match.
341 Netfilter mark matching allows you to match packets based on the
342 "nfmark" value in the packet.
343 The target allows you to create rules in the "mangle" table which alter
344 the netfilter mark (nfmark) field associated with the packet.
346 Prior to routing, the nfmark can influence the routing method (see
347 "Use netfilter MARK value as routing key") and can also be used by
348 other subsystems to change their behavior.
350 config NETFILTER_XT_CONNMARK
351 tristate 'ctmark target and match support'
352 depends on NF_CONNTRACK
353 depends on NETFILTER_ADVANCED
354 select NF_CONNTRACK_MARK
356 This option adds the "CONNMARK" target and "connmark" match.
358 Netfilter allows you to store a mark value per connection (a.k.a.
359 ctmark), similarly to the packet mark (nfmark). Using this
360 target and match, you can set and match on this mark.
362 config NETFILTER_XT_SET
363 tristate 'set target and match support'
365 depends on NETFILTER_ADVANCED
367 This option adds the "SET" target and "set" match.
369 Using this target and match, you can add/delete and match
370 elements in the sets created by ipset(8).
372 To compile it as a module, choose M here. If unsure, say N.
374 # alphabetically ordered list of targets
376 comment "Xtables targets"
378 config NETFILTER_XT_TARGET_AUDIT
379 tristate "AUDIT target support"
381 depends on NETFILTER_ADVANCED
383 This option adds a 'AUDIT' target, which can be used to create
384 audit records for packets dropped/accepted.
386 To compileit as a module, choose M here. If unsure, say N.
388 config NETFILTER_XT_TARGET_CHECKSUM
389 tristate "CHECKSUM target support"
390 depends on IP_NF_MANGLE || IP6_NF_MANGLE
391 depends on NETFILTER_ADVANCED
393 This option adds a `CHECKSUM' target, which can be used in the iptables mangle
396 You can use this target to compute and fill in the checksum in
397 a packet that lacks a checksum. This is particularly useful,
398 if you need to work around old applications such as dhcp clients,
399 that do not work well with checksum offloads, but don't want to disable
400 checksum offload in your device.
402 To compile it as a module, choose M here. If unsure, say N.
404 config NETFILTER_XT_TARGET_CLASSIFY
405 tristate '"CLASSIFY" target support'
406 depends on NETFILTER_ADVANCED
408 This option adds a `CLASSIFY' target, which enables the user to set
409 the priority of a packet. Some qdiscs can use this value for
410 classification, among these are:
412 atm, cbq, dsmark, pfifo_fast, htb, prio
414 To compile it as a module, choose M here. If unsure, say N.
416 config NETFILTER_XT_TARGET_CONNMARK
417 tristate '"CONNMARK" target support'
418 depends on NF_CONNTRACK
419 depends on NETFILTER_ADVANCED
420 select NETFILTER_XT_CONNMARK
422 This is a backwards-compat option for the user's convenience
423 (e.g. when running oldconfig). It selects
424 CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
426 config NETFILTER_XT_TARGET_CONNSECMARK
427 tristate '"CONNSECMARK" target support'
428 depends on NF_CONNTRACK && NF_CONNTRACK_SECMARK
429 default m if NETFILTER_ADVANCED=n
431 The CONNSECMARK target copies security markings from packets
432 to connections, and restores security markings from connections
433 to packets (if the packets are not already marked). This would
434 normally be used in conjunction with the SECMARK target.
436 To compile it as a module, choose M here. If unsure, say N.
438 config NETFILTER_XT_TARGET_CT
439 tristate '"CT" target support'
440 depends on NF_CONNTRACK
441 depends on IP_NF_RAW || IP6_NF_RAW
442 depends on NETFILTER_ADVANCED
444 This options adds a `CT' target, which allows to specify initial
445 connection tracking parameters like events to be delivered and
446 the helper to be used.
448 To compile it as a module, choose M here. If unsure, say N.
450 config NETFILTER_XT_TARGET_DSCP
451 tristate '"DSCP" and "TOS" target support'
452 depends on IP_NF_MANGLE || IP6_NF_MANGLE
453 depends on NETFILTER_ADVANCED
455 This option adds a `DSCP' target, which allows you to manipulate
456 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
458 The DSCP field can have any value between 0x0 and 0x3f inclusive.
460 It also adds the "TOS" target, which allows you to create rules in
461 the "mangle" table which alter the Type Of Service field of an IPv4
462 or the Priority field of an IPv6 packet, prior to routing.
464 To compile it as a module, choose M here. If unsure, say N.
466 config NETFILTER_XT_TARGET_HL
467 tristate '"HL" hoplimit target support'
468 depends on IP_NF_MANGLE || IP6_NF_MANGLE
469 depends on NETFILTER_ADVANCED
471 This option adds the "HL" (for IPv6) and "TTL" (for IPv4)
472 targets, which enable the user to change the
473 hoplimit/time-to-live value of the IP header.
475 While it is safe to decrement the hoplimit/TTL value, the
476 modules also allow to increment and set the hoplimit value of
477 the header to arbitrary values. This is EXTREMELY DANGEROUS
478 since you can easily create immortal packets that loop
479 forever on the network.
481 config NETFILTER_XT_TARGET_IDLETIMER
482 tristate "IDLETIMER target support"
483 depends on NETFILTER_ADVANCED
486 This option adds the `IDLETIMER' target. Each matching packet
487 resets the timer associated with label specified when the rule is
488 added. When the timer expires, it triggers a sysfs notification.
489 The remaining time for expiration can be read via sysfs.
491 To compile it as a module, choose M here. If unsure, say N.
493 config NETFILTER_XT_TARGET_LED
494 tristate '"LED" target support'
495 depends on LEDS_CLASS && LEDS_TRIGGERS
496 depends on NETFILTER_ADVANCED
498 This option adds a `LED' target, which allows you to blink LEDs in
499 response to particular packets passing through your machine.
501 This can be used to turn a spare LED into a network activity LED,
502 which only flashes in response to FTP transfers, for example. Or
503 you could have an LED which lights up for a minute or two every time
504 somebody connects to your machine via SSH.
506 You will need support for the "led" class to make this work.
508 To create an LED trigger for incoming SSH traffic:
509 iptables -A INPUT -p tcp --dport 22 -j LED --led-trigger-id ssh --led-delay 1000
511 Then attach the new trigger to an LED on your system:
512 echo netfilter-ssh > /sys/class/leds/<ledname>/trigger
514 For more information on the LEDs available on your system, see
515 Documentation/leds/leds-class.txt
517 config NETFILTER_XT_TARGET_MARK
518 tristate '"MARK" target support'
519 depends on NETFILTER_ADVANCED
520 select NETFILTER_XT_MARK
522 This is a backwards-compat option for the user's convenience
523 (e.g. when running oldconfig). It selects
524 CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
526 config NETFILTER_XT_TARGET_NFLOG
527 tristate '"NFLOG" target support'
528 default m if NETFILTER_ADVANCED=n
529 select NETFILTER_NETLINK_LOG
531 This option enables the NFLOG target, which allows to LOG
532 messages through nfnetlink_log.
534 To compile it as a module, choose M here. If unsure, say N.
536 config NETFILTER_XT_TARGET_NFQUEUE
537 tristate '"NFQUEUE" target Support'
538 depends on NETFILTER_ADVANCED
539 select NETFILTER_NETLINK_QUEUE
541 This target replaced the old obsolete QUEUE target.
543 As opposed to QUEUE, it supports 65535 different queues,
546 To compile it as a module, choose M here. If unsure, say N.
548 config NETFILTER_XT_TARGET_NOTRACK
549 tristate '"NOTRACK" target support'
550 depends on IP_NF_RAW || IP6_NF_RAW
551 depends on NF_CONNTRACK
553 The NOTRACK target allows a select rule to specify
554 which packets *not* to enter the conntrack/NAT
555 subsystem with all the consequences (no ICMP error tracking,
556 no protocol helpers for the selected packets).
558 If you want to compile it as a module, say M here and read
559 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
561 config NETFILTER_XT_TARGET_RATEEST
562 tristate '"RATEEST" target support'
563 depends on NETFILTER_ADVANCED
565 This option adds a `RATEEST' target, which allows to measure
566 rates similar to TC estimators. The `rateest' match can be
567 used to match on the measured rates.
569 To compile it as a module, choose M here. If unsure, say N.
571 config NETFILTER_XT_TARGET_TEE
572 tristate '"TEE" - packet cloning to alternate destination'
573 depends on NETFILTER_ADVANCED
574 depends on (IPV6 || IPV6=n)
575 depends on !NF_CONNTRACK || NF_CONNTRACK
577 This option adds a "TEE" target with which a packet can be cloned and
578 this clone be rerouted to another nexthop.
580 config NETFILTER_XT_TARGET_TPROXY
581 tristate '"TPROXY" target support (EXPERIMENTAL)'
582 depends on EXPERIMENTAL
583 depends on NETFILTER_TPROXY
584 depends on NETFILTER_XTABLES
585 depends on NETFILTER_ADVANCED
586 select NF_DEFRAG_IPV4
587 select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES
589 This option adds a `TPROXY' target, which is somewhat similar to
590 REDIRECT. It can only be used in the mangle table and is useful
591 to redirect traffic to a transparent proxy. It does _not_ depend
592 on Netfilter connection tracking and NAT, unlike REDIRECT.
594 To compile it as a module, choose M here. If unsure, say N.
596 config NETFILTER_XT_TARGET_TRACE
597 tristate '"TRACE" target support'
598 depends on IP_NF_RAW || IP6_NF_RAW
599 depends on NETFILTER_ADVANCED
601 The TRACE target allows you to mark packets so that the kernel
602 will log every rule which match the packets as those traverse
603 the tables, chains, rules.
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_TARGET_SECMARK
609 tristate '"SECMARK" target support'
610 depends on NETWORK_SECMARK
611 default m if NETFILTER_ADVANCED=n
613 The SECMARK target allows security marking of network
614 packets, for use with security subsystems.
616 To compile it as a module, choose M here. If unsure, say N.
618 config NETFILTER_XT_TARGET_TCPMSS
619 tristate '"TCPMSS" target support'
620 depends on (IPV6 || IPV6=n)
621 default m if NETFILTER_ADVANCED=n
623 This option adds a `TCPMSS' target, which allows you to alter the
624 MSS value of TCP SYN packets, to control the maximum size for that
625 connection (usually limiting it to your outgoing interface's MTU
628 This is used to overcome criminally braindead ISPs or servers which
629 block ICMP Fragmentation Needed packets. The symptoms of this
630 problem are that everything works fine from your Linux
631 firewall/router, but machines behind it can never exchange large
633 1) Web browsers connect, then hang with no data received.
634 2) Small mail works fine, but large emails hang.
635 3) ssh works fine, but scp hangs after initial handshaking.
637 Workaround: activate this option and add a rule to your firewall
640 iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
641 -j TCPMSS --clamp-mss-to-pmtu
643 To compile it as a module, choose M here. If unsure, say N.
645 config NETFILTER_XT_TARGET_TCPOPTSTRIP
646 tristate '"TCPOPTSTRIP" target support (EXPERIMENTAL)'
647 depends on EXPERIMENTAL
648 depends on IP_NF_MANGLE || IP6_NF_MANGLE
649 depends on NETFILTER_ADVANCED
651 This option adds a "TCPOPTSTRIP" target, which allows you to strip
652 TCP options from TCP packets.
654 # alphabetically ordered list of matches
656 comment "Xtables matches"
658 config NETFILTER_XT_MATCH_ADDRTYPE
659 tristate '"addrtype" address type match support'
660 depends on NETFILTER_ADVANCED
662 This option allows you to match what routing thinks of an address,
663 eg. UNICAST, LOCAL, BROADCAST, ...
665 If you want to compile it as a module, say M here and read
666 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
668 config NETFILTER_XT_MATCH_CLUSTER
669 tristate '"cluster" match support'
670 depends on NF_CONNTRACK
671 depends on NETFILTER_ADVANCED
673 This option allows you to build work-load-sharing clusters of
674 network servers/stateful firewalls without having a dedicated
675 load-balancing router/server/switch. Basically, this match returns
676 true when the packet must be handled by this cluster node. Thus,
677 all nodes see all packets and this match decides which node handles
678 what packets. The work-load sharing algorithm is based on source
681 If you say Y or M here, try `iptables -m cluster --help` for
684 config NETFILTER_XT_MATCH_COMMENT
685 tristate '"comment" match support'
686 depends on NETFILTER_ADVANCED
688 This option adds a `comment' dummy-match, which allows you to put
689 comments in your iptables ruleset.
691 If you want to compile it as a module, say M here and read
692 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
694 config NETFILTER_XT_MATCH_CONNBYTES
695 tristate '"connbytes" per-connection counter match support'
696 depends on NF_CONNTRACK
697 depends on NETFILTER_ADVANCED
699 This option adds a `connbytes' match, which allows you to match the
700 number of bytes and/or packets for each direction within a connection.
702 If you want to compile it as a module, say M here and read
703 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
705 config NETFILTER_XT_MATCH_CONNLIMIT
706 tristate '"connlimit" match support"'
707 depends on NF_CONNTRACK
708 depends on NETFILTER_ADVANCED
710 This match allows you to match against the number of parallel
711 connections to a server per client IP address (or address block).
713 config NETFILTER_XT_MATCH_CONNMARK
714 tristate '"connmark" connection mark match support'
715 depends on NF_CONNTRACK
716 depends on NETFILTER_ADVANCED
717 select NETFILTER_XT_CONNMARK
719 This is a backwards-compat option for the user's convenience
720 (e.g. when running oldconfig). It selects
721 CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
723 config NETFILTER_XT_MATCH_CONNTRACK
724 tristate '"conntrack" connection tracking match support'
725 depends on NF_CONNTRACK
726 default m if NETFILTER_ADVANCED=n
728 This is a general conntrack match module, a superset of the state match.
730 It allows matching on additional conntrack information, which is
731 useful in complex configurations, such as NAT gateways with multiple
732 internet links or tunnels.
734 To compile it as a module, choose M here. If unsure, say N.
736 config NETFILTER_XT_MATCH_CPU
737 tristate '"cpu" match support'
738 depends on NETFILTER_ADVANCED
740 CPU matching allows you to match packets based on the CPU
741 currently handling the packet.
743 To compile it as a module, choose M here. If unsure, say N.
745 config NETFILTER_XT_MATCH_DCCP
746 tristate '"dccp" protocol match support'
747 depends on NETFILTER_ADVANCED
750 With this option enabled, you will be able to use the iptables
751 `dccp' match in order to match on DCCP source/destination ports
754 If you want to compile it as a module, say M here and read
755 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
757 config NETFILTER_XT_MATCH_DEVGROUP
758 tristate '"devgroup" match support'
759 depends on NETFILTER_ADVANCED
761 This options adds a `devgroup' match, which allows to match on the
762 device group a network device is assigned to.
764 To compile it as a module, choose M here. If unsure, say N.
766 config NETFILTER_XT_MATCH_DSCP
767 tristate '"dscp" and "tos" match support'
768 depends on NETFILTER_ADVANCED
770 This option adds a `DSCP' match, which allows you to match against
771 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
773 The DSCP field can have any value between 0x0 and 0x3f inclusive.
775 It will also add a "tos" match, which allows you to match packets
776 based on the Type Of Service fields of the IPv4 packet (which share
777 the same bits as DSCP).
779 To compile it as a module, choose M here. If unsure, say N.
781 config NETFILTER_XT_MATCH_ECN
782 tristate '"ecn" match support'
783 depends on NETFILTER_ADVANCED
785 This option adds an "ECN" match, which allows you to match against
786 the IPv4 and TCP header ECN fields.
788 To compile it as a module, choose M here. If unsure, say N.
790 config NETFILTER_XT_MATCH_ESP
791 tristate '"esp" match support'
792 depends on NETFILTER_ADVANCED
794 This match extension allows you to match a range of SPIs
795 inside ESP header of IPSec packets.
797 To compile it as a module, choose M here. If unsure, say N.
799 config NETFILTER_XT_MATCH_HASHLIMIT
800 tristate '"hashlimit" match support'
801 depends on (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
802 depends on NETFILTER_ADVANCED
804 This option adds a `hashlimit' match.
806 As opposed to `limit', this match dynamically creates a hash table
807 of limit buckets, based on your selection of source/destination
808 addresses and/or ports.
810 It enables you to express policies like `10kpps for any given
811 destination address' or `500pps from any given source address'
814 config NETFILTER_XT_MATCH_HELPER
815 tristate '"helper" match support'
816 depends on NF_CONNTRACK
817 depends on NETFILTER_ADVANCED
819 Helper matching allows you to match packets in dynamic connections
820 tracked by a conntrack-helper, ie. ip_conntrack_ftp
822 To compile it as a module, choose M here. If unsure, say Y.
824 config NETFILTER_XT_MATCH_HL
825 tristate '"hl" hoplimit/TTL match support'
826 depends on NETFILTER_ADVANCED
828 HL matching allows you to match packets based on the hoplimit
829 in the IPv6 header, or the time-to-live field in the IPv4
830 header of the packet.
832 config NETFILTER_XT_MATCH_IPRANGE
833 tristate '"iprange" address range match support'
834 depends on NETFILTER_ADVANCED
836 This option adds a "iprange" match, which allows you to match based on
837 an IP address range. (Normal iptables only matches on single addresses
838 with an optional mask.)
842 config NETFILTER_XT_MATCH_IPVS
843 tristate '"ipvs" match support'
845 depends on NETFILTER_ADVANCED
846 depends on NF_CONNTRACK
848 This option allows you to match against IPVS properties of a packet.
852 config NETFILTER_XT_MATCH_LENGTH
853 tristate '"length" match support'
854 depends on NETFILTER_ADVANCED
856 This option allows you to match the length of a packet against a
857 specific value or range of values.
859 To compile it as a module, choose M here. If unsure, say N.
861 config NETFILTER_XT_MATCH_LIMIT
862 tristate '"limit" match support'
863 depends on NETFILTER_ADVANCED
865 limit matching allows you to control the rate at which a rule can be
866 matched: mainly useful in combination with the LOG target ("LOG
867 target support", below) and to avoid some Denial of Service attacks.
869 To compile it as a module, choose M here. If unsure, say N.
871 config NETFILTER_XT_MATCH_MAC
872 tristate '"mac" address match support'
873 depends on NETFILTER_ADVANCED
875 MAC matching allows you to match packets based on the source
876 Ethernet address of the packet.
878 To compile it as a module, choose M here. If unsure, say N.
880 config NETFILTER_XT_MATCH_MARK
881 tristate '"mark" match support'
882 depends on NETFILTER_ADVANCED
883 select NETFILTER_XT_MARK
885 This is a backwards-compat option for the user's convenience
886 (e.g. when running oldconfig). It selects
887 CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
889 config NETFILTER_XT_MATCH_MULTIPORT
890 tristate '"multiport" Multiple port match support'
891 depends on NETFILTER_ADVANCED
893 Multiport matching allows you to match TCP or UDP packets based on
894 a series of source or destination ports: normally a rule can only
895 match a single range of ports.
897 To compile it as a module, choose M here. If unsure, say N.
899 config NETFILTER_XT_MATCH_NFACCT
900 tristate '"nfacct" match support'
901 default m if NETFILTER_ADVANCED=n
902 select NETFILTER_NETLINK_ACCT
904 This option allows you to use the extended accounting through
907 To compile it as a module, choose M here. If unsure, say N.
909 config NETFILTER_XT_MATCH_OSF
910 tristate '"osf" Passive OS fingerprint match'
911 depends on NETFILTER_ADVANCED && NETFILTER_NETLINK
913 This option selects the Passive OS Fingerprinting match module
914 that allows to passively match the remote operating system by
915 analyzing incoming TCP SYN packets.
917 Rules and loading software can be downloaded from
918 http://www.ioremap.net/projects/osf
920 To compile it as a module, choose M here. If unsure, say N.
922 config NETFILTER_XT_MATCH_OWNER
923 tristate '"owner" match support'
924 depends on NETFILTER_ADVANCED
926 Socket owner matching allows you to match locally-generated packets
927 based on who created the socket: the user or group. It is also
928 possible to check whether a socket actually exists.
930 config NETFILTER_XT_MATCH_POLICY
931 tristate 'IPsec "policy" match support'
933 default m if NETFILTER_ADVANCED=n
935 Policy matching allows you to match packets based on the
936 IPsec policy that was used during decapsulation/will
937 be used during encapsulation.
939 To compile it as a module, choose M here. If unsure, say N.
941 config NETFILTER_XT_MATCH_PHYSDEV
942 tristate '"physdev" match support'
943 depends on BRIDGE && BRIDGE_NETFILTER
944 depends on NETFILTER_ADVANCED
946 Physdev packet matching matches against the physical bridge ports
947 the IP packet arrived on or will leave by.
949 To compile it as a module, choose M here. If unsure, say N.
951 config NETFILTER_XT_MATCH_PKTTYPE
952 tristate '"pkttype" packet type match support'
953 depends on NETFILTER_ADVANCED
955 Packet type matching allows you to match a packet by
956 its "class", eg. BROADCAST, MULTICAST, ...
959 iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG
961 To compile it as a module, choose M here. If unsure, say N.
963 config NETFILTER_XT_MATCH_QUOTA
964 tristate '"quota" match support'
965 depends on NETFILTER_ADVANCED
967 This option adds a `quota' match, which allows to match on a
970 If you want to compile it as a module, say M here and read
971 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
973 config NETFILTER_XT_MATCH_RATEEST
974 tristate '"rateest" match support'
975 depends on NETFILTER_ADVANCED
976 select NETFILTER_XT_TARGET_RATEEST
978 This option adds a `rateest' match, which allows to match on the
979 rate estimated by the RATEEST target.
981 To compile it as a module, choose M here. If unsure, say N.
983 config NETFILTER_XT_MATCH_REALM
984 tristate '"realm" match support'
985 depends on NETFILTER_ADVANCED
986 select IP_ROUTE_CLASSID
988 This option adds a `realm' match, which allows you to use the realm
989 key from the routing subsystem inside iptables.
991 This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option
994 If you want to compile it as a module, say M here and read
995 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
997 config NETFILTER_XT_MATCH_RECENT
998 tristate '"recent" match support'
999 depends on NETFILTER_ADVANCED
1001 This match is used for creating one or many lists of recently
1002 used addresses and then matching against that/those list(s).
1004 Short options are available by using 'iptables -m recent -h'
1005 Official Website: <http://snowman.net/projects/ipt_recent/>
1007 config NETFILTER_XT_MATCH_SCTP
1008 tristate '"sctp" protocol match support (EXPERIMENTAL)'
1009 depends on EXPERIMENTAL
1010 depends on NETFILTER_ADVANCED
1013 With this option enabled, you will be able to use the
1014 `sctp' match in order to match on SCTP source/destination ports
1015 and SCTP chunk types.
1017 If you want to compile it as a module, say M here and read
1018 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1020 config NETFILTER_XT_MATCH_SOCKET
1021 tristate '"socket" match support (EXPERIMENTAL)'
1022 depends on EXPERIMENTAL
1023 depends on NETFILTER_TPROXY
1024 depends on NETFILTER_XTABLES
1025 depends on NETFILTER_ADVANCED
1026 depends on !NF_CONNTRACK || NF_CONNTRACK
1027 select NF_DEFRAG_IPV4
1028 select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES
1030 This option adds a `socket' match, which can be used to match
1031 packets for which a TCP or UDP socket lookup finds a valid socket.
1032 It can be used in combination with the MARK target and policy
1033 routing to implement full featured non-locally bound sockets.
1035 To compile it as a module, choose M here. If unsure, say N.
1037 config NETFILTER_XT_MATCH_STATE
1038 tristate '"state" match support'
1039 depends on NF_CONNTRACK
1040 default m if NETFILTER_ADVANCED=n
1042 Connection state matching allows you to match packets based on their
1043 relationship to a tracked connection (ie. previous packets). This
1044 is a powerful tool for packet classification.
1046 To compile it as a module, choose M here. If unsure, say N.
1048 config NETFILTER_XT_MATCH_STATISTIC
1049 tristate '"statistic" match support'
1050 depends on NETFILTER_ADVANCED
1052 This option adds a `statistic' match, which allows you to match
1053 on packets periodically or randomly with a given percentage.
1055 To compile it as a module, choose M here. If unsure, say N.
1057 config NETFILTER_XT_MATCH_STRING
1058 tristate '"string" match support'
1059 depends on NETFILTER_ADVANCED
1061 select TEXTSEARCH_KMP
1062 select TEXTSEARCH_BM
1063 select TEXTSEARCH_FSM
1065 This option adds a `string' match, which allows you to look for
1066 pattern matchings in packets.
1068 To compile it as a module, choose M here. If unsure, say N.
1070 config NETFILTER_XT_MATCH_TCPMSS
1071 tristate '"tcpmss" match support'
1072 depends on NETFILTER_ADVANCED
1074 This option adds a `tcpmss' match, which allows you to examine the
1075 MSS value of TCP SYN packets, which control the maximum packet size
1076 for that connection.
1078 To compile it as a module, choose M here. If unsure, say N.
1080 config NETFILTER_XT_MATCH_TIME
1081 tristate '"time" match support'
1082 depends on NETFILTER_ADVANCED
1084 This option adds a "time" match, which allows you to match based on
1085 the packet arrival time (at the machine which netfilter is running)
1086 on) or departure time/date (for locally generated packets).
1088 If you say Y here, try `iptables -m time --help` for
1091 If you want to compile it as a module, say M here.
1094 config NETFILTER_XT_MATCH_U32
1095 tristate '"u32" match support'
1096 depends on NETFILTER_ADVANCED
1098 u32 allows you to extract quantities of up to 4 bytes from a packet,
1099 AND them with specified masks, shift them by specified amounts and
1100 test whether the results are in any of a set of specified ranges.
1101 The specification of what to extract is general enough to skip over
1102 headers with lengths stored in the packet, as in IP or TCP header
1105 Details and examples are in the kernel module source.
1107 endif # NETFILTER_XTABLES
1111 source "net/netfilter/ipset/Kconfig"
1113 source "net/netfilter/ipvs/Kconfig"