Kconfig 27.9 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 36 37 38 39 40 41
	  This is required to do Masquerading or other kinds of Network
	  Address Translation (except for Fast NAT).  It can also be used to
	  enhance packet filtering (see `Connection state match support'
	  below).

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

42 43
config NF_CT_ACCT
	bool "Connection tracking flow accounting"
44
	depends on NETFILTER_ADVANCED
45 46 47 48 49 50 51 52 53 54 55 56
	depends on NF_CONNTRACK
	help
	  If this option is enabled, the connection tracking code will
	  keep per-flow packet and byte counters.

	  Those counters can be used for flow-based accounting or the
	  `connbytes' match.

	  If unsure, say `N'.

config NF_CONNTRACK_MARK
	bool  'Connection mark tracking support'
57
	depends on NETFILTER_ADVANCED
58 59 60 61 62 63 64
	depends on NF_CONNTRACK
	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.

65 66 67
config NF_CONNTRACK_SECMARK
	bool  'Connection tracking security mark support'
	depends on NF_CONNTRACK && NETWORK_SECMARK
68
	default m if NETFILTER_ADVANCED=n
69 70 71 72 73 74 75 76 77
	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'.

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

	  If unsure, say `N'.

89 90
config NF_CT_PROTO_GRE
	tristate
91
	depends on NF_CONNTRACK
92

93
config NF_CT_PROTO_SCTP
94
	tristate 'SCTP protocol connection tracking support (EXPERIMENTAL)'
95
	depends on EXPERIMENTAL && NF_CONNTRACK
96
	depends on NETFILTER_ADVANCED
97 98 99 100 101
	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
102
	  <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
103

104 105 106
config NF_CT_PROTO_UDPLITE
	tristate 'UDP-Lite protocol connection tracking support (EXPERIMENTAL)'
	depends on EXPERIMENTAL && NF_CONNTRACK
107
	depends on NETFILTER_ADVANCED
108 109 110 111 112 113 114
	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.

115
config NF_CONNTRACK_AMANDA
116 117
	tristate "Amanda backup protocol support"
	depends on NF_CONNTRACK
118
	depends on NETFILTER_ADVANCED
119 120 121 122 123 124 125 126 127 128 129 130
	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.

131
config NF_CONNTRACK_FTP
132 133
	tristate "FTP protocol support"
	depends on NF_CONNTRACK
134
	default m if NETFILTER_ADVANCED=n
135 136 137 138 139 140 141 142 143 144 145
	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.

146 147
config NF_CONNTRACK_H323
	tristate "H.323 protocol support (EXPERIMENTAL)"
148
	depends on EXPERIMENTAL && NF_CONNTRACK && (IPV6 || IPV6=n)
149
	depends on NETFILTER_ADVANCED
150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165
	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.

166
config NF_CONNTRACK_IRC
167 168
	tristate "IRC protocol support"
	depends on NF_CONNTRACK
169
	default m if NETFILTER_ADVANCED=n
170 171 172 173 174 175 176 177 178 179 180 181
	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.

182 183 184
config NF_CONNTRACK_NETBIOS_NS
	tristate "NetBIOS name service protocol support (EXPERIMENTAL)"
	depends on EXPERIMENTAL && NF_CONNTRACK
185
	depends on NETFILTER_ADVANCED
186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201
	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.

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

222 223 224
config NF_CONNTRACK_SANE
	tristate "SANE protocol support (EXPERIMENTAL)"
	depends on EXPERIMENTAL && NF_CONNTRACK
225
	depends on NETFILTER_ADVANCED
226 227 228 229 230 231 232 233 234 235
	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.

236 237 238
config NF_CONNTRACK_SIP
	tristate "SIP protocol support (EXPERIMENTAL)"
	depends on EXPERIMENTAL && NF_CONNTRACK
239
	default m if NETFILTER_ADVANCED=n
240 241 242 243 244 245 246 247 248
	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.

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

261 262
config NF_CT_NETLINK
	tristate 'Connection tracking netlink interface (EXPERIMENTAL)'
263 264
	depends on EXPERIMENTAL && NF_CONNTRACK
	select NETFILTER_NETLINK
265
	depends on NF_NAT=n || NF_NAT
266
	default m if NETFILTER_ADVANCED=n
267 268 269
	help
	  This option enables support for a netlink-based userspace interface

270 271
config NETFILTER_XTABLES
	tristate "Netfilter Xtables support (required for ip_tables)"
272
	default m if NETFILTER_ADVANCED=n
273 274 275 276 277 278 279 280 281
	help
	  This is required if you intend to use any of ip_tables,
	  ip6_tables or arp_tables.

# alphabetically ordered list of targets

config NETFILTER_XT_TARGET_CLASSIFY
	tristate '"CLASSIFY" target support'
	depends on NETFILTER_XTABLES
282
	depends on NETFILTER_ADVANCED
283 284 285 286 287 288 289 290 291 292 293 294 295
	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'
	depends on NETFILTER_XTABLES
	depends on IP_NF_MANGLE || IP6_NF_MANGLE
296
	depends on NF_CONNTRACK
297
	depends on NETFILTER_ADVANCED
298
	select NF_CONNTRACK_MARK
299 300 301 302
	help
	  This option adds a `CONNMARK' target, which allows one to manipulate
	  the connection mark value.  Similar to the MARK target, but
	  affects the connection mark value rather than the packet mark value.
303

304
	  If you want to compile it as a module, say M here and read
305 306
	  <file:Documentation/kbuild/modules.txt>.  The module will be called
	  ipt_CONNMARK.ko.  If unsure, say `N'.
307

308
config NETFILTER_XT_TARGET_DSCP
309
	tristate '"DSCP" and "TOS" target support'
310 311
	depends on NETFILTER_XTABLES
	depends on IP_NF_MANGLE || IP6_NF_MANGLE
312
	depends on NETFILTER_ADVANCED
313 314 315 316 317 318
	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.

319 320
	  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
321
	  or the Priority field of an IPv6 packet, prior to routing.
322

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

325 326 327
config NETFILTER_XT_TARGET_MARK
	tristate '"MARK" target support'
	depends on NETFILTER_XTABLES
328
	default m if NETFILTER_ADVANCED=n
329 330 331 332 333 334 335 336 337 338 339 340 341
	help
	  This option adds a `MARK' target, which allows you to create rules
	  in the `mangle' table which alter the netfilter mark (nfmark) field
	  associated with the packet prior to routing. This can change
	  the routing method (see `Use netfilter MARK value as routing
	  key') and can also be used by other subsystems to change their
	  behavior.

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

config NETFILTER_XT_TARGET_NFQUEUE
	tristate '"NFQUEUE" target Support'
	depends on NETFILTER_XTABLES
342
	depends on NETFILTER_ADVANCED
343
	help
T
Thomas Vgtle 已提交
344
	  This target replaced the old obsolete QUEUE target.
345 346 347 348 349 350

	  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.

351 352 353
config NETFILTER_XT_TARGET_NFLOG
	tristate '"NFLOG" target support'
	depends on NETFILTER_XTABLES
354
	default m if NETFILTER_ADVANCED=n
355 356 357 358 359 360 361 362
	help
	  This option enables the NFLOG target, which allows to LOG
	  messages through the netfilter logging API, which can use
	  either the old LOG target, the old ULOG target or nfnetlink_log
	  as backend.

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

363 364 365 366
config NETFILTER_XT_TARGET_NOTRACK
	tristate  '"NOTRACK" target support'
	depends on NETFILTER_XTABLES
	depends on IP_NF_RAW || IP6_NF_RAW
367
	depends on NF_CONNTRACK
368
	depends on NETFILTER_ADVANCED
369 370 371 372 373
	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).
374

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

378 379 380
config NETFILTER_XT_TARGET_RATEEST
	tristate '"RATEEST" target support'
	depends on NETFILTER_XTABLES
381
	depends on NETFILTER_ADVANCED
382 383 384 385 386 387 388
	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.

389 390 391 392
config NETFILTER_XT_TARGET_TRACE
	tristate  '"TRACE" target support'
	depends on NETFILTER_XTABLES
	depends on IP_NF_RAW || IP6_NF_RAW
393
	depends on NETFILTER_ADVANCED
394 395 396 397 398 399
	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
400
	  <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
401

402 403 404
config NETFILTER_XT_TARGET_SECMARK
	tristate '"SECMARK" target support'
	depends on NETFILTER_XTABLES && NETWORK_SECMARK
405
	default m if NETFILTER_ADVANCED=n
406 407 408 409 410 411
	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.

412 413
config NETFILTER_XT_TARGET_CONNSECMARK
	tristate '"CONNSECMARK" target support'
414
	depends on NETFILTER_XTABLES && NF_CONNTRACK && NF_CONNTRACK_SECMARK
415
	default m if NETFILTER_ADVANCED=n
416 417 418 419 420 421 422 423
	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.

424 425 426
config NETFILTER_XT_TARGET_TCPMSS
	tristate '"TCPMSS" target support'
	depends on NETFILTER_XTABLES && (IPV6 || IPV6=n)
427
	default m if NETFILTER_ADVANCED=n
428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450
	---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.

451 452 453 454
config NETFILTER_XT_TARGET_TCPOPTSTRIP
	tristate '"TCPOPTSTRIP" target support (EXPERIMENTAL)'
	depends on EXPERIMENTAL && NETFILTER_XTABLES
	depends on IP_NF_MANGLE || IP6_NF_MANGLE
455
	depends on NETFILTER_ADVANCED
456 457 458 459
	help
	  This option adds a "TCPOPTSTRIP" target, which allows you to strip
	  TCP options from TCP packets.

460 461 462
config NETFILTER_XT_MATCH_COMMENT
	tristate  '"comment" match support'
	depends on NETFILTER_XTABLES
463
	depends on NETFILTER_ADVANCED
464 465 466 467 468
	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
469
	  <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
470 471 472 473

config NETFILTER_XT_MATCH_CONNBYTES
	tristate  '"connbytes" per-connection counter match support'
	depends on NETFILTER_XTABLES
474
	depends on NF_CONNTRACK
475
	depends on NETFILTER_ADVANCED
476
	select NF_CT_ACCT
477 478 479 480 481
	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
482
	  <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
483

484 485 486
config NETFILTER_XT_MATCH_CONNLIMIT
	tristate '"connlimit" match support"'
	depends on NETFILTER_XTABLES
487
	depends on NF_CONNTRACK
488
	depends on NETFILTER_ADVANCED
489 490 491 492
	---help---
	  This match allows you to match against the number of parallel
	  connections to a server per client IP address (or address block).

493 494 495
config NETFILTER_XT_MATCH_CONNMARK
	tristate  '"connmark" connection mark match support'
	depends on NETFILTER_XTABLES
496
	depends on NF_CONNTRACK
497
	depends on NETFILTER_ADVANCED
498
	select NF_CONNTRACK_MARK
499 500 501
	help
	  This option adds a `connmark' match, which allows you to match the
	  connection mark value previously set for the session by `CONNMARK'. 
502

503
	  If you want to compile it as a module, say M here and read
504 505
	  <file:Documentation/kbuild/modules.txt>.  The module will be called
	  ipt_connmark.ko.  If unsure, say `N'.
506 507 508 509

config NETFILTER_XT_MATCH_CONNTRACK
	tristate '"conntrack" connection tracking match support'
	depends on NETFILTER_XTABLES
510
	depends on NF_CONNTRACK
511
	default m if NETFILTER_ADVANCED=n
512 513 514 515 516 517 518 519 520 521
	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.

config NETFILTER_XT_MATCH_DCCP
522
	tristate '"dccp" protocol match support'
523
	depends on NETFILTER_XTABLES
524
	depends on NETFILTER_ADVANCED
525 526 527 528 529 530
	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
531
	  <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
532

533
config NETFILTER_XT_MATCH_DSCP
534
	tristate '"dscp" and "tos" match support'
535
	depends on NETFILTER_XTABLES
536
	depends on NETFILTER_ADVANCED
537 538 539 540 541 542
	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.

543 544 545 546
	  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).

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

549
config NETFILTER_XT_MATCH_ESP
550
	tristate '"esp" match support'
551
	depends on NETFILTER_XTABLES
552
	depends on NETFILTER_ADVANCED
553 554 555 556 557 558
	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.

559 560 561
config NETFILTER_XT_MATCH_HELPER
	tristate '"helper" match support'
	depends on NETFILTER_XTABLES
562
	depends on NF_CONNTRACK
563
	depends on NETFILTER_ADVANCED
564 565 566 567 568 569 570 571 572
	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.

config NETFILTER_XT_MATCH_LENGTH
	tristate '"length" match support'
	depends on NETFILTER_XTABLES
573
	depends on NETFILTER_ADVANCED
574 575 576 577 578 579 580 581 582
	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'
	depends on NETFILTER_XTABLES
583
	depends on NETFILTER_ADVANCED
584 585 586 587 588 589 590 591 592 593
	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'
	depends on NETFILTER_XTABLES
594
	depends on NETFILTER_ADVANCED
595 596 597 598 599 600 601 602 603
	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'
	depends on NETFILTER_XTABLES
604
	default m if NETFILTER_ADVANCED=n
605 606 607 608 609 610 611
	help
	  Netfilter mark matching allows you to match packets based on the
	  `nfmark' value in the packet.  This can be set by the MARK target
	  (see below).

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

612 613 614
config NETFILTER_XT_MATCH_OWNER
	tristate '"owner" match support'
	depends on NETFILTER_XTABLES
615
	depends on NETFILTER_ADVANCED
616 617 618 619 620
	---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.

621 622 623
config NETFILTER_XT_MATCH_POLICY
	tristate 'IPsec "policy" match support'
	depends on NETFILTER_XTABLES && XFRM
624
	default m if NETFILTER_ADVANCED=n
625 626 627 628 629 630 631
	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.

632
config NETFILTER_XT_MATCH_MULTIPORT
633
	tristate '"multiport" Multiple port match support'
634
	depends on NETFILTER_XTABLES
635
	depends on NETFILTER_ADVANCED
636 637 638 639 640 641 642
	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.

643 644
config NETFILTER_XT_MATCH_PHYSDEV
	tristate '"physdev" match support'
645
	depends on NETFILTER_XTABLES && BRIDGE && BRIDGE_NETFILTER
646
	depends on NETFILTER_ADVANCED
647 648 649 650 651 652 653 654 655
	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'
	depends on NETFILTER_XTABLES
656
	depends on NETFILTER_ADVANCED
657 658 659 660 661 662 663 664 665
	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.

666 667 668
config NETFILTER_XT_MATCH_QUOTA
	tristate '"quota" match support'
	depends on NETFILTER_XTABLES
669
	depends on NETFILTER_ADVANCED
670 671 672 673 674
	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
675
	  <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
676

677 678 679
config NETFILTER_XT_MATCH_RATEEST
	tristate '"rateest" match support'
	depends on NETFILTER_XTABLES
680
	depends on NETFILTER_ADVANCED
681 682 683 684 685 686 687
	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.

688 689 690
config NETFILTER_XT_MATCH_REALM
	tristate  '"realm" match support'
	depends on NETFILTER_XTABLES
691
	depends on NETFILTER_ADVANCED
692 693 694 695
	select NET_CLS_ROUTE
	help
	  This option adds a `realm' match, which allows you to use the realm
	  key from the routing subsystem inside iptables.
696

697 698
	  This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option 
	  in tc world.
699

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

config NETFILTER_XT_MATCH_SCTP
704 705
	tristate  '"sctp" protocol match support (EXPERIMENTAL)'
	depends on NETFILTER_XTABLES && EXPERIMENTAL
706
	depends on NETFILTER_ADVANCED
707 708 709 710 711 712
	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
713
	  <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
714 715 716 717

config NETFILTER_XT_MATCH_STATE
	tristate '"state" match support'
	depends on NETFILTER_XTABLES
718
	depends on NF_CONNTRACK
719
	default m if NETFILTER_ADVANCED=n
720 721 722 723 724 725 726
	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.

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

737 738 739
config NETFILTER_XT_MATCH_STRING
	tristate  '"string" match support'
	depends on NETFILTER_XTABLES
740
	depends on NETFILTER_ADVANCED
741 742 743 744 745 746 747 748 749 750 751 752 753
	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'
	depends on NETFILTER_XTABLES
754
	depends on NETFILTER_ADVANCED
755 756 757 758 759 760 761
	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.

762 763 764
config NETFILTER_XT_MATCH_TIME
	tristate '"time" match support'
	depends on NETFILTER_XTABLES
765
	depends on NETFILTER_ADVANCED
766 767 768 769 770 771 772 773 774 775 776
	---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 已提交
777 778 779
config NETFILTER_XT_MATCH_U32
	tristate '"u32" match support'
	depends on NETFILTER_XTABLES
780
	depends on NETFILTER_ADVANCED
J
Jan Engelhardt 已提交
781 782 783 784 785 786 787 788 789 790
	---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.

791 792
config NETFILTER_XT_MATCH_HASHLIMIT
	tristate '"hashlimit" match support'
793
	depends on NETFILTER_XTABLES && (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
794
	depends on NETFILTER_ADVANCED
795 796 797 798 799 800 801 802 803 804 805
	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.

806 807
endmenu