1 menu "Core Netfilter Configuration"
2 depends on NET && INET && NETFILTER
4 config NETFILTER_INGRESS
5 bool "Netfilter ingress support"
9 This allows you to classify packets from ingress using the Netfilter
12 config NETFILTER_NETLINK
15 config NETFILTER_NETLINK_ACCT
16 tristate "Netfilter NFACCT 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 extended accounting via NFNETLINK.
23 config NETFILTER_NETLINK_QUEUE
24 tristate "Netfilter NFQUEUE over NFNETLINK interface"
25 depends on NETFILTER_ADVANCED
26 select NETFILTER_NETLINK
28 If this option is enabled, the kernel will include support
29 for queueing packets via NFNETLINK.
31 config NETFILTER_NETLINK_LOG
32 tristate "Netfilter LOG over NFNETLINK interface"
33 default m if NETFILTER_ADVANCED=n
34 select NETFILTER_NETLINK
36 If this option is enabled, the kernel will include support
37 for logging packets via NFNETLINK.
39 This obsoletes the existing ipt_ULOG and ebg_ulog mechanisms,
40 and is also scheduled to replace the old syslog-based ipt_LOG
44 tristate "Netfilter connection tracking support"
45 default m if NETFILTER_ADVANCED=n
47 Connection tracking keeps a record of what packets have passed
48 through your machine, in order to figure out how they are related
51 This is required to do Masquerading or other kinds of Network
52 Address Translation. It can also be used to enhance packet
53 filtering (see `Connection state match support' below).
55 To compile it as a module, choose M here. If unsure, say N.
61 tristate "Netdev packet logging"
66 config NF_CONNTRACK_MARK
67 bool 'Connection mark tracking support'
68 depends on NETFILTER_ADVANCED
70 This option enables support for connection marks, used by the
71 `CONNMARK' target and `connmark' match. Similar to the mark value
72 of packets, but this mark value is kept in the conntrack session
73 instead of the individual packets.
75 config NF_CONNTRACK_SECMARK
76 bool 'Connection tracking security mark support'
77 depends on NETWORK_SECMARK
78 default y if NETFILTER_ADVANCED=n
80 This option enables security markings to be applied to
81 connections. Typically they are copied to connections from
82 packets using the CONNSECMARK target and copied back from
83 connections to packets with the same target, with the packets
84 being originally labeled via SECMARK.
88 config NF_CONNTRACK_ZONES
89 bool 'Connection tracking zones'
90 depends on NETFILTER_ADVANCED
91 depends on NETFILTER_XT_TARGET_CT
93 This option enables support for connection tracking zones.
94 Normally, each connection needs to have a unique system wide
95 identity. Connection tracking zones allow to have multiple
96 connections using the same identity, as long as they are
97 contained in different zones.
101 config NF_CONNTRACK_PROCFS
102 bool "Supply CT list in procfs (OBSOLETE)"
105 This option enables for the list of known conntrack entries
106 to be shown in procfs under net/netfilter/nf_conntrack. This
107 is considered obsolete in favor of using the conntrack(8)
108 tool which uses Netlink.
110 config NF_CONNTRACK_EVENTS
111 bool "Connection tracking events"
112 depends on NETFILTER_ADVANCED
114 If this option is enabled, the connection tracking code will
115 provide a notifier chain that can be used by other kernel code
116 to get notified about changes in the connection tracking state.
120 config NF_CONNTRACK_TIMEOUT
121 bool 'Connection tracking timeout'
122 depends on NETFILTER_ADVANCED
124 This option enables support for connection tracking timeout
125 extension. This allows you to attach timeout policies to flow
130 config NF_CONNTRACK_TIMESTAMP
131 bool 'Connection tracking timestamping'
132 depends on NETFILTER_ADVANCED
134 This option enables support for connection tracking timestamping.
135 This allows you to store the flow start-time and to obtain
136 the flow-stop time (once it has been destroyed) via Connection
141 config NF_CONNTRACK_LABELS
144 This option enables support for assigning user-defined flag bits
145 to connection tracking entries. It selected by the connlabel match.
147 config NF_CT_PROTO_DCCP
148 bool 'DCCP protocol connection tracking support'
149 depends on NETFILTER_ADVANCED
152 With this option enabled, the layer 3 independent connection
153 tracking code will be able to do state tracking on DCCP connections.
157 config NF_CT_PROTO_GRE
160 config NF_CT_PROTO_SCTP
161 bool 'SCTP protocol connection tracking support'
162 depends on NETFILTER_ADVANCED
166 With this option enabled, the layer 3 independent connection
167 tracking code will be able to do state tracking on SCTP connections.
171 config NF_CT_PROTO_UDPLITE
172 bool 'UDP-Lite protocol connection tracking support'
173 depends on NETFILTER_ADVANCED
176 With this option enabled, the layer 3 independent connection
177 tracking code will be able to do state tracking on UDP-Lite
182 config NF_CONNTRACK_AMANDA
183 tristate "Amanda backup protocol support"
184 depends on NETFILTER_ADVANCED
186 select TEXTSEARCH_KMP
188 If you are running the Amanda backup package <http://www.amanda.org/>
189 on this machine or machines that will be MASQUERADED through this
190 machine, then you may want to enable this feature. This allows the
191 connection tracking and natting code to allow the sub-channels that
192 Amanda requires for communication of the backup data, messages and
195 To compile it as a module, choose M here. If unsure, say N.
197 config NF_CONNTRACK_FTP
198 tristate "FTP protocol support"
199 default m if NETFILTER_ADVANCED=n
201 Tracking FTP connections is problematic: special helpers are
202 required for tracking them, and doing masquerading and other forms
203 of Network Address Translation on them.
205 This is FTP support on Layer 3 independent connection tracking.
206 Layer 3 independent connection tracking is experimental scheme
207 which generalize ip_conntrack to support other layer 3 protocols.
209 To compile it as a module, choose M here. If unsure, say N.
211 config NF_CONNTRACK_H323
212 tristate "H.323 protocol support"
213 depends on IPV6 || IPV6=n
214 depends on NETFILTER_ADVANCED
216 H.323 is a VoIP signalling protocol from ITU-T. As one of the most
217 important VoIP protocols, it is widely used by voice hardware and
218 software including voice gateways, IP phones, Netmeeting, OpenPhone,
221 With this module you can support H.323 on a connection tracking/NAT
224 This module supports RAS, Fast Start, H.245 Tunnelling, Call
225 Forwarding, RTP/RTCP and T.120 based audio, video, fax, chat,
226 whiteboard, file transfer, etc. For more information, please
227 visit http://nath323.sourceforge.net/.
229 To compile it as a module, choose M here. If unsure, say N.
231 config NF_CONNTRACK_IRC
232 tristate "IRC protocol support"
233 default m if NETFILTER_ADVANCED=n
235 There is a commonly-used extension to IRC called
236 Direct Client-to-Client Protocol (DCC). This enables users to send
237 files to each other, and also chat to each other without the need
238 of a server. DCC Sending is used anywhere you send files over IRC,
239 and DCC Chat is most commonly used by Eggdrop bots. If you are
240 using NAT, this extension will enable you to send files and initiate
241 chats. Note that you do NOT need this extension to get files or
242 have others initiate chats, or everything else in IRC.
244 To compile it as a module, choose M here. If unsure, say N.
246 config NF_CONNTRACK_BROADCAST
249 config NF_CONNTRACK_NETBIOS_NS
250 tristate "NetBIOS name service protocol support"
251 select NF_CONNTRACK_BROADCAST
253 NetBIOS name service requests are sent as broadcast messages from an
254 unprivileged port and responded to with unicast messages to the
255 same port. This make them hard to firewall properly because connection
256 tracking doesn't deal with broadcasts. This helper tracks locally
257 originating NetBIOS name service requests and the corresponding
258 responses. It relies on correct IP address configuration, specifically
259 netmask and broadcast address. When properly configured, the output
260 of "ip address show" should look similar to this:
262 $ ip -4 address show eth0
263 4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
264 inet 172.16.2.252/24 brd 172.16.2.255 scope global eth0
266 To compile it as a module, choose M here. If unsure, say N.
268 config NF_CONNTRACK_SNMP
269 tristate "SNMP service protocol support"
270 depends on NETFILTER_ADVANCED
271 select NF_CONNTRACK_BROADCAST
273 SNMP service requests are sent as broadcast messages from an
274 unprivileged port and responded to with unicast messages to the
275 same port. This make them hard to firewall properly because connection
276 tracking doesn't deal with broadcasts. This helper tracks locally
277 originating SNMP service requests and the corresponding
278 responses. It relies on correct IP address configuration, specifically
279 netmask and broadcast address.
281 To compile it as a module, choose M here. If unsure, say N.
283 config NF_CONNTRACK_PPTP
284 tristate "PPtP protocol support"
285 depends on NETFILTER_ADVANCED
286 select NF_CT_PROTO_GRE
288 This module adds support for PPTP (Point to Point Tunnelling
289 Protocol, RFC2637) connection tracking and NAT.
291 If you are running PPTP sessions over a stateful firewall or NAT
292 box, you may want to enable this feature.
294 Please note that not all PPTP modes of operation are supported yet.
295 Specifically these limitations exist:
296 - Blindly assumes that control connections are always established
297 in PNS->PAC direction. This is a violation of RFC2637.
298 - Only supports a single call within each session
300 To compile it as a module, choose M here. If unsure, say N.
302 config NF_CONNTRACK_SANE
303 tristate "SANE protocol support"
304 depends on NETFILTER_ADVANCED
306 SANE is a protocol for remote access to scanners as implemented
307 by the 'saned' daemon. Like FTP, it uses separate control and
310 With this module you can support SANE on a connection tracking
313 To compile it as a module, choose M here. If unsure, say N.
315 config NF_CONNTRACK_SIP
316 tristate "SIP protocol support"
317 default m if NETFILTER_ADVANCED=n
319 SIP is an application-layer control protocol that can establish,
320 modify, and terminate multimedia sessions (conferences) such as
321 Internet telephony calls. With the ip_conntrack_sip and
322 the nf_nat_sip modules you can support the protocol on a connection
323 tracking/NATing firewall.
325 To compile it as a module, choose M here. If unsure, say N.
327 config NF_CONNTRACK_TFTP
328 tristate "TFTP protocol support"
329 depends on NETFILTER_ADVANCED
331 TFTP connection tracking helper, this is required depending
332 on how restrictive your ruleset is.
333 If you are using a tftp client behind -j SNAT or -j MASQUERADING
336 To compile it as a module, choose M here. If unsure, say N.
339 tristate 'Connection tracking netlink interface'
340 select NETFILTER_NETLINK
341 default m if NETFILTER_ADVANCED=n
343 This option enables support for a netlink-based userspace interface
345 config NF_CT_NETLINK_TIMEOUT
346 tristate 'Connection tracking timeout tuning via Netlink'
347 select NETFILTER_NETLINK
348 depends on NETFILTER_ADVANCED
350 This option enables support for connection tracking timeout
351 fine-grain tuning. This allows you to attach specific timeout
352 policies to flows, instead of using the global timeout policy.
356 config NF_CT_NETLINK_HELPER
357 tristate 'Connection tracking helpers in user-space via Netlink'
358 select NETFILTER_NETLINK
359 depends on NF_CT_NETLINK
360 depends on NETFILTER_NETLINK_QUEUE
361 depends on NETFILTER_NETLINK_GLUE_CT
362 depends on NETFILTER_ADVANCED
364 This option enables the user-space connection tracking helpers
369 config NETFILTER_NETLINK_GLUE_CT
370 bool "NFQUEUE and NFLOG integration with Connection Tracking"
372 depends on (NETFILTER_NETLINK_QUEUE || NETFILTER_NETLINK_LOG) && NF_CT_NETLINK
374 If this option is enabled, NFQUEUE and NFLOG can include
375 Connection Tracking information together with the packet is
376 the enqueued via NFNETLINK.
386 config NF_NAT_PROTO_DCCP
388 depends on NF_NAT && NF_CT_PROTO_DCCP
389 default NF_NAT && NF_CT_PROTO_DCCP
391 config NF_NAT_PROTO_UDPLITE
393 depends on NF_NAT && NF_CT_PROTO_UDPLITE
394 default NF_NAT && NF_CT_PROTO_UDPLITE
396 config NF_NAT_PROTO_SCTP
398 default NF_NAT && NF_CT_PROTO_SCTP
399 depends on NF_NAT && NF_CT_PROTO_SCTP
403 depends on NF_CONNTRACK && NF_NAT
404 default NF_NAT && NF_CONNTRACK_AMANDA
408 depends on NF_CONNTRACK && NF_NAT
409 default NF_NAT && NF_CONNTRACK_FTP
413 depends on NF_CONNTRACK && NF_NAT
414 default NF_NAT && NF_CONNTRACK_IRC
418 depends on NF_CONNTRACK && NF_NAT
419 default NF_NAT && NF_CONNTRACK_SIP
423 depends on NF_CONNTRACK && NF_NAT
424 default NF_NAT && NF_CONNTRACK_TFTP
426 config NF_NAT_REDIRECT
427 tristate "IPv4/IPv6 redirect support"
430 This is the kernel functionality to redirect packets to local
433 config NETFILTER_SYNPROXY
439 select NETFILTER_NETLINK
440 tristate "Netfilter nf_tables support"
442 nftables is the new packet classification framework that intends to
443 replace the existing {ip,ip6,arp,eb}_tables infrastructure. It
444 provides a pseudo-state machine with an extensible instruction-set
445 (also known as expressions) that the userspace 'nft' utility
446 (http://www.netfilter.org/projects/nftables) uses to build the
447 rule-set. It also comes with the generic set infrastructure that
448 allows you to construct mappings between matchings and actions
449 for performance lookups.
451 To compile it as a module, choose M here.
455 config NF_TABLES_INET
457 select NF_TABLES_IPV4
458 select NF_TABLES_IPV6
459 tristate "Netfilter nf_tables mixed IPv4/IPv6 tables support"
461 This option enables support for a mixed IPv4/IPv6 "inet" table.
463 config NF_TABLES_NETDEV
464 tristate "Netfilter nf_tables netdev tables support"
466 This option enables support for the "netdev" table.
469 tristate "Netfilter nf_tables exthdr module"
471 This option adds the "exthdr" expression that you can use to match
472 IPv6 extension headers and tcp options.
475 tristate "Netfilter nf_tables meta module"
477 This option adds the "meta" expression that you can use to match and
478 to set packet metainformation such as the packet mark.
481 tristate "Netfilter nf_tables routing module"
483 This option adds the "rt" expression that you can use to match
484 packet routing information such as the packet nexthop.
487 tristate "Netfilter nf_tables number generator module"
489 This option adds the number generator expression used to perform
490 incremental counting and random numbers bound to a upper limit.
493 depends on NF_CONNTRACK
494 tristate "Netfilter nf_tables conntrack module"
496 This option adds the "ct" expression that you can use to match
497 connection tracking information such as the flow state.
499 config NFT_SET_RBTREE
500 tristate "Netfilter nf_tables rbtree set module"
502 This option adds the "rbtree" set type (Red Black tree) that is used
503 to build interval-based sets.
506 tristate "Netfilter nf_tables hash set module"
508 This option adds the "hash" set type that is used to build one-way
509 mappings between matchings and actions.
511 config NFT_SET_BITMAP
512 tristate "Netfilter nf_tables bitmap set module"
514 This option adds the "bitmap" set type that is used to build sets
515 whose keys are smaller or equal to 16 bits.
518 tristate "Netfilter nf_tables counter module"
520 This option adds the "counter" expression that you can use to
521 include packet and byte counters in a rule.
524 tristate "Netfilter nf_tables log module"
526 This option adds the "log" expression that you can use to log
527 packets matching some criteria.
530 tristate "Netfilter nf_tables limit module"
532 This option adds the "limit" expression that you can use to
533 ratelimit rule matchings.
536 depends on NF_CONNTRACK
538 tristate "Netfilter nf_tables masquerade support"
540 This option adds the "masquerade" expression that you can use
541 to perform NAT in the masquerade flavour.
544 depends on NF_CONNTRACK
546 tristate "Netfilter nf_tables redirect support"
548 This options adds the "redirect" expression that you can use
549 to perform NAT in the redirect flavour.
552 depends on NF_CONNTRACK
554 tristate "Netfilter nf_tables nat module"
556 This option adds the "nat" expression that you can use to perform
557 typical Network Address Translation (NAT) packet transformations.
560 tristate "Netfilter nf_tables stateful object reference module"
562 This option adds the "objref" expression that allows you to refer to
563 stateful objects, such as counters and quotas.
566 depends on NETFILTER_NETLINK_QUEUE
567 tristate "Netfilter nf_tables queue module"
569 This is required if you intend to use the userspace queueing
570 infrastructure (also known as NFQUEUE) from nftables.
573 tristate "Netfilter nf_tables quota module"
575 This option adds the "quota" expression that you can use to match
576 enforce bytes quotas.
579 default m if NETFILTER_ADVANCED=n
580 tristate "Netfilter nf_tables reject support"
582 This option adds the "reject" expression that you can use to
583 explicitly deny and notify via TCP reset/ICMP informational errors
586 config NFT_REJECT_INET
587 depends on NF_TABLES_INET
592 depends on NETFILTER_XTABLES
593 tristate "Netfilter x_tables over nf_tables module"
595 This is required if you intend to use any of existing
596 x_tables match/target extensions over the nf_tables
600 tristate "Netfilter nf_tables hash module"
602 This option adds the "hash" expression that you can use to perform
603 a hash operation on registers.
609 depends on NF_TABLES_INET
610 depends on NFT_FIB_IPV4
611 depends on NFT_FIB_IPV6
612 tristate "Netfilter nf_tables fib inet support"
614 This option allows using the FIB expression from the inet table.
615 The lookup will be delegated to the IPv4 or IPv6 FIB depending
616 on the protocol of the packet.
621 tristate "Netfilter packet duplication support"
623 This option enables the generic packet duplication infrastructure
626 config NFT_DUP_NETDEV
627 tristate "Netfilter nf_tables netdev packet duplication support"
630 This option enables packet duplication for the "netdev" family.
632 config NFT_FWD_NETDEV
633 tristate "Netfilter nf_tables netdev packet forwarding support"
636 This option enables packet forwarding for the "netdev" family.
638 config NFT_FIB_NETDEV
639 depends on NFT_FIB_IPV4
640 depends on NFT_FIB_IPV6
641 tristate "Netfilter nf_tables netdev fib lookups support"
643 This option allows using the FIB expression from the netdev table.
644 The lookup will be delegated to the IPv4 or IPv6 FIB depending
645 on the protocol of the packet.
647 endif # NF_TABLES_NETDEV
651 config NETFILTER_XTABLES
652 tristate "Netfilter Xtables support (required for ip_tables)"
653 default m if NETFILTER_ADVANCED=n
655 This is required if you intend to use any of ip_tables,
656 ip6_tables or arp_tables.
660 comment "Xtables combined modules"
662 config NETFILTER_XT_MARK
663 tristate 'nfmark target and match support'
664 default m if NETFILTER_ADVANCED=n
666 This option adds the "MARK" target and "mark" match.
668 Netfilter mark matching allows you to match packets based on the
669 "nfmark" value in the packet.
670 The target allows you to create rules in the "mangle" table which alter
671 the netfilter mark (nfmark) field associated with the packet.
673 Prior to routing, the nfmark can influence the routing method and can
674 also be used by other subsystems to change their behavior.
676 config NETFILTER_XT_CONNMARK
677 tristate 'ctmark target and match support'
678 depends on NF_CONNTRACK
679 depends on NETFILTER_ADVANCED
680 select NF_CONNTRACK_MARK
682 This option adds the "CONNMARK" target and "connmark" match.
684 Netfilter allows you to store a mark value per connection (a.k.a.
685 ctmark), similarly to the packet mark (nfmark). Using this
686 target and match, you can set and match on this mark.
688 config NETFILTER_XT_SET
689 tristate 'set target and match support'
691 depends on NETFILTER_ADVANCED
693 This option adds the "SET" target and "set" match.
695 Using this target and match, you can add/delete and match
696 elements in the sets created by ipset(8).
698 To compile it as a module, choose M here. If unsure, say N.
700 # alphabetically ordered list of targets
702 comment "Xtables targets"
704 config NETFILTER_XT_TARGET_AUDIT
705 tristate "AUDIT target support"
707 depends on NETFILTER_ADVANCED
709 This option adds a 'AUDIT' target, which can be used to create
710 audit records for packets dropped/accepted.
712 To compileit as a module, choose M here. If unsure, say N.
714 config NETFILTER_XT_TARGET_CHECKSUM
715 tristate "CHECKSUM target support"
716 depends on IP_NF_MANGLE || IP6_NF_MANGLE
717 depends on NETFILTER_ADVANCED
719 This option adds a `CHECKSUM' target, which can be used in the iptables mangle
722 You can use this target to compute and fill in the checksum in
723 a packet that lacks a checksum. This is particularly useful,
724 if you need to work around old applications such as dhcp clients,
725 that do not work well with checksum offloads, but don't want to disable
726 checksum offload in your device.
728 To compile it as a module, choose M here. If unsure, say N.
730 config NETFILTER_XT_TARGET_CLASSIFY
731 tristate '"CLASSIFY" target support'
732 depends on NETFILTER_ADVANCED
734 This option adds a `CLASSIFY' target, which enables the user to set
735 the priority of a packet. Some qdiscs can use this value for
736 classification, among these are:
738 atm, cbq, dsmark, pfifo_fast, htb, prio
740 To compile it as a module, choose M here. If unsure, say N.
742 config NETFILTER_XT_TARGET_CONNMARK
743 tristate '"CONNMARK" target support'
744 depends on NF_CONNTRACK
745 depends on NETFILTER_ADVANCED
746 select NETFILTER_XT_CONNMARK
748 This is a backwards-compat option for the user's convenience
749 (e.g. when running oldconfig). It selects
750 CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
752 config NETFILTER_XT_TARGET_CONNSECMARK
753 tristate '"CONNSECMARK" target support'
754 depends on NF_CONNTRACK && NF_CONNTRACK_SECMARK
755 default m if NETFILTER_ADVANCED=n
757 The CONNSECMARK target copies security markings from packets
758 to connections, and restores security markings from connections
759 to packets (if the packets are not already marked). This would
760 normally be used in conjunction with the SECMARK target.
762 To compile it as a module, choose M here. If unsure, say N.
764 config NETFILTER_XT_TARGET_CT
765 tristate '"CT" target support'
766 depends on NF_CONNTRACK
767 depends on IP_NF_RAW || IP6_NF_RAW
768 depends on NETFILTER_ADVANCED
770 This options adds a `CT' target, which allows to specify initial
771 connection tracking parameters like events to be delivered and
772 the helper to be used.
774 To compile it as a module, choose M here. If unsure, say N.
776 config NETFILTER_XT_TARGET_DSCP
777 tristate '"DSCP" and "TOS" target support'
778 depends on IP_NF_MANGLE || IP6_NF_MANGLE
779 depends on NETFILTER_ADVANCED
781 This option adds a `DSCP' target, which allows you to manipulate
782 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
784 The DSCP field can have any value between 0x0 and 0x3f inclusive.
786 It also adds the "TOS" target, which allows you to create rules in
787 the "mangle" table which alter the Type Of Service field of an IPv4
788 or the Priority field of an IPv6 packet, prior to routing.
790 To compile it as a module, choose M here. If unsure, say N.
792 config NETFILTER_XT_TARGET_HL
793 tristate '"HL" hoplimit target support'
794 depends on IP_NF_MANGLE || IP6_NF_MANGLE
795 depends on NETFILTER_ADVANCED
797 This option adds the "HL" (for IPv6) and "TTL" (for IPv4)
798 targets, which enable the user to change the
799 hoplimit/time-to-live value of the IP header.
801 While it is safe to decrement the hoplimit/TTL value, the
802 modules also allow to increment and set the hoplimit value of
803 the header to arbitrary values. This is EXTREMELY DANGEROUS
804 since you can easily create immortal packets that loop
805 forever on the network.
807 config NETFILTER_XT_TARGET_HMARK
808 tristate '"HMARK" target support'
809 depends on IP6_NF_IPTABLES || IP6_NF_IPTABLES=n
810 depends on NETFILTER_ADVANCED
812 This option adds the "HMARK" target.
814 The target allows you to create rules in the "raw" and "mangle" tables
815 which set the skbuff mark by means of hash calculation within a given
816 range. The nfmark can influence the routing method and can also be used
817 by other subsystems to change their behaviour.
819 To compile it as a module, choose M here. If unsure, say N.
821 config NETFILTER_XT_TARGET_IDLETIMER
822 tristate "IDLETIMER target support"
823 depends on NETFILTER_ADVANCED
826 This option adds the `IDLETIMER' target. Each matching packet
827 resets the timer associated with label specified when the rule is
828 added. When the timer expires, it triggers a sysfs notification.
829 The remaining time for expiration can be read via sysfs.
831 To compile it as a module, choose M here. If unsure, say N.
833 config NETFILTER_XT_TARGET_LED
834 tristate '"LED" target support'
835 depends on LEDS_CLASS && LEDS_TRIGGERS
836 depends on NETFILTER_ADVANCED
838 This option adds a `LED' target, which allows you to blink LEDs in
839 response to particular packets passing through your machine.
841 This can be used to turn a spare LED into a network activity LED,
842 which only flashes in response to FTP transfers, for example. Or
843 you could have an LED which lights up for a minute or two every time
844 somebody connects to your machine via SSH.
846 You will need support for the "led" class to make this work.
848 To create an LED trigger for incoming SSH traffic:
849 iptables -A INPUT -p tcp --dport 22 -j LED --led-trigger-id ssh --led-delay 1000
851 Then attach the new trigger to an LED on your system:
852 echo netfilter-ssh > /sys/class/leds/<ledname>/trigger
854 For more information on the LEDs available on your system, see
855 Documentation/leds/leds-class.txt
857 config NETFILTER_XT_TARGET_LOG
858 tristate "LOG target support"
861 select NF_LOG_IPV6 if IPV6
862 default m if NETFILTER_ADVANCED=n
864 This option adds a `LOG' target, which allows you to create rules in
865 any iptables table which records the packet header to the syslog.
867 To compile it as a module, choose M here. If unsure, say N.
869 config NETFILTER_XT_TARGET_MARK
870 tristate '"MARK" target support'
871 depends on NETFILTER_ADVANCED
872 select NETFILTER_XT_MARK
874 This is a backwards-compat option for the user's convenience
875 (e.g. when running oldconfig). It selects
876 CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
878 config NETFILTER_XT_NAT
879 tristate '"SNAT and DNAT" targets support'
882 This option enables the SNAT and DNAT targets.
884 To compile it as a module, choose M here. If unsure, say N.
886 config NETFILTER_XT_TARGET_NETMAP
887 tristate '"NETMAP" target support'
890 NETMAP is an implementation of static 1:1 NAT mapping of network
891 addresses. It maps the network address part, while keeping the host
894 To compile it as a module, choose M here. If unsure, say N.
896 config NETFILTER_XT_TARGET_NFLOG
897 tristate '"NFLOG" target support'
898 default m if NETFILTER_ADVANCED=n
899 select NETFILTER_NETLINK_LOG
901 This option enables the NFLOG target, which allows to LOG
902 messages through nfnetlink_log.
904 To compile it as a module, choose M here. If unsure, say N.
906 config NETFILTER_XT_TARGET_NFQUEUE
907 tristate '"NFQUEUE" target Support'
908 depends on NETFILTER_ADVANCED
909 select NETFILTER_NETLINK_QUEUE
911 This target replaced the old obsolete QUEUE target.
913 As opposed to QUEUE, it supports 65535 different queues,
916 To compile it as a module, choose M here. If unsure, say N.
918 config NETFILTER_XT_TARGET_NOTRACK
919 tristate '"NOTRACK" target support (DEPRECATED)'
920 depends on NF_CONNTRACK
921 depends on IP_NF_RAW || IP6_NF_RAW
922 depends on NETFILTER_ADVANCED
923 select NETFILTER_XT_TARGET_CT
925 config NETFILTER_XT_TARGET_RATEEST
926 tristate '"RATEEST" target support'
927 depends on NETFILTER_ADVANCED
929 This option adds a `RATEEST' target, which allows to measure
930 rates similar to TC estimators. The `rateest' match can be
931 used to match on the measured rates.
933 To compile it as a module, choose M here. If unsure, say N.
935 config NETFILTER_XT_TARGET_REDIRECT
936 tristate "REDIRECT target support"
938 select NF_NAT_REDIRECT
940 REDIRECT is a special case of NAT: all incoming connections are
941 mapped onto the incoming interface's address, causing the packets to
942 come to the local machine instead of passing through. This is
943 useful for transparent proxies.
945 To compile it as a module, choose M here. If unsure, say N.
947 config NETFILTER_XT_TARGET_TEE
948 tristate '"TEE" - packet cloning to alternate destination'
949 depends on NETFILTER_ADVANCED
950 depends on IPV6 || IPV6=n
951 depends on !NF_CONNTRACK || NF_CONNTRACK
953 select NF_DUP_IPV6 if IPV6
955 This option adds a "TEE" target with which a packet can be cloned and
956 this clone be rerouted to another nexthop.
958 config NETFILTER_XT_TARGET_TPROXY
959 tristate '"TPROXY" target transparent proxying support'
960 depends on NETFILTER_XTABLES
961 depends on NETFILTER_ADVANCED
962 depends on IPV6 || IPV6=n
963 depends on IP6_NF_IPTABLES || IP6_NF_IPTABLES=n
964 depends on IP_NF_MANGLE
965 select NF_DEFRAG_IPV4
966 select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES != n
968 This option adds a `TPROXY' target, which is somewhat similar to
969 REDIRECT. It can only be used in the mangle table and is useful
970 to redirect traffic to a transparent proxy. It does _not_ depend
971 on Netfilter connection tracking and NAT, unlike REDIRECT.
972 For it to work you will have to configure certain iptables rules
973 and use policy routing. For more information on how to set it up
974 see Documentation/networking/tproxy.txt.
976 To compile it as a module, choose M here. If unsure, say N.
978 config NETFILTER_XT_TARGET_TRACE
979 tristate '"TRACE" target support'
980 depends on IP_NF_RAW || IP6_NF_RAW
981 depends on NETFILTER_ADVANCED
983 The TRACE target allows you to mark packets so that the kernel
984 will log every rule which match the packets as those traverse
985 the tables, chains, rules.
987 If you want to compile it as a module, say M here and read
988 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
990 config NETFILTER_XT_TARGET_SECMARK
991 tristate '"SECMARK" target support'
992 depends on NETWORK_SECMARK
993 default m if NETFILTER_ADVANCED=n
995 The SECMARK target allows security marking of network
996 packets, for use with security subsystems.
998 To compile it as a module, choose M here. If unsure, say N.
1000 config NETFILTER_XT_TARGET_TCPMSS
1001 tristate '"TCPMSS" target support'
1002 depends on IPV6 || IPV6=n
1003 default m if NETFILTER_ADVANCED=n
1005 This option adds a `TCPMSS' target, which allows you to alter the
1006 MSS value of TCP SYN packets, to control the maximum size for that
1007 connection (usually limiting it to your outgoing interface's MTU
1010 This is used to overcome criminally braindead ISPs or servers which
1011 block ICMP Fragmentation Needed packets. The symptoms of this
1012 problem are that everything works fine from your Linux
1013 firewall/router, but machines behind it can never exchange large
1015 1) Web browsers connect, then hang with no data received.
1016 2) Small mail works fine, but large emails hang.
1017 3) ssh works fine, but scp hangs after initial handshaking.
1019 Workaround: activate this option and add a rule to your firewall
1022 iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
1023 -j TCPMSS --clamp-mss-to-pmtu
1025 To compile it as a module, choose M here. If unsure, say N.
1027 config NETFILTER_XT_TARGET_TCPOPTSTRIP
1028 tristate '"TCPOPTSTRIP" target support'
1029 depends on IP_NF_MANGLE || IP6_NF_MANGLE
1030 depends on NETFILTER_ADVANCED
1032 This option adds a "TCPOPTSTRIP" target, which allows you to strip
1033 TCP options from TCP packets.
1035 # alphabetically ordered list of matches
1037 comment "Xtables matches"
1039 config NETFILTER_XT_MATCH_ADDRTYPE
1040 tristate '"addrtype" address type match support'
1041 default m if NETFILTER_ADVANCED=n
1043 This option allows you to match what routing thinks of an address,
1044 eg. UNICAST, LOCAL, BROADCAST, ...
1046 If you want to compile it as a module, say M here and read
1047 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1049 config NETFILTER_XT_MATCH_BPF
1050 tristate '"bpf" match support'
1051 depends on NETFILTER_ADVANCED
1053 BPF matching applies a linux socket filter to each packet and
1054 accepts those for which the filter returns non-zero.
1056 To compile it as a module, choose M here. If unsure, say N.
1058 config NETFILTER_XT_MATCH_CGROUP
1059 tristate '"control group" match support'
1060 depends on NETFILTER_ADVANCED
1062 select CGROUP_NET_CLASSID
1064 Socket/process control group matching allows you to match locally
1065 generated packets based on which net_cls control group processes
1068 config NETFILTER_XT_MATCH_CLUSTER
1069 tristate '"cluster" match support'
1070 depends on NF_CONNTRACK
1071 depends on NETFILTER_ADVANCED
1073 This option allows you to build work-load-sharing clusters of
1074 network servers/stateful firewalls without having a dedicated
1075 load-balancing router/server/switch. Basically, this match returns
1076 true when the packet must be handled by this cluster node. Thus,
1077 all nodes see all packets and this match decides which node handles
1078 what packets. The work-load sharing algorithm is based on source
1081 If you say Y or M here, try `iptables -m cluster --help` for
1084 config NETFILTER_XT_MATCH_COMMENT
1085 tristate '"comment" match support'
1086 depends on NETFILTER_ADVANCED
1088 This option adds a `comment' dummy-match, which allows you to put
1089 comments in your iptables ruleset.
1091 If you want to compile it as a module, say M here and read
1092 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1094 config NETFILTER_XT_MATCH_CONNBYTES
1095 tristate '"connbytes" per-connection counter match support'
1096 depends on NF_CONNTRACK
1097 depends on NETFILTER_ADVANCED
1099 This option adds a `connbytes' match, which allows you to match the
1100 number of bytes and/or packets for each direction within a connection.
1102 If you want to compile it as a module, say M here and read
1103 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1105 config NETFILTER_XT_MATCH_CONNLABEL
1106 tristate '"connlabel" match support'
1107 select NF_CONNTRACK_LABELS
1108 depends on NF_CONNTRACK
1109 depends on NETFILTER_ADVANCED
1111 This match allows you to test and assign userspace-defined labels names
1112 to a connection. The kernel only stores bit values - mapping
1113 names to bits is done by userspace.
1115 Unlike connmark, more than 32 flag bits may be assigned to a
1116 connection simultaneously.
1118 config NETFILTER_XT_MATCH_CONNLIMIT
1119 tristate '"connlimit" match support'
1120 depends on NF_CONNTRACK
1121 depends on NETFILTER_ADVANCED
1123 This match allows you to match against the number of parallel
1124 connections to a server per client IP address (or address block).
1126 config NETFILTER_XT_MATCH_CONNMARK
1127 tristate '"connmark" connection mark match support'
1128 depends on NF_CONNTRACK
1129 depends on NETFILTER_ADVANCED
1130 select NETFILTER_XT_CONNMARK
1132 This is a backwards-compat option for the user's convenience
1133 (e.g. when running oldconfig). It selects
1134 CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
1136 config NETFILTER_XT_MATCH_CONNTRACK
1137 tristate '"conntrack" connection tracking match support'
1138 depends on NF_CONNTRACK
1139 default m if NETFILTER_ADVANCED=n
1141 This is a general conntrack match module, a superset of the state match.
1143 It allows matching on additional conntrack information, which is
1144 useful in complex configurations, such as NAT gateways with multiple
1145 internet links or tunnels.
1147 To compile it as a module, choose M here. If unsure, say N.
1149 config NETFILTER_XT_MATCH_CPU
1150 tristate '"cpu" match support'
1151 depends on NETFILTER_ADVANCED
1153 CPU matching allows you to match packets based on the CPU
1154 currently handling the packet.
1156 To compile it as a module, choose M here. If unsure, say N.
1158 config NETFILTER_XT_MATCH_DCCP
1159 tristate '"dccp" protocol match support'
1160 depends on NETFILTER_ADVANCED
1163 With this option enabled, you will be able to use the iptables
1164 `dccp' match in order to match on DCCP source/destination ports
1167 If you want to compile it as a module, say M here and read
1168 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1170 config NETFILTER_XT_MATCH_DEVGROUP
1171 tristate '"devgroup" match support'
1172 depends on NETFILTER_ADVANCED
1174 This options adds a `devgroup' match, which allows to match on the
1175 device group a network device is assigned to.
1177 To compile it as a module, choose M here. If unsure, say N.
1179 config NETFILTER_XT_MATCH_DSCP
1180 tristate '"dscp" and "tos" match support'
1181 depends on NETFILTER_ADVANCED
1183 This option adds a `DSCP' match, which allows you to match against
1184 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
1186 The DSCP field can have any value between 0x0 and 0x3f inclusive.
1188 It will also add a "tos" match, which allows you to match packets
1189 based on the Type Of Service fields of the IPv4 packet (which share
1190 the same bits as DSCP).
1192 To compile it as a module, choose M here. If unsure, say N.
1194 config NETFILTER_XT_MATCH_ECN
1195 tristate '"ecn" match support'
1196 depends on NETFILTER_ADVANCED
1198 This option adds an "ECN" match, which allows you to match against
1199 the IPv4 and TCP header ECN fields.
1201 To compile it as a module, choose M here. If unsure, say N.
1203 config NETFILTER_XT_MATCH_ESP
1204 tristate '"esp" match support'
1205 depends on NETFILTER_ADVANCED
1207 This match extension allows you to match a range of SPIs
1208 inside ESP header of IPSec packets.
1210 To compile it as a module, choose M here. If unsure, say N.
1212 config NETFILTER_XT_MATCH_HASHLIMIT
1213 tristate '"hashlimit" match support'
1214 depends on IP6_NF_IPTABLES || IP6_NF_IPTABLES=n
1215 depends on NETFILTER_ADVANCED
1217 This option adds a `hashlimit' match.
1219 As opposed to `limit', this match dynamically creates a hash table
1220 of limit buckets, based on your selection of source/destination
1221 addresses and/or ports.
1223 It enables you to express policies like `10kpps for any given
1224 destination address' or `500pps from any given source address'
1227 config NETFILTER_XT_MATCH_HELPER
1228 tristate '"helper" match support'
1229 depends on NF_CONNTRACK
1230 depends on NETFILTER_ADVANCED
1232 Helper matching allows you to match packets in dynamic connections
1233 tracked by a conntrack-helper, ie. ip_conntrack_ftp
1235 To compile it as a module, choose M here. If unsure, say Y.
1237 config NETFILTER_XT_MATCH_HL
1238 tristate '"hl" hoplimit/TTL match support'
1239 depends on NETFILTER_ADVANCED
1241 HL matching allows you to match packets based on the hoplimit
1242 in the IPv6 header, or the time-to-live field in the IPv4
1243 header of the packet.
1245 config NETFILTER_XT_MATCH_IPCOMP
1246 tristate '"ipcomp" match support'
1247 depends on NETFILTER_ADVANCED
1249 This match extension allows you to match a range of CPIs(16 bits)
1250 inside IPComp header of IPSec packets.
1252 To compile it as a module, choose M here. If unsure, say N.
1254 config NETFILTER_XT_MATCH_IPRANGE
1255 tristate '"iprange" address range match support'
1256 depends on NETFILTER_ADVANCED
1258 This option adds a "iprange" match, which allows you to match based on
1259 an IP address range. (Normal iptables only matches on single addresses
1260 with an optional mask.)
1264 config NETFILTER_XT_MATCH_IPVS
1265 tristate '"ipvs" match support'
1267 depends on NETFILTER_ADVANCED
1268 depends on NF_CONNTRACK
1270 This option allows you to match against IPVS properties of a packet.
1274 config NETFILTER_XT_MATCH_L2TP
1275 tristate '"l2tp" match support'
1276 depends on NETFILTER_ADVANCED
1279 This option adds an "L2TP" match, which allows you to match against
1280 L2TP protocol header fields.
1282 To compile it as a module, choose M here. If unsure, say N.
1284 config NETFILTER_XT_MATCH_LENGTH
1285 tristate '"length" match support'
1286 depends on NETFILTER_ADVANCED
1288 This option allows you to match the length of a packet against a
1289 specific value or range of values.
1291 To compile it as a module, choose M here. If unsure, say N.
1293 config NETFILTER_XT_MATCH_LIMIT
1294 tristate '"limit" match support'
1295 depends on NETFILTER_ADVANCED
1297 limit matching allows you to control the rate at which a rule can be
1298 matched: mainly useful in combination with the LOG target ("LOG
1299 target support", below) and to avoid some Denial of Service attacks.
1301 To compile it as a module, choose M here. If unsure, say N.
1303 config NETFILTER_XT_MATCH_MAC
1304 tristate '"mac" address match support'
1305 depends on NETFILTER_ADVANCED
1307 MAC matching allows you to match packets based on the source
1308 Ethernet address of the packet.
1310 To compile it as a module, choose M here. If unsure, say N.
1312 config NETFILTER_XT_MATCH_MARK
1313 tristate '"mark" match support'
1314 depends on NETFILTER_ADVANCED
1315 select NETFILTER_XT_MARK
1317 This is a backwards-compat option for the user's convenience
1318 (e.g. when running oldconfig). It selects
1319 CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
1321 config NETFILTER_XT_MATCH_MULTIPORT
1322 tristate '"multiport" Multiple port match support'
1323 depends on NETFILTER_ADVANCED
1325 Multiport matching allows you to match TCP or UDP packets based on
1326 a series of source or destination ports: normally a rule can only
1327 match a single range of ports.
1329 To compile it as a module, choose M here. If unsure, say N.
1331 config NETFILTER_XT_MATCH_NFACCT
1332 tristate '"nfacct" match support'
1333 depends on NETFILTER_ADVANCED
1334 select NETFILTER_NETLINK_ACCT
1336 This option allows you to use the extended accounting through
1339 To compile it as a module, choose M here. If unsure, say N.
1341 config NETFILTER_XT_MATCH_OSF
1342 tristate '"osf" Passive OS fingerprint match'
1343 depends on NETFILTER_ADVANCED && NETFILTER_NETLINK
1345 This option selects the Passive OS Fingerprinting match module
1346 that allows to passively match the remote operating system by
1347 analyzing incoming TCP SYN packets.
1349 Rules and loading software can be downloaded from
1350 http://www.ioremap.net/projects/osf
1352 To compile it as a module, choose M here. If unsure, say N.
1354 config NETFILTER_XT_MATCH_OWNER
1355 tristate '"owner" match support'
1356 depends on NETFILTER_ADVANCED
1358 Socket owner matching allows you to match locally-generated packets
1359 based on who created the socket: the user or group. It is also
1360 possible to check whether a socket actually exists.
1362 config NETFILTER_XT_MATCH_POLICY
1363 tristate 'IPsec "policy" match support'
1365 default m if NETFILTER_ADVANCED=n
1367 Policy matching allows you to match packets based on the
1368 IPsec policy that was used during decapsulation/will
1369 be used during encapsulation.
1371 To compile it as a module, choose M here. If unsure, say N.
1373 config NETFILTER_XT_MATCH_PHYSDEV
1374 tristate '"physdev" match support'
1375 depends on BRIDGE && BRIDGE_NETFILTER
1376 depends on NETFILTER_ADVANCED
1378 Physdev packet matching matches against the physical bridge ports
1379 the IP packet arrived on or will leave by.
1381 To compile it as a module, choose M here. If unsure, say N.
1383 config NETFILTER_XT_MATCH_PKTTYPE
1384 tristate '"pkttype" packet type match support'
1385 depends on NETFILTER_ADVANCED
1387 Packet type matching allows you to match a packet by
1388 its "class", eg. BROADCAST, MULTICAST, ...
1391 iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG
1393 To compile it as a module, choose M here. If unsure, say N.
1395 config NETFILTER_XT_MATCH_QUOTA
1396 tristate '"quota" match support'
1397 depends on NETFILTER_ADVANCED
1399 This option adds a `quota' match, which allows to match on a
1402 If you want to compile it as a module, say M here and read
1403 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1405 config NETFILTER_XT_MATCH_RATEEST
1406 tristate '"rateest" match support'
1407 depends on NETFILTER_ADVANCED
1408 select NETFILTER_XT_TARGET_RATEEST
1410 This option adds a `rateest' match, which allows to match on the
1411 rate estimated by the RATEEST target.
1413 To compile it as a module, choose M here. If unsure, say N.
1415 config NETFILTER_XT_MATCH_REALM
1416 tristate '"realm" match support'
1417 depends on NETFILTER_ADVANCED
1418 select IP_ROUTE_CLASSID
1420 This option adds a `realm' match, which allows you to use the realm
1421 key from the routing subsystem inside iptables.
1423 This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option
1426 If you want to compile it as a module, say M here and read
1427 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1429 config NETFILTER_XT_MATCH_RECENT
1430 tristate '"recent" match support'
1431 depends on NETFILTER_ADVANCED
1433 This match is used for creating one or many lists of recently
1434 used addresses and then matching against that/those list(s).
1436 Short options are available by using 'iptables -m recent -h'
1437 Official Website: <http://snowman.net/projects/ipt_recent/>
1439 config NETFILTER_XT_MATCH_SCTP
1440 tristate '"sctp" protocol match support'
1441 depends on NETFILTER_ADVANCED
1444 With this option enabled, you will be able to use the
1445 `sctp' match in order to match on SCTP source/destination ports
1446 and SCTP chunk types.
1448 If you want to compile it as a module, say M here and read
1449 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1451 config NETFILTER_XT_MATCH_SOCKET
1452 tristate '"socket" match support'
1453 depends on NETFILTER_XTABLES
1454 depends on NETFILTER_ADVANCED
1455 depends on IPV6 || IPV6=n
1456 depends on IP6_NF_IPTABLES || IP6_NF_IPTABLES=n
1457 depends on NF_SOCKET_IPV4
1458 depends on NF_SOCKET_IPV6
1459 select NF_DEFRAG_IPV4
1460 select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES != n
1462 This option adds a `socket' match, which can be used to match
1463 packets for which a TCP or UDP socket lookup finds a valid socket.
1464 It can be used in combination with the MARK target and policy
1465 routing to implement full featured non-locally bound sockets.
1467 To compile it as a module, choose M here. If unsure, say N.
1469 config NETFILTER_XT_MATCH_STATE
1470 tristate '"state" match support'
1471 depends on NF_CONNTRACK
1472 default m if NETFILTER_ADVANCED=n
1474 Connection state matching allows you to match packets based on their
1475 relationship to a tracked connection (ie. previous packets). This
1476 is a powerful tool for packet classification.
1478 To compile it as a module, choose M here. If unsure, say N.
1480 config NETFILTER_XT_MATCH_STATISTIC
1481 tristate '"statistic" match support'
1482 depends on NETFILTER_ADVANCED
1484 This option adds a `statistic' match, which allows you to match
1485 on packets periodically or randomly with a given percentage.
1487 To compile it as a module, choose M here. If unsure, say N.
1489 config NETFILTER_XT_MATCH_STRING
1490 tristate '"string" match support'
1491 depends on NETFILTER_ADVANCED
1493 select TEXTSEARCH_KMP
1494 select TEXTSEARCH_BM
1495 select TEXTSEARCH_FSM
1497 This option adds a `string' match, which allows you to look for
1498 pattern matchings in packets.
1500 To compile it as a module, choose M here. If unsure, say N.
1502 config NETFILTER_XT_MATCH_TCPMSS
1503 tristate '"tcpmss" match support'
1504 depends on NETFILTER_ADVANCED
1506 This option adds a `tcpmss' match, which allows you to examine the
1507 MSS value of TCP SYN packets, which control the maximum packet size
1508 for that connection.
1510 To compile it as a module, choose M here. If unsure, say N.
1512 config NETFILTER_XT_MATCH_TIME
1513 tristate '"time" match support'
1514 depends on NETFILTER_ADVANCED
1516 This option adds a "time" match, which allows you to match based on
1517 the packet arrival time (at the machine which netfilter is running)
1518 on) or departure time/date (for locally generated packets).
1520 If you say Y here, try `iptables -m time --help` for
1523 If you want to compile it as a module, say M here.
1526 config NETFILTER_XT_MATCH_U32
1527 tristate '"u32" match support'
1528 depends on NETFILTER_ADVANCED
1530 u32 allows you to extract quantities of up to 4 bytes from a packet,
1531 AND them with specified masks, shift them by specified amounts and
1532 test whether the results are in any of a set of specified ranges.
1533 The specification of what to extract is general enough to skip over
1534 headers with lengths stored in the packet, as in IP or TCP header
1537 Details and examples are in the kernel module source.
1539 endif # NETFILTER_XTABLES
1543 source "net/netfilter/ipset/Kconfig"
1545 source "net/netfilter/ipvs/Kconfig"