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_QUEUE
   8         tristate "Netfilter NFQUEUE 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 queueing packets via NFNETLINK.
  14
  15 config NETFILTER_NETLINK_LOG
  16         tristate "Netfilter LOG over NFNETLINK interface"
  17         default m if NETFILTER_ADVANCED=n
  18         select NETFILTER_NETLINK
  19         help
  20           If this option is enabled, the kernel will include support
  21           for logging packets via NFNETLINK.
  22
  23           This obsoletes the existing ipt_ULOG and ebg_ulog mechanisms,
  24           and is also scheduled to replace the old syslog-based ipt_LOG
  25           and ip6t_LOG modules.
  26
  27 config NF_CONNTRACK
  28         tristate "Netfilter connection tracking support"
  29         default m if NETFILTER_ADVANCED=n
  30         help
  31           Connection tracking keeps a record of what packets have passed
  32           through your machine, in order to figure out how they are related
  33           into connections.
  34
  35           This is required to do Masquerading or other kinds of Network
  36           Address Translation.  It can also be used to enhance packet
  37           filtering (see `Connection state match support' below).
  38
  39           To compile it as a module, choose M here.  If unsure, say N.
  40
  41 if NF_CONNTRACK
  42
  43 config NF_CT_ACCT
  44         bool "Connection tracking flow accounting"
  45         depends on NETFILTER_ADVANCED
  46         help
  47           If this option is enabled, the connection tracking code will
  48           keep per-flow packet and byte counters.
  49
  50           Those counters can be used for flow-based accounting or the
  51           `connbytes' match.
  52
  53           Please note that currently this option only sets a default state.
  54           You may change it at boot time with nf_conntrack.acct=0/1 kernel
  55           paramater or by loading the nf_conntrack module with acct=0/1.
  56
  57           You may also disable/enable it on a running system with:
  58            sysctl net.netfilter.nf_conntrack_acct=0/1
  59
  60           This option will be removed in 2.6.29.
  61
  62           If unsure, say `N'.
  63
  64 config NF_CONNTRACK_MARK
  65         bool  'Connection mark tracking support'
  66         depends on NETFILTER_ADVANCED
  67         help
  68           This option enables support for connection marks, used by the
  69           `CONNMARK' target and `connmark' match. Similar to the mark value
  70           of packets, but this mark value is kept in the conntrack session
  71           instead of the individual packets.
  72
  73 config NF_CONNTRACK_SECMARK
  74         bool  'Connection tracking security mark support'
  75         depends on NETWORK_SECMARK
  76         default m if NETFILTER_ADVANCED=n
  77         help
  78           This option enables security markings to be applied to
  79           connections.  Typically they are copied to connections from
  80           packets using the CONNSECMARK target and copied back from
  81           connections to packets with the same target, with the packets
  82           being originally labeled via SECMARK.
  83
  84           If unsure, say 'N'.
  85
  86 config NF_CONNTRACK_EVENTS
  87         bool "Connection tracking events"
  88         depends on NETFILTER_ADVANCED
  89         help
  90           If this option is enabled, the connection tracking code will
  91           provide a notifier chain that can be used by other kernel code
  92           to get notified about changes in the connection tracking state.
  93
  94           If unsure, say `N'.
  95
  96 config NF_CT_PROTO_DCCP
  97         tristate 'DCCP protocol connection tracking support (EXPERIMENTAL)'
  98         depends on EXPERIMENTAL
  99         depends on NETFILTER_ADVANCED
 100         default IP_DCCP
 101         help
 102           With this option enabled, the layer 3 independent connection
 103           tracking code will be able to do state tracking on DCCP connections.
 104
 105           If unsure, say 'N'.
 106
 107 config NF_CT_PROTO_GRE
 108         tristate
 109
 110 config NF_CT_PROTO_SCTP
 111         tristate 'SCTP protocol connection tracking support (EXPERIMENTAL)'
 112         depends on EXPERIMENTAL
 113         depends on NETFILTER_ADVANCED
 114         default IP_SCTP
 115         help
 116           With this option enabled, the layer 3 independent connection
 117           tracking code will be able to do state tracking on SCTP connections.
 118
 119           If you want to compile it as a module, say M here and read
 120           <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
 121
 122 config NF_CT_PROTO_UDPLITE
 123         tristate 'UDP-Lite protocol connection tracking support'
 124         depends on NETFILTER_ADVANCED
 125         help
 126           With this option enabled, the layer 3 independent connection
 127           tracking code will be able to do state tracking on UDP-Lite
 128           connections.
 129
 130           To compile it as a module, choose M here.  If unsure, say N.
 131
 132 config NF_CONNTRACK_AMANDA
 133         tristate "Amanda backup protocol support"
 134         depends on NETFILTER_ADVANCED
 135         select TEXTSEARCH
 136         select TEXTSEARCH_KMP
 137         help
 138           If you are running the Amanda backup package <http://www.amanda.org/>
 139           on this machine or machines that will be MASQUERADED through this
 140           machine, then you may want to enable this feature.  This allows the
 141           connection tracking and natting code to allow the sub-channels that
 142           Amanda requires for communication of the backup data, messages and
 143           index.
 144
 145           To compile it as a module, choose M here.  If unsure, say N.
 146
 147 config NF_CONNTRACK_FTP
 148         tristate "FTP protocol support"
 149         default m if NETFILTER_ADVANCED=n
 150         help
 151           Tracking FTP connections is problematic: special helpers are
 152           required for tracking them, and doing masquerading and other forms
 153           of Network Address Translation on them.
 154
 155           This is FTP support on Layer 3 independent connection tracking.
 156           Layer 3 independent connection tracking is experimental scheme
 157           which generalize ip_conntrack to support other layer 3 protocols.
 158
 159           To compile it as a module, choose M here.  If unsure, say N.
 160
 161 config NF_CONNTRACK_H323
 162         tristate "H.323 protocol support"
 163         depends on (IPV6 || IPV6=n)
 164         depends on NETFILTER_ADVANCED
 165         help
 166           H.323 is a VoIP signalling protocol from ITU-T. As one of the most
 167           important VoIP protocols, it is widely used by voice hardware and
 168           software including voice gateways, IP phones, Netmeeting, OpenPhone,
 169           Gnomemeeting, etc.
 170
 171           With this module you can support H.323 on a connection tracking/NAT
 172           firewall.
 173
 174           This module supports RAS, Fast Start, H.245 Tunnelling, Call
 175           Forwarding, RTP/RTCP and T.120 based audio, video, fax, chat,
 176           whiteboard, file transfer, etc. For more information, please
 177           visit http://nath323.sourceforge.net/.
 178
 179           To compile it as a module, choose M here.  If unsure, say N.
 180
 181 config NF_CONNTRACK_IRC
 182         tristate "IRC protocol support"
 183         default m if NETFILTER_ADVANCED=n
 184         help
 185           There is a commonly-used extension to IRC called
 186           Direct Client-to-Client Protocol (DCC).  This enables users to send
 187           files to each other, and also chat to each other without the need
 188           of a server.  DCC Sending is used anywhere you send files over IRC,
 189           and DCC Chat is most commonly used by Eggdrop bots.  If you are
 190           using NAT, this extension will enable you to send files and initiate
 191           chats.  Note that you do NOT need this extension to get files or
 192           have others initiate chats, or everything else in IRC.
 193
 194           To compile it as a module, choose M here.  If unsure, say N.
 195
 196 config NF_CONNTRACK_NETBIOS_NS
 197         tristate "NetBIOS name service protocol support"
 198         depends on NETFILTER_ADVANCED
 199         help
 200           NetBIOS name service requests are sent as broadcast messages from an
 201           unprivileged port and responded to with unicast messages to the
 202           same port. This make them hard to firewall properly because connection
 203           tracking doesn't deal with broadcasts. This helper tracks locally
 204           originating NetBIOS name service requests and the corresponding
 205           responses. It relies on correct IP address configuration, specifically
 206           netmask and broadcast address. When properly configured, the output
 207           of "ip address show" should look similar to this:
 208
 209           $ ip -4 address show eth0
 210           4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
 211               inet 172.16.2.252/24 brd 172.16.2.255 scope global eth0
 212
 213           To compile it as a module, choose M here.  If unsure, say N.
 214
 215 config NF_CONNTRACK_PPTP
 216         tristate "PPtP protocol support"
 217         depends on NETFILTER_ADVANCED
 218         select NF_CT_PROTO_GRE
 219         help
 220           This module adds support for PPTP (Point to Point Tunnelling
 221           Protocol, RFC2637) connection tracking and NAT.
 222
 223           If you are running PPTP sessions over a stateful firewall or NAT
 224           box, you may want to enable this feature.
 225
 226           Please note that not all PPTP modes of operation are supported yet.
 227           Specifically these limitations exist:
 228             - Blindly assumes that control connections are always established
 229               in PNS->PAC direction. This is a violation of RFC2637.
 230             - Only supports a single call within each session
 231
 232           To compile it as a module, choose M here.  If unsure, say N.
 233
 234 config NF_CONNTRACK_SANE
 235         tristate "SANE protocol support (EXPERIMENTAL)"
 236         depends on EXPERIMENTAL
 237         depends on NETFILTER_ADVANCED
 238         help
 239           SANE is a protocol for remote access to scanners as implemented
 240           by the 'saned' daemon. Like FTP, it uses separate control and
 241           data connections.
 242
 243           With this module you can support SANE on a connection tracking
 244           firewall.
 245
 246           To compile it as a module, choose M here.  If unsure, say N.
 247
 248 config NF_CONNTRACK_SIP
 249         tristate "SIP protocol support"
 250         default m if NETFILTER_ADVANCED=n
 251         help
 252           SIP is an application-layer control protocol that can establish,
 253           modify, and terminate multimedia sessions (conferences) such as
 254           Internet telephony calls. With the ip_conntrack_sip and
 255           the nf_nat_sip modules you can support the protocol on a connection
 256           tracking/NATing firewall.
 257
 258           To compile it as a module, choose M here.  If unsure, say N.
 259
 260 config NF_CONNTRACK_TFTP
 261         tristate "TFTP protocol support"
 262         depends on NETFILTER_ADVANCED
 263         help
 264           TFTP connection tracking helper, this is required depending
 265           on how restrictive your ruleset is.
 266           If you are using a tftp client behind -j SNAT or -j MASQUERADING
 267           you will need this.
 268
 269           To compile it as a module, choose M here.  If unsure, say N.
 270
 271 config NF_CT_NETLINK
 272         tristate 'Connection tracking netlink interface'
 273         select NETFILTER_NETLINK
 274         default m if NETFILTER_ADVANCED=n
 275         help
 276           This option enables support for a netlink-based userspace interface
 277
 278 # transparent proxy support
 279 config NETFILTER_TPROXY
 280         tristate "Transparent proxying support (EXPERIMENTAL)"
 281         depends on EXPERIMENTAL
 282         depends on IP_NF_MANGLE
 283         depends on NETFILTER_ADVANCED
 284         help
 285           This option enables transparent proxying support, that is,
 286           support for handling non-locally bound IPv4 TCP and UDP sockets.
 287           For it to work you will have to configure certain iptables rules
 288           and use policy routing. For more information on how to set it up
 289           see Documentation/networking/tproxy.txt.
 290
 291           To compile it as a module, choose M here.  If unsure, say N.
 292
 293 endif # NF_CONNTRACK
 294
 295 config NETFILTER_XTABLES
 296         tristate "Netfilter Xtables support (required for ip_tables)"
 297         default m if NETFILTER_ADVANCED=n
 298         help
 299           This is required if you intend to use any of ip_tables,
 300           ip6_tables or arp_tables.
 301
 302 if NETFILTER_XTABLES
 303
 304 # alphabetically ordered list of targets
 305
 306 config NETFILTER_XT_TARGET_CLASSIFY
 307         tristate '"CLASSIFY" target support'
 308         depends on NETFILTER_ADVANCED
 309         help
 310           This option adds a `CLASSIFY' target, which enables the user to set
 311           the priority of a packet. Some qdiscs can use this value for
 312           classification, among these are:
 313
 314           atm, cbq, dsmark, pfifo_fast, htb, prio
 315
 316           To compile it as a module, choose M here.  If unsure, say N.
 317
 318 config NETFILTER_XT_TARGET_CONNMARK
 319         tristate  '"CONNMARK" target support'
 320         depends on NF_CONNTRACK
 321         depends on NETFILTER_ADVANCED
 322         select NF_CONNTRACK_MARK
 323         help
 324           This option adds a `CONNMARK' target, which allows one to manipulate
 325           the connection mark value.  Similar to the MARK target, but
 326           affects the connection mark value rather than the packet mark value.
 327
 328           If you want to compile it as a module, say M here and read
 329           <file:Documentation/kbuild/modules.txt>.  The module will be called
 330           ipt_CONNMARK.ko.  If unsure, say `N'.
 331
 332 config NETFILTER_XT_TARGET_CONNSECMARK
 333         tristate '"CONNSECMARK" target support'
 334         depends on NF_CONNTRACK && NF_CONNTRACK_SECMARK
 335         default m if NETFILTER_ADVANCED=n
 336         help
 337           The CONNSECMARK target copies security markings from packets
 338           to connections, and restores security markings from connections
 339           to packets (if the packets are not already marked).  This would
 340           normally be used in conjunction with the SECMARK target.
 341
 342           To compile it as a module, choose M here.  If unsure, say N.
 343
 344 config NETFILTER_XT_TARGET_DSCP
 345         tristate '"DSCP" and "TOS" target support'
 346         depends on IP_NF_MANGLE || IP6_NF_MANGLE
 347         depends on NETFILTER_ADVANCED
 348         help
 349           This option adds a `DSCP' target, which allows you to manipulate
 350           the IPv4/IPv6 header DSCP field (differentiated services codepoint).
 351
 352           The DSCP field can have any value between 0x0 and 0x3f inclusive.
 353
 354           It also adds the "TOS" target, which allows you to create rules in
 355           the "mangle" table which alter the Type Of Service field of an IPv4
 356           or the Priority field of an IPv6 packet, prior to routing.
 357
 358           To compile it as a module, choose M here.  If unsure, say N.
 359
 360 config NETFILTER_XT_TARGET_MARK
 361         tristate '"MARK" target support'
 362         default m if NETFILTER_ADVANCED=n
 363         help
 364           This option adds a `MARK' target, which allows you to create rules
 365           in the `mangle' table which alter the netfilter mark (nfmark) field
 366           associated with the packet prior to routing. This can change
 367           the routing method (see `Use netfilter MARK value as routing
 368           key') and can also be used by other subsystems to change their
 369           behavior.
 370
 371           To compile it as a module, choose M here.  If unsure, say N.
 372
 373 config NETFILTER_XT_TARGET_NFLOG
 374         tristate '"NFLOG" target support'
 375         default m if NETFILTER_ADVANCED=n
 376         select NETFILTER_NETLINK_LOG
 377         help
 378           This option enables the NFLOG target, which allows to LOG
 379           messages through nfnetlink_log.
 380
 381           To compile it as a module, choose M here.  If unsure, say N.
 382
 383 config NETFILTER_XT_TARGET_NFQUEUE
 384         tristate '"NFQUEUE" target Support'
 385         depends on NETFILTER_ADVANCED
 386         help
 387           This target replaced the old obsolete QUEUE target.
 388
 389           As opposed to QUEUE, it supports 65535 different queues,
 390           not just one.
 391
 392           To compile it as a module, choose M here.  If unsure, say N.
 393
 394 config NETFILTER_XT_TARGET_NOTRACK
 395         tristate  '"NOTRACK" target support'
 396         depends on IP_NF_RAW || IP6_NF_RAW
 397         depends on NF_CONNTRACK
 398         depends on NETFILTER_ADVANCED
 399         help
 400           The NOTRACK target allows a select rule to specify
 401           which packets *not* to enter the conntrack/NAT
 402           subsystem with all the consequences (no ICMP error tracking,
 403           no protocol helpers for the selected packets).
 404
 405           If you want to compile it as a module, say M here and read
 406           <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
 407
 408 config NETFILTER_XT_TARGET_RATEEST
 409         tristate '"RATEEST" target support'
 410         depends on NETFILTER_ADVANCED
 411         help
 412           This option adds a `RATEEST' target, which allows to measure
 413           rates similar to TC estimators. The `rateest' match can be
 414           used to match on the measured rates.
 415
 416           To compile it as a module, choose M here.  If unsure, say N.
 417
 418 config NETFILTER_XT_TARGET_TPROXY
 419         tristate '"TPROXY" target support (EXPERIMENTAL)'
 420         depends on EXPERIMENTAL
 421         depends on NETFILTER_TPROXY
 422         depends on NETFILTER_XTABLES
 423         depends on NETFILTER_ADVANCED
 424         select NF_DEFRAG_IPV4
 425         help
 426           This option adds a `TPROXY' target, which is somewhat similar to
 427           REDIRECT.  It can only be used in the mangle table and is useful
 428           to redirect traffic to a transparent proxy.  It does _not_ depend
 429           on Netfilter connection tracking and NAT, unlike REDIRECT.
 430
 431           To compile it as a module, choose M here.  If unsure, say N.
 432
 433 config NETFILTER_XT_TARGET_TRACE
 434         tristate  '"TRACE" target support'
 435         depends on IP_NF_RAW || IP6_NF_RAW
 436         depends on NETFILTER_ADVANCED
 437         help
 438           The TRACE target allows you to mark packets so that the kernel
 439           will log every rule which match the packets as those traverse
 440           the tables, chains, rules.
 441
 442           If you want to compile it as a module, say M here and read
 443           <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
 444
 445 config NETFILTER_XT_TARGET_SECMARK
 446         tristate '"SECMARK" target support'
 447         depends on NETWORK_SECMARK
 448         default m if NETFILTER_ADVANCED=n
 449         help
 450           The SECMARK target allows security marking of network
 451           packets, for use with security subsystems.
 452
 453           To compile it as a module, choose M here.  If unsure, say N.
 454
 455 config NETFILTER_XT_TARGET_TCPMSS
 456         tristate '"TCPMSS" target support'
 457         depends on (IPV6 || IPV6=n)
 458         default m if NETFILTER_ADVANCED=n
 459         ---help---
 460           This option adds a `TCPMSS' target, which allows you to alter the
 461           MSS value of TCP SYN packets, to control the maximum size for that
 462           connection (usually limiting it to your outgoing interface's MTU
 463           minus 40).
 464
 465           This is used to overcome criminally braindead ISPs or servers which
 466           block ICMP Fragmentation Needed packets.  The symptoms of this
 467           problem are that everything works fine from your Linux
 468           firewall/router, but machines behind it can never exchange large
 469           packets:
 470                 1) Web browsers connect, then hang with no data received.
 471                 2) Small mail works fine, but large emails hang.
 472                 3) ssh works fine, but scp hangs after initial handshaking.
 473
 474           Workaround: activate this option and add a rule to your firewall
 475           configuration like:
 476
 477           iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
 478                          -j TCPMSS --clamp-mss-to-pmtu
 479
 480           To compile it as a module, choose M here.  If unsure, say N.
 481
 482 config NETFILTER_XT_TARGET_TCPOPTSTRIP
 483         tristate '"TCPOPTSTRIP" target support (EXPERIMENTAL)'
 484         depends on EXPERIMENTAL
 485         depends on IP_NF_MANGLE || IP6_NF_MANGLE
 486         depends on NETFILTER_ADVANCED
 487         help
 488           This option adds a "TCPOPTSTRIP" target, which allows you to strip
 489           TCP options from TCP packets.
 490
 491 config NETFILTER_XT_MATCH_COMMENT
 492         tristate  '"comment" match support'
 493         depends on NETFILTER_ADVANCED
 494         help
 495           This option adds a `comment' dummy-match, which allows you to put
 496           comments in your iptables ruleset.
 497
 498           If you want to compile it as a module, say M here and read
 499           <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
 500
 501 config NETFILTER_XT_MATCH_CONNBYTES
 502         tristate  '"connbytes" per-connection counter match support'
 503         depends on NF_CONNTRACK
 504         depends on NETFILTER_ADVANCED
 505         select NF_CT_ACCT
 506         help
 507           This option adds a `connbytes' match, which allows you to match the
 508           number of bytes and/or packets for each direction within a connection.
 509
 510           If you want to compile it as a module, say M here and read
 511           <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
 512
 513 config NETFILTER_XT_MATCH_CONNLIMIT
 514         tristate '"connlimit" match support"'
 515         depends on NF_CONNTRACK
 516         depends on NETFILTER_ADVANCED
 517         ---help---
 518           This match allows you to match against the number of parallel
 519           connections to a server per client IP address (or address block).
 520
 521 config NETFILTER_XT_MATCH_CONNMARK
 522         tristate  '"connmark" connection mark match support'
 523         depends on NF_CONNTRACK
 524         depends on NETFILTER_ADVANCED
 525         select NF_CONNTRACK_MARK
 526         help
 527           This option adds a `connmark' match, which allows you to match the
 528           connection mark value previously set for the session by `CONNMARK'.
 529
 530           If you want to compile it as a module, say M here and read
 531           <file:Documentation/kbuild/modules.txt>.  The module will be called
 532           ipt_connmark.ko.  If unsure, say `N'.
 533
 534 config NETFILTER_XT_MATCH_CONNTRACK
 535         tristate '"conntrack" connection tracking match support'
 536         depends on NF_CONNTRACK
 537         default m if NETFILTER_ADVANCED=n
 538         help
 539           This is a general conntrack match module, a superset of the state match.
 540
 541           It allows matching on additional conntrack information, which is
 542           useful in complex configurations, such as NAT gateways with multiple
 543           internet links or tunnels.
 544
 545           To compile it as a module, choose M here.  If unsure, say N.
 546
 547 config NETFILTER_XT_MATCH_DCCP
 548         tristate '"dccp" protocol match support'
 549         depends on NETFILTER_ADVANCED
 550         default IP_DCCP
 551         help
 552           With this option enabled, you will be able to use the iptables
 553           `dccp' match in order to match on DCCP source/destination ports
 554           and DCCP flags.
 555
 556           If you want to compile it as a module, say M here and read
 557           <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
 558
 559 config NETFILTER_XT_MATCH_DSCP
 560         tristate '"dscp" and "tos" match support'
 561         depends on NETFILTER_ADVANCED
 562         help
 563           This option adds a `DSCP' match, which allows you to match against
 564           the IPv4/IPv6 header DSCP field (differentiated services codepoint).
 565
 566           The DSCP field can have any value between 0x0 and 0x3f inclusive.
 567
 568           It will also add a "tos" match, which allows you to match packets
 569           based on the Type Of Service fields of the IPv4 packet (which share
 570           the same bits as DSCP).
 571
 572           To compile it as a module, choose M here.  If unsure, say N.
 573
 574 config NETFILTER_XT_MATCH_ESP
 575         tristate '"esp" match support'
 576         depends on NETFILTER_ADVANCED
 577         help
 578           This match extension allows you to match a range of SPIs
 579           inside ESP header of IPSec packets.
 580
 581           To compile it as a module, choose M here.  If unsure, say N.
 582
 583 config NETFILTER_XT_MATCH_HASHLIMIT
 584         tristate '"hashlimit" match support'
 585         depends on (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
 586         depends on NETFILTER_ADVANCED
 587         help
 588           This option adds a `hashlimit' match.
 589
 590           As opposed to `limit', this match dynamically creates a hash table
 591           of limit buckets, based on your selection of source/destination
 592           addresses and/or ports.
 593
 594           It enables you to express policies like `10kpps for any given
 595           destination address' or `500pps from any given source address'
 596           with a single rule.
 597
 598 config NETFILTER_XT_MATCH_HELPER
 599         tristate '"helper" match support'
 600         depends on NF_CONNTRACK
 601         depends on NETFILTER_ADVANCED
 602         help
 603           Helper matching allows you to match packets in dynamic connections
 604           tracked by a conntrack-helper, ie. ip_conntrack_ftp
 605
 606           To compile it as a module, choose M here.  If unsure, say Y.
 607
 608 config NETFILTER_XT_MATCH_IPRANGE
 609         tristate '"iprange" address range match support'
 610         depends on NETFILTER_ADVANCED
 611         ---help---
 612         This option adds a "iprange" match, which allows you to match based on
 613         an IP address range. (Normal iptables only matches on single addresses
 614         with an optional mask.)
 615
 616         If unsure, say M.
 617
 618 config NETFILTER_XT_MATCH_LENGTH
 619         tristate '"length" match support'
 620         depends on NETFILTER_ADVANCED
 621         help
 622           This option allows you to match the length of a packet against a
 623           specific value or range of values.
 624
 625           To compile it as a module, choose M here.  If unsure, say N.
 626
 627 config NETFILTER_XT_MATCH_LIMIT
 628         tristate '"limit" match support'
 629         depends on NETFILTER_ADVANCED
 630         help
 631           limit matching allows you to control the rate at which a rule can be
 632           matched: mainly useful in combination with the LOG target ("LOG
 633           target support", below) and to avoid some Denial of Service attacks.
 634
 635           To compile it as a module, choose M here.  If unsure, say N.
 636
 637 config NETFILTER_XT_MATCH_MAC
 638         tristate '"mac" address match support'
 639         depends on NETFILTER_ADVANCED
 640         help
 641           MAC matching allows you to match packets based on the source
 642           Ethernet address of the packet.
 643
 644           To compile it as a module, choose M here.  If unsure, say N.
 645
 646 config NETFILTER_XT_MATCH_MARK
 647         tristate '"mark" match support'
 648         default m if NETFILTER_ADVANCED=n
 649         help
 650           Netfilter mark matching allows you to match packets based on the
 651           `nfmark' value in the packet.  This can be set by the MARK target
 652           (see below).
 653
 654           To compile it as a module, choose M here.  If unsure, say N.
 655
 656 config NETFILTER_XT_MATCH_MULTIPORT
 657         tristate '"multiport" Multiple port match support'
 658         depends on NETFILTER_ADVANCED
 659         help
 660           Multiport matching allows you to match TCP or UDP packets based on
 661           a series of source or destination ports: normally a rule can only
 662           match a single range of ports.
 663
 664           To compile it as a module, choose M here.  If unsure, say N.
 665
 666 config NETFILTER_XT_MATCH_OWNER
 667         tristate '"owner" match support'
 668         depends on NETFILTER_ADVANCED
 669         ---help---
 670         Socket owner matching allows you to match locally-generated packets
 671         based on who created the socket: the user or group. It is also
 672         possible to check whether a socket actually exists.
 673
 674 config NETFILTER_XT_MATCH_POLICY
 675         tristate 'IPsec "policy" match support'
 676         depends on XFRM
 677         default m if NETFILTER_ADVANCED=n
 678         help
 679           Policy matching allows you to match packets based on the
 680           IPsec policy that was used during decapsulation/will
 681           be used during encapsulation.
 682
 683           To compile it as a module, choose M here.  If unsure, say N.
 684
 685 config NETFILTER_XT_MATCH_PHYSDEV
 686         tristate '"physdev" match support'
 687         depends on BRIDGE && BRIDGE_NETFILTER
 688         depends on NETFILTER_ADVANCED
 689         help
 690           Physdev packet matching matches against the physical bridge ports
 691           the IP packet arrived on or will leave by.
 692
 693           To compile it as a module, choose M here.  If unsure, say N.
 694
 695 config NETFILTER_XT_MATCH_PKTTYPE
 696         tristate '"pkttype" packet type match support'
 697         depends on NETFILTER_ADVANCED
 698         help
 699           Packet type matching allows you to match a packet by
 700           its "class", eg. BROADCAST, MULTICAST, ...
 701
 702           Typical usage:
 703           iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG
 704
 705           To compile it as a module, choose M here.  If unsure, say N.
 706
 707 config NETFILTER_XT_MATCH_QUOTA
 708         tristate '"quota" match support'
 709         depends on NETFILTER_ADVANCED
 710         help
 711           This option adds a `quota' match, which allows to match on a
 712           byte counter.
 713
 714           If you want to compile it as a module, say M here and read
 715           <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
 716
 717 config NETFILTER_XT_MATCH_RATEEST
 718         tristate '"rateest" match support'
 719         depends on NETFILTER_ADVANCED
 720         select NETFILTER_XT_TARGET_RATEEST
 721         help
 722           This option adds a `rateest' match, which allows to match on the
 723           rate estimated by the RATEEST target.
 724
 725           To compile it as a module, choose M here.  If unsure, say N.
 726
 727 config NETFILTER_XT_MATCH_REALM
 728         tristate  '"realm" match support'
 729         depends on NETFILTER_ADVANCED
 730         select NET_CLS_ROUTE
 731         help
 732           This option adds a `realm' match, which allows you to use the realm
 733           key from the routing subsystem inside iptables.
 734
 735           This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option
 736           in tc world.
 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_MATCH_RECENT
 742         tristate '"recent" match support'
 743         depends on NETFILTER_ADVANCED
 744         ---help---
 745         This match is used for creating one or many lists of recently
 746         used addresses and then matching against that/those list(s).
 747
 748         Short options are available by using 'iptables -m recent -h'
 749         Official Website: <http://snowman.net/projects/ipt_recent/>
 750
 751 config NETFILTER_XT_MATCH_RECENT_PROC_COMPAT
 752         bool 'Enable obsolete /proc/net/ipt_recent'
 753         depends on NETFILTER_XT_MATCH_RECENT && PROC_FS
 754         ---help---
 755         This option enables the old /proc/net/ipt_recent interface,
 756         which has been obsoleted by /proc/net/xt_recent.
 757
 758 config NETFILTER_XT_MATCH_SCTP
 759         tristate  '"sctp" protocol match support (EXPERIMENTAL)'
 760         depends on EXPERIMENTAL
 761         depends on NETFILTER_ADVANCED
 762         default IP_SCTP
 763         help
 764           With this option enabled, you will be able to use the
 765           `sctp' match in order to match on SCTP source/destination ports
 766           and SCTP chunk types.
 767
 768           If you want to compile it as a module, say M here and read
 769           <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
 770
 771 config NETFILTER_XT_MATCH_SOCKET
 772         tristate '"socket" match support (EXPERIMENTAL)'
 773         depends on EXPERIMENTAL
 774         depends on NETFILTER_TPROXY
 775         depends on NETFILTER_XTABLES
 776         depends on NETFILTER_ADVANCED
 777         select NF_DEFRAG_IPV4
 778         help
 779           This option adds a `socket' match, which can be used to match
 780           packets for which a TCP or UDP socket lookup finds a valid socket.
 781           It can be used in combination with the MARK target and policy
 782           routing to implement full featured non-locally bound sockets.
 783
 784           To compile it as a module, choose M here.  If unsure, say N.
 785
 786 config NETFILTER_XT_MATCH_STATE
 787         tristate '"state" match support'
 788         depends on NF_CONNTRACK
 789         default m if NETFILTER_ADVANCED=n
 790         help
 791           Connection state matching allows you to match packets based on their
 792           relationship to a tracked connection (ie. previous packets).  This
 793           is a powerful tool for packet classification.
 794
 795           To compile it as a module, choose M here.  If unsure, say N.
 796
 797 config NETFILTER_XT_MATCH_STATISTIC
 798         tristate '"statistic" match support'
 799         depends on NETFILTER_ADVANCED
 800         help
 801           This option adds a `statistic' match, which allows you to match
 802           on packets periodically or randomly with a given percentage.
 803
 804           To compile it as a module, choose M here.  If unsure, say N.
 805
 806 config NETFILTER_XT_MATCH_STRING
 807         tristate  '"string" match support'
 808         depends on NETFILTER_ADVANCED
 809         select TEXTSEARCH
 810         select TEXTSEARCH_KMP
 811         select TEXTSEARCH_BM
 812         select TEXTSEARCH_FSM
 813         help
 814           This option adds a `string' match, which allows you to look for
 815           pattern matchings in packets.
 816
 817           To compile it as a module, choose M here.  If unsure, say N.
 818
 819 config NETFILTER_XT_MATCH_TCPMSS
 820         tristate '"tcpmss" match support'
 821         depends on NETFILTER_ADVANCED
 822         help
 823           This option adds a `tcpmss' match, which allows you to examine the
 824           MSS value of TCP SYN packets, which control the maximum packet size
 825           for that connection.
 826
 827           To compile it as a module, choose M here.  If unsure, say N.
 828
 829 config NETFILTER_XT_MATCH_TIME
 830         tristate '"time" match support'
 831         depends on NETFILTER_ADVANCED
 832         ---help---
 833           This option adds a "time" match, which allows you to match based on
 834           the packet arrival time (at the machine which netfilter is running)
 835           on) or departure time/date (for locally generated packets).
 836
 837           If you say Y here, try `iptables -m time --help` for
 838           more information.
 839
 840           If you want to compile it as a module, say M here.
 841           If unsure, say N.
 842
 843 config NETFILTER_XT_MATCH_U32
 844         tristate '"u32" match support'
 845         depends on NETFILTER_ADVANCED
 846         ---help---
 847           u32 allows you to extract quantities of up to 4 bytes from a packet,
 848           AND them with specified masks, shift them by specified amounts and
 849           test whether the results are in any of a set of specified ranges.
 850           The specification of what to extract is general enough to skip over
 851           headers with lengths stored in the packet, as in IP or TCP header
 852           lengths.
 853
 854           Details and examples are in the kernel module source.
 855
 856 endif # NETFILTER_XTABLES
 857
 858 endmenu
 859
 860 source "net/netfilter/ipvs/Kconfig"