[net-next-2.6.git] / net / Kconfig

#
# Network configuration
#

menuconfig NET
	bool "Networking support"
	---help---
	  Unless you really know what you are doing, you should say Y here.
	  The reason is that some programs need kernel networking support even
	  when running on a stand-alone machine that isn't connected to any
	  other computer.
	  
	  If you are upgrading from an older kernel, you
	  should consider updating your networking tools too because changes
	  in the kernel and the tools often go hand in hand. The tools are
	  contained in the package net-tools, the location and version number
	  of which are given in <file:Documentation/Changes>.

	  For a general introduction to Linux networking, it is highly
	  recommended to read the NET-HOWTO, available from
	  <http://www.tldp.org/docs.html#howto>.

if NET

menu "Networking options"

config NET_NS
	bool "Network namespace support"
	default n
	depends on EXPERIMENTAL && !SYSFS && NAMESPACES
	help
	  Allow user space to create what appear to be multiple instances
	  of the network stack.

source "net/packet/Kconfig"
source "net/unix/Kconfig"
source "net/xfrm/Kconfig"
source "net/iucv/Kconfig"

config INET
	bool "TCP/IP networking"
	---help---
	  These are the protocols used on the Internet and on most local
	  Ethernets. It is highly recommended to say Y here (this will enlarge
	  your kernel by about 400 KB), since some programs (e.g. the X window
	  system) use TCP/IP even if your machine is not connected to any
	  other computer. You will get the so-called loopback device which
	  allows you to ping yourself (great fun, that!).

	  For an excellent introduction to Linux networking, please read the
	  Linux Networking HOWTO, available from
	  <http://www.tldp.org/docs.html#howto>.

	  If you say Y here and also to "/proc file system support" and
	  "Sysctl support" below, you can change various aspects of the
	  behavior of the TCP/IP code by writing to the (virtual) files in
	  /proc/sys/net/ipv4/*; the options are explained in the file
	  <file:Documentation/networking/ip-sysctl.txt>.

	  Short answer: say Y.

if INET
source "net/ipv4/Kconfig"
source "net/ipv6/Kconfig"
source "net/netlabel/Kconfig"

endif # if INET

config NETWORK_SECMARK
	bool "Security Marking"
	help
	  This enables security marking of network packets, similar
	  to nfmark, but designated for security purposes.
	  If you are unsure how to answer this question, answer N.

menuconfig NETFILTER
	bool "Network packet filtering framework (Netfilter)"
	---help---
	  Netfilter is a framework for filtering and mangling network packets
	  that pass through your Linux box.

	  The most common use of packet filtering is to run your Linux box as
	  a firewall protecting a local network from the Internet. The type of
	  firewall provided by this kernel support is called a "packet
	  filter", which means that it can reject individual network packets
	  based on type, source, destination etc. The other kind of firewall,
	  a "proxy-based" one, is more secure but more intrusive and more
	  bothersome to set up; it inspects the network traffic much more
	  closely, modifies it and has knowledge about the higher level
	  protocols, which a packet filter lacks. Moreover, proxy-based
	  firewalls often require changes to the programs running on the local
	  clients. Proxy-based firewalls don't need support by the kernel, but
	  they are often combined with a packet filter, which only works if
	  you say Y here.

	  You should also say Y here if you intend to use your Linux box as
	  the gateway to the Internet for a local network of machines without
	  globally valid IP addresses. This is called "masquerading": if one
	  of the computers on your local network wants to send something to
	  the outside, your box can "masquerade" as that computer, i.e. it
	  forwards the traffic to the intended outside destination, but
	  modifies the packets to make it look like they came from the
	  firewall box itself. It works both ways: if the outside host
	  replies, the Linux box will silently forward the traffic to the
	  correct local computer. This way, the computers on your local net
	  are completely invisible to the outside world, even though they can
	  reach the outside and can receive replies. It is even possible to
	  run globally visible servers from within a masqueraded local network
	  using a mechanism called portforwarding. Masquerading is also often
	  called NAT (Network Address Translation).

	  Another use of Netfilter is in transparent proxying: if a machine on
	  the local network tries to connect to an outside host, your Linux
	  box can transparently forward the traffic to a local server,
	  typically a caching proxy server.

	  Yet another use of Netfilter is building a bridging firewall. Using
	  a bridge with Network packet filtering enabled makes iptables "see"
	  the bridged traffic. For filtering on the lower network and Ethernet
	  protocols over the bridge, use ebtables (under bridge netfilter
	  configuration).

	  Various modules exist for netfilter which replace the previous
	  masquerading (ipmasqadm), packet filtering (ipchains), transparent
	  proxying, and portforwarding mechanisms. Please see
	  <file:Documentation/Changes> under "iptables" for the location of
	  these packages.

	  Make sure to say N to "Fast switching" below if you intend to say Y
	  here, as Fast switching currently bypasses netfilter.

	  Chances are that you should say Y here if you compile a kernel which
	  will run as a router and N for regular hosts. If unsure, say N.

if NETFILTER

config NETFILTER_DEBUG
	bool "Network packet filtering debugging"
	depends on NETFILTER
	help
	  You can say Y here if you want to get additional messages useful in
	  debugging the netfilter code.

config NETFILTER_ADVANCED
	bool "Advanced netfilter configuration"
	depends on NETFILTER
	default y
	help
	  If you say Y here you can select between all the netfilter modules.
	  If you say N the more ununsual ones will not be shown and the
	  basic ones needed by most people will default to 'M'.

	  If unsure, say Y.

config BRIDGE_NETFILTER
	bool "Bridged IP/ARP packets filtering"
	depends on BRIDGE && NETFILTER && INET
	depends on NETFILTER_ADVANCED
	default y
	---help---
	  Enabling this option will let arptables resp. iptables see bridged
	  ARP resp. IP traffic. If you want a bridging firewall, you probably
	  want this option enabled.
	  Enabling or disabling this option doesn't enable or disable
	  ebtables.

	  If unsure, say N.

source "net/netfilter/Kconfig"
source "net/ipv4/netfilter/Kconfig"
source "net/ipv6/netfilter/Kconfig"
source "net/decnet/netfilter/Kconfig"
source "net/bridge/netfilter/Kconfig"

endif

source "net/dccp/Kconfig"
source "net/sctp/Kconfig"
source "net/tipc/Kconfig"
source "net/atm/Kconfig"
source "net/802/Kconfig"
source "net/bridge/Kconfig"
source "net/8021q/Kconfig"
source "net/decnet/Kconfig"
source "net/llc/Kconfig"
source "net/ipx/Kconfig"
source "drivers/net/appletalk/Kconfig"
source "net/x25/Kconfig"
source "net/lapb/Kconfig"
source "net/econet/Kconfig"
source "net/wanrouter/Kconfig"
source "net/sched/Kconfig"

menu "Network testing"

config NET_PKTGEN
	tristate "Packet Generator (USE WITH CAUTION)"
	depends on PROC_FS
	---help---
	  This module will inject preconfigured packets, at a configurable
	  rate, out of a given interface.  It is used for network interface
	  stress testing and performance analysis.  If you don't understand
	  what was just said, you don't need it: say N.

	  Documentation on how to use the packet generator can be found
	  at <file:Documentation/networking/pktgen.txt>.

	  To compile this code as a module, choose M here: the
	  module will be called pktgen.

config NET_TCPPROBE
	tristate "TCP connection probing"
	depends on INET && EXPERIMENTAL && PROC_FS && KPROBES
	---help---
	This module allows for capturing the changes to TCP connection
	state in response to incoming packets. It is used for debugging
	TCP congestion avoidance modules. If you don't understand
	what was just said, you don't need it: say N.

	Documentation on how to use TCP connection probing can be found
	at http://linux-net.osdl.org/index.php/TcpProbe

	To compile this code as a module, choose M here: the
	module will be called tcp_probe.

endmenu

endmenu

source "net/ax25/Kconfig"
source "net/can/Kconfig"
source "net/irda/Kconfig"
source "net/bluetooth/Kconfig"
source "net/rxrpc/Kconfig"

config FIB_RULES
	bool

menu "Wireless"
	depends on !S390

source "net/wireless/Kconfig"
source "net/mac80211/Kconfig"
source "net/ieee80211/Kconfig"

endmenu

source "net/rfkill/Kconfig"
source "net/9p/Kconfig"

endif   # if NET
Commit	Line	Data
1da177e4 LT	1	#
	2	# Network configuration
	3	#
	4
031cf19e	5	menuconfig NET
1da177e4 LT	6	bool "Networking support"
	7	---help---
	8	Unless you really know what you are doing, you should say Y here.
	9	The reason is that some programs need kernel networking support even
	10	when running on a stand-alone machine that isn't connected to any
d5950b43 SR	11	other computer.
	12
	13	If you are upgrading from an older kernel, you
1da177e4 LT	14	should consider updating your networking tools too because changes
	15	in the kernel and the tools often go hand in hand. The tools are
	16	contained in the package net-tools, the location and version number
	17	of which are given in <file:Documentation/Changes>.
	18
	19	For a general introduction to Linux networking, it is highly
	20	recommended to read the NET-HOWTO, available from
	21	<http://www.tldp.org/docs.html#howto>.
	22
6a2e9b73	23	if NET
1da177e4	24
6a2e9b73	25	menu "Networking options"
1da177e4	26
9dd776b6 EB	27	config NET_NS
	28	bool "Network namespace support"
	29	default n
cbdc7387	30	depends on EXPERIMENTAL && !SYSFS && NAMESPACES
9dd776b6 EB	31	help
	32	Allow user space to create what appear to be multiple instances
	33	of the network stack.
	34
6a2e9b73 SR	35	source "net/packet/Kconfig"
	36	source "net/unix/Kconfig"
	37	source "net/xfrm/Kconfig"
2356f4cb	38	source "net/iucv/Kconfig"
1da177e4 LT	39
	40	config INET
	41	bool "TCP/IP networking"
	42	---help---
	43	These are the protocols used on the Internet and on most local
	44	Ethernets. It is highly recommended to say Y here (this will enlarge
cf80efc2	45	your kernel by about 400 KB), since some programs (e.g. the X window
1da177e4 LT	46	system) use TCP/IP even if your machine is not connected to any
	47	other computer. You will get the so-called loopback device which
	48	allows you to ping yourself (great fun, that!).
	49
	50	For an excellent introduction to Linux networking, please read the
	51	Linux Networking HOWTO, available from
	52	<http://www.tldp.org/docs.html#howto>.
	53
	54	If you say Y here and also to "/proc file system support" and
	55	"Sysctl support" below, you can change various aspects of the
	56	behavior of the TCP/IP code by writing to the (virtual) files in
	57	/proc/sys/net/ipv4/*; the options are explained in the file
	58	<file:Documentation/networking/ip-sysctl.txt>.
	59
	60	Short answer: say Y.
	61
6a2e9b73	62	if INET
1da177e4	63	source "net/ipv4/Kconfig"
1da177e4	64	source "net/ipv6/Kconfig"
38c94377	65	source "net/netlabel/Kconfig"
1da177e4	66
6a2e9b73 SR	67	endif # if INET
6a2e9b73 SR	68
984bc16c JM	69	config NETWORK_SECMARK
	70	bool "Security Marking"
	71	help
	72	This enables security marking of network packets, similar
	73	to nfmark, but designated for security purposes.
	74	If you are unsure how to answer this question, answer N.
	75
1da177e4	76	menuconfig NETFILTER
ef91fd52	77	bool "Network packet filtering framework (Netfilter)"
1da177e4 LT	78	---help---
	79	Netfilter is a framework for filtering and mangling network packets
	80	that pass through your Linux box.
	81
	82	The most common use of packet filtering is to run your Linux box as
	83	a firewall protecting a local network from the Internet. The type of
	84	firewall provided by this kernel support is called a "packet
	85	filter", which means that it can reject individual network packets
	86	based on type, source, destination etc. The other kind of firewall,
	87	a "proxy-based" one, is more secure but more intrusive and more
	88	bothersome to set up; it inspects the network traffic much more
	89	closely, modifies it and has knowledge about the higher level
	90	protocols, which a packet filter lacks. Moreover, proxy-based
	91	firewalls often require changes to the programs running on the local
	92	clients. Proxy-based firewalls don't need support by the kernel, but
	93	they are often combined with a packet filter, which only works if
	94	you say Y here.
	95
	96	You should also say Y here if you intend to use your Linux box as
	97	the gateway to the Internet for a local network of machines without
	98	globally valid IP addresses. This is called "masquerading": if one
	99	of the computers on your local network wants to send something to
	100	the outside, your box can "masquerade" as that computer, i.e. it
	101	forwards the traffic to the intended outside destination, but
	102	modifies the packets to make it look like they came from the
	103	firewall box itself. It works both ways: if the outside host
	104	replies, the Linux box will silently forward the traffic to the
	105	correct local computer. This way, the computers on your local net
	106	are completely invisible to the outside world, even though they can
	107	reach the outside and can receive replies. It is even possible to
	108	run globally visible servers from within a masqueraded local network
	109	using a mechanism called portforwarding. Masquerading is also often
	110	called NAT (Network Address Translation).
	111
	112	Another use of Netfilter is in transparent proxying: if a machine on
	113	the local network tries to connect to an outside host, your Linux
	114	box can transparently forward the traffic to a local server,
	115	typically a caching proxy server.
	116
	117	Yet another use of Netfilter is building a bridging firewall. Using
	118	a bridge with Network packet filtering enabled makes iptables "see"
	119	the bridged traffic. For filtering on the lower network and Ethernet
	120	protocols over the bridge, use ebtables (under bridge netfilter
	121	configuration).
	122
	123	Various modules exist for netfilter which replace the previous
	124	masquerading (ipmasqadm), packet filtering (ipchains), transparent
	125	proxying, and portforwarding mechanisms. Please see
	126	<file:Documentation/Changes> under "iptables" for the location of
	127	these packages.
	128
	129	Make sure to say N to "Fast switching" below if you intend to say Y
	130	here, as Fast switching currently bypasses netfilter.
	131
	132	Chances are that you should say Y here if you compile a kernel which
	133	will run as a router and N for regular hosts. If unsure, say N.
	134
	135	if NETFILTER
	136
	137	config NETFILTER_DEBUG
	138	bool "Network packet filtering debugging"
	139	depends on NETFILTER
	140	help
	141	You can say Y here if you want to get additional messages useful in
142	debugging the netfilter code.
143
33b8e776 PM	144	config NETFILTER_ADVANCED
	145	bool "Advanced netfilter configuration"
	146	depends on NETFILTER
	147	default y
	148	help
	149	If you say Y here you can select between all the netfilter modules.
	150	If you say N the more ununsual ones will not be shown and the
	151	basic ones needed by most people will default to 'M'.
	152
	153	If unsure, say Y.
	154
1da177e4 LT	155	config BRIDGE_NETFILTER
	156	bool "Bridged IP/ARP packets filtering"
	157	depends on BRIDGE && NETFILTER && INET
33b8e776	158	depends on NETFILTER_ADVANCED
1da177e4 LT	159	default y
	160	---help---
	161	Enabling this option will let arptables resp. iptables see bridged
	162	ARP resp. IP traffic. If you want a bridging firewall, you probably
	163	want this option enabled.
	164	Enabling or disabling this option doesn't enable or disable
	165	ebtables.
	166
	167	If unsure, say N.
	168
9eb0eec7	169	source "net/netfilter/Kconfig"
1da177e4 LT	170	source "net/ipv4/netfilter/Kconfig"
	171	source "net/ipv6/netfilter/Kconfig"
	172	source "net/decnet/netfilter/Kconfig"
	173	source "net/bridge/netfilter/Kconfig"
	174
	175	endif
	176
7c657876	177	source "net/dccp/Kconfig"
1da177e4	178	source "net/sctp/Kconfig"
1e63e681	179	source "net/tipc/Kconfig"
6a2e9b73	180	source "net/atm/Kconfig"
a19800d7	181	source "net/802/Kconfig"
6a2e9b73 SR	182	source "net/bridge/Kconfig"
6a2e9b73 SR	183	source "net/8021q/Kconfig"
1da177e4	184	source "net/decnet/Kconfig"
1da177e4	185	source "net/llc/Kconfig"
1da177e4	186	source "net/ipx/Kconfig"
1da177e4	187	source "drivers/net/appletalk/Kconfig"
6a2e9b73 SR	188	source "net/x25/Kconfig"
6a2e9b73 SR	189	source "net/lapb/Kconfig"
6a2e9b73 SR	190	source "net/econet/Kconfig"
6a2e9b73 SR	191	source "net/wanrouter/Kconfig"
1da177e4 LT	192	source "net/sched/Kconfig"
1da177e4 LT	193
1da177e4 LT	194	menu "Network testing"
	195
	196	config NET_PKTGEN
	197	tristate "Packet Generator (USE WITH CAUTION)"
	198	depends on PROC_FS
	199	---help---
	200	This module will inject preconfigured packets, at a configurable
	201	rate, out of a given interface. It is used for network interface
	202	stress testing and performance analysis. If you don't understand
	203	what was just said, you don't need it: say N.
	204
	205	Documentation on how to use the packet generator can be found
	206	at <file:Documentation/networking/pktgen.txt>.
	207
	208	To compile this code as a module, choose M here: the
	209	module will be called pktgen.
	210
a42e9d6c SH	211	config NET_TCPPROBE
	212	tristate "TCP connection probing"
	213	depends on INET && EXPERIMENTAL && PROC_FS && KPROBES
	214	---help---
	215	This module allows for capturing the changes to TCP connection
9dadaa19	216	state in response to incoming packets. It is used for debugging
a42e9d6c SH	217	TCP congestion avoidance modules. If you don't understand
	218	what was just said, you don't need it: say N.
	219
82fe7c92	220	Documentation on how to use TCP connection probing can be found
a42e9d6c SH	221	at http://linux-net.osdl.org/index.php/TcpProbe
	222
	223	To compile this code as a module, choose M here: the
	224	module will be called tcp_probe.
	225
1da177e4 LT	226	endmenu
	227
	228	endmenu
	229
1da177e4	230	source "net/ax25/Kconfig"
0d66548a	231	source "net/can/Kconfig"
1da177e4	232	source "net/irda/Kconfig"
1da177e4	233	source "net/bluetooth/Kconfig"
17926a79	234	source "net/rxrpc/Kconfig"
d86b5e0e	235
14c0b97d TG	236	config FIB_RULES
	237	bool
	238
2a5e1c0e	239	menu "Wireless"
f54bfc0e	240	depends on !S390
2a5e1c0e JB	241
2a5e1c0e JB	242	source "net/wireless/Kconfig"
f0706e82	243	source "net/mac80211/Kconfig"
2a5e1c0e JB	244	source "net/ieee80211/Kconfig"
	245
	246	endmenu
	247
cf4328cd	248	source "net/rfkill/Kconfig"
bd238fb4	249	source "net/9p/Kconfig"
cf4328cd	250
6a2e9b73	251	endif # if NET