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_CT_PROTO_DCCP
89 tristate 'DCCP protocol connection tracking support (EXPERIMENTAL)'
90 depends on EXPERIMENTAL
91 depends on NETFILTER_ADVANCED
94 With this option enabled, the layer 3 independent connection
95 tracking code will be able to do state tracking on DCCP connections.
99 config NF_CT_PROTO_GRE
102 config NF_CT_PROTO_SCTP
103 tristate 'SCTP protocol connection tracking support (EXPERIMENTAL)'
104 depends on EXPERIMENTAL
105 depends on NETFILTER_ADVANCED
108 With this option enabled, the layer 3 independent connection
109 tracking code will be able to do state tracking on SCTP connections.
111 If you want to compile it as a module, say M here and read
112 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
114 config NF_CT_PROTO_UDPLITE
115 tristate 'UDP-Lite protocol connection tracking support'
116 depends on NETFILTER_ADVANCED
118 With this option enabled, the layer 3 independent connection
119 tracking code will be able to do state tracking on UDP-Lite
122 To compile it as a module, choose M here. If unsure, say N.
124 config NF_CONNTRACK_AMANDA
125 tristate "Amanda backup protocol support"
126 depends on NETFILTER_ADVANCED
128 select TEXTSEARCH_KMP
130 If you are running the Amanda backup package <http://www.amanda.org/>
131 on this machine or machines that will be MASQUERADED through this
132 machine, then you may want to enable this feature. This allows the
133 connection tracking and natting code to allow the sub-channels that
134 Amanda requires for communication of the backup data, messages and
137 To compile it as a module, choose M here. If unsure, say N.
139 config NF_CONNTRACK_FTP
140 tristate "FTP protocol support"
141 default m if NETFILTER_ADVANCED=n
143 Tracking FTP connections is problematic: special helpers are
144 required for tracking them, and doing masquerading and other forms
145 of Network Address Translation on them.
147 This is FTP support on Layer 3 independent connection tracking.
148 Layer 3 independent connection tracking is experimental scheme
149 which generalize ip_conntrack to support other layer 3 protocols.
151 To compile it as a module, choose M here. If unsure, say N.
153 config NF_CONNTRACK_H323
154 tristate "H.323 protocol support"
155 depends on (IPV6 || IPV6=n)
156 depends on NETFILTER_ADVANCED
158 H.323 is a VoIP signalling protocol from ITU-T. As one of the most
159 important VoIP protocols, it is widely used by voice hardware and
160 software including voice gateways, IP phones, Netmeeting, OpenPhone,
163 With this module you can support H.323 on a connection tracking/NAT
166 This module supports RAS, Fast Start, H.245 Tunnelling, Call
167 Forwarding, RTP/RTCP and T.120 based audio, video, fax, chat,
168 whiteboard, file transfer, etc. For more information, please
169 visit http://nath323.sourceforge.net/.
171 To compile it as a module, choose M here. If unsure, say N.
173 config NF_CONNTRACK_IRC
174 tristate "IRC protocol support"
175 default m if NETFILTER_ADVANCED=n
177 There is a commonly-used extension to IRC called
178 Direct Client-to-Client Protocol (DCC). This enables users to send
179 files to each other, and also chat to each other without the need
180 of a server. DCC Sending is used anywhere you send files over IRC,
181 and DCC Chat is most commonly used by Eggdrop bots. If you are
182 using NAT, this extension will enable you to send files and initiate
183 chats. Note that you do NOT need this extension to get files or
184 have others initiate chats, or everything else in IRC.
186 To compile it as a module, choose M here. If unsure, say N.
188 config NF_CONNTRACK_NETBIOS_NS
189 tristate "NetBIOS name service protocol support"
190 depends on NETFILTER_ADVANCED
192 NetBIOS name service requests are sent as broadcast messages from an
193 unprivileged port and responded to with unicast messages to the
194 same port. This make them hard to firewall properly because connection
195 tracking doesn't deal with broadcasts. This helper tracks locally
196 originating NetBIOS name service requests and the corresponding
197 responses. It relies on correct IP address configuration, specifically
198 netmask and broadcast address. When properly configured, the output
199 of "ip address show" should look similar to this:
201 $ ip -4 address show eth0
202 4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
203 inet 172.16.2.252/24 brd 172.16.2.255 scope global eth0
205 To compile it as a module, choose M here. If unsure, say N.
207 config NF_CONNTRACK_PPTP
208 tristate "PPtP protocol support"
209 depends on NETFILTER_ADVANCED
210 select NF_CT_PROTO_GRE
212 This module adds support for PPTP (Point to Point Tunnelling
213 Protocol, RFC2637) connection tracking and NAT.
215 If you are running PPTP sessions over a stateful firewall or NAT
216 box, you may want to enable this feature.
218 Please note that not all PPTP modes of operation are supported yet.
219 Specifically these limitations exist:
220 - Blindly assumes that control connections are always established
221 in PNS->PAC direction. This is a violation of RFC2637.
222 - Only supports a single call within each session
224 To compile it as a module, choose M here. If unsure, say N.
226 config NF_CONNTRACK_SANE
227 tristate "SANE protocol support (EXPERIMENTAL)"
228 depends on EXPERIMENTAL
229 depends on NETFILTER_ADVANCED
231 SANE is a protocol for remote access to scanners as implemented
232 by the 'saned' daemon. Like FTP, it uses separate control and
235 With this module you can support SANE on a connection tracking
238 To compile it as a module, choose M here. If unsure, say N.
240 config NF_CONNTRACK_SIP
241 tristate "SIP protocol support"
242 default m if NETFILTER_ADVANCED=n
244 SIP is an application-layer control protocol that can establish,
245 modify, and terminate multimedia sessions (conferences) such as
246 Internet telephony calls. With the ip_conntrack_sip and
247 the nf_nat_sip modules you can support the protocol on a connection
248 tracking/NATing firewall.
250 To compile it as a module, choose M here. If unsure, say N.
252 config NF_CONNTRACK_TFTP
253 tristate "TFTP protocol support"
254 depends on NETFILTER_ADVANCED
256 TFTP connection tracking helper, this is required depending
257 on how restrictive your ruleset is.
258 If you are using a tftp client behind -j SNAT or -j MASQUERADING
261 To compile it as a module, choose M here. If unsure, say N.
264 tristate 'Connection tracking netlink interface'
265 select NETFILTER_NETLINK
266 default m if NETFILTER_ADVANCED=n
268 This option enables support for a netlink-based userspace interface
272 # transparent proxy support
273 config NETFILTER_TPROXY
274 tristate "Transparent proxying support (EXPERIMENTAL)"
275 depends on EXPERIMENTAL
276 depends on IP_NF_MANGLE
277 depends on NETFILTER_ADVANCED
279 This option enables transparent proxying support, that is,
280 support for handling non-locally bound IPv4 TCP and UDP sockets.
281 For it to work you will have to configure certain iptables rules
282 and use policy routing. For more information on how to set it up
283 see Documentation/networking/tproxy.txt.
285 To compile it as a module, choose M here. If unsure, say N.
287 config NETFILTER_XTABLES
288 tristate "Netfilter Xtables support (required for ip_tables)"
289 default m if NETFILTER_ADVANCED=n
291 This is required if you intend to use any of ip_tables,
292 ip6_tables or arp_tables.
296 comment "Xtables combined modules"
298 config NETFILTER_XT_MARK
299 tristate 'nfmark target and match support'
300 default m if NETFILTER_ADVANCED=n
302 This option adds the "MARK" target and "mark" match.
304 Netfilter mark matching allows you to match packets based on the
305 "nfmark" value in the packet.
306 The target allows you to create rules in the "mangle" table which alter
307 the netfilter mark (nfmark) field associated with the packet.
309 Prior to routing, the nfmark can influence the routing method (see
310 "Use netfilter MARK value as routing key") and can also be used by
311 other subsystems to change their behavior.
313 config NETFILTER_XT_CONNMARK
314 tristate 'ctmark target and match support'
315 depends on NF_CONNTRACK
316 depends on NETFILTER_ADVANCED
317 select NF_CONNTRACK_MARK
319 This option adds the "CONNMARK" target and "connmark" match.
321 Netfilter allows you to store a mark value per connection (a.k.a.
322 ctmark), similarly to the packet mark (nfmark). Using this
323 target and match, you can set and match on this mark.
325 # alphabetically ordered list of targets
327 comment "Xtables targets"
329 config NETFILTER_XT_TARGET_AUDIT
330 tristate "AUDIT target support"
332 depends on NETFILTER_ADVANCED
334 This option adds a 'AUDIT' target, which can be used to create
335 audit records for packets dropped/accepted.
337 To compileit as a module, choose M here. If unsure, say N.
339 config NETFILTER_XT_TARGET_CHECKSUM
340 tristate "CHECKSUM target support"
341 depends on IP_NF_MANGLE || IP6_NF_MANGLE
342 depends on NETFILTER_ADVANCED
344 This option adds a `CHECKSUM' target, which can be used in the iptables mangle
347 You can use this target to compute and fill in the checksum in
348 a packet that lacks a checksum. This is particularly useful,
349 if you need to work around old applications such as dhcp clients,
350 that do not work well with checksum offloads, but don't want to disable
351 checksum offload in your device.
353 To compile it as a module, choose M here. If unsure, say N.
355 config NETFILTER_XT_TARGET_CLASSIFY
356 tristate '"CLASSIFY" target support'
357 depends on NETFILTER_ADVANCED
359 This option adds a `CLASSIFY' target, which enables the user to set
360 the priority of a packet. Some qdiscs can use this value for
361 classification, among these are:
363 atm, cbq, dsmark, pfifo_fast, htb, prio
365 To compile it as a module, choose M here. If unsure, say N.
367 config NETFILTER_XT_TARGET_CONNMARK
368 tristate '"CONNMARK" target support'
369 depends on NF_CONNTRACK
370 depends on NETFILTER_ADVANCED
371 select NETFILTER_XT_CONNMARK
373 This is a backwards-compat option for the user's convenience
374 (e.g. when running oldconfig). It selects
375 CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
377 config NETFILTER_XT_TARGET_CONNSECMARK
378 tristate '"CONNSECMARK" target support'
379 depends on NF_CONNTRACK && NF_CONNTRACK_SECMARK
380 default m if NETFILTER_ADVANCED=n
382 The CONNSECMARK target copies security markings from packets
383 to connections, and restores security markings from connections
384 to packets (if the packets are not already marked). This would
385 normally be used in conjunction with the SECMARK target.
387 To compile it as a module, choose M here. If unsure, say N.
389 config NETFILTER_XT_TARGET_CT
390 tristate '"CT" target support'
391 depends on NF_CONNTRACK
392 depends on IP_NF_RAW || IP6_NF_RAW
393 depends on NETFILTER_ADVANCED
395 This options adds a `CT' target, which allows to specify initial
396 connection tracking parameters like events to be delivered and
397 the helper to be used.
399 To compile it as a module, choose M here. If unsure, say N.
401 config NETFILTER_XT_TARGET_DSCP
402 tristate '"DSCP" and "TOS" target support'
403 depends on IP_NF_MANGLE || IP6_NF_MANGLE
404 depends on NETFILTER_ADVANCED
406 This option adds a `DSCP' target, which allows you to manipulate
407 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
409 The DSCP field can have any value between 0x0 and 0x3f inclusive.
411 It also adds the "TOS" target, which allows you to create rules in
412 the "mangle" table which alter the Type Of Service field of an IPv4
413 or the Priority field of an IPv6 packet, prior to routing.
415 To compile it as a module, choose M here. If unsure, say N.
417 config NETFILTER_XT_TARGET_HL
418 tristate '"HL" hoplimit target support'
419 depends on IP_NF_MANGLE || IP6_NF_MANGLE
420 depends on NETFILTER_ADVANCED
422 This option adds the "HL" (for IPv6) and "TTL" (for IPv4)
423 targets, which enable the user to change the
424 hoplimit/time-to-live value of the IP header.
426 While it is safe to decrement the hoplimit/TTL value, the
427 modules also allow to increment and set the hoplimit value of
428 the header to arbitrary values. This is EXTREMELY DANGEROUS
429 since you can easily create immortal packets that loop
430 forever on the network.
432 config NETFILTER_XT_TARGET_IDLETIMER
433 tristate "IDLETIMER target support"
434 depends on NETFILTER_ADVANCED
437 This option adds the `IDLETIMER' target. Each matching packet
438 resets the timer associated with label specified when the rule is
439 added. When the timer expires, it triggers a sysfs notification.
440 The remaining time for expiration can be read via sysfs.
442 To compile it as a module, choose M here. If unsure, say N.
444 config NETFILTER_XT_TARGET_LED
445 tristate '"LED" target support'
446 depends on LEDS_CLASS && LEDS_TRIGGERS
447 depends on NETFILTER_ADVANCED
449 This option adds a `LED' target, which allows you to blink LEDs in
450 response to particular packets passing through your machine.
452 This can be used to turn a spare LED into a network activity LED,
453 which only flashes in response to FTP transfers, for example. Or
454 you could have an LED which lights up for a minute or two every time
455 somebody connects to your machine via SSH.
457 You will need support for the "led" class to make this work.
459 To create an LED trigger for incoming SSH traffic:
460 iptables -A INPUT -p tcp --dport 22 -j LED --led-trigger-id ssh --led-delay 1000
462 Then attach the new trigger to an LED on your system:
463 echo netfilter-ssh > /sys/class/leds/<ledname>/trigger
465 For more information on the LEDs available on your system, see
466 Documentation/leds-class.txt
468 config NETFILTER_XT_TARGET_MARK
469 tristate '"MARK" target support'
470 depends on NETFILTER_ADVANCED
471 select NETFILTER_XT_MARK
473 This is a backwards-compat option for the user's convenience
474 (e.g. when running oldconfig). It selects
475 CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
477 config NETFILTER_XT_TARGET_NFLOG
478 tristate '"NFLOG" target support'
479 default m if NETFILTER_ADVANCED=n
480 select NETFILTER_NETLINK_LOG
482 This option enables the NFLOG target, which allows to LOG
483 messages through nfnetlink_log.
485 To compile it as a module, choose M here. If unsure, say N.
487 config NETFILTER_XT_TARGET_NFQUEUE
488 tristate '"NFQUEUE" target Support'
489 depends on NETFILTER_ADVANCED
490 select NETFILTER_NETLINK_QUEUE
492 This target replaced the old obsolete QUEUE target.
494 As opposed to QUEUE, it supports 65535 different queues,
497 To compile it as a module, choose M here. If unsure, say N.
499 config NETFILTER_XT_TARGET_NOTRACK
500 tristate '"NOTRACK" target support'
501 depends on IP_NF_RAW || IP6_NF_RAW
502 depends on NF_CONNTRACK
503 depends on NETFILTER_ADVANCED
505 The NOTRACK target allows a select rule to specify
506 which packets *not* to enter the conntrack/NAT
507 subsystem with all the consequences (no ICMP error tracking,
508 no protocol helpers for the selected packets).
510 If you want to compile it as a module, say M here and read
511 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
513 config NETFILTER_XT_TARGET_RATEEST
514 tristate '"RATEEST" target support'
515 depends on NETFILTER_ADVANCED
517 This option adds a `RATEEST' target, which allows to measure
518 rates similar to TC estimators. The `rateest' match can be
519 used to match on the measured rates.
521 To compile it as a module, choose M here. If unsure, say N.
523 config NETFILTER_XT_TARGET_TEE
524 tristate '"TEE" - packet cloning to alternate destination'
525 depends on NETFILTER_ADVANCED
526 depends on (IPV6 || IPV6=n)
527 depends on !NF_CONNTRACK || NF_CONNTRACK
529 This option adds a "TEE" target with which a packet can be cloned and
530 this clone be rerouted to another nexthop.
532 config NETFILTER_XT_TARGET_TPROXY
533 tristate '"TPROXY" target support (EXPERIMENTAL)'
534 depends on EXPERIMENTAL
535 depends on NETFILTER_TPROXY
536 depends on NETFILTER_XTABLES
537 depends on NETFILTER_ADVANCED
538 select NF_DEFRAG_IPV4
539 select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES
541 This option adds a `TPROXY' target, which is somewhat similar to
542 REDIRECT. It can only be used in the mangle table and is useful
543 to redirect traffic to a transparent proxy. It does _not_ depend
544 on Netfilter connection tracking and NAT, unlike REDIRECT.
546 To compile it as a module, choose M here. If unsure, say N.
548 config NETFILTER_XT_TARGET_TRACE
549 tristate '"TRACE" target support'
550 depends on IP_NF_RAW || IP6_NF_RAW
551 depends on NETFILTER_ADVANCED
553 The TRACE target allows you to mark packets so that the kernel
554 will log every rule which match the packets as those traverse
555 the tables, chains, rules.
557 If you want to compile it as a module, say M here and read
558 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
560 config NETFILTER_XT_TARGET_SECMARK
561 tristate '"SECMARK" target support'
562 depends on NETWORK_SECMARK
563 default m if NETFILTER_ADVANCED=n
565 The SECMARK target allows security marking of network
566 packets, for use with security subsystems.
568 To compile it as a module, choose M here. If unsure, say N.
570 config NETFILTER_XT_TARGET_TCPMSS
571 tristate '"TCPMSS" target support'
572 depends on (IPV6 || IPV6=n)
573 default m if NETFILTER_ADVANCED=n
575 This option adds a `TCPMSS' target, which allows you to alter the
576 MSS value of TCP SYN packets, to control the maximum size for that
577 connection (usually limiting it to your outgoing interface's MTU
580 This is used to overcome criminally braindead ISPs or servers which
581 block ICMP Fragmentation Needed packets. The symptoms of this
582 problem are that everything works fine from your Linux
583 firewall/router, but machines behind it can never exchange large
585 1) Web browsers connect, then hang with no data received.
586 2) Small mail works fine, but large emails hang.
587 3) ssh works fine, but scp hangs after initial handshaking.
589 Workaround: activate this option and add a rule to your firewall
592 iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
593 -j TCPMSS --clamp-mss-to-pmtu
595 To compile it as a module, choose M here. If unsure, say N.
597 config NETFILTER_XT_TARGET_TCPOPTSTRIP
598 tristate '"TCPOPTSTRIP" target support (EXPERIMENTAL)'
599 depends on EXPERIMENTAL
600 depends on IP_NF_MANGLE || IP6_NF_MANGLE
601 depends on NETFILTER_ADVANCED
603 This option adds a "TCPOPTSTRIP" target, which allows you to strip
604 TCP options from TCP packets.
606 # alphabetically ordered list of matches
608 comment "Xtables matches"
610 config NETFILTER_XT_MATCH_CLUSTER
611 tristate '"cluster" match support'
612 depends on NF_CONNTRACK
613 depends on NETFILTER_ADVANCED
615 This option allows you to build work-load-sharing clusters of
616 network servers/stateful firewalls without having a dedicated
617 load-balancing router/server/switch. Basically, this match returns
618 true when the packet must be handled by this cluster node. Thus,
619 all nodes see all packets and this match decides which node handles
620 what packets. The work-load sharing algorithm is based on source
623 If you say Y or M here, try `iptables -m cluster --help` for
626 config NETFILTER_XT_MATCH_COMMENT
627 tristate '"comment" match support'
628 depends on NETFILTER_ADVANCED
630 This option adds a `comment' dummy-match, which allows you to put
631 comments in your iptables ruleset.
633 If you want to compile it as a module, say M here and read
634 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
636 config NETFILTER_XT_MATCH_CONNBYTES
637 tristate '"connbytes" per-connection counter match support'
638 depends on NF_CONNTRACK
639 depends on NETFILTER_ADVANCED
641 This option adds a `connbytes' match, which allows you to match the
642 number of bytes and/or packets for each direction within a connection.
644 If you want to compile it as a module, say M here and read
645 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
647 config NETFILTER_XT_MATCH_CONNLIMIT
648 tristate '"connlimit" match support"'
649 depends on NF_CONNTRACK
650 depends on NETFILTER_ADVANCED
652 This match allows you to match against the number of parallel
653 connections to a server per client IP address (or address block).
655 config NETFILTER_XT_MATCH_CONNMARK
656 tristate '"connmark" connection mark match support'
657 depends on NF_CONNTRACK
658 depends on NETFILTER_ADVANCED
659 select NETFILTER_XT_CONNMARK
661 This is a backwards-compat option for the user's convenience
662 (e.g. when running oldconfig). It selects
663 CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
665 config NETFILTER_XT_MATCH_CONNTRACK
666 tristate '"conntrack" connection tracking match support'
667 depends on NF_CONNTRACK
668 default m if NETFILTER_ADVANCED=n
670 This is a general conntrack match module, a superset of the state match.
672 It allows matching on additional conntrack information, which is
673 useful in complex configurations, such as NAT gateways with multiple
674 internet links or tunnels.
676 To compile it as a module, choose M here. If unsure, say N.
678 config NETFILTER_XT_MATCH_CPU
679 tristate '"cpu" match support'
680 depends on NETFILTER_ADVANCED
682 CPU matching allows you to match packets based on the CPU
683 currently handling the packet.
685 To compile it as a module, choose M here. If unsure, say N.
687 config NETFILTER_XT_MATCH_DCCP
688 tristate '"dccp" protocol match support'
689 depends on NETFILTER_ADVANCED
692 With this option enabled, you will be able to use the iptables
693 `dccp' match in order to match on DCCP source/destination ports
696 If you want to compile it as a module, say M here and read
697 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
699 config NETFILTER_XT_MATCH_DSCP
700 tristate '"dscp" and "tos" match support'
701 depends on NETFILTER_ADVANCED
703 This option adds a `DSCP' match, which allows you to match against
704 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
706 The DSCP field can have any value between 0x0 and 0x3f inclusive.
708 It will also add a "tos" match, which allows you to match packets
709 based on the Type Of Service fields of the IPv4 packet (which share
710 the same bits as DSCP).
712 To compile it as a module, choose M here. If unsure, say N.
714 config NETFILTER_XT_MATCH_ESP
715 tristate '"esp" match support'
716 depends on NETFILTER_ADVANCED
718 This match extension allows you to match a range of SPIs
719 inside ESP header of IPSec packets.
721 To compile it as a module, choose M here. If unsure, say N.
723 config NETFILTER_XT_MATCH_HASHLIMIT
724 tristate '"hashlimit" match support'
725 depends on (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
726 depends on NETFILTER_ADVANCED
728 This option adds a `hashlimit' match.
730 As opposed to `limit', this match dynamically creates a hash table
731 of limit buckets, based on your selection of source/destination
732 addresses and/or ports.
734 It enables you to express policies like `10kpps for any given
735 destination address' or `500pps from any given source address'
738 config NETFILTER_XT_MATCH_HELPER
739 tristate '"helper" match support'
740 depends on NF_CONNTRACK
741 depends on NETFILTER_ADVANCED
743 Helper matching allows you to match packets in dynamic connections
744 tracked by a conntrack-helper, ie. ip_conntrack_ftp
746 To compile it as a module, choose M here. If unsure, say Y.
748 config NETFILTER_XT_MATCH_HL
749 tristate '"hl" hoplimit/TTL match support'
750 depends on NETFILTER_ADVANCED
752 HL matching allows you to match packets based on the hoplimit
753 in the IPv6 header, or the time-to-live field in the IPv4
754 header of the packet.
756 config NETFILTER_XT_MATCH_IPRANGE
757 tristate '"iprange" address range match support'
758 depends on NETFILTER_ADVANCED
760 This option adds a "iprange" match, which allows you to match based on
761 an IP address range. (Normal iptables only matches on single addresses
762 with an optional mask.)
766 config NETFILTER_XT_MATCH_IPVS
767 tristate '"ipvs" match support'
769 depends on NETFILTER_ADVANCED
770 depends on NF_CONNTRACK
772 This option allows you to match against IPVS properties of a packet.
776 config NETFILTER_XT_MATCH_LENGTH
777 tristate '"length" match support'
778 depends on NETFILTER_ADVANCED
780 This option allows you to match the length of a packet against a
781 specific value or range of values.
783 To compile it as a module, choose M here. If unsure, say N.
785 config NETFILTER_XT_MATCH_LIMIT
786 tristate '"limit" match support'
787 depends on NETFILTER_ADVANCED
789 limit matching allows you to control the rate at which a rule can be
790 matched: mainly useful in combination with the LOG target ("LOG
791 target support", below) and to avoid some Denial of Service attacks.
793 To compile it as a module, choose M here. If unsure, say N.
795 config NETFILTER_XT_MATCH_MAC
796 tristate '"mac" address match support'
797 depends on NETFILTER_ADVANCED
799 MAC matching allows you to match packets based on the source
800 Ethernet address of the packet.
802 To compile it as a module, choose M here. If unsure, say N.
804 config NETFILTER_XT_MATCH_MARK
805 tristate '"mark" match support'
806 depends on NETFILTER_ADVANCED
807 select NETFILTER_XT_MARK
809 This is a backwards-compat option for the user's convenience
810 (e.g. when running oldconfig). It selects
811 CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
813 config NETFILTER_XT_MATCH_MULTIPORT
814 tristate '"multiport" Multiple port match support'
815 depends on NETFILTER_ADVANCED
817 Multiport matching allows you to match TCP or UDP packets based on
818 a series of source or destination ports: normally a rule can only
819 match a single range of ports.
821 To compile it as a module, choose M here. If unsure, say N.
823 config NETFILTER_XT_MATCH_OSF
824 tristate '"osf" Passive OS fingerprint match'
825 depends on NETFILTER_ADVANCED && NETFILTER_NETLINK
827 This option selects the Passive OS Fingerprinting match module
828 that allows to passively match the remote operating system by
829 analyzing incoming TCP SYN packets.
831 Rules and loading software can be downloaded from
832 http://www.ioremap.net/projects/osf
834 To compile it as a module, choose M here. If unsure, say N.
836 config NETFILTER_XT_MATCH_OWNER
837 tristate '"owner" match support'
838 depends on NETFILTER_ADVANCED
840 Socket owner matching allows you to match locally-generated packets
841 based on who created the socket: the user or group. It is also
842 possible to check whether a socket actually exists.
844 config NETFILTER_XT_MATCH_POLICY
845 tristate 'IPsec "policy" match support'
847 default m if NETFILTER_ADVANCED=n
849 Policy matching allows you to match packets based on the
850 IPsec policy that was used during decapsulation/will
851 be used during encapsulation.
853 To compile it as a module, choose M here. If unsure, say N.
855 config NETFILTER_XT_MATCH_PHYSDEV
856 tristate '"physdev" match support'
857 depends on BRIDGE && BRIDGE_NETFILTER
858 depends on NETFILTER_ADVANCED
860 Physdev packet matching matches against the physical bridge ports
861 the IP packet arrived on or will leave by.
863 To compile it as a module, choose M here. If unsure, say N.
865 config NETFILTER_XT_MATCH_PKTTYPE
866 tristate '"pkttype" packet type match support'
867 depends on NETFILTER_ADVANCED
869 Packet type matching allows you to match a packet by
870 its "class", eg. BROADCAST, MULTICAST, ...
873 iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG
875 To compile it as a module, choose M here. If unsure, say N.
877 config NETFILTER_XT_MATCH_QUOTA
878 tristate '"quota" match support'
879 depends on NETFILTER_ADVANCED
881 This option adds a `quota' match, which allows to match on a
884 If you want to compile it as a module, say M here and read
885 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
887 config NETFILTER_XT_MATCH_RATEEST
888 tristate '"rateest" match support'
889 depends on NETFILTER_ADVANCED
890 select NETFILTER_XT_TARGET_RATEEST
892 This option adds a `rateest' match, which allows to match on the
893 rate estimated by the RATEEST target.
895 To compile it as a module, choose M here. If unsure, say N.
897 config NETFILTER_XT_MATCH_REALM
898 tristate '"realm" match support'
899 depends on NETFILTER_ADVANCED
900 select IP_ROUTE_CLASSID
902 This option adds a `realm' match, which allows you to use the realm
903 key from the routing subsystem inside iptables.
905 This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option
908 If you want to compile it as a module, say M here and read
909 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
911 config NETFILTER_XT_MATCH_RECENT
912 tristate '"recent" match support'
913 depends on NETFILTER_ADVANCED
915 This match is used for creating one or many lists of recently
916 used addresses and then matching against that/those list(s).
918 Short options are available by using 'iptables -m recent -h'
919 Official Website: <http://snowman.net/projects/ipt_recent/>
921 config NETFILTER_XT_MATCH_SCTP
922 tristate '"sctp" protocol match support (EXPERIMENTAL)'
923 depends on EXPERIMENTAL
924 depends on NETFILTER_ADVANCED
927 With this option enabled, you will be able to use the
928 `sctp' match in order to match on SCTP source/destination ports
929 and SCTP chunk types.
931 If you want to compile it as a module, say M here and read
932 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
934 config NETFILTER_XT_MATCH_SOCKET
935 tristate '"socket" match support (EXPERIMENTAL)'
936 depends on EXPERIMENTAL
937 depends on NETFILTER_TPROXY
938 depends on NETFILTER_XTABLES
939 depends on NETFILTER_ADVANCED
940 depends on !NF_CONNTRACK || NF_CONNTRACK
941 select NF_DEFRAG_IPV4
942 select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES
944 This option adds a `socket' match, which can be used to match
945 packets for which a TCP or UDP socket lookup finds a valid socket.
946 It can be used in combination with the MARK target and policy
947 routing to implement full featured non-locally bound sockets.
949 To compile it as a module, choose M here. If unsure, say N.
951 config NETFILTER_XT_MATCH_STATE
952 tristate '"state" match support'
953 depends on NF_CONNTRACK
954 default m if NETFILTER_ADVANCED=n
956 Connection state matching allows you to match packets based on their
957 relationship to a tracked connection (ie. previous packets). This
958 is a powerful tool for packet classification.
960 To compile it as a module, choose M here. If unsure, say N.
962 config NETFILTER_XT_MATCH_STATISTIC
963 tristate '"statistic" match support'
964 depends on NETFILTER_ADVANCED
966 This option adds a `statistic' match, which allows you to match
967 on packets periodically or randomly with a given percentage.
969 To compile it as a module, choose M here. If unsure, say N.
971 config NETFILTER_XT_MATCH_STRING
972 tristate '"string" match support'
973 depends on NETFILTER_ADVANCED
975 select TEXTSEARCH_KMP
977 select TEXTSEARCH_FSM
979 This option adds a `string' match, which allows you to look for
980 pattern matchings in packets.
982 To compile it as a module, choose M here. If unsure, say N.
984 config NETFILTER_XT_MATCH_TCPMSS
985 tristate '"tcpmss" match support'
986 depends on NETFILTER_ADVANCED
988 This option adds a `tcpmss' match, which allows you to examine the
989 MSS value of TCP SYN packets, which control the maximum packet size
992 To compile it as a module, choose M here. If unsure, say N.
994 config NETFILTER_XT_MATCH_TIME
995 tristate '"time" match support'
996 depends on NETFILTER_ADVANCED
998 This option adds a "time" match, which allows you to match based on
999 the packet arrival time (at the machine which netfilter is running)
1000 on) or departure time/date (for locally generated packets).
1002 If you say Y here, try `iptables -m time --help` for
1005 If you want to compile it as a module, say M here.
1008 config NETFILTER_XT_MATCH_U32
1009 tristate '"u32" match support'
1010 depends on NETFILTER_ADVANCED
1012 u32 allows you to extract quantities of up to 4 bytes from a packet,
1013 AND them with specified masks, shift them by specified amounts and
1014 test whether the results are in any of a set of specified ranges.
1015 The specification of what to extract is general enough to skip over
1016 headers with lengths stored in the packet, as in IP or TCP header
1019 Details and examples are in the kernel module source.
1021 endif # NETFILTER_XTABLES
1025 source "net/netfilter/ipvs/Kconfig"