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"
750 depends on NF_LOG_IPV4 && NF_LOG_IPV6
751 default m if NETFILTER_ADVANCED=n
753 This option adds a `LOG' target, which allows you to create rules in
754 any iptables table which records the packet header to the syslog.
756 To compile it as a module, choose M here. If unsure, say N.
758 config NETFILTER_XT_TARGET_MARK
759 tristate '"MARK" target support'
760 depends on NETFILTER_ADVANCED
761 select NETFILTER_XT_MARK
763 This is a backwards-compat option for the user's convenience
764 (e.g. when running oldconfig). It selects
765 CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
767 config NETFILTER_XT_TARGET_NETMAP
768 tristate '"NETMAP" target support'
771 NETMAP is an implementation of static 1:1 NAT mapping of network
772 addresses. It maps the network address part, while keeping the host
775 To compile it as a module, choose M here. If unsure, say N.
777 config NETFILTER_XT_TARGET_NFLOG
778 tristate '"NFLOG" target support'
779 default m if NETFILTER_ADVANCED=n
780 select NETFILTER_NETLINK_LOG
782 This option enables the NFLOG target, which allows to LOG
783 messages through nfnetlink_log.
785 To compile it as a module, choose M here. If unsure, say N.
787 config NETFILTER_XT_TARGET_NFQUEUE
788 tristate '"NFQUEUE" target Support'
789 depends on NETFILTER_ADVANCED
790 select NETFILTER_NETLINK_QUEUE
792 This target replaced the old obsolete QUEUE target.
794 As opposed to QUEUE, it supports 65535 different queues,
797 To compile it as a module, choose M here. If unsure, say N.
799 config NETFILTER_XT_TARGET_NOTRACK
800 tristate '"NOTRACK" target support (DEPRECATED)'
801 depends on NF_CONNTRACK
802 depends on IP_NF_RAW || IP6_NF_RAW
803 depends on NETFILTER_ADVANCED
804 select NETFILTER_XT_TARGET_CT
806 config NETFILTER_XT_TARGET_RATEEST
807 tristate '"RATEEST" target support'
808 depends on NETFILTER_ADVANCED
810 This option adds a `RATEEST' target, which allows to measure
811 rates similar to TC estimators. The `rateest' match can be
812 used to match on the measured rates.
814 To compile it as a module, choose M here. If unsure, say N.
816 config NETFILTER_XT_TARGET_REDIRECT
817 tristate "REDIRECT target support"
820 REDIRECT is a special case of NAT: all incoming connections are
821 mapped onto the incoming interface's address, causing the packets to
822 come to the local machine instead of passing through. This is
823 useful for transparent proxies.
825 To compile it as a module, choose M here. If unsure, say N.
827 config NETFILTER_XT_TARGET_TEE
828 tristate '"TEE" - packet cloning to alternate destination'
829 depends on NETFILTER_ADVANCED
830 depends on (IPV6 || IPV6=n)
831 depends on !NF_CONNTRACK || NF_CONNTRACK
833 This option adds a "TEE" target with which a packet can be cloned and
834 this clone be rerouted to another nexthop.
836 config NETFILTER_XT_TARGET_TPROXY
837 tristate '"TPROXY" target transparent proxying support'
838 depends on NETFILTER_XTABLES
839 depends on NETFILTER_ADVANCED
840 depends on IP_NF_MANGLE
841 select NF_DEFRAG_IPV4
842 select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES
844 This option adds a `TPROXY' target, which is somewhat similar to
845 REDIRECT. It can only be used in the mangle table and is useful
846 to redirect traffic to a transparent proxy. It does _not_ depend
847 on Netfilter connection tracking and NAT, unlike REDIRECT.
848 For it to work you will have to configure certain iptables rules
849 and use policy routing. For more information on how to set it up
850 see Documentation/networking/tproxy.txt.
852 To compile it as a module, choose M here. If unsure, say N.
854 config NETFILTER_XT_TARGET_TRACE
855 tristate '"TRACE" target support'
856 depends on IP_NF_RAW || IP6_NF_RAW
857 depends on NETFILTER_ADVANCED
859 The TRACE target allows you to mark packets so that the kernel
860 will log every rule which match the packets as those traverse
861 the tables, chains, rules.
863 If you want to compile it as a module, say M here and read
864 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
866 config NETFILTER_XT_TARGET_SECMARK
867 tristate '"SECMARK" target support'
868 depends on NETWORK_SECMARK
869 default m if NETFILTER_ADVANCED=n
871 The SECMARK target allows security marking of network
872 packets, for use with security subsystems.
874 To compile it as a module, choose M here. If unsure, say N.
876 config NETFILTER_XT_TARGET_TCPMSS
877 tristate '"TCPMSS" target support'
878 depends on (IPV6 || IPV6=n)
879 default m if NETFILTER_ADVANCED=n
881 This option adds a `TCPMSS' target, which allows you to alter the
882 MSS value of TCP SYN packets, to control the maximum size for that
883 connection (usually limiting it to your outgoing interface's MTU
886 This is used to overcome criminally braindead ISPs or servers which
887 block ICMP Fragmentation Needed packets. The symptoms of this
888 problem are that everything works fine from your Linux
889 firewall/router, but machines behind it can never exchange large
891 1) Web browsers connect, then hang with no data received.
892 2) Small mail works fine, but large emails hang.
893 3) ssh works fine, but scp hangs after initial handshaking.
895 Workaround: activate this option and add a rule to your firewall
898 iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
899 -j TCPMSS --clamp-mss-to-pmtu
901 To compile it as a module, choose M here. If unsure, say N.
903 config NETFILTER_XT_TARGET_TCPOPTSTRIP
904 tristate '"TCPOPTSTRIP" target support'
905 depends on IP_NF_MANGLE || IP6_NF_MANGLE
906 depends on NETFILTER_ADVANCED
908 This option adds a "TCPOPTSTRIP" target, which allows you to strip
909 TCP options from TCP packets.
911 # alphabetically ordered list of matches
913 comment "Xtables matches"
915 config NETFILTER_XT_MATCH_ADDRTYPE
916 tristate '"addrtype" address type match support'
917 depends on NETFILTER_ADVANCED
919 This option allows you to match what routing thinks of an address,
920 eg. UNICAST, LOCAL, BROADCAST, ...
922 If you want to compile it as a module, say M here and read
923 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
925 config NETFILTER_XT_MATCH_BPF
926 tristate '"bpf" match support'
927 depends on NETFILTER_ADVANCED
929 BPF matching applies a linux socket filter to each packet and
930 accepts those for which the filter returns non-zero.
932 To compile it as a module, choose M here. If unsure, say N.
934 config NETFILTER_XT_MATCH_CGROUP
935 tristate '"control group" match support'
936 depends on NETFILTER_ADVANCED
938 select CGROUP_NET_CLASSID
940 Socket/process control group matching allows you to match locally
941 generated packets based on which net_cls control group processes
944 config NETFILTER_XT_MATCH_CLUSTER
945 tristate '"cluster" match support'
946 depends on NF_CONNTRACK
947 depends on NETFILTER_ADVANCED
949 This option allows you to build work-load-sharing clusters of
950 network servers/stateful firewalls without having a dedicated
951 load-balancing router/server/switch. Basically, this match returns
952 true when the packet must be handled by this cluster node. Thus,
953 all nodes see all packets and this match decides which node handles
954 what packets. The work-load sharing algorithm is based on source
957 If you say Y or M here, try `iptables -m cluster --help` for
960 config NETFILTER_XT_MATCH_COMMENT
961 tristate '"comment" match support'
962 depends on NETFILTER_ADVANCED
964 This option adds a `comment' dummy-match, which allows you to put
965 comments in your iptables ruleset.
967 If you want to compile it as a module, say M here and read
968 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
970 config NETFILTER_XT_MATCH_CONNBYTES
971 tristate '"connbytes" per-connection counter match support'
972 depends on NF_CONNTRACK
973 depends on NETFILTER_ADVANCED
975 This option adds a `connbytes' match, which allows you to match the
976 number of bytes and/or packets for each direction within a connection.
978 If you want to compile it as a module, say M here and read
979 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
981 config NETFILTER_XT_MATCH_CONNLABEL
982 tristate '"connlabel" match support'
983 select NF_CONNTRACK_LABELS
984 depends on NF_CONNTRACK
985 depends on NETFILTER_ADVANCED
987 This match allows you to test and assign userspace-defined labels names
988 to a connection. The kernel only stores bit values - mapping
989 names to bits is done by userspace.
991 Unlike connmark, more than 32 flag bits may be assigned to a
992 connection simultaneously.
994 config NETFILTER_XT_MATCH_CONNLIMIT
995 tristate '"connlimit" match support'
996 depends on NF_CONNTRACK
997 depends on NETFILTER_ADVANCED
999 This match allows you to match against the number of parallel
1000 connections to a server per client IP address (or address block).
1002 config NETFILTER_XT_MATCH_CONNMARK
1003 tristate '"connmark" connection mark match support'
1004 depends on NF_CONNTRACK
1005 depends on NETFILTER_ADVANCED
1006 select NETFILTER_XT_CONNMARK
1008 This is a backwards-compat option for the user's convenience
1009 (e.g. when running oldconfig). It selects
1010 CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
1012 config NETFILTER_XT_MATCH_CONNTRACK
1013 tristate '"conntrack" connection tracking match support'
1014 depends on NF_CONNTRACK
1015 default m if NETFILTER_ADVANCED=n
1017 This is a general conntrack match module, a superset of the state match.
1019 It allows matching on additional conntrack information, which is
1020 useful in complex configurations, such as NAT gateways with multiple
1021 internet links or tunnels.
1023 To compile it as a module, choose M here. If unsure, say N.
1025 config NETFILTER_XT_MATCH_CPU
1026 tristate '"cpu" match support'
1027 depends on NETFILTER_ADVANCED
1029 CPU matching allows you to match packets based on the CPU
1030 currently handling the packet.
1032 To compile it as a module, choose M here. If unsure, say N.
1034 config NETFILTER_XT_MATCH_DCCP
1035 tristate '"dccp" protocol match support'
1036 depends on NETFILTER_ADVANCED
1039 With this option enabled, you will be able to use the iptables
1040 `dccp' match in order to match on DCCP source/destination ports
1043 If you want to compile it as a module, say M here and read
1044 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1046 config NETFILTER_XT_MATCH_DEVGROUP
1047 tristate '"devgroup" match support'
1048 depends on NETFILTER_ADVANCED
1050 This options adds a `devgroup' match, which allows to match on the
1051 device group a network device is assigned to.
1053 To compile it as a module, choose M here. If unsure, say N.
1055 config NETFILTER_XT_MATCH_DSCP
1056 tristate '"dscp" and "tos" match support'
1057 depends on NETFILTER_ADVANCED
1059 This option adds a `DSCP' match, which allows you to match against
1060 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
1062 The DSCP field can have any value between 0x0 and 0x3f inclusive.
1064 It will also add a "tos" match, which allows you to match packets
1065 based on the Type Of Service fields of the IPv4 packet (which share
1066 the same bits as DSCP).
1068 To compile it as a module, choose M here. If unsure, say N.
1070 config NETFILTER_XT_MATCH_ECN
1071 tristate '"ecn" match support'
1072 depends on NETFILTER_ADVANCED
1074 This option adds an "ECN" match, which allows you to match against
1075 the IPv4 and TCP header ECN fields.
1077 To compile it as a module, choose M here. If unsure, say N.
1079 config NETFILTER_XT_MATCH_ESP
1080 tristate '"esp" match support'
1081 depends on NETFILTER_ADVANCED
1083 This match extension allows you to match a range of SPIs
1084 inside ESP header of IPSec packets.
1086 To compile it as a module, choose M here. If unsure, say N.
1088 config NETFILTER_XT_MATCH_HASHLIMIT
1089 tristate '"hashlimit" match support'
1090 depends on (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
1091 depends on NETFILTER_ADVANCED
1093 This option adds a `hashlimit' match.
1095 As opposed to `limit', this match dynamically creates a hash table
1096 of limit buckets, based on your selection of source/destination
1097 addresses and/or ports.
1099 It enables you to express policies like `10kpps for any given
1100 destination address' or `500pps from any given source address'
1103 config NETFILTER_XT_MATCH_HELPER
1104 tristate '"helper" match support'
1105 depends on NF_CONNTRACK
1106 depends on NETFILTER_ADVANCED
1108 Helper matching allows you to match packets in dynamic connections
1109 tracked by a conntrack-helper, ie. ip_conntrack_ftp
1111 To compile it as a module, choose M here. If unsure, say Y.
1113 config NETFILTER_XT_MATCH_HL
1114 tristate '"hl" hoplimit/TTL match support'
1115 depends on NETFILTER_ADVANCED
1117 HL matching allows you to match packets based on the hoplimit
1118 in the IPv6 header, or the time-to-live field in the IPv4
1119 header of the packet.
1121 config NETFILTER_XT_MATCH_IPCOMP
1122 tristate '"ipcomp" match support'
1123 depends on NETFILTER_ADVANCED
1125 This match extension allows you to match a range of CPIs(16 bits)
1126 inside IPComp header of IPSec packets.
1128 To compile it as a module, choose M here. If unsure, say N.
1130 config NETFILTER_XT_MATCH_IPRANGE
1131 tristate '"iprange" address range match support'
1132 depends on NETFILTER_ADVANCED
1134 This option adds a "iprange" match, which allows you to match based on
1135 an IP address range. (Normal iptables only matches on single addresses
1136 with an optional mask.)
1140 config NETFILTER_XT_MATCH_IPVS
1141 tristate '"ipvs" match support'
1143 depends on NETFILTER_ADVANCED
1144 depends on NF_CONNTRACK
1146 This option allows you to match against IPVS properties of a packet.
1150 config NETFILTER_XT_MATCH_L2TP
1151 tristate '"l2tp" match support'
1152 depends on NETFILTER_ADVANCED
1155 This option adds an "L2TP" match, which allows you to match against
1156 L2TP protocol header fields.
1158 To compile it as a module, choose M here. If unsure, say N.
1160 config NETFILTER_XT_MATCH_LENGTH
1161 tristate '"length" match support'
1162 depends on NETFILTER_ADVANCED
1164 This option allows you to match the length of a packet against a
1165 specific value or range of values.
1167 To compile it as a module, choose M here. If unsure, say N.
1169 config NETFILTER_XT_MATCH_LIMIT
1170 tristate '"limit" match support'
1171 depends on NETFILTER_ADVANCED
1173 limit matching allows you to control the rate at which a rule can be
1174 matched: mainly useful in combination with the LOG target ("LOG
1175 target support", below) and to avoid some Denial of Service attacks.
1177 To compile it as a module, choose M here. If unsure, say N.
1179 config NETFILTER_XT_MATCH_MAC
1180 tristate '"mac" address match support'
1181 depends on NETFILTER_ADVANCED
1183 MAC matching allows you to match packets based on the source
1184 Ethernet address of the packet.
1186 To compile it as a module, choose M here. If unsure, say N.
1188 config NETFILTER_XT_MATCH_MARK
1189 tristate '"mark" match support'
1190 depends on NETFILTER_ADVANCED
1191 select NETFILTER_XT_MARK
1193 This is a backwards-compat option for the user's convenience
1194 (e.g. when running oldconfig). It selects
1195 CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
1197 config NETFILTER_XT_MATCH_MULTIPORT
1198 tristate '"multiport" Multiple port match support'
1199 depends on NETFILTER_ADVANCED
1201 Multiport matching allows you to match TCP or UDP packets based on
1202 a series of source or destination ports: normally a rule can only
1203 match a single range of ports.
1205 To compile it as a module, choose M here. If unsure, say N.
1207 config NETFILTER_XT_MATCH_NFACCT
1208 tristate '"nfacct" match support'
1209 depends on NETFILTER_ADVANCED
1210 select NETFILTER_NETLINK_ACCT
1212 This option allows you to use the extended accounting through
1215 To compile it as a module, choose M here. If unsure, say N.
1217 config NETFILTER_XT_MATCH_OSF
1218 tristate '"osf" Passive OS fingerprint match'
1219 depends on NETFILTER_ADVANCED && NETFILTER_NETLINK
1221 This option selects the Passive OS Fingerprinting match module
1222 that allows to passively match the remote operating system by
1223 analyzing incoming TCP SYN packets.
1225 Rules and loading software can be downloaded from
1226 http://www.ioremap.net/projects/osf
1228 To compile it as a module, choose M here. If unsure, say N.
1230 config NETFILTER_XT_MATCH_OWNER
1231 tristate '"owner" match support'
1232 depends on NETFILTER_ADVANCED
1234 Socket owner matching allows you to match locally-generated packets
1235 based on who created the socket: the user or group. It is also
1236 possible to check whether a socket actually exists.
1238 config NETFILTER_XT_MATCH_POLICY
1239 tristate 'IPsec "policy" match support'
1241 default m if NETFILTER_ADVANCED=n
1243 Policy matching allows you to match packets based on the
1244 IPsec policy that was used during decapsulation/will
1245 be used during encapsulation.
1247 To compile it as a module, choose M here. If unsure, say N.
1249 config NETFILTER_XT_MATCH_PHYSDEV
1250 tristate '"physdev" match support'
1251 depends on BRIDGE && BRIDGE_NETFILTER
1252 depends on NETFILTER_ADVANCED
1254 Physdev packet matching matches against the physical bridge ports
1255 the IP packet arrived on or will leave by.
1257 To compile it as a module, choose M here. If unsure, say N.
1259 config NETFILTER_XT_MATCH_PKTTYPE
1260 tristate '"pkttype" packet type match support'
1261 depends on NETFILTER_ADVANCED
1263 Packet type matching allows you to match a packet by
1264 its "class", eg. BROADCAST, MULTICAST, ...
1267 iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG
1269 To compile it as a module, choose M here. If unsure, say N.
1271 config NETFILTER_XT_MATCH_QUOTA
1272 tristate '"quota" match support'
1273 depends on NETFILTER_ADVANCED
1275 This option adds a `quota' match, which allows to match on a
1278 If you want to compile it as a module, say M here and read
1279 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1281 config NETFILTER_XT_MATCH_RATEEST
1282 tristate '"rateest" match support'
1283 depends on NETFILTER_ADVANCED
1284 select NETFILTER_XT_TARGET_RATEEST
1286 This option adds a `rateest' match, which allows to match on the
1287 rate estimated by the RATEEST target.
1289 To compile it as a module, choose M here. If unsure, say N.
1291 config NETFILTER_XT_MATCH_REALM
1292 tristate '"realm" match support'
1293 depends on NETFILTER_ADVANCED
1294 select IP_ROUTE_CLASSID
1296 This option adds a `realm' match, which allows you to use the realm
1297 key from the routing subsystem inside iptables.
1299 This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option
1302 If you want to compile it as a module, say M here and read
1303 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1305 config NETFILTER_XT_MATCH_RECENT
1306 tristate '"recent" match support'
1307 depends on NETFILTER_ADVANCED
1309 This match is used for creating one or many lists of recently
1310 used addresses and then matching against that/those list(s).
1312 Short options are available by using 'iptables -m recent -h'
1313 Official Website: <http://snowman.net/projects/ipt_recent/>
1315 config NETFILTER_XT_MATCH_SCTP
1316 tristate '"sctp" protocol match support'
1317 depends on NETFILTER_ADVANCED
1320 With this option enabled, you will be able to use the
1321 `sctp' match in order to match on SCTP source/destination ports
1322 and SCTP chunk types.
1324 If you want to compile it as a module, say M here and read
1325 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1327 config NETFILTER_XT_MATCH_SOCKET
1328 tristate '"socket" match support'
1329 depends on NETFILTER_XTABLES
1330 depends on NETFILTER_ADVANCED
1331 depends on !NF_CONNTRACK || NF_CONNTRACK
1332 depends on (IPV6 || IPV6=n)
1333 select NF_DEFRAG_IPV4
1334 select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES
1336 This option adds a `socket' match, which can be used to match
1337 packets for which a TCP or UDP socket lookup finds a valid socket.
1338 It can be used in combination with the MARK target and policy
1339 routing to implement full featured non-locally bound sockets.
1341 To compile it as a module, choose M here. If unsure, say N.
1343 config NETFILTER_XT_MATCH_STATE
1344 tristate '"state" match support'
1345 depends on NF_CONNTRACK
1346 default m if NETFILTER_ADVANCED=n
1348 Connection state matching allows you to match packets based on their
1349 relationship to a tracked connection (ie. previous packets). This
1350 is a powerful tool for packet classification.
1352 To compile it as a module, choose M here. If unsure, say N.
1354 config NETFILTER_XT_MATCH_STATISTIC
1355 tristate '"statistic" match support'
1356 depends on NETFILTER_ADVANCED
1358 This option adds a `statistic' match, which allows you to match
1359 on packets periodically or randomly with a given percentage.
1361 To compile it as a module, choose M here. If unsure, say N.
1363 config NETFILTER_XT_MATCH_STRING
1364 tristate '"string" match support'
1365 depends on NETFILTER_ADVANCED
1367 select TEXTSEARCH_KMP
1368 select TEXTSEARCH_BM
1369 select TEXTSEARCH_FSM
1371 This option adds a `string' match, which allows you to look for
1372 pattern matchings in packets.
1374 To compile it as a module, choose M here. If unsure, say N.
1376 config NETFILTER_XT_MATCH_TCPMSS
1377 tristate '"tcpmss" match support'
1378 depends on NETFILTER_ADVANCED
1380 This option adds a `tcpmss' match, which allows you to examine the
1381 MSS value of TCP SYN packets, which control the maximum packet size
1382 for that connection.
1384 To compile it as a module, choose M here. If unsure, say N.
1386 config NETFILTER_XT_MATCH_TIME
1387 tristate '"time" match support'
1388 depends on NETFILTER_ADVANCED
1390 This option adds a "time" match, which allows you to match based on
1391 the packet arrival time (at the machine which netfilter is running)
1392 on) or departure time/date (for locally generated packets).
1394 If you say Y here, try `iptables -m time --help` for
1397 If you want to compile it as a module, say M here.
1400 config NETFILTER_XT_MATCH_U32
1401 tristate '"u32" match support'
1402 depends on NETFILTER_ADVANCED
1404 u32 allows you to extract quantities of up to 4 bytes from a packet,
1405 AND them with specified masks, shift them by specified amounts and
1406 test whether the results are in any of a set of specified ranges.
1407 The specification of what to extract is general enough to skip over
1408 headers with lengths stored in the packet, as in IP or TCP header
1411 Details and examples are in the kernel module source.
1413 endif # NETFILTER_XTABLES
1417 source "net/netfilter/ipset/Kconfig"
1419 source "net/netfilter/ipvs/Kconfig"