net/ipv4/netfilter/Kconfig

   1 #
   2 # IP netfilter configuration
   3 #
   4
   5 menu "IP: Netfilter Configuration"
   6         depends on INET && NETFILTER
   7
   8 config NF_CONNTRACK_IPV4
   9         tristate "IPv4 support for new connection tracking (required for NAT) (EXPERIMENTAL)"
  10         depends on EXPERIMENTAL && NF_CONNTRACK
  11         ---help---
  12           Connection tracking keeps a record of what packets have passed
  13           through your machine, in order to figure out how they are related
  14           into connections.
  15
  16           This is IPv4 support on Layer 3 independent connection tracking.
  17           Layer 3 independent connection tracking is experimental scheme
  18           which generalize ip_conntrack to support other layer 3 protocols.
  19
  20           To compile it as a module, choose M here.  If unsure, say N.
  21
  22 config NF_CONNTRACK_PROC_COMPAT
  23         bool "proc/sysctl compatibility with old connection tracking"
  24         depends on NF_CONNTRACK_IPV4
  25         default y
  26         help
  27           This option enables /proc and sysctl compatibility with the old
  28           layer 3 dependant connection tracking. This is needed to keep
  29           old programs that have not been adapted to the new names working.
  30
  31           If unsure, say Y.
  32
  33 # connection tracking, helpers and protocols
  34 config IP_NF_CT_ACCT
  35         bool "Connection tracking flow accounting"
  36         depends on IP_NF_CONNTRACK
  37         help
  38           If this option is enabled, the connection tracking code will
  39           keep per-flow packet and byte counters.
  40
  41           Those counters can be used for flow-based accounting or the
  42           `connbytes' match.
  43
  44           If unsure, say `N'.
  45
  46 config IP_NF_CONNTRACK_MARK
  47         bool  'Connection mark tracking support'
  48         depends on IP_NF_CONNTRACK
  49         help
  50           This option enables support for connection marks, used by the
  51           `CONNMARK' target and `connmark' match. Similar to the mark value
  52           of packets, but this mark value is kept in the conntrack session
  53           instead of the individual packets.
  54
  55 config IP_NF_CONNTRACK_SECMARK
  56         bool  'Connection tracking security mark support'
  57         depends on IP_NF_CONNTRACK && NETWORK_SECMARK
  58         help
  59           This option enables security markings to be applied to
  60           connections.  Typically they are copied to connections from
  61           packets using the CONNSECMARK target and copied back from
  62           connections to packets with the same target, with the packets
  63           being originally labeled via SECMARK.
  64
  65           If unsure, say 'N'.
  66
  67 config IP_NF_CONNTRACK_EVENTS
  68         bool "Connection tracking events (EXPERIMENTAL)"
  69         depends on EXPERIMENTAL && IP_NF_CONNTRACK
  70         help
  71           If this option is enabled, the connection tracking code will
  72           provide a notifier chain that can be used by other kernel code
  73           to get notified about changes in the connection tracking state.
  74
  75           IF unsure, say `N'.
  76
  77 config IP_NF_CONNTRACK_NETLINK
  78         tristate 'Connection tracking netlink interface (EXPERIMENTAL)'
  79         depends on EXPERIMENTAL && IP_NF_CONNTRACK && NETFILTER_NETLINK
  80         depends on IP_NF_CONNTRACK!=y || NETFILTER_NETLINK!=m
  81         depends on IP_NF_NAT=n || IP_NF_NAT
  82         help
  83           This option enables support for a netlink-based userspace interface
  84
  85
  86 config IP_NF_CT_PROTO_SCTP
  87         tristate  'SCTP protocol connection tracking support (EXPERIMENTAL)'
  88         depends on IP_NF_CONNTRACK && EXPERIMENTAL
  89         help
  90           With this option enabled, the connection tracking code will
  91           be able to do state tracking on SCTP connections.
  92
  93           If you want to compile it as a module, say M here and read
  94           <file:Documentation/modules.txt>.  If unsure, say `N'.
  95
  96 config IP_NF_FTP
  97         tristate "FTP protocol support"
  98         depends on IP_NF_CONNTRACK
  99         help
 100           Tracking FTP connections is problematic: special helpers are
 101           required for tracking them, and doing masquerading and other forms
 102           of Network Address Translation on them.
 103
 104           To compile it as a module, choose M here.  If unsure, say Y.
 105
 106 config IP_NF_IRC
 107         tristate "IRC protocol support"
 108         depends on IP_NF_CONNTRACK
 109         ---help---
 110           There is a commonly-used extension to IRC called
 111           Direct Client-to-Client Protocol (DCC).  This enables users to send
 112           files to each other, and also chat to each other without the need
 113           of a server.  DCC Sending is used anywhere you send files over IRC,
 114           and DCC Chat is most commonly used by Eggdrop bots.  If you are
 115           using NAT, this extension will enable you to send files and initiate
 116           chats.  Note that you do NOT need this extension to get files or
 117           have others initiate chats, or everything else in IRC.
 118
 119           To compile it as a module, choose M here.  If unsure, say Y.
 120
 121 config IP_NF_NETBIOS_NS
 122         tristate "NetBIOS name service protocol support (EXPERIMENTAL)"
 123         depends on IP_NF_CONNTRACK && EXPERIMENTAL
 124         help
 125           NetBIOS name service requests are sent as broadcast messages from an
 126           unprivileged port and responded to with unicast messages to the
 127           same port. This make them hard to firewall properly because connection
 128           tracking doesn't deal with broadcasts. This helper tracks locally
 129           originating NetBIOS name service requests and the corresponding
 130           responses. It relies on correct IP address configuration, specifically
 131           netmask and broadcast address. When properly configured, the output
 132           of "ip address show" should look similar to this:
 133
 134           $ ip -4 address show eth0
 135           4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
 136               inet 172.16.2.252/24 brd 172.16.2.255 scope global eth0
 137
 138           To compile it as a module, choose M here.  If unsure, say N.
 139
 140 config IP_NF_TFTP
 141         tristate "TFTP protocol support"
 142         depends on IP_NF_CONNTRACK
 143         help
 144           TFTP connection tracking helper, this is required depending
 145           on how restrictive your ruleset is.
 146           If you are using a tftp client behind -j SNAT or -j MASQUERADING
 147           you will need this.
 148
 149           To compile it as a module, choose M here.  If unsure, say Y.
 150
 151 config IP_NF_AMANDA
 152         tristate "Amanda backup protocol support"
 153         depends on IP_NF_CONNTRACK
 154         select TEXTSEARCH
 155         select TEXTSEARCH_KMP
 156         help
 157           If you are running the Amanda backup package <http://www.amanda.org/>
 158           on this machine or machines that will be MASQUERADED through this
 159           machine, then you may want to enable this feature.  This allows the
 160           connection tracking and natting code to allow the sub-channels that
 161           Amanda requires for communication of the backup data, messages and
 162           index.
 163
 164           To compile it as a module, choose M here.  If unsure, say Y.
 165
 166 config IP_NF_PPTP
 167         tristate  'PPTP protocol support'
 168         depends on IP_NF_CONNTRACK
 169         help
 170           This module adds support for PPTP (Point to Point Tunnelling
 171           Protocol, RFC2637) connection tracking and NAT.
 172
 173           If you are running PPTP sessions over a stateful firewall or NAT
 174           box, you may want to enable this feature.
 175
 176           Please note that not all PPTP modes of operation are supported yet.
 177           For more info, read top of the file
 178           net/ipv4/netfilter/ip_conntrack_pptp.c
 179
 180           If you want to compile it as a module, say M here and read
 181           Documentation/modules.txt.  If unsure, say `N'.
 182
 183 config IP_NF_H323
 184         tristate  'H.323 protocol support (EXPERIMENTAL)'
 185         depends on IP_NF_CONNTRACK && EXPERIMENTAL
 186         help
 187           H.323 is a VoIP signalling protocol from ITU-T. As one of the most
 188           important VoIP protocols, it is widely used by voice hardware and
 189           software including voice gateways, IP phones, Netmeeting, OpenPhone,
 190           Gnomemeeting, etc.
 191
 192           With this module you can support H.323 on a connection tracking/NAT
 193           firewall.
 194
 195           This module supports RAS, Fast Start, H.245 Tunnelling, Call
 196           Forwarding, RTP/RTCP and T.120 based audio, video, fax, chat,
 197           whiteboard, file transfer, etc. For more information, please
 198           visit http://nath323.sourceforge.net/.
 199
 200           If you want to compile it as a module, say 'M' here and read
 201           Documentation/modules.txt.  If unsure, say 'N'.
 202
 203 config IP_NF_SIP
 204         tristate "SIP protocol support (EXPERIMENTAL)"
 205         depends on IP_NF_CONNTRACK && EXPERIMENTAL
 206         help
 207           SIP is an application-layer control protocol that can establish,
 208           modify, and terminate multimedia sessions (conferences) such as
 209           Internet telephony calls. With the ip_conntrack_sip and
 210           the ip_nat_sip modules you can support the protocol on a connection
 211           tracking/NATing firewall.
 212
 213           To compile it as a module, choose M here.  If unsure, say Y.
 214
 215 config IP_NF_QUEUE
 216         tristate "IP Userspace queueing via NETLINK (OBSOLETE)"
 217         help
 218           Netfilter has the ability to queue packets to user space: the
 219           netlink device can be used to access them using this driver.
 220
 221           This option enables the old IPv4-only "ip_queue" implementation
 222           which has been obsoleted by the new "nfnetlink_queue" code (see
 223           CONFIG_NETFILTER_NETLINK_QUEUE).
 224
 225           To compile it as a module, choose M here.  If unsure, say N.
 226
 227 config IP_NF_IPTABLES
 228         tristate "IP tables support (required for filtering/masq/NAT)"
 229         depends on NETFILTER_XTABLES
 230         help
 231           iptables is a general, extensible packet identification framework.
 232           The packet filtering and full NAT (masquerading, port forwarding,
 233           etc) subsystems now use this: say `Y' or `M' here if you want to use
 234           either of those.
 235
 236           To compile it as a module, choose M here.  If unsure, say N.
 237
 238 # The matches.
 239 config IP_NF_MATCH_IPRANGE
 240         tristate "IP range match support"
 241         depends on IP_NF_IPTABLES
 242         help
 243           This option makes possible to match IP addresses against IP address
 244           ranges.
 245
 246           To compile it as a module, choose M here.  If unsure, say N.
 247
 248 config IP_NF_MATCH_TOS
 249         tristate "TOS match support"
 250         depends on IP_NF_IPTABLES
 251         help
 252           TOS matching allows you to match packets based on the Type Of
 253           Service fields of the IP packet.
 254
 255           To compile it as a module, choose M here.  If unsure, say N.
 256
 257 config IP_NF_MATCH_RECENT
 258         tristate "recent match support"
 259         depends on IP_NF_IPTABLES
 260         help
 261           This match is used for creating one or many lists of recently
 262           used addresses and then matching against that/those list(s).
 263
 264           Short options are available by using 'iptables -m recent -h'
 265           Official Website: <http://snowman.net/projects/ipt_recent/>
 266
 267           To compile it as a module, choose M here.  If unsure, say N.
 268
 269 config IP_NF_MATCH_ECN
 270         tristate "ECN match support"
 271         depends on IP_NF_IPTABLES
 272         help
 273           This option adds a `ECN' match, which allows you to match against
 274           the IPv4 and TCP header ECN fields.
 275
 276           To compile it as a module, choose M here.  If unsure, say N.
 277
 278 config IP_NF_MATCH_AH
 279         tristate "AH match support"
 280         depends on IP_NF_IPTABLES
 281         help
 282           This match extension allows you to match a range of SPIs
 283           inside AH header of IPSec packets.
 284
 285           To compile it as a module, choose M here.  If unsure, say N.
 286
 287 config IP_NF_MATCH_TTL
 288         tristate "TTL match support"
 289         depends on IP_NF_IPTABLES
 290         help
 291           This adds CONFIG_IP_NF_MATCH_TTL option, which enabled the user
 292           to match packets by their TTL value.
 293
 294           To compile it as a module, choose M here.  If unsure, say N.
 295
 296 config IP_NF_MATCH_OWNER
 297         tristate "Owner match support"
 298         depends on IP_NF_IPTABLES
 299         help
 300           Packet owner matching allows you to match locally-generated packets
 301           based on who created them: the user, group, process or session.
 302
 303           To compile it as a module, choose M here.  If unsure, say N.
 304
 305 config IP_NF_MATCH_ADDRTYPE
 306         tristate  'address type match support'
 307         depends on IP_NF_IPTABLES
 308         help
 309           This option allows you to match what routing thinks of an address,
 310           eg. UNICAST, LOCAL, BROADCAST, ...
 311
 312           If you want to compile it as a module, say M here and read
 313           <file:Documentation/modules.txt>.  If unsure, say `N'.
 314
 315 # `filter', generic and specific targets
 316 config IP_NF_FILTER
 317         tristate "Packet filtering"
 318         depends on IP_NF_IPTABLES
 319         help
 320           Packet filtering defines a table `filter', which has a series of
 321           rules for simple packet filtering at local input, forwarding and
 322           local output.  See the man page for iptables(8).
 323
 324           To compile it as a module, choose M here.  If unsure, say N.
 325
 326 config IP_NF_TARGET_REJECT
 327         tristate "REJECT target support"
 328         depends on IP_NF_FILTER
 329         help
 330           The REJECT target allows a filtering rule to specify that an ICMP
 331           error should be issued in response to an incoming packet, rather
 332           than silently being dropped.
 333
 334           To compile it as a module, choose M here.  If unsure, say N.
 335
 336 config IP_NF_TARGET_LOG
 337         tristate "LOG target support"
 338         depends on IP_NF_IPTABLES
 339         help
 340           This option adds a `LOG' target, which allows you to create rules in
 341           any iptables table which records the packet header to the syslog.
 342
 343           To compile it as a module, choose M here.  If unsure, say N.
 344
 345 config IP_NF_TARGET_ULOG
 346         tristate "ULOG target support"
 347         depends on IP_NF_IPTABLES
 348         ---help---
 349
 350           This option enables the old IPv4-only "ipt_ULOG" implementation
 351           which has been obsoleted by the new "nfnetlink_log" code (see
 352           CONFIG_NETFILTER_NETLINK_LOG).
 353
 354           This option adds a `ULOG' target, which allows you to create rules in
 355           any iptables table. The packet is passed to a userspace logging
 356           daemon using netlink multicast sockets; unlike the LOG target
 357           which can only be viewed through syslog.
 358
 359           The appropriate userspace logging daemon (ulogd) may be obtained from
 360           <http://www.gnumonks.org/projects/ulogd/>
 361
 362           To compile it as a module, choose M here.  If unsure, say N.
 363
 364 config IP_NF_TARGET_TCPMSS
 365         tristate "TCPMSS target support"
 366         depends on IP_NF_IPTABLES
 367         ---help---
 368           This option adds a `TCPMSS' target, which allows you to alter the
 369           MSS value of TCP SYN packets, to control the maximum size for that
 370           connection (usually limiting it to your outgoing interface's MTU
 371           minus 40).
 372
 373           This is used to overcome criminally braindead ISPs or servers which
 374           block ICMP Fragmentation Needed packets.  The symptoms of this
 375           problem are that everything works fine from your Linux
 376           firewall/router, but machines behind it can never exchange large
 377           packets:
 378                 1) Web browsers connect, then hang with no data received.
 379                 2) Small mail works fine, but large emails hang.
 380                 3) ssh works fine, but scp hangs after initial handshaking.
 381
 382           Workaround: activate this option and add a rule to your firewall
 383           configuration like:
 384
 385           iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
 386                          -j TCPMSS --clamp-mss-to-pmtu
 387
 388           To compile it as a module, choose M here.  If unsure, say N.
 389
 390 # NAT + specific targets: ip_conntrack
 391 config IP_NF_NAT
 392         tristate "Full NAT"
 393         depends on IP_NF_IPTABLES && IP_NF_CONNTRACK
 394         help
 395           The Full NAT option allows masquerading, port forwarding and other
 396           forms of full Network Address Port Translation.  It is controlled by
 397           the `nat' table in iptables: see the man page for iptables(8).
 398
 399           To compile it as a module, choose M here.  If unsure, say N.
 400
 401 # NAT + specific targets: nf_conntrack
 402 config NF_NAT
 403         tristate "Full NAT"
 404         depends on IP_NF_IPTABLES && NF_CONNTRACK
 405         help
 406           The Full NAT option allows masquerading, port forwarding and other
 407           forms of full Network Address Port Translation.  It is controlled by
 408           the `nat' table in iptables: see the man page for iptables(8).
 409
 410           To compile it as a module, choose M here.  If unsure, say N.
 411
 412 config IP_NF_NAT_NEEDED
 413         bool
 414         depends on IP_NF_NAT
 415         default y
 416
 417 config NF_NAT_NEEDED
 418         bool
 419         depends on NF_NAT
 420         default y
 421
 422 config IP_NF_TARGET_MASQUERADE
 423         tristate "MASQUERADE target support"
 424         depends on (NF_NAT || IP_NF_NAT)
 425         help
 426           Masquerading is a special case of NAT: all outgoing connections are
 427           changed to seem to come from a particular interface's address, and
 428           if the interface goes down, those connections are lost.  This is
 429           only useful for dialup accounts with dynamic IP address (ie. your IP
 430           address will be different on next dialup).
 431
 432           To compile it as a module, choose M here.  If unsure, say N.
 433
 434 config IP_NF_TARGET_REDIRECT
 435         tristate "REDIRECT target support"
 436         depends on (NF_NAT || IP_NF_NAT)
 437         help
 438           REDIRECT is a special case of NAT: all incoming connections are
 439           mapped onto the incoming interface's address, causing the packets to
 440           come to the local machine instead of passing through.  This is
 441           useful for transparent proxies.
 442
 443           To compile it as a module, choose M here.  If unsure, say N.
 444
 445 config IP_NF_TARGET_NETMAP
 446         tristate "NETMAP target support"
 447         depends on (NF_NAT || IP_NF_NAT)
 448         help
 449           NETMAP is an implementation of static 1:1 NAT mapping of network
 450           addresses. It maps the network address part, while keeping the host
 451           address part intact. It is similar to Fast NAT, except that
 452           Netfilter's connection tracking doesn't work well with Fast NAT.
 453
 454           To compile it as a module, choose M here.  If unsure, say N.
 455
 456 config IP_NF_TARGET_SAME
 457         tristate "SAME target support"
 458         depends on (NF_NAT || IP_NF_NAT)
 459         help
 460           This option adds a `SAME' target, which works like the standard SNAT
 461           target, but attempts to give clients the same IP for all connections.
 462
 463           To compile it as a module, choose M here.  If unsure, say N.
 464
 465 config IP_NF_NAT_SNMP_BASIC
 466         tristate "Basic SNMP-ALG support (EXPERIMENTAL)"
 467         depends on EXPERIMENTAL && IP_NF_NAT
 468         ---help---
 469
 470           This module implements an Application Layer Gateway (ALG) for
 471           SNMP payloads.  In conjunction with NAT, it allows a network
 472           management system to access multiple private networks with
 473           conflicting addresses.  It works by modifying IP addresses
 474           inside SNMP payloads to match IP-layer NAT mapping.
 475
 476           This is the "basic" form of SNMP-ALG, as described in RFC 2962
 477
 478           To compile it as a module, choose M here.  If unsure, say N.
 479
 480 # If they want FTP, set to $CONFIG_IP_NF_NAT (m or y),
 481 # or $CONFIG_IP_NF_FTP (m or y), whichever is weaker.
 482 # From kconfig-language.txt:
 483 #
 484 #           <expr> '&&' <expr>                   (6)
 485 #
 486 # (6) Returns the result of min(/expr/, /expr/).
 487 config NF_NAT_PROTO_GRE
 488         tristate
 489         depends on NF_NAT && NF_CT_PROTO_GRE
 490
 491 config IP_NF_NAT_FTP
 492         tristate
 493         depends on IP_NF_IPTABLES && IP_NF_CONNTRACK && IP_NF_NAT
 494         default IP_NF_NAT && IP_NF_FTP
 495
 496 config NF_NAT_FTP
 497         tristate
 498         depends on IP_NF_IPTABLES && NF_CONNTRACK && NF_NAT
 499         default NF_NAT && NF_CONNTRACK_FTP
 500
 501 config IP_NF_NAT_IRC
 502         tristate
 503         depends on IP_NF_IPTABLES!=n && IP_NF_CONNTRACK!=n && IP_NF_NAT!=n
 504         default IP_NF_NAT if IP_NF_IRC=y
 505         default m if IP_NF_IRC=m
 506
 507 config NF_NAT_IRC
 508         tristate
 509         depends on IP_NF_IPTABLES && NF_CONNTRACK && NF_NAT
 510         default NF_NAT && NF_CONNTRACK_IRC
 511
 512 config IP_NF_NAT_TFTP
 513         tristate
 514         depends on IP_NF_IPTABLES!=n && IP_NF_CONNTRACK!=n && IP_NF_NAT!=n
 515         default IP_NF_NAT if IP_NF_TFTP=y
 516         default m if IP_NF_TFTP=m
 517
 518 config IP_NF_NAT_AMANDA
 519         tristate
 520         depends on IP_NF_IPTABLES!=n && IP_NF_CONNTRACK!=n && IP_NF_NAT!=n
 521         default IP_NF_NAT if IP_NF_AMANDA=y
 522         default m if IP_NF_AMANDA=m
 523
 524 config NF_NAT_AMANDA
 525         tristate
 526         depends on IP_NF_IPTABLES && NF_CONNTRACK && NF_NAT
 527         default NF_NAT && NF_CONNTRACK_AMANDA
 528
 529 config IP_NF_NAT_PPTP
 530         tristate
 531         depends on IP_NF_NAT!=n && IP_NF_PPTP!=n
 532         default IP_NF_NAT if IP_NF_PPTP=y
 533         default m if IP_NF_PPTP=m
 534
 535 config NF_NAT_PPTP
 536         tristate
 537         depends on IP_NF_IPTABLES && NF_CONNTRACK && NF_NAT
 538         default NF_NAT && NF_CONNTRACK_PPTP
 539         select NF_NAT_PROTO_GRE
 540
 541 config IP_NF_NAT_H323
 542         tristate
 543         depends on IP_NF_IPTABLES!=n && IP_NF_CONNTRACK!=n && IP_NF_NAT!=n
 544         default IP_NF_NAT if IP_NF_H323=y
 545         default m if IP_NF_H323=m
 546
 547 config NF_NAT_H323
 548         tristate
 549         depends on IP_NF_IPTABLES && NF_CONNTRACK && NF_NAT
 550         default NF_NAT && NF_CONNTRACK_H323
 551
 552 config IP_NF_NAT_SIP
 553         tristate
 554         depends on IP_NF_IPTABLES!=n && IP_NF_CONNTRACK!=n && IP_NF_NAT!=n
 555         default IP_NF_NAT if IP_NF_SIP=y
 556         default m if IP_NF_SIP=m
 557
 558 config NF_NAT_SIP
 559         tristate
 560         depends on IP_NF_IPTABLES && NF_CONNTRACK && NF_NAT
 561         default NF_NAT && NF_CONNTRACK_SIP
 562
 563 # mangle + specific targets
 564 config IP_NF_MANGLE
 565         tristate "Packet mangling"
 566         depends on IP_NF_IPTABLES
 567         help
 568           This option adds a `mangle' table to iptables: see the man page for
 569           iptables(8).  This table is used for various packet alterations
 570           which can effect how the packet is routed.
 571
 572           To compile it as a module, choose M here.  If unsure, say N.
 573
 574 config IP_NF_TARGET_TOS
 575         tristate "TOS target support"
 576         depends on IP_NF_MANGLE
 577         help
 578           This option adds a `TOS' target, which allows you to create rules in
 579           the `mangle' table which alter the Type Of Service field of an IP
 580           packet prior to routing.
 581
 582           To compile it as a module, choose M here.  If unsure, say N.
 583
 584 config IP_NF_TARGET_ECN
 585         tristate "ECN target support"
 586         depends on IP_NF_MANGLE
 587         ---help---
 588           This option adds a `ECN' target, which can be used in the iptables mangle
 589           table.
 590
 591           You can use this target to remove the ECN bits from the IPv4 header of
 592           an IP packet.  This is particularly useful, if you need to work around
 593           existing ECN blackholes on the internet, but don't want to disable
 594           ECN support in general.
 595
 596           To compile it as a module, choose M here.  If unsure, say N.
 597
 598 config IP_NF_TARGET_TTL
 599         tristate  'TTL target support'
 600         depends on IP_NF_MANGLE
 601         help
 602           This option adds a `TTL' target, which enables the user to modify
 603           the TTL value of the IP header.
 604
 605           While it is safe to decrement/lower the TTL, this target also enables
 606           functionality to increment and set the TTL value of the IP header to
 607           arbitrary values.  This is EXTREMELY DANGEROUS since you can easily
 608           create immortal packets that loop forever on the network.
 609
 610           To compile it as a module, choose M here.  If unsure, say N.
 611
 612 config IP_NF_TARGET_CLUSTERIP
 613         tristate "CLUSTERIP target support (EXPERIMENTAL)"
 614         depends on IP_NF_MANGLE && EXPERIMENTAL
 615         depends on (IP_NF_CONNTRACK && IP_NF_CONNTRACK_MARK) || (NF_CONNTRACK_MARK && NF_CONNTRACK_IPV4)
 616         help
 617           The CLUSTERIP target allows you to build load-balancing clusters of
 618           network servers without having a dedicated load-balancing
 619           router/server/switch.
 620
 621           To compile it as a module, choose M here.  If unsure, say N.
 622
 623 # raw + specific targets
 624 config IP_NF_RAW
 625         tristate  'raw table support (required for NOTRACK/TRACE)'
 626         depends on IP_NF_IPTABLES
 627         help
 628           This option adds a `raw' table to iptables. This table is the very
 629           first in the netfilter framework and hooks in at the PREROUTING
 630           and OUTPUT chains.
 631
 632           If you want to compile it as a module, say M here and read
 633           <file:Documentation/modules.txt>.  If unsure, say `N'.
 634
 635 # ARP tables
 636 config IP_NF_ARPTABLES
 637         tristate "ARP tables support"
 638         depends on NETFILTER_XTABLES
 639         help
 640           arptables is a general, extensible packet identification framework.
 641           The ARP packet filtering and mangling (manipulation)subsystems
 642           use this: say Y or M here if you want to use either of those.
 643
 644           To compile it as a module, choose M here.  If unsure, say N.
 645
 646 config IP_NF_ARPFILTER
 647         tristate "ARP packet filtering"
 648         depends on IP_NF_ARPTABLES
 649         help
 650           ARP packet filtering defines a table `filter', which has a series of
 651           rules for simple ARP packet filtering at local input and
 652           local output.  On a bridge, you can also specify filtering rules
 653           for forwarded ARP packets. See the man page for arptables(8).
 654
 655           To compile it as a module, choose M here.  If unsure, say N.
 656
 657 config IP_NF_ARP_MANGLE
 658         tristate "ARP payload mangling"
 659         depends on IP_NF_ARPTABLES
 660         help
 661           Allows altering the ARP packet payload: source and destination
 662           hardware and network addresses.
 663
 664 endmenu
 665