Linux Audio

Check our new training course

Linux BSP development engineering services

Need help to port Linux and bootloaders to your hardware?
Loading...
v6.13.7
  1# SPDX-License-Identifier: GPL-2.0-only
  2#
  3# IP netfilter configuration
  4#
  5
  6menu "IP: Netfilter Configuration"
  7	depends on INET && NETFILTER
  8
  9config NF_DEFRAG_IPV4
 10	tristate
 11	default n
 12
 13# old sockopt interface and eval loop
 14config IP_NF_IPTABLES_LEGACY
 15	tristate "Legacy IP tables support"
 16	default	n
 17	select NETFILTER_XTABLES
 18	help
 19	  iptables is a legacy packet classifier.
 20	  This is not needed if you are using iptables over nftables
 21	  (iptables-nft).
 22
 23config NF_SOCKET_IPV4
 24	tristate "IPv4 socket lookup support"
 25	help
 26	  This option enables the IPv4 socket lookup infrastructure. This is
 27	  is required by the {ip,nf}tables socket match.
 28
 29config NF_TPROXY_IPV4
 30	tristate "IPv4 tproxy support"
 31
 32if NF_TABLES
 33
 34config NF_TABLES_IPV4
 35	bool "IPv4 nf_tables support"
 36	help
 37	  This option enables the IPv4 support for nf_tables.
 38
 39if NF_TABLES_IPV4
 40
 41config NFT_REJECT_IPV4
 42	select NF_REJECT_IPV4
 43	default NFT_REJECT
 44	tristate
 45
 46config NFT_DUP_IPV4
 47	tristate "IPv4 nf_tables packet duplication support"
 48	depends on !NF_CONNTRACK || NF_CONNTRACK
 49	select NF_DUP_IPV4
 50	help
 51	  This module enables IPv4 packet duplication support for nf_tables.
 52
 53config NFT_FIB_IPV4
 54	select NFT_FIB
 55	tristate "nf_tables fib / ip route lookup support"
 56	help
 57	  This module enables IPv4 FIB lookups, e.g. for reverse path filtering.
 58	  It also allows query of the FIB for the route type, e.g. local, unicast,
 59	  multicast or blackhole.
 60
 61endif # NF_TABLES_IPV4
 62
 63config NF_TABLES_ARP
 64	bool "ARP nf_tables support"
 65	select NETFILTER_FAMILY_ARP
 66	help
 67	  This option enables the ARP support for nf_tables.
 68
 69endif # NF_TABLES
 70
 71config NF_DUP_IPV4
 72	tristate "Netfilter IPv4 packet duplication to alternate destination"
 73	depends on !NF_CONNTRACK || NF_CONNTRACK
 74	help
 75	  This option enables the nf_dup_ipv4 core, which duplicates an IPv4
 76	  packet to be rerouted to another destination.
 77
 78config NF_LOG_ARP
 79	tristate "ARP packet logging"
 80	default m if NETFILTER_ADVANCED=n
 81	select NF_LOG_SYSLOG
 82	help
 83	This is a backwards-compat option for the user's convenience
 84	(e.g. when running oldconfig). It selects CONFIG_NF_LOG_SYSLOG.
 
 
 
 
 
 85
 86config NF_LOG_IPV4
 87	tristate "IPv4 packet logging"
 88	default m if NETFILTER_ADVANCED=n
 89	select NF_LOG_SYSLOG
 90	help
 91	This is a backwards-compat option for the user's convenience
 92	(e.g. when running oldconfig). It selects CONFIG_NF_LOG_SYSLOG.
 93
 94config NF_REJECT_IPV4
 95	tristate "IPv4 packet rejection"
 96	default m if NETFILTER_ADVANCED=n
 
 
 
 
 
 97
 98if NF_NAT
 99config NF_NAT_SNMP_BASIC
100	tristate "Basic SNMP-ALG support"
101	depends on NF_CONNTRACK_SNMP
102	depends on NETFILTER_ADVANCED
103	default NF_NAT && NF_CONNTRACK_SNMP
104	select ASN1
105	help
 
 
106
107	  This module implements an Application Layer Gateway (ALG) for
108	  SNMP payloads.  In conjunction with NAT, it allows a network
109	  management system to access multiple private networks with
110	  conflicting addresses.  It works by modifying IP addresses
111	  inside SNMP payloads to match IP-layer NAT mapping.
112
113	  This is the "basic" form of SNMP-ALG, as described in RFC 2962
114
115	  To compile it as a module, choose M here.  If unsure, say N.
116
117config NF_NAT_PPTP
118	tristate
119	depends on NF_CONNTRACK
120	default NF_CONNTRACK_PPTP
121
122config NF_NAT_H323
123	tristate
124	depends on NF_CONNTRACK
125	default NF_CONNTRACK_H323
126
127endif # NF_NAT
128
129config IP_NF_IPTABLES
130	tristate "IP tables support (required for filtering/masq/NAT)"
131	default m if NETFILTER_ADVANCED=n
132	select NETFILTER_XTABLES
133	help
134	  iptables is a general, extensible packet identification framework.
135	  The packet filtering and full NAT (masquerading, port forwarding,
136	  etc) subsystems now use this: say `Y' or `M' here if you want to use
137	  either of those.
138
139	  To compile it as a module, choose M here.  If unsure, say N.
140
141if IP_NF_IPTABLES
142
143# The matches.
144config IP_NF_MATCH_AH
145	tristate '"ah" match support'
146	depends on NETFILTER_ADVANCED
147	help
148	  This match extension allows you to match a range of SPIs
149	  inside AH header of IPSec packets.
150
151	  To compile it as a module, choose M here.  If unsure, say N.
152
153config IP_NF_MATCH_ECN
154	tristate '"ecn" match support'
155	depends on NETFILTER_ADVANCED
156	select NETFILTER_XT_MATCH_ECN
157	help
158	This is a backwards-compat option for the user's convenience
159	(e.g. when running oldconfig). It selects
160	CONFIG_NETFILTER_XT_MATCH_ECN.
161
162config IP_NF_MATCH_RPFILTER
163	tristate '"rpfilter" reverse path filter match support'
164	depends on NETFILTER_ADVANCED
165	depends on IP_NF_MANGLE || IP_NF_RAW || NFT_COMPAT
166	help
167	  This option allows you to match packets whose replies would
168	  go out via the interface the packet came in.
169
170	  To compile it as a module, choose M here.  If unsure, say N.
171	  The module will be called ipt_rpfilter.
172
173config IP_NF_MATCH_TTL
174	tristate '"ttl" match support'
175	depends on NETFILTER_ADVANCED
176	select NETFILTER_XT_MATCH_HL
177	help
178	This is a backwards-compat option for the user's convenience
179	(e.g. when running oldconfig). It selects
180	CONFIG_NETFILTER_XT_MATCH_HL.
181
182# `filter', generic and specific targets
183config IP_NF_FILTER
184	tristate "Packet filtering"
185	default m if NETFILTER_ADVANCED=n
186	select IP_NF_IPTABLES_LEGACY
187	help
188	  Packet filtering defines a table `filter', which has a series of
189	  rules for simple packet filtering at local input, forwarding and
190	  local output.  See the man page for iptables(8).
191
192	  To compile it as a module, choose M here.  If unsure, say N.
193
194config IP_NF_TARGET_REJECT
195	tristate "REJECT target support"
196	depends on IP_NF_FILTER || NFT_COMPAT
197	select NF_REJECT_IPV4
198	default m if NETFILTER_ADVANCED=n
199	help
200	  The REJECT target allows a filtering rule to specify that an ICMP
201	  error should be issued in response to an incoming packet, rather
202	  than silently being dropped.
203
204	  To compile it as a module, choose M here.  If unsure, say N.
205
206config IP_NF_TARGET_SYNPROXY
207	tristate "SYNPROXY target support"
208	depends on NF_CONNTRACK && NETFILTER_ADVANCED
209	select NETFILTER_SYNPROXY
210	select SYN_COOKIES
211	help
212	  The SYNPROXY target allows you to intercept TCP connections and
213	  establish them using syncookies before they are passed on to the
214	  server. This allows to avoid conntrack and server resource usage
215	  during SYN-flood attacks.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
216
217	  To compile it as a module, choose M here. If unsure, say N.
218
219# NAT + specific targets: nf_conntrack
220config IP_NF_NAT
221	tristate "iptables NAT support"
222	depends on NF_CONNTRACK
223	default m if NETFILTER_ADVANCED=n
224	select NF_NAT
225	select NETFILTER_XT_NAT
226	select IP_NF_IPTABLES_LEGACY
227	help
228	  This enables the `nat' table in iptables. This allows masquerading,
229	  port forwarding and other forms of full Network Address Port
230	  Translation.
231
232	  To compile it as a module, choose M here.  If unsure, say N.
233
234if IP_NF_NAT
 
 
 
235
236config IP_NF_TARGET_MASQUERADE
237	tristate "MASQUERADE target support"
238	select NETFILTER_XT_TARGET_MASQUERADE
 
239	help
240	  This is a backwards-compat option for the user's convenience
241	  (e.g. when running oldconfig). It selects NETFILTER_XT_TARGET_MASQUERADE.
 
 
 
 
 
242
243config IP_NF_TARGET_NETMAP
244	tristate "NETMAP target support"
 
245	depends on NETFILTER_ADVANCED
246	select NETFILTER_XT_TARGET_NETMAP
247	help
248	This is a backwards-compat option for the user's convenience
249	(e.g. when running oldconfig). It selects
250	CONFIG_NETFILTER_XT_TARGET_NETMAP.
 
 
251
252config IP_NF_TARGET_REDIRECT
253	tristate "REDIRECT target support"
 
254	depends on NETFILTER_ADVANCED
255	select NETFILTER_XT_TARGET_REDIRECT
256	help
257	This is a backwards-compat option for the user's convenience
258	(e.g. when running oldconfig). It selects
259	CONFIG_NETFILTER_XT_TARGET_REDIRECT.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
260
261endif # IP_NF_NAT
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
262
263# mangle + specific targets
264config IP_NF_MANGLE
265	tristate "Packet mangling"
266	default m if NETFILTER_ADVANCED=n
267	select IP_NF_IPTABLES_LEGACY
268	help
269	  This option adds a `mangle' table to iptables: see the man page for
270	  iptables(8).  This table is used for various packet alterations
271	  which can effect how the packet is routed.
272
273	  To compile it as a module, choose M here.  If unsure, say N.
274
 
 
 
 
 
 
 
 
 
 
 
 
 
275config IP_NF_TARGET_ECN
276	tristate "ECN target support"
277	depends on IP_NF_MANGLE || NFT_COMPAT
278	depends on NETFILTER_ADVANCED
279	help
280	  This option adds a `ECN' target, which can be used in the iptables mangle
281	  table.
282
283	  You can use this target to remove the ECN bits from the IPv4 header of
284	  an IP packet.  This is particularly useful, if you need to work around
285	  existing ECN blackholes on the internet, but don't want to disable
286	  ECN support in general.
287
288	  To compile it as a module, choose M here.  If unsure, say N.
289
290config IP_NF_TARGET_TTL
291	tristate '"TTL" target support'
292	depends on NETFILTER_ADVANCED && IP_NF_MANGLE
293	select NETFILTER_XT_TARGET_HL
294	help
295	This is a backwards-compatible option for the user's convenience
296	(e.g. when running oldconfig). It selects
297	CONFIG_NETFILTER_XT_TARGET_HL.
298
299# raw + specific targets
300config IP_NF_RAW
301	tristate  'raw table support (required for NOTRACK/TRACE)'
302	select IP_NF_IPTABLES_LEGACY
303	help
304	  This option adds a `raw' table to iptables. This table is the very
305	  first in the netfilter framework and hooks in at the PREROUTING
306	  and OUTPUT chains.
307
308	  If you want to compile it as a module, say M here and read
309	  <file:Documentation/kbuild/modules.rst>.  If unsure, say `N'.
310
311# security table for MAC policy
312config IP_NF_SECURITY
313	tristate "Security table"
314	depends on SECURITY
315	depends on NETFILTER_ADVANCED
316	select IP_NF_IPTABLES_LEGACY
317	help
318	  This option adds a `security' table to iptables, for use
319	  with Mandatory Access Control (MAC) policy.
320
321	  If unsure, say N.
322
323endif # IP_NF_IPTABLES
324
325# ARP tables
326config IP_NF_ARPTABLES
327	tristate "Legacy ARPTABLES support"
328	depends on NETFILTER_XTABLES
329	default n
330	help
331	  arptables is a legacy packet classifier.
332	  This is not needed if you are using arptables over nftables
333	  (iptables-nft).
334
335config NFT_COMPAT_ARP
336	tristate
337	depends on NF_TABLES_ARP && NFT_COMPAT
338	default m if NFT_COMPAT=m
339	default y if NFT_COMPAT=y
340
341config IP_NF_ARPFILTER
342	tristate "arptables-legacy packet filtering support"
343	select IP_NF_ARPTABLES
344	select NETFILTER_FAMILY_ARP
345	depends on NETFILTER_XTABLES
346	help
347	  ARP packet filtering defines a table `filter', which has a series of
348	  rules for simple ARP packet filtering at local input and
349	  local output.  This is only needed for arptables-legacy(8).
350	  Neither arptables-nft nor nftables need this to work.
351
352	  To compile it as a module, choose M here.  If unsure, say N.
353
354config IP_NF_ARP_MANGLE
355	tristate "ARP payload mangling"
356	depends on IP_NF_ARPTABLES || NFT_COMPAT_ARP
357	help
358	  Allows altering the ARP packet payload: source and destination
359	  hardware and network addresses.
360
361	  This option is needed by both arptables-legacy and arptables-nft.
362	  It is not used by nftables.
363
364endmenu
365
v3.1
 
  1#
  2# IP netfilter configuration
  3#
  4
  5menu "IP: Netfilter Configuration"
  6	depends on INET && NETFILTER
  7
  8config NF_DEFRAG_IPV4
  9	tristate
 10	default n
 11
 12config NF_CONNTRACK_IPV4
 13	tristate "IPv4 connection tracking support (required for NAT)"
 14	depends on NF_CONNTRACK
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 15	default m if NETFILTER_ADVANCED=n
 16	select NF_DEFRAG_IPV4
 17	---help---
 18	  Connection tracking keeps a record of what packets have passed
 19	  through your machine, in order to figure out how they are related
 20	  into connections.
 21
 22	  This is IPv4 support on Layer 3 independent connection tracking.
 23	  Layer 3 independent connection tracking is experimental scheme
 24	  which generalize ip_conntrack to support other layer 3 protocols.
 25
 26	  To compile it as a module, choose M here.  If unsure, say N.
 
 
 
 
 
 
 27
 28config NF_CONNTRACK_PROC_COMPAT
 29	bool "proc/sysctl compatibility with old connection tracking"
 30	depends on NF_CONNTRACK_IPV4
 31	default y
 32	help
 33	  This option enables /proc and sysctl compatibility with the old
 34	  layer 3 dependent connection tracking. This is needed to keep
 35	  old programs that have not been adapted to the new names working.
 36
 37	  If unsure, say Y.
 38
 39config IP_NF_QUEUE
 40	tristate "IP Userspace queueing via NETLINK (OBSOLETE)"
 41	depends on NETFILTER_ADVANCED
 
 
 42	help
 43	  Netfilter has the ability to queue packets to user space: the
 44	  netlink device can be used to access them using this driver.
 45
 46	  This option enables the old IPv4-only "ip_queue" implementation
 47	  which has been obsoleted by the new "nfnetlink_queue" code (see
 48	  CONFIG_NETFILTER_NETLINK_QUEUE).
 
 
 
 
 49
 50	  To compile it as a module, choose M here.  If unsure, say N.
 51
 
 
 
 
 
 
 
 
 
 
 
 
 52config IP_NF_IPTABLES
 53	tristate "IP tables support (required for filtering/masq/NAT)"
 54	default m if NETFILTER_ADVANCED=n
 55	select NETFILTER_XTABLES
 56	help
 57	  iptables is a general, extensible packet identification framework.
 58	  The packet filtering and full NAT (masquerading, port forwarding,
 59	  etc) subsystems now use this: say `Y' or `M' here if you want to use
 60	  either of those.
 61
 62	  To compile it as a module, choose M here.  If unsure, say N.
 63
 64if IP_NF_IPTABLES
 65
 66# The matches.
 67config IP_NF_MATCH_AH
 68	tristate '"ah" match support'
 69	depends on NETFILTER_ADVANCED
 70	help
 71	  This match extension allows you to match a range of SPIs
 72	  inside AH header of IPSec packets.
 73
 74	  To compile it as a module, choose M here.  If unsure, say N.
 75
 76config IP_NF_MATCH_ECN
 77	tristate '"ecn" match support'
 78	depends on NETFILTER_ADVANCED
 
 79	help
 80	  This option adds a `ECN' match, which allows you to match against
 81	  the IPv4 and TCP header ECN fields.
 
 
 
 
 
 
 
 
 
 82
 83	  To compile it as a module, choose M here.  If unsure, say N.
 
 84
 85config IP_NF_MATCH_TTL
 86	tristate '"ttl" match support'
 87	depends on NETFILTER_ADVANCED
 88	select NETFILTER_XT_MATCH_HL
 89	---help---
 90	This is a backwards-compat option for the user's convenience
 91	(e.g. when running oldconfig). It selects
 92	CONFIG_NETFILTER_XT_MATCH_HL.
 93
 94# `filter', generic and specific targets
 95config IP_NF_FILTER
 96	tristate "Packet filtering"
 97	default m if NETFILTER_ADVANCED=n
 
 98	help
 99	  Packet filtering defines a table `filter', which has a series of
100	  rules for simple packet filtering at local input, forwarding and
101	  local output.  See the man page for iptables(8).
102
103	  To compile it as a module, choose M here.  If unsure, say N.
104
105config IP_NF_TARGET_REJECT
106	tristate "REJECT target support"
107	depends on IP_NF_FILTER
 
108	default m if NETFILTER_ADVANCED=n
109	help
110	  The REJECT target allows a filtering rule to specify that an ICMP
111	  error should be issued in response to an incoming packet, rather
112	  than silently being dropped.
113
114	  To compile it as a module, choose M here.  If unsure, say N.
115
116config IP_NF_TARGET_LOG
117	tristate "LOG target support"
118	default m if NETFILTER_ADVANCED=n
119	help
120	  This option adds a `LOG' target, which allows you to create rules in
121	  any iptables table which records the packet header to the syslog.
122
123	  To compile it as a module, choose M here.  If unsure, say N.
124
125config IP_NF_TARGET_ULOG
126	tristate "ULOG target support"
127	default m if NETFILTER_ADVANCED=n
128	---help---
129
130	  This option enables the old IPv4-only "ipt_ULOG" implementation
131	  which has been obsoleted by the new "nfnetlink_log" code (see
132	  CONFIG_NETFILTER_NETLINK_LOG).
133
134	  This option adds a `ULOG' target, which allows you to create rules in
135	  any iptables table. The packet is passed to a userspace logging
136	  daemon using netlink multicast sockets; unlike the LOG target
137	  which can only be viewed through syslog.
138
139	  The appropriate userspace logging daemon (ulogd) may be obtained from
140	  <http://www.netfilter.org/projects/ulogd/index.html>
141
142	  To compile it as a module, choose M here.  If unsure, say N.
143
144# NAT + specific targets: nf_conntrack
145config NF_NAT
146	tristate "Full NAT"
147	depends on NF_CONNTRACK_IPV4
148	default m if NETFILTER_ADVANCED=n
 
 
 
149	help
150	  The Full NAT option allows masquerading, port forwarding and other
151	  forms of full Network Address Port Translation.  It is controlled by
152	  the `nat' table in iptables: see the man page for iptables(8).
153
154	  To compile it as a module, choose M here.  If unsure, say N.
155
156config NF_NAT_NEEDED
157	bool
158	depends on NF_NAT
159	default y
160
161config IP_NF_TARGET_MASQUERADE
162	tristate "MASQUERADE target support"
163	depends on NF_NAT
164	default m if NETFILTER_ADVANCED=n
165	help
166	  Masquerading is a special case of NAT: all outgoing connections are
167	  changed to seem to come from a particular interface's address, and
168	  if the interface goes down, those connections are lost.  This is
169	  only useful for dialup accounts with dynamic IP address (ie. your IP
170	  address will be different on next dialup).
171
172	  To compile it as a module, choose M here.  If unsure, say N.
173
174config IP_NF_TARGET_NETMAP
175	tristate "NETMAP target support"
176	depends on NF_NAT
177	depends on NETFILTER_ADVANCED
 
178	help
179	  NETMAP is an implementation of static 1:1 NAT mapping of network
180	  addresses. It maps the network address part, while keeping the host
181	  address part intact.
182
183	  To compile it as a module, choose M here.  If unsure, say N.
184
185config IP_NF_TARGET_REDIRECT
186	tristate "REDIRECT target support"
187	depends on NF_NAT
188	depends on NETFILTER_ADVANCED
 
189	help
190	  REDIRECT is a special case of NAT: all incoming connections are
191	  mapped onto the incoming interface's address, causing the packets to
192	  come to the local machine instead of passing through.  This is
193	  useful for transparent proxies.
194
195	  To compile it as a module, choose M here.  If unsure, say N.
196
197config NF_NAT_SNMP_BASIC
198	tristate "Basic SNMP-ALG support"
199	depends on NF_CONNTRACK_SNMP && NF_NAT
200	depends on NETFILTER_ADVANCED
201	default NF_NAT && NF_CONNTRACK_SNMP
202	---help---
203
204	  This module implements an Application Layer Gateway (ALG) for
205	  SNMP payloads.  In conjunction with NAT, it allows a network
206	  management system to access multiple private networks with
207	  conflicting addresses.  It works by modifying IP addresses
208	  inside SNMP payloads to match IP-layer NAT mapping.
209
210	  This is the "basic" form of SNMP-ALG, as described in RFC 2962
211
212	  To compile it as a module, choose M here.  If unsure, say N.
213
214# If they want FTP, set to $CONFIG_IP_NF_NAT (m or y),
215# or $CONFIG_IP_NF_FTP (m or y), whichever is weaker.
216# From kconfig-language.txt:
217#
218#           <expr> '&&' <expr>                   (6)
219#
220# (6) Returns the result of min(/expr/, /expr/).
221config NF_NAT_PROTO_DCCP
222	tristate
223	depends on NF_NAT && NF_CT_PROTO_DCCP
224	default NF_NAT && NF_CT_PROTO_DCCP
225
226config NF_NAT_PROTO_GRE
227	tristate
228	depends on NF_NAT && NF_CT_PROTO_GRE
229
230config NF_NAT_PROTO_UDPLITE
231	tristate
232	depends on NF_NAT && NF_CT_PROTO_UDPLITE
233	default NF_NAT && NF_CT_PROTO_UDPLITE
234
235config NF_NAT_PROTO_SCTP
236	tristate
237	default NF_NAT && NF_CT_PROTO_SCTP
238	depends on NF_NAT && NF_CT_PROTO_SCTP
239	select LIBCRC32C
240
241config NF_NAT_FTP
242	tristate
243	depends on NF_CONNTRACK && NF_NAT
244	default NF_NAT && NF_CONNTRACK_FTP
245
246config NF_NAT_IRC
247	tristate
248	depends on NF_CONNTRACK && NF_NAT
249	default NF_NAT && NF_CONNTRACK_IRC
250
251config NF_NAT_TFTP
252	tristate
253	depends on NF_CONNTRACK && NF_NAT
254	default NF_NAT && NF_CONNTRACK_TFTP
255
256config NF_NAT_AMANDA
257	tristate
258	depends on NF_CONNTRACK && NF_NAT
259	default NF_NAT && NF_CONNTRACK_AMANDA
260
261config NF_NAT_PPTP
262	tristate
263	depends on NF_CONNTRACK && NF_NAT
264	default NF_NAT && NF_CONNTRACK_PPTP
265	select NF_NAT_PROTO_GRE
266
267config NF_NAT_H323
268	tristate
269	depends on NF_CONNTRACK && NF_NAT
270	default NF_NAT && NF_CONNTRACK_H323
271
272config NF_NAT_SIP
273	tristate
274	depends on NF_CONNTRACK && NF_NAT
275	default NF_NAT && NF_CONNTRACK_SIP
276
277# mangle + specific targets
278config IP_NF_MANGLE
279	tristate "Packet mangling"
280	default m if NETFILTER_ADVANCED=n
 
281	help
282	  This option adds a `mangle' table to iptables: see the man page for
283	  iptables(8).  This table is used for various packet alterations
284	  which can effect how the packet is routed.
285
286	  To compile it as a module, choose M here.  If unsure, say N.
287
288config IP_NF_TARGET_CLUSTERIP
289	tristate "CLUSTERIP target support (EXPERIMENTAL)"
290	depends on IP_NF_MANGLE && EXPERIMENTAL
291	depends on NF_CONNTRACK_IPV4
292	depends on NETFILTER_ADVANCED
293	select NF_CONNTRACK_MARK
294	help
295	  The CLUSTERIP target allows you to build load-balancing clusters of
296	  network servers without having a dedicated load-balancing
297	  router/server/switch.
298	
299	  To compile it as a module, choose M here.  If unsure, say N.
300
301config IP_NF_TARGET_ECN
302	tristate "ECN target support"
303	depends on IP_NF_MANGLE
304	depends on NETFILTER_ADVANCED
305	---help---
306	  This option adds a `ECN' target, which can be used in the iptables mangle
307	  table.  
308
309	  You can use this target to remove the ECN bits from the IPv4 header of
310	  an IP packet.  This is particularly useful, if you need to work around
311	  existing ECN blackholes on the internet, but don't want to disable
312	  ECN support in general.
313
314	  To compile it as a module, choose M here.  If unsure, say N.
315
316config IP_NF_TARGET_TTL
317	tristate '"TTL" target support'
318	depends on NETFILTER_ADVANCED && IP_NF_MANGLE
319	select NETFILTER_XT_TARGET_HL
320	---help---
321	This is a backwards-compatible option for the user's convenience
322	(e.g. when running oldconfig). It selects
323	CONFIG_NETFILTER_XT_TARGET_HL.
324
325# raw + specific targets
326config IP_NF_RAW
327	tristate  'raw table support (required for NOTRACK/TRACE)'
328	depends on NETFILTER_ADVANCED
329	help
330	  This option adds a `raw' table to iptables. This table is the very
331	  first in the netfilter framework and hooks in at the PREROUTING
332	  and OUTPUT chains.
333	
334	  If you want to compile it as a module, say M here and read
335	  <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'.
336
337# security table for MAC policy
338config IP_NF_SECURITY
339	tristate "Security table"
340	depends on SECURITY
341	depends on NETFILTER_ADVANCED
 
342	help
343	  This option adds a `security' table to iptables, for use
344	  with Mandatory Access Control (MAC) policy.
345	 
346	  If unsure, say N.
347
348endif # IP_NF_IPTABLES
349
350# ARP tables
351config IP_NF_ARPTABLES
352	tristate "ARP tables support"
353	select NETFILTER_XTABLES
354	depends on NETFILTER_ADVANCED
355	help
356	  arptables is a general, extensible packet identification framework.
357	  The ARP packet filtering and mangling (manipulation)subsystems
358	  use this: say Y or M here if you want to use either of those.
359
360	  To compile it as a module, choose M here.  If unsure, say N.
361
362if IP_NF_ARPTABLES
 
 
363
364config IP_NF_ARPFILTER
365	tristate "ARP packet filtering"
 
 
 
366	help
367	  ARP packet filtering defines a table `filter', which has a series of
368	  rules for simple ARP packet filtering at local input and
369	  local output.  On a bridge, you can also specify filtering rules
370	  for forwarded ARP packets. See the man page for arptables(8).
371
372	  To compile it as a module, choose M here.  If unsure, say N.
373
374config IP_NF_ARP_MANGLE
375	tristate "ARP payload mangling"
 
376	help
377	  Allows altering the ARP packet payload: source and destination
378	  hardware and network addresses.
379
380endif # IP_NF_ARPTABLES
 
381
382endmenu
383