390f96cc8ed4443fc9b53b3bce9712549105dee5
[deliverable/linux.git] / net / netfilter / Kconfig
1 menu "Core Netfilter Configuration"
2 depends on NET && INET && NETFILTER
3
4 config NETFILTER_NETLINK
5 tristate
6
7 config NETFILTER_NETLINK_ACCT
8 tristate "Netfilter NFACCT over NFNETLINK interface"
9 depends on NETFILTER_ADVANCED
10 select NETFILTER_NETLINK
11 help
12 If this option is enabled, the kernel will include support
13 for extended accounting via NFNETLINK.
14
15 config NETFILTER_NETLINK_QUEUE
16 tristate "Netfilter NFQUEUE over NFNETLINK interface"
17 depends on NETFILTER_ADVANCED
18 select NETFILTER_NETLINK
19 help
20 If this option is enabled, the kernel will include support
21 for queueing packets via NFNETLINK.
22
23 config NETFILTER_NETLINK_LOG
24 tristate "Netfilter LOG over NFNETLINK interface"
25 default m if NETFILTER_ADVANCED=n
26 select NETFILTER_NETLINK
27 help
28 If this option is enabled, the kernel will include support
29 for logging packets via NFNETLINK.
30
31 This obsoletes the existing ipt_ULOG and ebg_ulog mechanisms,
32 and is also scheduled to replace the old syslog-based ipt_LOG
33 and ip6t_LOG modules.
34
35 config NF_CONNTRACK
36 tristate "Netfilter connection tracking support"
37 default m if NETFILTER_ADVANCED=n
38 help
39 Connection tracking keeps a record of what packets have passed
40 through your machine, in order to figure out how they are related
41 into connections.
42
43 This is required to do Masquerading or other kinds of Network
44 Address Translation. It can also be used to enhance packet
45 filtering (see `Connection state match support' below).
46
47 To compile it as a module, choose M here. If unsure, say N.
48
49 if NF_CONNTRACK
50
51 config NF_CONNTRACK_MARK
52 bool 'Connection mark tracking support'
53 depends on NETFILTER_ADVANCED
54 help
55 This option enables support for connection marks, used by the
56 `CONNMARK' target and `connmark' match. Similar to the mark value
57 of packets, but this mark value is kept in the conntrack session
58 instead of the individual packets.
59
60 config NF_CONNTRACK_SECMARK
61 bool 'Connection tracking security mark support'
62 depends on NETWORK_SECMARK
63 default m if NETFILTER_ADVANCED=n
64 help
65 This option enables security markings to be applied to
66 connections. Typically they are copied to connections from
67 packets using the CONNSECMARK target and copied back from
68 connections to packets with the same target, with the packets
69 being originally labeled via SECMARK.
70
71 If unsure, say 'N'.
72
73 config NF_CONNTRACK_ZONES
74 bool 'Connection tracking zones'
75 depends on NETFILTER_ADVANCED
76 depends on NETFILTER_XT_TARGET_CT
77 help
78 This option enables support for connection tracking zones.
79 Normally, each connection needs to have a unique system wide
80 identity. Connection tracking zones allow to have multiple
81 connections using the same identity, as long as they are
82 contained in different zones.
83
84 If unsure, say `N'.
85
86 config NF_CONNTRACK_PROCFS
87 bool "Supply CT list in procfs (OBSOLETE)"
88 default y
89 depends on PROC_FS
90 ---help---
91 This option enables for the list of known conntrack entries
92 to be shown in procfs under net/netfilter/nf_conntrack. This
93 is considered obsolete in favor of using the conntrack(8)
94 tool which uses Netlink.
95
96 config NF_CONNTRACK_EVENTS
97 bool "Connection tracking events"
98 depends on NETFILTER_ADVANCED
99 help
100 If this option is enabled, the connection tracking code will
101 provide a notifier chain that can be used by other kernel code
102 to get notified about changes in the connection tracking state.
103
104 If unsure, say `N'.
105
106 config NF_CONNTRACK_TIMEOUT
107 bool 'Connection tracking timeout'
108 depends on NETFILTER_ADVANCED
109 help
110 This option enables support for connection tracking timeout
111 extension. This allows you to attach timeout policies to flow
112 via the CT target.
113
114 If unsure, say `N'.
115
116 config NF_CONNTRACK_TIMESTAMP
117 bool 'Connection tracking timestamping'
118 depends on NETFILTER_ADVANCED
119 help
120 This option enables support for connection tracking timestamping.
121 This allows you to store the flow start-time and to obtain
122 the flow-stop time (once it has been destroyed) via Connection
123 tracking events.
124
125 If unsure, say `N'.
126
127 config NF_CT_PROTO_DCCP
128 tristate 'DCCP protocol connection tracking support (EXPERIMENTAL)'
129 depends on EXPERIMENTAL
130 depends on NETFILTER_ADVANCED
131 default IP_DCCP
132 help
133 With this option enabled, the layer 3 independent connection
134 tracking code will be able to do state tracking on DCCP connections.
135
136 If unsure, say 'N'.
137
138 config NF_CT_PROTO_GRE
139 tristate
140
141 config NF_CT_PROTO_SCTP
142 tristate 'SCTP protocol connection tracking support (EXPERIMENTAL)'
143 depends on EXPERIMENTAL
144 depends on NETFILTER_ADVANCED
145 default IP_SCTP
146 help
147 With this option enabled, the layer 3 independent connection
148 tracking code will be able to do state tracking on SCTP connections.
149
150 If you want to compile it as a module, say M here and read
151 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
152
153 config NF_CT_PROTO_UDPLITE
154 tristate 'UDP-Lite protocol connection tracking support'
155 depends on NETFILTER_ADVANCED
156 help
157 With this option enabled, the layer 3 independent connection
158 tracking code will be able to do state tracking on UDP-Lite
159 connections.
160
161 To compile it as a module, choose M here. If unsure, say N.
162
163 config NF_CONNTRACK_AMANDA
164 tristate "Amanda backup protocol support"
165 depends on NETFILTER_ADVANCED
166 select TEXTSEARCH
167 select TEXTSEARCH_KMP
168 help
169 If you are running the Amanda backup package <http://www.amanda.org/>
170 on this machine or machines that will be MASQUERADED through this
171 machine, then you may want to enable this feature. This allows the
172 connection tracking and natting code to allow the sub-channels that
173 Amanda requires for communication of the backup data, messages and
174 index.
175
176 To compile it as a module, choose M here. If unsure, say N.
177
178 config NF_CONNTRACK_FTP
179 tristate "FTP protocol support"
180 default m if NETFILTER_ADVANCED=n
181 help
182 Tracking FTP connections is problematic: special helpers are
183 required for tracking them, and doing masquerading and other forms
184 of Network Address Translation on them.
185
186 This is FTP support on Layer 3 independent connection tracking.
187 Layer 3 independent connection tracking is experimental scheme
188 which generalize ip_conntrack to support other layer 3 protocols.
189
190 To compile it as a module, choose M here. If unsure, say N.
191
192 config NF_CONNTRACK_H323
193 tristate "H.323 protocol support"
194 depends on (IPV6 || IPV6=n)
195 depends on NETFILTER_ADVANCED
196 help
197 H.323 is a VoIP signalling protocol from ITU-T. As one of the most
198 important VoIP protocols, it is widely used by voice hardware and
199 software including voice gateways, IP phones, Netmeeting, OpenPhone,
200 Gnomemeeting, etc.
201
202 With this module you can support H.323 on a connection tracking/NAT
203 firewall.
204
205 This module supports RAS, Fast Start, H.245 Tunnelling, Call
206 Forwarding, RTP/RTCP and T.120 based audio, video, fax, chat,
207 whiteboard, file transfer, etc. For more information, please
208 visit http://nath323.sourceforge.net/.
209
210 To compile it as a module, choose M here. If unsure, say N.
211
212 config NF_CONNTRACK_IRC
213 tristate "IRC protocol support"
214 default m if NETFILTER_ADVANCED=n
215 help
216 There is a commonly-used extension to IRC called
217 Direct Client-to-Client Protocol (DCC). This enables users to send
218 files to each other, and also chat to each other without the need
219 of a server. DCC Sending is used anywhere you send files over IRC,
220 and DCC Chat is most commonly used by Eggdrop bots. If you are
221 using NAT, this extension will enable you to send files and initiate
222 chats. Note that you do NOT need this extension to get files or
223 have others initiate chats, or everything else in IRC.
224
225 To compile it as a module, choose M here. If unsure, say N.
226
227 config NF_CONNTRACK_BROADCAST
228 tristate
229
230 config NF_CONNTRACK_NETBIOS_NS
231 tristate "NetBIOS name service protocol support"
232 select NF_CONNTRACK_BROADCAST
233 help
234 NetBIOS name service requests are sent as broadcast messages from an
235 unprivileged port and responded to with unicast messages to the
236 same port. This make them hard to firewall properly because connection
237 tracking doesn't deal with broadcasts. This helper tracks locally
238 originating NetBIOS name service requests and the corresponding
239 responses. It relies on correct IP address configuration, specifically
240 netmask and broadcast address. When properly configured, the output
241 of "ip address show" should look similar to this:
242
243 $ ip -4 address show eth0
244 4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
245 inet 172.16.2.252/24 brd 172.16.2.255 scope global eth0
246
247 To compile it as a module, choose M here. If unsure, say N.
248
249 config NF_CONNTRACK_SNMP
250 tristate "SNMP service protocol support"
251 depends on NETFILTER_ADVANCED
252 select NF_CONNTRACK_BROADCAST
253 help
254 SNMP service requests are sent as broadcast messages from an
255 unprivileged port and responded to with unicast messages to the
256 same port. This make them hard to firewall properly because connection
257 tracking doesn't deal with broadcasts. This helper tracks locally
258 originating SNMP service requests and the corresponding
259 responses. It relies on correct IP address configuration, specifically
260 netmask and broadcast address.
261
262 To compile it as a module, choose M here. If unsure, say N.
263
264 config NF_CONNTRACK_PPTP
265 tristate "PPtP protocol support"
266 depends on NETFILTER_ADVANCED
267 select NF_CT_PROTO_GRE
268 help
269 This module adds support for PPTP (Point to Point Tunnelling
270 Protocol, RFC2637) connection tracking and NAT.
271
272 If you are running PPTP sessions over a stateful firewall or NAT
273 box, you may want to enable this feature.
274
275 Please note that not all PPTP modes of operation are supported yet.
276 Specifically these limitations exist:
277 - Blindly assumes that control connections are always established
278 in PNS->PAC direction. This is a violation of RFC2637.
279 - Only supports a single call within each session
280
281 To compile it as a module, choose M here. If unsure, say N.
282
283 config NF_CONNTRACK_SANE
284 tristate "SANE protocol support (EXPERIMENTAL)"
285 depends on EXPERIMENTAL
286 depends on NETFILTER_ADVANCED
287 help
288 SANE is a protocol for remote access to scanners as implemented
289 by the 'saned' daemon. Like FTP, it uses separate control and
290 data connections.
291
292 With this module you can support SANE on a connection tracking
293 firewall.
294
295 To compile it as a module, choose M here. If unsure, say N.
296
297 config NF_CONNTRACK_SIP
298 tristate "SIP protocol support"
299 default m if NETFILTER_ADVANCED=n
300 help
301 SIP is an application-layer control protocol that can establish,
302 modify, and terminate multimedia sessions (conferences) such as
303 Internet telephony calls. With the ip_conntrack_sip and
304 the nf_nat_sip modules you can support the protocol on a connection
305 tracking/NATing firewall.
306
307 To compile it as a module, choose M here. If unsure, say N.
308
309 config NF_CONNTRACK_TFTP
310 tristate "TFTP protocol support"
311 depends on NETFILTER_ADVANCED
312 help
313 TFTP connection tracking helper, this is required depending
314 on how restrictive your ruleset is.
315 If you are using a tftp client behind -j SNAT or -j MASQUERADING
316 you will need this.
317
318 To compile it as a module, choose M here. If unsure, say N.
319
320 config NF_CT_NETLINK
321 tristate 'Connection tracking netlink interface'
322 select NETFILTER_NETLINK
323 default m if NETFILTER_ADVANCED=n
324 help
325 This option enables support for a netlink-based userspace interface
326
327 config NF_CT_NETLINK_TIMEOUT
328 tristate 'Connection tracking timeout tuning via Netlink'
329 select NETFILTER_NETLINK
330 depends on NETFILTER_ADVANCED
331 help
332 This option enables support for connection tracking timeout
333 fine-grain tuning. This allows you to attach specific timeout
334 policies to flows, instead of using the global timeout policy.
335
336 If unsure, say `N'.
337
338 config NF_CT_NETLINK_HELPER
339 tristate 'Connection tracking helpers in user-space via Netlink'
340 select NETFILTER_NETLINK
341 depends on NF_CT_NETLINK
342 depends on NETFILTER_NETLINK_QUEUE
343 depends on NETFILTER_NETLINK_QUEUE_CT
344 depends on NETFILTER_ADVANCED
345 help
346 This option enables the user-space connection tracking helpers
347 infrastructure.
348
349 If unsure, say `N'.
350
351 config NETFILTER_NETLINK_QUEUE_CT
352 bool "NFQUEUE integration with Connection Tracking"
353 default n
354 depends on NETFILTER_NETLINK_QUEUE
355 help
356 If this option is enabled, NFQUEUE can include Connection Tracking
357 information together with the packet is the enqueued via NFNETLINK.
358
359 config NF_NAT
360 tristate
361
362 config NF_NAT_NEEDED
363 bool
364 depends on NF_NAT
365 default y
366
367 config NF_NAT_PROTO_DCCP
368 tristate
369 depends on NF_NAT && NF_CT_PROTO_DCCP
370 default NF_NAT && NF_CT_PROTO_DCCP
371
372 config NF_NAT_PROTO_UDPLITE
373 tristate
374 depends on NF_NAT && NF_CT_PROTO_UDPLITE
375 default NF_NAT && NF_CT_PROTO_UDPLITE
376
377 config NF_NAT_PROTO_SCTP
378 tristate
379 default NF_NAT && NF_CT_PROTO_SCTP
380 depends on NF_NAT && NF_CT_PROTO_SCTP
381 select LIBCRC32C
382
383 config NF_NAT_AMANDA
384 tristate
385 depends on NF_CONNTRACK && NF_NAT
386 default NF_NAT && NF_CONNTRACK_AMANDA
387
388 config NF_NAT_FTP
389 tristate
390 depends on NF_CONNTRACK && NF_NAT
391 default NF_NAT && NF_CONNTRACK_FTP
392
393 config NF_NAT_IRC
394 tristate
395 depends on NF_CONNTRACK && NF_NAT
396 default NF_NAT && NF_CONNTRACK_IRC
397
398 config NF_NAT_SIP
399 tristate
400 depends on NF_CONNTRACK && NF_NAT
401 default NF_NAT && NF_CONNTRACK_SIP
402
403 config NF_NAT_TFTP
404 tristate
405 depends on NF_CONNTRACK && NF_NAT
406 default NF_NAT && NF_CONNTRACK_TFTP
407
408 endif # NF_CONNTRACK
409
410 # transparent proxy support
411 config NETFILTER_TPROXY
412 tristate "Transparent proxying support (EXPERIMENTAL)"
413 depends on EXPERIMENTAL
414 depends on IP_NF_MANGLE
415 depends on NETFILTER_ADVANCED
416 help
417 This option enables transparent proxying support, that is,
418 support for handling non-locally bound IPv4 TCP and UDP sockets.
419 For it to work you will have to configure certain iptables rules
420 and use policy routing. For more information on how to set it up
421 see Documentation/networking/tproxy.txt.
422
423 To compile it as a module, choose M here. If unsure, say N.
424
425 config NETFILTER_XTABLES
426 tristate "Netfilter Xtables support (required for ip_tables)"
427 default m if NETFILTER_ADVANCED=n
428 help
429 This is required if you intend to use any of ip_tables,
430 ip6_tables or arp_tables.
431
432 if NETFILTER_XTABLES
433
434 comment "Xtables combined modules"
435
436 config NETFILTER_XT_MARK
437 tristate 'nfmark target and match support'
438 default m if NETFILTER_ADVANCED=n
439 ---help---
440 This option adds the "MARK" target and "mark" match.
441
442 Netfilter mark matching allows you to match packets based on the
443 "nfmark" value in the packet.
444 The target allows you to create rules in the "mangle" table which alter
445 the netfilter mark (nfmark) field associated with the packet.
446
447 Prior to routing, the nfmark can influence the routing method (see
448 "Use netfilter MARK value as routing key") and can also be used by
449 other subsystems to change their behavior.
450
451 config NETFILTER_XT_CONNMARK
452 tristate 'ctmark target and match support'
453 depends on NF_CONNTRACK
454 depends on NETFILTER_ADVANCED
455 select NF_CONNTRACK_MARK
456 ---help---
457 This option adds the "CONNMARK" target and "connmark" match.
458
459 Netfilter allows you to store a mark value per connection (a.k.a.
460 ctmark), similarly to the packet mark (nfmark). Using this
461 target and match, you can set and match on this mark.
462
463 config NETFILTER_XT_SET
464 tristate 'set target and match support'
465 depends on IP_SET
466 depends on NETFILTER_ADVANCED
467 help
468 This option adds the "SET" target and "set" match.
469
470 Using this target and match, you can add/delete and match
471 elements in the sets created by ipset(8).
472
473 To compile it as a module, choose M here. If unsure, say N.
474
475 # alphabetically ordered list of targets
476
477 comment "Xtables targets"
478
479 config NETFILTER_XT_TARGET_AUDIT
480 tristate "AUDIT target support"
481 depends on AUDIT
482 depends on NETFILTER_ADVANCED
483 ---help---
484 This option adds a 'AUDIT' target, which can be used to create
485 audit records for packets dropped/accepted.
486
487 To compileit as a module, choose M here. If unsure, say N.
488
489 config NETFILTER_XT_TARGET_CHECKSUM
490 tristate "CHECKSUM target support"
491 depends on IP_NF_MANGLE || IP6_NF_MANGLE
492 depends on NETFILTER_ADVANCED
493 ---help---
494 This option adds a `CHECKSUM' target, which can be used in the iptables mangle
495 table.
496
497 You can use this target to compute and fill in the checksum in
498 a packet that lacks a checksum. This is particularly useful,
499 if you need to work around old applications such as dhcp clients,
500 that do not work well with checksum offloads, but don't want to disable
501 checksum offload in your device.
502
503 To compile it as a module, choose M here. If unsure, say N.
504
505 config NETFILTER_XT_TARGET_CLASSIFY
506 tristate '"CLASSIFY" target support'
507 depends on NETFILTER_ADVANCED
508 help
509 This option adds a `CLASSIFY' target, which enables the user to set
510 the priority of a packet. Some qdiscs can use this value for
511 classification, among these are:
512
513 atm, cbq, dsmark, pfifo_fast, htb, prio
514
515 To compile it as a module, choose M here. If unsure, say N.
516
517 config NETFILTER_XT_TARGET_CONNMARK
518 tristate '"CONNMARK" target support'
519 depends on NF_CONNTRACK
520 depends on NETFILTER_ADVANCED
521 select NETFILTER_XT_CONNMARK
522 ---help---
523 This is a backwards-compat option for the user's convenience
524 (e.g. when running oldconfig). It selects
525 CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
526
527 config NETFILTER_XT_TARGET_CONNSECMARK
528 tristate '"CONNSECMARK" target support'
529 depends on NF_CONNTRACK && NF_CONNTRACK_SECMARK
530 default m if NETFILTER_ADVANCED=n
531 help
532 The CONNSECMARK target copies security markings from packets
533 to connections, and restores security markings from connections
534 to packets (if the packets are not already marked). This would
535 normally be used in conjunction with the SECMARK target.
536
537 To compile it as a module, choose M here. If unsure, say N.
538
539 config NETFILTER_XT_TARGET_CT
540 tristate '"CT" target support'
541 depends on NF_CONNTRACK
542 depends on IP_NF_RAW || IP6_NF_RAW
543 depends on NETFILTER_ADVANCED
544 help
545 This options adds a `CT' target, which allows to specify initial
546 connection tracking parameters like events to be delivered and
547 the helper to be used.
548
549 To compile it as a module, choose M here. If unsure, say N.
550
551 config NETFILTER_XT_TARGET_DSCP
552 tristate '"DSCP" and "TOS" target support'
553 depends on IP_NF_MANGLE || IP6_NF_MANGLE
554 depends on NETFILTER_ADVANCED
555 help
556 This option adds a `DSCP' target, which allows you to manipulate
557 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
558
559 The DSCP field can have any value between 0x0 and 0x3f inclusive.
560
561 It also adds the "TOS" target, which allows you to create rules in
562 the "mangle" table which alter the Type Of Service field of an IPv4
563 or the Priority field of an IPv6 packet, prior to routing.
564
565 To compile it as a module, choose M here. If unsure, say N.
566
567 config NETFILTER_XT_TARGET_HL
568 tristate '"HL" hoplimit target support'
569 depends on IP_NF_MANGLE || IP6_NF_MANGLE
570 depends on NETFILTER_ADVANCED
571 ---help---
572 This option adds the "HL" (for IPv6) and "TTL" (for IPv4)
573 targets, which enable the user to change the
574 hoplimit/time-to-live value of the IP header.
575
576 While it is safe to decrement the hoplimit/TTL value, the
577 modules also allow to increment and set the hoplimit value of
578 the header to arbitrary values. This is EXTREMELY DANGEROUS
579 since you can easily create immortal packets that loop
580 forever on the network.
581
582 config NETFILTER_XT_TARGET_HMARK
583 tristate '"HMARK" target support'
584 depends on (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
585 depends on NETFILTER_ADVANCED
586 ---help---
587 This option adds the "HMARK" target.
588
589 The target allows you to create rules in the "raw" and "mangle" tables
590 which set the skbuff mark by means of hash calculation within a given
591 range. The nfmark can influence the routing method (see "Use netfilter
592 MARK value as routing key") and can also be used by other subsystems to
593 change their behaviour.
594
595 To compile it as a module, choose M here. If unsure, say N.
596
597 config NETFILTER_XT_TARGET_IDLETIMER
598 tristate "IDLETIMER target support"
599 depends on NETFILTER_ADVANCED
600 help
601
602 This option adds the `IDLETIMER' target. Each matching packet
603 resets the timer associated with label specified when the rule is
604 added. When the timer expires, it triggers a sysfs notification.
605 The remaining time for expiration can be read via sysfs.
606
607 To compile it as a module, choose M here. If unsure, say N.
608
609 config NETFILTER_XT_TARGET_LED
610 tristate '"LED" target support'
611 depends on LEDS_CLASS && LEDS_TRIGGERS
612 depends on NETFILTER_ADVANCED
613 help
614 This option adds a `LED' target, which allows you to blink LEDs in
615 response to particular packets passing through your machine.
616
617 This can be used to turn a spare LED into a network activity LED,
618 which only flashes in response to FTP transfers, for example. Or
619 you could have an LED which lights up for a minute or two every time
620 somebody connects to your machine via SSH.
621
622 You will need support for the "led" class to make this work.
623
624 To create an LED trigger for incoming SSH traffic:
625 iptables -A INPUT -p tcp --dport 22 -j LED --led-trigger-id ssh --led-delay 1000
626
627 Then attach the new trigger to an LED on your system:
628 echo netfilter-ssh > /sys/class/leds/<ledname>/trigger
629
630 For more information on the LEDs available on your system, see
631 Documentation/leds/leds-class.txt
632
633 config NETFILTER_XT_TARGET_LOG
634 tristate "LOG target support"
635 default m if NETFILTER_ADVANCED=n
636 help
637 This option adds a `LOG' target, which allows you to create rules in
638 any iptables table which records the packet header to the syslog.
639
640 To compile it as a module, choose M here. If unsure, say N.
641
642 config NETFILTER_XT_TARGET_MARK
643 tristate '"MARK" target support'
644 depends on NETFILTER_ADVANCED
645 select NETFILTER_XT_MARK
646 ---help---
647 This is a backwards-compat option for the user's convenience
648 (e.g. when running oldconfig). It selects
649 CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
650
651 config NETFILTER_XT_TARGET_NETMAP
652 tristate '"NETMAP" target support'
653 depends on NF_NAT
654 ---help---
655 NETMAP is an implementation of static 1:1 NAT mapping of network
656 addresses. It maps the network address part, while keeping the host
657 address part intact.
658
659 To compile it as a module, choose M here. If unsure, say N.
660
661 config NETFILTER_XT_TARGET_NFLOG
662 tristate '"NFLOG" target support'
663 default m if NETFILTER_ADVANCED=n
664 select NETFILTER_NETLINK_LOG
665 help
666 This option enables the NFLOG target, which allows to LOG
667 messages through nfnetlink_log.
668
669 To compile it as a module, choose M here. If unsure, say N.
670
671 config NETFILTER_XT_TARGET_NFQUEUE
672 tristate '"NFQUEUE" target Support'
673 depends on NETFILTER_ADVANCED
674 select NETFILTER_NETLINK_QUEUE
675 help
676 This target replaced the old obsolete QUEUE target.
677
678 As opposed to QUEUE, it supports 65535 different queues,
679 not just one.
680
681 To compile it as a module, choose M here. If unsure, say N.
682
683 config NETFILTER_XT_TARGET_NOTRACK
684 tristate '"NOTRACK" target support (DEPRECATED)'
685 select NETFILTER_XT_TARGET_CT
686
687 config NETFILTER_XT_TARGET_RATEEST
688 tristate '"RATEEST" target support'
689 depends on NETFILTER_ADVANCED
690 help
691 This option adds a `RATEEST' target, which allows to measure
692 rates similar to TC estimators. The `rateest' match can be
693 used to match on the measured rates.
694
695 To compile it as a module, choose M here. If unsure, say N.
696
697 config NETFILTER_XT_TARGET_REDIRECT
698 tristate "REDIRECT target support"
699 depends on NF_NAT
700 ---help---
701 REDIRECT is a special case of NAT: all incoming connections are
702 mapped onto the incoming interface's address, causing the packets to
703 come to the local machine instead of passing through. This is
704 useful for transparent proxies.
705
706 To compile it as a module, choose M here. If unsure, say N.
707
708 config NETFILTER_XT_TARGET_TEE
709 tristate '"TEE" - packet cloning to alternate destination'
710 depends on NETFILTER_ADVANCED
711 depends on (IPV6 || IPV6=n)
712 depends on !NF_CONNTRACK || NF_CONNTRACK
713 ---help---
714 This option adds a "TEE" target with which a packet can be cloned and
715 this clone be rerouted to another nexthop.
716
717 config NETFILTER_XT_TARGET_TPROXY
718 tristate '"TPROXY" target support (EXPERIMENTAL)'
719 depends on EXPERIMENTAL
720 depends on NETFILTER_TPROXY
721 depends on NETFILTER_XTABLES
722 depends on NETFILTER_ADVANCED
723 select NF_DEFRAG_IPV4
724 select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES
725 help
726 This option adds a `TPROXY' target, which is somewhat similar to
727 REDIRECT. It can only be used in the mangle table and is useful
728 to redirect traffic to a transparent proxy. It does _not_ depend
729 on Netfilter connection tracking and NAT, unlike REDIRECT.
730
731 To compile it as a module, choose M here. If unsure, say N.
732
733 config NETFILTER_XT_TARGET_TRACE
734 tristate '"TRACE" target support'
735 depends on IP_NF_RAW || IP6_NF_RAW
736 depends on NETFILTER_ADVANCED
737 help
738 The TRACE target allows you to mark packets so that the kernel
739 will log every rule which match the packets as those traverse
740 the tables, chains, rules.
741
742 If you want to compile it as a module, say M here and read
743 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
744
745 config NETFILTER_XT_TARGET_SECMARK
746 tristate '"SECMARK" target support'
747 depends on NETWORK_SECMARK
748 default m if NETFILTER_ADVANCED=n
749 help
750 The SECMARK target allows security marking of network
751 packets, for use with security subsystems.
752
753 To compile it as a module, choose M here. If unsure, say N.
754
755 config NETFILTER_XT_TARGET_TCPMSS
756 tristate '"TCPMSS" target support'
757 depends on (IPV6 || IPV6=n)
758 default m if NETFILTER_ADVANCED=n
759 ---help---
760 This option adds a `TCPMSS' target, which allows you to alter the
761 MSS value of TCP SYN packets, to control the maximum size for that
762 connection (usually limiting it to your outgoing interface's MTU
763 minus 40).
764
765 This is used to overcome criminally braindead ISPs or servers which
766 block ICMP Fragmentation Needed packets. The symptoms of this
767 problem are that everything works fine from your Linux
768 firewall/router, but machines behind it can never exchange large
769 packets:
770 1) Web browsers connect, then hang with no data received.
771 2) Small mail works fine, but large emails hang.
772 3) ssh works fine, but scp hangs after initial handshaking.
773
774 Workaround: activate this option and add a rule to your firewall
775 configuration like:
776
777 iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
778 -j TCPMSS --clamp-mss-to-pmtu
779
780 To compile it as a module, choose M here. If unsure, say N.
781
782 config NETFILTER_XT_TARGET_TCPOPTSTRIP
783 tristate '"TCPOPTSTRIP" target support (EXPERIMENTAL)'
784 depends on EXPERIMENTAL
785 depends on IP_NF_MANGLE || IP6_NF_MANGLE
786 depends on NETFILTER_ADVANCED
787 help
788 This option adds a "TCPOPTSTRIP" target, which allows you to strip
789 TCP options from TCP packets.
790
791 # alphabetically ordered list of matches
792
793 comment "Xtables matches"
794
795 config NETFILTER_XT_MATCH_ADDRTYPE
796 tristate '"addrtype" address type match support'
797 depends on NETFILTER_ADVANCED
798 ---help---
799 This option allows you to match what routing thinks of an address,
800 eg. UNICAST, LOCAL, BROADCAST, ...
801
802 If you want to compile it as a module, say M here and read
803 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
804
805 config NETFILTER_XT_MATCH_CLUSTER
806 tristate '"cluster" match support'
807 depends on NF_CONNTRACK
808 depends on NETFILTER_ADVANCED
809 ---help---
810 This option allows you to build work-load-sharing clusters of
811 network servers/stateful firewalls without having a dedicated
812 load-balancing router/server/switch. Basically, this match returns
813 true when the packet must be handled by this cluster node. Thus,
814 all nodes see all packets and this match decides which node handles
815 what packets. The work-load sharing algorithm is based on source
816 address hashing.
817
818 If you say Y or M here, try `iptables -m cluster --help` for
819 more information.
820
821 config NETFILTER_XT_MATCH_COMMENT
822 tristate '"comment" match support'
823 depends on NETFILTER_ADVANCED
824 help
825 This option adds a `comment' dummy-match, which allows you to put
826 comments in your iptables ruleset.
827
828 If you want to compile it as a module, say M here and read
829 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
830
831 config NETFILTER_XT_MATCH_CONNBYTES
832 tristate '"connbytes" per-connection counter match support'
833 depends on NF_CONNTRACK
834 depends on NETFILTER_ADVANCED
835 help
836 This option adds a `connbytes' match, which allows you to match the
837 number of bytes and/or packets for each direction within a connection.
838
839 If you want to compile it as a module, say M here and read
840 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
841
842 config NETFILTER_XT_MATCH_CONNLIMIT
843 tristate '"connlimit" match support"'
844 depends on NF_CONNTRACK
845 depends on NETFILTER_ADVANCED
846 ---help---
847 This match allows you to match against the number of parallel
848 connections to a server per client IP address (or address block).
849
850 config NETFILTER_XT_MATCH_CONNMARK
851 tristate '"connmark" connection mark match support'
852 depends on NF_CONNTRACK
853 depends on NETFILTER_ADVANCED
854 select NETFILTER_XT_CONNMARK
855 ---help---
856 This is a backwards-compat option for the user's convenience
857 (e.g. when running oldconfig). It selects
858 CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
859
860 config NETFILTER_XT_MATCH_CONNTRACK
861 tristate '"conntrack" connection tracking match support'
862 depends on NF_CONNTRACK
863 default m if NETFILTER_ADVANCED=n
864 help
865 This is a general conntrack match module, a superset of the state match.
866
867 It allows matching on additional conntrack information, which is
868 useful in complex configurations, such as NAT gateways with multiple
869 internet links or tunnels.
870
871 To compile it as a module, choose M here. If unsure, say N.
872
873 config NETFILTER_XT_MATCH_CPU
874 tristate '"cpu" match support'
875 depends on NETFILTER_ADVANCED
876 help
877 CPU matching allows you to match packets based on the CPU
878 currently handling the packet.
879
880 To compile it as a module, choose M here. If unsure, say N.
881
882 config NETFILTER_XT_MATCH_DCCP
883 tristate '"dccp" protocol match support'
884 depends on NETFILTER_ADVANCED
885 default IP_DCCP
886 help
887 With this option enabled, you will be able to use the iptables
888 `dccp' match in order to match on DCCP source/destination ports
889 and DCCP flags.
890
891 If you want to compile it as a module, say M here and read
892 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
893
894 config NETFILTER_XT_MATCH_DEVGROUP
895 tristate '"devgroup" match support'
896 depends on NETFILTER_ADVANCED
897 help
898 This options adds a `devgroup' match, which allows to match on the
899 device group a network device is assigned to.
900
901 To compile it as a module, choose M here. If unsure, say N.
902
903 config NETFILTER_XT_MATCH_DSCP
904 tristate '"dscp" and "tos" match support'
905 depends on NETFILTER_ADVANCED
906 help
907 This option adds a `DSCP' match, which allows you to match against
908 the IPv4/IPv6 header DSCP field (differentiated services codepoint).
909
910 The DSCP field can have any value between 0x0 and 0x3f inclusive.
911
912 It will also add a "tos" match, which allows you to match packets
913 based on the Type Of Service fields of the IPv4 packet (which share
914 the same bits as DSCP).
915
916 To compile it as a module, choose M here. If unsure, say N.
917
918 config NETFILTER_XT_MATCH_ECN
919 tristate '"ecn" match support'
920 depends on NETFILTER_ADVANCED
921 ---help---
922 This option adds an "ECN" match, which allows you to match against
923 the IPv4 and TCP header ECN fields.
924
925 To compile it as a module, choose M here. If unsure, say N.
926
927 config NETFILTER_XT_MATCH_ESP
928 tristate '"esp" match support'
929 depends on NETFILTER_ADVANCED
930 help
931 This match extension allows you to match a range of SPIs
932 inside ESP header of IPSec packets.
933
934 To compile it as a module, choose M here. If unsure, say N.
935
936 config NETFILTER_XT_MATCH_HASHLIMIT
937 tristate '"hashlimit" match support'
938 depends on (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
939 depends on NETFILTER_ADVANCED
940 help
941 This option adds a `hashlimit' match.
942
943 As opposed to `limit', this match dynamically creates a hash table
944 of limit buckets, based on your selection of source/destination
945 addresses and/or ports.
946
947 It enables you to express policies like `10kpps for any given
948 destination address' or `500pps from any given source address'
949 with a single rule.
950
951 config NETFILTER_XT_MATCH_HELPER
952 tristate '"helper" match support'
953 depends on NF_CONNTRACK
954 depends on NETFILTER_ADVANCED
955 help
956 Helper matching allows you to match packets in dynamic connections
957 tracked by a conntrack-helper, ie. ip_conntrack_ftp
958
959 To compile it as a module, choose M here. If unsure, say Y.
960
961 config NETFILTER_XT_MATCH_HL
962 tristate '"hl" hoplimit/TTL match support'
963 depends on NETFILTER_ADVANCED
964 ---help---
965 HL matching allows you to match packets based on the hoplimit
966 in the IPv6 header, or the time-to-live field in the IPv4
967 header of the packet.
968
969 config NETFILTER_XT_MATCH_IPRANGE
970 tristate '"iprange" address range match support'
971 depends on NETFILTER_ADVANCED
972 ---help---
973 This option adds a "iprange" match, which allows you to match based on
974 an IP address range. (Normal iptables only matches on single addresses
975 with an optional mask.)
976
977 If unsure, say M.
978
979 config NETFILTER_XT_MATCH_IPVS
980 tristate '"ipvs" match support'
981 depends on IP_VS
982 depends on NETFILTER_ADVANCED
983 depends on NF_CONNTRACK
984 help
985 This option allows you to match against IPVS properties of a packet.
986
987 If unsure, say N.
988
989 config NETFILTER_XT_MATCH_LENGTH
990 tristate '"length" match support'
991 depends on NETFILTER_ADVANCED
992 help
993 This option allows you to match the length of a packet against a
994 specific value or range of values.
995
996 To compile it as a module, choose M here. If unsure, say N.
997
998 config NETFILTER_XT_MATCH_LIMIT
999 tristate '"limit" match support'
1000 depends on NETFILTER_ADVANCED
1001 help
1002 limit matching allows you to control the rate at which a rule can be
1003 matched: mainly useful in combination with the LOG target ("LOG
1004 target support", below) and to avoid some Denial of Service attacks.
1005
1006 To compile it as a module, choose M here. If unsure, say N.
1007
1008 config NETFILTER_XT_MATCH_MAC
1009 tristate '"mac" address match support'
1010 depends on NETFILTER_ADVANCED
1011 help
1012 MAC matching allows you to match packets based on the source
1013 Ethernet address of the packet.
1014
1015 To compile it as a module, choose M here. If unsure, say N.
1016
1017 config NETFILTER_XT_MATCH_MARK
1018 tristate '"mark" match support'
1019 depends on NETFILTER_ADVANCED
1020 select NETFILTER_XT_MARK
1021 ---help---
1022 This is a backwards-compat option for the user's convenience
1023 (e.g. when running oldconfig). It selects
1024 CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
1025
1026 config NETFILTER_XT_MATCH_MULTIPORT
1027 tristate '"multiport" Multiple port match support'
1028 depends on NETFILTER_ADVANCED
1029 help
1030 Multiport matching allows you to match TCP or UDP packets based on
1031 a series of source or destination ports: normally a rule can only
1032 match a single range of ports.
1033
1034 To compile it as a module, choose M here. If unsure, say N.
1035
1036 config NETFILTER_XT_MATCH_NFACCT
1037 tristate '"nfacct" match support'
1038 depends on NETFILTER_ADVANCED
1039 select NETFILTER_NETLINK_ACCT
1040 help
1041 This option allows you to use the extended accounting through
1042 nfnetlink_acct.
1043
1044 To compile it as a module, choose M here. If unsure, say N.
1045
1046 config NETFILTER_XT_MATCH_OSF
1047 tristate '"osf" Passive OS fingerprint match'
1048 depends on NETFILTER_ADVANCED && NETFILTER_NETLINK
1049 help
1050 This option selects the Passive OS Fingerprinting match module
1051 that allows to passively match the remote operating system by
1052 analyzing incoming TCP SYN packets.
1053
1054 Rules and loading software can be downloaded from
1055 http://www.ioremap.net/projects/osf
1056
1057 To compile it as a module, choose M here. If unsure, say N.
1058
1059 config NETFILTER_XT_MATCH_OWNER
1060 tristate '"owner" match support'
1061 depends on NETFILTER_ADVANCED
1062 ---help---
1063 Socket owner matching allows you to match locally-generated packets
1064 based on who created the socket: the user or group. It is also
1065 possible to check whether a socket actually exists.
1066
1067 config NETFILTER_XT_MATCH_POLICY
1068 tristate 'IPsec "policy" match support'
1069 depends on XFRM
1070 default m if NETFILTER_ADVANCED=n
1071 help
1072 Policy matching allows you to match packets based on the
1073 IPsec policy that was used during decapsulation/will
1074 be used during encapsulation.
1075
1076 To compile it as a module, choose M here. If unsure, say N.
1077
1078 config NETFILTER_XT_MATCH_PHYSDEV
1079 tristate '"physdev" match support'
1080 depends on BRIDGE && BRIDGE_NETFILTER
1081 depends on NETFILTER_ADVANCED
1082 help
1083 Physdev packet matching matches against the physical bridge ports
1084 the IP packet arrived on or will leave by.
1085
1086 To compile it as a module, choose M here. If unsure, say N.
1087
1088 config NETFILTER_XT_MATCH_PKTTYPE
1089 tristate '"pkttype" packet type match support'
1090 depends on NETFILTER_ADVANCED
1091 help
1092 Packet type matching allows you to match a packet by
1093 its "class", eg. BROADCAST, MULTICAST, ...
1094
1095 Typical usage:
1096 iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG
1097
1098 To compile it as a module, choose M here. If unsure, say N.
1099
1100 config NETFILTER_XT_MATCH_QUOTA
1101 tristate '"quota" match support'
1102 depends on NETFILTER_ADVANCED
1103 help
1104 This option adds a `quota' match, which allows to match on a
1105 byte counter.
1106
1107 If you want to compile it as a module, say M here and read
1108 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1109
1110 config NETFILTER_XT_MATCH_RATEEST
1111 tristate '"rateest" match support'
1112 depends on NETFILTER_ADVANCED
1113 select NETFILTER_XT_TARGET_RATEEST
1114 help
1115 This option adds a `rateest' match, which allows to match on the
1116 rate estimated by the RATEEST target.
1117
1118 To compile it as a module, choose M here. If unsure, say N.
1119
1120 config NETFILTER_XT_MATCH_REALM
1121 tristate '"realm" match support'
1122 depends on NETFILTER_ADVANCED
1123 select IP_ROUTE_CLASSID
1124 help
1125 This option adds a `realm' match, which allows you to use the realm
1126 key from the routing subsystem inside iptables.
1127
1128 This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option
1129 in tc world.
1130
1131 If you want to compile it as a module, say M here and read
1132 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1133
1134 config NETFILTER_XT_MATCH_RECENT
1135 tristate '"recent" match support'
1136 depends on NETFILTER_ADVANCED
1137 ---help---
1138 This match is used for creating one or many lists of recently
1139 used addresses and then matching against that/those list(s).
1140
1141 Short options are available by using 'iptables -m recent -h'
1142 Official Website: <http://snowman.net/projects/ipt_recent/>
1143
1144 config NETFILTER_XT_MATCH_SCTP
1145 tristate '"sctp" protocol match support (EXPERIMENTAL)'
1146 depends on EXPERIMENTAL
1147 depends on NETFILTER_ADVANCED
1148 default IP_SCTP
1149 help
1150 With this option enabled, you will be able to use the
1151 `sctp' match in order to match on SCTP source/destination ports
1152 and SCTP chunk types.
1153
1154 If you want to compile it as a module, say M here and read
1155 <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
1156
1157 config NETFILTER_XT_MATCH_SOCKET
1158 tristate '"socket" match support (EXPERIMENTAL)'
1159 depends on EXPERIMENTAL
1160 depends on NETFILTER_TPROXY
1161 depends on NETFILTER_XTABLES
1162 depends on NETFILTER_ADVANCED
1163 depends on !NF_CONNTRACK || NF_CONNTRACK
1164 select NF_DEFRAG_IPV4
1165 select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES
1166 help
1167 This option adds a `socket' match, which can be used to match
1168 packets for which a TCP or UDP socket lookup finds a valid socket.
1169 It can be used in combination with the MARK target and policy
1170 routing to implement full featured non-locally bound sockets.
1171
1172 To compile it as a module, choose M here. If unsure, say N.
1173
1174 config NETFILTER_XT_MATCH_STATE
1175 tristate '"state" match support'
1176 depends on NF_CONNTRACK
1177 default m if NETFILTER_ADVANCED=n
1178 help
1179 Connection state matching allows you to match packets based on their
1180 relationship to a tracked connection (ie. previous packets). This
1181 is a powerful tool for packet classification.
1182
1183 To compile it as a module, choose M here. If unsure, say N.
1184
1185 config NETFILTER_XT_MATCH_STATISTIC
1186 tristate '"statistic" match support'
1187 depends on NETFILTER_ADVANCED
1188 help
1189 This option adds a `statistic' match, which allows you to match
1190 on packets periodically or randomly with a given percentage.
1191
1192 To compile it as a module, choose M here. If unsure, say N.
1193
1194 config NETFILTER_XT_MATCH_STRING
1195 tristate '"string" match support'
1196 depends on NETFILTER_ADVANCED
1197 select TEXTSEARCH
1198 select TEXTSEARCH_KMP
1199 select TEXTSEARCH_BM
1200 select TEXTSEARCH_FSM
1201 help
1202 This option adds a `string' match, which allows you to look for
1203 pattern matchings in packets.
1204
1205 To compile it as a module, choose M here. If unsure, say N.
1206
1207 config NETFILTER_XT_MATCH_TCPMSS
1208 tristate '"tcpmss" match support'
1209 depends on NETFILTER_ADVANCED
1210 help
1211 This option adds a `tcpmss' match, which allows you to examine the
1212 MSS value of TCP SYN packets, which control the maximum packet size
1213 for that connection.
1214
1215 To compile it as a module, choose M here. If unsure, say N.
1216
1217 config NETFILTER_XT_MATCH_TIME
1218 tristate '"time" match support'
1219 depends on NETFILTER_ADVANCED
1220 ---help---
1221 This option adds a "time" match, which allows you to match based on
1222 the packet arrival time (at the machine which netfilter is running)
1223 on) or departure time/date (for locally generated packets).
1224
1225 If you say Y here, try `iptables -m time --help` for
1226 more information.
1227
1228 If you want to compile it as a module, say M here.
1229 If unsure, say N.
1230
1231 config NETFILTER_XT_MATCH_U32
1232 tristate '"u32" match support'
1233 depends on NETFILTER_ADVANCED
1234 ---help---
1235 u32 allows you to extract quantities of up to 4 bytes from a packet,
1236 AND them with specified masks, shift them by specified amounts and
1237 test whether the results are in any of a set of specified ranges.
1238 The specification of what to extract is general enough to skip over
1239 headers with lengths stored in the packet, as in IP or TCP header
1240 lengths.
1241
1242 Details and examples are in the kernel module source.
1243
1244 endif # NETFILTER_XTABLES
1245
1246 endmenu
1247
1248 source "net/netfilter/ipset/Kconfig"
1249
1250 source "net/netfilter/ipvs/Kconfig"
This page took 0.099152 seconds and 4 git commands to generate.