net/netfilter/Kconfig

   1 menu "Core Netfilter Configuration"
   2         depends on NET && INET && NETFILTER
   3
   4 config NETFILTER_NETLINK
   5         tristate
   6
   7 config NETFILTER_NETLINK_ACCT
   8 tristate "Netfilter NFACCT over NFNETLINK interface"
   9         depends on NETFILTER_ADVANCED
  10         select NETFILTER_NETLINK
  11         help
  12           If this option is enabled, the kernel will include support
  13           for extended accounting via NFNETLINK.
  14
  15 config NETFILTER_NETLINK_QUEUE
  16         tristate "Netfilter NFQUEUE over NFNETLINK interface"
  17         depends on NETFILTER_ADVANCED
  18         select NETFILTER_NETLINK
  19         help
  20           If this option is enabled, the kernel will include support
  21           for queueing packets via NFNETLINK.
  22
  23 config NETFILTER_NETLINK_LOG
  24         tristate "Netfilter LOG over NFNETLINK interface"
  25         default m if NETFILTER_ADVANCED=n
  26         select NETFILTER_NETLINK
  27         help
  28           If this option is enabled, the kernel will include support
  29           for logging packets via NFNETLINK.
  30
  31           This obsoletes the existing ipt_ULOG and ebg_ulog mechanisms,
  32           and is also scheduled to replace the old syslog-based ipt_LOG
  33           and ip6t_LOG modules.
  34
  35 config NF_CONNTRACK
  36         tristate "Netfilter connection tracking support"
  37         default m if NETFILTER_ADVANCED=n
  38         help
  39           Connection tracking keeps a record of what packets have passed
  40           through your machine, in order to figure out how they are related
  41           into connections.
  42
  43           This is required to do Masquerading or other kinds of Network
  44           Address Translation.  It can also be used to enhance packet
  45           filtering (see `Connection state match support' below).
  46
  47           To compile it as a module, choose M here.  If unsure, say N.
  48
  49 if NF_CONNTRACK
  50
  51 config NF_CONNTRACK_MARK
  52         bool  'Connection mark tracking support'
  53         depends on NETFILTER_ADVANCED
  54         help
  55           This option enables support for connection marks, used by the
  56           `CONNMARK' target and `connmark' match. Similar to the mark value
  57           of packets, but this mark value is kept in the conntrack session
  58           instead of the individual packets.
  59
  60 config NF_CONNTRACK_SECMARK
  61         bool  'Connection tracking security mark support'
  62         depends on NETWORK_SECMARK
  63         default m if NETFILTER_ADVANCED=n
  64         help
  65           This option enables security markings to be applied to
  66           connections.  Typically they are copied to connections from
  67           packets using the CONNSECMARK target and copied back from
  68           connections to packets with the same target, with the packets
  69           being originally labeled via SECMARK.
  70
  71           If unsure, say 'N'.
  72
  73 config NF_CONNTRACK_ZONES
  74         bool  'Connection tracking zones'
  75         depends on NETFILTER_ADVANCED
  76         depends on NETFILTER_XT_TARGET_CT
  77         help
  78           This option enables support for connection tracking zones.
  79           Normally, each connection needs to have a unique system wide
  80           identity. Connection tracking zones allow to have multiple
  81           connections using the same identity, as long as they are
  82           contained in different zones.
  83
  84           If unsure, say `N'.
  85
  86 config NF_CONNTRACK_PROCFS
  87         bool "Supply CT list in procfs (OBSOLETE)"
  88         default y
  89         depends on PROC_FS
  90         ---help---
  91         This option enables for the list of known conntrack entries
  92         to be shown in procfs under net/netfilter/nf_conntrack. This
  93         is considered obsolete in favor of using the conntrack(8)
  94         tool which uses Netlink.
  95
  96 config NF_CONNTRACK_EVENTS
  97         bool "Connection tracking events"
  98         depends on NETFILTER_ADVANCED
  99         help
 100           If this option is enabled, the connection tracking code will
 101           provide a notifier chain that can be used by other kernel code
 102           to get notified about changes in the connection tracking state.
 103
 104           If unsure, say `N'.
 105
 106 config NF_CONNTRACK_TIMEOUT
 107         bool  'Connection tracking timeout'
 108         depends on NETFILTER_ADVANCED
 109         help
 110           This option enables support for connection tracking timeout
 111           extension. This allows you to attach timeout policies to flow
 112           via the CT target.
 113
 114           If unsure, say `N'.
 115
 116 config NF_CONNTRACK_TIMESTAMP
 117         bool  'Connection tracking timestamping'
 118         depends on NETFILTER_ADVANCED
 119         help
 120           This option enables support for connection tracking timestamping.
 121           This allows you to store the flow start-time and to obtain
 122           the flow-stop time (once it has been destroyed) via Connection
 123           tracking events.
 124
 125           If unsure, say `N'.
 126
 127 config NF_CONNTRACK_LABELS
 128         bool
 129         help
 130           This option enables support for assigning user-defined flag bits
 131           to connection tracking entries.  It selected by the connlabel match.
 132
 133 config NF_CT_PROTO_DCCP
 134         tristate 'DCCP protocol connection tracking support'
 135         depends on NETFILTER_ADVANCED
 136         default IP_DCCP
 137         help
 138           With this option enabled, the layer 3 independent connection
 139           tracking code will be able to do state tracking on DCCP connections.
 140
 141           If unsure, say 'N'.
 142
 143 config NF_CT_PROTO_GRE
 144         tristate
 145
 146 config NF_CT_PROTO_SCTP
 147         tristate 'SCTP protocol connection tracking support'
 148         depends on NETFILTER_ADVANCED
 149         default IP_SCTP
 150         help
 151           With this option enabled, the layer 3 independent connection
 152           tracking code will be able to do state tracking on SCTP connections.
 153
 154           If you want to compile it as a module, say M here and read
 155           <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
 156
 157 config NF_CT_PROTO_UDPLITE
 158         tristate 'UDP-Lite protocol connection tracking support'
 159         depends on NETFILTER_ADVANCED
 160         help
 161           With this option enabled, the layer 3 independent connection
 162           tracking code will be able to do state tracking on UDP-Lite
 163           connections.
 164
 165           To compile it as a module, choose M here.  If unsure, say N.
 166
 167 config NF_CONNTRACK_AMANDA
 168         tristate "Amanda backup protocol support"
 169         depends on NETFILTER_ADVANCED
 170         select TEXTSEARCH
 171         select TEXTSEARCH_KMP
 172         help
 173           If you are running the Amanda backup package <http://www.amanda.org/>
 174           on this machine or machines that will be MASQUERADED through this
 175           machine, then you may want to enable this feature.  This allows the
 176           connection tracking and natting code to allow the sub-channels that
 177           Amanda requires for communication of the backup data, messages and
 178           index.
 179
 180           To compile it as a module, choose M here.  If unsure, say N.
 181
 182 config NF_CONNTRACK_FTP
 183         tristate "FTP protocol support"
 184         default m if NETFILTER_ADVANCED=n
 185         help
 186           Tracking FTP connections is problematic: special helpers are
 187           required for tracking them, and doing masquerading and other forms
 188           of Network Address Translation on them.
 189
 190           This is FTP support on Layer 3 independent connection tracking.
 191           Layer 3 independent connection tracking is experimental scheme
 192           which generalize ip_conntrack to support other layer 3 protocols.
 193
 194           To compile it as a module, choose M here.  If unsure, say N.
 195
 196 config NF_CONNTRACK_H323
 197         tristate "H.323 protocol support"
 198         depends on (IPV6 || IPV6=n)
 199         depends on NETFILTER_ADVANCED
 200         help
 201           H.323 is a VoIP signalling protocol from ITU-T. As one of the most
 202           important VoIP protocols, it is widely used by voice hardware and
 203           software including voice gateways, IP phones, Netmeeting, OpenPhone,
 204           Gnomemeeting, etc.
 205
 206           With this module you can support H.323 on a connection tracking/NAT
 207           firewall.
 208
 209           This module supports RAS, Fast Start, H.245 Tunnelling, Call
 210           Forwarding, RTP/RTCP and T.120 based audio, video, fax, chat,
 211           whiteboard, file transfer, etc. For more information, please
 212           visit http://nath323.sourceforge.net/.
 213
 214           To compile it as a module, choose M here.  If unsure, say N.
 215
 216 config NF_CONNTRACK_IRC
 217         tristate "IRC protocol support"
 218         default m if NETFILTER_ADVANCED=n
 219         help
 220           There is a commonly-used extension to IRC called
 221           Direct Client-to-Client Protocol (DCC).  This enables users to send
 222           files to each other, and also chat to each other without the need
 223           of a server.  DCC Sending is used anywhere you send files over IRC,
 224           and DCC Chat is most commonly used by Eggdrop bots.  If you are
 225           using NAT, this extension will enable you to send files and initiate
 226           chats.  Note that you do NOT need this extension to get files or
 227           have others initiate chats, or everything else in IRC.
 228
 229           To compile it as a module, choose M here.  If unsure, say N.
 230
 231 config NF_CONNTRACK_BROADCAST
 232         tristate
 233
 234 config NF_CONNTRACK_NETBIOS_NS
 235         tristate "NetBIOS name service protocol support"
 236         select NF_CONNTRACK_BROADCAST
 237         help
 238           NetBIOS name service requests are sent as broadcast messages from an
 239           unprivileged port and responded to with unicast messages to the
 240           same port. This make them hard to firewall properly because connection
 241           tracking doesn't deal with broadcasts. This helper tracks locally
 242           originating NetBIOS name service requests and the corresponding
 243           responses. It relies on correct IP address configuration, specifically
 244           netmask and broadcast address. When properly configured, the output
 245           of "ip address show" should look similar to this:
 246
 247           $ ip -4 address show eth0
 248           4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
 249               inet 172.16.2.252/24 brd 172.16.2.255 scope global eth0
 250
 251           To compile it as a module, choose M here.  If unsure, say N.
 252
 253 config NF_CONNTRACK_SNMP
 254         tristate "SNMP service protocol support"
 255         depends on NETFILTER_ADVANCED
 256         select NF_CONNTRACK_BROADCAST
 257         help
 258           SNMP service requests are sent as broadcast messages from an
 259           unprivileged port and responded to with unicast messages to the
 260           same port. This make them hard to firewall properly because connection
 261           tracking doesn't deal with broadcasts. This helper tracks locally
 262           originating SNMP service requests and the corresponding
 263           responses. It relies on correct IP address configuration, specifically
 264           netmask and broadcast address.
 265
 266           To compile it as a module, choose M here.  If unsure, say N.
 267
 268 config NF_CONNTRACK_PPTP
 269         tristate "PPtP protocol support"
 270         depends on NETFILTER_ADVANCED
 271         select NF_CT_PROTO_GRE
 272         help
 273           This module adds support for PPTP (Point to Point Tunnelling
 274           Protocol, RFC2637) connection tracking and NAT.
 275
 276           If you are running PPTP sessions over a stateful firewall or NAT
 277           box, you may want to enable this feature.
 278
 279           Please note that not all PPTP modes of operation are supported yet.
 280           Specifically these limitations exist:
 281             - Blindly assumes that control connections are always established
 282               in PNS->PAC direction. This is a violation of RFC2637.
 283             - Only supports a single call within each session
 284
 285           To compile it as a module, choose M here.  If unsure, say N.
 286
 287 config NF_CONNTRACK_SANE
 288         tristate "SANE protocol support"
 289         depends on NETFILTER_ADVANCED
 290         help
 291           SANE is a protocol for remote access to scanners as implemented
 292           by the 'saned' daemon. Like FTP, it uses separate control and
 293           data connections.
 294
 295           With this module you can support SANE on a connection tracking
 296           firewall.
 297
 298           To compile it as a module, choose M here.  If unsure, say N.
 299
 300 config NF_CONNTRACK_SIP
 301         tristate "SIP protocol support"
 302         default m if NETFILTER_ADVANCED=n
 303         help
 304           SIP is an application-layer control protocol that can establish,
 305           modify, and terminate multimedia sessions (conferences) such as
 306           Internet telephony calls. With the ip_conntrack_sip and
 307           the nf_nat_sip modules you can support the protocol on a connection
 308           tracking/NATing firewall.
 309
 310           To compile it as a module, choose M here.  If unsure, say N.
 311
 312 config NF_CONNTRACK_TFTP
 313         tristate "TFTP protocol support"
 314         depends on NETFILTER_ADVANCED
 315         help
 316           TFTP connection tracking helper, this is required depending
 317           on how restrictive your ruleset is.
 318           If you are using a tftp client behind -j SNAT or -j MASQUERADING
 319           you will need this.
 320
 321           To compile it as a module, choose M here.  If unsure, say N.
 322
 323 config NF_CT_NETLINK
 324         tristate 'Connection tracking netlink interface'
 325         select NETFILTER_NETLINK
 326         default m if NETFILTER_ADVANCED=n
 327         help
 328           This option enables support for a netlink-based userspace interface
 329
 330 config NF_CT_NETLINK_TIMEOUT
 331         tristate  'Connection tracking timeout tuning via Netlink'
 332         select NETFILTER_NETLINK
 333         depends on NETFILTER_ADVANCED
 334         help
 335           This option enables support for connection tracking timeout
 336           fine-grain tuning. This allows you to attach specific timeout
 337           policies to flows, instead of using the global timeout policy.
 338
 339           If unsure, say `N'.
 340
 341 config NF_CT_NETLINK_HELPER
 342         tristate 'Connection tracking helpers in user-space via Netlink'
 343         select NETFILTER_NETLINK
 344         depends on NF_CT_NETLINK
 345         depends on NETFILTER_NETLINK_QUEUE
 346         depends on NETFILTER_NETLINK_QUEUE_CT
 347         depends on NETFILTER_ADVANCED
 348         help
 349           This option enables the user-space connection tracking helpers
 350           infrastructure.
 351
 352           If unsure, say `N'.
 353
 354 config NETFILTER_NETLINK_QUEUE_CT
 355         bool "NFQUEUE integration with Connection Tracking"
 356         default n
 357         depends on NETFILTER_NETLINK_QUEUE
 358         help
 359           If this option is enabled, NFQUEUE can include Connection Tracking
 360           information together with the packet is the enqueued via NFNETLINK.
 361
 362 config NF_NAT
 363         tristate
 364
 365 config NF_NAT_NEEDED
 366         bool
 367         depends on NF_NAT
 368         default y
 369
 370 config NF_NAT_PROTO_DCCP
 371         tristate
 372         depends on NF_NAT && NF_CT_PROTO_DCCP
 373         default NF_NAT && NF_CT_PROTO_DCCP
 374
 375 config NF_NAT_PROTO_UDPLITE
 376         tristate
 377         depends on NF_NAT && NF_CT_PROTO_UDPLITE
 378         default NF_NAT && NF_CT_PROTO_UDPLITE
 379
 380 config NF_NAT_PROTO_SCTP
 381         tristate
 382         default NF_NAT && NF_CT_PROTO_SCTP
 383         depends on NF_NAT && NF_CT_PROTO_SCTP
 384         select LIBCRC32C
 385
 386 config NF_NAT_AMANDA
 387         tristate
 388         depends on NF_CONNTRACK && NF_NAT
 389         default NF_NAT && NF_CONNTRACK_AMANDA
 390
 391 config NF_NAT_FTP
 392         tristate
 393         depends on NF_CONNTRACK && NF_NAT
 394         default NF_NAT && NF_CONNTRACK_FTP
 395
 396 config NF_NAT_IRC
 397         tristate
 398         depends on NF_CONNTRACK && NF_NAT
 399         default NF_NAT && NF_CONNTRACK_IRC
 400
 401 config NF_NAT_SIP
 402         tristate
 403         depends on NF_CONNTRACK && NF_NAT
 404         default NF_NAT && NF_CONNTRACK_SIP
 405
 406 config NF_NAT_TFTP
 407         tristate
 408         depends on NF_CONNTRACK && NF_NAT
 409         default NF_NAT && NF_CONNTRACK_TFTP
 410
 411 config NETFILTER_SYNPROXY
 412         tristate
 413
 414 endif # NF_CONNTRACK
 415
 416 config NETFILTER_XTABLES
 417         tristate "Netfilter Xtables support (required for ip_tables)"
 418         default m if NETFILTER_ADVANCED=n
 419         help
 420           This is required if you intend to use any of ip_tables,
 421           ip6_tables or arp_tables.
 422
 423 if NETFILTER_XTABLES
 424
 425 comment "Xtables combined modules"
 426
 427 config NETFILTER_XT_MARK
 428         tristate 'nfmark target and match support'
 429         default m if NETFILTER_ADVANCED=n
 430         ---help---
 431         This option adds the "MARK" target and "mark" match.
 432
 433         Netfilter mark matching allows you to match packets based on the
 434         "nfmark" value in the packet.
 435         The target allows you to create rules in the "mangle" table which alter
 436         the netfilter mark (nfmark) field associated with the packet.
 437
 438         Prior to routing, the nfmark can influence the routing method (see
 439         "Use netfilter MARK value as routing key") and can also be used by
 440         other subsystems to change their behavior.
 441
 442 config NETFILTER_XT_CONNMARK
 443         tristate 'ctmark target and match support'
 444         depends on NF_CONNTRACK
 445         depends on NETFILTER_ADVANCED
 446         select NF_CONNTRACK_MARK
 447         ---help---
 448         This option adds the "CONNMARK" target and "connmark" match.
 449
 450         Netfilter allows you to store a mark value per connection (a.k.a.
 451         ctmark), similarly to the packet mark (nfmark). Using this
 452         target and match, you can set and match on this mark.
 453
 454 config NETFILTER_XT_SET
 455         tristate 'set target and match support'
 456         depends on IP_SET
 457         depends on NETFILTER_ADVANCED
 458         help
 459           This option adds the "SET" target and "set" match.
 460
 461           Using this target and match, you can add/delete and match
 462           elements in the sets created by ipset(8).
 463
 464           To compile it as a module, choose M here.  If unsure, say N.
 465
 466 # alphabetically ordered list of targets
 467
 468 comment "Xtables targets"
 469
 470 config NETFILTER_XT_TARGET_AUDIT
 471         tristate "AUDIT target support"
 472         depends on AUDIT
 473         depends on NETFILTER_ADVANCED
 474         ---help---
 475           This option adds a 'AUDIT' target, which can be used to create
 476           audit records for packets dropped/accepted.
 477
 478           To compileit as a module, choose M here. If unsure, say N.
 479
 480 config NETFILTER_XT_TARGET_CHECKSUM
 481         tristate "CHECKSUM target support"
 482         depends on IP_NF_MANGLE || IP6_NF_MANGLE
 483         depends on NETFILTER_ADVANCED
 484         ---help---
 485           This option adds a `CHECKSUM' target, which can be used in the iptables mangle
 486           table.
 487
 488           You can use this target to compute and fill in the checksum in
 489           a packet that lacks a checksum.  This is particularly useful,
 490           if you need to work around old applications such as dhcp clients,
 491           that do not work well with checksum offloads, but don't want to disable
 492           checksum offload in your device.
 493
 494           To compile it as a module, choose M here.  If unsure, say N.
 495
 496 config NETFILTER_XT_TARGET_CLASSIFY
 497         tristate '"CLASSIFY" target support'
 498         depends on NETFILTER_ADVANCED
 499         help
 500           This option adds a `CLASSIFY' target, which enables the user to set
 501           the priority of a packet. Some qdiscs can use this value for
 502           classification, among these are:
 503
 504           atm, cbq, dsmark, pfifo_fast, htb, prio
 505
 506           To compile it as a module, choose M here.  If unsure, say N.
 507
 508 config NETFILTER_XT_TARGET_CONNMARK
 509         tristate  '"CONNMARK" target support'
 510         depends on NF_CONNTRACK
 511         depends on NETFILTER_ADVANCED
 512         select NETFILTER_XT_CONNMARK
 513         ---help---
 514         This is a backwards-compat option for the user's convenience
 515         (e.g. when running oldconfig). It selects
 516         CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
 517
 518 config NETFILTER_XT_TARGET_CONNSECMARK
 519         tristate '"CONNSECMARK" target support'
 520         depends on NF_CONNTRACK && NF_CONNTRACK_SECMARK
 521         default m if NETFILTER_ADVANCED=n
 522         help
 523           The CONNSECMARK target copies security markings from packets
 524           to connections, and restores security markings from connections
 525           to packets (if the packets are not already marked).  This would
 526           normally be used in conjunction with the SECMARK target.
 527
 528           To compile it as a module, choose M here.  If unsure, say N.
 529
 530 config NETFILTER_XT_TARGET_CT
 531         tristate '"CT" target support'
 532         depends on NF_CONNTRACK
 533         depends on IP_NF_RAW || IP6_NF_RAW
 534         depends on NETFILTER_ADVANCED
 535         help
 536           This options adds a `CT' target, which allows to specify initial
 537           connection tracking parameters like events to be delivered and
 538           the helper to be used.
 539
 540           To compile it as a module, choose M here.  If unsure, say N.
 541
 542 config NETFILTER_XT_TARGET_DSCP
 543         tristate '"DSCP" and "TOS" target support'
 544         depends on IP_NF_MANGLE || IP6_NF_MANGLE
 545         depends on NETFILTER_ADVANCED
 546         help
 547           This option adds a `DSCP' target, which allows you to manipulate
 548           the IPv4/IPv6 header DSCP field (differentiated services codepoint).
 549
 550           The DSCP field can have any value between 0x0 and 0x3f inclusive.
 551
 552           It also adds the "TOS" target, which allows you to create rules in
 553           the "mangle" table which alter the Type Of Service field of an IPv4
 554           or the Priority field of an IPv6 packet, prior to routing.
 555
 556           To compile it as a module, choose M here.  If unsure, say N.
 557
 558 config NETFILTER_XT_TARGET_HL
 559         tristate '"HL" hoplimit target support'
 560         depends on IP_NF_MANGLE || IP6_NF_MANGLE
 561         depends on NETFILTER_ADVANCED
 562         ---help---
 563         This option adds the "HL" (for IPv6) and "TTL" (for IPv4)
 564         targets, which enable the user to change the
 565         hoplimit/time-to-live value of the IP header.
 566
 567         While it is safe to decrement the hoplimit/TTL value, the
 568         modules also allow to increment and set the hoplimit value of
 569         the header to arbitrary values. This is EXTREMELY DANGEROUS
 570         since you can easily create immortal packets that loop
 571         forever on the network.
 572
 573 config NETFILTER_XT_TARGET_HMARK
 574         tristate '"HMARK" target support'
 575         depends on (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
 576         depends on NETFILTER_ADVANCED
 577         ---help---
 578         This option adds the "HMARK" target.
 579
 580         The target allows you to create rules in the "raw" and "mangle" tables
 581         which set the skbuff mark by means of hash calculation within a given
 582         range. The nfmark can influence the routing method (see "Use netfilter
 583         MARK value as routing key") and can also be used by other subsystems to
 584         change their behaviour.
 585
 586         To compile it as a module, choose M here. If unsure, say N.
 587
 588 config NETFILTER_XT_TARGET_IDLETIMER
 589         tristate  "IDLETIMER target support"
 590         depends on NETFILTER_ADVANCED
 591         help
 592
 593           This option adds the `IDLETIMER' target.  Each matching packet
 594           resets the timer associated with label specified when the rule is
 595           added.  When the timer expires, it triggers a sysfs notification.
 596           The remaining time for expiration can be read via sysfs.
 597
 598           To compile it as a module, choose M here.  If unsure, say N.
 599
 600 config NETFILTER_XT_TARGET_LED
 601         tristate '"LED" target support'
 602         depends on LEDS_CLASS && LEDS_TRIGGERS
 603         depends on NETFILTER_ADVANCED
 604         help
 605           This option adds a `LED' target, which allows you to blink LEDs in
 606           response to particular packets passing through your machine.
 607
 608           This can be used to turn a spare LED into a network activity LED,
 609           which only flashes in response to FTP transfers, for example.  Or
 610           you could have an LED which lights up for a minute or two every time
 611           somebody connects to your machine via SSH.
 612
 613           You will need support for the "led" class to make this work.
 614
 615           To create an LED trigger for incoming SSH traffic:
 616             iptables -A INPUT -p tcp --dport 22 -j LED --led-trigger-id ssh --led-delay 1000
 617
 618           Then attach the new trigger to an LED on your system:
 619             echo netfilter-ssh > /sys/class/leds/<ledname>/trigger
 620
 621           For more information on the LEDs available on your system, see
 622           Documentation/leds/leds-class.txt
 623
 624 config NETFILTER_XT_TARGET_LOG
 625         tristate "LOG target support"
 626         default m if NETFILTER_ADVANCED=n
 627         help
 628           This option adds a `LOG' target, which allows you to create rules in
 629           any iptables table which records the packet header to the syslog.
 630
 631           To compile it as a module, choose M here.  If unsure, say N.
 632
 633 config NETFILTER_XT_TARGET_MARK
 634         tristate '"MARK" target support'
 635         depends on NETFILTER_ADVANCED
 636         select NETFILTER_XT_MARK
 637         ---help---
 638         This is a backwards-compat option for the user's convenience
 639         (e.g. when running oldconfig). It selects
 640         CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
 641
 642 config NETFILTER_XT_TARGET_NETMAP
 643         tristate '"NETMAP" target support'
 644         depends on NF_NAT
 645         ---help---
 646         NETMAP is an implementation of static 1:1 NAT mapping of network
 647         addresses. It maps the network address part, while keeping the host
 648         address part intact.
 649
 650         To compile it as a module, choose M here. If unsure, say N.
 651
 652 config NETFILTER_XT_TARGET_NFLOG
 653         tristate '"NFLOG" target support'
 654         default m if NETFILTER_ADVANCED=n
 655         select NETFILTER_NETLINK_LOG
 656         help
 657           This option enables the NFLOG target, which allows to LOG
 658           messages through nfnetlink_log.
 659
 660           To compile it as a module, choose M here.  If unsure, say N.
 661
 662 config NETFILTER_XT_TARGET_NFQUEUE
 663         tristate '"NFQUEUE" target Support'
 664         depends on NETFILTER_ADVANCED
 665         select NETFILTER_NETLINK_QUEUE
 666         help
 667           This target replaced the old obsolete QUEUE target.
 668
 669           As opposed to QUEUE, it supports 65535 different queues,
 670           not just one.
 671
 672           To compile it as a module, choose M here.  If unsure, say N.
 673
 674 config NETFILTER_XT_TARGET_NOTRACK
 675         tristate  '"NOTRACK" target support (DEPRECATED)'
 676         depends on NF_CONNTRACK
 677         depends on IP_NF_RAW || IP6_NF_RAW
 678         depends on NETFILTER_ADVANCED
 679         select NETFILTER_XT_TARGET_CT
 680
 681 config NETFILTER_XT_TARGET_RATEEST
 682         tristate '"RATEEST" target support'
 683         depends on NETFILTER_ADVANCED
 684         help
 685           This option adds a `RATEEST' target, which allows to measure
 686           rates similar to TC estimators. The `rateest' match can be
 687           used to match on the measured rates.
 688
 689           To compile it as a module, choose M here.  If unsure, say N.
 690
 691 config NETFILTER_XT_TARGET_REDIRECT
 692         tristate "REDIRECT target support"
 693         depends on NF_NAT
 694         ---help---
 695         REDIRECT is a special case of NAT: all incoming connections are
 696         mapped onto the incoming interface's address, causing the packets to
 697         come to the local machine instead of passing through. This is
 698         useful for transparent proxies.
 699
 700         To compile it as a module, choose M here. If unsure, say N.
 701
 702 config NETFILTER_XT_TARGET_TEE
 703         tristate '"TEE" - packet cloning to alternate destination'
 704         depends on NETFILTER_ADVANCED
 705         depends on (IPV6 || IPV6=n)
 706         depends on !NF_CONNTRACK || NF_CONNTRACK
 707         ---help---
 708         This option adds a "TEE" target with which a packet can be cloned and
 709         this clone be rerouted to another nexthop.
 710
 711 config NETFILTER_XT_TARGET_TPROXY
 712         tristate '"TPROXY" target transparent proxying support'
 713         depends on NETFILTER_XTABLES
 714         depends on NETFILTER_ADVANCED
 715         depends on IP_NF_MANGLE
 716         select NF_DEFRAG_IPV4
 717         select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES
 718         help
 719           This option adds a `TPROXY' target, which is somewhat similar to
 720           REDIRECT.  It can only be used in the mangle table and is useful
 721           to redirect traffic to a transparent proxy.  It does _not_ depend
 722           on Netfilter connection tracking and NAT, unlike REDIRECT.
 723           For it to work you will have to configure certain iptables rules
 724           and use policy routing. For more information on how to set it up
 725           see Documentation/networking/tproxy.txt.
 726
 727           To compile it as a module, choose M here.  If unsure, say N.
 728
 729 config NETFILTER_XT_TARGET_TRACE
 730         tristate  '"TRACE" target support'
 731         depends on IP_NF_RAW || IP6_NF_RAW
 732         depends on NETFILTER_ADVANCED
 733         help
 734           The TRACE target allows you to mark packets so that the kernel
 735           will log every rule which match the packets as those traverse
 736           the tables, chains, rules.
 737
 738           If you want to compile it as a module, say M here and read
 739           <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
 740
 741 config NETFILTER_XT_TARGET_SECMARK
 742         tristate '"SECMARK" target support'
 743         depends on NETWORK_SECMARK
 744         default m if NETFILTER_ADVANCED=n
 745         help
 746           The SECMARK target allows security marking of network
 747           packets, for use with security subsystems.
 748
 749           To compile it as a module, choose M here.  If unsure, say N.
 750
 751 config NETFILTER_XT_TARGET_TCPMSS
 752         tristate '"TCPMSS" target support'
 753         depends on (IPV6 || IPV6=n)
 754         default m if NETFILTER_ADVANCED=n
 755         ---help---
 756           This option adds a `TCPMSS' target, which allows you to alter the
 757           MSS value of TCP SYN packets, to control the maximum size for that
 758           connection (usually limiting it to your outgoing interface's MTU
 759           minus 40).
 760
 761           This is used to overcome criminally braindead ISPs or servers which
 762           block ICMP Fragmentation Needed packets.  The symptoms of this
 763           problem are that everything works fine from your Linux
 764           firewall/router, but machines behind it can never exchange large
 765           packets:
 766                 1) Web browsers connect, then hang with no data received.
 767                 2) Small mail works fine, but large emails hang.
 768                 3) ssh works fine, but scp hangs after initial handshaking.
 769
 770           Workaround: activate this option and add a rule to your firewall
 771           configuration like:
 772
 773           iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
 774                          -j TCPMSS --clamp-mss-to-pmtu
 775
 776           To compile it as a module, choose M here.  If unsure, say N.
 777
 778 config NETFILTER_XT_TARGET_TCPOPTSTRIP
 779         tristate '"TCPOPTSTRIP" target support'
 780         depends on IP_NF_MANGLE || IP6_NF_MANGLE
 781         depends on NETFILTER_ADVANCED
 782         help
 783           This option adds a "TCPOPTSTRIP" target, which allows you to strip
 784           TCP options from TCP packets.
 785
 786 # alphabetically ordered list of matches
 787
 788 comment "Xtables matches"
 789
 790 config NETFILTER_XT_MATCH_ADDRTYPE
 791         tristate '"addrtype" address type match support'
 792         depends on NETFILTER_ADVANCED
 793         ---help---
 794           This option allows you to match what routing thinks of an address,
 795           eg. UNICAST, LOCAL, BROADCAST, ...
 796
 797           If you want to compile it as a module, say M here and read
 798           <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
 799
 800 config NETFILTER_XT_MATCH_BPF
 801         tristate '"bpf" match support'
 802         depends on NETFILTER_ADVANCED
 803         help
 804           BPF matching applies a linux socket filter to each packet and
 805           accepts those for which the filter returns non-zero.
 806
 807           To compile it as a module, choose M here.  If unsure, say N.
 808
 809 config NETFILTER_XT_MATCH_CLUSTER
 810         tristate '"cluster" match support'
 811         depends on NF_CONNTRACK
 812         depends on NETFILTER_ADVANCED
 813         ---help---
 814           This option allows you to build work-load-sharing clusters of
 815           network servers/stateful firewalls without having a dedicated
 816           load-balancing router/server/switch. Basically, this match returns
 817           true when the packet must be handled by this cluster node. Thus,
 818           all nodes see all packets and this match decides which node handles
 819           what packets. The work-load sharing algorithm is based on source
 820           address hashing.
 821
 822           If you say Y or M here, try `iptables -m cluster --help` for
 823           more information.
 824
 825 config NETFILTER_XT_MATCH_COMMENT
 826         tristate  '"comment" match support'
 827         depends on NETFILTER_ADVANCED
 828         help
 829           This option adds a `comment' dummy-match, which allows you to put
 830           comments in your iptables ruleset.
 831
 832           If you want to compile it as a module, say M here and read
 833           <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
 834
 835 config NETFILTER_XT_MATCH_CONNBYTES
 836         tristate  '"connbytes" per-connection counter match support'
 837         depends on NF_CONNTRACK
 838         depends on NETFILTER_ADVANCED
 839         help
 840           This option adds a `connbytes' match, which allows you to match the
 841           number of bytes and/or packets for each direction within a connection.
 842
 843           If you want to compile it as a module, say M here and read
 844           <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
 845
 846 config NETFILTER_XT_MATCH_CONNLABEL
 847         tristate '"connlabel" match support'
 848         select NF_CONNTRACK_LABELS
 849         depends on NF_CONNTRACK
 850         depends on NETFILTER_ADVANCED
 851         ---help---
 852           This match allows you to test and assign userspace-defined labels names
 853           to a connection.  The kernel only stores bit values - mapping
 854           names to bits is done by userspace.
 855
 856           Unlike connmark, more than 32 flag bits may be assigned to a
 857           connection simultaneously.
 858
 859 config NETFILTER_XT_MATCH_CONNLIMIT
 860         tristate '"connlimit" match support"'
 861         depends on NF_CONNTRACK
 862         depends on NETFILTER_ADVANCED
 863         ---help---
 864           This match allows you to match against the number of parallel
 865           connections to a server per client IP address (or address block).
 866
 867 config NETFILTER_XT_MATCH_CONNMARK
 868         tristate  '"connmark" connection mark match support'
 869         depends on NF_CONNTRACK
 870         depends on NETFILTER_ADVANCED
 871         select NETFILTER_XT_CONNMARK
 872         ---help---
 873         This is a backwards-compat option for the user's convenience
 874         (e.g. when running oldconfig). It selects
 875         CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
 876
 877 config NETFILTER_XT_MATCH_CONNTRACK
 878         tristate '"conntrack" connection tracking match support'
 879         depends on NF_CONNTRACK
 880         default m if NETFILTER_ADVANCED=n
 881         help
 882           This is a general conntrack match module, a superset of the state match.
 883
 884           It allows matching on additional conntrack information, which is
 885           useful in complex configurations, such as NAT gateways with multiple
 886           internet links or tunnels.
 887
 888           To compile it as a module, choose M here.  If unsure, say N.
 889
 890 config NETFILTER_XT_MATCH_CPU
 891         tristate '"cpu" match support'
 892         depends on NETFILTER_ADVANCED
 893         help
 894           CPU matching allows you to match packets based on the CPU
 895           currently handling the packet.
 896
 897           To compile it as a module, choose M here.  If unsure, say N.
 898
 899 config NETFILTER_XT_MATCH_DCCP
 900         tristate '"dccp" protocol match support'
 901         depends on NETFILTER_ADVANCED
 902         default IP_DCCP
 903         help
 904           With this option enabled, you will be able to use the iptables
 905           `dccp' match in order to match on DCCP source/destination ports
 906           and DCCP flags.
 907
 908           If you want to compile it as a module, say M here and read
 909           <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
 910
 911 config NETFILTER_XT_MATCH_DEVGROUP
 912         tristate '"devgroup" match support'
 913         depends on NETFILTER_ADVANCED
 914         help
 915           This options adds a `devgroup' match, which allows to match on the
 916           device group a network device is assigned to.
 917
 918           To compile it as a module, choose M here.  If unsure, say N.
 919
 920 config NETFILTER_XT_MATCH_DSCP
 921         tristate '"dscp" and "tos" match support'
 922         depends on NETFILTER_ADVANCED
 923         help
 924           This option adds a `DSCP' match, which allows you to match against
 925           the IPv4/IPv6 header DSCP field (differentiated services codepoint).
 926
 927           The DSCP field can have any value between 0x0 and 0x3f inclusive.
 928
 929           It will also add a "tos" match, which allows you to match packets
 930           based on the Type Of Service fields of the IPv4 packet (which share
 931           the same bits as DSCP).
 932
 933           To compile it as a module, choose M here.  If unsure, say N.
 934
 935 config NETFILTER_XT_MATCH_ECN
 936         tristate '"ecn" match support'
 937         depends on NETFILTER_ADVANCED
 938         ---help---
 939         This option adds an "ECN" match, which allows you to match against
 940         the IPv4 and TCP header ECN fields.
 941
 942         To compile it as a module, choose M here. If unsure, say N.
 943
 944 config NETFILTER_XT_MATCH_ESP
 945         tristate '"esp" match support'
 946         depends on NETFILTER_ADVANCED
 947         help
 948           This match extension allows you to match a range of SPIs
 949           inside ESP header of IPSec packets.
 950
 951           To compile it as a module, choose M here.  If unsure, say N.
 952
 953 config NETFILTER_XT_MATCH_HASHLIMIT
 954         tristate '"hashlimit" match support'
 955         depends on (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
 956         depends on NETFILTER_ADVANCED
 957         help
 958           This option adds a `hashlimit' match.
 959
 960           As opposed to `limit', this match dynamically creates a hash table
 961           of limit buckets, based on your selection of source/destination
 962           addresses and/or ports.
 963
 964           It enables you to express policies like `10kpps for any given
 965           destination address' or `500pps from any given source address'
 966           with a single rule.
 967
 968 config NETFILTER_XT_MATCH_HELPER
 969         tristate '"helper" match support'
 970         depends on NF_CONNTRACK
 971         depends on NETFILTER_ADVANCED
 972         help
 973           Helper matching allows you to match packets in dynamic connections
 974           tracked by a conntrack-helper, ie. ip_conntrack_ftp
 975
 976           To compile it as a module, choose M here.  If unsure, say Y.
 977
 978 config NETFILTER_XT_MATCH_HL
 979         tristate '"hl" hoplimit/TTL match support'
 980         depends on NETFILTER_ADVANCED
 981         ---help---
 982         HL matching allows you to match packets based on the hoplimit
 983         in the IPv6 header, or the time-to-live field in the IPv4
 984         header of the packet.
 985
 986 config NETFILTER_XT_MATCH_IPRANGE
 987         tristate '"iprange" address range match support'
 988         depends on NETFILTER_ADVANCED
 989         ---help---
 990         This option adds a "iprange" match, which allows you to match based on
 991         an IP address range. (Normal iptables only matches on single addresses
 992         with an optional mask.)
 993
 994         If unsure, say M.
 995
 996 config NETFILTER_XT_MATCH_IPVS
 997         tristate '"ipvs" match support'
 998         depends on IP_VS
 999         depends on NETFILTER_ADVANCED
1000         depends on NF_CONNTRACK
1001         help
1002           This option allows you to match against IPVS properties of a packet.
1003
1004           If unsure, say N.
1005
1006 config NETFILTER_XT_MATCH_LENGTH
1007         tristate '"length" match support'
1008         depends on NETFILTER_ADVANCED
1009         help
1010           This option allows you to match the length of a packet against a
1011           specific value or range of values.
1012
1013           To compile it as a module, choose M here.  If unsure, say N.
1014
1015 config NETFILTER_XT_MATCH_LIMIT
1016         tristate '"limit" match support'
1017         depends on NETFILTER_ADVANCED
1018         help
1019           limit matching allows you to control the rate at which a rule can be
1020           matched: mainly useful in combination with the LOG target ("LOG
1021           target support", below) and to avoid some Denial of Service attacks.
1022
1023           To compile it as a module, choose M here.  If unsure, say N.
1024
1025 config NETFILTER_XT_MATCH_MAC
1026         tristate '"mac" address match support'
1027         depends on NETFILTER_ADVANCED
1028         help
1029           MAC matching allows you to match packets based on the source
1030           Ethernet address of the packet.
1031
1032           To compile it as a module, choose M here.  If unsure, say N.
1033
1034 config NETFILTER_XT_MATCH_MARK
1035         tristate '"mark" match support'
1036         depends on NETFILTER_ADVANCED
1037         select NETFILTER_XT_MARK
1038         ---help---
1039         This is a backwards-compat option for the user's convenience
1040         (e.g. when running oldconfig). It selects
1041         CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
1042
1043 config NETFILTER_XT_MATCH_MULTIPORT
1044         tristate '"multiport" Multiple port match support'
1045         depends on NETFILTER_ADVANCED
1046         help
1047           Multiport matching allows you to match TCP or UDP packets based on
1048           a series of source or destination ports: normally a rule can only
1049           match a single range of ports.
1050
1051           To compile it as a module, choose M here.  If unsure, say N.
1052
1053 config NETFILTER_XT_MATCH_NFACCT
1054         tristate '"nfacct" match support'
1055         depends on NETFILTER_ADVANCED
1056         select NETFILTER_NETLINK_ACCT
1057         help
1058           This option allows you to use the extended accounting through
1059           nfnetlink_acct.
1060
1061           To compile it as a module, choose M here.  If unsure, say N.
1062
1063 config NETFILTER_XT_MATCH_OSF
1064         tristate '"osf" Passive OS fingerprint match'
1065         depends on NETFILTER_ADVANCED && NETFILTER_NETLINK
1066         help
1067           This option selects the Passive OS Fingerprinting match module
1068           that allows to passively match the remote operating system by
1069           analyzing incoming TCP SYN packets.
1070
1071           Rules and loading software can be downloaded from
1072           http://www.ioremap.net/projects/osf
1073
1074           To compile it as a module, choose M here.  If unsure, say N.
1075
1076 config NETFILTER_XT_MATCH_OWNER
1077         tristate '"owner" match support'
1078         depends on NETFILTER_ADVANCED
1079         ---help---
1080         Socket owner matching allows you to match locally-generated packets
1081         based on who created the socket: the user or group. It is also
1082         possible to check whether a socket actually exists.
1083
1084 config NETFILTER_XT_MATCH_POLICY
1085         tristate 'IPsec "policy" match support'
1086         depends on XFRM
1087         default m if NETFILTER_ADVANCED=n
1088         help
1089           Policy matching allows you to match packets based on the
1090           IPsec policy that was used during decapsulation/will
1091           be used during encapsulation.
1092
1093           To compile it as a module, choose M here.  If unsure, say N.
1094
1095 config NETFILTER_XT_MATCH_PHYSDEV
1096         tristate '"physdev" match support'
1097         depends on BRIDGE && BRIDGE_NETFILTER
1098         depends on NETFILTER_ADVANCED
1099         help
1100           Physdev packet matching matches against the physical bridge ports
1101           the IP packet arrived on or will leave by.
1102
1103           To compile it as a module, choose M here.  If unsure, say N.
1104
1105 config NETFILTER_XT_MATCH_PKTTYPE
1106         tristate '"pkttype" packet type match support'
1107         depends on NETFILTER_ADVANCED
1108         help
1109           Packet type matching allows you to match a packet by
1110           its "class", eg. BROADCAST, MULTICAST, ...
1111
1112           Typical usage:
1113           iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG
1114
1115           To compile it as a module, choose M here.  If unsure, say N.
1116
1117 config NETFILTER_XT_MATCH_QUOTA
1118         tristate '"quota" match support'
1119         depends on NETFILTER_ADVANCED
1120         help
1121           This option adds a `quota' match, which allows to match on a
1122           byte counter.
1123
1124           If you want to compile it as a module, say M here and read
1125           <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
1126
1127 config NETFILTER_XT_MATCH_RATEEST
1128         tristate '"rateest" match support'
1129         depends on NETFILTER_ADVANCED
1130         select NETFILTER_XT_TARGET_RATEEST
1131         help
1132           This option adds a `rateest' match, which allows to match on the
1133           rate estimated by the RATEEST target.
1134
1135           To compile it as a module, choose M here.  If unsure, say N.
1136
1137 config NETFILTER_XT_MATCH_REALM
1138         tristate  '"realm" match support'
1139         depends on NETFILTER_ADVANCED
1140         select IP_ROUTE_CLASSID
1141         help
1142           This option adds a `realm' match, which allows you to use the realm
1143           key from the routing subsystem inside iptables.
1144
1145           This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option
1146           in tc world.
1147
1148           If you want to compile it as a module, say M here and read
1149           <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
1150
1151 config NETFILTER_XT_MATCH_RECENT
1152         tristate '"recent" match support'
1153         depends on NETFILTER_ADVANCED
1154         ---help---
1155         This match is used for creating one or many lists of recently
1156         used addresses and then matching against that/those list(s).
1157
1158         Short options are available by using 'iptables -m recent -h'
1159         Official Website: <http://snowman.net/projects/ipt_recent/>
1160
1161 config NETFILTER_XT_MATCH_SCTP
1162         tristate  '"sctp" protocol match support'
1163         depends on NETFILTER_ADVANCED
1164         default IP_SCTP
1165         help
1166           With this option enabled, you will be able to use the
1167           `sctp' match in order to match on SCTP source/destination ports
1168           and SCTP chunk types.
1169
1170           If you want to compile it as a module, say M here and read
1171           <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
1172
1173 config NETFILTER_XT_MATCH_SOCKET
1174         tristate '"socket" match support'
1175         depends on NETFILTER_XTABLES
1176         depends on NETFILTER_ADVANCED
1177         depends on !NF_CONNTRACK || NF_CONNTRACK
1178         depends on (IPV6 || IPV6=n)
1179         select NF_DEFRAG_IPV4
1180         select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES
1181         help
1182           This option adds a `socket' match, which can be used to match
1183           packets for which a TCP or UDP socket lookup finds a valid socket.
1184           It can be used in combination with the MARK target and policy
1185           routing to implement full featured non-locally bound sockets.
1186
1187           To compile it as a module, choose M here.  If unsure, say N.
1188
1189 config NETFILTER_XT_MATCH_STATE
1190         tristate '"state" match support'
1191         depends on NF_CONNTRACK
1192         default m if NETFILTER_ADVANCED=n
1193         help
1194           Connection state matching allows you to match packets based on their
1195           relationship to a tracked connection (ie. previous packets).  This
1196           is a powerful tool for packet classification.
1197
1198           To compile it as a module, choose M here.  If unsure, say N.
1199
1200 config NETFILTER_XT_MATCH_STATISTIC
1201         tristate '"statistic" match support'
1202         depends on NETFILTER_ADVANCED
1203         help
1204           This option adds a `statistic' match, which allows you to match
1205           on packets periodically or randomly with a given percentage.
1206
1207           To compile it as a module, choose M here.  If unsure, say N.
1208
1209 config NETFILTER_XT_MATCH_STRING
1210         tristate  '"string" match support'
1211         depends on NETFILTER_ADVANCED
1212         select TEXTSEARCH
1213         select TEXTSEARCH_KMP
1214         select TEXTSEARCH_BM
1215         select TEXTSEARCH_FSM
1216         help
1217           This option adds a `string' match, which allows you to look for
1218           pattern matchings in packets.
1219
1220           To compile it as a module, choose M here.  If unsure, say N.
1221
1222 config NETFILTER_XT_MATCH_TCPMSS
1223         tristate '"tcpmss" match support'
1224         depends on NETFILTER_ADVANCED
1225         help
1226           This option adds a `tcpmss' match, which allows you to examine the
1227           MSS value of TCP SYN packets, which control the maximum packet size
1228           for that connection.
1229
1230           To compile it as a module, choose M here.  If unsure, say N.
1231
1232 config NETFILTER_XT_MATCH_TIME
1233         tristate '"time" match support'
1234         depends on NETFILTER_ADVANCED
1235         ---help---
1236           This option adds a "time" match, which allows you to match based on
1237           the packet arrival time (at the machine which netfilter is running)
1238           on) or departure time/date (for locally generated packets).
1239
1240           If you say Y here, try `iptables -m time --help` for
1241           more information.
1242
1243           If you want to compile it as a module, say M here.
1244           If unsure, say N.
1245
1246 config NETFILTER_XT_MATCH_U32
1247         tristate '"u32" match support'
1248         depends on NETFILTER_ADVANCED
1249         ---help---
1250           u32 allows you to extract quantities of up to 4 bytes from a packet,
1251           AND them with specified masks, shift them by specified amounts and
1252           test whether the results are in any of a set of specified ranges.
1253           The specification of what to extract is general enough to skip over
1254           headers with lengths stored in the packet, as in IP or TCP header
1255           lengths.
1256
1257           Details and examples are in the kernel module source.
1258
1259 endif # NETFILTER_XTABLES
1260
1261 endmenu
1262
1263 source "net/netfilter/ipset/Kconfig"
1264
1265 source "net/netfilter/ipvs/Kconfig"