Kconfig 52.7 KB
Newer Older
1
# SPDX-License-Identifier: GPL-2.0-only
2
menu "Core Netfilter Configuration"
3
	depends on INET && NETFILTER
4

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

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

16 17 18 19 20 21
config NETFILTER_FAMILY_BRIDGE
	bool

config NETFILTER_FAMILY_ARP
	bool

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

30 31
config NETFILTER_NETLINK_QUEUE
	tristate "Netfilter NFQUEUE over NFNETLINK interface"
32
	depends on NETFILTER_ADVANCED
33
	select NETFILTER_NETLINK
34
	help
T
Thomas Vgtle 已提交
35
	  If this option is enabled, the kernel will include support
36
	  for queueing packets via NFNETLINK.
37

38 39
config NETFILTER_NETLINK_LOG
	tristate "Netfilter LOG over NFNETLINK interface"
40
	default m if NETFILTER_ADVANCED=n
41
	select NETFILTER_NETLINK
42 43 44 45 46 47 48 49
	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.

50 51 52 53 54 55 56 57
config NETFILTER_NETLINK_OSF
	tristate "Netfilter OSF over NFNETLINK interface"
	depends on NETFILTER_ADVANCED
	select NETFILTER_NETLINK
	help
	  If this option is enabled, the kernel will include support
	  for passive OS fingerprint via NFNETLINK.

58
config NF_CONNTRACK
59
	tristate "Netfilter connection tracking support"
60
	default m if NETFILTER_ADVANCED=n
61 62
	select NF_DEFRAG_IPV4
	select NF_DEFRAG_IPV6 if IPV6 != n
63
	help
64 65 66 67
	  Connection tracking keeps a record of what packets have passed
	  through your machine, in order to figure out how they are related
	  into connections.

68
	  This is required to do Masquerading or other kinds of Network
69 70
	  Address Translation.  It can also be used to enhance packet
	  filtering (see `Connection state match support' below).
71 72 73

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

74 75 76
config NF_LOG_COMMON
	tristate

77 78 79 80 81 82 83 84 85 86 87 88
config NF_LOG_SYSLOG
	tristate "Syslog packet logging"
	default m if NETFILTER_ADVANCED=n
	select NF_LOG_COMMON
	help
	  This option enable support for packet logging via syslog.
	  It supports IPv4 and common transport protocols such as TCP and UDP.
	  This is a simpler but less flexible logging method compared to
	  CONFIG_NETFILTER_NETLINK_LOG.
	  If both are enabled the backend to use can be configured at run-time
	  by means of per-address-family sysctl tunables.

89
if NF_CONNTRACK
90 91
config NETFILTER_CONNCOUNT
	tristate
92

93 94
config NF_CONNTRACK_MARK
	bool  'Connection mark tracking support'
95
	depends on NETFILTER_ADVANCED
96 97 98 99 100 101
	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.

102 103
config NF_CONNTRACK_SECMARK
	bool  'Connection tracking security mark support'
104
	depends on NETWORK_SECMARK
105
	default m if NETFILTER_ADVANCED=n
106 107 108 109 110 111 112 113 114
	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'.

115 116 117 118 119 120 121 122 123 124 125 126
config NF_CONNTRACK_ZONES
	bool  'Connection tracking zones'
	depends on NETFILTER_ADVANCED
	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'.

127 128 129 130
config NF_CONNTRACK_PROCFS
	bool "Supply CT list in procfs (OBSOLETE)"
	default y
	depends on PROC_FS
131
	help
132 133 134 135 136
	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.

137
config NF_CONNTRACK_EVENTS
138
	bool "Connection tracking events"
139
	depends on NETFILTER_ADVANCED
140 141 142
	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 已提交
143
	  to get notified about changes in the connection tracking state.
144 145 146

	  If unsure, say `N'.

147 148 149 150 151 152 153 154 155 156
config NF_CONNTRACK_TIMEOUT
	bool  'Connection tracking timeout'
	depends on NETFILTER_ADVANCED
	help
	  This option enables support for connection tracking timeout
	  extension. This allows you to attach timeout policies to flow
	  via the CT target.

	  If unsure, say `N'.

157 158 159 160 161 162 163 164 165 166 167
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'.

168
config NF_CONNTRACK_LABELS
169
	bool "Connection tracking labels"
170 171
	help
	  This option enables support for assigning user-defined flag bits
172 173
	  to connection tracking entries.  It can be used with xtables connlabel
	  match and the nftables ct expression.
174

175
config NF_CT_PROTO_DCCP
176
	bool 'DCCP protocol connection tracking support'
177
	depends on NETFILTER_ADVANCED
178
	default y
179 180 181 182
	help
	  With this option enabled, the layer 3 independent connection
	  tracking code will be able to do state tracking on DCCP connections.

183
	  If unsure, say Y.
184

185
config NF_CT_PROTO_GRE
186
	bool
187

188
config NF_CT_PROTO_SCTP
189
	bool 'SCTP protocol connection tracking support'
190
	depends on NETFILTER_ADVANCED
191
	default y
192
	select LIBCRC32C
193 194 195 196
	help
	  With this option enabled, the layer 3 independent connection
	  tracking code will be able to do state tracking on SCTP connections.

197
	  If unsure, say Y.
198

199
config NF_CT_PROTO_UDPLITE
200
	bool 'UDP-Lite protocol connection tracking support'
201
	depends on NETFILTER_ADVANCED
202
	default y
203 204 205 206 207
	help
	  With this option enabled, the layer 3 independent connection
	  tracking code will be able to do state tracking on UDP-Lite
	  connections.

208
	  If unsure, say Y.
209

210
config NF_CONNTRACK_AMANDA
211
	tristate "Amanda backup protocol support"
212
	depends on NETFILTER_ADVANCED
213 214 215 216 217 218 219 220 221 222 223 224
	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.

225
config NF_CONNTRACK_FTP
226
	tristate "FTP protocol support"
227
	default m if NETFILTER_ADVANCED=n
228 229 230 231 232 233 234 235 236
	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.

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

237
config NF_CONNTRACK_H323
238
	tristate "H.323 protocol support"
239
	depends on IPV6 || IPV6=n
240
	depends on NETFILTER_ADVANCED
241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256
	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.

257
config NF_CONNTRACK_IRC
258
	tristate "IRC protocol support"
259
	default m if NETFILTER_ADVANCED=n
260 261 262 263 264 265 266 267 268 269 270 271
	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.

272 273 274
config NF_CONNTRACK_BROADCAST
	tristate

275
config NF_CONNTRACK_NETBIOS_NS
276
	tristate "NetBIOS name service protocol support"
277
	select NF_CONNTRACK_BROADCAST
278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293
	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.

294 295 296 297 298 299 300 301 302 303 304 305 306 307 308
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.

309
config NF_CONNTRACK_PPTP
310
	tristate "PPtP protocol support"
311
	depends on NETFILTER_ADVANCED
312 313 314 315 316 317 318 319 320 321
	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:
322
	    - Blindly assumes that control connections are always established
323 324 325 326 327
	      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.

328
config NF_CONNTRACK_SANE
329
	tristate "SANE protocol support"
330
	depends on NETFILTER_ADVANCED
331 332 333 334 335 336 337 338 339 340
	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.

341
config NF_CONNTRACK_SIP
342
	tristate "SIP protocol support"
343
	default m if NETFILTER_ADVANCED=n
344 345 346
	help
	  SIP is an application-layer control protocol that can establish,
	  modify, and terminate multimedia sessions (conferences) such as
347
	  Internet telephony calls. With the nf_conntrack_sip and
348 349 350 351 352
	  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.

353
config NF_CONNTRACK_TFTP
354
	tristate "TFTP protocol support"
355
	depends on NETFILTER_ADVANCED
356 357 358 359 360 361 362 363
	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.

364
config NF_CT_NETLINK
365
	tristate 'Connection tracking netlink interface'
366
	select NETFILTER_NETLINK
367
	default m if NETFILTER_ADVANCED=n
368 369 370
	help
	  This option enables support for a netlink-based userspace interface

371 372 373 374
config NF_CT_NETLINK_TIMEOUT
	tristate  'Connection tracking timeout tuning via Netlink'
	select NETFILTER_NETLINK
	depends on NETFILTER_ADVANCED
375
	depends on NF_CONNTRACK_TIMEOUT
376 377 378 379 380 381 382
	help
	  This option enables support for connection tracking timeout
	  fine-grain tuning. This allows you to attach specific timeout
	  policies to flows, instead of using the global timeout policy.

	  If unsure, say `N'.

383 384 385 386 387
config NF_CT_NETLINK_HELPER
	tristate 'Connection tracking helpers in user-space via Netlink'
	select NETFILTER_NETLINK
	depends on NF_CT_NETLINK
	depends on NETFILTER_NETLINK_QUEUE
388
	depends on NETFILTER_NETLINK_GLUE_CT
389 390 391 392 393 394 395
	depends on NETFILTER_ADVANCED
	help
	  This option enables the user-space connection tracking helpers
	  infrastructure.

	  If unsure, say `N'.

396
config NETFILTER_NETLINK_GLUE_CT
397
	bool "NFQUEUE and NFLOG integration with Connection Tracking"
398
	default n
399
	depends on (NETFILTER_NETLINK_QUEUE || NETFILTER_NETLINK_LOG) && NF_CT_NETLINK
400
	help
401 402 403
	  If this option is enabled, NFQUEUE and NFLOG can include
	  Connection Tracking information together with the packet is
	  the enqueued via NFNETLINK.
404

405
config NF_NAT
406 407 408 409 410 411 412
	tristate "Network Address Translation support"
	depends on NF_CONNTRACK
	default m if NETFILTER_ADVANCED=n
	help
	  The NAT option allows masquerading, port forwarding and other
	  forms of full Network Address Port Translation. This can be
	  controlled by iptables, ip6tables or nft.
413

414 415 416 417 418
config NF_NAT_AMANDA
	tristate
	depends on NF_CONNTRACK && NF_NAT
	default NF_NAT && NF_CONNTRACK_AMANDA

419 420 421 422 423
config NF_NAT_FTP
	tristate
	depends on NF_CONNTRACK && NF_NAT
	default NF_NAT && NF_CONNTRACK_FTP

424 425 426 427 428
config NF_NAT_IRC
	tristate
	depends on NF_CONNTRACK && NF_NAT
	default NF_NAT && NF_CONNTRACK_IRC

429 430 431 432 433
config NF_NAT_SIP
	tristate
	depends on NF_CONNTRACK && NF_NAT
	default NF_NAT && NF_CONNTRACK_SIP

434 435 436 437 438
config NF_NAT_TFTP
	tristate
	depends on NF_CONNTRACK && NF_NAT
	default NF_NAT && NF_CONNTRACK_TFTP

439
config NF_NAT_REDIRECT
440
	bool
441

442 443 444
config NF_NAT_MASQUERADE
	bool

445 446 447
config NETFILTER_SYNPROXY
	tristate

448 449
endif # NF_CONNTRACK

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

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

466
if NF_TABLES
467
config NF_TABLES_INET
468
	depends on IPV6
469 470
	select NF_TABLES_IPV4
	select NF_TABLES_IPV6
471
	bool "Netfilter nf_tables mixed IPv4/IPv6 tables support"
472 473 474
	help
	  This option enables support for a mixed IPv4/IPv6 "inet" table.

475
config NF_TABLES_NETDEV
476
	bool "Netfilter nf_tables netdev tables support"
477 478 479
	help
	  This option enables support for the "netdev" table.

480 481 482 483 484 485
config NFT_NUMGEN
	tristate "Netfilter nf_tables number generator module"
	help
	  This option adds the number generator expression used to perform
	  incremental counting and random numbers bound to a upper limit.

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

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

P
Patrick McHardy 已提交
500 501
config NFT_COUNTER
	tristate "Netfilter nf_tables counter module"
502 503 504
	help
	  This option adds the "counter" expression that you can use to
	  include packet and byte counters in a rule.
P
Patrick McHardy 已提交
505

506 507 508 509 510 511 512 513 514
config NFT_CONNLIMIT
	tristate "Netfilter nf_tables connlimit module"
	depends on NF_CONNTRACK
	depends on NETFILTER_ADVANCED
	select NETFILTER_CONNCOUNT
	help
	  This option adds the "connlimit" expression that you can use to
	  ratelimit rule matchings per connections.

P
Patrick McHardy 已提交
515 516
config NFT_LOG
	tristate "Netfilter nf_tables log module"
517 518 519
	help
	  This option adds the "log" expression that you can use to log
	  packets matching some criteria.
P
Patrick McHardy 已提交
520 521 522

config NFT_LIMIT
	tristate "Netfilter nf_tables limit module"
523 524 525
	help
	  This option adds the "limit" expression that you can use to
	  ratelimit rule matchings.
P
Patrick McHardy 已提交
526

527 528 529
config NFT_MASQ
	depends on NF_CONNTRACK
	depends on NF_NAT
530
	select NF_NAT_MASQUERADE
531 532 533 534 535
	tristate "Netfilter nf_tables masquerade support"
	help
	  This option adds the "masquerade" expression that you can use
	  to perform NAT in the masquerade flavour.

536 537 538 539
config NFT_REDIR
	depends on NF_CONNTRACK
	depends on NF_NAT
	tristate "Netfilter nf_tables redirect support"
540
	select NF_NAT_REDIRECT
541 542 543 544
	help
	  This options adds the "redirect" expression that you can use
	  to perform NAT in the redirect flavour.

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

554 555 556 557 558 559
config NFT_TUNNEL
	tristate "Netfilter nf_tables tunnel module"
	help
	  This option adds the "tunnel" expression that you can use to set
	  tunneling policies.

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

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

573 574 575 576 577 578
config NFT_QUOTA
	tristate "Netfilter nf_tables quota module"
	help
	  This option adds the "quota" expression that you can use to match
	  enforce bytes quotas.

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

588 589 590 591 592
config NFT_REJECT_INET
	depends on NF_TABLES_INET
	default NFT_REJECT
	tristate

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

601 602 603 604 605 606
config NFT_HASH
	tristate "Netfilter nf_tables hash module"
	help
	  This option adds the "hash" expression that you can use to perform
	  a hash operation on registers.

607 608 609 610 611 612 613 614 615 616 617 618 619
config NFT_FIB
	tristate

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

620 621 622 623 624 625 626
config NFT_XFRM
	tristate "Netfilter nf_tables xfrm/IPSec security association matching"
	depends on XFRM
	help
	  This option adds an expression that you can use to extract properties
	  of a packets security association.

627 628 629 630
config NFT_SOCKET
	tristate "Netfilter nf_tables socket match support"
	depends on IPV6 || IPV6=n
	select NF_SOCKET_IPV4
631
	select NF_SOCKET_IPV6 if NF_TABLES_IPV6
632 633 634 635
	help
	  This option allows matching for the presence or absence of a
	  corresponding socket and its attributes.

636 637 638 639 640 641 642
config NFT_OSF
	tristate "Netfilter nf_tables passive OS fingerprint support"
	depends on NETFILTER_ADVANCED
	select NETFILTER_NETLINK_OSF
	help
	  This option allows matching packets from an specific OS.

643 644 645 646 647 648 649 650 651 652
config NFT_TPROXY
	tristate "Netfilter nf_tables tproxy support"
	depends on IPV6 || IPV6=n
	select NF_DEFRAG_IPV4
	select NF_DEFRAG_IPV6 if NF_TABLES_IPV6
	select NF_TPROXY_IPV4
	select NF_TPROXY_IPV6 if NF_TABLES_IPV6
	help
	  This makes transparent proxy support available in nftables.

653 654 655 656 657 658 659 660 661 662 663
config NFT_SYNPROXY
	tristate "Netfilter nf_tables SYNPROXY expression support"
	depends on NF_CONNTRACK && NETFILTER_ADVANCED
	select NETFILTER_SYNPROXY
	select SYN_COOKIES
	help
	  The SYNPROXY expression allows you to intercept TCP connections and
	  establish them using syncookies before they are passed on to the
	  server. This allows to avoid conntrack and server resource usage
	  during SYN-flood attacks.

664 665 666 667 668 669 670 671 672 673 674 675 676 677
if NF_TABLES_NETDEV

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

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

678 679 680 681 682 683
config NFT_FWD_NETDEV
	tristate "Netfilter nf_tables netdev packet forwarding support"
	select NF_DUP_NETDEV
	help
	  This option enables packet forwarding for the "netdev" family.

684 685 686 687 688 689 690 691 692
config NFT_FIB_NETDEV
	depends on NFT_FIB_IPV4
	depends on NFT_FIB_IPV6
	tristate "Netfilter nf_tables netdev fib lookups support"
	help
	  This option allows using the FIB expression from the netdev table.
	  The lookup will be delegated to the IPv4 or IPv6 FIB depending
	  on the protocol of the packet.

693 694 695 696 697 698 699 700 701 702
config NFT_REJECT_NETDEV
	depends on NFT_REJECT_IPV4
	depends on NFT_REJECT_IPV6
	tristate "Netfilter nf_tables netdev REJECT support"
	help
	  This option enables the REJECT support from the netdev table.
	  The return packet generation will be delegated to the IPv4
	  or IPv6 ICMP or TCP RST implementation depending on the
	  protocol of the packet.

703 704
endif # NF_TABLES_NETDEV

705 706
endif # NF_TABLES

707 708
config NF_FLOW_TABLE_INET
	tristate "Netfilter flow table mixed IPv4/IPv6 module"
709
	depends on NF_FLOW_TABLE
710
	help
711
	  This option adds the flow table mixed IPv4/IPv6 support.
712 713 714

	  To compile it as a module, choose M here.

715 716
config NF_FLOW_TABLE
	tristate "Netfilter flow table module"
717 718 719
	depends on NETFILTER_INGRESS
	depends on NF_CONNTRACK
	depends on NF_TABLES
720 721 722 723 724
	help
	  This option adds the flow table core infrastructure.

	  To compile it as a module, choose M here.

725 726
config NETFILTER_XTABLES
	tristate "Netfilter Xtables support (required for ip_tables)"
727
	default m if NETFILTER_ADVANCED=n
728 729 730 731
	help
	  This is required if you intend to use any of ip_tables,
	  ip6_tables or arp_tables.

732 733
if NETFILTER_XTABLES

734 735 736 737 738
comment "Xtables combined modules"

config NETFILTER_XT_MARK
	tristate 'nfmark target and match support'
	default m if NETFILTER_ADVANCED=n
739
	help
740 741 742 743 744 745 746
	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.

747 748
	Prior to routing, the nfmark can influence the routing method and can
	also be used by other subsystems to change their behavior.
749

750 751 752 753 754
config NETFILTER_XT_CONNMARK
	tristate 'ctmark target and match support'
	depends on NF_CONNTRACK
	depends on NETFILTER_ADVANCED
	select NF_CONNTRACK_MARK
755
	help
756 757 758 759 760 761
	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.

762 763 764 765 766 767 768 769 770 771 772 773
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.

774 775
# alphabetically ordered list of targets

776 777
comment "Xtables targets"

778 779 780 781
config NETFILTER_XT_TARGET_AUDIT
	tristate "AUDIT target support"
	depends on AUDIT
	depends on NETFILTER_ADVANCED
782
	help
783 784 785 786 787
	  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.

788 789 790 791
config NETFILTER_XT_TARGET_CHECKSUM
	tristate "CHECKSUM target support"
	depends on IP_NF_MANGLE || IP6_NF_MANGLE
	depends on NETFILTER_ADVANCED
792
	help
793
	  This option adds a `CHECKSUM' target, which can be used in the iptables mangle
794
	  table to work around buggy DHCP clients in virtualized environments.
795

796 797 798 799 800
	  Some old DHCP clients drop packets because they are not aware
	  that the checksum would normally be offloaded to hardware and
	  thus should be considered valid.
	  This target can be used to fill in the checksum using iptables
	  when such packets are sent via a virtual network device.
801 802 803

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

804 805
config NETFILTER_XT_TARGET_CLASSIFY
	tristate '"CLASSIFY" target support'
806
	depends on NETFILTER_ADVANCED
807 808 809 810 811 812 813 814 815 816 817
	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'
818
	depends on NF_CONNTRACK
819
	depends on NETFILTER_ADVANCED
820
	select NETFILTER_XT_CONNMARK
821
	help
822 823 824
	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).
825

826 827
config NETFILTER_XT_TARGET_CONNSECMARK
	tristate '"CONNSECMARK" target support'
828
	depends on NF_CONNTRACK && NF_CONNTRACK_SECMARK
829 830 831 832 833 834 835 836 837
	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.

838 839 840 841 842 843 844 845 846 847 848 849
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.

850
config NETFILTER_XT_TARGET_DSCP
851
	tristate '"DSCP" and "TOS" target support'
852
	depends on IP_NF_MANGLE || IP6_NF_MANGLE
853
	depends on NETFILTER_ADVANCED
854 855 856 857 858 859
	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.

860 861
	  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
862
	  or the Priority field of an IPv6 packet, prior to routing.
863

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

866 867 868 869
config NETFILTER_XT_TARGET_HL
	tristate '"HL" hoplimit target support'
	depends on IP_NF_MANGLE || IP6_NF_MANGLE
	depends on NETFILTER_ADVANCED
870
	help
871 872 873 874 875 876 877 878 879 880
	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.

881 882
config NETFILTER_XT_TARGET_HMARK
	tristate '"HMARK" target support'
883
	depends on IP6_NF_IPTABLES || IP6_NF_IPTABLES=n
884
	depends on NETFILTER_ADVANCED
885
	help
886 887 888 889
	This option adds the "HMARK" target.

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

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

895 896 897 898 899 900 901 902 903 904 905 906
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.

907 908
config NETFILTER_XT_TARGET_LED
	tristate '"LED" target support'
909
	depends on LEDS_CLASS && LEDS_TRIGGERS
910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928
	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
929
	  Documentation/leds/leds-class.rst
930

931 932
config NETFILTER_XT_TARGET_LOG
	tristate "LOG target support"
933
	select NF_LOG_COMMON
934
	select NF_LOG_SYSLOG
935
	select NF_LOG_IPV6 if IP6_NF_IPTABLES
936 937 938 939 940 941 942
	default m if NETFILTER_ADVANCED=n
	help
	  This option adds a `LOG' target, which allows you to create rules in
	  any iptables table which records the packet header to the syslog.

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

943 944
config NETFILTER_XT_TARGET_MARK
	tristate '"MARK" target support'
945 946
	depends on NETFILTER_ADVANCED
	select NETFILTER_XT_MARK
947
	help
948 949 950
	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).
951

952 953 954
config NETFILTER_XT_NAT
	tristate '"SNAT and DNAT" targets support'
	depends on NF_NAT
955
	help
956 957 958 959
	This option enables the SNAT and DNAT targets.

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

960 961 962
config NETFILTER_XT_TARGET_NETMAP
	tristate '"NETMAP" target support'
	depends on NF_NAT
963
	help
964 965 966 967 968 969
	NETMAP is an implementation of static 1:1 NAT mapping of network
	addresses. It maps the network address part, while keeping the host
	address part intact.

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

970 971
config NETFILTER_XT_TARGET_NFLOG
	tristate '"NFLOG" target support'
972
	default m if NETFILTER_ADVANCED=n
973
	select NETFILTER_NETLINK_LOG
974 975
	help
	  This option enables the NFLOG target, which allows to LOG
976
	  messages through nfnetlink_log.
977 978 979

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

980 981 982
config NETFILTER_XT_TARGET_NFQUEUE
	tristate '"NFQUEUE" target Support'
	depends on NETFILTER_ADVANCED
983
	select NETFILTER_NETLINK_QUEUE
984 985 986 987 988 989 990 991
	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.

992 993
config NETFILTER_XT_TARGET_NOTRACK
	tristate  '"NOTRACK" target support (DEPRECATED)'
994 995 996
	depends on NF_CONNTRACK
	depends on IP_NF_RAW || IP6_NF_RAW
	depends on NETFILTER_ADVANCED
997 998
	select NETFILTER_XT_TARGET_CT

999 1000
config NETFILTER_XT_TARGET_RATEEST
	tristate '"RATEEST" target support'
1001
	depends on NETFILTER_ADVANCED
1002 1003 1004 1005 1006 1007 1008
	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.

1009 1010 1011
config NETFILTER_XT_TARGET_REDIRECT
	tristate "REDIRECT target support"
	depends on NF_NAT
1012
	select NF_NAT_REDIRECT
1013
	help
1014 1015 1016 1017 1018 1019 1020
	REDIRECT is a special case of NAT: all incoming connections are
	mapped onto the incoming interface's address, causing the packets to
	come to the local machine instead of passing through. This is
	useful for transparent proxies.

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

1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034
config NETFILTER_XT_TARGET_MASQUERADE
	tristate "MASQUERADE target support"
	depends on NF_NAT
	default m if NETFILTER_ADVANCED=n
	select NF_NAT_MASQUERADE
	help
	  Masquerading is a special case of NAT: all outgoing connections are
	  changed to seem to come from a particular interface's address, and
	  if the interface goes down, those connections are lost.  This is
	  only useful for dialup accounts with dynamic IP address (ie. your IP
	  address will be different on next dialup).

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

1035
config NETFILTER_XT_TARGET_TEE
1036
	tristate '"TEE" - packet cloning to alternate destination'
1037
	depends on NETFILTER_ADVANCED
1038
	depends on IPV6 || IPV6=n
1039
	depends on !NF_CONNTRACK || NF_CONNTRACK
1040
	depends on IP6_NF_IPTABLES || !IP6_NF_IPTABLES
1041
	select NF_DUP_IPV4
1042
	select NF_DUP_IPV6 if IP6_NF_IPTABLES
1043
	help
1044 1045 1046
	This option adds a "TEE" target with which a packet can be cloned and
	this clone be rerouted to another nexthop.

1047
config NETFILTER_XT_TARGET_TPROXY
1048
	tristate '"TPROXY" target transparent proxying support'
1049 1050
	depends on NETFILTER_XTABLES
	depends on NETFILTER_ADVANCED
1051 1052
	depends on IPV6 || IPV6=n
	depends on IP6_NF_IPTABLES || IP6_NF_IPTABLES=n
1053
	depends on IP_NF_MANGLE
1054
	select NF_DEFRAG_IPV4
1055
	select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES != n
M
Máté Eckl 已提交
1056 1057
	select NF_TPROXY_IPV4
	select NF_TPROXY_IPV6 if IP6_NF_IPTABLES
1058 1059 1060 1061 1062
	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.
1063 1064
	  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
1065
	  see Documentation/networking/tproxy.rst.
1066 1067 1068

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

1069 1070 1071
config NETFILTER_XT_TARGET_TRACE
	tristate  '"TRACE" target support'
	depends on IP_NF_RAW || IP6_NF_RAW
1072
	depends on NETFILTER_ADVANCED
1073 1074 1075 1076 1077 1078
	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
1079
	  <file:Documentation/kbuild/modules.rst>.  If unsure, say `N'.
1080

1081 1082
config NETFILTER_XT_TARGET_SECMARK
	tristate '"SECMARK" target support'
1083
	depends on NETWORK_SECMARK
1084
	default m if NETFILTER_ADVANCED=n
1085 1086 1087 1088 1089 1090
	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.

1091 1092
config NETFILTER_XT_TARGET_TCPMSS
	tristate '"TCPMSS" target support'
1093
	depends on IPV6 || IPV6=n
1094
	default m if NETFILTER_ADVANCED=n
1095
	help
1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117
	  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.

1118
config NETFILTER_XT_TARGET_TCPOPTSTRIP
1119
	tristate '"TCPOPTSTRIP" target support'
1120
	depends on IP_NF_MANGLE || IP6_NF_MANGLE
1121
	depends on NETFILTER_ADVANCED
1122 1123 1124 1125
	help
	  This option adds a "TCPOPTSTRIP" target, which allows you to strip
	  TCP options from TCP packets.

1126 1127 1128 1129
# alphabetically ordered list of matches

comment "Xtables matches"

1130 1131
config NETFILTER_XT_MATCH_ADDRTYPE
	tristate '"addrtype" address type match support'
1132
	default m if NETFILTER_ADVANCED=n
1133
	help
1134 1135 1136 1137
	  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
1138
	  <file:Documentation/kbuild/modules.rst>.  If unsure, say `N'.
1139

1140 1141 1142 1143 1144 1145 1146 1147 1148
config NETFILTER_XT_MATCH_BPF
	tristate '"bpf" match support'
	depends on NETFILTER_ADVANCED
	help
	  BPF matching applies a linux socket filter to each packet and
	  accepts those for which the filter returns non-zero.

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

1149 1150 1151 1152 1153
config NETFILTER_XT_MATCH_CGROUP
	tristate '"control group" match support'
	depends on NETFILTER_ADVANCED
	depends on CGROUPS
	select CGROUP_NET_CLASSID
1154
	help
1155 1156 1157 1158
	Socket/process control group matching allows you to match locally
	generated packets based on which net_cls control group processes
	belong to.

1159 1160 1161 1162
config NETFILTER_XT_MATCH_CLUSTER
	tristate '"cluster" match support'
	depends on NF_CONNTRACK
	depends on NETFILTER_ADVANCED
1163
	help
1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174
	  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.

1175 1176
config NETFILTER_XT_MATCH_COMMENT
	tristate  '"comment" match support'
1177
	depends on NETFILTER_ADVANCED
1178 1179 1180 1181 1182
	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
1183
	  <file:Documentation/kbuild/modules.rst>.  If unsure, say `N'.
1184 1185 1186

config NETFILTER_XT_MATCH_CONNBYTES
	tristate  '"connbytes" per-connection counter match support'
1187
	depends on NF_CONNTRACK
1188
	depends on NETFILTER_ADVANCED
1189 1190 1191 1192 1193
	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
1194
	  <file:Documentation/kbuild/modules.rst>.  If unsure, say `N'.
1195

1196 1197 1198
config NETFILTER_XT_MATCH_CONNLABEL
	tristate '"connlabel" match support'
	select NF_CONNTRACK_LABELS
1199
	depends on NF_CONNTRACK
1200
	depends on NETFILTER_ADVANCED
1201
	help
1202 1203 1204 1205 1206 1207 1208
	  This match allows you to test and assign userspace-defined labels names
	  to a connection.  The kernel only stores bit values - mapping
	  names to bits is done by userspace.

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

1209
config NETFILTER_XT_MATCH_CONNLIMIT
1210
	tristate '"connlimit" match support'
1211
	depends on NF_CONNTRACK
1212
	depends on NETFILTER_ADVANCED
1213
	select NETFILTER_CONNCOUNT
1214
	help
1215 1216 1217
	  This match allows you to match against the number of parallel
	  connections to a server per client IP address (or address block).

1218 1219
config NETFILTER_XT_MATCH_CONNMARK
	tristate  '"connmark" connection mark match support'
1220
	depends on NF_CONNTRACK
1221
	depends on NETFILTER_ADVANCED
1222
	select NETFILTER_XT_CONNMARK
1223
	help
1224 1225 1226
	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).
1227 1228 1229

config NETFILTER_XT_MATCH_CONNTRACK
	tristate '"conntrack" connection tracking match support'
1230
	depends on NF_CONNTRACK
1231
	default m if NETFILTER_ADVANCED=n
1232 1233 1234 1235 1236 1237 1238 1239
	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 已提交
1240 1241 1242 1243 1244 1245 1246 1247 1248

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.
1249 1250

config NETFILTER_XT_MATCH_DCCP
1251
	tristate '"dccp" protocol match support'
1252
	depends on NETFILTER_ADVANCED
1253
	default IP_DCCP
1254 1255 1256 1257 1258 1259
	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
1260
	  <file:Documentation/kbuild/modules.rst>.  If unsure, say `N'.
1261

1262 1263 1264 1265 1266 1267 1268 1269 1270
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.

1271
config NETFILTER_XT_MATCH_DSCP
1272
	tristate '"dscp" and "tos" match support'
1273
	depends on NETFILTER_ADVANCED
1274 1275 1276 1277 1278 1279
	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.

1280 1281 1282 1283
	  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).

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

1286 1287 1288
config NETFILTER_XT_MATCH_ECN
	tristate '"ecn" match support'
	depends on NETFILTER_ADVANCED
1289
	help
1290 1291 1292 1293 1294
	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.

1295
config NETFILTER_XT_MATCH_ESP
1296
	tristate '"esp" match support'
1297
	depends on NETFILTER_ADVANCED
1298 1299 1300 1301 1302 1303
	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.

1304 1305
config NETFILTER_XT_MATCH_HASHLIMIT
	tristate '"hashlimit" match support'
1306
	depends on IP6_NF_IPTABLES || IP6_NF_IPTABLES=n
1307 1308 1309 1310 1311 1312 1313 1314 1315 1316 1317 1318
	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.

1319 1320
config NETFILTER_XT_MATCH_HELPER
	tristate '"helper" match support'
1321
	depends on NF_CONNTRACK
1322
	depends on NETFILTER_ADVANCED
1323 1324
	help
	  Helper matching allows you to match packets in dynamic connections
1325
	  tracked by a conntrack-helper, ie. nf_conntrack_ftp
1326 1327 1328

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

1329 1330 1331
config NETFILTER_XT_MATCH_HL
	tristate '"hl" hoplimit/TTL match support'
	depends on NETFILTER_ADVANCED
1332
	help
1333 1334 1335 1336
	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.

1337 1338 1339 1340 1341 1342 1343 1344 1345
config NETFILTER_XT_MATCH_IPCOMP
	tristate '"ipcomp" match support'
	depends on NETFILTER_ADVANCED
	help
	  This match extension allows you to match a range of CPIs(16 bits)
	  inside IPComp header of IPSec packets.

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

1346 1347 1348
config NETFILTER_XT_MATCH_IPRANGE
	tristate '"iprange" address range match support'
	depends on NETFILTER_ADVANCED
1349
	help
1350 1351 1352 1353 1354 1355
	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.

1356 1357 1358 1359 1360 1361 1362 1363 1364 1365
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.

1366 1367 1368 1369
config NETFILTER_XT_MATCH_L2TP
	tristate '"l2tp" match support'
	depends on NETFILTER_ADVANCED
	default L2TP
1370
	help
1371 1372 1373 1374 1375
	This option adds an "L2TP" match, which allows you to match against
	L2TP protocol header fields.

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

1376 1377
config NETFILTER_XT_MATCH_LENGTH
	tristate '"length" match support'
1378
	depends on NETFILTER_ADVANCED
1379 1380 1381 1382 1383 1384 1385 1386
	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'
1387
	depends on NETFILTER_ADVANCED
1388 1389 1390 1391 1392 1393 1394 1395 1396
	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'
1397
	depends on NETFILTER_ADVANCED
1398 1399 1400 1401 1402 1403 1404 1405
	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'
1406 1407
	depends on NETFILTER_ADVANCED
	select NETFILTER_XT_MARK
1408
	help
1409 1410 1411
	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).
1412

1413 1414 1415 1416 1417 1418 1419 1420 1421 1422
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.

1423 1424
config NETFILTER_XT_MATCH_NFACCT
	tristate '"nfacct" match support'
1425
	depends on NETFILTER_ADVANCED
1426 1427 1428 1429 1430 1431 1432
	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.

1433 1434
config NETFILTER_XT_MATCH_OSF
	tristate '"osf" Passive OS fingerprint match'
1435 1436
	depends on NETFILTER_ADVANCED
	select NETFILTER_NETLINK_OSF
1437 1438 1439 1440 1441 1442 1443 1444 1445 1446
	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.

1447 1448
config NETFILTER_XT_MATCH_OWNER
	tristate '"owner" match support'
1449
	depends on NETFILTER_ADVANCED
1450
	help
1451 1452 1453 1454
	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.

1455 1456
config NETFILTER_XT_MATCH_POLICY
	tristate 'IPsec "policy" match support'
1457
	depends on XFRM
1458
	default m if NETFILTER_ADVANCED=n
1459 1460 1461 1462 1463 1464 1465
	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.

1466 1467
config NETFILTER_XT_MATCH_PHYSDEV
	tristate '"physdev" match support'
1468
	depends on BRIDGE && BRIDGE_NETFILTER
1469
	depends on NETFILTER_ADVANCED
1470 1471 1472 1473 1474 1475 1476 1477
	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'
1478
	depends on NETFILTER_ADVANCED
1479 1480 1481 1482 1483 1484 1485 1486 1487
	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.

1488 1489
config NETFILTER_XT_MATCH_QUOTA
	tristate '"quota" match support'
1490
	depends on NETFILTER_ADVANCED
1491 1492 1493 1494 1495
	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
1496
	  <file:Documentation/kbuild/modules.rst>.  If unsure, say `N'.
1497

1498 1499
config NETFILTER_XT_MATCH_RATEEST
	tristate '"rateest" match support'
1500
	depends on NETFILTER_ADVANCED
1501 1502 1503 1504 1505 1506 1507
	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.

1508 1509
config NETFILTER_XT_MATCH_REALM
	tristate  '"realm" match support'
1510
	depends on NETFILTER_ADVANCED
1511
	select IP_ROUTE_CLASSID
1512 1513 1514
	help
	  This option adds a `realm' match, which allows you to use the realm
	  key from the routing subsystem inside iptables.
1515

1516
	  This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option
1517
	  in tc world.
1518

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

1522 1523 1524
config NETFILTER_XT_MATCH_RECENT
	tristate '"recent" match support'
	depends on NETFILTER_ADVANCED
1525
	help
1526 1527 1528 1529 1530 1531
	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/>

1532
config NETFILTER_XT_MATCH_SCTP
1533
	tristate  '"sctp" protocol match support'
1534
	depends on NETFILTER_ADVANCED
1535
	default IP_SCTP
1536
	help
1537
	  With this option enabled, you will be able to use the
1538 1539 1540 1541
	  `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
1542
	  <file:Documentation/kbuild/modules.rst>.  If unsure, say `N'.
1543

1544
config NETFILTER_XT_MATCH_SOCKET
1545
	tristate '"socket" match support'
1546 1547
	depends on NETFILTER_XTABLES
	depends on NETFILTER_ADVANCED
1548 1549
	depends on IPV6 || IPV6=n
	depends on IP6_NF_IPTABLES || IP6_NF_IPTABLES=n
1550 1551
	select NF_SOCKET_IPV4
	select NF_SOCKET_IPV6 if IP6_NF_IPTABLES
1552
	select NF_DEFRAG_IPV4
1553
	select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES != n
1554 1555 1556 1557 1558 1559 1560 1561
	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.

1562 1563
config NETFILTER_XT_MATCH_STATE
	tristate '"state" match support'
1564
	depends on NF_CONNTRACK
1565
	default m if NETFILTER_ADVANCED=n
1566 1567 1568 1569 1570 1571 1572
	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.

1573 1574
config NETFILTER_XT_MATCH_STATISTIC
	tristate '"statistic" match support'
1575
	depends on NETFILTER_ADVANCED
1576
	help
1577 1578 1579 1580
	  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.
1581

1582 1583
config NETFILTER_XT_MATCH_STRING
	tristate  '"string" match support'
1584
	depends on NETFILTER_ADVANCED
1585 1586 1587 1588 1589 1590 1591 1592 1593 1594 1595 1596
	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'
1597
	depends on NETFILTER_ADVANCED
1598 1599 1600 1601 1602 1603 1604
	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.

1605 1606
config NETFILTER_XT_MATCH_TIME
	tristate '"time" match support'
1607
	depends on NETFILTER_ADVANCED
1608
	help
1609 1610 1611 1612 1613 1614 1615 1616 1617 1618
	  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 已提交
1619 1620
config NETFILTER_XT_MATCH_U32
	tristate '"u32" match support'
1621
	depends on NETFILTER_ADVANCED
1622
	help
J
Jan Engelhardt 已提交
1623 1624 1625 1626 1627 1628 1629 1630 1631
	  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.

1632
endif # NETFILTER_XTABLES
1633

1634
endmenu
1635

1636 1637
source "net/netfilter/ipset/Kconfig"

1638
source "net/netfilter/ipvs/Kconfig"