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 NETWORK_SECMARK
90 bool "Security Marking"
92 This enables security marking of network packets, similar
93 to nfmark, but designated for security purposes.
94 If you are unsure how to answer this question, answer N.
96 config NET_PTP_CLASSIFY
99 config NETWORK_PHY_TIMESTAMPING
100 bool "Timestamping in PHY devices"
101 select NET_PTP_CLASSIFY
103 This allows timestamping of network packets by PHYs with
104 hardware timestamping capabilities. This option adds some
105 overhead in the transmit and receive paths.
107 If you are unsure how to answer this question, answer N.
110 bool "Network packet filtering framework (Netfilter)"
112 Netfilter is a framework for filtering and mangling network packets
113 that pass through your Linux box.
115 The most common use of packet filtering is to run your Linux box as
116 a firewall protecting a local network from the Internet. The type of
117 firewall provided by this kernel support is called a "packet
118 filter", which means that it can reject individual network packets
119 based on type, source, destination etc. The other kind of firewall,
120 a "proxy-based" one, is more secure but more intrusive and more
121 bothersome to set up; it inspects the network traffic much more
122 closely, modifies it and has knowledge about the higher level
123 protocols, which a packet filter lacks. Moreover, proxy-based
124 firewalls often require changes to the programs running on the local
125 clients. Proxy-based firewalls don't need support by the kernel, but
126 they are often combined with a packet filter, which only works if
129 You should also say Y here if you intend to use your Linux box as
130 the gateway to the Internet for a local network of machines without
131 globally valid IP addresses. This is called "masquerading": if one
132 of the computers on your local network wants to send something to
133 the outside, your box can "masquerade" as that computer, i.e. it
134 forwards the traffic to the intended outside destination, but
135 modifies the packets to make it look like they came from the
136 firewall box itself. It works both ways: if the outside host
137 replies, the Linux box will silently forward the traffic to the
138 correct local computer. This way, the computers on your local net
139 are completely invisible to the outside world, even though they can
140 reach the outside and can receive replies. It is even possible to
141 run globally visible servers from within a masqueraded local network
142 using a mechanism called portforwarding. Masquerading is also often
143 called NAT (Network Address Translation).
145 Another use of Netfilter is in transparent proxying: if a machine on
146 the local network tries to connect to an outside host, your Linux
147 box can transparently forward the traffic to a local server,
148 typically a caching proxy server.
150 Yet another use of Netfilter is building a bridging firewall. Using
151 a bridge with Network packet filtering enabled makes iptables "see"
152 the bridged traffic. For filtering on the lower network and Ethernet
153 protocols over the bridge, use ebtables (under bridge netfilter
156 Various modules exist for netfilter which replace the previous
157 masquerading (ipmasqadm), packet filtering (ipchains), transparent
158 proxying, and portforwarding mechanisms. Please see
159 <file:Documentation/Changes> under "iptables" for the location of
164 config NETFILTER_DEBUG
165 bool "Network packet filtering debugging"
168 You can say Y here if you want to get additional messages useful in
169 debugging the netfilter code.
171 config NETFILTER_ADVANCED
172 bool "Advanced netfilter configuration"
176 If you say Y here you can select between all the netfilter modules.
177 If you say N the more unusual ones will not be shown and the
178 basic ones needed by most people will default to 'M'.
182 config BRIDGE_NETFILTER
183 tristate "Bridged IP/ARP packets filtering"
185 depends on NETFILTER && INET
186 depends on NETFILTER_ADVANCED
189 Enabling this option will let arptables resp. iptables see bridged
190 ARP resp. IP traffic. If you want a bridging firewall, you probably
191 want this option enabled.
192 Enabling or disabling this option doesn't enable or disable
197 source "net/netfilter/Kconfig"
198 source "net/ipv4/netfilter/Kconfig"
199 source "net/ipv6/netfilter/Kconfig"
200 source "net/decnet/netfilter/Kconfig"
201 source "net/bridge/netfilter/Kconfig"
205 source "net/dccp/Kconfig"
206 source "net/sctp/Kconfig"
207 source "net/rds/Kconfig"
208 source "net/tipc/Kconfig"
209 source "net/atm/Kconfig"
210 source "net/l2tp/Kconfig"
211 source "net/802/Kconfig"
212 source "net/bridge/Kconfig"
213 source "net/dsa/Kconfig"
214 source "net/8021q/Kconfig"
215 source "net/decnet/Kconfig"
216 source "net/llc/Kconfig"
217 source "net/ipx/Kconfig"
218 source "drivers/net/appletalk/Kconfig"
219 source "net/x25/Kconfig"
220 source "net/lapb/Kconfig"
221 source "net/phonet/Kconfig"
222 source "net/6lowpan/Kconfig"
223 source "net/ieee802154/Kconfig"
224 source "net/mac802154/Kconfig"
225 source "net/sched/Kconfig"
226 source "net/dcb/Kconfig"
227 source "net/dns_resolver/Kconfig"
228 source "net/batman-adv/Kconfig"
229 source "net/openvswitch/Kconfig"
230 source "net/vmw_vsock/Kconfig"
231 source "net/netlink/Kconfig"
232 source "net/mpls/Kconfig"
233 source "net/hsr/Kconfig"
234 source "net/switchdev/Kconfig"
235 source "net/l3mdev/Kconfig"
236 source "net/qrtr/Kconfig"
240 depends on SMP && SYSFS
254 config CGROUP_NET_PRIO
255 bool "Network priority cgroup"
258 Cgroup subsystem for use in assigning processes to network priorities on
259 a per-interface basis.
261 config CGROUP_NET_CLASSID
262 bool "Network classid cgroup"
265 Cgroup subsystem for use as general purpose socket classid marker that is
266 being used in cls_cgroup and for netfilter matching.
268 config NET_RX_BUSY_POLL
279 bool "enable BPF Just In Time compiler"
280 depends on HAVE_BPF_JIT
283 Berkeley Packet Filter filtering capabilities are normally handled
284 by an interpreter. This option allows kernel to generate a native
285 code when filter is loaded in memory. This should speedup
286 packet sniffing (libpcap/tcpdump). Note : Admin should enable
287 this feature changing /proc/sys/net/core/bpf_jit_enable
289 config NET_FLOW_LIMIT
294 The network stack has to drop packets when a receive processing CPU's
295 backlog reaches netdev_max_backlog. If a few out of many active flows
296 generate the vast majority of load, drop their traffic earlier to
297 maintain capacity for the other flows. This feature provides servers
298 with many clients some protection against DoS by a single (spoofed)
299 flow that greatly exceeds average workload.
301 menu "Network testing"
304 tristate "Packet Generator (USE WITH CAUTION)"
305 depends on INET && PROC_FS
307 This module will inject preconfigured packets, at a configurable
308 rate, out of a given interface. It is used for network interface
309 stress testing and performance analysis. If you don't understand
310 what was just said, you don't need it: say N.
312 Documentation on how to use the packet generator can be found
313 at <file:Documentation/networking/pktgen.txt>.
315 To compile this code as a module, choose M here: the
316 module will be called pktgen.
319 tristate "TCP connection probing"
320 depends on INET && PROC_FS && KPROBES
322 This module allows for capturing the changes to TCP connection
323 state in response to incoming packets. It is used for debugging
324 TCP congestion avoidance modules. If you don't understand
325 what was just said, you don't need it: say N.
327 Documentation on how to use TCP connection probing can be found
330 http://www.linuxfoundation.org/collaborate/workgroups/networking/tcpprobe
332 To compile this code as a module, choose M here: the
333 module will be called tcp_probe.
335 config NET_DROP_MONITOR
336 tristate "Network packet drop alerting service"
337 depends on INET && TRACEPOINTS
339 This feature provides an alerting service to userspace in the
340 event that packets are discarded in the network stack. Alerts
341 are broadcast via netlink socket to any listening user space
342 process. If you don't need network drop alerts, or if you are ok
343 just checking the various proc files and other utilities for
344 drop statistics, say N here.
350 source "net/ax25/Kconfig"
351 source "net/can/Kconfig"
352 source "net/irda/Kconfig"
353 source "net/bluetooth/Kconfig"
354 source "net/rxrpc/Kconfig"
355 source "net/kcm/Kconfig"
367 source "net/wireless/Kconfig"
368 source "net/mac80211/Kconfig"
372 source "net/wimax/Kconfig"
374 source "net/rfkill/Kconfig"
375 source "net/9p/Kconfig"
376 source "net/caif/Kconfig"
377 source "net/ceph/Kconfig"
378 source "net/nfc/Kconfig"
381 bool "Network light weight tunnels"
383 This feature provides an infrastructure to support light weight
384 tunnels like mpls. There is no netdevice associated with a light
385 weight tunnel endpoint. Tunnel encapsulation parameters are stored
386 with light weight tunnel state associated with fib routes.
390 # Used by archs to tell that they support BPF_JIT