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!
58 menu "Networking options"
60 source "net/packet/Kconfig"
61 source "net/unix/Kconfig"
62 source "net/tls/Kconfig"
63 source "net/xfrm/Kconfig"
64 source "net/iucv/Kconfig"
65 source "net/smc/Kconfig"
66 source "net/xdp/Kconfig"
69 bool "Connecion oriented routing"
75 bool "TCP/IP networking"
77 These are the protocols used on the Internet and on most local
78 Ethernets. It is highly recommended to say Y here (this will enlarge
79 your kernel by about 400 KB), since some programs (e.g. the X window
80 system) use TCP/IP even if your machine is not connected to any
81 other computer. You will get the so-called loopback device which
82 allows you to ping yourself (great fun, that!).
84 For an excellent introduction to Linux networking, please read the
85 Linux Networking HOWTO, available from
86 <http://www.tldp.org/docs.html#howto>.
88 If you say Y here and also to "/proc file system support" and
89 "Sysctl support" below, you can change various aspects of the
90 behavior of the TCP/IP code by writing to the (virtual) files in
91 /proc/sys/net/ipv4/*; the options are explained in the file
92 <file:Documentation/networking/ip-sysctl.txt>.
97 source "net/ipv4/Kconfig"
98 source "net/ipv6/Kconfig"
99 source "net/netlabel/Kconfig"
103 config NETWORK_SECMARK
104 bool "Security Marking"
106 This enables security marking of network packets, similar
107 to nfmark, but designated for security purposes.
108 If you are unsure how to answer this question, answer N.
110 config NET_PTP_CLASSIFY
113 config NETWORK_PHY_TIMESTAMPING
114 bool "Timestamping in PHY devices"
115 select NET_PTP_CLASSIFY
117 This allows timestamping of network packets by PHYs with
118 hardware timestamping capabilities. This option adds some
119 overhead in the transmit and receive paths.
121 If you are unsure how to answer this question, answer N.
124 bool "Network packet filtering framework (Netfilter)"
126 Netfilter is a framework for filtering and mangling network packets
127 that pass through your Linux box.
129 The most common use of packet filtering is to run your Linux box as
130 a firewall protecting a local network from the Internet. The type of
131 firewall provided by this kernel support is called a "packet
132 filter", which means that it can reject individual network packets
133 based on type, source, destination etc. The other kind of firewall,
134 a "proxy-based" one, is more secure but more intrusive and more
135 bothersome to set up; it inspects the network traffic much more
136 closely, modifies it and has knowledge about the higher level
137 protocols, which a packet filter lacks. Moreover, proxy-based
138 firewalls often require changes to the programs running on the local
139 clients. Proxy-based firewalls don't need support by the kernel, but
140 they are often combined with a packet filter, which only works if
143 You should also say Y here if you intend to use your Linux box as
144 the gateway to the Internet for a local network of machines without
145 globally valid IP addresses. This is called "masquerading": if one
146 of the computers on your local network wants to send something to
147 the outside, your box can "masquerade" as that computer, i.e. it
148 forwards the traffic to the intended outside destination, but
149 modifies the packets to make it look like they came from the
150 firewall box itself. It works both ways: if the outside host
151 replies, the Linux box will silently forward the traffic to the
152 correct local computer. This way, the computers on your local net
153 are completely invisible to the outside world, even though they can
154 reach the outside and can receive replies. It is even possible to
155 run globally visible servers from within a masqueraded local network
156 using a mechanism called portforwarding. Masquerading is also often
157 called NAT (Network Address Translation).
159 Another use of Netfilter is in transparent proxying: if a machine on
160 the local network tries to connect to an outside host, your Linux
161 box can transparently forward the traffic to a local server,
162 typically a caching proxy server.
164 Yet another use of Netfilter is building a bridging firewall. Using
165 a bridge with Network packet filtering enabled makes iptables "see"
166 the bridged traffic. For filtering on the lower network and Ethernet
167 protocols over the bridge, use ebtables (under bridge netfilter
170 Various modules exist for netfilter which replace the previous
171 masquerading (ipmasqadm), packet filtering (ipchains), transparent
172 proxying, and portforwarding mechanisms. Please see
173 <file:Documentation/Changes> under "iptables" for the location of
178 config NETFILTER_ADVANCED
179 bool "Advanced netfilter configuration"
183 If you say Y here you can select between all the netfilter modules.
184 If you say N the more unusual ones will not be shown and the
185 basic ones needed by most people will default to 'M'.
189 config BRIDGE_NETFILTER
190 tristate "Bridged IP/ARP packets filtering"
192 depends on NETFILTER && INET
193 depends on NETFILTER_ADVANCED
194 select NETFILTER_FAMILY_BRIDGE
195 select SKB_EXTENSIONS
198 Enabling this option will let arptables resp. iptables see bridged
199 ARP resp. IP traffic. If you want a bridging firewall, you probably
200 want this option enabled.
201 Enabling or disabling this option doesn't enable or disable
206 source "net/netfilter/Kconfig"
207 source "net/ipv4/netfilter/Kconfig"
208 source "net/ipv6/netfilter/Kconfig"
209 source "net/decnet/netfilter/Kconfig"
210 source "net/bridge/netfilter/Kconfig"
214 source "net/bpfilter/Kconfig"
216 source "net/dccp/Kconfig"
217 source "net/sctp/Kconfig"
218 source "net/rds/Kconfig"
219 source "net/tipc/Kconfig"
220 source "net/atm/Kconfig"
221 source "net/l2tp/Kconfig"
222 source "net/802/Kconfig"
223 source "net/bridge/Kconfig"
224 source "net/dsa/Kconfig"
225 source "net/8021q/Kconfig"
226 source "net/decnet/Kconfig"
227 source "net/llc/Kconfig"
228 source "drivers/net/appletalk/Kconfig"
229 source "net/x25/Kconfig"
230 source "net/lapb/Kconfig"
231 source "net/phonet/Kconfig"
232 source "net/6lowpan/Kconfig"
233 source "net/ieee802154/Kconfig"
234 source "net/mac802154/Kconfig"
235 source "net/sched/Kconfig"
236 source "net/dcb/Kconfig"
237 source "net/dns_resolver/Kconfig"
238 source "net/batman-adv/Kconfig"
239 source "net/openvswitch/Kconfig"
240 source "net/vmw_vsock/Kconfig"
241 source "net/netlink/Kconfig"
242 source "net/mpls/Kconfig"
243 source "net/nsh/Kconfig"
244 source "net/hsr/Kconfig"
245 source "net/switchdev/Kconfig"
246 source "net/l3mdev/Kconfig"
247 source "net/qrtr/Kconfig"
248 source "net/ncsi/Kconfig"
252 depends on SMP && SYSFS
269 config CGROUP_NET_PRIO
270 bool "Network priority cgroup"
272 select SOCK_CGROUP_DATA
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"
280 select SOCK_CGROUP_DATA
282 Cgroup subsystem for use as general purpose socket classid marker that is
283 being used in cls_cgroup and for netfilter matching.
285 config NET_RX_BUSY_POLL
296 bool "enable BPF Just In Time compiler"
297 depends on HAVE_CBPF_JIT || HAVE_EBPF_JIT
300 Berkeley Packet Filter filtering capabilities are normally handled
301 by an interpreter. This option allows kernel to generate a native
302 code when filter is loaded in memory. This should speedup
303 packet sniffing (libpcap/tcpdump).
305 Note, admin should enable this feature changing:
306 /proc/sys/net/core/bpf_jit_enable
307 /proc/sys/net/core/bpf_jit_harden (optional)
308 /proc/sys/net/core/bpf_jit_kallsyms (optional)
310 config BPF_STREAM_PARSER
311 bool "enable BPF STREAM_PARSER"
313 depends on BPF_SYSCALL
314 depends on CGROUP_BPF
318 Enabling this allows a stream parser to be used with
319 BPF_MAP_TYPE_SOCKMAP.
321 BPF_MAP_TYPE_SOCKMAP provides a map type to use with network sockets.
322 It can be used to enforce socket policy, implement socket redirects,
325 config NET_FLOW_LIMIT
330 The network stack has to drop packets when a receive processing CPU's
331 backlog reaches netdev_max_backlog. If a few out of many active flows
332 generate the vast majority of load, drop their traffic earlier to
333 maintain capacity for the other flows. This feature provides servers
334 with many clients some protection against DoS by a single (spoofed)
335 flow that greatly exceeds average workload.
337 menu "Network testing"
340 tristate "Packet Generator (USE WITH CAUTION)"
341 depends on INET && PROC_FS
343 This module will inject preconfigured packets, at a configurable
344 rate, out of a given interface. It is used for network interface
345 stress testing and performance analysis. If you don't understand
346 what was just said, you don't need it: say N.
348 Documentation on how to use the packet generator can be found
349 at <file:Documentation/networking/pktgen.txt>.
351 To compile this code as a module, choose M here: the
352 module will be called pktgen.
354 config NET_DROP_MONITOR
355 tristate "Network packet drop alerting service"
356 depends on INET && TRACEPOINTS
358 This feature provides an alerting service to userspace in the
359 event that packets are discarded in the network stack. Alerts
360 are broadcast via netlink socket to any listening user space
361 process. If you don't need network drop alerts, or if you are ok
362 just checking the various proc files and other utilities for
363 drop statistics, say N here.
369 source "net/ax25/Kconfig"
370 source "net/can/Kconfig"
371 source "net/bluetooth/Kconfig"
372 source "net/rxrpc/Kconfig"
373 source "net/kcm/Kconfig"
374 source "net/strparser/Kconfig"
386 source "net/wireless/Kconfig"
387 source "net/mac80211/Kconfig"
391 source "net/wimax/Kconfig"
393 source "net/rfkill/Kconfig"
394 source "net/9p/Kconfig"
395 source "net/caif/Kconfig"
396 source "net/ceph/Kconfig"
397 source "net/nfc/Kconfig"
398 source "net/psample/Kconfig"
399 source "net/ife/Kconfig"
402 bool "Network light weight tunnels"
404 This feature provides an infrastructure to support light weight
405 tunnels like mpls. There is no netdevice associated with a light
406 weight tunnel endpoint. Tunnel encapsulation parameters are stored
407 with light weight tunnel state associated with fib routes.
410 bool "Execute BPF program as route nexthop action"
411 depends on LWTUNNEL && INET
412 default y if LWTUNNEL=y
414 Allows to run BPF programs as a nexthop action following a route
415 lookup for incoming and outgoing packets.
425 config SOCK_VALIDATE_XMIT
432 The NET_SOCK_MSG provides a framework for plain sockets (e.g. TCP) or
433 ULPs (upper layer modules, e.g. TLS) to process L7 application data
434 with the help of BPF programs.
439 imply NET_DROP_MONITOR
445 tristate "Generic failover module"
447 The failover module provides a generic interface for paravirtual
448 drivers to register a netdev and a set of ops with a failover
449 instance. The ops are used as event handlers that get called to
450 handle netdev register/unregister/link change/name change events
451 on slave pci ethernet devices with the same mac address as the
452 failover netdev. This enables paravirtual drivers to use a
453 VF as an accelerated low latency datapath. It also allows live
454 migration of VMs with direct attached VFs by failing over to the
455 paravirtual datapath when the VF is unplugged.
459 # Used by archs to tell that they support BPF JIT compiler plus which flavour.
460 # Only one of the two can be selected for a specific arch since eBPF JIT supersedes
463 # Classic BPF JIT (cBPF)
467 # Extended BPF JIT (eBPF)