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

#
# Network configuration
#

menuconfig NET
	bool "Networking support"
	select NLATTR
	---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

config WANT_COMPAT_NETLINK_MESSAGES
	bool
	help
	  This option can be selected by other options that need compat
	  netlink messages.

config COMPAT_NETLINK_MESSAGES
	def_bool y
	depends on COMPAT
	depends on WIRELESS_EXT || WANT_COMPAT_NETLINK_MESSAGES
	help
	  This option makes it possible to send different netlink messages
	  to tasks depending on whether the task is a compat task or not. To
	  achieve this, you need to set skb_shinfo(skb)->frag_list to the
	  compat skb before sending the skb, the netlink code will sort out
	  which message to actually pass to the task.

	  Newly written code should NEVER need this option but do
	  compat-independent messages instead!

menu "Networking options"

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.

config NETWORK_PHY_TIMESTAMPING
	bool "Timestamping in PHY devices"
	depends on EXPERIMENTAL
	help
	  This allows timestamping of network packets by PHYs with
	  hardware timestamping capabilities. This option adds some
	  overhead in the transmit and receive paths.

	  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.

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 unusual 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/rds/Kconfig"
source "net/tipc/Kconfig"
source "net/atm/Kconfig"
source "net/l2tp/Kconfig"
source "net/802/Kconfig"
source "net/bridge/Kconfig"
source "net/dsa/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/phonet/Kconfig"
source "net/ieee802154/Kconfig"
source "net/sched/Kconfig"
source "net/dcb/Kconfig"

config RPS
	boolean
	depends on SMP && SYSFS
	default y

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.

config NET_DROP_MONITOR
	boolean "Network packet drop alerting service"
	depends on INET && EXPERIMENTAL && TRACEPOINTS
	---help---
	This feature provides an alerting service to userspace in the
	event that packets are discarded in the network stack.  Alerts
	are broadcast via netlink socket to any listening user space
	process.  If you don't need network drop alerts, or if you are ok
	just checking the various proc files and other utilities for
	drop statistics, say N here.

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

menuconfig WIRELESS
	bool "Wireless"
	depends on !S390
	default y

if WIRELESS

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

endif # WIRELESS

source "net/wimax/Kconfig"

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


endif   # if NET
Commit	Line	Data
	1	#
	2	# Network configuration
	3	#
	4
	5	menuconfig NET
	6	bool "Networking support"
	7	select NLATTR
	8	---help---
	9	Unless you really know what you are doing, you should say Y here.
	10	The reason is that some programs need kernel networking support even
	11	when running on a stand-alone machine that isn't connected to any
	12	other computer.
	13
	14	If you are upgrading from an older kernel, you
	15	should consider updating your networking tools too because changes
	16	in the kernel and the tools often go hand in hand. The tools are
	17	contained in the package net-tools, the location and version number
	18	of which are given in <file:Documentation/Changes>.
	19
	20	For a general introduction to Linux networking, it is highly
	21	recommended to read the NET-HOWTO, available from
	22	<http://www.tldp.org/docs.html#howto>.
	23
	24	if NET
	25
	26	config WANT_COMPAT_NETLINK_MESSAGES
	27	bool
	28	help
	29	This option can be selected by other options that need compat
	30	netlink messages.
	31
	32	config COMPAT_NETLINK_MESSAGES
	33	def_bool y
	34	depends on COMPAT
	35	depends on WIRELESS_EXT \|\| WANT_COMPAT_NETLINK_MESSAGES
	36	help
	37	This option makes it possible to send different netlink messages
	38	to tasks depending on whether the task is a compat task or not. To
	39	achieve this, you need to set skb_shinfo(skb)->frag_list to the
	40	compat skb before sending the skb, the netlink code will sort out
	41	which message to actually pass to the task.
	42
	43	Newly written code should NEVER need this option but do
	44	compat-independent messages instead!
	45
	46	menu "Networking options"
	47
	48	source "net/packet/Kconfig"
	49	source "net/unix/Kconfig"
	50	source "net/xfrm/Kconfig"
	51	source "net/iucv/Kconfig"
	52
	53	config INET
	54	bool "TCP/IP networking"
	55	---help---
	56	These are the protocols used on the Internet and on most local
	57	Ethernets. It is highly recommended to say Y here (this will enlarge
	58	your kernel by about 400 KB), since some programs (e.g. the X window
	59	system) use TCP/IP even if your machine is not connected to any
	60	other computer. You will get the so-called loopback device which
	61	allows you to ping yourself (great fun, that!).
	62
	63	For an excellent introduction to Linux networking, please read the
	64	Linux Networking HOWTO, available from
	65	<http://www.tldp.org/docs.html#howto>.
	66
	67	If you say Y here and also to "/proc file system support" and
	68	"Sysctl support" below, you can change various aspects of the
	69	behavior of the TCP/IP code by writing to the (virtual) files in
	70	/proc/sys/net/ipv4/*; the options are explained in the file
	71	<file:Documentation/networking/ip-sysctl.txt>.
	72
	73	Short answer: say Y.
	74
	75	if INET
	76	source "net/ipv4/Kconfig"
	77	source "net/ipv6/Kconfig"
	78	source "net/netlabel/Kconfig"
	79
	80	endif # if INET
	81
	82	config NETWORK_SECMARK
	83	bool "Security Marking"
	84	help
	85	This enables security marking of network packets, similar
	86	to nfmark, but designated for security purposes.
	87	If you are unsure how to answer this question, answer N.
	88
	89	config NETWORK_PHY_TIMESTAMPING
	90	bool "Timestamping in PHY devices"
	91	depends on EXPERIMENTAL
	92	help
	93	This allows timestamping of network packets by PHYs with
	94	hardware timestamping capabilities. This option adds some
	95	overhead in the transmit and receive paths.
	96
	97	If you are unsure how to answer this question, answer N.
	98
	99	menuconfig NETFILTER
	100	bool "Network packet filtering framework (Netfilter)"
	101	---help---
	102	Netfilter is a framework for filtering and mangling network packets
	103	that pass through your Linux box.
	104
	105	The most common use of packet filtering is to run your Linux box as
	106	a firewall protecting a local network from the Internet. The type of
	107	firewall provided by this kernel support is called a "packet
	108	filter", which means that it can reject individual network packets
	109	based on type, source, destination etc. The other kind of firewall,
	110	a "proxy-based" one, is more secure but more intrusive and more
	111	bothersome to set up; it inspects the network traffic much more
	112	closely, modifies it and has knowledge about the higher level
	113	protocols, which a packet filter lacks. Moreover, proxy-based
	114	firewalls often require changes to the programs running on the local
	115	clients. Proxy-based firewalls don't need support by the kernel, but
	116	they are often combined with a packet filter, which only works if
	117	you say Y here.
	118
	119	You should also say Y here if you intend to use your Linux box as
	120	the gateway to the Internet for a local network of machines without
	121	globally valid IP addresses. This is called "masquerading": if one
	122	of the computers on your local network wants to send something to
	123	the outside, your box can "masquerade" as that computer, i.e. it
	124	forwards the traffic to the intended outside destination, but
	125	modifies the packets to make it look like they came from the
	126	firewall box itself. It works both ways: if the outside host
	127	replies, the Linux box will silently forward the traffic to the
	128	correct local computer. This way, the computers on your local net
	129	are completely invisible to the outside world, even though they can
	130	reach the outside and can receive replies. It is even possible to
	131	run globally visible servers from within a masqueraded local network
	132	using a mechanism called portforwarding. Masquerading is also often
	133	called NAT (Network Address Translation).
	134
	135	Another use of Netfilter is in transparent proxying: if a machine on
	136	the local network tries to connect to an outside host, your Linux
	137	box can transparently forward the traffic to a local server,
	138	typically a caching proxy server.
	139
	140	Yet another use of Netfilter is building a bridging firewall. Using
	141	a bridge with Network packet filtering enabled makes iptables "see"
	142	the bridged traffic. For filtering on the lower network and Ethernet
	143	protocols over the bridge, use ebtables (under bridge netfilter
	144	configuration).
	145
	146	Various modules exist for netfilter which replace the previous
	147	masquerading (ipmasqadm), packet filtering (ipchains), transparent
	148	proxying, and portforwarding mechanisms. Please see
	149	<file:Documentation/Changes> under "iptables" for the location of
	150	these packages.
	151
	152	if NETFILTER
	153
	154	config NETFILTER_DEBUG
	155	bool "Network packet filtering debugging"
	156	depends on NETFILTER
	157	help
	158	You can say Y here if you want to get additional messages useful in
	159	debugging the netfilter code.
	160
	161	config NETFILTER_ADVANCED
	162	bool "Advanced netfilter configuration"
	163	depends on NETFILTER
	164	default y
	165	help
	166	If you say Y here you can select between all the netfilter modules.
	167	If you say N the more unusual ones will not be shown and the
	168	basic ones needed by most people will default to 'M'.
	169
	170	If unsure, say Y.
	171
	172	config BRIDGE_NETFILTER
	173	bool "Bridged IP/ARP packets filtering"
	174	depends on BRIDGE && NETFILTER && INET
	175	depends on NETFILTER_ADVANCED
	176	default y
	177	---help---
	178	Enabling this option will let arptables resp. iptables see bridged
	179	ARP resp. IP traffic. If you want a bridging firewall, you probably
	180	want this option enabled.
	181	Enabling or disabling this option doesn't enable or disable
	182	ebtables.
	183
	184	If unsure, say N.
	185
	186	source "net/netfilter/Kconfig"
	187	source "net/ipv4/netfilter/Kconfig"
	188	source "net/ipv6/netfilter/Kconfig"
	189	source "net/decnet/netfilter/Kconfig"
	190	source "net/bridge/netfilter/Kconfig"
	191
	192	endif
	193
	194	source "net/dccp/Kconfig"
	195	source "net/sctp/Kconfig"
	196	source "net/rds/Kconfig"
	197	source "net/tipc/Kconfig"
	198	source "net/atm/Kconfig"
	199	source "net/l2tp/Kconfig"
	200	source "net/802/Kconfig"
	201	source "net/bridge/Kconfig"
	202	source "net/dsa/Kconfig"
	203	source "net/8021q/Kconfig"
	204	source "net/decnet/Kconfig"
	205	source "net/llc/Kconfig"
	206	source "net/ipx/Kconfig"
	207	source "drivers/net/appletalk/Kconfig"
	208	source "net/x25/Kconfig"
	209	source "net/lapb/Kconfig"
	210	source "net/econet/Kconfig"
	211	source "net/wanrouter/Kconfig"
	212	source "net/phonet/Kconfig"
	213	source "net/ieee802154/Kconfig"
	214	source "net/sched/Kconfig"
	215	source "net/dcb/Kconfig"
	216
	217	config RPS
	218	boolean
	219	depends on SMP && SYSFS
	220	default y
	221
	222	menu "Network testing"
	223
	224	config NET_PKTGEN
	225	tristate "Packet Generator (USE WITH CAUTION)"
	226	depends on PROC_FS
	227	---help---
	228	This module will inject preconfigured packets, at a configurable
	229	rate, out of a given interface. It is used for network interface
	230	stress testing and performance analysis. If you don't understand
	231	what was just said, you don't need it: say N.
	232
	233	Documentation on how to use the packet generator can be found
	234	at <file:Documentation/networking/pktgen.txt>.
	235
	236	To compile this code as a module, choose M here: the
	237	module will be called pktgen.
	238
	239	config NET_TCPPROBE
	240	tristate "TCP connection probing"
	241	depends on INET && EXPERIMENTAL && PROC_FS && KPROBES
	242	---help---
	243	This module allows for capturing the changes to TCP connection
	244	state in response to incoming packets. It is used for debugging
	245	TCP congestion avoidance modules. If you don't understand
	246	what was just said, you don't need it: say N.
	247
	248	Documentation on how to use TCP connection probing can be found
	249	at http://linux-net.osdl.org/index.php/TcpProbe
	250
	251	To compile this code as a module, choose M here: the
	252	module will be called tcp_probe.
	253
	254	config NET_DROP_MONITOR
	255	boolean "Network packet drop alerting service"
	256	depends on INET && EXPERIMENTAL && TRACEPOINTS
	257	---help---
	258	This feature provides an alerting service to userspace in the
	259	event that packets are discarded in the network stack. Alerts
	260	are broadcast via netlink socket to any listening user space
	261	process. If you don't need network drop alerts, or if you are ok
	262	just checking the various proc files and other utilities for
	263	drop statistics, say N here.
	264
	265	endmenu
	266
	267	endmenu
	268
	269	source "net/ax25/Kconfig"
	270	source "net/can/Kconfig"
	271	source "net/irda/Kconfig"
	272	source "net/bluetooth/Kconfig"
	273	source "net/rxrpc/Kconfig"
	274
	275	config FIB_RULES
	276	bool
	277
	278	menuconfig WIRELESS
	279	bool "Wireless"
	280	depends on !S390
	281	default y
	282
	283	if WIRELESS
	284
	285	source "net/wireless/Kconfig"
	286	source "net/mac80211/Kconfig"
	287
	288	endif # WIRELESS
	289
	290	source "net/wimax/Kconfig"
	291
	292	source "net/rfkill/Kconfig"
	293	source "net/9p/Kconfig"
	294	source "net/caif/Kconfig"
	295
	296
	297	endif # if NET