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.
54 config NF_CONNTRACK_MARK
55 bool 'Connection mark tracking support'
56 depends on NETFILTER_ADVANCED
58 This option enables support for connection marks, used by the
59 `CONNMARK' target and `connmark' match. Similar to the mark value
60 of packets, but this mark value is kept in the conntrack session
61 instead of the individual packets.
63 config NF_CONNTRACK_SECMARK
64 bool 'Connection tracking security mark support'
65 depends on NETWORK_SECMARK
66 default m if NETFILTER_ADVANCED=n
68 This option enables security markings to be applied to
69 connections. Typically they are copied to connections from
70 packets using the CONNSECMARK target and copied back from
71 connections to packets with the same target, with the packets
72 being originally labeled via SECMARK.
76 config NF_CONNTRACK_ZONES
77 bool 'Connection tracking zones'
78 depends on NETFILTER_ADVANCED
79 depends on NETFILTER_XT_TARGET_CT
81 This option enables support for connection tracking zones.
82 Normally, each connection needs to have a unique system wide
83 identity. Connection tracking zones allow to have multiple
84 connections using the same identity, as long as they are
85 contained in different zones.
89 config NF_CONNTRACK_PROCFS
90 bool "Supply CT list in procfs (OBSOLETE)"
94 This option enables for the list of known conntrack entries
95 to be shown in procfs under net/netfilter/nf_conntrack. This
96 is considered obsolete in favor of using the conntrack(8)
97 tool which uses Netlink.
99 config NF_CONNTRACK_EVENTS
100 bool "Connection tracking events"
101 depends on NETFILTER_ADVANCED
103 If this option is enabled, the connection tracking code will
104 provide a notifier chain that can be used by other kernel code
105 to get notified about changes in the connection tracking state.
109 config NF_CONNTRACK_TIMEOUT
110 bool 'Connection tracking timeout'
111 depends on NETFILTER_ADVANCED
113 This option enables support for connection tracking timeout
114 extension. This allows you to attach timeout policies to flow
119 config NF_CONNTRACK_TIMESTAMP
120 bool 'Connection tracking timestamping'
121 depends on NETFILTER_ADVANCED
123 This option enables support for connection tracking timestamping.
124 This allows you to store the flow start-time and to obtain
125 the flow-stop time (once it has been destroyed) via Connection
130 config NF_CONNTRACK_LABELS
133 This option enables support for assigning user-defined flag bits
134 to connection tracking entries. It selected by the connlabel match.
136 config NF_CT_PROTO_DCCP
137 tristate 'DCCP protocol connection tracking support'
138 depends on NETFILTER_ADVANCED
141 With this option enabled, the layer 3 independent connection
142 tracking code will be able to do state tracking on DCCP connections.
146 config NF_CT_PROTO_GRE
149 config NF_CT_PROTO_SCTP
150 tristate 'SCTP protocol connection tracking support'
151 depends on NETFILTER_ADVANCED
154 With this option enabled, the layer 3 independent connection
155 tracking code will be able to do state tracking on SCTP connections.
157 If you want to compile it as a module, say M here and read
158 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
160 config NF_CT_PROTO_UDPLITE
161 tristate 'UDP-Lite protocol connection tracking support'
162 depends on NETFILTER_ADVANCED
164 With this option enabled, the layer 3 independent connection
165 tracking code will be able to do state tracking on UDP-Lite
168 To compile it as a module, choose M here. If unsure, say N.
170 config NF_CONNTRACK_AMANDA
171 tristate "Amanda backup protocol support"
172 depends on NETFILTER_ADVANCED
174 select TEXTSEARCH_KMP
176 If you are running the Amanda backup package <http://www.amanda.org/>
177 on this machine or machines that will be MASQUERADED through this
178 machine, then you may want to enable this feature. This allows the
179 connection tracking and natting code to allow the sub-channels that
180 Amanda requires for communication of the backup data, messages and
183 To compile it as a module, choose M here. If unsure, say N.
185 config NF_CONNTRACK_FTP
186 tristate "FTP protocol support"
187 default m if NETFILTER_ADVANCED=n
189 Tracking FTP connections is problematic: special helpers are
190 required for tracking them, and doing masquerading and other forms
191 of Network Address Translation on them.
193 This is FTP support on Layer 3 independent connection tracking.
194 Layer 3 independent connection tracking is experimental scheme
195 which generalize ip_conntrack to support other layer 3 protocols.
197 To compile it as a module, choose M here. If unsure, say N.
199 config NF_CONNTRACK_H323
200 tristate "H.323 protocol support"
201 depends on (IPV6 || IPV6=n)
202 depends on NETFILTER_ADVANCED
204 H.323 is a VoIP signalling protocol from ITU-T. As one of the most
205 important VoIP protocols, it is widely used by voice hardware and
206 software including voice gateways, IP phones, Netmeeting, OpenPhone,
209 With this module you can support H.323 on a connection tracking/NAT
212 This module supports RAS, Fast Start, H.245 Tunnelling, Call
213 Forwarding, RTP/RTCP and T.120 based audio, video, fax, chat,
214 whiteboard, file transfer, etc. For more information, please
215 visit http://nath323.sourceforge.net/.
217 To compile it as a module, choose M here. If unsure, say N.
219 config NF_CONNTRACK_IRC
220 tristate "IRC protocol support"
221 default m if NETFILTER_ADVANCED=n
223 There is a commonly-used extension to IRC called
224 Direct Client-to-Client Protocol (DCC). This enables users to send
225 files to each other, and also chat to each other without the need
226 of a server. DCC Sending is used anywhere you send files over IRC,
227 and DCC Chat is most commonly used by Eggdrop bots. If you are
228 using NAT, this extension will enable you to send files and initiate
229 chats. Note that you do NOT need this extension to get files or
230 have others initiate chats, or everything else in IRC.
232 To compile it as a module, choose M here. If unsure, say N.
234 config NF_CONNTRACK_BROADCAST
237 config NF_CONNTRACK_NETBIOS_NS
238 tristate "NetBIOS name service protocol support"
239 select NF_CONNTRACK_BROADCAST
241 NetBIOS name service requests are sent as broadcast messages from an
242 unprivileged port and responded to with unicast messages to the
243 same port. This make them hard to firewall properly because connection
244 tracking doesn't deal with broadcasts. This helper tracks locally
245 originating NetBIOS name service requests and the corresponding
246 responses. It relies on correct IP address configuration, specifically
247 netmask and broadcast address. When properly configured, the output
248 of "ip address show" should look similar to this:
250 $ ip -4 address show eth0
251 4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
252 inet 172.16.2.252/24 brd 172.16.2.255 scope global eth0
254 To compile it as a module, choose M here. If unsure, say N.
256 config NF_CONNTRACK_SNMP
257 tristate "SNMP service protocol support"
258 depends on NETFILTER_ADVANCED
259 select NF_CONNTRACK_BROADCAST
261 SNMP service requests are sent as broadcast messages from an
262 unprivileged port and responded to with unicast messages to the
263 same port. This make them hard to firewall properly because connection
264 tracking doesn't deal with broadcasts. This helper tracks locally
265 originating SNMP service requests and the corresponding
266 responses. It relies on correct IP address configuration, specifically
267 netmask and broadcast address.
269 To compile it as a module, choose M here. If unsure, say N.
271 config NF_CONNTRACK_PPTP
272 tristate "PPtP protocol support"
273 depends on NETFILTER_ADVANCED
274 select NF_CT_PROTO_GRE
276 This module adds support for PPTP (Point to Point Tunnelling
277 Protocol, RFC2637) connection tracking and NAT.
279 If you are running PPTP sessions over a stateful firewall or NAT
280 box, you may want to enable this feature.
282 Please note that not all PPTP modes of operation are supported yet.
283 Specifically these limitations exist:
284 - Blindly assumes that control connections are always established
285 in PNS->PAC direction. This is a violation of RFC2637.
286 - Only supports a single call within each session
288 To compile it as a module, choose M here. If unsure, say N.
290 config NF_CONNTRACK_SANE
291 tristate "SANE protocol support"
292 depends on NETFILTER_ADVANCED
294 SANE is a protocol for remote access to scanners as implemented
295 by the 'saned' daemon. Like FTP, it uses separate control and
298 With this module you can support SANE on a connection tracking
301 To compile it as a module, choose M here. If unsure, say N.
303 config NF_CONNTRACK_SIP
304 tristate "SIP protocol support"
305 default m if NETFILTER_ADVANCED=n
307 SIP is an application-layer control protocol that can establish,
308 modify, and terminate multimedia sessions (conferences) such as
309 Internet telephony calls. With the ip_conntrack_sip and
310 the nf_nat_sip modules you can support the protocol on a connection
311 tracking/NATing firewall.
313 To compile it as a module, choose M here. If unsure, say N.
315 config NF_CONNTRACK_TFTP
316 tristate "TFTP protocol support"
317 depends on NETFILTER_ADVANCED
319 TFTP connection tracking helper, this is required depending
320 on how restrictive your ruleset is.
321 If you are using a tftp client behind -j SNAT or -j MASQUERADING
324 To compile it as a module, choose M here. If unsure, say N.
327 tristate 'Connection tracking netlink interface'
328 select NETFILTER_NETLINK
329 default m if NETFILTER_ADVANCED=n
331 This option enables support for a netlink-based userspace interface
333 config NF_CT_NETLINK_TIMEOUT
334 tristate 'Connection tracking timeout tuning via Netlink'
335 select NETFILTER_NETLINK
336 depends on NETFILTER_ADVANCED
338 This option enables support for connection tracking timeout
339 fine-grain tuning. This allows you to attach specific timeout
340 policies to flows, instead of using the global timeout policy.
344 config NF_CT_NETLINK_HELPER
345 tristate 'Connection tracking helpers in user-space via Netlink'
346 select NETFILTER_NETLINK
347 depends on NF_CT_NETLINK
348 depends on NETFILTER_NETLINK_QUEUE
349 depends on NETFILTER_NETLINK_QUEUE_CT
350 depends on NETFILTER_ADVANCED
352 This option enables the user-space connection tracking helpers
357 config NETFILTER_NETLINK_QUEUE_CT
358 bool "NFQUEUE integration with Connection Tracking"
360 depends on NETFILTER_NETLINK_QUEUE
362 If this option is enabled, NFQUEUE can include Connection Tracking
363 information together with the packet is the enqueued via NFNETLINK.
373 config NF_NAT_PROTO_DCCP
375 depends on NF_NAT && NF_CT_PROTO_DCCP
376 default NF_NAT && NF_CT_PROTO_DCCP
378 config NF_NAT_PROTO_UDPLITE
380 depends on NF_NAT && NF_CT_PROTO_UDPLITE
381 default NF_NAT && NF_CT_PROTO_UDPLITE
383 config NF_NAT_PROTO_SCTP
385 default NF_NAT && NF_CT_PROTO_SCTP
386 depends on NF_NAT && NF_CT_PROTO_SCTP
391 depends on NF_CONNTRACK && NF_NAT
392 default NF_NAT && NF_CONNTRACK_AMANDA
396 depends on NF_CONNTRACK && NF_NAT
397 default NF_NAT && NF_CONNTRACK_FTP
401 depends on NF_CONNTRACK && NF_NAT
402 default NF_NAT && NF_CONNTRACK_IRC
406 depends on NF_CONNTRACK && NF_NAT
407 default NF_NAT && NF_CONNTRACK_SIP
411 depends on NF_CONNTRACK && NF_NAT
412 default NF_NAT && NF_CONNTRACK_TFTP
414 config NETFILTER_SYNPROXY
420 select NETFILTER_NETLINK
421 tristate "Netfilter nf_tables support"
423 nftables is the new packet classification framework that intends to
424 replace the existing {ip,ip6,arp,eb}_tables infrastructure. It
425 provides a pseudo-state machine with an extensible instruction-set
426 (also known as expressions) that the userspace 'nft' utility
427 (http://www.netfilter.org/projects/nftables) uses to build the
428 rule-set. It also comes with the generic set infrastructure that
429 allows you to construct mappings between matchings and actions
430 for performance lookups.
432 To compile it as a module, choose M here.
434 config NF_TABLES_INET
435 depends on NF_TABLES && IPV6
436 select NF_TABLES_IPV4
437 select NF_TABLES_IPV6
438 tristate "Netfilter nf_tables mixed IPv4/IPv6 tables support"
440 This option enables support for a mixed IPv4/IPv6 "inet" table.
444 tristate "Netfilter nf_tables IPv6 exthdr module"
446 This option adds the "exthdr" expression that you can use to match
447 IPv6 extension headers.
451 tristate "Netfilter nf_tables meta module"
453 This option adds the "meta" expression that you can use to match and
454 to set packet metainformation such as the packet mark.
458 depends on NF_CONNTRACK
459 tristate "Netfilter nf_tables conntrack module"
461 This option adds the "meta" expression that you can use to match
462 connection tracking information such as the flow state.
466 tristate "Netfilter nf_tables rbtree set module"
468 This option adds the "rbtree" set type (Red Black tree) that is used
469 to build interval-based sets.
473 tristate "Netfilter nf_tables hash set module"
475 This option adds the "hash" set type that is used to build one-way
476 mappings between matchings and actions.
480 tristate "Netfilter nf_tables counter module"
482 This option adds the "counter" expression that you can use to
483 include packet and byte counters in a rule.
487 tristate "Netfilter nf_tables log module"
489 This option adds the "log" expression that you can use to log
490 packets matching some criteria.
494 tristate "Netfilter nf_tables limit module"
496 This option adds the "limit" expression that you can use to
497 ratelimit rule matchings.
501 depends on NF_CONNTRACK
503 tristate "Netfilter nf_tables nat module"
505 This option adds the "nat" expression that you can use to perform
506 typical Network Address Translation (NAT) packet transformations.
510 depends on NETFILTER_XTABLES
511 depends on NETFILTER_NETLINK_QUEUE
512 tristate "Netfilter nf_tables queue module"
514 This is required if you intend to use the userspace queueing
515 infrastructure (also known as NFQUEUE) from nftables.
519 default m if NETFILTER_ADVANCED=n
520 tristate "Netfilter nf_tables reject support"
522 This option adds the "reject" expression that you can use to
523 explicitly deny and notify via TCP reset/ICMP informational errors
526 config NFT_REJECT_INET
527 depends on NF_TABLES_INET
533 depends on NETFILTER_XTABLES
534 tristate "Netfilter x_tables over nf_tables module"
536 This is required if you intend to use any of existing
537 x_tables match/target extensions over the nf_tables
540 config NETFILTER_XTABLES
541 tristate "Netfilter Xtables support (required for ip_tables)"
542 default m if NETFILTER_ADVANCED=n
544 This is required if you intend to use any of ip_tables,
545 ip6_tables or arp_tables.
549 comment "Xtables combined modules"
551 config NETFILTER_XT_MARK
552 tristate 'nfmark target and match support'
553 default m if NETFILTER_ADVANCED=n
555 This option adds the "MARK" target and "mark" match.
557 Netfilter mark matching allows you to match packets based on the
558 "nfmark" value in the packet.
559 The target allows you to create rules in the "mangle" table which alter
560 the netfilter mark (nfmark) field associated with the packet.
562 Prior to routing, the nfmark can influence the routing method (see
563 "Use netfilter MARK value as routing key") and can also be used by
564 other subsystems to change their behavior.
566 config NETFILTER_XT_CONNMARK
567 tristate 'ctmark target and match support'
568 depends on NF_CONNTRACK
569 depends on NETFILTER_ADVANCED
570 select NF_CONNTRACK_MARK
572 This option adds the "CONNMARK" target and "connmark" match.
574 Netfilter allows you to store a mark value per connection (a.k.a.
575 ctmark), similarly to the packet mark (nfmark). Using this
576 target and match, you can set and match on this mark.
578 config NETFILTER_XT_SET
579 tristate 'set target and match support'
581 depends on NETFILTER_ADVANCED
583 This option adds the "SET" target and "set" match.
585 Using this target and match, you can add/delete and match
586 elements in the sets created by ipset(8).
588 To compile it as a module, choose M here. If unsure, say N.
590 # alphabetically ordered list of targets
592 comment "Xtables targets"
594 config NETFILTER_XT_TARGET_AUDIT
595 tristate "AUDIT target support"
597 depends on NETFILTER_ADVANCED
599 This option adds a 'AUDIT' target, which can be used to create
600 audit records for packets dropped/accepted.
602 To compileit as a module, choose M here. If unsure, say N.
604 config NETFILTER_XT_TARGET_CHECKSUM
605 tristate "CHECKSUM target support"
606 depends on IP_NF_MANGLE || IP6_NF_MANGLE
607 depends on NETFILTER_ADVANCED
609 This option adds a `CHECKSUM' target, which can be used in the iptables mangle
612 You can use this target to compute and fill in the checksum in
613 a packet that lacks a checksum. This is particularly useful,
614 if you need to work around old applications such as dhcp clients,
615 that do not work well with checksum offloads, but don't want to disable
616 checksum offload in your device.
618 To compile it as a module, choose M here. If unsure, say N.
620 config NETFILTER_XT_TARGET_CLASSIFY
621 tristate '"CLASSIFY" target support'
622 depends on NETFILTER_ADVANCED
624 This option adds a `CLASSIFY' target, which enables the user to set
625 the priority of a packet. Some qdiscs can use this value for
626 classification, among these are:
628 atm, cbq, dsmark, pfifo_fast, htb, prio
630 To compile it as a module, choose M here. If unsure, say N.
632 config NETFILTER_XT_TARGET_CONNMARK
633 tristate '"CONNMARK" target support'
634 depends on NF_CONNTRACK
635 depends on NETFILTER_ADVANCED
636 select NETFILTER_XT_CONNMARK
638 This is a backwards-compat option for the user's convenience
639 (e.g. when running oldconfig). It selects
640 CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
642 config NETFILTER_XT_TARGET_CONNSECMARK
643 tristate '"CONNSECMARK" target support'
644 depends on NF_CONNTRACK && NF_CONNTRACK_SECMARK
645 default m if NETFILTER_ADVANCED=n
647 The CONNSECMARK target copies security markings from packets
648 to connections, and restores security markings from connections
649 to packets (if the packets are not already marked). This would
650 normally be used in conjunction with the SECMARK target.
652 To compile it as a module, choose M here. If unsure, say N.
654 config NETFILTER_XT_TARGET_CT
655 tristate '"CT" target support'
656 depends on NF_CONNTRACK
657 depends on IP_NF_RAW || IP6_NF_RAW
658 depends on NETFILTER_ADVANCED
660 This options adds a `CT' target, which allows to specify initial
661 connection tracking parameters like events to be delivered and
662 the helper to be used.
664 To compile it as a module, choose M here. If unsure, say N.
666 config NETFILTER_XT_TARGET_DSCP
667 tristate '"DSCP" and "TOS" target support'
668 depends on IP_NF_MANGLE || IP6_NF_MANGLE
669 depends on NETFILTER_ADVANCED
671 This option adds a `DSCP' target, which allows you to manipulate
672 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
674 The DSCP field can have any value between 0x0 and 0x3f inclusive.
676 It also adds the "TOS" target, which allows you to create rules in
677 the "mangle" table which alter the Type Of Service field of an IPv4
678 or the Priority field of an IPv6 packet, prior to routing.
680 To compile it as a module, choose M here. If unsure, say N.
682 config NETFILTER_XT_TARGET_HL
683 tristate '"HL" hoplimit target support'
684 depends on IP_NF_MANGLE || IP6_NF_MANGLE
685 depends on NETFILTER_ADVANCED
687 This option adds the "HL" (for IPv6) and "TTL" (for IPv4)
688 targets, which enable the user to change the
689 hoplimit/time-to-live value of the IP header.
691 While it is safe to decrement the hoplimit/TTL value, the
692 modules also allow to increment and set the hoplimit value of
693 the header to arbitrary values. This is EXTREMELY DANGEROUS
694 since you can easily create immortal packets that loop
695 forever on the network.
697 config NETFILTER_XT_TARGET_HMARK
698 tristate '"HMARK" target support'
699 depends on (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
700 depends on NETFILTER_ADVANCED
702 This option adds the "HMARK" target.
704 The target allows you to create rules in the "raw" and "mangle" tables
705 which set the skbuff mark by means of hash calculation within a given
706 range. The nfmark can influence the routing method (see "Use netfilter
707 MARK value as routing key") and can also be used by other subsystems to
708 change their behaviour.
710 To compile it as a module, choose M here. If unsure, say N.
712 config NETFILTER_XT_TARGET_IDLETIMER
713 tristate "IDLETIMER target support"
714 depends on NETFILTER_ADVANCED
717 This option adds the `IDLETIMER' target. Each matching packet
718 resets the timer associated with label specified when the rule is
719 added. When the timer expires, it triggers a sysfs notification.
720 The remaining time for expiration can be read via sysfs.
722 To compile it as a module, choose M here. If unsure, say N.
724 config NETFILTER_XT_TARGET_LED
725 tristate '"LED" target support'
726 depends on LEDS_CLASS && LEDS_TRIGGERS
727 depends on NETFILTER_ADVANCED
729 This option adds a `LED' target, which allows you to blink LEDs in
730 response to particular packets passing through your machine.
732 This can be used to turn a spare LED into a network activity LED,
733 which only flashes in response to FTP transfers, for example. Or
734 you could have an LED which lights up for a minute or two every time
735 somebody connects to your machine via SSH.
737 You will need support for the "led" class to make this work.
739 To create an LED trigger for incoming SSH traffic:
740 iptables -A INPUT -p tcp --dport 22 -j LED --led-trigger-id ssh --led-delay 1000
742 Then attach the new trigger to an LED on your system:
743 echo netfilter-ssh > /sys/class/leds/<ledname>/trigger
745 For more information on the LEDs available on your system, see
746 Documentation/leds/leds-class.txt
748 config NETFILTER_XT_TARGET_LOG
749 tristate "LOG target support"
752 select NF_LOG_IPV6 if IPV6
753 default m if NETFILTER_ADVANCED=n
755 This option adds a `LOG' target, which allows you to create rules in
756 any iptables table which records the packet header to the syslog.
758 To compile it as a module, choose M here. If unsure, say N.
760 config NETFILTER_XT_TARGET_MARK
761 tristate '"MARK" target support'
762 depends on NETFILTER_ADVANCED
763 select NETFILTER_XT_MARK
765 This is a backwards-compat option for the user's convenience
766 (e.g. when running oldconfig). It selects
767 CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
769 config NETFILTER_XT_TARGET_NETMAP
770 tristate '"NETMAP" target support'
773 NETMAP is an implementation of static 1:1 NAT mapping of network
774 addresses. It maps the network address part, while keeping the host
777 To compile it as a module, choose M here. If unsure, say N.
779 config NETFILTER_XT_TARGET_NFLOG
780 tristate '"NFLOG" target support'
781 default m if NETFILTER_ADVANCED=n
782 select NETFILTER_NETLINK_LOG
784 This option enables the NFLOG target, which allows to LOG
785 messages through nfnetlink_log.
787 To compile it as a module, choose M here. If unsure, say N.
789 config NETFILTER_XT_TARGET_NFQUEUE
790 tristate '"NFQUEUE" target Support'
791 depends on NETFILTER_ADVANCED
792 select NETFILTER_NETLINK_QUEUE
794 This target replaced the old obsolete QUEUE target.
796 As opposed to QUEUE, it supports 65535 different queues,
799 To compile it as a module, choose M here. If unsure, say N.
801 config NETFILTER_XT_TARGET_NOTRACK
802 tristate '"NOTRACK" target support (DEPRECATED)'
803 depends on NF_CONNTRACK
804 depends on IP_NF_RAW || IP6_NF_RAW
805 depends on NETFILTER_ADVANCED
806 select NETFILTER_XT_TARGET_CT
808 config NETFILTER_XT_TARGET_RATEEST
809 tristate '"RATEEST" target support'
810 depends on NETFILTER_ADVANCED
812 This option adds a `RATEEST' target, which allows to measure
813 rates similar to TC estimators. The `rateest' match can be
814 used to match on the measured rates.
816 To compile it as a module, choose M here. If unsure, say N.
818 config NETFILTER_XT_TARGET_REDIRECT
819 tristate "REDIRECT target support"
822 REDIRECT is a special case of NAT: all incoming connections are
823 mapped onto the incoming interface's address, causing the packets to
824 come to the local machine instead of passing through. This is
825 useful for transparent proxies.
827 To compile it as a module, choose M here. If unsure, say N.
829 config NETFILTER_XT_TARGET_TEE
830 tristate '"TEE" - packet cloning to alternate destination'
831 depends on NETFILTER_ADVANCED
832 depends on (IPV6 || IPV6=n)
833 depends on !NF_CONNTRACK || NF_CONNTRACK
835 This option adds a "TEE" target with which a packet can be cloned and
836 this clone be rerouted to another nexthop.
838 config NETFILTER_XT_TARGET_TPROXY
839 tristate '"TPROXY" target transparent proxying support'
840 depends on NETFILTER_XTABLES
841 depends on NETFILTER_ADVANCED
842 depends on IP_NF_MANGLE
843 select NF_DEFRAG_IPV4
844 select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES
846 This option adds a `TPROXY' target, which is somewhat similar to
847 REDIRECT. It can only be used in the mangle table and is useful
848 to redirect traffic to a transparent proxy. It does _not_ depend
849 on Netfilter connection tracking and NAT, unlike REDIRECT.
850 For it to work you will have to configure certain iptables rules
851 and use policy routing. For more information on how to set it up
852 see Documentation/networking/tproxy.txt.
854 To compile it as a module, choose M here. If unsure, say N.
856 config NETFILTER_XT_TARGET_TRACE
857 tristate '"TRACE" target support'
858 depends on IP_NF_RAW || IP6_NF_RAW
859 depends on NETFILTER_ADVANCED
861 The TRACE target allows you to mark packets so that the kernel
862 will log every rule which match the packets as those traverse
863 the tables, chains, rules.
865 If you want to compile it as a module, say M here and read
866 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
868 config NETFILTER_XT_TARGET_SECMARK
869 tristate '"SECMARK" target support'
870 depends on NETWORK_SECMARK
871 default m if NETFILTER_ADVANCED=n
873 The SECMARK target allows security marking of network
874 packets, for use with security subsystems.
876 To compile it as a module, choose M here. If unsure, say N.
878 config NETFILTER_XT_TARGET_TCPMSS
879 tristate '"TCPMSS" target support'
880 depends on (IPV6 || IPV6=n)
881 default m if NETFILTER_ADVANCED=n
883 This option adds a `TCPMSS' target, which allows you to alter the
884 MSS value of TCP SYN packets, to control the maximum size for that
885 connection (usually limiting it to your outgoing interface's MTU
888 This is used to overcome criminally braindead ISPs or servers which
889 block ICMP Fragmentation Needed packets. The symptoms of this
890 problem are that everything works fine from your Linux
891 firewall/router, but machines behind it can never exchange large
893 1) Web browsers connect, then hang with no data received.
894 2) Small mail works fine, but large emails hang.
895 3) ssh works fine, but scp hangs after initial handshaking.
897 Workaround: activate this option and add a rule to your firewall
900 iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
901 -j TCPMSS --clamp-mss-to-pmtu
903 To compile it as a module, choose M here. If unsure, say N.
905 config NETFILTER_XT_TARGET_TCPOPTSTRIP
906 tristate '"TCPOPTSTRIP" target support'
907 depends on IP_NF_MANGLE || IP6_NF_MANGLE
908 depends on NETFILTER_ADVANCED
910 This option adds a "TCPOPTSTRIP" target, which allows you to strip
911 TCP options from TCP packets.
913 # alphabetically ordered list of matches
915 comment "Xtables matches"
917 config NETFILTER_XT_MATCH_ADDRTYPE
918 tristate '"addrtype" address type match support'
919 depends on NETFILTER_ADVANCED
921 This option allows you to match what routing thinks of an address,
922 eg. UNICAST, LOCAL, BROADCAST, ...
924 If you want to compile it as a module, say M here and read
925 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
927 config NETFILTER_XT_MATCH_BPF
928 tristate '"bpf" match support'
929 depends on NETFILTER_ADVANCED
931 BPF matching applies a linux socket filter to each packet and
932 accepts those for which the filter returns non-zero.
934 To compile it as a module, choose M here. If unsure, say N.
936 config NETFILTER_XT_MATCH_CGROUP
937 tristate '"control group" match support'
938 depends on NETFILTER_ADVANCED
940 select CGROUP_NET_CLASSID
942 Socket/process control group matching allows you to match locally
943 generated packets based on which net_cls control group processes
946 config NETFILTER_XT_MATCH_CLUSTER
947 tristate '"cluster" match support'
948 depends on NF_CONNTRACK
949 depends on NETFILTER_ADVANCED
951 This option allows you to build work-load-sharing clusters of
952 network servers/stateful firewalls without having a dedicated
953 load-balancing router/server/switch. Basically, this match returns
954 true when the packet must be handled by this cluster node. Thus,
955 all nodes see all packets and this match decides which node handles
956 what packets. The work-load sharing algorithm is based on source
959 If you say Y or M here, try `iptables -m cluster --help` for
962 config NETFILTER_XT_MATCH_COMMENT
963 tristate '"comment" match support'
964 depends on NETFILTER_ADVANCED
966 This option adds a `comment' dummy-match, which allows you to put
967 comments in your iptables ruleset.
969 If you want to compile it as a module, say M here and read
970 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
972 config NETFILTER_XT_MATCH_CONNBYTES
973 tristate '"connbytes" per-connection counter match support'
974 depends on NF_CONNTRACK
975 depends on NETFILTER_ADVANCED
977 This option adds a `connbytes' match, which allows you to match the
978 number of bytes and/or packets for each direction within a connection.
980 If you want to compile it as a module, say M here and read
981 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
983 config NETFILTER_XT_MATCH_CONNLABEL
984 tristate '"connlabel" match support'
985 select NF_CONNTRACK_LABELS
986 depends on NF_CONNTRACK
987 depends on NETFILTER_ADVANCED
989 This match allows you to test and assign userspace-defined labels names
990 to a connection. The kernel only stores bit values - mapping
991 names to bits is done by userspace.
993 Unlike connmark, more than 32 flag bits may be assigned to a
994 connection simultaneously.
996 config NETFILTER_XT_MATCH_CONNLIMIT
997 tristate '"connlimit" match support'
998 depends on NF_CONNTRACK
999 depends on NETFILTER_ADVANCED
1001 This match allows you to match against the number of parallel
1002 connections to a server per client IP address (or address block).
1004 config NETFILTER_XT_MATCH_CONNMARK
1005 tristate '"connmark" connection mark match support'
1006 depends on NF_CONNTRACK
1007 depends on NETFILTER_ADVANCED
1008 select NETFILTER_XT_CONNMARK
1010 This is a backwards-compat option for the user's convenience
1011 (e.g. when running oldconfig). It selects
1012 CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
1014 config NETFILTER_XT_MATCH_CONNTRACK
1015 tristate '"conntrack" connection tracking match support'
1016 depends on NF_CONNTRACK
1017 default m if NETFILTER_ADVANCED=n
1019 This is a general conntrack match module, a superset of the state match.
1021 It allows matching on additional conntrack information, which is
1022 useful in complex configurations, such as NAT gateways with multiple
1023 internet links or tunnels.
1025 To compile it as a module, choose M here. If unsure, say N.
1027 config NETFILTER_XT_MATCH_CPU
1028 tristate '"cpu" match support'
1029 depends on NETFILTER_ADVANCED
1031 CPU matching allows you to match packets based on the CPU
1032 currently handling the packet.
1034 To compile it as a module, choose M here. If unsure, say N.
1036 config NETFILTER_XT_MATCH_DCCP
1037 tristate '"dccp" protocol match support'
1038 depends on NETFILTER_ADVANCED
1041 With this option enabled, you will be able to use the iptables
1042 `dccp' match in order to match on DCCP source/destination ports
1045 If you want to compile it as a module, say M here and read
1046 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1048 config NETFILTER_XT_MATCH_DEVGROUP
1049 tristate '"devgroup" match support'
1050 depends on NETFILTER_ADVANCED
1052 This options adds a `devgroup' match, which allows to match on the
1053 device group a network device is assigned to.
1055 To compile it as a module, choose M here. If unsure, say N.
1057 config NETFILTER_XT_MATCH_DSCP
1058 tristate '"dscp" and "tos" match support'
1059 depends on NETFILTER_ADVANCED
1061 This option adds a `DSCP' match, which allows you to match against
1062 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
1064 The DSCP field can have any value between 0x0 and 0x3f inclusive.
1066 It will also add a "tos" match, which allows you to match packets
1067 based on the Type Of Service fields of the IPv4 packet (which share
1068 the same bits as DSCP).
1070 To compile it as a module, choose M here. If unsure, say N.
1072 config NETFILTER_XT_MATCH_ECN
1073 tristate '"ecn" match support'
1074 depends on NETFILTER_ADVANCED
1076 This option adds an "ECN" match, which allows you to match against
1077 the IPv4 and TCP header ECN fields.
1079 To compile it as a module, choose M here. If unsure, say N.
1081 config NETFILTER_XT_MATCH_ESP
1082 tristate '"esp" match support'
1083 depends on NETFILTER_ADVANCED
1085 This match extension allows you to match a range of SPIs
1086 inside ESP header of IPSec packets.
1088 To compile it as a module, choose M here. If unsure, say N.
1090 config NETFILTER_XT_MATCH_HASHLIMIT
1091 tristate '"hashlimit" match support'
1092 depends on (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
1093 depends on NETFILTER_ADVANCED
1095 This option adds a `hashlimit' match.
1097 As opposed to `limit', this match dynamically creates a hash table
1098 of limit buckets, based on your selection of source/destination
1099 addresses and/or ports.
1101 It enables you to express policies like `10kpps for any given
1102 destination address' or `500pps from any given source address'
1105 config NETFILTER_XT_MATCH_HELPER
1106 tristate '"helper" match support'
1107 depends on NF_CONNTRACK
1108 depends on NETFILTER_ADVANCED
1110 Helper matching allows you to match packets in dynamic connections
1111 tracked by a conntrack-helper, ie. ip_conntrack_ftp
1113 To compile it as a module, choose M here. If unsure, say Y.
1115 config NETFILTER_XT_MATCH_HL
1116 tristate '"hl" hoplimit/TTL match support'
1117 depends on NETFILTER_ADVANCED
1119 HL matching allows you to match packets based on the hoplimit
1120 in the IPv6 header, or the time-to-live field in the IPv4
1121 header of the packet.
1123 config NETFILTER_XT_MATCH_IPCOMP
1124 tristate '"ipcomp" match support'
1125 depends on NETFILTER_ADVANCED
1127 This match extension allows you to match a range of CPIs(16 bits)
1128 inside IPComp header of IPSec packets.
1130 To compile it as a module, choose M here. If unsure, say N.
1132 config NETFILTER_XT_MATCH_IPRANGE
1133 tristate '"iprange" address range match support'
1134 depends on NETFILTER_ADVANCED
1136 This option adds a "iprange" match, which allows you to match based on
1137 an IP address range. (Normal iptables only matches on single addresses
1138 with an optional mask.)
1142 config NETFILTER_XT_MATCH_IPVS
1143 tristate '"ipvs" match support'
1145 depends on NETFILTER_ADVANCED
1146 depends on NF_CONNTRACK
1148 This option allows you to match against IPVS properties of a packet.
1152 config NETFILTER_XT_MATCH_L2TP
1153 tristate '"l2tp" match support'
1154 depends on NETFILTER_ADVANCED
1157 This option adds an "L2TP" match, which allows you to match against
1158 L2TP protocol header fields.
1160 To compile it as a module, choose M here. If unsure, say N.
1162 config NETFILTER_XT_MATCH_LENGTH
1163 tristate '"length" match support'
1164 depends on NETFILTER_ADVANCED
1166 This option allows you to match the length of a packet against a
1167 specific value or range of values.
1169 To compile it as a module, choose M here. If unsure, say N.
1171 config NETFILTER_XT_MATCH_LIMIT
1172 tristate '"limit" match support'
1173 depends on NETFILTER_ADVANCED
1175 limit matching allows you to control the rate at which a rule can be
1176 matched: mainly useful in combination with the LOG target ("LOG
1177 target support", below) and to avoid some Denial of Service attacks.
1179 To compile it as a module, choose M here. If unsure, say N.
1181 config NETFILTER_XT_MATCH_MAC
1182 tristate '"mac" address match support'
1183 depends on NETFILTER_ADVANCED
1185 MAC matching allows you to match packets based on the source
1186 Ethernet address of the packet.
1188 To compile it as a module, choose M here. If unsure, say N.
1190 config NETFILTER_XT_MATCH_MARK
1191 tristate '"mark" match support'
1192 depends on NETFILTER_ADVANCED
1193 select NETFILTER_XT_MARK
1195 This is a backwards-compat option for the user's convenience
1196 (e.g. when running oldconfig). It selects
1197 CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
1199 config NETFILTER_XT_MATCH_MULTIPORT
1200 tristate '"multiport" Multiple port match support'
1201 depends on NETFILTER_ADVANCED
1203 Multiport matching allows you to match TCP or UDP packets based on
1204 a series of source or destination ports: normally a rule can only
1205 match a single range of ports.
1207 To compile it as a module, choose M here. If unsure, say N.
1209 config NETFILTER_XT_MATCH_NFACCT
1210 tristate '"nfacct" match support'
1211 depends on NETFILTER_ADVANCED
1212 select NETFILTER_NETLINK_ACCT
1214 This option allows you to use the extended accounting through
1217 To compile it as a module, choose M here. If unsure, say N.
1219 config NETFILTER_XT_MATCH_OSF
1220 tristate '"osf" Passive OS fingerprint match'
1221 depends on NETFILTER_ADVANCED && NETFILTER_NETLINK
1223 This option selects the Passive OS Fingerprinting match module
1224 that allows to passively match the remote operating system by
1225 analyzing incoming TCP SYN packets.
1227 Rules and loading software can be downloaded from
1228 http://www.ioremap.net/projects/osf
1230 To compile it as a module, choose M here. If unsure, say N.
1232 config NETFILTER_XT_MATCH_OWNER
1233 tristate '"owner" match support'
1234 depends on NETFILTER_ADVANCED
1236 Socket owner matching allows you to match locally-generated packets
1237 based on who created the socket: the user or group. It is also
1238 possible to check whether a socket actually exists.
1240 config NETFILTER_XT_MATCH_POLICY
1241 tristate 'IPsec "policy" match support'
1243 default m if NETFILTER_ADVANCED=n
1245 Policy matching allows you to match packets based on the
1246 IPsec policy that was used during decapsulation/will
1247 be used during encapsulation.
1249 To compile it as a module, choose M here. If unsure, say N.
1251 config NETFILTER_XT_MATCH_PHYSDEV
1252 tristate '"physdev" match support'
1253 depends on BRIDGE && BRIDGE_NETFILTER
1254 depends on NETFILTER_ADVANCED
1256 Physdev packet matching matches against the physical bridge ports
1257 the IP packet arrived on or will leave by.
1259 To compile it as a module, choose M here. If unsure, say N.
1261 config NETFILTER_XT_MATCH_PKTTYPE
1262 tristate '"pkttype" packet type match support'
1263 depends on NETFILTER_ADVANCED
1265 Packet type matching allows you to match a packet by
1266 its "class", eg. BROADCAST, MULTICAST, ...
1269 iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG
1271 To compile it as a module, choose M here. If unsure, say N.
1273 config NETFILTER_XT_MATCH_QUOTA
1274 tristate '"quota" match support'
1275 depends on NETFILTER_ADVANCED
1277 This option adds a `quota' match, which allows to match on a
1280 If you want to compile it as a module, say M here and read
1281 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1283 config NETFILTER_XT_MATCH_RATEEST
1284 tristate '"rateest" match support'
1285 depends on NETFILTER_ADVANCED
1286 select NETFILTER_XT_TARGET_RATEEST
1288 This option adds a `rateest' match, which allows to match on the
1289 rate estimated by the RATEEST target.
1291 To compile it as a module, choose M here. If unsure, say N.
1293 config NETFILTER_XT_MATCH_REALM
1294 tristate '"realm" match support'
1295 depends on NETFILTER_ADVANCED
1296 select IP_ROUTE_CLASSID
1298 This option adds a `realm' match, which allows you to use the realm
1299 key from the routing subsystem inside iptables.
1301 This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option
1304 If you want to compile it as a module, say M here and read
1305 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1307 config NETFILTER_XT_MATCH_RECENT
1308 tristate '"recent" match support'
1309 depends on NETFILTER_ADVANCED
1311 This match is used for creating one or many lists of recently
1312 used addresses and then matching against that/those list(s).
1314 Short options are available by using 'iptables -m recent -h'
1315 Official Website: <http://snowman.net/projects/ipt_recent/>
1317 config NETFILTER_XT_MATCH_SCTP
1318 tristate '"sctp" protocol match support'
1319 depends on NETFILTER_ADVANCED
1322 With this option enabled, you will be able to use the
1323 `sctp' match in order to match on SCTP source/destination ports
1324 and SCTP chunk types.
1326 If you want to compile it as a module, say M here and read
1327 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1329 config NETFILTER_XT_MATCH_SOCKET
1330 tristate '"socket" match support'
1331 depends on NETFILTER_XTABLES
1332 depends on NETFILTER_ADVANCED
1333 depends on !NF_CONNTRACK || NF_CONNTRACK
1334 depends on (IPV6 || IPV6=n)
1335 select NF_DEFRAG_IPV4
1336 select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES
1338 This option adds a `socket' match, which can be used to match
1339 packets for which a TCP or UDP socket lookup finds a valid socket.
1340 It can be used in combination with the MARK target and policy
1341 routing to implement full featured non-locally bound sockets.
1343 To compile it as a module, choose M here. If unsure, say N.
1345 config NETFILTER_XT_MATCH_STATE
1346 tristate '"state" match support'
1347 depends on NF_CONNTRACK
1348 default m if NETFILTER_ADVANCED=n
1350 Connection state matching allows you to match packets based on their
1351 relationship to a tracked connection (ie. previous packets). This
1352 is a powerful tool for packet classification.
1354 To compile it as a module, choose M here. If unsure, say N.
1356 config NETFILTER_XT_MATCH_STATISTIC
1357 tristate '"statistic" match support'
1358 depends on NETFILTER_ADVANCED
1360 This option adds a `statistic' match, which allows you to match
1361 on packets periodically or randomly with a given percentage.
1363 To compile it as a module, choose M here. If unsure, say N.
1365 config NETFILTER_XT_MATCH_STRING
1366 tristate '"string" match support'
1367 depends on NETFILTER_ADVANCED
1369 select TEXTSEARCH_KMP
1370 select TEXTSEARCH_BM
1371 select TEXTSEARCH_FSM
1373 This option adds a `string' match, which allows you to look for
1374 pattern matchings in packets.
1376 To compile it as a module, choose M here. If unsure, say N.
1378 config NETFILTER_XT_MATCH_TCPMSS
1379 tristate '"tcpmss" match support'
1380 depends on NETFILTER_ADVANCED
1382 This option adds a `tcpmss' match, which allows you to examine the
1383 MSS value of TCP SYN packets, which control the maximum packet size
1384 for that connection.
1386 To compile it as a module, choose M here. If unsure, say N.
1388 config NETFILTER_XT_MATCH_TIME
1389 tristate '"time" match support'
1390 depends on NETFILTER_ADVANCED
1392 This option adds a "time" match, which allows you to match based on
1393 the packet arrival time (at the machine which netfilter is running)
1394 on) or departure time/date (for locally generated packets).
1396 If you say Y here, try `iptables -m time --help` for
1399 If you want to compile it as a module, say M here.
1402 config NETFILTER_XT_MATCH_U32
1403 tristate '"u32" match support'
1404 depends on NETFILTER_ADVANCED
1406 u32 allows you to extract quantities of up to 4 bytes from a packet,
1407 AND them with specified masks, shift them by specified amounts and
1408 test whether the results are in any of a set of specified ranges.
1409 The specification of what to extract is general enough to skip over
1410 headers with lengths stored in the packet, as in IP or TCP header
1413 Details and examples are in the kernel module source.
1415 endif # NETFILTER_XTABLES
1419 source "net/netfilter/ipset/Kconfig"
1421 source "net/netfilter/ipvs/Kconfig"