Kconfig 34.6 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

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

27
config NF_CONNTRACK
28
	tristate "Netfilter connection tracking support"
29
	default m if NETFILTER_ADVANCED=n
30
	help
31 32 33 34
	  Connection tracking keeps a record of what packets have passed
	  through your machine, in order to figure out how they are related
	  into connections.

35
	  This is required to do Masquerading or other kinds of Network
36 37
	  Address Translation.  It can also be used to enhance packet
	  filtering (see `Connection state match support' below).
38 39 40

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

41 42
if NF_CONNTRACK

43 44
config NF_CONNTRACK_MARK
	bool  'Connection mark tracking support'
45
	depends on NETFILTER_ADVANCED
46 47 48 49 50 51
	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.

52 53
config NF_CONNTRACK_SECMARK
	bool  'Connection tracking security mark support'
54
	depends on NETWORK_SECMARK
55
	default m if NETFILTER_ADVANCED=n
56 57 58 59 60 61 62 63 64
	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'.

65 66 67 68 69 70 71 72 73 74 75 76 77
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'.

78
config NF_CONNTRACK_EVENTS
79
	bool "Connection tracking events"
80
	depends on NETFILTER_ADVANCED
81 82 83
	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 已提交
84
	  to get notified about changes in the connection tracking state.
85 86 87

	  If unsure, say `N'.

88 89
config NF_CT_PROTO_DCCP
	tristate 'DCCP protocol connection tracking support (EXPERIMENTAL)'
90
	depends on EXPERIMENTAL
91
	depends on NETFILTER_ADVANCED
92
	default IP_DCCP
93 94 95 96 97 98
	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'.

99 100 101
config NF_CT_PROTO_GRE
	tristate

102
config NF_CT_PROTO_SCTP
103
	tristate 'SCTP protocol connection tracking support (EXPERIMENTAL)'
104
	depends on EXPERIMENTAL
105
	depends on NETFILTER_ADVANCED
106
	default IP_SCTP
107 108 109 110 111
	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
112
	  <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
113

114
config NF_CT_PROTO_UDPLITE
115
	tristate 'UDP-Lite protocol connection tracking support'
116
	depends on NETFILTER_ADVANCED
117 118 119 120 121 122 123
	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.

124
config NF_CONNTRACK_AMANDA
125
	tristate "Amanda backup protocol support"
126
	depends on NETFILTER_ADVANCED
127 128 129 130 131 132 133 134 135 136 137 138
	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.

139
config NF_CONNTRACK_FTP
140
	tristate "FTP protocol support"
141
	default m if NETFILTER_ADVANCED=n
142 143 144 145 146 147 148 149 150 151 152
	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.

153
config NF_CONNTRACK_H323
154
	tristate "H.323 protocol support"
155
	depends on (IPV6 || IPV6=n)
156
	depends on NETFILTER_ADVANCED
157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172
	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.

173
config NF_CONNTRACK_IRC
174
	tristate "IRC protocol support"
175
	default m if NETFILTER_ADVANCED=n
176 177 178 179 180 181 182 183 184 185 186 187
	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.

188
config NF_CONNTRACK_NETBIOS_NS
189
	tristate "NetBIOS name service protocol support"
190
	depends on NETFILTER_ADVANCED
191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206
	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.

207
config NF_CONNTRACK_PPTP
208
	tristate "PPtP protocol support"
209
	depends on NETFILTER_ADVANCED
210 211 212 213 214 215 216 217 218 219
	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:
220
	    - Blindly assumes that control connections are always established
221 222 223 224 225
	      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.

226 227
config NF_CONNTRACK_SANE
	tristate "SANE protocol support (EXPERIMENTAL)"
228
	depends on EXPERIMENTAL
229
	depends on NETFILTER_ADVANCED
230 231 232 233 234 235 236 237 238 239
	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.

240
config NF_CONNTRACK_SIP
241
	tristate "SIP protocol support"
242
	default m if NETFILTER_ADVANCED=n
243 244 245 246 247 248 249 250 251
	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.

252
config NF_CONNTRACK_TFTP
253
	tristate "TFTP protocol support"
254
	depends on NETFILTER_ADVANCED
255 256 257 258 259 260 261 262
	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.

263
config NF_CT_NETLINK
264
	tristate 'Connection tracking netlink interface'
265
	select NETFILTER_NETLINK
266
	default m if NETFILTER_ADVANCED=n
267 268 269
	help
	  This option enables support for a netlink-based userspace interface

270 271
endif # NF_CONNTRACK

K
KOVACS Krisztian 已提交
272 273 274 275 276 277 278 279 280 281 282 283 284 285 286
# transparent proxy support
config NETFILTER_TPROXY
	tristate "Transparent proxying support (EXPERIMENTAL)"
	depends on EXPERIMENTAL
	depends on IP_NF_MANGLE
	depends on NETFILTER_ADVANCED
	help
	  This option enables transparent proxying support, that is,
	  support for handling non-locally bound IPv4 TCP and UDP sockets.
	  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.

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

287 288
config NETFILTER_XTABLES
	tristate "Netfilter Xtables support (required for ip_tables)"
289
	default m if NETFILTER_ADVANCED=n
290 291 292 293
	help
	  This is required if you intend to use any of ip_tables,
	  ip6_tables or arp_tables.

294 295
if NETFILTER_XTABLES

296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312
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.

313 314 315 316 317 318 319 320 321 322 323 324
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.

325 326
# alphabetically ordered list of targets

327 328
comment "Xtables targets"

329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344
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.

345 346
config NETFILTER_XT_TARGET_CLASSIFY
	tristate '"CLASSIFY" target support'
347
	depends on NETFILTER_ADVANCED
348 349 350 351 352 353 354 355 356 357 358
	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'
359
	depends on NF_CONNTRACK
360
	depends on NETFILTER_ADVANCED
361 362 363 364 365
	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).
366

367 368
config NETFILTER_XT_TARGET_CONNSECMARK
	tristate '"CONNSECMARK" target support'
369
	depends on NF_CONNTRACK && NF_CONNTRACK_SECMARK
370 371 372 373 374 375 376 377 378
	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.

379 380 381 382 383 384 385 386 387 388 389 390
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.

391
config NETFILTER_XT_TARGET_DSCP
392
	tristate '"DSCP" and "TOS" target support'
393
	depends on IP_NF_MANGLE || IP6_NF_MANGLE
394
	depends on NETFILTER_ADVANCED
395 396 397 398 399 400
	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.

401 402
	  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
403
	  or the Priority field of an IPv6 packet, prior to routing.
404

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

407 408 409 410 411 412 413 414 415 416 417 418 419 420 421
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.

422 423 424 425 426 427 428 429 430 431 432 433
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.

434 435
config NETFILTER_XT_TARGET_LED
	tristate '"LED" target support'
436
	depends on LEDS_CLASS && LEDS_TRIGGERS
437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457
	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
	  Documentation/leds-class.txt

458 459
config NETFILTER_XT_TARGET_MARK
	tristate '"MARK" target support'
460 461 462 463 464 465
	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).
466

467 468
config NETFILTER_XT_TARGET_NFLOG
	tristate '"NFLOG" target support'
469
	default m if NETFILTER_ADVANCED=n
470
	select NETFILTER_NETLINK_LOG
471 472
	help
	  This option enables the NFLOG target, which allows to LOG
473
	  messages through nfnetlink_log.
474 475 476

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

477 478 479 480 481 482 483 484 485 486 487
config NETFILTER_XT_TARGET_NFQUEUE
	tristate '"NFQUEUE" target Support'
	depends on NETFILTER_ADVANCED
	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.

488 489 490
config NETFILTER_XT_TARGET_NOTRACK
	tristate  '"NOTRACK" target support'
	depends on IP_NF_RAW || IP6_NF_RAW
491
	depends on NF_CONNTRACK
492
	depends on NETFILTER_ADVANCED
493 494 495 496 497
	help
	  The NOTRACK target allows a select rule to specify
	  which packets *not* to enter the conntrack/NAT
	  subsystem with all the consequences (no ICMP error tracking,
	  no protocol helpers for the selected packets).
498

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

502 503
config NETFILTER_XT_TARGET_RATEEST
	tristate '"RATEEST" target support'
504
	depends on NETFILTER_ADVANCED
505 506 507 508 509 510 511
	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.

512
config NETFILTER_XT_TARGET_TEE
513
	tristate '"TEE" - packet cloning to alternate destination'
514
	depends on NETFILTER_ADVANCED
515
	depends on (IPV6 || IPV6=n)
516
	depends on !NF_CONNTRACK || NF_CONNTRACK
517 518 519 520
	---help---
	This option adds a "TEE" target with which a packet can be cloned and
	this clone be rerouted to another nexthop.

521 522 523 524 525 526 527
config NETFILTER_XT_TARGET_TPROXY
	tristate '"TPROXY" target support (EXPERIMENTAL)'
	depends on EXPERIMENTAL
	depends on NETFILTER_TPROXY
	depends on NETFILTER_XTABLES
	depends on NETFILTER_ADVANCED
	select NF_DEFRAG_IPV4
528
	select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES
529 530 531 532 533 534 535 536
	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.

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

537 538 539
config NETFILTER_XT_TARGET_TRACE
	tristate  '"TRACE" target support'
	depends on IP_NF_RAW || IP6_NF_RAW
540
	depends on NETFILTER_ADVANCED
541 542 543 544 545 546
	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
547
	  <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
548

549 550
config NETFILTER_XT_TARGET_SECMARK
	tristate '"SECMARK" target support'
551
	depends on NETWORK_SECMARK
552
	default m if NETFILTER_ADVANCED=n
553 554 555 556 557 558
	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.

559 560
config NETFILTER_XT_TARGET_TCPMSS
	tristate '"TCPMSS" target support'
561
	depends on (IPV6 || IPV6=n)
562
	default m if NETFILTER_ADVANCED=n
563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585
	---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.

586 587
config NETFILTER_XT_TARGET_TCPOPTSTRIP
	tristate '"TCPOPTSTRIP" target support (EXPERIMENTAL)'
588
	depends on EXPERIMENTAL
589
	depends on IP_NF_MANGLE || IP6_NF_MANGLE
590
	depends on NETFILTER_ADVANCED
591 592 593 594
	help
	  This option adds a "TCPOPTSTRIP" target, which allows you to strip
	  TCP options from TCP packets.

595 596 597 598
# alphabetically ordered list of matches

comment "Xtables matches"

599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614
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.

615 616
config NETFILTER_XT_MATCH_COMMENT
	tristate  '"comment" match support'
617
	depends on NETFILTER_ADVANCED
618 619 620 621 622
	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
623
	  <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
624 625 626

config NETFILTER_XT_MATCH_CONNBYTES
	tristate  '"connbytes" per-connection counter match support'
627
	depends on NF_CONNTRACK
628
	depends on NETFILTER_ADVANCED
629 630 631 632 633
	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
634
	  <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
635

636 637
config NETFILTER_XT_MATCH_CONNLIMIT
	tristate '"connlimit" match support"'
638
	depends on NF_CONNTRACK
639
	depends on NETFILTER_ADVANCED
640 641 642 643
	---help---
	  This match allows you to match against the number of parallel
	  connections to a server per client IP address (or address block).

644 645
config NETFILTER_XT_MATCH_CONNMARK
	tristate  '"connmark" connection mark match support'
646
	depends on NF_CONNTRACK
647
	depends on NETFILTER_ADVANCED
648 649 650 651 652
	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).
653 654 655

config NETFILTER_XT_MATCH_CONNTRACK
	tristate '"conntrack" connection tracking match support'
656
	depends on NF_CONNTRACK
657
	default m if NETFILTER_ADVANCED=n
658 659 660 661 662 663 664 665
	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 已提交
666 667 668 669 670 671 672 673 674

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.
675 676

config NETFILTER_XT_MATCH_DCCP
677
	tristate '"dccp" protocol match support'
678
	depends on NETFILTER_ADVANCED
679
	default IP_DCCP
680 681 682 683 684 685
	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
686
	  <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
687

688
config NETFILTER_XT_MATCH_DSCP
689
	tristate '"dscp" and "tos" match support'
690
	depends on NETFILTER_ADVANCED
691 692 693 694 695 696
	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.

697 698 699 700
	  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).

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

703
config NETFILTER_XT_MATCH_ESP
704
	tristate '"esp" match support'
705
	depends on NETFILTER_ADVANCED
706 707 708 709 710 711
	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.

712 713
config NETFILTER_XT_MATCH_HASHLIMIT
	tristate '"hashlimit" match support'
714
	depends on (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
715 716 717 718 719 720 721 722 723 724 725 726
	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.

727 728
config NETFILTER_XT_MATCH_HELPER
	tristate '"helper" match support'
729
	depends on NF_CONNTRACK
730
	depends on NETFILTER_ADVANCED
731 732 733 734 735 736
	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.

737 738 739 740 741 742 743 744
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.

745 746 747 748 749 750 751 752 753 754
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.

755 756 757 758 759 760 761 762 763 764
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.

765 766
config NETFILTER_XT_MATCH_LENGTH
	tristate '"length" match support'
767
	depends on NETFILTER_ADVANCED
768 769 770 771 772 773 774 775
	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'
776
	depends on NETFILTER_ADVANCED
777 778 779 780 781 782 783 784 785
	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'
786
	depends on NETFILTER_ADVANCED
787 788 789 790 791 792 793 794
	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'
795 796 797 798 799 800
	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).
801

802 803 804 805 806 807 808 809 810 811
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.

812 813 814 815 816 817 818 819 820 821 822 823 824
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.

825 826
config NETFILTER_XT_MATCH_OWNER
	tristate '"owner" match support'
827
	depends on NETFILTER_ADVANCED
828 829 830 831 832
	---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.

833 834
config NETFILTER_XT_MATCH_POLICY
	tristate 'IPsec "policy" match support'
835
	depends on XFRM
836
	default m if NETFILTER_ADVANCED=n
837 838 839 840 841 842 843
	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.

844 845
config NETFILTER_XT_MATCH_PHYSDEV
	tristate '"physdev" match support'
846
	depends on BRIDGE && BRIDGE_NETFILTER
847
	depends on NETFILTER_ADVANCED
848 849 850 851 852 853 854 855
	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'
856
	depends on NETFILTER_ADVANCED
857 858 859 860 861 862 863 864 865
	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.

866 867
config NETFILTER_XT_MATCH_QUOTA
	tristate '"quota" match support'
868
	depends on NETFILTER_ADVANCED
869 870 871 872 873
	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
874
	  <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
875

876 877
config NETFILTER_XT_MATCH_RATEEST
	tristate '"rateest" match support'
878
	depends on NETFILTER_ADVANCED
879 880 881 882 883 884 885
	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.

886 887
config NETFILTER_XT_MATCH_REALM
	tristate  '"realm" match support'
888
	depends on NETFILTER_ADVANCED
889
	select IP_ROUTE_CLASSID
890 891 892
	help
	  This option adds a `realm' match, which allows you to use the realm
	  key from the routing subsystem inside iptables.
893

894 895
	  This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option 
	  in tc world.
896

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

900 901 902 903 904 905 906 907 908 909
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/>

910
config NETFILTER_XT_MATCH_SCTP
911
	tristate  '"sctp" protocol match support (EXPERIMENTAL)'
912
	depends on EXPERIMENTAL
913
	depends on NETFILTER_ADVANCED
914
	default IP_SCTP
915 916 917 918 919 920
	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
921
	  <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
922

923 924 925 926 927 928
config NETFILTER_XT_MATCH_SOCKET
	tristate '"socket" match support (EXPERIMENTAL)'
	depends on EXPERIMENTAL
	depends on NETFILTER_TPROXY
	depends on NETFILTER_XTABLES
	depends on NETFILTER_ADVANCED
929
	depends on !NF_CONNTRACK || NF_CONNTRACK
930
	select NF_DEFRAG_IPV4
931
	select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES
932 933 934 935 936 937 938 939
	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.

940 941
config NETFILTER_XT_MATCH_STATE
	tristate '"state" match support'
942
	depends on NF_CONNTRACK
943
	default m if NETFILTER_ADVANCED=n
944 945 946 947 948 949 950
	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.

951 952
config NETFILTER_XT_MATCH_STATISTIC
	tristate '"statistic" match support'
953
	depends on NETFILTER_ADVANCED
954
	help
955 956 957 958
	  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.
959

960 961
config NETFILTER_XT_MATCH_STRING
	tristate  '"string" match support'
962
	depends on NETFILTER_ADVANCED
963 964 965 966 967 968 969 970 971 972 973 974
	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'
975
	depends on NETFILTER_ADVANCED
976 977 978 979 980 981 982
	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.

983 984
config NETFILTER_XT_MATCH_TIME
	tristate '"time" match support'
985
	depends on NETFILTER_ADVANCED
986 987 988 989 990 991 992 993 994 995 996
	---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 已提交
997 998
config NETFILTER_XT_MATCH_U32
	tristate '"u32" match support'
999
	depends on NETFILTER_ADVANCED
J
Jan Engelhardt 已提交
1000 1001 1002 1003 1004 1005 1006 1007 1008 1009
	---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.

1010
endif # NETFILTER_XTABLES
1011

1012
endmenu
1013

1014
source "net/netfilter/ipvs/Kconfig"