2 # Network configuration
6 bool "Networking support"
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
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>.
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>.
26 config WANT_COMPAT_NETLINK_MESSAGES
29 This option can be selected by other options that need compat
32 config COMPAT_NETLINK_MESSAGES
35 depends on WIRELESS_EXT || WANT_COMPAT_NETLINK_MESSAGES
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.
43 Newly written code should NEVER need this option but do
44 compat-independent messages instead!
46 menu "Networking options"
49 bool "Network namespace support"
51 depends on EXPERIMENTAL && NAMESPACES
53 Allow user space to create what appear to be multiple instances
56 source "net/packet/Kconfig"
57 source "net/unix/Kconfig"
58 source "net/xfrm/Kconfig"
59 source "net/iucv/Kconfig"
62 bool "TCP/IP networking"
64 These are the protocols used on the Internet and on most local
65 Ethernets. It is highly recommended to say Y here (this will enlarge
66 your kernel by about 400 KB), since some programs (e.g. the X window
67 system) use TCP/IP even if your machine is not connected to any
68 other computer. You will get the so-called loopback device which
69 allows you to ping yourself (great fun, that!).
71 For an excellent introduction to Linux networking, please read the
72 Linux Networking HOWTO, available from
73 <http://www.tldp.org/docs.html#howto>.
75 If you say Y here and also to "/proc file system support" and
76 "Sysctl support" below, you can change various aspects of the
77 behavior of the TCP/IP code by writing to the (virtual) files in
78 /proc/sys/net/ipv4/*; the options are explained in the file
79 <file:Documentation/networking/ip-sysctl.txt>.
84 source "net/ipv4/Kconfig"
85 source "net/ipv6/Kconfig"
86 source "net/netlabel/Kconfig"
90 config NETWORK_SECMARK
91 bool "Security Marking"
93 This enables security marking of network packets, similar
94 to nfmark, but designated for security purposes.
95 If you are unsure how to answer this question, answer N.
98 bool "Network packet filtering framework (Netfilter)"
100 Netfilter is a framework for filtering and mangling network packets
101 that pass through your Linux box.
103 The most common use of packet filtering is to run your Linux box as
104 a firewall protecting a local network from the Internet. The type of
105 firewall provided by this kernel support is called a "packet
106 filter", which means that it can reject individual network packets
107 based on type, source, destination etc. The other kind of firewall,
108 a "proxy-based" one, is more secure but more intrusive and more
109 bothersome to set up; it inspects the network traffic much more
110 closely, modifies it and has knowledge about the higher level
111 protocols, which a packet filter lacks. Moreover, proxy-based
112 firewalls often require changes to the programs running on the local
113 clients. Proxy-based firewalls don't need support by the kernel, but
114 they are often combined with a packet filter, which only works if
117 You should also say Y here if you intend to use your Linux box as
118 the gateway to the Internet for a local network of machines without
119 globally valid IP addresses. This is called "masquerading": if one
120 of the computers on your local network wants to send something to
121 the outside, your box can "masquerade" as that computer, i.e. it
122 forwards the traffic to the intended outside destination, but
123 modifies the packets to make it look like they came from the
124 firewall box itself. It works both ways: if the outside host
125 replies, the Linux box will silently forward the traffic to the
126 correct local computer. This way, the computers on your local net
127 are completely invisible to the outside world, even though they can
128 reach the outside and can receive replies. It is even possible to
129 run globally visible servers from within a masqueraded local network
130 using a mechanism called portforwarding. Masquerading is also often
131 called NAT (Network Address Translation).
133 Another use of Netfilter is in transparent proxying: if a machine on
134 the local network tries to connect to an outside host, your Linux
135 box can transparently forward the traffic to a local server,
136 typically a caching proxy server.
138 Yet another use of Netfilter is building a bridging firewall. Using
139 a bridge with Network packet filtering enabled makes iptables "see"
140 the bridged traffic. For filtering on the lower network and Ethernet
141 protocols over the bridge, use ebtables (under bridge netfilter
144 Various modules exist for netfilter which replace the previous
145 masquerading (ipmasqadm), packet filtering (ipchains), transparent
146 proxying, and portforwarding mechanisms. Please see
147 <file:Documentation/Changes> under "iptables" for the location of
152 config NETFILTER_DEBUG
153 bool "Network packet filtering debugging"
156 You can say Y here if you want to get additional messages useful in
157 debugging the netfilter code.
159 config NETFILTER_ADVANCED
160 bool "Advanced netfilter configuration"
164 If you say Y here you can select between all the netfilter modules.
165 If you say N the more unusual ones will not be shown and the
166 basic ones needed by most people will default to 'M'.
170 config BRIDGE_NETFILTER
171 bool "Bridged IP/ARP packets filtering"
172 depends on BRIDGE && NETFILTER && INET
173 depends on NETFILTER_ADVANCED
176 Enabling this option will let arptables resp. iptables see bridged
177 ARP resp. IP traffic. If you want a bridging firewall, you probably
178 want this option enabled.
179 Enabling or disabling this option doesn't enable or disable
184 source "net/netfilter/Kconfig"
185 source "net/ipv4/netfilter/Kconfig"
186 source "net/ipv6/netfilter/Kconfig"
187 source "net/decnet/netfilter/Kconfig"
188 source "net/bridge/netfilter/Kconfig"
192 source "net/dccp/Kconfig"
193 source "net/sctp/Kconfig"
194 source "net/rds/Kconfig"
195 source "net/tipc/Kconfig"
196 source "net/atm/Kconfig"
197 source "net/l2tp/Kconfig"
198 source "net/802/Kconfig"
199 source "net/bridge/Kconfig"
200 source "net/dsa/Kconfig"
201 source "net/8021q/Kconfig"
202 source "net/decnet/Kconfig"
203 source "net/llc/Kconfig"
204 source "net/ipx/Kconfig"
205 source "drivers/net/appletalk/Kconfig"
206 source "net/x25/Kconfig"
207 source "net/lapb/Kconfig"
208 source "net/econet/Kconfig"
209 source "net/wanrouter/Kconfig"
210 source "net/phonet/Kconfig"
211 source "net/ieee802154/Kconfig"
212 source "net/sched/Kconfig"
213 source "net/dcb/Kconfig"
217 depends on SMP && SYSFS
220 menu "Network testing"
223 tristate "Packet Generator (USE WITH CAUTION)"
226 This module will inject preconfigured packets, at a configurable
227 rate, out of a given interface. It is used for network interface
228 stress testing and performance analysis. If you don't understand
229 what was just said, you don't need it: say N.
231 Documentation on how to use the packet generator can be found
232 at <file:Documentation/networking/pktgen.txt>.
234 To compile this code as a module, choose M here: the
235 module will be called pktgen.
238 tristate "TCP connection probing"
239 depends on INET && EXPERIMENTAL && PROC_FS && KPROBES
241 This module allows for capturing the changes to TCP connection
242 state in response to incoming packets. It is used for debugging
243 TCP congestion avoidance modules. If you don't understand
244 what was just said, you don't need it: say N.
246 Documentation on how to use TCP connection probing can be found
247 at http://linux-net.osdl.org/index.php/TcpProbe
249 To compile this code as a module, choose M here: the
250 module will be called tcp_probe.
252 config NET_DROP_MONITOR
253 boolean "Network packet drop alerting service"
254 depends on INET && EXPERIMENTAL && TRACEPOINTS
256 This feature provides an alerting service to userspace in the
257 event that packets are discarded in the network stack. Alerts
258 are broadcast via netlink socket to any listening user space
259 process. If you don't need network drop alerts, or if you are ok
260 just checking the various proc files and other utilities for
261 drop statistics, say N here.
267 source "net/ax25/Kconfig"
268 source "net/can/Kconfig"
269 source "net/irda/Kconfig"
270 source "net/bluetooth/Kconfig"
271 source "net/rxrpc/Kconfig"
283 source "net/wireless/Kconfig"
284 source "net/mac80211/Kconfig"
288 source "net/wimax/Kconfig"
290 source "net/rfkill/Kconfig"
291 source "net/9p/Kconfig"
292 source "net/caif/Kconfig"