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