net/netfilter/Kconfig

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