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!
54 menu "Networking options"
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"
66 These are the protocols used on the Internet and on most local
67 Ethernets. It is highly recommended to say Y here (this will enlarge
68 your kernel by about 400 KB), since some programs (e.g. the X window
69 system) use TCP/IP even if your machine is not connected to any
70 other computer. You will get the so-called loopback device which
71 allows you to ping yourself (great fun, that!).
73 For an excellent introduction to Linux networking, please read the
74 Linux Networking HOWTO, available from
75 <http://www.tldp.org/docs.html#howto>.
77 If you say Y here and also to "/proc file system support" and
78 "Sysctl support" below, you can change various aspects of the
79 behavior of the TCP/IP code by writing to the (virtual) files in
80 /proc/sys/net/ipv4/*; the options are explained in the file
81 <file:Documentation/networking/ip-sysctl.txt>.
86 source "net/ipv4/Kconfig"
87 source "net/ipv6/Kconfig"
88 source "net/netlabel/Kconfig"
92 config NETWORK_SECMARK
93 bool "Security Marking"
95 This enables security marking of network packets, similar
96 to nfmark, but designated for security purposes.
97 If you are unsure how to answer this question, answer N.
99 config NET_PTP_CLASSIFY
102 config NETWORK_PHY_TIMESTAMPING
103 bool "Timestamping in PHY devices"
104 select NET_PTP_CLASSIFY
106 This allows timestamping of network packets by PHYs with
107 hardware timestamping capabilities. This option adds some
108 overhead in the transmit and receive paths.
110 If you are unsure how to answer this question, answer N.
113 bool "Network packet filtering framework (Netfilter)"
115 Netfilter is a framework for filtering and mangling network packets
116 that pass through your Linux box.
118 The most common use of packet filtering is to run your Linux box as
119 a firewall protecting a local network from the Internet. The type of
120 firewall provided by this kernel support is called a "packet
121 filter", which means that it can reject individual network packets
122 based on type, source, destination etc. The other kind of firewall,
123 a "proxy-based" one, is more secure but more intrusive and more
124 bothersome to set up; it inspects the network traffic much more
125 closely, modifies it and has knowledge about the higher level
126 protocols, which a packet filter lacks. Moreover, proxy-based
127 firewalls often require changes to the programs running on the local
128 clients. Proxy-based firewalls don't need support by the kernel, but
129 they are often combined with a packet filter, which only works if
132 You should also say Y here if you intend to use your Linux box as
133 the gateway to the Internet for a local network of machines without
134 globally valid IP addresses. This is called "masquerading": if one
135 of the computers on your local network wants to send something to
136 the outside, your box can "masquerade" as that computer, i.e. it
137 forwards the traffic to the intended outside destination, but
138 modifies the packets to make it look like they came from the
139 firewall box itself. It works both ways: if the outside host
140 replies, the Linux box will silently forward the traffic to the
141 correct local computer. This way, the computers on your local net
142 are completely invisible to the outside world, even though they can
143 reach the outside and can receive replies. It is even possible to
144 run globally visible servers from within a masqueraded local network
145 using a mechanism called portforwarding. Masquerading is also often
146 called NAT (Network Address Translation).
148 Another use of Netfilter is in transparent proxying: if a machine on
149 the local network tries to connect to an outside host, your Linux
150 box can transparently forward the traffic to a local server,
151 typically a caching proxy server.
153 Yet another use of Netfilter is building a bridging firewall. Using
154 a bridge with Network packet filtering enabled makes iptables "see"
155 the bridged traffic. For filtering on the lower network and Ethernet
156 protocols over the bridge, use ebtables (under bridge netfilter
159 Various modules exist for netfilter which replace the previous
160 masquerading (ipmasqadm), packet filtering (ipchains), transparent
161 proxying, and portforwarding mechanisms. Please see
162 <file:Documentation/Changes> under "iptables" for the location of
167 config NETFILTER_DEBUG
168 bool "Network packet filtering debugging"
171 You can say Y here if you want to get additional messages useful in
172 debugging the netfilter code.
174 config NETFILTER_ADVANCED
175 bool "Advanced netfilter configuration"
179 If you say Y here you can select between all the netfilter modules.
180 If you say N the more unusual ones will not be shown and the
181 basic ones needed by most people will default to 'M'.
185 config BRIDGE_NETFILTER
186 tristate "Bridged IP/ARP packets filtering"
188 depends on NETFILTER && INET
189 depends on NETFILTER_ADVANCED
192 Enabling this option will let arptables resp. iptables see bridged
193 ARP resp. IP traffic. If you want a bridging firewall, you probably
194 want this option enabled.
195 Enabling or disabling this option doesn't enable or disable
200 source "net/netfilter/Kconfig"
201 source "net/ipv4/netfilter/Kconfig"
202 source "net/ipv6/netfilter/Kconfig"
203 source "net/decnet/netfilter/Kconfig"
204 source "net/bridge/netfilter/Kconfig"
208 source "net/dccp/Kconfig"
209 source "net/sctp/Kconfig"
210 source "net/rds/Kconfig"
211 source "net/tipc/Kconfig"
212 source "net/atm/Kconfig"
213 source "net/l2tp/Kconfig"
214 source "net/802/Kconfig"
215 source "net/bridge/Kconfig"
216 source "net/dsa/Kconfig"
217 source "net/8021q/Kconfig"
218 source "net/decnet/Kconfig"
219 source "net/llc/Kconfig"
220 source "net/ipx/Kconfig"
221 source "drivers/net/appletalk/Kconfig"
222 source "net/x25/Kconfig"
223 source "net/lapb/Kconfig"
224 source "net/phonet/Kconfig"
225 source "net/6lowpan/Kconfig"
226 source "net/ieee802154/Kconfig"
227 source "net/mac802154/Kconfig"
228 source "net/sched/Kconfig"
229 source "net/dcb/Kconfig"
230 source "net/dns_resolver/Kconfig"
231 source "net/batman-adv/Kconfig"
232 source "net/openvswitch/Kconfig"
233 source "net/vmw_vsock/Kconfig"
234 source "net/netlink/Kconfig"
235 source "net/mpls/Kconfig"
236 source "net/hsr/Kconfig"
237 source "net/switchdev/Kconfig"
238 source "net/l3mdev/Kconfig"
242 depends on SMP && SYSFS
256 config SOCK_CGROUP_DATA
260 config CGROUP_NET_PRIO
261 bool "Network priority cgroup"
263 select SOCK_CGROUP_DATA
265 Cgroup subsystem for use in assigning processes to network priorities on
266 a per-interface basis.
268 config CGROUP_NET_CLASSID
269 bool "Network classid cgroup"
271 select SOCK_CGROUP_DATA
273 Cgroup subsystem for use as general purpose socket classid marker that is
274 being used in cls_cgroup and for netfilter matching.
276 config NET_RX_BUSY_POLL
287 bool "enable BPF Just In Time compiler"
288 depends on HAVE_BPF_JIT
291 Berkeley Packet Filter filtering capabilities are normally handled
292 by an interpreter. This option allows kernel to generate a native
293 code when filter is loaded in memory. This should speedup
294 packet sniffing (libpcap/tcpdump). Note : Admin should enable
295 this feature changing /proc/sys/net/core/bpf_jit_enable
297 config NET_FLOW_LIMIT
302 The network stack has to drop packets when a receive processing CPU's
303 backlog reaches netdev_max_backlog. If a few out of many active flows
304 generate the vast majority of load, drop their traffic earlier to
305 maintain capacity for the other flows. This feature provides servers
306 with many clients some protection against DoS by a single (spoofed)
307 flow that greatly exceeds average workload.
309 menu "Network testing"
312 tristate "Packet Generator (USE WITH CAUTION)"
313 depends on INET && PROC_FS
315 This module will inject preconfigured packets, at a configurable
316 rate, out of a given interface. It is used for network interface
317 stress testing and performance analysis. If you don't understand
318 what was just said, you don't need it: say N.
320 Documentation on how to use the packet generator can be found
321 at <file:Documentation/networking/pktgen.txt>.
323 To compile this code as a module, choose M here: the
324 module will be called pktgen.
327 tristate "TCP connection probing"
328 depends on INET && PROC_FS && KPROBES
330 This module allows for capturing the changes to TCP connection
331 state in response to incoming packets. It is used for debugging
332 TCP congestion avoidance modules. If you don't understand
333 what was just said, you don't need it: say N.
335 Documentation on how to use TCP connection probing can be found
338 http://www.linuxfoundation.org/collaborate/workgroups/networking/tcpprobe
340 To compile this code as a module, choose M here: the
341 module will be called tcp_probe.
343 config NET_DROP_MONITOR
344 tristate "Network packet drop alerting service"
345 depends on INET && TRACEPOINTS
347 This feature provides an alerting service to userspace in the
348 event that packets are discarded in the network stack. Alerts
349 are broadcast via netlink socket to any listening user space
350 process. If you don't need network drop alerts, or if you are ok
351 just checking the various proc files and other utilities for
352 drop statistics, say N here.
358 source "net/ax25/Kconfig"
359 source "net/can/Kconfig"
360 source "net/irda/Kconfig"
361 source "net/bluetooth/Kconfig"
362 source "net/rxrpc/Kconfig"
374 source "net/wireless/Kconfig"
375 source "net/mac80211/Kconfig"
379 source "net/wimax/Kconfig"
381 source "net/rfkill/Kconfig"
382 source "net/9p/Kconfig"
383 source "net/caif/Kconfig"
384 source "net/ceph/Kconfig"
385 source "net/nfc/Kconfig"
388 bool "Network light weight tunnels"
390 This feature provides an infrastructure to support light weight
391 tunnels like mpls. There is no netdevice associated with a light
392 weight tunnel endpoint. Tunnel encapsulation parameters are stored
393 with light weight tunnel state associated with fib routes.
400 tristate "Network physical/parent device Netlink interface"
402 Network physical/parent device Netlink interface provides
403 infrastructure to support access to physical chip-wide config and
406 config MAY_USE_DEVLINK
408 default m if NET_DEVLINK=m
409 default y if NET_DEVLINK=y || NET_DEVLINK=n
411 Drivers using the devlink infrastructure should have a dependency
412 on MAY_USE_DEVLINK to ensure they do not cause link errors when
413 devlink is a loadable module and the driver using it is built-in.
417 # Used by archs to tell that they support BPF_JIT