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