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

H
Harald Welte 已提交
4
config NETFILTER_NETLINK
5
	tristate
6

7 8 9 10 11 12 13 14
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.

15 16
config NETFILTER_NETLINK_QUEUE
	tristate "Netfilter NFQUEUE over NFNETLINK interface"
17
	depends on NETFILTER_ADVANCED
18
	select NETFILTER_NETLINK
19
	help
T
Thomas Vgtle 已提交
20
	  If this option is enabled, the kernel will include support
21 22
	  for queueing packets via NFNETLINK.
	  
23 24
config NETFILTER_NETLINK_LOG
	tristate "Netfilter LOG over NFNETLINK interface"
25
	default m if NETFILTER_ADVANCED=n
26
	select NETFILTER_NETLINK
27 28 29 30 31 32 33 34
	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.

35
config NF_CONNTRACK
36
	tristate "Netfilter connection tracking support"
37
	default m if NETFILTER_ADVANCED=n
38
	help
39 40 41 42
	  Connection tracking keeps a record of what packets have passed
	  through your machine, in order to figure out how they are related
	  into connections.

43
	  This is required to do Masquerading or other kinds of Network
44 45
	  Address Translation.  It can also be used to enhance packet
	  filtering (see `Connection state match support' below).
46 47 48

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

49 50
if NF_CONNTRACK

51 52
config NF_CONNTRACK_MARK
	bool  'Connection mark tracking support'
53
	depends on NETFILTER_ADVANCED
54 55 56 57 58 59
	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.

60 61
config NF_CONNTRACK_SECMARK
	bool  'Connection tracking security mark support'
62
	depends on NETWORK_SECMARK
63
	default m if NETFILTER_ADVANCED=n
64 65 66 67 68 69 70 71 72
	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'.

73 74 75 76 77 78 79 80 81 82 83 84 85
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'.

86 87 88 89 90 91 92 93 94 95
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.

96
config NF_CONNTRACK_EVENTS
97
	bool "Connection tracking events"
98
	depends on NETFILTER_ADVANCED
99 100 101
	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 已提交
102
	  to get notified about changes in the connection tracking state.
103 104 105

	  If unsure, say `N'.

106 107 108 109 110 111 112 113 114 115
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'.

116 117 118 119 120 121 122 123 124 125 126
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'.

127 128 129 130 131 132
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.

133
config NF_CT_PROTO_DCCP
134
	tristate 'DCCP protocol connection tracking support'
135
	depends on NETFILTER_ADVANCED
136
	default IP_DCCP
137 138 139 140 141 142
	help
	  With this option enabled, the layer 3 independent connection
	  tracking code will be able to do state tracking on DCCP connections.

	  If unsure, say 'N'.

143 144 145
config NF_CT_PROTO_GRE
	tristate

146
config NF_CT_PROTO_SCTP
147
	tristate 'SCTP protocol connection tracking support'
148
	depends on NETFILTER_ADVANCED
149
	default IP_SCTP
150 151 152 153 154
	help
	  With this option enabled, the layer 3 independent connection
	  tracking code will be able to do state tracking on SCTP connections.

	  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

157
config NF_CT_PROTO_UDPLITE
158
	tristate 'UDP-Lite protocol connection tracking support'
159
	depends on NETFILTER_ADVANCED
160 161 162 163 164 165 166
	help
	  With this option enabled, the layer 3 independent connection
	  tracking code will be able to do state tracking on UDP-Lite
	  connections.

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

167
config NF_CONNTRACK_AMANDA
168
	tristate "Amanda backup protocol support"
169
	depends on NETFILTER_ADVANCED
170 171 172 173 174 175 176 177 178 179 180 181
	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.

182
config NF_CONNTRACK_FTP
183
	tristate "FTP protocol support"
184
	default m if NETFILTER_ADVANCED=n
185 186 187 188 189 190 191 192 193 194 195
	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.

196
config NF_CONNTRACK_H323
197
	tristate "H.323 protocol support"
198
	depends on (IPV6 || IPV6=n)
199
	depends on NETFILTER_ADVANCED
200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215
	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.

216
config NF_CONNTRACK_IRC
217
	tristate "IRC protocol support"
218
	default m if NETFILTER_ADVANCED=n
219 220 221 222 223 224 225 226 227 228 229 230
	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.

231 232 233
config NF_CONNTRACK_BROADCAST
	tristate

234
config NF_CONNTRACK_NETBIOS_NS
235
	tristate "NetBIOS name service protocol support"
236
	select NF_CONNTRACK_BROADCAST
237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252
	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.

253 254 255 256 257 258 259 260 261 262 263 264 265 266 267
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.

268
config NF_CONNTRACK_PPTP
269
	tristate "PPtP protocol support"
270
	depends on NETFILTER_ADVANCED
271 272 273 274 275 276 277 278 279 280
	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:
281
	    - Blindly assumes that control connections are always established
282 283 284 285 286
	      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.

287
config NF_CONNTRACK_SANE
288
	tristate "SANE protocol support"
289
	depends on NETFILTER_ADVANCED
290 291 292 293 294 295 296 297 298 299
	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.

300
config NF_CONNTRACK_SIP
301
	tristate "SIP protocol support"
302
	default m if NETFILTER_ADVANCED=n
303 304 305 306 307 308 309 310 311
	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.

312
config NF_CONNTRACK_TFTP
313
	tristate "TFTP protocol support"
314
	depends on NETFILTER_ADVANCED
315 316 317 318 319 320 321 322
	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.

323
config NF_CT_NETLINK
324
	tristate 'Connection tracking netlink interface'
325
	select NETFILTER_NETLINK
326
	default m if NETFILTER_ADVANCED=n
327 328 329
	help
	  This option enables support for a netlink-based userspace interface

330 331 332 333 334 335 336 337 338 339 340
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'.

341 342 343 344 345
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
346
	depends on NETFILTER_NETLINK_QUEUE_CT
347 348 349 350 351 352 353
	depends on NETFILTER_ADVANCED
	help
	  This option enables the user-space connection tracking helpers
	  infrastructure.

	  If unsure, say `N'.

354 355 356 357 358 359 360 361
config NETFILTER_NETLINK_QUEUE_CT
        bool "NFQUEUE integration with Connection Tracking"
        default n
        depends on NETFILTER_NETLINK_QUEUE
	help
	  If this option is enabled, NFQUEUE can include Connection Tracking
	  information together with the packet is the enqueued via NFNETLINK.

362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385
config NF_NAT
	tristate

config NF_NAT_NEEDED
	bool
	depends on NF_NAT
	default y

config NF_NAT_PROTO_DCCP
	tristate
	depends on NF_NAT && NF_CT_PROTO_DCCP
	default NF_NAT && NF_CT_PROTO_DCCP

config NF_NAT_PROTO_UDPLITE
	tristate
	depends on NF_NAT && NF_CT_PROTO_UDPLITE
	default NF_NAT && NF_CT_PROTO_UDPLITE

config NF_NAT_PROTO_SCTP
	tristate
	default NF_NAT && NF_CT_PROTO_SCTP
	depends on NF_NAT && NF_CT_PROTO_SCTP
	select LIBCRC32C

386 387 388 389 390
config NF_NAT_AMANDA
	tristate
	depends on NF_CONNTRACK && NF_NAT
	default NF_NAT && NF_CONNTRACK_AMANDA

391 392 393 394 395
config NF_NAT_FTP
	tristate
	depends on NF_CONNTRACK && NF_NAT
	default NF_NAT && NF_CONNTRACK_FTP

396 397 398 399 400
config NF_NAT_IRC
	tristate
	depends on NF_CONNTRACK && NF_NAT
	default NF_NAT && NF_CONNTRACK_IRC

401 402 403 404 405
config NF_NAT_SIP
	tristate
	depends on NF_CONNTRACK && NF_NAT
	default NF_NAT && NF_CONNTRACK_SIP

406 407 408 409 410
config NF_NAT_TFTP
	tristate
	depends on NF_CONNTRACK && NF_NAT
	default NF_NAT && NF_CONNTRACK_TFTP

411 412 413
config NETFILTER_SYNPROXY
	tristate

414 415
endif # NF_CONNTRACK

P
Patrick McHardy 已提交
416
config NF_TABLES
417
	select NETFILTER_NETLINK
P
Patrick McHardy 已提交
418
	tristate "Netfilter nf_tables support"
419 420 421 422 423 424 425 426 427 428 429
	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 已提交
430 431 432 433

config NFT_EXTHDR
	depends on NF_TABLES
	tristate "Netfilter nf_tables IPv6 exthdr module"
434 435 436
	help
	  This option adds the "exthdr" expression that you can use to match
	  IPv6 extension headers.
P
Patrick McHardy 已提交
437 438 439 440

config NFT_META
	depends on NF_TABLES
	tristate "Netfilter nf_tables meta module"
441 442 443
	help
	  This option adds the "meta" expression that you can use to match and
	  to set packet metainformation such as the packet mark.
P
Patrick McHardy 已提交
444 445 446 447 448

config NFT_CT
	depends on NF_TABLES
	depends on NF_CONNTRACK
	tristate "Netfilter nf_tables conntrack module"
449 450 451
	help
	  This option adds the "meta" expression that you can use to match
	  connection tracking information such as the flow state.
P
Patrick McHardy 已提交
452

453
config NFT_RBTREE
P
Patrick McHardy 已提交
454
	depends on NF_TABLES
455
	tristate "Netfilter nf_tables rbtree set module"
456 457 458
	help
	  This option adds the "rbtree" set type (Red Black tree) that is used
	  to build interval-based sets.
P
Patrick McHardy 已提交
459 460 461

config NFT_HASH
	depends on NF_TABLES
462
	tristate "Netfilter nf_tables hash set module"
463 464 465
	help
	  This option adds the "hash" set type that is used to build one-way
	  mappings between matchings and actions.
P
Patrick McHardy 已提交
466 467 468 469

config NFT_COUNTER
	depends on NF_TABLES
	tristate "Netfilter nf_tables counter module"
470 471 472
	help
	  This option adds the "counter" expression that you can use to
	  include packet and byte counters in a rule.
P
Patrick McHardy 已提交
473 474 475 476

config NFT_LOG
	depends on NF_TABLES
	tristate "Netfilter nf_tables log module"
477 478 479
	help
	  This option adds the "log" expression that you can use to log
	  packets matching some criteria.
P
Patrick McHardy 已提交
480 481 482 483

config NFT_LIMIT
	depends on NF_TABLES
	tristate "Netfilter nf_tables limit module"
484 485 486
	help
	  This option adds the "limit" expression that you can use to
	  ratelimit rule matchings.
P
Patrick McHardy 已提交
487

488 489 490 491 492
config NFT_NAT
	depends on NF_TABLES
	depends on NF_CONNTRACK
	depends on NF_NAT
	tristate "Netfilter nf_tables nat module"
493 494 495
	help
	  This option adds the "nat" expression that you can use to perform
	  typical Network Address Translation (NAT) packet transformations.
496

E
Eric Leblond 已提交
497 498 499 500 501 502 503 504 505
config NFT_QUEUE
	depends on NF_TABLES
	depends on NETFILTER_XTABLES
	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.

506 507 508 509 510
config NFT_REJECT
	depends on NF_TABLES
	depends on NF_TABLES_IPV6 || !NF_TABLES_IPV6
	default m if NETFILTER_ADVANCED=n
	tristate "Netfilter nf_tables reject support"
511 512 513 514
	help
	  This option adds the "reject" expression that you can use to
	  explicitly deny and notify via TCP reset/ICMP informational errors
	  unallowed traffic.
515

516 517 518 519 520 521 522 523 524
config NFT_COMPAT
	depends on NF_TABLES
	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.

525 526
config NETFILTER_XTABLES
	tristate "Netfilter Xtables support (required for ip_tables)"
527
	default m if NETFILTER_ADVANCED=n
528 529 530 531
	help
	  This is required if you intend to use any of ip_tables,
	  ip6_tables or arp_tables.

532 533
if NETFILTER_XTABLES

534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550
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.

	Prior to routing, the nfmark can influence the routing method (see
	"Use netfilter MARK value as routing key") and can also be used by
	other subsystems to change their behavior.

551 552 553 554 555 556 557 558 559 560 561 562
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.

563 564 565 566 567 568 569 570 571 572 573 574
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.

575 576
# alphabetically ordered list of targets

577 578
comment "Xtables targets"

579 580 581 582 583 584 585 586 587 588
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.

589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604
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.

605 606
config NETFILTER_XT_TARGET_CLASSIFY
	tristate '"CLASSIFY" target support'
607
	depends on NETFILTER_ADVANCED
608 609 610 611 612 613 614 615 616 617 618
	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'
619
	depends on NF_CONNTRACK
620
	depends on NETFILTER_ADVANCED
621 622 623 624 625
	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).
626

627 628
config NETFILTER_XT_TARGET_CONNSECMARK
	tristate '"CONNSECMARK" target support'
629
	depends on NF_CONNTRACK && NF_CONNTRACK_SECMARK
630 631 632 633 634 635 636 637 638
	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.

639 640 641 642 643 644 645 646 647 648 649 650
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.

651
config NETFILTER_XT_TARGET_DSCP
652
	tristate '"DSCP" and "TOS" target support'
653
	depends on IP_NF_MANGLE || IP6_NF_MANGLE
654
	depends on NETFILTER_ADVANCED
655 656 657 658 659 660
	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.

661 662
	  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
663
	  or the Priority field of an IPv6 packet, prior to routing.
664

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

667 668 669 670 671 672 673 674 675 676 677 678 679 680 681
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.

682 683 684 685 686 687 688 689 690 691 692 693 694 695 696
config NETFILTER_XT_TARGET_HMARK
	tristate '"HMARK" target support'
	depends on (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
	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
	range. The nfmark can influence the routing method (see "Use netfilter
	MARK value as routing key") and can also be used by other subsystems to
	change their behaviour.

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

697 698 699 700 701 702 703 704 705 706 707 708
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.

709 710
config NETFILTER_XT_TARGET_LED
	tristate '"LED" target support'
711
	depends on LEDS_CLASS && LEDS_TRIGGERS
712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730
	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 已提交
731
	  Documentation/leds/leds-class.txt
732

733 734 735 736 737 738 739 740 741
config NETFILTER_XT_TARGET_LOG
	tristate "LOG target support"
	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.

742 743
config NETFILTER_XT_TARGET_MARK
	tristate '"MARK" target support'
744 745 746 747 748 749
	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).
750

751 752 753 754 755 756 757 758 759 760
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.

761 762
config NETFILTER_XT_TARGET_NFLOG
	tristate '"NFLOG" target support'
763
	default m if NETFILTER_ADVANCED=n
764
	select NETFILTER_NETLINK_LOG
765 766
	help
	  This option enables the NFLOG target, which allows to LOG
767
	  messages through nfnetlink_log.
768 769 770

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

771 772 773
config NETFILTER_XT_TARGET_NFQUEUE
	tristate '"NFQUEUE" target Support'
	depends on NETFILTER_ADVANCED
774
	select NETFILTER_NETLINK_QUEUE
775 776 777 778 779 780 781 782
	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.

783 784
config NETFILTER_XT_TARGET_NOTRACK
	tristate  '"NOTRACK" target support (DEPRECATED)'
785 786 787
	depends on NF_CONNTRACK
	depends on IP_NF_RAW || IP6_NF_RAW
	depends on NETFILTER_ADVANCED
788 789
	select NETFILTER_XT_TARGET_CT

790 791
config NETFILTER_XT_TARGET_RATEEST
	tristate '"RATEEST" target support'
792
	depends on NETFILTER_ADVANCED
793 794 795 796 797 798 799
	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.

800 801 802 803 804 805 806 807 808 809 810
config NETFILTER_XT_TARGET_REDIRECT
	tristate "REDIRECT target support"
	depends on NF_NAT
	---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.

811
config NETFILTER_XT_TARGET_TEE
812
	tristate '"TEE" - packet cloning to alternate destination'
813
	depends on NETFILTER_ADVANCED
814
	depends on (IPV6 || IPV6=n)
815
	depends on !NF_CONNTRACK || NF_CONNTRACK
816 817 818 819
	---help---
	This option adds a "TEE" target with which a packet can be cloned and
	this clone be rerouted to another nexthop.

820
config NETFILTER_XT_TARGET_TPROXY
821
	tristate '"TPROXY" target transparent proxying support'
822 823
	depends on NETFILTER_XTABLES
	depends on NETFILTER_ADVANCED
824
	depends on IP_NF_MANGLE
825
	select NF_DEFRAG_IPV4
826
	select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES
827 828 829 830 831
	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.
832 833 834
	  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.
835 836 837

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

838 839 840
config NETFILTER_XT_TARGET_TRACE
	tristate  '"TRACE" target support'
	depends on IP_NF_RAW || IP6_NF_RAW
841
	depends on NETFILTER_ADVANCED
842 843 844 845 846 847
	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
848
	  <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
849

850 851
config NETFILTER_XT_TARGET_SECMARK
	tristate '"SECMARK" target support'
852
	depends on NETWORK_SECMARK
853
	default m if NETFILTER_ADVANCED=n
854 855 856 857 858 859
	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.

860 861
config NETFILTER_XT_TARGET_TCPMSS
	tristate '"TCPMSS" target support'
862
	depends on (IPV6 || IPV6=n)
863
	default m if NETFILTER_ADVANCED=n
864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886
	---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.

887
config NETFILTER_XT_TARGET_TCPOPTSTRIP
888
	tristate '"TCPOPTSTRIP" target support'
889
	depends on IP_NF_MANGLE || IP6_NF_MANGLE
890
	depends on NETFILTER_ADVANCED
891 892 893 894
	help
	  This option adds a "TCPOPTSTRIP" target, which allows you to strip
	  TCP options from TCP packets.

895 896 897 898
# alphabetically ordered list of matches

comment "Xtables matches"

899 900 901 902 903 904 905 906 907 908
config NETFILTER_XT_MATCH_ADDRTYPE
	tristate '"addrtype" address type match support'
	depends on NETFILTER_ADVANCED
	---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'.

909 910 911 912 913 914 915 916 917
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.

918 919 920 921 922 923 924 925 926 927
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.

928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943
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.

944 945
config NETFILTER_XT_MATCH_COMMENT
	tristate  '"comment" match support'
946
	depends on NETFILTER_ADVANCED
947 948 949 950 951
	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
952
	  <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
953 954 955

config NETFILTER_XT_MATCH_CONNBYTES
	tristate  '"connbytes" per-connection counter match support'
956
	depends on NF_CONNTRACK
957
	depends on NETFILTER_ADVANCED
958 959 960 961 962
	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
963
	  <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
964

965 966 967
config NETFILTER_XT_MATCH_CONNLABEL
	tristate '"connlabel" match support'
	select NF_CONNTRACK_LABELS
968
	depends on NF_CONNTRACK
969 970 971 972 973 974 975 976 977
	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.

978
config NETFILTER_XT_MATCH_CONNLIMIT
979
	tristate '"connlimit" match support'
980
	depends on NF_CONNTRACK
981
	depends on NETFILTER_ADVANCED
982 983 984 985
	---help---
	  This match allows you to match against the number of parallel
	  connections to a server per client IP address (or address block).

986 987
config NETFILTER_XT_MATCH_CONNMARK
	tristate  '"connmark" connection mark match support'
988
	depends on NF_CONNTRACK
989
	depends on NETFILTER_ADVANCED
990 991 992 993 994
	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).
995 996 997

config NETFILTER_XT_MATCH_CONNTRACK
	tristate '"conntrack" connection tracking match support'
998
	depends on NF_CONNTRACK
999
	default m if NETFILTER_ADVANCED=n
1000 1001 1002 1003 1004 1005 1006 1007
	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 已提交
1008 1009 1010 1011 1012 1013 1014 1015 1016

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.
1017 1018

config NETFILTER_XT_MATCH_DCCP
1019
	tristate '"dccp" protocol match support'
1020
	depends on NETFILTER_ADVANCED
1021
	default IP_DCCP
1022 1023 1024 1025 1026 1027
	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
1028
	  <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
1029

1030 1031 1032 1033 1034 1035 1036 1037 1038
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.

1039
config NETFILTER_XT_MATCH_DSCP
1040
	tristate '"dscp" and "tos" match support'
1041
	depends on NETFILTER_ADVANCED
1042 1043 1044 1045 1046 1047
	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.

1048 1049 1050 1051
	  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).

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

1054 1055 1056 1057 1058 1059 1060 1061 1062
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.

1063
config NETFILTER_XT_MATCH_ESP
1064
	tristate '"esp" match support'
1065
	depends on NETFILTER_ADVANCED
1066 1067 1068 1069 1070 1071
	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.

1072 1073
config NETFILTER_XT_MATCH_HASHLIMIT
	tristate '"hashlimit" match support'
1074
	depends on (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086
	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.

1087 1088
config NETFILTER_XT_MATCH_HELPER
	tristate '"helper" match support'
1089
	depends on NF_CONNTRACK
1090
	depends on NETFILTER_ADVANCED
1091 1092 1093 1094 1095 1096
	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.

1097 1098 1099 1100 1101 1102 1103 1104
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.

1105 1106 1107 1108 1109 1110 1111 1112 1113
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.

1114 1115 1116 1117 1118 1119 1120 1121 1122 1123
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.

1124 1125 1126 1127 1128 1129 1130 1131 1132 1133
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.

1134 1135
config NETFILTER_XT_MATCH_LENGTH
	tristate '"length" match support'
1136
	depends on NETFILTER_ADVANCED
1137 1138 1139 1140 1141 1142 1143 1144
	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'
1145
	depends on NETFILTER_ADVANCED
1146 1147 1148 1149 1150 1151 1152 1153 1154
	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'
1155
	depends on NETFILTER_ADVANCED
1156 1157 1158 1159 1160 1161 1162 1163
	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'
1164 1165 1166 1167 1168 1169
	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).
1170

1171 1172 1173 1174 1175 1176 1177 1178 1179 1180
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.

1181 1182
config NETFILTER_XT_MATCH_NFACCT
	tristate '"nfacct" match support'
1183
	depends on NETFILTER_ADVANCED
1184 1185 1186 1187 1188 1189 1190
	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.

1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203
config NETFILTER_XT_MATCH_OSF
	tristate '"osf" Passive OS fingerprint match'
	depends on NETFILTER_ADVANCED && NETFILTER_NETLINK
	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.

1204 1205
config NETFILTER_XT_MATCH_OWNER
	tristate '"owner" match support'
1206
	depends on NETFILTER_ADVANCED
1207 1208 1209 1210 1211
	---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.

1212 1213
config NETFILTER_XT_MATCH_POLICY
	tristate 'IPsec "policy" match support'
1214
	depends on XFRM
1215
	default m if NETFILTER_ADVANCED=n
1216 1217 1218 1219 1220 1221 1222
	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.

1223 1224
config NETFILTER_XT_MATCH_PHYSDEV
	tristate '"physdev" match support'
1225
	depends on BRIDGE && BRIDGE_NETFILTER
1226
	depends on NETFILTER_ADVANCED
1227 1228 1229 1230 1231 1232 1233 1234
	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'
1235
	depends on NETFILTER_ADVANCED
1236 1237 1238 1239 1240 1241 1242 1243 1244
	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.

1245 1246
config NETFILTER_XT_MATCH_QUOTA
	tristate '"quota" match support'
1247
	depends on NETFILTER_ADVANCED
1248 1249 1250 1251 1252
	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
1253
	  <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
1254

1255 1256
config NETFILTER_XT_MATCH_RATEEST
	tristate '"rateest" match support'
1257
	depends on NETFILTER_ADVANCED
1258 1259 1260 1261 1262 1263 1264
	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.

1265 1266
config NETFILTER_XT_MATCH_REALM
	tristate  '"realm" match support'
1267
	depends on NETFILTER_ADVANCED
1268
	select IP_ROUTE_CLASSID
1269 1270 1271
	help
	  This option adds a `realm' match, which allows you to use the realm
	  key from the routing subsystem inside iptables.
1272

1273 1274
	  This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option 
	  in tc world.
1275

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

1279 1280 1281 1282 1283 1284 1285 1286 1287 1288
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/>

1289
config NETFILTER_XT_MATCH_SCTP
1290
	tristate  '"sctp" protocol match support'
1291
	depends on NETFILTER_ADVANCED
1292
	default IP_SCTP
1293 1294 1295 1296 1297 1298
	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
1299
	  <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
1300

1301
config NETFILTER_XT_MATCH_SOCKET
1302
	tristate '"socket" match support'
1303 1304
	depends on NETFILTER_XTABLES
	depends on NETFILTER_ADVANCED
1305
	depends on !NF_CONNTRACK || NF_CONNTRACK
1306
	depends on (IPV6 || IPV6=n)
1307
	select NF_DEFRAG_IPV4
1308
	select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES
1309 1310 1311 1312 1313 1314 1315 1316
	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.

1317 1318
config NETFILTER_XT_MATCH_STATE
	tristate '"state" match support'
1319
	depends on NF_CONNTRACK
1320
	default m if NETFILTER_ADVANCED=n
1321 1322 1323 1324 1325 1326 1327
	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.

1328 1329
config NETFILTER_XT_MATCH_STATISTIC
	tristate '"statistic" match support'
1330
	depends on NETFILTER_ADVANCED
1331
	help
1332 1333 1334 1335
	  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.
1336

1337 1338
config NETFILTER_XT_MATCH_STRING
	tristate  '"string" match support'
1339
	depends on NETFILTER_ADVANCED
1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350 1351
	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'
1352
	depends on NETFILTER_ADVANCED
1353 1354 1355 1356 1357 1358 1359
	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.

1360 1361
config NETFILTER_XT_MATCH_TIME
	tristate '"time" match support'
1362
	depends on NETFILTER_ADVANCED
1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1373
	---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 已提交
1374 1375
config NETFILTER_XT_MATCH_U32
	tristate '"u32" match support'
1376
	depends on NETFILTER_ADVANCED
J
Jan Engelhardt 已提交
1377 1378 1379 1380 1381 1382 1383 1384 1385 1386
	---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.

1387
endif # NETFILTER_XTABLES
1388

1389
endmenu
1390

1391 1392
source "net/netfilter/ipset/Kconfig"

1393
source "net/netfilter/ipvs/Kconfig"