Kconfig 38.0 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 116
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'.

117 118
config NF_CT_PROTO_DCCP
	tristate 'DCCP protocol connection tracking support (EXPERIMENTAL)'
119
	depends on EXPERIMENTAL
120
	depends on NETFILTER_ADVANCED
121
	default IP_DCCP
122 123 124 125 126 127
	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'.

128 129 130
config NF_CT_PROTO_GRE
	tristate

131
config NF_CT_PROTO_SCTP
132
	tristate 'SCTP protocol connection tracking support (EXPERIMENTAL)'
133
	depends on EXPERIMENTAL
134
	depends on NETFILTER_ADVANCED
135
	default IP_SCTP
136 137 138 139 140
	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
141
	  <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
142

143
config NF_CT_PROTO_UDPLITE
144
	tristate 'UDP-Lite protocol connection tracking support'
145
	depends on NETFILTER_ADVANCED
146 147 148 149 150 151 152
	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.

153
config NF_CONNTRACK_AMANDA
154
	tristate "Amanda backup protocol support"
155
	depends on NETFILTER_ADVANCED
156 157 158 159 160 161 162 163 164 165 166 167
	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.

168
config NF_CONNTRACK_FTP
169
	tristate "FTP protocol support"
170
	default m if NETFILTER_ADVANCED=n
171 172 173 174 175 176 177 178 179 180 181
	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.

182
config NF_CONNTRACK_H323
183
	tristate "H.323 protocol support"
184
	depends on (IPV6 || IPV6=n)
185
	depends on NETFILTER_ADVANCED
186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201
	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.

202
config NF_CONNTRACK_IRC
203
	tristate "IRC protocol support"
204
	default m if NETFILTER_ADVANCED=n
205 206 207 208 209 210 211 212 213 214 215 216
	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.

217 218 219
config NF_CONNTRACK_BROADCAST
	tristate

220
config NF_CONNTRACK_NETBIOS_NS
221
	tristate "NetBIOS name service protocol support"
222
	select NF_CONNTRACK_BROADCAST
223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238
	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.

239 240 241 242 243 244 245 246 247 248 249 250 251 252 253
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.

254
config NF_CONNTRACK_PPTP
255
	tristate "PPtP protocol support"
256
	depends on NETFILTER_ADVANCED
257 258 259 260 261 262 263 264 265 266
	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:
267
	    - Blindly assumes that control connections are always established
268 269 270 271 272
	      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.

273 274
config NF_CONNTRACK_SANE
	tristate "SANE protocol support (EXPERIMENTAL)"
275
	depends on EXPERIMENTAL
276
	depends on NETFILTER_ADVANCED
277 278 279 280 281 282 283 284 285 286
	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.

287
config NF_CONNTRACK_SIP
288
	tristate "SIP protocol support"
289
	default m if NETFILTER_ADVANCED=n
290 291 292 293 294 295 296 297 298
	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.

299
config NF_CONNTRACK_TFTP
300
	tristate "TFTP protocol support"
301
	depends on NETFILTER_ADVANCED
302 303 304 305 306 307 308 309
	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.

310
config NF_CT_NETLINK
311
	tristate 'Connection tracking netlink interface'
312
	select NETFILTER_NETLINK
313
	default m if NETFILTER_ADVANCED=n
314 315 316
	help
	  This option enables support for a netlink-based userspace interface

317 318
endif # NF_CONNTRACK

K
KOVACS Krisztian 已提交
319 320 321 322 323 324 325 326 327 328 329 330 331 332 333
# 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.

334 335
config NETFILTER_XTABLES
	tristate "Netfilter Xtables support (required for ip_tables)"
336
	default m if NETFILTER_ADVANCED=n
337 338 339 340
	help
	  This is required if you intend to use any of ip_tables,
	  ip6_tables or arp_tables.

341 342
if NETFILTER_XTABLES

343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359
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.

360 361 362 363 364 365 366 367 368 369 370 371
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.

372 373 374 375 376 377 378 379 380 381 382 383
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.

384 385
# alphabetically ordered list of targets

386 387
comment "Xtables targets"

388 389 390 391 392 393 394 395 396 397
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.

398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413
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.

414 415
config NETFILTER_XT_TARGET_CLASSIFY
	tristate '"CLASSIFY" target support'
416
	depends on NETFILTER_ADVANCED
417 418 419 420 421 422 423 424 425 426 427
	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'
428
	depends on NF_CONNTRACK
429
	depends on NETFILTER_ADVANCED
430 431 432 433 434
	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).
435

436 437
config NETFILTER_XT_TARGET_CONNSECMARK
	tristate '"CONNSECMARK" target support'
438
	depends on NF_CONNTRACK && NF_CONNTRACK_SECMARK
439 440 441 442 443 444 445 446 447
	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.

448 449 450 451 452 453 454 455 456 457 458 459
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.

460
config NETFILTER_XT_TARGET_DSCP
461
	tristate '"DSCP" and "TOS" target support'
462
	depends on IP_NF_MANGLE || IP6_NF_MANGLE
463
	depends on NETFILTER_ADVANCED
464 465 466 467 468 469
	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.

470 471
	  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
472
	  or the Priority field of an IPv6 packet, prior to routing.
473

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

476 477 478 479 480 481 482 483 484 485 486 487 488 489 490
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.

491 492 493 494 495 496 497 498 499 500 501 502
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.

503 504
config NETFILTER_XT_TARGET_LED
	tristate '"LED" target support'
505
	depends on LEDS_CLASS && LEDS_TRIGGERS
506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524
	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 已提交
525
	  Documentation/leds/leds-class.txt
526

527 528
config NETFILTER_XT_TARGET_MARK
	tristate '"MARK" target support'
529 530 531 532 533 534
	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).
535

536 537
config NETFILTER_XT_TARGET_NFLOG
	tristate '"NFLOG" target support'
538
	default m if NETFILTER_ADVANCED=n
539
	select NETFILTER_NETLINK_LOG
540 541
	help
	  This option enables the NFLOG target, which allows to LOG
542
	  messages through nfnetlink_log.
543 544 545

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

546 547 548
config NETFILTER_XT_TARGET_NFQUEUE
	tristate '"NFQUEUE" target Support'
	depends on NETFILTER_ADVANCED
549
	select NETFILTER_NETLINK_QUEUE
550 551 552 553 554 555 556 557
	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.

558 559 560
config NETFILTER_XT_TARGET_NOTRACK
	tristate  '"NOTRACK" target support'
	depends on IP_NF_RAW || IP6_NF_RAW
561
	depends on NF_CONNTRACK
562 563 564 565 566
	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).
567

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

571 572
config NETFILTER_XT_TARGET_RATEEST
	tristate '"RATEEST" target support'
573
	depends on NETFILTER_ADVANCED
574 575 576 577 578 579 580
	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.

581
config NETFILTER_XT_TARGET_TEE
582
	tristate '"TEE" - packet cloning to alternate destination'
583
	depends on NETFILTER_ADVANCED
584
	depends on (IPV6 || IPV6=n)
585
	depends on !NF_CONNTRACK || NF_CONNTRACK
586 587 588 589
	---help---
	This option adds a "TEE" target with which a packet can be cloned and
	this clone be rerouted to another nexthop.

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

606 607 608
config NETFILTER_XT_TARGET_TRACE
	tristate  '"TRACE" target support'
	depends on IP_NF_RAW || IP6_NF_RAW
609
	depends on NETFILTER_ADVANCED
610 611 612 613 614 615
	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
616
	  <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
617

618 619
config NETFILTER_XT_TARGET_SECMARK
	tristate '"SECMARK" target support'
620
	depends on NETWORK_SECMARK
621
	default m if NETFILTER_ADVANCED=n
622 623 624 625 626 627
	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.

628 629
config NETFILTER_XT_TARGET_TCPMSS
	tristate '"TCPMSS" target support'
630
	depends on (IPV6 || IPV6=n)
631
	default m if NETFILTER_ADVANCED=n
632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654
	---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.

655 656
config NETFILTER_XT_TARGET_TCPOPTSTRIP
	tristate '"TCPOPTSTRIP" target support (EXPERIMENTAL)'
657
	depends on EXPERIMENTAL
658
	depends on IP_NF_MANGLE || IP6_NF_MANGLE
659
	depends on NETFILTER_ADVANCED
660 661 662 663
	help
	  This option adds a "TCPOPTSTRIP" target, which allows you to strip
	  TCP options from TCP packets.

664 665 666 667
# alphabetically ordered list of matches

comment "Xtables matches"

668 669 670 671 672 673 674 675 676 677
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'.

678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693
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.

694 695
config NETFILTER_XT_MATCH_COMMENT
	tristate  '"comment" match support'
696
	depends on NETFILTER_ADVANCED
697 698 699 700 701
	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
702
	  <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
703 704 705

config NETFILTER_XT_MATCH_CONNBYTES
	tristate  '"connbytes" per-connection counter match support'
706
	depends on NF_CONNTRACK
707
	depends on NETFILTER_ADVANCED
708 709 710 711 712
	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
713
	  <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
714

715 716
config NETFILTER_XT_MATCH_CONNLIMIT
	tristate '"connlimit" match support"'
717
	depends on NF_CONNTRACK
718
	depends on NETFILTER_ADVANCED
719 720 721 722
	---help---
	  This match allows you to match against the number of parallel
	  connections to a server per client IP address (or address block).

723 724
config NETFILTER_XT_MATCH_CONNMARK
	tristate  '"connmark" connection mark match support'
725
	depends on NF_CONNTRACK
726
	depends on NETFILTER_ADVANCED
727 728 729 730 731
	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).
732 733 734

config NETFILTER_XT_MATCH_CONNTRACK
	tristate '"conntrack" connection tracking match support'
735
	depends on NF_CONNTRACK
736
	default m if NETFILTER_ADVANCED=n
737 738 739 740 741 742 743 744
	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 已提交
745 746 747 748 749 750 751 752 753

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.
754 755

config NETFILTER_XT_MATCH_DCCP
756
	tristate '"dccp" protocol match support'
757
	depends on NETFILTER_ADVANCED
758
	default IP_DCCP
759 760 761 762 763 764
	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
765
	  <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
766

767 768 769 770 771 772 773 774 775
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.

776
config NETFILTER_XT_MATCH_DSCP
777
	tristate '"dscp" and "tos" match support'
778
	depends on NETFILTER_ADVANCED
779 780 781 782 783 784
	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.

785 786 787 788
	  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).

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

791 792 793 794 795 796 797 798 799
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.

800
config NETFILTER_XT_MATCH_ESP
801
	tristate '"esp" match support'
802
	depends on NETFILTER_ADVANCED
803 804 805 806 807 808
	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.

809 810
config NETFILTER_XT_MATCH_HASHLIMIT
	tristate '"hashlimit" match support'
811
	depends on (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
812 813 814 815 816 817 818 819 820 821 822 823
	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.

824 825
config NETFILTER_XT_MATCH_HELPER
	tristate '"helper" match support'
826
	depends on NF_CONNTRACK
827
	depends on NETFILTER_ADVANCED
828 829 830 831 832 833
	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.

834 835 836 837 838 839 840 841
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.

842 843 844 845 846 847 848 849 850 851
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.

852 853 854 855 856 857 858 859 860 861
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.

862 863
config NETFILTER_XT_MATCH_LENGTH
	tristate '"length" match support'
864
	depends on NETFILTER_ADVANCED
865 866 867 868 869 870 871 872
	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'
873
	depends on NETFILTER_ADVANCED
874 875 876 877 878 879 880 881 882
	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'
883
	depends on NETFILTER_ADVANCED
884 885 886 887 888 889 890 891
	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'
892 893 894 895 896 897
	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).
898

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

909 910
config NETFILTER_XT_MATCH_NFACCT
	tristate '"nfacct" match support'
911
	depends on NETFILTER_ADVANCED
912 913 914 915 916 917 918
	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.

919 920 921 922 923 924 925 926 927 928 929 930 931
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.

932 933
config NETFILTER_XT_MATCH_OWNER
	tristate '"owner" match support'
934
	depends on NETFILTER_ADVANCED
935 936 937 938 939
	---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.

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

951 952
config NETFILTER_XT_MATCH_PHYSDEV
	tristate '"physdev" match support'
953
	depends on BRIDGE && BRIDGE_NETFILTER
954
	depends on NETFILTER_ADVANCED
955 956 957 958 959 960 961 962
	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'
963
	depends on NETFILTER_ADVANCED
964 965 966 967 968 969 970 971 972
	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.

973 974
config NETFILTER_XT_MATCH_QUOTA
	tristate '"quota" match support'
975
	depends on NETFILTER_ADVANCED
976 977 978 979 980
	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
981
	  <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
982

983 984
config NETFILTER_XT_MATCH_RATEEST
	tristate '"rateest" match support'
985
	depends on NETFILTER_ADVANCED
986 987 988 989 990 991 992
	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.

993 994
config NETFILTER_XT_MATCH_REALM
	tristate  '"realm" match support'
995
	depends on NETFILTER_ADVANCED
996
	select IP_ROUTE_CLASSID
997 998 999
	help
	  This option adds a `realm' match, which allows you to use the realm
	  key from the routing subsystem inside iptables.
1000

1001 1002
	  This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option 
	  in tc world.
1003

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

1007 1008 1009 1010 1011 1012 1013 1014 1015 1016
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/>

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

1030 1031 1032 1033 1034 1035
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
1036
	depends on !NF_CONNTRACK || NF_CONNTRACK
1037
	select NF_DEFRAG_IPV4
1038
	select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES
1039 1040 1041 1042 1043 1044 1045 1046
	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.

1047 1048
config NETFILTER_XT_MATCH_STATE
	tristate '"state" match support'
1049
	depends on NF_CONNTRACK
1050
	default m if NETFILTER_ADVANCED=n
1051 1052 1053 1054 1055 1056 1057
	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.

1058 1059
config NETFILTER_XT_MATCH_STATISTIC
	tristate '"statistic" match support'
1060
	depends on NETFILTER_ADVANCED
1061
	help
1062 1063 1064 1065
	  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.
1066

1067 1068
config NETFILTER_XT_MATCH_STRING
	tristate  '"string" match support'
1069
	depends on NETFILTER_ADVANCED
1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081
	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'
1082
	depends on NETFILTER_ADVANCED
1083 1084 1085 1086 1087 1088 1089
	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.

1090 1091
config NETFILTER_XT_MATCH_TIME
	tristate '"time" match support'
1092
	depends on NETFILTER_ADVANCED
1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103
	---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 已提交
1104 1105
config NETFILTER_XT_MATCH_U32
	tristate '"u32" match support'
1106
	depends on NETFILTER_ADVANCED
J
Jan Engelhardt 已提交
1107 1108 1109 1110 1111 1112 1113 1114 1115 1116
	---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.

1117
endif # NETFILTER_XTABLES
1118

1119
endmenu
1120

1121 1122
source "net/netfilter/ipset/Kconfig"

1123
source "net/netfilter/ipvs/Kconfig"