1 # SPDX-License-Identifier: GPL-2.0-only
3 # Network configuration
7 bool "Networking support"
9 select GENERIC_NET_UTILS
12 Unless you really know what you are doing, you should say Y here.
13 The reason is that some programs need kernel networking support even
14 when running on a stand-alone machine that isn't connected to any
17 If you are upgrading from an older kernel, you
18 should consider updating your networking tools too because changes
19 in the kernel and the tools often go hand in hand. The tools are
20 contained in the package net-tools, the location and version number
21 of which are given in <file:Documentation/Changes>.
23 For a general introduction to Linux networking, it is highly
24 recommended to read the NET-HOWTO, available from
25 <http://www.tldp.org/docs.html#howto>.
29 config WANT_COMPAT_NETLINK_MESSAGES
32 This option can be selected by other options that need compat
35 config COMPAT_NETLINK_MESSAGES
38 depends on WEXT_CORE || WANT_COMPAT_NETLINK_MESSAGES
40 This option makes it possible to send different netlink messages
41 to tasks depending on whether the task is a compat task or not. To
42 achieve this, you need to set skb_shinfo(skb)->frag_list to the
43 compat skb before sending the skb, the netlink code will sort out
44 which message to actually pass to the task.
46 Newly written code should NEVER need this option but do
47 compat-independent messages instead!
61 menu "Networking options"
63 source "net/packet/Kconfig"
64 source "net/unix/Kconfig"
65 source "net/tls/Kconfig"
66 source "net/xfrm/Kconfig"
67 source "net/iucv/Kconfig"
68 source "net/smc/Kconfig"
69 source "net/xdp/Kconfig"
72 bool "TCP/IP networking"
74 These are the protocols used on the Internet and on most local
75 Ethernets. It is highly recommended to say Y here (this will enlarge
76 your kernel by about 400 KB), since some programs (e.g. the X window
77 system) use TCP/IP even if your machine is not connected to any
78 other computer. You will get the so-called loopback device which
79 allows you to ping yourself (great fun, that!).
81 For an excellent introduction to Linux networking, please read the
82 Linux Networking HOWTO, available from
83 <http://www.tldp.org/docs.html#howto>.
85 If you say Y here and also to "/proc file system support" and
86 "Sysctl support" below, you can change various aspects of the
87 behavior of the TCP/IP code by writing to the (virtual) files in
88 /proc/sys/net/ipv4/*; the options are explained in the file
89 <file:Documentation/networking/ip-sysctl.rst>.
94 source "net/ipv4/Kconfig"
95 source "net/ipv6/Kconfig"
96 source "net/netlabel/Kconfig"
97 source "net/mptcp/Kconfig"
101 config NETWORK_SECMARK
102 bool "Security Marking"
104 This enables security marking of network packets, similar
105 to nfmark, but designated for security purposes.
106 If you are unsure how to answer this question, answer N.
108 config NET_PTP_CLASSIFY
111 config NETWORK_PHY_TIMESTAMPING
112 bool "Timestamping in PHY devices"
113 select NET_PTP_CLASSIFY
115 This allows timestamping of network packets by PHYs (or
116 other MII bus snooping devices) with hardware timestamping
117 capabilities. This option adds some overhead in the transmit
120 If you are unsure how to answer this question, answer N.
123 bool "Network packet filtering framework (Netfilter)"
125 Netfilter is a framework for filtering and mangling network packets
126 that pass through your Linux box.
128 The most common use of packet filtering is to run your Linux box as
129 a firewall protecting a local network from the Internet. The type of
130 firewall provided by this kernel support is called a "packet
131 filter", which means that it can reject individual network packets
132 based on type, source, destination etc. The other kind of firewall,
133 a "proxy-based" one, is more secure but more intrusive and more
134 bothersome to set up; it inspects the network traffic much more
135 closely, modifies it and has knowledge about the higher level
136 protocols, which a packet filter lacks. Moreover, proxy-based
137 firewalls often require changes to the programs running on the local
138 clients. Proxy-based firewalls don't need support by the kernel, but
139 they are often combined with a packet filter, which only works if
142 You should also say Y here if you intend to use your Linux box as
143 the gateway to the Internet for a local network of machines without
144 globally valid IP addresses. This is called "masquerading": if one
145 of the computers on your local network wants to send something to
146 the outside, your box can "masquerade" as that computer, i.e. it
147 forwards the traffic to the intended outside destination, but
148 modifies the packets to make it look like they came from the
149 firewall box itself. It works both ways: if the outside host
150 replies, the Linux box will silently forward the traffic to the
151 correct local computer. This way, the computers on your local net
152 are completely invisible to the outside world, even though they can
153 reach the outside and can receive replies. It is even possible to
154 run globally visible servers from within a masqueraded local network
155 using a mechanism called portforwarding. Masquerading is also often
156 called NAT (Network Address Translation).
158 Another use of Netfilter is in transparent proxying: if a machine on
159 the local network tries to connect to an outside host, your Linux
160 box can transparently forward the traffic to a local server,
161 typically a caching proxy server.
163 Yet another use of Netfilter is building a bridging firewall. Using
164 a bridge with Network packet filtering enabled makes iptables "see"
165 the bridged traffic. For filtering on the lower network and Ethernet
166 protocols over the bridge, use ebtables (under bridge netfilter
169 Various modules exist for netfilter which replace the previous
170 masquerading (ipmasqadm), packet filtering (ipchains), transparent
171 proxying, and portforwarding mechanisms. Please see
172 <file:Documentation/Changes> under "iptables" for the location of
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
193 select NETFILTER_FAMILY_BRIDGE
194 select SKB_EXTENSIONS
196 Enabling this option will let arptables resp. iptables see bridged
197 ARP resp. IP traffic. If you want a bridging firewall, you probably
198 want this option enabled.
199 Enabling or disabling this option doesn't enable or disable
204 source "net/netfilter/Kconfig"
205 source "net/ipv4/netfilter/Kconfig"
206 source "net/ipv6/netfilter/Kconfig"
207 source "net/decnet/netfilter/Kconfig"
208 source "net/bridge/netfilter/Kconfig"
212 source "net/bpfilter/Kconfig"
214 source "net/dccp/Kconfig"
215 source "net/sctp/Kconfig"
216 source "net/rds/Kconfig"
217 source "net/tipc/Kconfig"
218 source "net/atm/Kconfig"
219 source "net/l2tp/Kconfig"
220 source "net/802/Kconfig"
221 source "net/bridge/Kconfig"
222 source "net/dsa/Kconfig"
223 source "net/8021q/Kconfig"
224 source "net/decnet/Kconfig"
225 source "net/llc/Kconfig"
226 source "drivers/net/appletalk/Kconfig"
227 source "net/x25/Kconfig"
228 source "net/lapb/Kconfig"
229 source "net/phonet/Kconfig"
230 source "net/6lowpan/Kconfig"
231 source "net/ieee802154/Kconfig"
232 source "net/mac802154/Kconfig"
233 source "net/sched/Kconfig"
234 source "net/dcb/Kconfig"
235 source "net/dns_resolver/Kconfig"
236 source "net/batman-adv/Kconfig"
237 source "net/openvswitch/Kconfig"
238 source "net/vmw_vsock/Kconfig"
239 source "net/netlink/Kconfig"
240 source "net/mpls/Kconfig"
241 source "net/nsh/Kconfig"
242 source "net/hsr/Kconfig"
243 source "net/switchdev/Kconfig"
244 source "net/l3mdev/Kconfig"
245 source "net/qrtr/Kconfig"
246 source "net/ncsi/Kconfig"
248 config PCPU_DEV_REFCNT
249 bool "Use percpu variables to maintain network device refcount"
253 network device refcount are using per cpu variables if this option is set.
254 This can be forced to N to detect underflows (with a performance drop).
258 depends on SMP && SYSFS
267 config SOCK_RX_QUEUE_MAPPING
273 select SOCK_RX_QUEUE_MAPPING
279 config CGROUP_NET_PRIO
280 bool "Network priority cgroup"
282 select SOCK_CGROUP_DATA
284 Cgroup subsystem for use in assigning processes to network priorities on
285 a per-interface basis.
287 config CGROUP_NET_CLASSID
288 bool "Network classid cgroup"
290 select SOCK_CGROUP_DATA
292 Cgroup subsystem for use as general purpose socket classid marker that is
293 being used in cls_cgroup and for netfilter matching.
295 config NET_RX_BUSY_POLL
306 bool "enable BPF Just In Time compiler"
307 depends on HAVE_CBPF_JIT || HAVE_EBPF_JIT
310 Berkeley Packet Filter filtering capabilities are normally handled
311 by an interpreter. This option allows kernel to generate a native
312 code when filter is loaded in memory. This should speedup
313 packet sniffing (libpcap/tcpdump).
315 Note, admin should enable this feature changing:
316 /proc/sys/net/core/bpf_jit_enable
317 /proc/sys/net/core/bpf_jit_harden (optional)
318 /proc/sys/net/core/bpf_jit_kallsyms (optional)
320 config BPF_STREAM_PARSER
321 bool "enable BPF STREAM_PARSER"
323 depends on BPF_SYSCALL
324 depends on CGROUP_BPF
328 Enabling this allows a TCP stream parser to be used with
329 BPF_MAP_TYPE_SOCKMAP.
331 config NET_FLOW_LIMIT
336 The network stack has to drop packets when a receive processing CPU's
337 backlog reaches netdev_max_backlog. If a few out of many active flows
338 generate the vast majority of load, drop their traffic earlier to
339 maintain capacity for the other flows. This feature provides servers
340 with many clients some protection against DoS by a single (spoofed)
341 flow that greatly exceeds average workload.
343 menu "Network testing"
346 tristate "Packet Generator (USE WITH CAUTION)"
347 depends on INET && PROC_FS
349 This module will inject preconfigured packets, at a configurable
350 rate, out of a given interface. It is used for network interface
351 stress testing and performance analysis. If you don't understand
352 what was just said, you don't need it: say N.
354 Documentation on how to use the packet generator can be found
355 at <file:Documentation/networking/pktgen.rst>.
357 To compile this code as a module, choose M here: the
358 module will be called pktgen.
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/bluetooth/Kconfig"
378 source "net/rxrpc/Kconfig"
379 source "net/kcm/Kconfig"
380 source "net/strparser/Kconfig"
392 source "net/wireless/Kconfig"
393 source "net/mac80211/Kconfig"
397 source "net/rfkill/Kconfig"
398 source "net/9p/Kconfig"
399 source "net/caif/Kconfig"
400 source "net/ceph/Kconfig"
401 source "net/nfc/Kconfig"
402 source "net/psample/Kconfig"
403 source "net/ife/Kconfig"
406 bool "Network light weight tunnels"
408 This feature provides an infrastructure to support light weight
409 tunnels like mpls. There is no netdevice associated with a light
410 weight tunnel endpoint. Tunnel encapsulation parameters are stored
411 with light weight tunnel state associated with fib routes.
414 bool "Execute BPF program as route nexthop action"
415 depends on LWTUNNEL && INET
416 default y if LWTUNNEL=y
418 Allows to run BPF programs as a nexthop action following a route
419 lookup for incoming and outgoing packets.
429 config SOCK_VALIDATE_XMIT
434 depends on PHYLIB && INET
440 The NET_SOCK_MSG provides a framework for plain sockets (e.g. TCP) or
441 ULPs (upper layer modules, e.g. TLS) to process L7 application data
442 with the help of BPF programs.
452 tristate "Generic failover module"
454 The failover module provides a generic interface for paravirtual
455 drivers to register a netdev and a set of ops with a failover
456 instance. The ops are used as event handlers that get called to
457 handle netdev register/unregister/link change/name change events
458 on slave pci ethernet devices with the same mac address as the
459 failover netdev. This enables paravirtual drivers to use a
460 VF as an accelerated low latency datapath. It also allows live
461 migration of VMs with direct attached VFs by failing over to the
462 paravirtual datapath when the VF is unplugged.
464 config ETHTOOL_NETLINK
465 bool "Netlink interface for ethtool"
468 An alternative userspace interface for ethtool based on generic
469 netlink. It provides better extensibility and some new features,
470 e.g. notification messages.
474 # Used by archs to tell that they support BPF JIT compiler plus which flavour.
475 # Only one of the two can be selected for a specific arch since eBPF JIT supersedes
478 # Classic BPF JIT (cBPF)
482 # Extended BPF JIT (eBPF)