1 # SPDX-License-Identifier: GPL-2.0-only
2 menu "Core Netfilter Configuration"
3 depends on NET && INET && NETFILTER
5 config NETFILTER_INGRESS
6 bool "Netfilter ingress support"
10 This allows you to classify packets from ingress using the Netfilter
13 config NETFILTER_NETLINK
16 config NETFILTER_FAMILY_BRIDGE
19 config NETFILTER_FAMILY_ARP
22 config NETFILTER_NETLINK_ACCT
23 tristate "Netfilter NFACCT over NFNETLINK interface"
24 depends on NETFILTER_ADVANCED
25 select NETFILTER_NETLINK
27 If this option is enabled, the kernel will include support
28 for extended accounting via NFNETLINK.
30 config NETFILTER_NETLINK_QUEUE
31 tristate "Netfilter NFQUEUE over NFNETLINK interface"
32 depends on NETFILTER_ADVANCED
33 select NETFILTER_NETLINK
35 If this option is enabled, the kernel will include support
36 for queueing packets via NFNETLINK.
38 config NETFILTER_NETLINK_LOG
39 tristate "Netfilter LOG over NFNETLINK interface"
40 default m if NETFILTER_ADVANCED=n
41 select NETFILTER_NETLINK
43 If this option is enabled, the kernel will include support
44 for logging packets via NFNETLINK.
46 This obsoletes the existing ipt_ULOG and ebg_ulog mechanisms,
47 and is also scheduled to replace the old syslog-based ipt_LOG
50 config NETFILTER_NETLINK_OSF
51 tristate "Netfilter OSF over NFNETLINK interface"
52 depends on NETFILTER_ADVANCED
53 select NETFILTER_NETLINK
55 If this option is enabled, the kernel will include support
56 for passive OS fingerprint via NFNETLINK.
59 tristate "Netfilter connection tracking support"
60 default m if NETFILTER_ADVANCED=n
62 select NF_DEFRAG_IPV6 if IPV6 != n
64 Connection tracking keeps a record of what packets have passed
65 through your machine, in order to figure out how they are related
68 This is required to do Masquerading or other kinds of Network
69 Address Translation. It can also be used to enhance packet
70 filtering (see `Connection state match support' below).
72 To compile it as a module, choose M here. If unsure, say N.
78 tristate "Netdev packet logging"
82 config NETFILTER_CONNCOUNT
85 config NF_CONNTRACK_MARK
86 bool 'Connection mark tracking support'
87 depends on NETFILTER_ADVANCED
89 This option enables support for connection marks, used by the
90 `CONNMARK' target and `connmark' match. Similar to the mark value
91 of packets, but this mark value is kept in the conntrack session
92 instead of the individual packets.
94 config NF_CONNTRACK_SECMARK
95 bool 'Connection tracking security mark support'
96 depends on NETWORK_SECMARK
97 default m if NETFILTER_ADVANCED=n
99 This option enables security markings to be applied to
100 connections. Typically they are copied to connections from
101 packets using the CONNSECMARK target and copied back from
102 connections to packets with the same target, with the packets
103 being originally labeled via SECMARK.
107 config NF_CONNTRACK_ZONES
108 bool 'Connection tracking zones'
109 depends on NETFILTER_ADVANCED
111 This option enables support for connection tracking zones.
112 Normally, each connection needs to have a unique system wide
113 identity. Connection tracking zones allow to have multiple
114 connections using the same identity, as long as they are
115 contained in different zones.
119 config NF_CONNTRACK_PROCFS
120 bool "Supply CT list in procfs (OBSOLETE)"
124 This option enables for the list of known conntrack entries
125 to be shown in procfs under net/netfilter/nf_conntrack. This
126 is considered obsolete in favor of using the conntrack(8)
127 tool which uses Netlink.
129 config NF_CONNTRACK_EVENTS
130 bool "Connection tracking events"
131 depends on NETFILTER_ADVANCED
133 If this option is enabled, the connection tracking code will
134 provide a notifier chain that can be used by other kernel code
135 to get notified about changes in the connection tracking state.
139 config NF_CONNTRACK_TIMEOUT
140 bool 'Connection tracking timeout'
141 depends on NETFILTER_ADVANCED
143 This option enables support for connection tracking timeout
144 extension. This allows you to attach timeout policies to flow
149 config NF_CONNTRACK_TIMESTAMP
150 bool 'Connection tracking timestamping'
151 depends on NETFILTER_ADVANCED
153 This option enables support for connection tracking timestamping.
154 This allows you to store the flow start-time and to obtain
155 the flow-stop time (once it has been destroyed) via Connection
160 config NF_CONNTRACK_LABELS
161 bool "Connection tracking labels"
163 This option enables support for assigning user-defined flag bits
164 to connection tracking entries. It can be used with xtables connlabel
165 match and the nftables ct expression.
167 config NF_CT_PROTO_DCCP
168 bool 'DCCP protocol connection tracking support'
169 depends on NETFILTER_ADVANCED
172 With this option enabled, the layer 3 independent connection
173 tracking code will be able to do state tracking on DCCP connections.
177 config NF_CT_PROTO_GRE
180 config NF_CT_PROTO_SCTP
181 bool 'SCTP protocol connection tracking support'
182 depends on NETFILTER_ADVANCED
186 With this option enabled, the layer 3 independent connection
187 tracking code will be able to do state tracking on SCTP connections.
191 config NF_CT_PROTO_UDPLITE
192 bool 'UDP-Lite protocol connection tracking support'
193 depends on NETFILTER_ADVANCED
196 With this option enabled, the layer 3 independent connection
197 tracking code will be able to do state tracking on UDP-Lite
202 config NF_CONNTRACK_AMANDA
203 tristate "Amanda backup protocol support"
204 depends on NETFILTER_ADVANCED
206 select TEXTSEARCH_KMP
208 If you are running the Amanda backup package <http://www.amanda.org/>
209 on this machine or machines that will be MASQUERADED through this
210 machine, then you may want to enable this feature. This allows the
211 connection tracking and natting code to allow the sub-channels that
212 Amanda requires for communication of the backup data, messages and
215 To compile it as a module, choose M here. If unsure, say N.
217 config NF_CONNTRACK_FTP
218 tristate "FTP protocol support"
219 default m if NETFILTER_ADVANCED=n
221 Tracking FTP connections is problematic: special helpers are
222 required for tracking them, and doing masquerading and other forms
223 of Network Address Translation on them.
225 This is FTP support on Layer 3 independent connection tracking.
227 To compile it as a module, choose M here. If unsure, say N.
229 config NF_CONNTRACK_H323
230 tristate "H.323 protocol support"
231 depends on IPV6 || IPV6=n
232 depends on NETFILTER_ADVANCED
234 H.323 is a VoIP signalling protocol from ITU-T. As one of the most
235 important VoIP protocols, it is widely used by voice hardware and
236 software including voice gateways, IP phones, Netmeeting, OpenPhone,
239 With this module you can support H.323 on a connection tracking/NAT
242 This module supports RAS, Fast Start, H.245 Tunnelling, Call
243 Forwarding, RTP/RTCP and T.120 based audio, video, fax, chat,
244 whiteboard, file transfer, etc. For more information, please
245 visit http://nath323.sourceforge.net/.
247 To compile it as a module, choose M here. If unsure, say N.
249 config NF_CONNTRACK_IRC
250 tristate "IRC protocol support"
251 default m if NETFILTER_ADVANCED=n
253 There is a commonly-used extension to IRC called
254 Direct Client-to-Client Protocol (DCC). This enables users to send
255 files to each other, and also chat to each other without the need
256 of a server. DCC Sending is used anywhere you send files over IRC,
257 and DCC Chat is most commonly used by Eggdrop bots. If you are
258 using NAT, this extension will enable you to send files and initiate
259 chats. Note that you do NOT need this extension to get files or
260 have others initiate chats, or everything else in IRC.
262 To compile it as a module, choose M here. If unsure, say N.
264 config NF_CONNTRACK_BROADCAST
267 config NF_CONNTRACK_NETBIOS_NS
268 tristate "NetBIOS name service protocol support"
269 select NF_CONNTRACK_BROADCAST
271 NetBIOS name service requests are sent as broadcast messages from an
272 unprivileged port and responded to with unicast messages to the
273 same port. This make them hard to firewall properly because connection
274 tracking doesn't deal with broadcasts. This helper tracks locally
275 originating NetBIOS name service requests and the corresponding
276 responses. It relies on correct IP address configuration, specifically
277 netmask and broadcast address. When properly configured, the output
278 of "ip address show" should look similar to this:
280 $ ip -4 address show eth0
281 4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
282 inet 172.16.2.252/24 brd 172.16.2.255 scope global eth0
284 To compile it as a module, choose M here. If unsure, say N.
286 config NF_CONNTRACK_SNMP
287 tristate "SNMP service protocol support"
288 depends on NETFILTER_ADVANCED
289 select NF_CONNTRACK_BROADCAST
291 SNMP service requests are sent as broadcast messages from an
292 unprivileged port and responded to with unicast messages to the
293 same port. This make them hard to firewall properly because connection
294 tracking doesn't deal with broadcasts. This helper tracks locally
295 originating SNMP service requests and the corresponding
296 responses. It relies on correct IP address configuration, specifically
297 netmask and broadcast address.
299 To compile it as a module, choose M here. If unsure, say N.
301 config NF_CONNTRACK_PPTP
302 tristate "PPtP protocol support"
303 depends on NETFILTER_ADVANCED
304 select NF_CT_PROTO_GRE
306 This module adds support for PPTP (Point to Point Tunnelling
307 Protocol, RFC2637) connection tracking and NAT.
309 If you are running PPTP sessions over a stateful firewall or NAT
310 box, you may want to enable this feature.
312 Please note that not all PPTP modes of operation are supported yet.
313 Specifically these limitations exist:
314 - Blindly assumes that control connections are always established
315 in PNS->PAC direction. This is a violation of RFC2637.
316 - Only supports a single call within each session
318 To compile it as a module, choose M here. If unsure, say N.
320 config NF_CONNTRACK_SANE
321 tristate "SANE protocol support"
322 depends on NETFILTER_ADVANCED
324 SANE is a protocol for remote access to scanners as implemented
325 by the 'saned' daemon. Like FTP, it uses separate control and
328 With this module you can support SANE on a connection tracking
331 To compile it as a module, choose M here. If unsure, say N.
333 config NF_CONNTRACK_SIP
334 tristate "SIP protocol support"
335 default m if NETFILTER_ADVANCED=n
337 SIP is an application-layer control protocol that can establish,
338 modify, and terminate multimedia sessions (conferences) such as
339 Internet telephony calls. With the nf_conntrack_sip and
340 the nf_nat_sip modules you can support the protocol on a connection
341 tracking/NATing firewall.
343 To compile it as a module, choose M here. If unsure, say N.
345 config NF_CONNTRACK_TFTP
346 tristate "TFTP protocol support"
347 depends on NETFILTER_ADVANCED
349 TFTP connection tracking helper, this is required depending
350 on how restrictive your ruleset is.
351 If you are using a tftp client behind -j SNAT or -j MASQUERADING
354 To compile it as a module, choose M here. If unsure, say N.
357 tristate 'Connection tracking netlink interface'
358 select NETFILTER_NETLINK
359 default m if NETFILTER_ADVANCED=n
361 This option enables support for a netlink-based userspace interface
363 config NF_CT_NETLINK_TIMEOUT
364 tristate 'Connection tracking timeout tuning via Netlink'
365 select NETFILTER_NETLINK
366 depends on NETFILTER_ADVANCED
367 depends on NF_CONNTRACK_TIMEOUT
369 This option enables support for connection tracking timeout
370 fine-grain tuning. This allows you to attach specific timeout
371 policies to flows, instead of using the global timeout policy.
375 config NF_CT_NETLINK_HELPER
376 tristate 'Connection tracking helpers in user-space via Netlink'
377 select NETFILTER_NETLINK
378 depends on NF_CT_NETLINK
379 depends on NETFILTER_NETLINK_QUEUE
380 depends on NETFILTER_NETLINK_GLUE_CT
381 depends on NETFILTER_ADVANCED
383 This option enables the user-space connection tracking helpers
388 config NETFILTER_NETLINK_GLUE_CT
389 bool "NFQUEUE and NFLOG integration with Connection Tracking"
391 depends on (NETFILTER_NETLINK_QUEUE || NETFILTER_NETLINK_LOG) && NF_CT_NETLINK
393 If this option is enabled, NFQUEUE and NFLOG can include
394 Connection Tracking information together with the packet is
395 the enqueued via NFNETLINK.
398 tristate "Network Address Translation support"
399 depends on NF_CONNTRACK
400 default m if NETFILTER_ADVANCED=n
402 The NAT option allows masquerading, port forwarding and other
403 forms of full Network Address Port Translation. This can be
404 controlled by iptables, ip6tables or nft.
408 depends on NF_CONNTRACK && NF_NAT
409 default NF_NAT && NF_CONNTRACK_AMANDA
413 depends on NF_CONNTRACK && NF_NAT
414 default NF_NAT && NF_CONNTRACK_FTP
418 depends on NF_CONNTRACK && NF_NAT
419 default NF_NAT && NF_CONNTRACK_IRC
423 depends on NF_CONNTRACK && NF_NAT
424 default NF_NAT && NF_CONNTRACK_SIP
428 depends on NF_CONNTRACK && NF_NAT
429 default NF_NAT && NF_CONNTRACK_TFTP
431 config NF_NAT_REDIRECT
434 config NF_NAT_MASQUERADE
437 config NETFILTER_SYNPROXY
443 select NETFILTER_NETLINK
444 tristate "Netfilter nf_tables support"
446 nftables is the new packet classification framework that intends to
447 replace the existing {ip,ip6,arp,eb}_tables infrastructure. It
448 provides a pseudo-state machine with an extensible instruction-set
449 (also known as expressions) that the userspace 'nft' utility
450 (http://www.netfilter.org/projects/nftables) uses to build the
451 rule-set. It also comes with the generic set infrastructure that
452 allows you to construct mappings between matchings and actions
453 for performance lookups.
455 To compile it as a module, choose M here.
458 config NF_TABLES_INET
460 select NF_TABLES_IPV4
461 select NF_TABLES_IPV6
462 bool "Netfilter nf_tables mixed IPv4/IPv6 tables support"
464 This option enables support for a mixed IPv4/IPv6 "inet" table.
466 config NF_TABLES_NETDEV
467 bool "Netfilter nf_tables netdev tables support"
469 This option enables support for the "netdev" table.
472 tristate "Netfilter nf_tables number generator module"
474 This option adds the number generator expression used to perform
475 incremental counting and random numbers bound to a upper limit.
478 depends on NF_CONNTRACK
479 tristate "Netfilter nf_tables conntrack module"
481 This option adds the "ct" expression that you can use to match
482 connection tracking information such as the flow state.
484 config NFT_FLOW_OFFLOAD
485 depends on NF_CONNTRACK && NF_FLOW_TABLE
486 tristate "Netfilter nf_tables hardware flow offload module"
488 This option adds the "flow_offload" expression that you can use to
489 choose what flows are placed into the hardware.
492 tristate "Netfilter nf_tables counter module"
494 This option adds the "counter" expression that you can use to
495 include packet and byte counters in a rule.
498 tristate "Netfilter nf_tables connlimit module"
499 depends on NF_CONNTRACK
500 depends on NETFILTER_ADVANCED
501 select NETFILTER_CONNCOUNT
503 This option adds the "connlimit" expression that you can use to
504 ratelimit rule matchings per connections.
507 tristate "Netfilter nf_tables log module"
509 This option adds the "log" expression that you can use to log
510 packets matching some criteria.
513 tristate "Netfilter nf_tables limit module"
515 This option adds the "limit" expression that you can use to
516 ratelimit rule matchings.
519 depends on NF_CONNTRACK
521 select NF_NAT_MASQUERADE
522 tristate "Netfilter nf_tables masquerade support"
524 This option adds the "masquerade" expression that you can use
525 to perform NAT in the masquerade flavour.
528 depends on NF_CONNTRACK
530 tristate "Netfilter nf_tables redirect support"
531 select NF_NAT_REDIRECT
533 This options adds the "redirect" expression that you can use
534 to perform NAT in the redirect flavour.
537 depends on NF_CONNTRACK
539 depends on NF_TABLES_IPV4 || NF_TABLES_IPV6
540 tristate "Netfilter nf_tables nat module"
542 This option adds the "nat" expression that you can use to perform
543 typical Network Address Translation (NAT) packet transformations.
546 tristate "Netfilter nf_tables tunnel module"
548 This option adds the "tunnel" expression that you can use to set
552 tristate "Netfilter nf_tables stateful object reference module"
554 This option adds the "objref" expression that allows you to refer to
555 stateful objects, such as counters and quotas.
558 depends on NETFILTER_NETLINK_QUEUE
559 tristate "Netfilter nf_tables queue module"
561 This is required if you intend to use the userspace queueing
562 infrastructure (also known as NFQUEUE) from nftables.
565 tristate "Netfilter nf_tables quota module"
567 This option adds the "quota" expression that you can use to match
568 enforce bytes quotas.
571 default m if NETFILTER_ADVANCED=n
572 tristate "Netfilter nf_tables reject support"
573 depends on !NF_TABLES_INET || (IPV6!=m || m)
575 This option adds the "reject" expression that you can use to
576 explicitly deny and notify via TCP reset/ICMP informational errors
579 config NFT_REJECT_INET
580 depends on NF_TABLES_INET
585 depends on NETFILTER_XTABLES
586 tristate "Netfilter x_tables over nf_tables module"
588 This is required if you intend to use any of existing
589 x_tables match/target extensions over the nf_tables
593 tristate "Netfilter nf_tables hash module"
595 This option adds the "hash" expression that you can use to perform
596 a hash operation on registers.
602 depends on NF_TABLES_INET
603 depends on NFT_FIB_IPV4
604 depends on NFT_FIB_IPV6
605 tristate "Netfilter nf_tables fib inet support"
607 This option allows using the FIB expression from the inet table.
608 The lookup will be delegated to the IPv4 or IPv6 FIB depending
609 on the protocol of the packet.
612 tristate "Netfilter nf_tables xfrm/IPSec security association matching"
615 This option adds an expression that you can use to extract properties
616 of a packets security association.
619 tristate "Netfilter nf_tables socket match support"
620 depends on IPV6 || IPV6=n
621 select NF_SOCKET_IPV4
622 select NF_SOCKET_IPV6 if NF_TABLES_IPV6
624 This option allows matching for the presence or absence of a
625 corresponding socket and its attributes.
628 tristate "Netfilter nf_tables passive OS fingerprint support"
629 depends on NETFILTER_ADVANCED
630 select NETFILTER_NETLINK_OSF
632 This option allows matching packets from an specific OS.
635 tristate "Netfilter nf_tables tproxy support"
636 depends on IPV6 || IPV6=n
637 select NF_DEFRAG_IPV4
638 select NF_DEFRAG_IPV6 if NF_TABLES_IPV6
639 select NF_TPROXY_IPV4
640 select NF_TPROXY_IPV6 if NF_TABLES_IPV6
642 This makes transparent proxy support available in nftables.
645 tristate "Netfilter nf_tables SYNPROXY expression support"
646 depends on NF_CONNTRACK && NETFILTER_ADVANCED
647 select NETFILTER_SYNPROXY
650 The SYNPROXY expression allows you to intercept TCP connections and
651 establish them using syncookies before they are passed on to the
652 server. This allows to avoid conntrack and server resource usage
653 during SYN-flood attacks.
658 tristate "Netfilter packet duplication support"
660 This option enables the generic packet duplication infrastructure
663 config NFT_DUP_NETDEV
664 tristate "Netfilter nf_tables netdev packet duplication support"
667 This option enables packet duplication for the "netdev" family.
669 config NFT_FWD_NETDEV
670 tristate "Netfilter nf_tables netdev packet forwarding support"
673 This option enables packet forwarding for the "netdev" family.
675 config NFT_FIB_NETDEV
676 depends on NFT_FIB_IPV4
677 depends on NFT_FIB_IPV6
678 tristate "Netfilter nf_tables netdev fib lookups support"
680 This option allows using the FIB expression from the netdev table.
681 The lookup will be delegated to the IPv4 or IPv6 FIB depending
682 on the protocol of the packet.
684 endif # NF_TABLES_NETDEV
688 config NF_FLOW_TABLE_INET
689 tristate "Netfilter flow table mixed IPv4/IPv6 module"
690 depends on NF_FLOW_TABLE
692 This option adds the flow table mixed IPv4/IPv6 support.
694 To compile it as a module, choose M here.
697 tristate "Netfilter flow table module"
698 depends on NETFILTER_INGRESS
699 depends on NF_CONNTRACK
702 This option adds the flow table core infrastructure.
704 To compile it as a module, choose M here.
706 config NETFILTER_XTABLES
707 tristate "Netfilter Xtables support (required for ip_tables)"
708 default m if NETFILTER_ADVANCED=n
710 This is required if you intend to use any of ip_tables,
711 ip6_tables or arp_tables.
715 comment "Xtables combined modules"
717 config NETFILTER_XT_MARK
718 tristate 'nfmark target and match support'
719 default m if NETFILTER_ADVANCED=n
721 This option adds the "MARK" target and "mark" match.
723 Netfilter mark matching allows you to match packets based on the
724 "nfmark" value in the packet.
725 The target allows you to create rules in the "mangle" table which alter
726 the netfilter mark (nfmark) field associated with the packet.
728 Prior to routing, the nfmark can influence the routing method and can
729 also be used by other subsystems to change their behavior.
731 config NETFILTER_XT_CONNMARK
732 tristate 'ctmark target and match support'
733 depends on NF_CONNTRACK
734 depends on NETFILTER_ADVANCED
735 select NF_CONNTRACK_MARK
737 This option adds the "CONNMARK" target and "connmark" match.
739 Netfilter allows you to store a mark value per connection (a.k.a.
740 ctmark), similarly to the packet mark (nfmark). Using this
741 target and match, you can set and match on this mark.
743 config NETFILTER_XT_SET
744 tristate 'set target and match support'
746 depends on NETFILTER_ADVANCED
748 This option adds the "SET" target and "set" match.
750 Using this target and match, you can add/delete and match
751 elements in the sets created by ipset(8).
753 To compile it as a module, choose M here. If unsure, say N.
755 # alphabetically ordered list of targets
757 comment "Xtables targets"
759 config NETFILTER_XT_TARGET_AUDIT
760 tristate "AUDIT target support"
762 depends on NETFILTER_ADVANCED
764 This option adds a 'AUDIT' target, which can be used to create
765 audit records for packets dropped/accepted.
767 To compileit as a module, choose M here. If unsure, say N.
769 config NETFILTER_XT_TARGET_CHECKSUM
770 tristate "CHECKSUM target support"
771 depends on IP_NF_MANGLE || IP6_NF_MANGLE
772 depends on NETFILTER_ADVANCED
774 This option adds a `CHECKSUM' target, which can be used in the iptables mangle
775 table to work around buggy DHCP clients in virtualized environments.
777 Some old DHCP clients drop packets because they are not aware
778 that the checksum would normally be offloaded to hardware and
779 thus should be considered valid.
780 This target can be used to fill in the checksum using iptables
781 when such packets are sent via a virtual network device.
783 To compile it as a module, choose M here. If unsure, say N.
785 config NETFILTER_XT_TARGET_CLASSIFY
786 tristate '"CLASSIFY" target support'
787 depends on NETFILTER_ADVANCED
789 This option adds a `CLASSIFY' target, which enables the user to set
790 the priority of a packet. Some qdiscs can use this value for
791 classification, among these are:
793 atm, cbq, dsmark, pfifo_fast, htb, prio
795 To compile it as a module, choose M here. If unsure, say N.
797 config NETFILTER_XT_TARGET_CONNMARK
798 tristate '"CONNMARK" target support'
799 depends on NF_CONNTRACK
800 depends on NETFILTER_ADVANCED
801 select NETFILTER_XT_CONNMARK
803 This is a backwards-compat option for the user's convenience
804 (e.g. when running oldconfig). It selects
805 CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
807 config NETFILTER_XT_TARGET_CONNSECMARK
808 tristate '"CONNSECMARK" target support'
809 depends on NF_CONNTRACK && NF_CONNTRACK_SECMARK
810 default m if NETFILTER_ADVANCED=n
812 The CONNSECMARK target copies security markings from packets
813 to connections, and restores security markings from connections
814 to packets (if the packets are not already marked). This would
815 normally be used in conjunction with the SECMARK target.
817 To compile it as a module, choose M here. If unsure, say N.
819 config NETFILTER_XT_TARGET_CT
820 tristate '"CT" target support'
821 depends on NF_CONNTRACK
822 depends on IP_NF_RAW || IP6_NF_RAW
823 depends on NETFILTER_ADVANCED
825 This options adds a `CT' target, which allows to specify initial
826 connection tracking parameters like events to be delivered and
827 the helper to be used.
829 To compile it as a module, choose M here. If unsure, say N.
831 config NETFILTER_XT_TARGET_DSCP
832 tristate '"DSCP" and "TOS" target support'
833 depends on IP_NF_MANGLE || IP6_NF_MANGLE
834 depends on NETFILTER_ADVANCED
836 This option adds a `DSCP' target, which allows you to manipulate
837 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
839 The DSCP field can have any value between 0x0 and 0x3f inclusive.
841 It also adds the "TOS" target, which allows you to create rules in
842 the "mangle" table which alter the Type Of Service field of an IPv4
843 or the Priority field of an IPv6 packet, prior to routing.
845 To compile it as a module, choose M here. If unsure, say N.
847 config NETFILTER_XT_TARGET_HL
848 tristate '"HL" hoplimit target support'
849 depends on IP_NF_MANGLE || IP6_NF_MANGLE
850 depends on NETFILTER_ADVANCED
852 This option adds the "HL" (for IPv6) and "TTL" (for IPv4)
853 targets, which enable the user to change the
854 hoplimit/time-to-live value of the IP header.
856 While it is safe to decrement the hoplimit/TTL value, the
857 modules also allow to increment and set the hoplimit value of
858 the header to arbitrary values. This is EXTREMELY DANGEROUS
859 since you can easily create immortal packets that loop
860 forever on the network.
862 config NETFILTER_XT_TARGET_HMARK
863 tristate '"HMARK" target support'
864 depends on IP6_NF_IPTABLES || IP6_NF_IPTABLES=n
865 depends on NETFILTER_ADVANCED
867 This option adds the "HMARK" target.
869 The target allows you to create rules in the "raw" and "mangle" tables
870 which set the skbuff mark by means of hash calculation within a given
871 range. The nfmark can influence the routing method and can also be used
872 by other subsystems to change their behaviour.
874 To compile it as a module, choose M here. If unsure, say N.
876 config NETFILTER_XT_TARGET_IDLETIMER
877 tristate "IDLETIMER target support"
878 depends on NETFILTER_ADVANCED
881 This option adds the `IDLETIMER' target. Each matching packet
882 resets the timer associated with label specified when the rule is
883 added. When the timer expires, it triggers a sysfs notification.
884 The remaining time for expiration can be read via sysfs.
886 To compile it as a module, choose M here. If unsure, say N.
888 config NETFILTER_XT_TARGET_LED
889 tristate '"LED" target support'
890 depends on LEDS_CLASS && LEDS_TRIGGERS
891 depends on NETFILTER_ADVANCED
893 This option adds a `LED' target, which allows you to blink LEDs in
894 response to particular packets passing through your machine.
896 This can be used to turn a spare LED into a network activity LED,
897 which only flashes in response to FTP transfers, for example. Or
898 you could have an LED which lights up for a minute or two every time
899 somebody connects to your machine via SSH.
901 You will need support for the "led" class to make this work.
903 To create an LED trigger for incoming SSH traffic:
904 iptables -A INPUT -p tcp --dport 22 -j LED --led-trigger-id ssh --led-delay 1000
906 Then attach the new trigger to an LED on your system:
907 echo netfilter-ssh > /sys/class/leds/<ledname>/trigger
909 For more information on the LEDs available on your system, see
910 Documentation/leds/leds-class.rst
912 config NETFILTER_XT_TARGET_LOG
913 tristate "LOG target support"
916 select NF_LOG_IPV6 if IP6_NF_IPTABLES
917 default m if NETFILTER_ADVANCED=n
919 This option adds a `LOG' target, which allows you to create rules in
920 any iptables table which records the packet header to the syslog.
922 To compile it as a module, choose M here. If unsure, say N.
924 config NETFILTER_XT_TARGET_MARK
925 tristate '"MARK" target support'
926 depends on NETFILTER_ADVANCED
927 select NETFILTER_XT_MARK
929 This is a backwards-compat option for the user's convenience
930 (e.g. when running oldconfig). It selects
931 CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
933 config NETFILTER_XT_NAT
934 tristate '"SNAT and DNAT" targets support'
937 This option enables the SNAT and DNAT targets.
939 To compile it as a module, choose M here. If unsure, say N.
941 config NETFILTER_XT_TARGET_NETMAP
942 tristate '"NETMAP" target support'
945 NETMAP is an implementation of static 1:1 NAT mapping of network
946 addresses. It maps the network address part, while keeping the host
949 To compile it as a module, choose M here. If unsure, say N.
951 config NETFILTER_XT_TARGET_NFLOG
952 tristate '"NFLOG" target support'
953 default m if NETFILTER_ADVANCED=n
954 select NETFILTER_NETLINK_LOG
956 This option enables the NFLOG target, which allows to LOG
957 messages through nfnetlink_log.
959 To compile it as a module, choose M here. If unsure, say N.
961 config NETFILTER_XT_TARGET_NFQUEUE
962 tristate '"NFQUEUE" target Support'
963 depends on NETFILTER_ADVANCED
964 select NETFILTER_NETLINK_QUEUE
966 This target replaced the old obsolete QUEUE target.
968 As opposed to QUEUE, it supports 65535 different queues,
971 To compile it as a module, choose M here. If unsure, say N.
973 config NETFILTER_XT_TARGET_NOTRACK
974 tristate '"NOTRACK" target support (DEPRECATED)'
975 depends on NF_CONNTRACK
976 depends on IP_NF_RAW || IP6_NF_RAW
977 depends on NETFILTER_ADVANCED
978 select NETFILTER_XT_TARGET_CT
980 config NETFILTER_XT_TARGET_RATEEST
981 tristate '"RATEEST" target support'
982 depends on NETFILTER_ADVANCED
984 This option adds a `RATEEST' target, which allows to measure
985 rates similar to TC estimators. The `rateest' match can be
986 used to match on the measured rates.
988 To compile it as a module, choose M here. If unsure, say N.
990 config NETFILTER_XT_TARGET_REDIRECT
991 tristate "REDIRECT target support"
993 select NF_NAT_REDIRECT
995 REDIRECT is a special case of NAT: all incoming connections are
996 mapped onto the incoming interface's address, causing the packets to
997 come to the local machine instead of passing through. This is
998 useful for transparent proxies.
1000 To compile it as a module, choose M here. If unsure, say N.
1002 config NETFILTER_XT_TARGET_MASQUERADE
1003 tristate "MASQUERADE target support"
1005 default m if NETFILTER_ADVANCED=n
1006 select NF_NAT_MASQUERADE
1008 Masquerading is a special case of NAT: all outgoing connections are
1009 changed to seem to come from a particular interface's address, and
1010 if the interface goes down, those connections are lost. This is
1011 only useful for dialup accounts with dynamic IP address (ie. your IP
1012 address will be different on next dialup).
1014 To compile it as a module, choose M here. If unsure, say N.
1016 config NETFILTER_XT_TARGET_TEE
1017 tristate '"TEE" - packet cloning to alternate destination'
1018 depends on NETFILTER_ADVANCED
1019 depends on IPV6 || IPV6=n
1020 depends on !NF_CONNTRACK || NF_CONNTRACK
1021 depends on IP6_NF_IPTABLES || !IP6_NF_IPTABLES
1023 select NF_DUP_IPV6 if IP6_NF_IPTABLES
1025 This option adds a "TEE" target with which a packet can be cloned and
1026 this clone be rerouted to another nexthop.
1028 config NETFILTER_XT_TARGET_TPROXY
1029 tristate '"TPROXY" target transparent proxying support'
1030 depends on NETFILTER_XTABLES
1031 depends on NETFILTER_ADVANCED
1032 depends on IPV6 || IPV6=n
1033 depends on IP6_NF_IPTABLES || IP6_NF_IPTABLES=n
1034 depends on IP_NF_MANGLE
1035 select NF_DEFRAG_IPV4
1036 select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES != n
1037 select NF_TPROXY_IPV4
1038 select NF_TPROXY_IPV6 if IP6_NF_IPTABLES
1040 This option adds a `TPROXY' target, which is somewhat similar to
1041 REDIRECT. It can only be used in the mangle table and is useful
1042 to redirect traffic to a transparent proxy. It does _not_ depend
1043 on Netfilter connection tracking and NAT, unlike REDIRECT.
1044 For it to work you will have to configure certain iptables rules
1045 and use policy routing. For more information on how to set it up
1046 see Documentation/networking/tproxy.rst.
1048 To compile it as a module, choose M here. If unsure, say N.
1050 config NETFILTER_XT_TARGET_TRACE
1051 tristate '"TRACE" target support'
1052 depends on IP_NF_RAW || IP6_NF_RAW
1053 depends on NETFILTER_ADVANCED
1055 The TRACE target allows you to mark packets so that the kernel
1056 will log every rule which match the packets as those traverse
1057 the tables, chains, rules.
1059 If you want to compile it as a module, say M here and read
1060 <file:Documentation/kbuild/modules.rst>. If unsure, say `N'.
1062 config NETFILTER_XT_TARGET_SECMARK
1063 tristate '"SECMARK" target support'
1064 depends on NETWORK_SECMARK
1065 default m if NETFILTER_ADVANCED=n
1067 The SECMARK target allows security marking of network
1068 packets, for use with security subsystems.
1070 To compile it as a module, choose M here. If unsure, say N.
1072 config NETFILTER_XT_TARGET_TCPMSS
1073 tristate '"TCPMSS" target support'
1074 depends on IPV6 || IPV6=n
1075 default m if NETFILTER_ADVANCED=n
1077 This option adds a `TCPMSS' target, which allows you to alter the
1078 MSS value of TCP SYN packets, to control the maximum size for that
1079 connection (usually limiting it to your outgoing interface's MTU
1082 This is used to overcome criminally braindead ISPs or servers which
1083 block ICMP Fragmentation Needed packets. The symptoms of this
1084 problem are that everything works fine from your Linux
1085 firewall/router, but machines behind it can never exchange large
1087 1) Web browsers connect, then hang with no data received.
1088 2) Small mail works fine, but large emails hang.
1089 3) ssh works fine, but scp hangs after initial handshaking.
1091 Workaround: activate this option and add a rule to your firewall
1094 iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
1095 -j TCPMSS --clamp-mss-to-pmtu
1097 To compile it as a module, choose M here. If unsure, say N.
1099 config NETFILTER_XT_TARGET_TCPOPTSTRIP
1100 tristate '"TCPOPTSTRIP" target support'
1101 depends on IP_NF_MANGLE || IP6_NF_MANGLE
1102 depends on NETFILTER_ADVANCED
1104 This option adds a "TCPOPTSTRIP" target, which allows you to strip
1105 TCP options from TCP packets.
1107 # alphabetically ordered list of matches
1109 comment "Xtables matches"
1111 config NETFILTER_XT_MATCH_ADDRTYPE
1112 tristate '"addrtype" address type match support'
1113 default m if NETFILTER_ADVANCED=n
1115 This option allows you to match what routing thinks of an address,
1116 eg. UNICAST, LOCAL, BROADCAST, ...
1118 If you want to compile it as a module, say M here and read
1119 <file:Documentation/kbuild/modules.rst>. If unsure, say `N'.
1121 config NETFILTER_XT_MATCH_BPF
1122 tristate '"bpf" match support'
1123 depends on NETFILTER_ADVANCED
1125 BPF matching applies a linux socket filter to each packet and
1126 accepts those for which the filter returns non-zero.
1128 To compile it as a module, choose M here. If unsure, say N.
1130 config NETFILTER_XT_MATCH_CGROUP
1131 tristate '"control group" match support'
1132 depends on NETFILTER_ADVANCED
1134 select CGROUP_NET_CLASSID
1136 Socket/process control group matching allows you to match locally
1137 generated packets based on which net_cls control group processes
1140 config NETFILTER_XT_MATCH_CLUSTER
1141 tristate '"cluster" match support'
1142 depends on NF_CONNTRACK
1143 depends on NETFILTER_ADVANCED
1145 This option allows you to build work-load-sharing clusters of
1146 network servers/stateful firewalls without having a dedicated
1147 load-balancing router/server/switch. Basically, this match returns
1148 true when the packet must be handled by this cluster node. Thus,
1149 all nodes see all packets and this match decides which node handles
1150 what packets. The work-load sharing algorithm is based on source
1153 If you say Y or M here, try `iptables -m cluster --help` for
1156 config NETFILTER_XT_MATCH_COMMENT
1157 tristate '"comment" match support'
1158 depends on NETFILTER_ADVANCED
1160 This option adds a `comment' dummy-match, which allows you to put
1161 comments in your iptables ruleset.
1163 If you want to compile it as a module, say M here and read
1164 <file:Documentation/kbuild/modules.rst>. If unsure, say `N'.
1166 config NETFILTER_XT_MATCH_CONNBYTES
1167 tristate '"connbytes" per-connection counter match support'
1168 depends on NF_CONNTRACK
1169 depends on NETFILTER_ADVANCED
1171 This option adds a `connbytes' match, which allows you to match the
1172 number of bytes and/or packets for each direction within a connection.
1174 If you want to compile it as a module, say M here and read
1175 <file:Documentation/kbuild/modules.rst>. If unsure, say `N'.
1177 config NETFILTER_XT_MATCH_CONNLABEL
1178 tristate '"connlabel" match support'
1179 select NF_CONNTRACK_LABELS
1180 depends on NF_CONNTRACK
1181 depends on NETFILTER_ADVANCED
1183 This match allows you to test and assign userspace-defined labels names
1184 to a connection. The kernel only stores bit values - mapping
1185 names to bits is done by userspace.
1187 Unlike connmark, more than 32 flag bits may be assigned to a
1188 connection simultaneously.
1190 config NETFILTER_XT_MATCH_CONNLIMIT
1191 tristate '"connlimit" match support'
1192 depends on NF_CONNTRACK
1193 depends on NETFILTER_ADVANCED
1194 select NETFILTER_CONNCOUNT
1196 This match allows you to match against the number of parallel
1197 connections to a server per client IP address (or address block).
1199 config NETFILTER_XT_MATCH_CONNMARK
1200 tristate '"connmark" connection mark match support'
1201 depends on NF_CONNTRACK
1202 depends on NETFILTER_ADVANCED
1203 select NETFILTER_XT_CONNMARK
1205 This is a backwards-compat option for the user's convenience
1206 (e.g. when running oldconfig). It selects
1207 CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
1209 config NETFILTER_XT_MATCH_CONNTRACK
1210 tristate '"conntrack" connection tracking match support'
1211 depends on NF_CONNTRACK
1212 default m if NETFILTER_ADVANCED=n
1214 This is a general conntrack match module, a superset of the state match.
1216 It allows matching on additional conntrack information, which is
1217 useful in complex configurations, such as NAT gateways with multiple
1218 internet links or tunnels.
1220 To compile it as a module, choose M here. If unsure, say N.
1222 config NETFILTER_XT_MATCH_CPU
1223 tristate '"cpu" match support'
1224 depends on NETFILTER_ADVANCED
1226 CPU matching allows you to match packets based on the CPU
1227 currently handling the packet.
1229 To compile it as a module, choose M here. If unsure, say N.
1231 config NETFILTER_XT_MATCH_DCCP
1232 tristate '"dccp" protocol match support'
1233 depends on NETFILTER_ADVANCED
1236 With this option enabled, you will be able to use the iptables
1237 `dccp' match in order to match on DCCP source/destination ports
1240 If you want to compile it as a module, say M here and read
1241 <file:Documentation/kbuild/modules.rst>. If unsure, say `N'.
1243 config NETFILTER_XT_MATCH_DEVGROUP
1244 tristate '"devgroup" match support'
1245 depends on NETFILTER_ADVANCED
1247 This options adds a `devgroup' match, which allows to match on the
1248 device group a network device is assigned to.
1250 To compile it as a module, choose M here. If unsure, say N.
1252 config NETFILTER_XT_MATCH_DSCP
1253 tristate '"dscp" and "tos" match support'
1254 depends on NETFILTER_ADVANCED
1256 This option adds a `DSCP' match, which allows you to match against
1257 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
1259 The DSCP field can have any value between 0x0 and 0x3f inclusive.
1261 It will also add a "tos" match, which allows you to match packets
1262 based on the Type Of Service fields of the IPv4 packet (which share
1263 the same bits as DSCP).
1265 To compile it as a module, choose M here. If unsure, say N.
1267 config NETFILTER_XT_MATCH_ECN
1268 tristate '"ecn" match support'
1269 depends on NETFILTER_ADVANCED
1271 This option adds an "ECN" match, which allows you to match against
1272 the IPv4 and TCP header ECN fields.
1274 To compile it as a module, choose M here. If unsure, say N.
1276 config NETFILTER_XT_MATCH_ESP
1277 tristate '"esp" match support'
1278 depends on NETFILTER_ADVANCED
1280 This match extension allows you to match a range of SPIs
1281 inside ESP header of IPSec packets.
1283 To compile it as a module, choose M here. If unsure, say N.
1285 config NETFILTER_XT_MATCH_HASHLIMIT
1286 tristate '"hashlimit" match support'
1287 depends on IP6_NF_IPTABLES || IP6_NF_IPTABLES=n
1288 depends on NETFILTER_ADVANCED
1290 This option adds a `hashlimit' match.
1292 As opposed to `limit', this match dynamically creates a hash table
1293 of limit buckets, based on your selection of source/destination
1294 addresses and/or ports.
1296 It enables you to express policies like `10kpps for any given
1297 destination address' or `500pps from any given source address'
1300 config NETFILTER_XT_MATCH_HELPER
1301 tristate '"helper" match support'
1302 depends on NF_CONNTRACK
1303 depends on NETFILTER_ADVANCED
1305 Helper matching allows you to match packets in dynamic connections
1306 tracked by a conntrack-helper, ie. nf_conntrack_ftp
1308 To compile it as a module, choose M here. If unsure, say Y.
1310 config NETFILTER_XT_MATCH_HL
1311 tristate '"hl" hoplimit/TTL match support'
1312 depends on NETFILTER_ADVANCED
1314 HL matching allows you to match packets based on the hoplimit
1315 in the IPv6 header, or the time-to-live field in the IPv4
1316 header of the packet.
1318 config NETFILTER_XT_MATCH_IPCOMP
1319 tristate '"ipcomp" match support'
1320 depends on NETFILTER_ADVANCED
1322 This match extension allows you to match a range of CPIs(16 bits)
1323 inside IPComp header of IPSec packets.
1325 To compile it as a module, choose M here. If unsure, say N.
1327 config NETFILTER_XT_MATCH_IPRANGE
1328 tristate '"iprange" address range match support'
1329 depends on NETFILTER_ADVANCED
1331 This option adds a "iprange" match, which allows you to match based on
1332 an IP address range. (Normal iptables only matches on single addresses
1333 with an optional mask.)
1337 config NETFILTER_XT_MATCH_IPVS
1338 tristate '"ipvs" match support'
1340 depends on NETFILTER_ADVANCED
1341 depends on NF_CONNTRACK
1343 This option allows you to match against IPVS properties of a packet.
1347 config NETFILTER_XT_MATCH_L2TP
1348 tristate '"l2tp" match support'
1349 depends on NETFILTER_ADVANCED
1352 This option adds an "L2TP" match, which allows you to match against
1353 L2TP protocol header fields.
1355 To compile it as a module, choose M here. If unsure, say N.
1357 config NETFILTER_XT_MATCH_LENGTH
1358 tristate '"length" match support'
1359 depends on NETFILTER_ADVANCED
1361 This option allows you to match the length of a packet against a
1362 specific value or range of values.
1364 To compile it as a module, choose M here. If unsure, say N.
1366 config NETFILTER_XT_MATCH_LIMIT
1367 tristate '"limit" match support'
1368 depends on NETFILTER_ADVANCED
1370 limit matching allows you to control the rate at which a rule can be
1371 matched: mainly useful in combination with the LOG target ("LOG
1372 target support", below) and to avoid some Denial of Service attacks.
1374 To compile it as a module, choose M here. If unsure, say N.
1376 config NETFILTER_XT_MATCH_MAC
1377 tristate '"mac" address match support'
1378 depends on NETFILTER_ADVANCED
1380 MAC matching allows you to match packets based on the source
1381 Ethernet address of the packet.
1383 To compile it as a module, choose M here. If unsure, say N.
1385 config NETFILTER_XT_MATCH_MARK
1386 tristate '"mark" match support'
1387 depends on NETFILTER_ADVANCED
1388 select NETFILTER_XT_MARK
1390 This is a backwards-compat option for the user's convenience
1391 (e.g. when running oldconfig). It selects
1392 CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
1394 config NETFILTER_XT_MATCH_MULTIPORT
1395 tristate '"multiport" Multiple port match support'
1396 depends on NETFILTER_ADVANCED
1398 Multiport matching allows you to match TCP or UDP packets based on
1399 a series of source or destination ports: normally a rule can only
1400 match a single range of ports.
1402 To compile it as a module, choose M here. If unsure, say N.
1404 config NETFILTER_XT_MATCH_NFACCT
1405 tristate '"nfacct" match support'
1406 depends on NETFILTER_ADVANCED
1407 select NETFILTER_NETLINK_ACCT
1409 This option allows you to use the extended accounting through
1412 To compile it as a module, choose M here. If unsure, say N.
1414 config NETFILTER_XT_MATCH_OSF
1415 tristate '"osf" Passive OS fingerprint match'
1416 depends on NETFILTER_ADVANCED
1417 select NETFILTER_NETLINK_OSF
1419 This option selects the Passive OS Fingerprinting match module
1420 that allows to passively match the remote operating system by
1421 analyzing incoming TCP SYN packets.
1423 Rules and loading software can be downloaded from
1424 http://www.ioremap.net/projects/osf
1426 To compile it as a module, choose M here. If unsure, say N.
1428 config NETFILTER_XT_MATCH_OWNER
1429 tristate '"owner" match support'
1430 depends on NETFILTER_ADVANCED
1432 Socket owner matching allows you to match locally-generated packets
1433 based on who created the socket: the user or group. It is also
1434 possible to check whether a socket actually exists.
1436 config NETFILTER_XT_MATCH_POLICY
1437 tristate 'IPsec "policy" match support'
1439 default m if NETFILTER_ADVANCED=n
1441 Policy matching allows you to match packets based on the
1442 IPsec policy that was used during decapsulation/will
1443 be used during encapsulation.
1445 To compile it as a module, choose M here. If unsure, say N.
1447 config NETFILTER_XT_MATCH_PHYSDEV
1448 tristate '"physdev" match support'
1449 depends on BRIDGE && BRIDGE_NETFILTER
1450 depends on NETFILTER_ADVANCED
1452 Physdev packet matching matches against the physical bridge ports
1453 the IP packet arrived on or will leave by.
1455 To compile it as a module, choose M here. If unsure, say N.
1457 config NETFILTER_XT_MATCH_PKTTYPE
1458 tristate '"pkttype" packet type match support'
1459 depends on NETFILTER_ADVANCED
1461 Packet type matching allows you to match a packet by
1462 its "class", eg. BROADCAST, MULTICAST, ...
1465 iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG
1467 To compile it as a module, choose M here. If unsure, say N.
1469 config NETFILTER_XT_MATCH_QUOTA
1470 tristate '"quota" match support'
1471 depends on NETFILTER_ADVANCED
1473 This option adds a `quota' match, which allows to match on a
1476 If you want to compile it as a module, say M here and read
1477 <file:Documentation/kbuild/modules.rst>. If unsure, say `N'.
1479 config NETFILTER_XT_MATCH_RATEEST
1480 tristate '"rateest" match support'
1481 depends on NETFILTER_ADVANCED
1482 select NETFILTER_XT_TARGET_RATEEST
1484 This option adds a `rateest' match, which allows to match on the
1485 rate estimated by the RATEEST target.
1487 To compile it as a module, choose M here. If unsure, say N.
1489 config NETFILTER_XT_MATCH_REALM
1490 tristate '"realm" match support'
1491 depends on NETFILTER_ADVANCED
1492 select IP_ROUTE_CLASSID
1494 This option adds a `realm' match, which allows you to use the realm
1495 key from the routing subsystem inside iptables.
1497 This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option
1500 If you want to compile it as a module, say M here and read
1501 <file:Documentation/kbuild/modules.rst>. If unsure, say `N'.
1503 config NETFILTER_XT_MATCH_RECENT
1504 tristate '"recent" match support'
1505 depends on NETFILTER_ADVANCED
1507 This match is used for creating one or many lists of recently
1508 used addresses and then matching against that/those list(s).
1510 Short options are available by using 'iptables -m recent -h'
1511 Official Website: <http://snowman.net/projects/ipt_recent/>
1513 config NETFILTER_XT_MATCH_SCTP
1514 tristate '"sctp" protocol match support'
1515 depends on NETFILTER_ADVANCED
1518 With this option enabled, you will be able to use the
1519 `sctp' match in order to match on SCTP source/destination ports
1520 and SCTP chunk types.
1522 If you want to compile it as a module, say M here and read
1523 <file:Documentation/kbuild/modules.rst>. If unsure, say `N'.
1525 config NETFILTER_XT_MATCH_SOCKET
1526 tristate '"socket" match support'
1527 depends on NETFILTER_XTABLES
1528 depends on NETFILTER_ADVANCED
1529 depends on IPV6 || IPV6=n
1530 depends on IP6_NF_IPTABLES || IP6_NF_IPTABLES=n
1531 select NF_SOCKET_IPV4
1532 select NF_SOCKET_IPV6 if IP6_NF_IPTABLES
1533 select NF_DEFRAG_IPV4
1534 select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES != n
1536 This option adds a `socket' match, which can be used to match
1537 packets for which a TCP or UDP socket lookup finds a valid socket.
1538 It can be used in combination with the MARK target and policy
1539 routing to implement full featured non-locally bound sockets.
1541 To compile it as a module, choose M here. If unsure, say N.
1543 config NETFILTER_XT_MATCH_STATE
1544 tristate '"state" match support'
1545 depends on NF_CONNTRACK
1546 default m if NETFILTER_ADVANCED=n
1548 Connection state matching allows you to match packets based on their
1549 relationship to a tracked connection (ie. previous packets). This
1550 is a powerful tool for packet classification.
1552 To compile it as a module, choose M here. If unsure, say N.
1554 config NETFILTER_XT_MATCH_STATISTIC
1555 tristate '"statistic" match support'
1556 depends on NETFILTER_ADVANCED
1558 This option adds a `statistic' match, which allows you to match
1559 on packets periodically or randomly with a given percentage.
1561 To compile it as a module, choose M here. If unsure, say N.
1563 config NETFILTER_XT_MATCH_STRING
1564 tristate '"string" match support'
1565 depends on NETFILTER_ADVANCED
1567 select TEXTSEARCH_KMP
1568 select TEXTSEARCH_BM
1569 select TEXTSEARCH_FSM
1571 This option adds a `string' match, which allows you to look for
1572 pattern matchings in packets.
1574 To compile it as a module, choose M here. If unsure, say N.
1576 config NETFILTER_XT_MATCH_TCPMSS
1577 tristate '"tcpmss" match support'
1578 depends on NETFILTER_ADVANCED
1580 This option adds a `tcpmss' match, which allows you to examine the
1581 MSS value of TCP SYN packets, which control the maximum packet size
1582 for that connection.
1584 To compile it as a module, choose M here. If unsure, say N.
1586 config NETFILTER_XT_MATCH_TIME
1587 tristate '"time" match support'
1588 depends on NETFILTER_ADVANCED
1590 This option adds a "time" match, which allows you to match based on
1591 the packet arrival time (at the machine which netfilter is running)
1592 on) or departure time/date (for locally generated packets).
1594 If you say Y here, try `iptables -m time --help` for
1597 If you want to compile it as a module, say M here.
1600 config NETFILTER_XT_MATCH_U32
1601 tristate '"u32" match support'
1602 depends on NETFILTER_ADVANCED
1604 u32 allows you to extract quantities of up to 4 bytes from a packet,
1605 AND them with specified masks, shift them by specified amounts and
1606 test whether the results are in any of a set of specified ranges.
1607 The specification of what to extract is general enough to skip over
1608 headers with lengths stored in the packet, as in IP or TCP header
1611 Details and examples are in the kernel module source.
1613 endif # NETFILTER_XTABLES
1617 source "net/netfilter/ipset/Kconfig"
1619 source "net/netfilter/ipvs/Kconfig"