2 # Network configuration
6 bool "Networking support"
8 select GENERIC_NET_UTILS
11 Unless you really know what you are doing, you should say Y here.
12 The reason is that some programs need kernel networking support even
13 when running on a stand-alone machine that isn't connected to any
16 If you are upgrading from an older kernel, you
17 should consider updating your networking tools too because changes
18 in the kernel and the tools often go hand in hand. The tools are
19 contained in the package net-tools, the location and version number
20 of which are given in <file:Documentation/Changes>.
22 For a general introduction to Linux networking, it is highly
23 recommended to read the NET-HOWTO, available from
24 <http://www.tldp.org/docs.html#howto>.
28 config WANT_COMPAT_NETLINK_MESSAGES
31 This option can be selected by other options that need compat
34 config COMPAT_NETLINK_MESSAGES
37 depends on WEXT_CORE || WANT_COMPAT_NETLINK_MESSAGES
39 This option makes it possible to send different netlink messages
40 to tasks depending on whether the task is a compat task or not. To
41 achieve this, you need to set skb_shinfo(skb)->frag_list to the
42 compat skb before sending the skb, the netlink code will sort out
43 which message to actually pass to the task.
45 Newly written code should NEVER need this option but do
46 compat-independent messages instead!
51 menu "Networking options"
53 source "net/packet/Kconfig"
54 source "net/unix/Kconfig"
55 source "net/xfrm/Kconfig"
56 source "net/iucv/Kconfig"
59 bool "TCP/IP networking"
63 These are the protocols used on the Internet and on most local
64 Ethernets. It is highly recommended to say Y here (this will enlarge
65 your kernel by about 400 KB), since some programs (e.g. the X window
66 system) use TCP/IP even if your machine is not connected to any
67 other computer. You will get the so-called loopback device which
68 allows you to ping yourself (great fun, that!).
70 For an excellent introduction to Linux networking, please read the
71 Linux Networking HOWTO, available from
72 <http://www.tldp.org/docs.html#howto>.
74 If you say Y here and also to "/proc file system support" and
75 "Sysctl support" below, you can change various aspects of the
76 behavior of the TCP/IP code by writing to the (virtual) files in
77 /proc/sys/net/ipv4/*; the options are explained in the file
78 <file:Documentation/networking/ip-sysctl.txt>.
83 source "net/ipv4/Kconfig"
84 source "net/ipv6/Kconfig"
85 source "net/netlabel/Kconfig"
89 config ANDROID_PARANOID_NETWORK
90 bool "Only allow certain groups to create sockets"
95 config NETWORK_SECMARK
96 bool "Security Marking"
98 This enables security marking of network packets, similar
99 to nfmark, but designated for security purposes.
100 If you are unsure how to answer this question, answer N.
102 config NET_PTP_CLASSIFY
105 config NETWORK_PHY_TIMESTAMPING
106 bool "Timestamping in PHY devices"
107 select NET_PTP_CLASSIFY
109 This allows timestamping of network packets by PHYs with
110 hardware timestamping capabilities. This option adds some
111 overhead in the transmit and receive paths.
113 If you are unsure how to answer this question, answer N.
116 bool "Network packet filtering framework (Netfilter)"
118 Netfilter is a framework for filtering and mangling network packets
119 that pass through your Linux box.
121 The most common use of packet filtering is to run your Linux box as
122 a firewall protecting a local network from the Internet. The type of
123 firewall provided by this kernel support is called a "packet
124 filter", which means that it can reject individual network packets
125 based on type, source, destination etc. The other kind of firewall,
126 a "proxy-based" one, is more secure but more intrusive and more
127 bothersome to set up; it inspects the network traffic much more
128 closely, modifies it and has knowledge about the higher level
129 protocols, which a packet filter lacks. Moreover, proxy-based
130 firewalls often require changes to the programs running on the local
131 clients. Proxy-based firewalls don't need support by the kernel, but
132 they are often combined with a packet filter, which only works if
135 You should also say Y here if you intend to use your Linux box as
136 the gateway to the Internet for a local network of machines without
137 globally valid IP addresses. This is called "masquerading": if one
138 of the computers on your local network wants to send something to
139 the outside, your box can "masquerade" as that computer, i.e. it
140 forwards the traffic to the intended outside destination, but
141 modifies the packets to make it look like they came from the
142 firewall box itself. It works both ways: if the outside host
143 replies, the Linux box will silently forward the traffic to the
144 correct local computer. This way, the computers on your local net
145 are completely invisible to the outside world, even though they can
146 reach the outside and can receive replies. It is even possible to
147 run globally visible servers from within a masqueraded local network
148 using a mechanism called portforwarding. Masquerading is also often
149 called NAT (Network Address Translation).
151 Another use of Netfilter is in transparent proxying: if a machine on
152 the local network tries to connect to an outside host, your Linux
153 box can transparently forward the traffic to a local server,
154 typically a caching proxy server.
156 Yet another use of Netfilter is building a bridging firewall. Using
157 a bridge with Network packet filtering enabled makes iptables "see"
158 the bridged traffic. For filtering on the lower network and Ethernet
159 protocols over the bridge, use ebtables (under bridge netfilter
162 Various modules exist for netfilter which replace the previous
163 masquerading (ipmasqadm), packet filtering (ipchains), transparent
164 proxying, and portforwarding mechanisms. Please see
165 <file:Documentation/Changes> under "iptables" for the location of
170 config NETFILTER_DEBUG
171 bool "Network packet filtering debugging"
174 You can say Y here if you want to get additional messages useful in
175 debugging the netfilter code.
177 config NETFILTER_ADVANCED
178 bool "Advanced netfilter configuration"
182 If you say Y here you can select between all the netfilter modules.
183 If you say N the more unusual ones will not be shown and the
184 basic ones needed by most people will default to 'M'.
188 config BRIDGE_NETFILTER
189 tristate "Bridged IP/ARP packets filtering"
191 depends on NETFILTER && INET
192 depends on NETFILTER_ADVANCED
195 Enabling this option will let arptables resp. iptables see bridged
196 ARP resp. IP traffic. If you want a bridging firewall, you probably
197 want this option enabled.
198 Enabling or disabling this option doesn't enable or disable
203 source "net/netfilter/Kconfig"
204 source "net/ipv4/netfilter/Kconfig"
205 source "net/ipv6/netfilter/Kconfig"
206 source "net/decnet/netfilter/Kconfig"
207 source "net/bridge/netfilter/Kconfig"
211 source "net/dccp/Kconfig"
212 source "net/sctp/Kconfig"
213 source "net/rds/Kconfig"
214 source "net/tipc/Kconfig"
215 source "net/atm/Kconfig"
216 source "net/l2tp/Kconfig"
217 source "net/802/Kconfig"
218 source "net/bridge/Kconfig"
219 source "net/dsa/Kconfig"
220 source "net/8021q/Kconfig"
221 source "net/decnet/Kconfig"
222 source "net/llc/Kconfig"
223 source "net/ipx/Kconfig"
224 source "drivers/net/appletalk/Kconfig"
225 source "net/x25/Kconfig"
226 source "net/lapb/Kconfig"
227 source "net/phonet/Kconfig"
228 source "net/6lowpan/Kconfig"
229 source "net/ieee802154/Kconfig"
230 source "net/mac802154/Kconfig"
231 source "net/sched/Kconfig"
232 source "net/dcb/Kconfig"
233 source "net/dns_resolver/Kconfig"
234 source "net/batman-adv/Kconfig"
235 source "net/openvswitch/Kconfig"
236 source "net/vmw_vsock/Kconfig"
237 source "net/netlink/Kconfig"
238 source "net/mpls/Kconfig"
239 source "net/hsr/Kconfig"
240 source "net/switchdev/Kconfig"
241 source "net/l3mdev/Kconfig"
245 depends on SMP && SYSFS
259 config CGROUP_NET_PRIO
260 bool "Network priority cgroup"
263 Cgroup subsystem for use in assigning processes to network priorities on
264 a per-interface basis.
266 config CGROUP_NET_CLASSID
267 bool "Network classid cgroup"
270 Cgroup subsystem for use as general purpose socket classid marker that is
271 being used in cls_cgroup and for netfilter matching.
273 config NET_RX_BUSY_POLL
284 bool "enable BPF Just In Time compiler"
285 depends on HAVE_BPF_JIT
288 Berkeley Packet Filter filtering capabilities are normally handled
289 by an interpreter. This option allows kernel to generate a native
290 code when filter is loaded in memory. This should speedup
291 packet sniffing (libpcap/tcpdump). Note : Admin should enable
292 this feature changing /proc/sys/net/core/bpf_jit_enable
294 config NET_FLOW_LIMIT
299 The network stack has to drop packets when a receive processing CPU's
300 backlog reaches netdev_max_backlog. If a few out of many active flows
301 generate the vast majority of load, drop their traffic earlier to
302 maintain capacity for the other flows. This feature provides servers
303 with many clients some protection against DoS by a single (spoofed)
304 flow that greatly exceeds average workload.
306 menu "Network testing"
309 tristate "Packet Generator (USE WITH CAUTION)"
310 depends on INET && PROC_FS
312 This module will inject preconfigured packets, at a configurable
313 rate, out of a given interface. It is used for network interface
314 stress testing and performance analysis. If you don't understand
315 what was just said, you don't need it: say N.
317 Documentation on how to use the packet generator can be found
318 at <file:Documentation/networking/pktgen.txt>.
320 To compile this code as a module, choose M here: the
321 module will be called pktgen.
324 tristate "TCP connection probing"
325 depends on INET && PROC_FS && KPROBES
327 This module allows for capturing the changes to TCP connection
328 state in response to incoming packets. It is used for debugging
329 TCP congestion avoidance modules. If you don't understand
330 what was just said, you don't need it: say N.
332 Documentation on how to use TCP connection probing can be found
335 http://www.linuxfoundation.org/collaborate/workgroups/networking/tcpprobe
337 To compile this code as a module, choose M here: the
338 module will be called tcp_probe.
340 config NET_DROP_MONITOR
341 tristate "Network packet drop alerting service"
342 depends on INET && TRACEPOINTS
344 This feature provides an alerting service to userspace in the
345 event that packets are discarded in the network stack. Alerts
346 are broadcast via netlink socket to any listening user space
347 process. If you don't need network drop alerts, or if you are ok
348 just checking the various proc files and other utilities for
349 drop statistics, say N here.
355 source "net/ax25/Kconfig"
356 source "net/can/Kconfig"
357 source "net/irda/Kconfig"
358 source "net/bluetooth/Kconfig"
359 source "net/rxrpc/Kconfig"
371 source "net/wireless/Kconfig"
372 source "net/mac80211/Kconfig"
376 source "net/wimax/Kconfig"
378 source "net/rfkill/Kconfig"
379 source "net/9p/Kconfig"
380 source "net/caif/Kconfig"
381 source "net/ceph/Kconfig"
382 source "net/nfc/Kconfig"
385 bool "Network light weight tunnels"
387 This feature provides an infrastructure to support light weight
388 tunnels like mpls. There is no netdevice associated with a light
389 weight tunnel endpoint. Tunnel encapsulation parameters are stored
390 with light weight tunnel state associated with fib routes.
394 # Used by archs to tell that they support BPF_JIT