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"
48 source "net/packet/Kconfig"
49 source "net/unix/Kconfig"
50 source "net/xfrm/Kconfig"
51 source "net/iucv/Kconfig"
54 bool "TCP/IP networking"
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!).
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>.
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>.
76 source "net/ipv4/Kconfig"
77 source "net/ipv6/Kconfig"
78 source "net/netlabel/Kconfig"
82 config ANDROID_PARANOID_NETWORK
83 bool "Only allow certain groups to create sockets"
88 config NETWORK_SECMARK
89 bool "Security Marking"
91 This enables security marking of network packets, similar
92 to nfmark, but designated for security purposes.
93 If you are unsure how to answer this question, answer N.
96 bool "Network packet filtering framework (Netfilter)"
98 Netfilter is a framework for filtering and mangling network packets
99 that pass through your Linux box.
101 The most common use of packet filtering is to run your Linux box as
102 a firewall protecting a local network from the Internet. The type of
103 firewall provided by this kernel support is called a "packet
104 filter", which means that it can reject individual network packets
105 based on type, source, destination etc. The other kind of firewall,
106 a "proxy-based" one, is more secure but more intrusive and more
107 bothersome to set up; it inspects the network traffic much more
108 closely, modifies it and has knowledge about the higher level
109 protocols, which a packet filter lacks. Moreover, proxy-based
110 firewalls often require changes to the programs running on the local
111 clients. Proxy-based firewalls don't need support by the kernel, but
112 they are often combined with a packet filter, which only works if
115 You should also say Y here if you intend to use your Linux box as
116 the gateway to the Internet for a local network of machines without
117 globally valid IP addresses. This is called "masquerading": if one
118 of the computers on your local network wants to send something to
119 the outside, your box can "masquerade" as that computer, i.e. it
120 forwards the traffic to the intended outside destination, but
121 modifies the packets to make it look like they came from the
122 firewall box itself. It works both ways: if the outside host
123 replies, the Linux box will silently forward the traffic to the
124 correct local computer. This way, the computers on your local net
125 are completely invisible to the outside world, even though they can
126 reach the outside and can receive replies. It is even possible to
127 run globally visible servers from within a masqueraded local network
128 using a mechanism called portforwarding. Masquerading is also often
129 called NAT (Network Address Translation).
131 Another use of Netfilter is in transparent proxying: if a machine on
132 the local network tries to connect to an outside host, your Linux
133 box can transparently forward the traffic to a local server,
134 typically a caching proxy server.
136 Yet another use of Netfilter is building a bridging firewall. Using
137 a bridge with Network packet filtering enabled makes iptables "see"
138 the bridged traffic. For filtering on the lower network and Ethernet
139 protocols over the bridge, use ebtables (under bridge netfilter
142 Various modules exist for netfilter which replace the previous
143 masquerading (ipmasqadm), packet filtering (ipchains), transparent
144 proxying, and portforwarding mechanisms. Please see
145 <file:Documentation/Changes> under "iptables" for the location of
150 config NETFILTER_DEBUG
151 bool "Network packet filtering debugging"
154 You can say Y here if you want to get additional messages useful in
155 debugging the netfilter code.
157 config NETFILTER_ADVANCED
158 bool "Advanced netfilter configuration"
162 If you say Y here you can select between all the netfilter modules.
163 If you say N the more unusual ones will not be shown and the
164 basic ones needed by most people will default to 'M'.
168 config BRIDGE_NETFILTER
169 bool "Bridged IP/ARP packets filtering"
170 depends on BRIDGE && NETFILTER && INET
171 depends on NETFILTER_ADVANCED
174 Enabling this option will let arptables resp. iptables see bridged
175 ARP resp. IP traffic. If you want a bridging firewall, you probably
176 want this option enabled.
177 Enabling or disabling this option doesn't enable or disable
182 source "net/netfilter/Kconfig"
183 source "net/ipv4/netfilter/Kconfig"
184 source "net/ipv6/netfilter/Kconfig"
185 source "net/decnet/netfilter/Kconfig"
186 source "net/bridge/netfilter/Kconfig"
190 source "net/dccp/Kconfig"
191 source "net/sctp/Kconfig"
192 source "net/rds/Kconfig"
193 source "net/tipc/Kconfig"
194 source "net/atm/Kconfig"
195 source "net/802/Kconfig"
196 source "net/bridge/Kconfig"
197 source "net/dsa/Kconfig"
198 source "net/8021q/Kconfig"
199 source "net/decnet/Kconfig"
200 source "net/llc/Kconfig"
201 source "net/ipx/Kconfig"
202 source "drivers/net/appletalk/Kconfig"
203 source "net/x25/Kconfig"
204 source "net/lapb/Kconfig"
205 source "net/econet/Kconfig"
206 source "net/wanrouter/Kconfig"
207 source "net/phonet/Kconfig"
208 source "net/ieee802154/Kconfig"
209 source "net/sched/Kconfig"
210 source "net/dcb/Kconfig"
212 menu "Network testing"
215 tristate "Packet Generator (USE WITH CAUTION)"
218 This module will inject preconfigured packets, at a configurable
219 rate, out of a given interface. It is used for network interface
220 stress testing and performance analysis. If you don't understand
221 what was just said, you don't need it: say N.
223 Documentation on how to use the packet generator can be found
224 at <file:Documentation/networking/pktgen.txt>.
226 To compile this code as a module, choose M here: the
227 module will be called pktgen.
230 tristate "TCP connection probing"
231 depends on INET && EXPERIMENTAL && PROC_FS && KPROBES
233 This module allows for capturing the changes to TCP connection
234 state in response to incoming packets. It is used for debugging
235 TCP congestion avoidance modules. If you don't understand
236 what was just said, you don't need it: say N.
238 Documentation on how to use TCP connection probing can be found
239 at http://linux-net.osdl.org/index.php/TcpProbe
241 To compile this code as a module, choose M here: the
242 module will be called tcp_probe.
244 config NET_DROP_MONITOR
245 boolean "Network packet drop alerting service"
246 depends on INET && EXPERIMENTAL && TRACEPOINTS
248 This feature provides an alerting service to userspace in the
249 event that packets are discarded in the network stack. Alerts
250 are broadcast via netlink socket to any listening user space
251 process. If you don't need network drop alerts, or if you are ok
252 just checking the various proc files and other utilities for
253 drop statistics, say N here.
259 source "net/ax25/Kconfig"
260 source "net/can/Kconfig"
261 source "net/irda/Kconfig"
262 source "net/bluetooth/Kconfig"
263 source "net/rxrpc/Kconfig"
275 source "net/wireless/Kconfig"
276 source "net/mac80211/Kconfig"
280 source "net/wimax/Kconfig"
282 source "net/rfkill/Kconfig"
283 source "net/9p/Kconfig"