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