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