Kconfig 50.2 KB
Newer Older
1
menu "Core Netfilter Configuration"
2
	depends on NET && INET && NETFILTER
3

4 5
config NETFILTER_INGRESS
	bool "Netfilter ingress support"
6
	default y
7 8 9 10 11
	select NET_INGRESS
	help
	  This allows you to classify packets from ingress using the Netfilter
	  infrastructure.

H
Harald Welte 已提交
12
config NETFILTER_NETLINK
13
	tristate
14

15 16 17 18 19 20
config NETFILTER_FAMILY_BRIDGE
	bool

config NETFILTER_FAMILY_ARP
	bool

21 22 23 24 25 26 27 28
config NETFILTER_NETLINK_ACCT
tristate "Netfilter NFACCT over NFNETLINK interface"
	depends on NETFILTER_ADVANCED
	select NETFILTER_NETLINK
	help
	  If this option is enabled, the kernel will include support
	  for extended accounting via NFNETLINK.

29 30
config NETFILTER_NETLINK_QUEUE
	tristate "Netfilter NFQUEUE over NFNETLINK interface"
31
	depends on NETFILTER_ADVANCED
32
	select NETFILTER_NETLINK
33
	help
T
Thomas Vgtle 已提交
34
	  If this option is enabled, the kernel will include support
35 36
	  for queueing packets via NFNETLINK.
	  
37 38
config NETFILTER_NETLINK_LOG
	tristate "Netfilter LOG over NFNETLINK interface"
39
	default m if NETFILTER_ADVANCED=n
40
	select NETFILTER_NETLINK
41 42 43 44 45 46 47 48
	help
	  If this option is enabled, the kernel will include support
	  for logging packets via NFNETLINK.

	  This obsoletes the existing ipt_ULOG and ebg_ulog mechanisms,
	  and is also scheduled to replace the old syslog-based ipt_LOG
	  and ip6t_LOG modules.

49
config NF_CONNTRACK
50
	tristate "Netfilter connection tracking support"
51
	default m if NETFILTER_ADVANCED=n
52
	help
53 54 55 56
	  Connection tracking keeps a record of what packets have passed
	  through your machine, in order to figure out how they are related
	  into connections.

57
	  This is required to do Masquerading or other kinds of Network
58 59
	  Address Translation.  It can also be used to enhance packet
	  filtering (see `Connection state match support' below).
60 61 62

	  To compile it as a module, choose M here.  If unsure, say N.

63 64 65
config NF_LOG_COMMON
	tristate

66 67 68 69
config NF_LOG_NETDEV
	tristate "Netdev packet logging"
	select NF_LOG_COMMON

70
if NF_CONNTRACK
71 72
config NETFILTER_CONNCOUNT
	tristate
73

74 75
config NF_CONNTRACK_MARK
	bool  'Connection mark tracking support'
76
	depends on NETFILTER_ADVANCED
77 78 79 80 81 82
	help
	  This option enables support for connection marks, used by the
	  `CONNMARK' target and `connmark' match. Similar to the mark value
	  of packets, but this mark value is kept in the conntrack session
	  instead of the individual packets.

83 84
config NF_CONNTRACK_SECMARK
	bool  'Connection tracking security mark support'
85
	depends on NETWORK_SECMARK
86
	default m if NETFILTER_ADVANCED=n
87 88 89 90 91 92 93 94 95
	help
	  This option enables security markings to be applied to
	  connections.  Typically they are copied to connections from
	  packets using the CONNSECMARK target and copied back from
	  connections to packets with the same target, with the packets
	  being originally labeled via SECMARK.

	  If unsure, say 'N'.

96 97 98 99 100 101 102 103 104 105 106 107 108
config NF_CONNTRACK_ZONES
	bool  'Connection tracking zones'
	depends on NETFILTER_ADVANCED
	depends on NETFILTER_XT_TARGET_CT
	help
	  This option enables support for connection tracking zones.
	  Normally, each connection needs to have a unique system wide
	  identity. Connection tracking zones allow to have multiple
	  connections using the same identity, as long as they are
	  contained in different zones.

	  If unsure, say `N'.

109 110 111 112 113 114 115 116 117 118
config NF_CONNTRACK_PROCFS
	bool "Supply CT list in procfs (OBSOLETE)"
	default y
	depends on PROC_FS
	---help---
	This option enables for the list of known conntrack entries
	to be shown in procfs under net/netfilter/nf_conntrack. This
	is considered obsolete in favor of using the conntrack(8)
	tool which uses Netlink.

119
config NF_CONNTRACK_EVENTS
120
	bool "Connection tracking events"
121
	depends on NETFILTER_ADVANCED
122 123 124
	help
	  If this option is enabled, the connection tracking code will
	  provide a notifier chain that can be used by other kernel code
T
Thomas Vgtle 已提交
125
	  to get notified about changes in the connection tracking state.
126 127 128

	  If unsure, say `N'.

129 130 131 132 133 134 135 136 137 138
config NF_CONNTRACK_TIMEOUT
	bool  'Connection tracking timeout'
	depends on NETFILTER_ADVANCED
	help
	  This option enables support for connection tracking timeout
	  extension. This allows you to attach timeout policies to flow
	  via the CT target.

	  If unsure, say `N'.

139 140 141 142 143 144 145 146 147 148 149
config NF_CONNTRACK_TIMESTAMP
	bool  'Connection tracking timestamping'
	depends on NETFILTER_ADVANCED
	help
	  This option enables support for connection tracking timestamping.
	  This allows you to store the flow start-time and to obtain
	  the flow-stop time (once it has been destroyed) via Connection
	  tracking events.

	  If unsure, say `N'.

150 151 152 153 154 155
config NF_CONNTRACK_LABELS
	bool
	help
	  This option enables support for assigning user-defined flag bits
	  to connection tracking entries.  It selected by the connlabel match.

156
config NF_CT_PROTO_DCCP
157
	bool 'DCCP protocol connection tracking support'
158
	depends on NETFILTER_ADVANCED
159
	default y
160 161 162 163
	help
	  With this option enabled, the layer 3 independent connection
	  tracking code will be able to do state tracking on DCCP connections.

164
	  If unsure, say Y.
165

166 167 168
config NF_CT_PROTO_GRE
	tristate

169
config NF_CT_PROTO_SCTP
170
	bool 'SCTP protocol connection tracking support'
171
	depends on NETFILTER_ADVANCED
172
	default y
173
	select LIBCRC32C
174 175 176 177
	help
	  With this option enabled, the layer 3 independent connection
	  tracking code will be able to do state tracking on SCTP connections.

178
	  If unsure, say Y.
179

180
config NF_CT_PROTO_UDPLITE
181
	bool 'UDP-Lite protocol connection tracking support'
182
	depends on NETFILTER_ADVANCED
183
	default y
184 185 186 187 188
	help
	  With this option enabled, the layer 3 independent connection
	  tracking code will be able to do state tracking on UDP-Lite
	  connections.

189
	  If unsure, say Y.
190

191
config NF_CONNTRACK_AMANDA
192
	tristate "Amanda backup protocol support"
193
	depends on NETFILTER_ADVANCED
194 195 196 197 198 199 200 201 202 203 204 205
	select TEXTSEARCH
	select TEXTSEARCH_KMP
	help
	  If you are running the Amanda backup package <http://www.amanda.org/>
	  on this machine or machines that will be MASQUERADED through this
	  machine, then you may want to enable this feature.  This allows the
	  connection tracking and natting code to allow the sub-channels that
	  Amanda requires for communication of the backup data, messages and
	  index.

	  To compile it as a module, choose M here.  If unsure, say N.

206
config NF_CONNTRACK_FTP
207
	tristate "FTP protocol support"
208
	default m if NETFILTER_ADVANCED=n
209 210 211 212 213 214 215 216 217 218 219
	help
	  Tracking FTP connections is problematic: special helpers are
	  required for tracking them, and doing masquerading and other forms
	  of Network Address Translation on them.

	  This is FTP support on Layer 3 independent connection tracking.
	  Layer 3 independent connection tracking is experimental scheme
	  which generalize ip_conntrack to support other layer 3 protocols.

	  To compile it as a module, choose M here.  If unsure, say N.

220
config NF_CONNTRACK_H323
221
	tristate "H.323 protocol support"
222
	depends on IPV6 || IPV6=n
223
	depends on NETFILTER_ADVANCED
224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239
	help
	  H.323 is a VoIP signalling protocol from ITU-T. As one of the most
	  important VoIP protocols, it is widely used by voice hardware and
	  software including voice gateways, IP phones, Netmeeting, OpenPhone,
	  Gnomemeeting, etc.

	  With this module you can support H.323 on a connection tracking/NAT
	  firewall.

	  This module supports RAS, Fast Start, H.245 Tunnelling, Call
	  Forwarding, RTP/RTCP and T.120 based audio, video, fax, chat,
	  whiteboard, file transfer, etc. For more information, please
	  visit http://nath323.sourceforge.net/.

	  To compile it as a module, choose M here.  If unsure, say N.

240
config NF_CONNTRACK_IRC
241
	tristate "IRC protocol support"
242
	default m if NETFILTER_ADVANCED=n
243 244 245 246 247 248 249 250 251 252 253 254
	help
	  There is a commonly-used extension to IRC called
	  Direct Client-to-Client Protocol (DCC).  This enables users to send
	  files to each other, and also chat to each other without the need
	  of a server.  DCC Sending is used anywhere you send files over IRC,
	  and DCC Chat is most commonly used by Eggdrop bots.  If you are
	  using NAT, this extension will enable you to send files and initiate
	  chats.  Note that you do NOT need this extension to get files or
	  have others initiate chats, or everything else in IRC.

	  To compile it as a module, choose M here.  If unsure, say N.

255 256 257
config NF_CONNTRACK_BROADCAST
	tristate

258
config NF_CONNTRACK_NETBIOS_NS
259
	tristate "NetBIOS name service protocol support"
260
	select NF_CONNTRACK_BROADCAST
261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276
	help
	  NetBIOS name service requests are sent as broadcast messages from an
	  unprivileged port and responded to with unicast messages to the
	  same port. This make them hard to firewall properly because connection
	  tracking doesn't deal with broadcasts. This helper tracks locally
	  originating NetBIOS name service requests and the corresponding
	  responses. It relies on correct IP address configuration, specifically
	  netmask and broadcast address. When properly configured, the output
	  of "ip address show" should look similar to this:

	  $ ip -4 address show eth0
	  4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
	      inet 172.16.2.252/24 brd 172.16.2.255 scope global eth0

	  To compile it as a module, choose M here.  If unsure, say N.

277 278 279 280 281 282 283 284 285 286 287 288 289 290 291
config NF_CONNTRACK_SNMP
	tristate "SNMP service protocol support"
	depends on NETFILTER_ADVANCED
	select NF_CONNTRACK_BROADCAST
	help
	  SNMP service requests are sent as broadcast messages from an
	  unprivileged port and responded to with unicast messages to the
	  same port. This make them hard to firewall properly because connection
	  tracking doesn't deal with broadcasts. This helper tracks locally
	  originating SNMP service requests and the corresponding
	  responses. It relies on correct IP address configuration, specifically
	  netmask and broadcast address.

	  To compile it as a module, choose M here.  If unsure, say N.

292
config NF_CONNTRACK_PPTP
293
	tristate "PPtP protocol support"
294
	depends on NETFILTER_ADVANCED
295 296 297 298 299 300 301 302 303 304
	select NF_CT_PROTO_GRE
	help
	  This module adds support for PPTP (Point to Point Tunnelling
	  Protocol, RFC2637) connection tracking and NAT.

	  If you are running PPTP sessions over a stateful firewall or NAT
	  box, you may want to enable this feature.

	  Please note that not all PPTP modes of operation are supported yet.
	  Specifically these limitations exist:
305
	    - Blindly assumes that control connections are always established
306 307 308 309 310
	      in PNS->PAC direction. This is a violation of RFC2637.
	    - Only supports a single call within each session

	  To compile it as a module, choose M here.  If unsure, say N.

311
config NF_CONNTRACK_SANE
312
	tristate "SANE protocol support"
313
	depends on NETFILTER_ADVANCED
314 315 316 317 318 319 320 321 322 323
	help
	  SANE is a protocol for remote access to scanners as implemented
	  by the 'saned' daemon. Like FTP, it uses separate control and
	  data connections.

	  With this module you can support SANE on a connection tracking
	  firewall.

	  To compile it as a module, choose M here.  If unsure, say N.

324
config NF_CONNTRACK_SIP
325
	tristate "SIP protocol support"
326
	default m if NETFILTER_ADVANCED=n
327 328 329 330 331 332 333 334 335
	help
	  SIP is an application-layer control protocol that can establish,
	  modify, and terminate multimedia sessions (conferences) such as
	  Internet telephony calls. With the ip_conntrack_sip and
	  the nf_nat_sip modules you can support the protocol on a connection
	  tracking/NATing firewall.

	  To compile it as a module, choose M here.  If unsure, say N.

336
config NF_CONNTRACK_TFTP
337
	tristate "TFTP protocol support"
338
	depends on NETFILTER_ADVANCED
339 340 341 342 343 344 345 346
	help
	  TFTP connection tracking helper, this is required depending
	  on how restrictive your ruleset is.
	  If you are using a tftp client behind -j SNAT or -j MASQUERADING
	  you will need this.

	  To compile it as a module, choose M here.  If unsure, say N.

347
config NF_CT_NETLINK
348
	tristate 'Connection tracking netlink interface'
349
	select NETFILTER_NETLINK
350
	default m if NETFILTER_ADVANCED=n
351 352 353
	help
	  This option enables support for a netlink-based userspace interface

354 355 356 357 358 359 360 361 362 363 364
config NF_CT_NETLINK_TIMEOUT
	tristate  'Connection tracking timeout tuning via Netlink'
	select NETFILTER_NETLINK
	depends on NETFILTER_ADVANCED
	help
	  This option enables support for connection tracking timeout
	  fine-grain tuning. This allows you to attach specific timeout
	  policies to flows, instead of using the global timeout policy.

	  If unsure, say `N'.

365 366 367 368 369
config NF_CT_NETLINK_HELPER
	tristate 'Connection tracking helpers in user-space via Netlink'
	select NETFILTER_NETLINK
	depends on NF_CT_NETLINK
	depends on NETFILTER_NETLINK_QUEUE
370
	depends on NETFILTER_NETLINK_GLUE_CT
371 372 373 374 375 376 377
	depends on NETFILTER_ADVANCED
	help
	  This option enables the user-space connection tracking helpers
	  infrastructure.

	  If unsure, say `N'.

378
config NETFILTER_NETLINK_GLUE_CT
379
	bool "NFQUEUE and NFLOG integration with Connection Tracking"
380
	default n
381
	depends on (NETFILTER_NETLINK_QUEUE || NETFILTER_NETLINK_LOG) && NF_CT_NETLINK
382
	help
383 384 385
	  If this option is enabled, NFQUEUE and NFLOG can include
	  Connection Tracking information together with the packet is
	  the enqueued via NFNETLINK.
386

387 388 389 390 391 392 393 394 395
config NF_NAT
	tristate

config NF_NAT_NEEDED
	bool
	depends on NF_NAT
	default y

config NF_NAT_PROTO_DCCP
396
	bool
397 398 399 400
	depends on NF_NAT && NF_CT_PROTO_DCCP
	default NF_NAT && NF_CT_PROTO_DCCP

config NF_NAT_PROTO_UDPLITE
401
	bool
402 403 404 405
	depends on NF_NAT && NF_CT_PROTO_UDPLITE
	default NF_NAT && NF_CT_PROTO_UDPLITE

config NF_NAT_PROTO_SCTP
406
	bool
407 408 409
	default NF_NAT && NF_CT_PROTO_SCTP
	depends on NF_NAT && NF_CT_PROTO_SCTP

410 411 412 413 414
config NF_NAT_AMANDA
	tristate
	depends on NF_CONNTRACK && NF_NAT
	default NF_NAT && NF_CONNTRACK_AMANDA

415 416 417 418 419
config NF_NAT_FTP
	tristate
	depends on NF_CONNTRACK && NF_NAT
	default NF_NAT && NF_CONNTRACK_FTP

420 421 422 423 424
config NF_NAT_IRC
	tristate
	depends on NF_CONNTRACK && NF_NAT
	default NF_NAT && NF_CONNTRACK_IRC

425 426 427 428 429
config NF_NAT_SIP
	tristate
	depends on NF_CONNTRACK && NF_NAT
	default NF_NAT && NF_CONNTRACK_SIP

430 431 432 433 434
config NF_NAT_TFTP
	tristate
	depends on NF_CONNTRACK && NF_NAT
	default NF_NAT && NF_CONNTRACK_TFTP

435
config NF_NAT_REDIRECT
436
	bool
437

438 439 440
config NETFILTER_SYNPROXY
	tristate

441 442
endif # NF_CONNTRACK

443
config NF_OSF
444
	tristate
445

P
Patrick McHardy 已提交
446
config NF_TABLES
447
	select NETFILTER_NETLINK
P
Patrick McHardy 已提交
448
	tristate "Netfilter nf_tables support"
449 450 451 452 453 454 455 456 457 458 459
	help
	  nftables is the new packet classification framework that intends to
	  replace the existing {ip,ip6,arp,eb}_tables infrastructure. It
	  provides a pseudo-state machine with an extensible instruction-set
	  (also known as expressions) that the userspace 'nft' utility
	  (http://www.netfilter.org/projects/nftables) uses to build the
	  rule-set. It also comes with the generic set infrastructure that
	  allows you to construct mappings between matchings and actions
	  for performance lookups.

	  To compile it as a module, choose M here.
P
Patrick McHardy 已提交
460

461 462
if NF_TABLES

463
config NF_TABLES_INET
464
	depends on IPV6
465 466
	select NF_TABLES_IPV4
	select NF_TABLES_IPV6
467
	bool "Netfilter nf_tables mixed IPv4/IPv6 tables support"
468 469 470
	help
	  This option enables support for a mixed IPv4/IPv6 "inet" table.

471
config NF_TABLES_NETDEV
472
	bool "Netfilter nf_tables netdev tables support"
473 474 475
	help
	  This option enables support for the "netdev" table.

476 477 478 479 480 481
config NFT_NUMGEN
	tristate "Netfilter nf_tables number generator module"
	help
	  This option adds the number generator expression used to perform
	  incremental counting and random numbers bound to a upper limit.

P
Patrick McHardy 已提交
482 483 484
config NFT_CT
	depends on NF_CONNTRACK
	tristate "Netfilter nf_tables conntrack module"
485
	help
486
	  This option adds the "ct" expression that you can use to match
487
	  connection tracking information such as the flow state.
P
Patrick McHardy 已提交
488

489
config NFT_FLOW_OFFLOAD
490
	depends on NF_CONNTRACK && NF_FLOW_TABLE
491 492 493 494 495
	tristate "Netfilter nf_tables hardware flow offload module"
	help
	  This option adds the "flow_offload" expression that you can use to
	  choose what flows are placed into the hardware.

496
config NFT_SET_RBTREE
497
	tristate "Netfilter nf_tables rbtree set module"
498 499 500
	help
	  This option adds the "rbtree" set type (Red Black tree) that is used
	  to build interval-based sets.
P
Patrick McHardy 已提交
501

502
config NFT_SET_HASH
503
	tristate "Netfilter nf_tables hash set module"
504 505 506
	help
	  This option adds the "hash" set type that is used to build one-way
	  mappings between matchings and actions.
P
Patrick McHardy 已提交
507

508 509 510 511 512 513
config NFT_SET_BITMAP
	tristate "Netfilter nf_tables bitmap set module"
	help
	  This option adds the "bitmap" set type that is used to build sets
	  whose keys are smaller or equal to 16 bits.

P
Patrick McHardy 已提交
514 515
config NFT_COUNTER
	tristate "Netfilter nf_tables counter module"
516 517 518
	help
	  This option adds the "counter" expression that you can use to
	  include packet and byte counters in a rule.
P
Patrick McHardy 已提交
519 520 521

config NFT_LOG
	tristate "Netfilter nf_tables log module"
522 523 524
	help
	  This option adds the "log" expression that you can use to log
	  packets matching some criteria.
P
Patrick McHardy 已提交
525 526 527

config NFT_LIMIT
	tristate "Netfilter nf_tables limit module"
528 529 530
	help
	  This option adds the "limit" expression that you can use to
	  ratelimit rule matchings.
P
Patrick McHardy 已提交
531

532 533 534 535 536 537 538 539
config NFT_MASQ
	depends on NF_CONNTRACK
	depends on NF_NAT
	tristate "Netfilter nf_tables masquerade support"
	help
	  This option adds the "masquerade" expression that you can use
	  to perform NAT in the masquerade flavour.

540 541 542 543 544 545 546 547
config NFT_REDIR
	depends on NF_CONNTRACK
	depends on NF_NAT
	tristate "Netfilter nf_tables redirect support"
	help
	  This options adds the "redirect" expression that you can use
	  to perform NAT in the redirect flavour.

548 549
config NFT_NAT
	depends on NF_CONNTRACK
550
	select NF_NAT
551
	tristate "Netfilter nf_tables nat module"
552 553 554
	help
	  This option adds the "nat" expression that you can use to perform
	  typical Network Address Translation (NAT) packet transformations.
555

556 557 558 559 560 561
config NFT_OBJREF
	tristate "Netfilter nf_tables stateful object reference module"
	help
	  This option adds the "objref" expression that allows you to refer to
	  stateful objects, such as counters and quotas.

E
Eric Leblond 已提交
562 563 564 565 566 567 568
config NFT_QUEUE
	depends on NETFILTER_NETLINK_QUEUE
	tristate "Netfilter nf_tables queue module"
	help
	  This is required if you intend to use the userspace queueing
	  infrastructure (also known as NFQUEUE) from nftables.

569 570 571 572 573 574
config NFT_QUOTA
	tristate "Netfilter nf_tables quota module"
	help
	  This option adds the "quota" expression that you can use to match
	  enforce bytes quotas.

575 576 577
config NFT_REJECT
	default m if NETFILTER_ADVANCED=n
	tristate "Netfilter nf_tables reject support"
578
	depends on !NF_TABLES_INET || (IPV6!=m || m)
579 580 581 582
	help
	  This option adds the "reject" expression that you can use to
	  explicitly deny and notify via TCP reset/ICMP informational errors
	  unallowed traffic.
583

584 585 586 587 588
config NFT_REJECT_INET
	depends on NF_TABLES_INET
	default NFT_REJECT
	tristate

589 590 591 592 593 594 595 596
config NFT_COMPAT
	depends on NETFILTER_XTABLES
	tristate "Netfilter x_tables over nf_tables module"
	help
	  This is required if you intend to use any of existing
	  x_tables match/target extensions over the nf_tables
	  framework.

597 598 599 600 601 602
config NFT_HASH
	tristate "Netfilter nf_tables hash module"
	help
	  This option adds the "hash" expression that you can use to perform
	  a hash operation on registers.

603 604 605 606 607 608 609 610 611 612 613 614 615
config NFT_FIB
	tristate

config NFT_FIB_INET
	depends on NF_TABLES_INET
	depends on NFT_FIB_IPV4
	depends on NFT_FIB_IPV6
	tristate "Netfilter nf_tables fib inet support"
	help
	  This option allows using the FIB expression from the inet table.
	  The lookup will be delegated to the IPv4 or IPv6 FIB depending
	  on the protocol of the packet.

616 617 618 619 620 621 622 623 624
config NFT_SOCKET
	tristate "Netfilter nf_tables socket match support"
	depends on IPV6 || IPV6=n
	select NF_SOCKET_IPV4
	select NF_SOCKET_IPV6 if IPV6
	help
	  This option allows matching for the presence or absence of a
	  corresponding socket and its attributes.

625 626 627 628 629 630 631 632 633 634 635 636 637 638
if NF_TABLES_NETDEV

config NF_DUP_NETDEV
	tristate "Netfilter packet duplication support"
	help
	  This option enables the generic packet duplication infrastructure
	  for Netfilter.

config NFT_DUP_NETDEV
	tristate "Netfilter nf_tables netdev packet duplication support"
	select NF_DUP_NETDEV
	help
	  This option enables packet duplication for the "netdev" family.

639 640 641 642 643 644
config NFT_FWD_NETDEV
	tristate "Netfilter nf_tables netdev packet forwarding support"
	select NF_DUP_NETDEV
	help
	  This option enables packet forwarding for the "netdev" family.

645 646 647 648 649 650 651 652 653
config NFT_FIB_NETDEV
	depends on NFT_FIB_IPV4
	depends on NFT_FIB_IPV6
	tristate "Netfilter nf_tables netdev fib lookups support"
	help
	  This option allows using the FIB expression from the netdev table.
	  The lookup will be delegated to the IPv4 or IPv6 FIB depending
	  on the protocol of the packet.

654 655
endif # NF_TABLES_NETDEV

656 657
endif # NF_TABLES

658 659
config NF_FLOW_TABLE_INET
	tristate "Netfilter flow table mixed IPv4/IPv6 module"
660
	depends on NF_FLOW_TABLE
661 662 663 664 665
	help
          This option adds the flow table mixed IPv4/IPv6 support.

	  To compile it as a module, choose M here.

666 667
config NF_FLOW_TABLE
	tristate "Netfilter flow table module"
668 669 670
	depends on NETFILTER_INGRESS
	depends on NF_CONNTRACK
	depends on NF_TABLES
671 672 673 674 675
	help
	  This option adds the flow table core infrastructure.

	  To compile it as a module, choose M here.

676 677
config NETFILTER_XTABLES
	tristate "Netfilter Xtables support (required for ip_tables)"
678
	default m if NETFILTER_ADVANCED=n
679 680 681 682
	help
	  This is required if you intend to use any of ip_tables,
	  ip6_tables or arp_tables.

683 684
if NETFILTER_XTABLES

685 686 687 688 689 690 691 692 693 694 695 696 697
comment "Xtables combined modules"

config NETFILTER_XT_MARK
	tristate 'nfmark target and match support'
	default m if NETFILTER_ADVANCED=n
	---help---
	This option adds the "MARK" target and "mark" match.

	Netfilter mark matching allows you to match packets based on the
	"nfmark" value in the packet.
	The target allows you to create rules in the "mangle" table which alter
	the netfilter mark (nfmark) field associated with the packet.

698 699
	Prior to routing, the nfmark can influence the routing method and can
	also be used by other subsystems to change their behavior.
700

701 702 703 704 705 706 707 708 709 710 711 712
config NETFILTER_XT_CONNMARK
	tristate 'ctmark target and match support'
	depends on NF_CONNTRACK
	depends on NETFILTER_ADVANCED
	select NF_CONNTRACK_MARK
	---help---
	This option adds the "CONNMARK" target and "connmark" match.

	Netfilter allows you to store a mark value per connection (a.k.a.
	ctmark), similarly to the packet mark (nfmark). Using this
	target and match, you can set and match on this mark.

713 714 715 716 717 718 719 720 721 722 723 724
config NETFILTER_XT_SET
	tristate 'set target and match support'
	depends on IP_SET
	depends on NETFILTER_ADVANCED
	help
	  This option adds the "SET" target and "set" match.

	  Using this target and match, you can add/delete and match
	  elements in the sets created by ipset(8).

	  To compile it as a module, choose M here.  If unsure, say N.

725 726
# alphabetically ordered list of targets

727 728
comment "Xtables targets"

729 730 731 732 733 734 735 736 737 738
config NETFILTER_XT_TARGET_AUDIT
	tristate "AUDIT target support"
	depends on AUDIT
	depends on NETFILTER_ADVANCED
	---help---
	  This option adds a 'AUDIT' target, which can be used to create
	  audit records for packets dropped/accepted.

	  To compileit as a module, choose M here. If unsure, say N.

739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754
config NETFILTER_XT_TARGET_CHECKSUM
	tristate "CHECKSUM target support"
	depends on IP_NF_MANGLE || IP6_NF_MANGLE
	depends on NETFILTER_ADVANCED
	---help---
	  This option adds a `CHECKSUM' target, which can be used in the iptables mangle
	  table.

	  You can use this target to compute and fill in the checksum in
	  a packet that lacks a checksum.  This is particularly useful,
	  if you need to work around old applications such as dhcp clients,
	  that do not work well with checksum offloads, but don't want to disable
	  checksum offload in your device.

	  To compile it as a module, choose M here.  If unsure, say N.

755 756
config NETFILTER_XT_TARGET_CLASSIFY
	tristate '"CLASSIFY" target support'
757
	depends on NETFILTER_ADVANCED
758 759 760 761 762 763 764 765 766 767 768
	help
	  This option adds a `CLASSIFY' target, which enables the user to set
	  the priority of a packet. Some qdiscs can use this value for
	  classification, among these are:

  	  atm, cbq, dsmark, pfifo_fast, htb, prio

	  To compile it as a module, choose M here.  If unsure, say N.

config NETFILTER_XT_TARGET_CONNMARK
	tristate  '"CONNMARK" target support'
769
	depends on NF_CONNTRACK
770
	depends on NETFILTER_ADVANCED
771 772 773 774 775
	select NETFILTER_XT_CONNMARK
	---help---
	This is a backwards-compat option for the user's convenience
	(e.g. when running oldconfig). It selects
	CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
776

777 778
config NETFILTER_XT_TARGET_CONNSECMARK
	tristate '"CONNSECMARK" target support'
779
	depends on NF_CONNTRACK && NF_CONNTRACK_SECMARK
780 781 782 783 784 785 786 787 788
	default m if NETFILTER_ADVANCED=n
	help
	  The CONNSECMARK target copies security markings from packets
	  to connections, and restores security markings from connections
	  to packets (if the packets are not already marked).  This would
	  normally be used in conjunction with the SECMARK target.

	  To compile it as a module, choose M here.  If unsure, say N.

789 790 791 792 793 794 795 796 797 798 799 800
config NETFILTER_XT_TARGET_CT
	tristate '"CT" target support'
	depends on NF_CONNTRACK
	depends on IP_NF_RAW || IP6_NF_RAW
	depends on NETFILTER_ADVANCED
	help
	  This options adds a `CT' target, which allows to specify initial
	  connection tracking parameters like events to be delivered and
	  the helper to be used.

	  To compile it as a module, choose M here.  If unsure, say N.

801
config NETFILTER_XT_TARGET_DSCP
802
	tristate '"DSCP" and "TOS" target support'
803
	depends on IP_NF_MANGLE || IP6_NF_MANGLE
804
	depends on NETFILTER_ADVANCED
805 806 807 808 809 810
	help
	  This option adds a `DSCP' target, which allows you to manipulate
	  the IPv4/IPv6 header DSCP field (differentiated services codepoint).

	  The DSCP field can have any value between 0x0 and 0x3f inclusive.

811 812
	  It also adds the "TOS" target, which allows you to create rules in
	  the "mangle" table which alter the Type Of Service field of an IPv4
813
	  or the Priority field of an IPv6 packet, prior to routing.
814

815 816
	  To compile it as a module, choose M here.  If unsure, say N.

817 818 819 820 821 822 823 824 825 826 827 828 829 830 831
config NETFILTER_XT_TARGET_HL
	tristate '"HL" hoplimit target support'
	depends on IP_NF_MANGLE || IP6_NF_MANGLE
	depends on NETFILTER_ADVANCED
	---help---
	This option adds the "HL" (for IPv6) and "TTL" (for IPv4)
	targets, which enable the user to change the
	hoplimit/time-to-live value of the IP header.

	While it is safe to decrement the hoplimit/TTL value, the
	modules also allow to increment and set the hoplimit value of
	the header to arbitrary values. This is EXTREMELY DANGEROUS
	since you can easily create immortal packets that loop
	forever on the network.

832 833
config NETFILTER_XT_TARGET_HMARK
	tristate '"HMARK" target support'
834
	depends on IP6_NF_IPTABLES || IP6_NF_IPTABLES=n
835 836 837 838 839 840
	depends on NETFILTER_ADVANCED
	---help---
	This option adds the "HMARK" target.

	The target allows you to create rules in the "raw" and "mangle" tables
	which set the skbuff mark by means of hash calculation within a given
841 842
	range. The nfmark can influence the routing method and can also be used
	by other subsystems to change their behaviour.
843 844 845

	To compile it as a module, choose M here. If unsure, say N.

846 847 848 849 850 851 852 853 854 855 856 857
config NETFILTER_XT_TARGET_IDLETIMER
	tristate  "IDLETIMER target support"
	depends on NETFILTER_ADVANCED
	help

	  This option adds the `IDLETIMER' target.  Each matching packet
	  resets the timer associated with label specified when the rule is
	  added.  When the timer expires, it triggers a sysfs notification.
	  The remaining time for expiration can be read via sysfs.

	  To compile it as a module, choose M here.  If unsure, say N.

858 859
config NETFILTER_XT_TARGET_LED
	tristate '"LED" target support'
860
	depends on LEDS_CLASS && LEDS_TRIGGERS
861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879
	depends on NETFILTER_ADVANCED
	help
	  This option adds a `LED' target, which allows you to blink LEDs in
	  response to particular packets passing through your machine.

	  This can be used to turn a spare LED into a network activity LED,
	  which only flashes in response to FTP transfers, for example.  Or
	  you could have an LED which lights up for a minute or two every time
	  somebody connects to your machine via SSH.

	  You will need support for the "led" class to make this work.

	  To create an LED trigger for incoming SSH traffic:
	    iptables -A INPUT -p tcp --dport 22 -j LED --led-trigger-id ssh --led-delay 1000

	  Then attach the new trigger to an LED on your system:
	    echo netfilter-ssh > /sys/class/leds/<ledname>/trigger

	  For more information on the LEDs available on your system, see
P
Paul Bolle 已提交
880
	  Documentation/leds/leds-class.txt
881

882 883
config NETFILTER_XT_TARGET_LOG
	tristate "LOG target support"
884 885 886
	select NF_LOG_COMMON
	select NF_LOG_IPV4
	select NF_LOG_IPV6 if IPV6
887 888 889 890 891 892 893
	default m if NETFILTER_ADVANCED=n
	help
	  This option adds a `LOG' target, which allows you to create rules in
	  any iptables table which records the packet header to the syslog.

	  To compile it as a module, choose M here.  If unsure, say N.

894 895
config NETFILTER_XT_TARGET_MARK
	tristate '"MARK" target support'
896 897 898 899 900 901
	depends on NETFILTER_ADVANCED
	select NETFILTER_XT_MARK
	---help---
	This is a backwards-compat option for the user's convenience
	(e.g. when running oldconfig). It selects
	CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
902

903 904 905 906 907 908 909 910
config NETFILTER_XT_NAT
	tristate '"SNAT and DNAT" targets support'
	depends on NF_NAT
	---help---
	This option enables the SNAT and DNAT targets.

	To compile it as a module, choose M here. If unsure, say N.

911 912 913 914 915 916 917 918 919 920
config NETFILTER_XT_TARGET_NETMAP
	tristate '"NETMAP" target support'
	depends on NF_NAT
	---help---
	NETMAP is an implementation of static 1:1 NAT mapping of network
	addresses. It maps the network address part, while keeping the host
	address part intact.

	To compile it as a module, choose M here. If unsure, say N.

921 922
config NETFILTER_XT_TARGET_NFLOG
	tristate '"NFLOG" target support'
923
	default m if NETFILTER_ADVANCED=n
924
	select NETFILTER_NETLINK_LOG
925 926
	help
	  This option enables the NFLOG target, which allows to LOG
927
	  messages through nfnetlink_log.
928 929 930

	  To compile it as a module, choose M here.  If unsure, say N.

931 932 933
config NETFILTER_XT_TARGET_NFQUEUE
	tristate '"NFQUEUE" target Support'
	depends on NETFILTER_ADVANCED
934
	select NETFILTER_NETLINK_QUEUE
935 936 937 938 939 940 941 942
	help
	  This target replaced the old obsolete QUEUE target.

	  As opposed to QUEUE, it supports 65535 different queues,
	  not just one.

	  To compile it as a module, choose M here.  If unsure, say N.

943 944
config NETFILTER_XT_TARGET_NOTRACK
	tristate  '"NOTRACK" target support (DEPRECATED)'
945 946 947
	depends on NF_CONNTRACK
	depends on IP_NF_RAW || IP6_NF_RAW
	depends on NETFILTER_ADVANCED
948 949
	select NETFILTER_XT_TARGET_CT

950 951
config NETFILTER_XT_TARGET_RATEEST
	tristate '"RATEEST" target support'
952
	depends on NETFILTER_ADVANCED
953 954 955 956 957 958 959
	help
	  This option adds a `RATEEST' target, which allows to measure
	  rates similar to TC estimators. The `rateest' match can be
	  used to match on the measured rates.

	  To compile it as a module, choose M here.  If unsure, say N.

960 961 962
config NETFILTER_XT_TARGET_REDIRECT
	tristate "REDIRECT target support"
	depends on NF_NAT
963
	select NF_NAT_REDIRECT
964 965 966 967 968 969 970 971
	---help---
	REDIRECT is a special case of NAT: all incoming connections are
	mapped onto the incoming interface's address, causing the packets to
	come to the local machine instead of passing through. This is
	useful for transparent proxies.

	To compile it as a module, choose M here. If unsure, say N.

972
config NETFILTER_XT_TARGET_TEE
973
	tristate '"TEE" - packet cloning to alternate destination'
974
	depends on NETFILTER_ADVANCED
975
	depends on IPV6 || IPV6=n
976
	depends on !NF_CONNTRACK || NF_CONNTRACK
977
	select NF_DUP_IPV4
978
	select NF_DUP_IPV6 if IPV6
979 980 981 982
	---help---
	This option adds a "TEE" target with which a packet can be cloned and
	this clone be rerouted to another nexthop.

983
config NETFILTER_XT_TARGET_TPROXY
984
	tristate '"TPROXY" target transparent proxying support'
985 986
	depends on NETFILTER_XTABLES
	depends on NETFILTER_ADVANCED
987 988
	depends on IPV6 || IPV6=n
	depends on IP6_NF_IPTABLES || IP6_NF_IPTABLES=n
989
	depends on IP_NF_MANGLE
990
	select NF_DEFRAG_IPV4
991
	select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES != n
M
Máté Eckl 已提交
992 993
	select NF_TPROXY_IPV4
	select NF_TPROXY_IPV6 if IP6_NF_IPTABLES
994 995 996 997 998
	help
	  This option adds a `TPROXY' target, which is somewhat similar to
	  REDIRECT.  It can only be used in the mangle table and is useful
	  to redirect traffic to a transparent proxy.  It does _not_ depend
	  on Netfilter connection tracking and NAT, unlike REDIRECT.
999 1000 1001
	  For it to work you will have to configure certain iptables rules
	  and use policy routing. For more information on how to set it up
	  see Documentation/networking/tproxy.txt.
1002 1003 1004

	  To compile it as a module, choose M here.  If unsure, say N.

1005 1006 1007
config NETFILTER_XT_TARGET_TRACE
	tristate  '"TRACE" target support'
	depends on IP_NF_RAW || IP6_NF_RAW
1008
	depends on NETFILTER_ADVANCED
1009 1010 1011 1012 1013 1014
	help
	  The TRACE target allows you to mark packets so that the kernel
	  will log every rule which match the packets as those traverse
	  the tables, chains, rules.

	  If you want to compile it as a module, say M here and read
1015
	  <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
1016

1017 1018
config NETFILTER_XT_TARGET_SECMARK
	tristate '"SECMARK" target support'
1019
	depends on NETWORK_SECMARK
1020
	default m if NETFILTER_ADVANCED=n
1021 1022 1023 1024 1025 1026
	help
	  The SECMARK target allows security marking of network
	  packets, for use with security subsystems.

	  To compile it as a module, choose M here.  If unsure, say N.

1027 1028
config NETFILTER_XT_TARGET_TCPMSS
	tristate '"TCPMSS" target support'
1029
	depends on IPV6 || IPV6=n
1030
	default m if NETFILTER_ADVANCED=n
1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053
	---help---
	  This option adds a `TCPMSS' target, which allows you to alter the
	  MSS value of TCP SYN packets, to control the maximum size for that
	  connection (usually limiting it to your outgoing interface's MTU
	  minus 40).

	  This is used to overcome criminally braindead ISPs or servers which
	  block ICMP Fragmentation Needed packets.  The symptoms of this
	  problem are that everything works fine from your Linux
	  firewall/router, but machines behind it can never exchange large
	  packets:
	        1) Web browsers connect, then hang with no data received.
	        2) Small mail works fine, but large emails hang.
	        3) ssh works fine, but scp hangs after initial handshaking.

	  Workaround: activate this option and add a rule to your firewall
	  configuration like:

	  iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
	                 -j TCPMSS --clamp-mss-to-pmtu

	  To compile it as a module, choose M here.  If unsure, say N.

1054
config NETFILTER_XT_TARGET_TCPOPTSTRIP
1055
	tristate '"TCPOPTSTRIP" target support'
1056
	depends on IP_NF_MANGLE || IP6_NF_MANGLE
1057
	depends on NETFILTER_ADVANCED
1058 1059 1060 1061
	help
	  This option adds a "TCPOPTSTRIP" target, which allows you to strip
	  TCP options from TCP packets.

1062 1063 1064 1065
# alphabetically ordered list of matches

comment "Xtables matches"

1066 1067
config NETFILTER_XT_MATCH_ADDRTYPE
	tristate '"addrtype" address type match support'
1068
	default m if NETFILTER_ADVANCED=n
1069 1070 1071 1072 1073 1074 1075
	---help---
	  This option allows you to match what routing thinks of an address,
	  eg. UNICAST, LOCAL, BROADCAST, ...

	  If you want to compile it as a module, say M here and read
	  <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.

1076 1077 1078 1079 1080 1081 1082 1083 1084
config NETFILTER_XT_MATCH_BPF
	tristate '"bpf" match support'
	depends on NETFILTER_ADVANCED
	help
	  BPF matching applies a linux socket filter to each packet and
	  accepts those for which the filter returns non-zero.

	  To compile it as a module, choose M here.  If unsure, say N.

1085 1086 1087 1088 1089 1090 1091 1092 1093 1094
config NETFILTER_XT_MATCH_CGROUP
	tristate '"control group" match support'
	depends on NETFILTER_ADVANCED
	depends on CGROUPS
	select CGROUP_NET_CLASSID
	---help---
	Socket/process control group matching allows you to match locally
	generated packets based on which net_cls control group processes
	belong to.

1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110
config NETFILTER_XT_MATCH_CLUSTER
	tristate '"cluster" match support'
	depends on NF_CONNTRACK
	depends on NETFILTER_ADVANCED
	---help---
	  This option allows you to build work-load-sharing clusters of
	  network servers/stateful firewalls without having a dedicated
	  load-balancing router/server/switch. Basically, this match returns
	  true when the packet must be handled by this cluster node. Thus,
	  all nodes see all packets and this match decides which node handles
	  what packets. The work-load sharing algorithm is based on source
	  address hashing.

	  If you say Y or M here, try `iptables -m cluster --help` for
	  more information.

1111 1112
config NETFILTER_XT_MATCH_COMMENT
	tristate  '"comment" match support'
1113
	depends on NETFILTER_ADVANCED
1114 1115 1116 1117 1118
	help
	  This option adds a `comment' dummy-match, which allows you to put
	  comments in your iptables ruleset.

	  If you want to compile it as a module, say M here and read
1119
	  <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
1120 1121 1122

config NETFILTER_XT_MATCH_CONNBYTES
	tristate  '"connbytes" per-connection counter match support'
1123
	depends on NF_CONNTRACK
1124
	depends on NETFILTER_ADVANCED
1125 1126 1127 1128 1129
	help
	  This option adds a `connbytes' match, which allows you to match the
	  number of bytes and/or packets for each direction within a connection.

	  If you want to compile it as a module, say M here and read
1130
	  <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
1131

1132 1133 1134
config NETFILTER_XT_MATCH_CONNLABEL
	tristate '"connlabel" match support'
	select NF_CONNTRACK_LABELS
1135
	depends on NF_CONNTRACK
1136 1137 1138 1139 1140 1141 1142 1143 1144
	depends on NETFILTER_ADVANCED
	---help---
	  This match allows you to test and assign userspace-defined labels names
	  to a connection.  The kernel only stores bit values - mapping
	  names to bits is done by userspace.

	  Unlike connmark, more than 32 flag bits may be assigned to a
	  connection simultaneously.

1145
config NETFILTER_XT_MATCH_CONNLIMIT
1146
	tristate '"connlimit" match support'
1147
	depends on NF_CONNTRACK
1148
	depends on NETFILTER_ADVANCED
1149
	select NETFILTER_CONNCOUNT
1150 1151 1152 1153
	---help---
	  This match allows you to match against the number of parallel
	  connections to a server per client IP address (or address block).

1154 1155
config NETFILTER_XT_MATCH_CONNMARK
	tristate  '"connmark" connection mark match support'
1156
	depends on NF_CONNTRACK
1157
	depends on NETFILTER_ADVANCED
1158 1159 1160 1161 1162
	select NETFILTER_XT_CONNMARK
	---help---
	This is a backwards-compat option for the user's convenience
	(e.g. when running oldconfig). It selects
	CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
1163 1164 1165

config NETFILTER_XT_MATCH_CONNTRACK
	tristate '"conntrack" connection tracking match support'
1166
	depends on NF_CONNTRACK
1167
	default m if NETFILTER_ADVANCED=n
1168 1169 1170 1171 1172 1173 1174 1175
	help
	  This is a general conntrack match module, a superset of the state match.

	  It allows matching on additional conntrack information, which is
	  useful in complex configurations, such as NAT gateways with multiple
	  internet links or tunnels.

	  To compile it as a module, choose M here.  If unsure, say N.
E
Eric Dumazet 已提交
1176 1177 1178 1179 1180 1181 1182 1183 1184

config NETFILTER_XT_MATCH_CPU
	tristate '"cpu" match support'
	depends on NETFILTER_ADVANCED
	help
	  CPU matching allows you to match packets based on the CPU
	  currently handling the packet.

	  To compile it as a module, choose M here.  If unsure, say N.
1185 1186

config NETFILTER_XT_MATCH_DCCP
1187
	tristate '"dccp" protocol match support'
1188
	depends on NETFILTER_ADVANCED
1189
	default IP_DCCP
1190 1191 1192 1193 1194 1195
	help
	  With this option enabled, you will be able to use the iptables
	  `dccp' match in order to match on DCCP source/destination ports
	  and DCCP flags.

	  If you want to compile it as a module, say M here and read
1196
	  <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
1197

1198 1199 1200 1201 1202 1203 1204 1205 1206
config NETFILTER_XT_MATCH_DEVGROUP
	tristate '"devgroup" match support'
	depends on NETFILTER_ADVANCED
	help
	  This options adds a `devgroup' match, which allows to match on the
	  device group a network device is assigned to.

	  To compile it as a module, choose M here.  If unsure, say N.

1207
config NETFILTER_XT_MATCH_DSCP
1208
	tristate '"dscp" and "tos" match support'
1209
	depends on NETFILTER_ADVANCED
1210 1211 1212 1213 1214 1215
	help
	  This option adds a `DSCP' match, which allows you to match against
	  the IPv4/IPv6 header DSCP field (differentiated services codepoint).

	  The DSCP field can have any value between 0x0 and 0x3f inclusive.

1216 1217 1218 1219
	  It will also add a "tos" match, which allows you to match packets
	  based on the Type Of Service fields of the IPv4 packet (which share
	  the same bits as DSCP).

1220 1221
	  To compile it as a module, choose M here.  If unsure, say N.

1222 1223 1224 1225 1226 1227 1228 1229 1230
config NETFILTER_XT_MATCH_ECN
	tristate '"ecn" match support'
	depends on NETFILTER_ADVANCED
	---help---
	This option adds an "ECN" match, which allows you to match against
	the IPv4 and TCP header ECN fields.

	To compile it as a module, choose M here. If unsure, say N.

1231
config NETFILTER_XT_MATCH_ESP
1232
	tristate '"esp" match support'
1233
	depends on NETFILTER_ADVANCED
1234 1235 1236 1237 1238 1239
	help
	  This match extension allows you to match a range of SPIs
	  inside ESP header of IPSec packets.

	  To compile it as a module, choose M here.  If unsure, say N.

1240 1241
config NETFILTER_XT_MATCH_HASHLIMIT
	tristate '"hashlimit" match support'
1242
	depends on IP6_NF_IPTABLES || IP6_NF_IPTABLES=n
1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254
	depends on NETFILTER_ADVANCED
	help
	  This option adds a `hashlimit' match.

	  As opposed to `limit', this match dynamically creates a hash table
	  of limit buckets, based on your selection of source/destination
	  addresses and/or ports.

	  It enables you to express policies like `10kpps for any given
	  destination address' or `500pps from any given source address'
	  with a single rule.

1255 1256
config NETFILTER_XT_MATCH_HELPER
	tristate '"helper" match support'
1257
	depends on NF_CONNTRACK
1258
	depends on NETFILTER_ADVANCED
1259 1260 1261 1262 1263 1264
	help
	  Helper matching allows you to match packets in dynamic connections
	  tracked by a conntrack-helper, ie. ip_conntrack_ftp

	  To compile it as a module, choose M here.  If unsure, say Y.

1265 1266 1267 1268 1269 1270 1271 1272
config NETFILTER_XT_MATCH_HL
	tristate '"hl" hoplimit/TTL match support'
	depends on NETFILTER_ADVANCED
	---help---
	HL matching allows you to match packets based on the hoplimit
	in the IPv6 header, or the time-to-live field in the IPv4
	header of the packet.

1273 1274 1275 1276 1277 1278 1279 1280 1281
config NETFILTER_XT_MATCH_IPCOMP
	tristate '"ipcomp" match support'
	depends on NETFILTER_ADVANCED
	help
	  This match extension allows you to match a range of CPIs(16 bits)
	  inside IPComp header of IPSec packets.

	  To compile it as a module, choose M here.  If unsure, say N.

1282 1283 1284 1285 1286 1287 1288 1289 1290 1291
config NETFILTER_XT_MATCH_IPRANGE
	tristate '"iprange" address range match support'
	depends on NETFILTER_ADVANCED
	---help---
	This option adds a "iprange" match, which allows you to match based on
	an IP address range. (Normal iptables only matches on single addresses
	with an optional mask.)

	If unsure, say M.

1292 1293 1294 1295 1296 1297 1298 1299 1300 1301
config NETFILTER_XT_MATCH_IPVS
	tristate '"ipvs" match support'
	depends on IP_VS
	depends on NETFILTER_ADVANCED
	depends on NF_CONNTRACK
	help
	  This option allows you to match against IPVS properties of a packet.

	  If unsure, say N.

1302 1303 1304 1305 1306 1307 1308 1309 1310 1311
config NETFILTER_XT_MATCH_L2TP
	tristate '"l2tp" match support'
	depends on NETFILTER_ADVANCED
	default L2TP
	---help---
	This option adds an "L2TP" match, which allows you to match against
	L2TP protocol header fields.

	To compile it as a module, choose M here. If unsure, say N.

1312 1313
config NETFILTER_XT_MATCH_LENGTH
	tristate '"length" match support'
1314
	depends on NETFILTER_ADVANCED
1315 1316 1317 1318 1319 1320 1321 1322
	help
	  This option allows you to match the length of a packet against a
	  specific value or range of values.

	  To compile it as a module, choose M here.  If unsure, say N.

config NETFILTER_XT_MATCH_LIMIT
	tristate '"limit" match support'
1323
	depends on NETFILTER_ADVANCED
1324 1325 1326 1327 1328 1329 1330 1331 1332
	help
	  limit matching allows you to control the rate at which a rule can be
	  matched: mainly useful in combination with the LOG target ("LOG
	  target support", below) and to avoid some Denial of Service attacks.

	  To compile it as a module, choose M here.  If unsure, say N.

config NETFILTER_XT_MATCH_MAC
	tristate '"mac" address match support'
1333
	depends on NETFILTER_ADVANCED
1334 1335 1336 1337 1338 1339 1340 1341
	help
	  MAC matching allows you to match packets based on the source
	  Ethernet address of the packet.

	  To compile it as a module, choose M here.  If unsure, say N.

config NETFILTER_XT_MATCH_MARK
	tristate '"mark" match support'
1342 1343 1344 1345 1346 1347
	depends on NETFILTER_ADVANCED
	select NETFILTER_XT_MARK
	---help---
	This is a backwards-compat option for the user's convenience
	(e.g. when running oldconfig). It selects
	CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
1348

1349 1350 1351 1352 1353 1354 1355 1356 1357 1358
config NETFILTER_XT_MATCH_MULTIPORT
	tristate '"multiport" Multiple port match support'
	depends on NETFILTER_ADVANCED
	help
	  Multiport matching allows you to match TCP or UDP packets based on
	  a series of source or destination ports: normally a rule can only
	  match a single range of ports.

	  To compile it as a module, choose M here.  If unsure, say N.

1359 1360
config NETFILTER_XT_MATCH_NFACCT
	tristate '"nfacct" match support'
1361
	depends on NETFILTER_ADVANCED
1362 1363 1364 1365 1366 1367 1368
	select NETFILTER_NETLINK_ACCT
	help
	  This option allows you to use the extended accounting through
	  nfnetlink_acct.

	  To compile it as a module, choose M here.  If unsure, say N.

1369 1370 1371
config NETFILTER_XT_MATCH_OSF
	tristate '"osf" Passive OS fingerprint match'
	depends on NETFILTER_ADVANCED && NETFILTER_NETLINK
1372
	select NF_OSF
1373 1374 1375 1376 1377 1378 1379 1380 1381 1382
	help
	  This option selects the Passive OS Fingerprinting match module
	  that allows to passively match the remote operating system by
	  analyzing incoming TCP SYN packets.

	  Rules and loading software can be downloaded from
	  http://www.ioremap.net/projects/osf

	  To compile it as a module, choose M here.  If unsure, say N.

1383 1384
config NETFILTER_XT_MATCH_OWNER
	tristate '"owner" match support'
1385
	depends on NETFILTER_ADVANCED
1386 1387 1388 1389 1390
	---help---
	Socket owner matching allows you to match locally-generated packets
	based on who created the socket: the user or group. It is also
	possible to check whether a socket actually exists.

1391 1392
config NETFILTER_XT_MATCH_POLICY
	tristate 'IPsec "policy" match support'
1393
	depends on XFRM
1394
	default m if NETFILTER_ADVANCED=n
1395 1396 1397 1398 1399 1400 1401
	help
	  Policy matching allows you to match packets based on the
	  IPsec policy that was used during decapsulation/will
	  be used during encapsulation.

	  To compile it as a module, choose M here.  If unsure, say N.

1402 1403
config NETFILTER_XT_MATCH_PHYSDEV
	tristate '"physdev" match support'
1404
	depends on BRIDGE && BRIDGE_NETFILTER
1405
	depends on NETFILTER_ADVANCED
1406 1407 1408 1409 1410 1411 1412 1413
	help
	  Physdev packet matching matches against the physical bridge ports
	  the IP packet arrived on or will leave by.

	  To compile it as a module, choose M here.  If unsure, say N.

config NETFILTER_XT_MATCH_PKTTYPE
	tristate '"pkttype" packet type match support'
1414
	depends on NETFILTER_ADVANCED
1415 1416 1417 1418 1419 1420 1421 1422 1423
	help
	  Packet type matching allows you to match a packet by
	  its "class", eg. BROADCAST, MULTICAST, ...

	  Typical usage:
	  iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG

	  To compile it as a module, choose M here.  If unsure, say N.

1424 1425
config NETFILTER_XT_MATCH_QUOTA
	tristate '"quota" match support'
1426
	depends on NETFILTER_ADVANCED
1427 1428 1429 1430 1431
	help
	  This option adds a `quota' match, which allows to match on a
	  byte counter.

	  If you want to compile it as a module, say M here and read
1432
	  <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
1433

1434 1435
config NETFILTER_XT_MATCH_RATEEST
	tristate '"rateest" match support'
1436
	depends on NETFILTER_ADVANCED
1437 1438 1439 1440 1441 1442 1443
	select NETFILTER_XT_TARGET_RATEEST
	help
	  This option adds a `rateest' match, which allows to match on the
	  rate estimated by the RATEEST target.

	  To compile it as a module, choose M here.  If unsure, say N.

1444 1445
config NETFILTER_XT_MATCH_REALM
	tristate  '"realm" match support'
1446
	depends on NETFILTER_ADVANCED
1447
	select IP_ROUTE_CLASSID
1448 1449 1450
	help
	  This option adds a `realm' match, which allows you to use the realm
	  key from the routing subsystem inside iptables.
1451

1452 1453
	  This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option 
	  in tc world.
1454

1455
	  If you want to compile it as a module, say M here and read
1456
	  <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
1457

1458 1459 1460 1461 1462 1463 1464 1465 1466 1467
config NETFILTER_XT_MATCH_RECENT
	tristate '"recent" match support'
	depends on NETFILTER_ADVANCED
	---help---
	This match is used for creating one or many lists of recently
	used addresses and then matching against that/those list(s).

	Short options are available by using 'iptables -m recent -h'
	Official Website: <http://snowman.net/projects/ipt_recent/>

1468
config NETFILTER_XT_MATCH_SCTP
1469
	tristate  '"sctp" protocol match support'
1470
	depends on NETFILTER_ADVANCED
1471
	default IP_SCTP
1472 1473 1474 1475 1476 1477
	help
	  With this option enabled, you will be able to use the 
	  `sctp' match in order to match on SCTP source/destination ports
	  and SCTP chunk types.

	  If you want to compile it as a module, say M here and read
1478
	  <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
1479

1480
config NETFILTER_XT_MATCH_SOCKET
1481
	tristate '"socket" match support'
1482 1483
	depends on NETFILTER_XTABLES
	depends on NETFILTER_ADVANCED
1484 1485
	depends on IPV6 || IPV6=n
	depends on IP6_NF_IPTABLES || IP6_NF_IPTABLES=n
1486 1487
	depends on NF_SOCKET_IPV4
	depends on NF_SOCKET_IPV6
1488
	select NF_DEFRAG_IPV4
1489
	select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES != n
1490 1491 1492 1493 1494 1495 1496 1497
	help
	  This option adds a `socket' match, which can be used to match
	  packets for which a TCP or UDP socket lookup finds a valid socket.
	  It can be used in combination with the MARK target and policy
	  routing to implement full featured non-locally bound sockets.

	  To compile it as a module, choose M here.  If unsure, say N.

1498 1499
config NETFILTER_XT_MATCH_STATE
	tristate '"state" match support'
1500
	depends on NF_CONNTRACK
1501
	default m if NETFILTER_ADVANCED=n
1502 1503 1504 1505 1506 1507 1508
	help
	  Connection state matching allows you to match packets based on their
	  relationship to a tracked connection (ie. previous packets).  This
	  is a powerful tool for packet classification.

	  To compile it as a module, choose M here.  If unsure, say N.

1509 1510
config NETFILTER_XT_MATCH_STATISTIC
	tristate '"statistic" match support'
1511
	depends on NETFILTER_ADVANCED
1512
	help
1513 1514 1515 1516
	  This option adds a `statistic' match, which allows you to match
	  on packets periodically or randomly with a given percentage.

	  To compile it as a module, choose M here.  If unsure, say N.
1517

1518 1519
config NETFILTER_XT_MATCH_STRING
	tristate  '"string" match support'
1520
	depends on NETFILTER_ADVANCED
1521 1522 1523 1524 1525 1526 1527 1528 1529 1530 1531 1532
	select TEXTSEARCH
	select TEXTSEARCH_KMP
	select TEXTSEARCH_BM
	select TEXTSEARCH_FSM
	help
	  This option adds a `string' match, which allows you to look for
	  pattern matchings in packets.

	  To compile it as a module, choose M here.  If unsure, say N.

config NETFILTER_XT_MATCH_TCPMSS
	tristate '"tcpmss" match support'
1533
	depends on NETFILTER_ADVANCED
1534 1535 1536 1537 1538 1539 1540
	help
	  This option adds a `tcpmss' match, which allows you to examine the
	  MSS value of TCP SYN packets, which control the maximum packet size
	  for that connection.

	  To compile it as a module, choose M here.  If unsure, say N.

1541 1542
config NETFILTER_XT_MATCH_TIME
	tristate '"time" match support'
1543
	depends on NETFILTER_ADVANCED
1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554
	---help---
	  This option adds a "time" match, which allows you to match based on
	  the packet arrival time (at the machine which netfilter is running)
	  on) or departure time/date (for locally generated packets).

	  If you say Y here, try `iptables -m time --help` for
	  more information.

	  If you want to compile it as a module, say M here.
	  If unsure, say N.

J
Jan Engelhardt 已提交
1555 1556
config NETFILTER_XT_MATCH_U32
	tristate '"u32" match support'
1557
	depends on NETFILTER_ADVANCED
J
Jan Engelhardt 已提交
1558 1559 1560 1561 1562 1563 1564 1565 1566 1567
	---help---
	  u32 allows you to extract quantities of up to 4 bytes from a packet,
	  AND them with specified masks, shift them by specified amounts and
	  test whether the results are in any of a set of specified ranges.
	  The specification of what to extract is general enough to skip over
	  headers with lengths stored in the packet, as in IP or TCP header
	  lengths.

	  Details and examples are in the kernel module source.

1568
endif # NETFILTER_XTABLES
1569

1570
endmenu
1571

1572 1573
source "net/netfilter/ipset/Kconfig"

1574
source "net/netfilter/ipvs/Kconfig"