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 config DISABLE_NET_SKB_FRAG_CACHE
52 bool "Disable skb fragment cache"
54 Enabling this option ensures that when allocating skbs the network
55 skb fragment cache is not used.
56 Disabling use of the fragment cache can be useful on some low end
57 targets because it reduces memory pressure.
59 If you are unsure how to answer this question, answer N.
61 menu "Networking options"
63 source "net/packet/Kconfig"
64 source "net/unix/Kconfig"
65 source "net/xfrm/Kconfig"
66 source "net/iucv/Kconfig"
69 bool "TCP/IP networking"
73 These are the protocols used on the Internet and on most local
74 Ethernets. It is highly recommended to say Y here (this will enlarge
75 your kernel by about 400 KB), since some programs (e.g. the X window
76 system) use TCP/IP even if your machine is not connected to any
77 other computer. You will get the so-called loopback device which
78 allows you to ping yourself (great fun, that!).
80 For an excellent introduction to Linux networking, please read the
81 Linux Networking HOWTO, available from
82 <http://www.tldp.org/docs.html#howto>.
84 If you say Y here and also to "/proc file system support" and
85 "Sysctl support" below, you can change various aspects of the
86 behavior of the TCP/IP code by writing to the (virtual) files in
87 /proc/sys/net/ipv4/*; the options are explained in the file
88 <file:Documentation/networking/ip-sysctl.txt>.
93 source "net/ipv4/Kconfig"
94 source "net/ipv6/Kconfig"
95 source "net/netlabel/Kconfig"
99 config ANDROID_PARANOID_NETWORK
100 bool "Only allow certain groups to create sockets"
105 config NETWORK_SECMARK
106 bool "Security Marking"
108 This enables security marking of network packets, similar
109 to nfmark, but designated for security purposes.
110 If you are unsure how to answer this question, answer N.
112 config NET_PTP_CLASSIFY
115 config NETWORK_PHY_TIMESTAMPING
116 bool "Timestamping in PHY devices"
117 select NET_PTP_CLASSIFY
119 This allows timestamping of network packets by PHYs with
120 hardware timestamping capabilities. This option adds some
121 overhead in the transmit and receive paths.
123 If you are unsure how to answer this question, answer N.
126 bool "Network packet filtering framework (Netfilter)"
128 Netfilter is a framework for filtering and mangling network packets
129 that pass through your Linux box.
131 The most common use of packet filtering is to run your Linux box as
132 a firewall protecting a local network from the Internet. The type of
133 firewall provided by this kernel support is called a "packet
134 filter", which means that it can reject individual network packets
135 based on type, source, destination etc. The other kind of firewall,
136 a "proxy-based" one, is more secure but more intrusive and more
137 bothersome to set up; it inspects the network traffic much more
138 closely, modifies it and has knowledge about the higher level
139 protocols, which a packet filter lacks. Moreover, proxy-based
140 firewalls often require changes to the programs running on the local
141 clients. Proxy-based firewalls don't need support by the kernel, but
142 they are often combined with a packet filter, which only works if
145 You should also say Y here if you intend to use your Linux box as
146 the gateway to the Internet for a local network of machines without
147 globally valid IP addresses. This is called "masquerading": if one
148 of the computers on your local network wants to send something to
149 the outside, your box can "masquerade" as that computer, i.e. it
150 forwards the traffic to the intended outside destination, but
151 modifies the packets to make it look like they came from the
152 firewall box itself. It works both ways: if the outside host
153 replies, the Linux box will silently forward the traffic to the
154 correct local computer. This way, the computers on your local net
155 are completely invisible to the outside world, even though they can
156 reach the outside and can receive replies. It is even possible to
157 run globally visible servers from within a masqueraded local network
158 using a mechanism called portforwarding. Masquerading is also often
159 called NAT (Network Address Translation).
161 Another use of Netfilter is in transparent proxying: if a machine on
162 the local network tries to connect to an outside host, your Linux
163 box can transparently forward the traffic to a local server,
164 typically a caching proxy server.
166 Yet another use of Netfilter is building a bridging firewall. Using
167 a bridge with Network packet filtering enabled makes iptables "see"
168 the bridged traffic. For filtering on the lower network and Ethernet
169 protocols over the bridge, use ebtables (under bridge netfilter
172 Various modules exist for netfilter which replace the previous
173 masquerading (ipmasqadm), packet filtering (ipchains), transparent
174 proxying, and portforwarding mechanisms. Please see
175 <file:Documentation/Changes> under "iptables" for the location of
180 config NETFILTER_DEBUG
181 bool "Network packet filtering debugging"
184 You can say Y here if you want to get additional messages useful in
185 debugging the netfilter code.
187 config NETFILTER_ADVANCED
188 bool "Advanced netfilter configuration"
192 If you say Y here you can select between all the netfilter modules.
193 If you say N the more unusual ones will not be shown and the
194 basic ones needed by most people will default to 'M'.
198 config BRIDGE_NETFILTER
199 tristate "Bridged IP/ARP packets filtering"
201 depends on NETFILTER && INET
202 depends on NETFILTER_ADVANCED
205 Enabling this option will let arptables resp. iptables see bridged
206 ARP resp. IP traffic. If you want a bridging firewall, you probably
207 want this option enabled.
208 Enabling or disabling this option doesn't enable or disable
213 source "net/netfilter/Kconfig"
214 source "net/ipv4/netfilter/Kconfig"
215 source "net/ipv6/netfilter/Kconfig"
216 source "net/decnet/netfilter/Kconfig"
217 source "net/bridge/netfilter/Kconfig"
221 source "net/dccp/Kconfig"
222 source "net/sctp/Kconfig"
223 source "net/rds/Kconfig"
224 source "net/tipc/Kconfig"
225 source "net/atm/Kconfig"
226 source "net/l2tp/Kconfig"
227 source "net/802/Kconfig"
228 source "net/bridge/Kconfig"
229 source "net/dsa/Kconfig"
230 source "net/8021q/Kconfig"
231 source "net/decnet/Kconfig"
232 source "net/llc/Kconfig"
233 source "net/ipx/Kconfig"
234 source "drivers/net/appletalk/Kconfig"
235 source "net/x25/Kconfig"
236 source "net/lapb/Kconfig"
237 source "net/phonet/Kconfig"
238 source "net/6lowpan/Kconfig"
239 source "net/ieee802154/Kconfig"
240 source "net/mac802154/Kconfig"
241 source "net/sched/Kconfig"
242 source "net/dcb/Kconfig"
243 source "net/dns_resolver/Kconfig"
244 source "net/batman-adv/Kconfig"
245 source "net/openvswitch/Kconfig"
246 source "net/vmw_vsock/Kconfig"
247 source "net/netlink/Kconfig"
248 source "net/mpls/Kconfig"
249 source "net/hsr/Kconfig"
250 source "net/switchdev/Kconfig"
251 source "net/l3mdev/Kconfig"
252 source "net/rmnet_data/Kconfig"
256 depends on SMP && SYSFS
270 config CGROUP_NET_PRIO
271 bool "Network priority cgroup"
274 Cgroup subsystem for use in assigning processes to network priorities on
275 a per-interface basis.
277 config CGROUP_NET_CLASSID
278 bool "Network classid cgroup"
281 Cgroup subsystem for use as general purpose socket classid marker that is
282 being used in cls_cgroup and for netfilter matching.
284 config NET_RX_BUSY_POLL
295 bool "enable BPF Just In Time compiler"
296 depends on HAVE_BPF_JIT
299 Berkeley Packet Filter filtering capabilities are normally handled
300 by an interpreter. This option allows kernel to generate a native
301 code when filter is loaded in memory. This should speedup
302 packet sniffing (libpcap/tcpdump). Note : Admin should enable
303 this feature changing /proc/sys/net/core/bpf_jit_enable
305 config NET_FLOW_LIMIT
310 The network stack has to drop packets when a receive processing CPU's
311 backlog reaches netdev_max_backlog. If a few out of many active flows
312 generate the vast majority of load, drop their traffic earlier to
313 maintain capacity for the other flows. This feature provides servers
314 with many clients some protection against DoS by a single (spoofed)
315 flow that greatly exceeds average workload.
317 config SOCKEV_NLMCAST
318 bool "Enable SOCKEV Netlink Multicast"
321 Default client for SOCKEV notifier events. Sends multicast netlink
322 messages whenever the socket event notifier is invoked. Enable if
323 user space entities need to be notified of socket events without
326 menu "Network testing"
329 tristate "Packet Generator (USE WITH CAUTION)"
330 depends on INET && PROC_FS
332 This module will inject preconfigured packets, at a configurable
333 rate, out of a given interface. It is used for network interface
334 stress testing and performance analysis. If you don't understand
335 what was just said, you don't need it: say N.
337 Documentation on how to use the packet generator can be found
338 at <file:Documentation/networking/pktgen.txt>.
340 To compile this code as a module, choose M here: the
341 module will be called pktgen.
344 tristate "TCP connection probing"
345 depends on INET && PROC_FS && KPROBES
347 This module allows for capturing the changes to TCP connection
348 state in response to incoming packets. It is used for debugging
349 TCP congestion avoidance modules. If you don't understand
350 what was just said, you don't need it: say N.
352 Documentation on how to use TCP connection probing can be found
355 http://www.linuxfoundation.org/collaborate/workgroups/networking/tcpprobe
357 To compile this code as a module, choose M here: the
358 module will be called tcp_probe.
360 config NET_DROP_MONITOR
361 tristate "Network packet drop alerting service"
362 depends on INET && TRACEPOINTS
364 This feature provides an alerting service to userspace in the
365 event that packets are discarded in the network stack. Alerts
366 are broadcast via netlink socket to any listening user space
367 process. If you don't need network drop alerts, or if you are ok
368 just checking the various proc files and other utilities for
369 drop statistics, say N here.
375 source "net/ax25/Kconfig"
376 source "net/can/Kconfig"
377 source "net/irda/Kconfig"
378 source "net/bluetooth/Kconfig"
379 source "net/rxrpc/Kconfig"
391 source "net/wireless/Kconfig"
392 source "net/mac80211/Kconfig"
396 source "net/wimax/Kconfig"
398 source "net/rfkill/Kconfig"
399 source "net/9p/Kconfig"
400 source "net/caif/Kconfig"
401 source "net/ceph/Kconfig"
402 source "net/nfc/Kconfig"
405 bool "Network light weight tunnels"
407 This feature provides an infrastructure to support light weight
408 tunnels like mpls. There is no netdevice associated with a light
409 weight tunnel endpoint. Tunnel encapsulation parameters are stored
410 with light weight tunnel state associated with fib routes.
412 source "net/ipc_router/Kconfig"
420 # Used by archs to tell that they support BPF_JIT