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