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         depends on NF_NAT=n || NF_NAT
 275         default m if NETFILTER_ADVANCED=n
 276         help
 277           This option enables support for a netlink-based userspace interface
 278
 279 # transparent proxy support
 280 config NETFILTER_TPROXY
 281         tristate "Transparent proxying support (EXPERIMENTAL)"
 282         depends on EXPERIMENTAL
 283         depends on IP_NF_MANGLE
 284         depends on NETFILTER_ADVANCED
 285         help
 286           This option enables transparent proxying support, that is,
 287           support for handling non-locally bound IPv4 TCP and UDP sockets.
 288           For it to work you will have to configure certain iptables rules
 289           and use policy routing. For more information on how to set it up
 290           see Documentation/networking/tproxy.txt.
 291
 292           To compile it as a module, choose M here.  If unsure, say N.
 293
 294 endif # NF_CONNTRACK
 295
 296 config NETFILTER_XTABLES
 297         tristate "Netfilter Xtables support (required for ip_tables)"
 298         default m if NETFILTER_ADVANCED=n
 299         help
 300           This is required if you intend to use any of ip_tables,
 301           ip6_tables or arp_tables.
 302
 303 if NETFILTER_XTABLES
 304
 305 # alphabetically ordered list of targets
 306
 307 config NETFILTER_XT_TARGET_CLASSIFY
 308         tristate '"CLASSIFY" target support'
 309         depends on NETFILTER_ADVANCED
 310         help
 311           This option adds a `CLASSIFY' target, which enables the user to set
 312           the priority of a packet. Some qdiscs can use this value for
 313           classification, among these are:
 314
 315           atm, cbq, dsmark, pfifo_fast, htb, prio
 316
 317           To compile it as a module, choose M here.  If unsure, say N.
 318
 319 config NETFILTER_XT_TARGET_CONNMARK
 320         tristate  '"CONNMARK" target support'
 321         depends on NF_CONNTRACK
 322         depends on NETFILTER_ADVANCED
 323         select NF_CONNTRACK_MARK
 324         help
 325           This option adds a `CONNMARK' target, which allows one to manipulate
 326           the connection mark value.  Similar to the MARK target, but
 327           affects the connection mark value rather than the packet mark value.
 328
 329           If you want to compile it as a module, say M here and read
 330           <file:Documentation/kbuild/modules.txt>.  The module will be called
 331           ipt_CONNMARK.ko.  If unsure, say `N'.
 332
 333 config NETFILTER_XT_TARGET_CONNSECMARK
 334         tristate '"CONNSECMARK" target support'
 335         depends on NF_CONNTRACK && NF_CONNTRACK_SECMARK
 336         default m if NETFILTER_ADVANCED=n
 337         help
 338           The CONNSECMARK target copies security markings from packets
 339           to connections, and restores security markings from connections
 340           to packets (if the packets are not already marked).  This would
 341           normally be used in conjunction with the SECMARK target.
 342
 343           To compile it as a module, choose M here.  If unsure, say N.
 344
 345 config NETFILTER_XT_TARGET_DSCP
 346         tristate '"DSCP" and "TOS" target support'
 347         depends on IP_NF_MANGLE || IP6_NF_MANGLE
 348         depends on NETFILTER_ADVANCED
 349         help
 350           This option adds a `DSCP' target, which allows you to manipulate
 351           the IPv4/IPv6 header DSCP field (differentiated services codepoint).
 352
 353           The DSCP field can have any value between 0x0 and 0x3f inclusive.
 354
 355           It also adds the "TOS" target, which allows you to create rules in
 356           the "mangle" table which alter the Type Of Service field of an IPv4
 357           or the Priority field of an IPv6 packet, prior to routing.
 358
 359           To compile it as a module, choose M here.  If unsure, say N.
 360
 361 config NETFILTER_XT_TARGET_MARK
 362         tristate '"MARK" target support'
 363         default m if NETFILTER_ADVANCED=n
 364         help
 365           This option adds a `MARK' target, which allows you to create rules
 366           in the `mangle' table which alter the netfilter mark (nfmark) field
 367           associated with the packet prior to routing. This can change
 368           the routing method (see `Use netfilter MARK value as routing
 369           key') and can also be used by other subsystems to change their
 370           behavior.
 371
 372           To compile it as a module, choose M here.  If unsure, say N.
 373
 374 config NETFILTER_XT_TARGET_NFLOG
 375         tristate '"NFLOG" target support'
 376         default m if NETFILTER_ADVANCED=n
 377         help
 378           This option enables the NFLOG target, which allows to LOG
 379           messages through the netfilter logging API, which can use
 380           either the old LOG target, the old ULOG target or nfnetlink_log
 381           as backend.
 382
 383           To compile it as a module, choose M here.  If unsure, say N.
 384
 385 config NETFILTER_XT_TARGET_NFQUEUE
 386         tristate '"NFQUEUE" target Support'
 387         depends on NETFILTER_ADVANCED
 388         help
 389           This target replaced the old obsolete QUEUE target.
 390
 391           As opposed to QUEUE, it supports 65535 different queues,
 392           not just one.
 393
 394           To compile it as a module, choose M here.  If unsure, say N.
 395
 396 config NETFILTER_XT_TARGET_NOTRACK
 397         tristate  '"NOTRACK" target support'
 398         depends on IP_NF_RAW || IP6_NF_RAW
 399         depends on NF_CONNTRACK
 400         depends on NETFILTER_ADVANCED
 401         help
 402           The NOTRACK target allows a select rule to specify
 403           which packets *not* to enter the conntrack/NAT
 404           subsystem with all the consequences (no ICMP error tracking,
 405           no protocol helpers for the selected packets).
 406
 407           If you want to compile it as a module, say M here and read
 408           <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
 409
 410 config NETFILTER_XT_TARGET_RATEEST
 411         tristate '"RATEEST" target support'
 412         depends on NETFILTER_ADVANCED
 413         help
 414           This option adds a `RATEEST' target, which allows to measure
 415           rates similar to TC estimators. The `rateest' match can be
 416           used to match on the measured rates.
 417
 418           To compile it as a module, choose M here.  If unsure, say N.
 419
 420 config NETFILTER_XT_TARGET_TPROXY
 421         tristate '"TPROXY" target support (EXPERIMENTAL)'
 422         depends on EXPERIMENTAL
 423         depends on NETFILTER_TPROXY
 424         depends on NETFILTER_XTABLES
 425         depends on NETFILTER_ADVANCED
 426         select NF_DEFRAG_IPV4
 427         help
 428           This option adds a `TPROXY' target, which is somewhat similar to
 429           REDIRECT.  It can only be used in the mangle table and is useful
 430           to redirect traffic to a transparent proxy.  It does _not_ depend
 431           on Netfilter connection tracking and NAT, unlike REDIRECT.
 432
 433           To compile it as a module, choose M here.  If unsure, say N.
 434
 435 config NETFILTER_XT_TARGET_TRACE
 436         tristate  '"TRACE" target support'
 437         depends on IP_NF_RAW || IP6_NF_RAW
 438         depends on NETFILTER_ADVANCED
 439         help
 440           The TRACE target allows you to mark packets so that the kernel
 441           will log every rule which match the packets as those traverse
 442           the tables, chains, rules.
 443
 444           If you want to compile it as a module, say M here and read
 445           <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
 446
 447 config NETFILTER_XT_TARGET_SECMARK
 448         tristate '"SECMARK" target support'
 449         depends on NETWORK_SECMARK
 450         default m if NETFILTER_ADVANCED=n
 451         help
 452           The SECMARK target allows security marking of network
 453           packets, for use with security subsystems.
 454
 455           To compile it as a module, choose M here.  If unsure, say N.
 456
 457 config NETFILTER_XT_TARGET_TCPMSS
 458         tristate '"TCPMSS" target support'
 459         depends on (IPV6 || IPV6=n)
 460         default m if NETFILTER_ADVANCED=n
 461         ---help---
 462           This option adds a `TCPMSS' target, which allows you to alter the
 463           MSS value of TCP SYN packets, to control the maximum size for that
 464           connection (usually limiting it to your outgoing interface's MTU
 465           minus 40).
 466
 467           This is used to overcome criminally braindead ISPs or servers which
 468           block ICMP Fragmentation Needed packets.  The symptoms of this
 469           problem are that everything works fine from your Linux
 470           firewall/router, but machines behind it can never exchange large
 471           packets:
 472                 1) Web browsers connect, then hang with no data received.
 473                 2) Small mail works fine, but large emails hang.
 474                 3) ssh works fine, but scp hangs after initial handshaking.
 475
 476           Workaround: activate this option and add a rule to your firewall
 477           configuration like:
 478
 479           iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
 480                          -j TCPMSS --clamp-mss-to-pmtu
 481
 482           To compile it as a module, choose M here.  If unsure, say N.
 483
 484 config NETFILTER_XT_TARGET_TCPOPTSTRIP
 485         tristate '"TCPOPTSTRIP" target support (EXPERIMENTAL)'
 486         depends on EXPERIMENTAL
 487         depends on IP_NF_MANGLE || IP6_NF_MANGLE
 488         depends on NETFILTER_ADVANCED
 489         help
 490           This option adds a "TCPOPTSTRIP" target, which allows you to strip
 491           TCP options from TCP packets.
 492
 493 config NETFILTER_XT_MATCH_COMMENT
 494         tristate  '"comment" match support'
 495         depends on NETFILTER_ADVANCED
 496         help
 497           This option adds a `comment' dummy-match, which allows you to put
 498           comments in your iptables ruleset.
 499
 500           If you want to compile it as a module, say M here and read
 501           <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
 502
 503 config NETFILTER_XT_MATCH_CONNBYTES
 504         tristate  '"connbytes" per-connection counter match support'
 505         depends on NF_CONNTRACK
 506         depends on NETFILTER_ADVANCED
 507         select NF_CT_ACCT
 508         help
 509           This option adds a `connbytes' match, which allows you to match the
 510           number of bytes and/or packets for each direction within a connection.
 511
 512           If you want to compile it as a module, say M here and read
 513           <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
 514
 515 config NETFILTER_XT_MATCH_CONNLIMIT
 516         tristate '"connlimit" match support"'
 517         depends on NF_CONNTRACK
 518         depends on NETFILTER_ADVANCED
 519         ---help---
 520           This match allows you to match against the number of parallel
 521           connections to a server per client IP address (or address block).
 522
 523 config NETFILTER_XT_MATCH_CONNMARK
 524         tristate  '"connmark" connection mark match support'
 525         depends on NF_CONNTRACK
 526         depends on NETFILTER_ADVANCED
 527         select NF_CONNTRACK_MARK
 528         help
 529           This option adds a `connmark' match, which allows you to match the
 530           connection mark value previously set for the session by `CONNMARK'.
 531
 532           If you want to compile it as a module, say M here and read
 533           <file:Documentation/kbuild/modules.txt>.  The module will be called
 534           ipt_connmark.ko.  If unsure, say `N'.
 535
 536 config NETFILTER_XT_MATCH_CONNTRACK
 537         tristate '"conntrack" connection tracking match support'
 538         depends on NF_CONNTRACK
 539         default m if NETFILTER_ADVANCED=n
 540         help
 541           This is a general conntrack match module, a superset of the state match.
 542
 543           It allows matching on additional conntrack information, which is
 544           useful in complex configurations, such as NAT gateways with multiple
 545           internet links or tunnels.
 546
 547           To compile it as a module, choose M here.  If unsure, say N.
 548
 549 config NETFILTER_XT_MATCH_DCCP
 550         tristate '"dccp" protocol match support'
 551         depends on NETFILTER_ADVANCED
 552         default IP_DCCP
 553         help
 554           With this option enabled, you will be able to use the iptables
 555           `dccp' match in order to match on DCCP source/destination ports
 556           and DCCP flags.
 557
 558           If you want to compile it as a module, say M here and read
 559           <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
 560
 561 config NETFILTER_XT_MATCH_DSCP
 562         tristate '"dscp" and "tos" match support'
 563         depends on NETFILTER_ADVANCED
 564         help
 565           This option adds a `DSCP' match, which allows you to match against
 566           the IPv4/IPv6 header DSCP field (differentiated services codepoint).
 567
 568           The DSCP field can have any value between 0x0 and 0x3f inclusive.
 569
 570           It will also add a "tos" match, which allows you to match packets
 571           based on the Type Of Service fields of the IPv4 packet (which share
 572           the same bits as DSCP).
 573
 574           To compile it as a module, choose M here.  If unsure, say N.
 575
 576 config NETFILTER_XT_MATCH_ESP
 577         tristate '"esp" match support'
 578         depends on NETFILTER_ADVANCED
 579         help
 580           This match extension allows you to match a range of SPIs
 581           inside ESP header of IPSec packets.
 582
 583           To compile it as a module, choose M here.  If unsure, say N.
 584
 585 config NETFILTER_XT_MATCH_HASHLIMIT
 586         tristate '"hashlimit" match support'
 587         depends on (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
 588         depends on NETFILTER_ADVANCED
 589         help
 590           This option adds a `hashlimit' match.
 591
 592           As opposed to `limit', this match dynamically creates a hash table
 593           of limit buckets, based on your selection of source/destination
 594           addresses and/or ports.
 595
 596           It enables you to express policies like `10kpps for any given
 597           destination address' or `500pps from any given source address'
 598           with a single rule.
 599
 600 config NETFILTER_XT_MATCH_HELPER
 601         tristate '"helper" match support'
 602         depends on NF_CONNTRACK
 603         depends on NETFILTER_ADVANCED
 604         help
 605           Helper matching allows you to match packets in dynamic connections
 606           tracked by a conntrack-helper, ie. ip_conntrack_ftp
 607
 608           To compile it as a module, choose M here.  If unsure, say Y.
 609
 610 config NETFILTER_XT_MATCH_IPRANGE
 611         tristate '"iprange" address range match support'
 612         depends on NETFILTER_ADVANCED
 613         ---help---
 614         This option adds a "iprange" match, which allows you to match based on
 615         an IP address range. (Normal iptables only matches on single addresses
 616         with an optional mask.)
 617
 618         If unsure, say M.
 619
 620 config NETFILTER_XT_MATCH_LENGTH
 621         tristate '"length" match support'
 622         depends on NETFILTER_ADVANCED
 623         help
 624           This option allows you to match the length of a packet against a
 625           specific value or range of values.
 626
 627           To compile it as a module, choose M here.  If unsure, say N.
 628
 629 config NETFILTER_XT_MATCH_LIMIT
 630         tristate '"limit" match support'
 631         depends on NETFILTER_ADVANCED
 632         help
 633           limit matching allows you to control the rate at which a rule can be
 634           matched: mainly useful in combination with the LOG target ("LOG
 635           target support", below) and to avoid some Denial of Service attacks.
 636
 637           To compile it as a module, choose M here.  If unsure, say N.
 638
 639 config NETFILTER_XT_MATCH_MAC
 640         tristate '"mac" address match support'
 641         depends on NETFILTER_ADVANCED
 642         help
 643           MAC matching allows you to match packets based on the source
 644           Ethernet address of the packet.
 645
 646           To compile it as a module, choose M here.  If unsure, say N.
 647
 648 config NETFILTER_XT_MATCH_MARK
 649         tristate '"mark" match support'
 650         default m if NETFILTER_ADVANCED=n
 651         help
 652           Netfilter mark matching allows you to match packets based on the
 653           `nfmark' value in the packet.  This can be set by the MARK target
 654           (see below).
 655
 656           To compile it as a module, choose M here.  If unsure, say N.
 657
 658 config NETFILTER_XT_MATCH_MULTIPORT
 659         tristate '"multiport" Multiple port match support'
 660         depends on NETFILTER_ADVANCED
 661         help
 662           Multiport matching allows you to match TCP or UDP packets based on
 663           a series of source or destination ports: normally a rule can only
 664           match a single range of ports.
 665
 666           To compile it as a module, choose M here.  If unsure, say N.
 667
 668 config NETFILTER_XT_MATCH_OWNER
 669         tristate '"owner" match support'
 670         depends on NETFILTER_ADVANCED
 671         ---help---
 672         Socket owner matching allows you to match locally-generated packets
 673         based on who created the socket: the user or group. It is also
 674         possible to check whether a socket actually exists.
 675
 676 config NETFILTER_XT_MATCH_POLICY
 677         tristate 'IPsec "policy" match support'
 678         depends on XFRM
 679         default m if NETFILTER_ADVANCED=n
 680         help
 681           Policy matching allows you to match packets based on the
 682           IPsec policy that was used during decapsulation/will
 683           be used during encapsulation.
 684
 685           To compile it as a module, choose M here.  If unsure, say N.
 686
 687 config NETFILTER_XT_MATCH_PHYSDEV
 688         tristate '"physdev" match support'
 689         depends on BRIDGE && BRIDGE_NETFILTER
 690         depends on NETFILTER_ADVANCED
 691         help
 692           Physdev packet matching matches against the physical bridge ports
 693           the IP packet arrived on or will leave by.
 694
 695           To compile it as a module, choose M here.  If unsure, say N.
 696
 697 config NETFILTER_XT_MATCH_PKTTYPE
 698         tristate '"pkttype" packet type match support'
 699         depends on NETFILTER_ADVANCED
 700         help
 701           Packet type matching allows you to match a packet by
 702           its "class", eg. BROADCAST, MULTICAST, ...
 703
 704           Typical usage:
 705           iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG
 706
 707           To compile it as a module, choose M here.  If unsure, say N.
 708
 709 config NETFILTER_XT_MATCH_QUOTA
 710         tristate '"quota" match support'
 711         depends on NETFILTER_ADVANCED
 712         help
 713           This option adds a `quota' match, which allows to match on a
 714           byte counter.
 715
 716           If you want to compile it as a module, say M here and read
 717           <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
 718
 719 config NETFILTER_XT_MATCH_RATEEST
 720         tristate '"rateest" match support'
 721         depends on NETFILTER_ADVANCED
 722         select NETFILTER_XT_TARGET_RATEEST
 723         help
 724           This option adds a `rateest' match, which allows to match on the
 725           rate estimated by the RATEEST target.
 726
 727           To compile it as a module, choose M here.  If unsure, say N.
 728
 729 config NETFILTER_XT_MATCH_REALM
 730         tristate  '"realm" match support'
 731         depends on NETFILTER_ADVANCED
 732         select NET_CLS_ROUTE
 733         help
 734           This option adds a `realm' match, which allows you to use the realm
 735           key from the routing subsystem inside iptables.
 736
 737           This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option
 738           in tc world.
 739
 740           If you want to compile it as a module, say M here and read
 741           <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
 742
 743 config NETFILTER_XT_MATCH_RECENT
 744         tristate '"recent" match support'
 745         depends on NETFILTER_ADVANCED
 746         ---help---
 747         This match is used for creating one or many lists of recently
 748         used addresses and then matching against that/those list(s).
 749
 750         Short options are available by using 'iptables -m recent -h'
 751         Official Website: <http://snowman.net/projects/ipt_recent/>
 752
 753 config NETFILTER_XT_MATCH_RECENT_PROC_COMPAT
 754         bool 'Enable obsolete /proc/net/ipt_recent'
 755         depends on NETFILTER_XT_MATCH_RECENT && PROC_FS
 756         ---help---
 757         This option enables the old /proc/net/ipt_recent interface,
 758         which has been obsoleted by /proc/net/xt_recent.
 759
 760 config NETFILTER_XT_MATCH_SCTP
 761         tristate  '"sctp" protocol match support (EXPERIMENTAL)'
 762         depends on EXPERIMENTAL
 763         depends on NETFILTER_ADVANCED
 764         default IP_SCTP
 765         help
 766           With this option enabled, you will be able to use the
 767           `sctp' match in order to match on SCTP source/destination ports
 768           and SCTP chunk types.
 769
 770           If you want to compile it as a module, say M here and read
 771           <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
 772
 773 config NETFILTER_XT_MATCH_SOCKET
 774         tristate '"socket" match support (EXPERIMENTAL)'
 775         depends on EXPERIMENTAL
 776         depends on NETFILTER_TPROXY
 777         depends on NETFILTER_XTABLES
 778         depends on NETFILTER_ADVANCED
 779         select NF_DEFRAG_IPV4
 780         help
 781           This option adds a `socket' match, which can be used to match
 782           packets for which a TCP or UDP socket lookup finds a valid socket.
 783           It can be used in combination with the MARK target and policy
 784           routing to implement full featured non-locally bound sockets.
 785
 786           To compile it as a module, choose M here.  If unsure, say N.
 787
 788 config NETFILTER_XT_MATCH_STATE
 789         tristate '"state" match support'
 790         depends on NF_CONNTRACK
 791         default m if NETFILTER_ADVANCED=n
 792         help
 793           Connection state matching allows you to match packets based on their
 794           relationship to a tracked connection (ie. previous packets).  This
 795           is a powerful tool for packet classification.
 796
 797           To compile it as a module, choose M here.  If unsure, say N.
 798
 799 config NETFILTER_XT_MATCH_STATISTIC
 800         tristate '"statistic" match support'
 801         depends on NETFILTER_ADVANCED
 802         help
 803           This option adds a `statistic' match, which allows you to match
 804           on packets periodically or randomly with a given percentage.
 805
 806           To compile it as a module, choose M here.  If unsure, say N.
 807
 808 config NETFILTER_XT_MATCH_STRING
 809         tristate  '"string" match support'
 810         depends on NETFILTER_ADVANCED
 811         select TEXTSEARCH
 812         select TEXTSEARCH_KMP
 813         select TEXTSEARCH_BM
 814         select TEXTSEARCH_FSM
 815         help
 816           This option adds a `string' match, which allows you to look for
 817           pattern matchings in packets.
 818
 819           To compile it as a module, choose M here.  If unsure, say N.
 820
 821 config NETFILTER_XT_MATCH_TCPMSS
 822         tristate '"tcpmss" match support'
 823         depends on NETFILTER_ADVANCED
 824         help
 825           This option adds a `tcpmss' match, which allows you to examine the
 826           MSS value of TCP SYN packets, which control the maximum packet size
 827           for that connection.
 828
 829           To compile it as a module, choose M here.  If unsure, say N.
 830
 831 config NETFILTER_XT_MATCH_TIME
 832         tristate '"time" match support'
 833         depends on NETFILTER_ADVANCED
 834         ---help---
 835           This option adds a "time" match, which allows you to match based on
 836           the packet arrival time (at the machine which netfilter is running)
 837           on) or departure time/date (for locally generated packets).
 838
 839           If you say Y here, try `iptables -m time --help` for
 840           more information.
 841
 842           If you want to compile it as a module, say M here.
 843           If unsure, say N.
 844
 845 config NETFILTER_XT_MATCH_U32
 846         tristate '"u32" match support'
 847         depends on NETFILTER_ADVANCED
 848         ---help---
 849           u32 allows you to extract quantities of up to 4 bytes from a packet,
 850           AND them with specified masks, shift them by specified amounts and
 851           test whether the results are in any of a set of specified ranges.
 852           The specification of what to extract is general enough to skip over
 853           headers with lengths stored in the packet, as in IP or TCP header
 854           lengths.
 855
 856           Details and examples are in the kernel module source.
 857
 858 endif # NETFILTER_XTABLES
 859
 860 endmenu
 861
 862 source "net/netfilter/ipvs/Kconfig"