1# SPDX-License-Identifier: GPL-2.0-only 2# 3# Network configuration 4# 5 6menuconfig NET 7 bool "Networking support" 8 select NLATTR 9 select GENERIC_NET_UTILS 10 select BPF 11 help 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 15 other computer. 16 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>. 22 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>. 26 27if NET 28 29config WANT_COMPAT_NETLINK_MESSAGES 30 bool 31 help 32 This option can be selected by other options that need compat 33 netlink messages. 34 35config COMPAT_NETLINK_MESSAGES 36 def_bool y 37 depends on COMPAT 38 depends on WEXT_CORE || WANT_COMPAT_NETLINK_MESSAGES 39 help 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. 45 46 Newly written code should NEVER need this option but do 47 compat-independent messages instead! 48 49config NET_INGRESS 50 bool 51 52config NET_EGRESS 53 bool 54 55config NET_XGRESS 56 select NET_INGRESS 57 select NET_EGRESS 58 bool 59 60config NET_REDIRECT 61 bool 62 63config SKB_DECRYPTED 64 bool 65 66config SKB_EXTENSIONS 67 bool 68 69config NET_DEVMEM 70 def_bool y 71 select GENERIC_ALLOCATOR 72 depends on DMA_SHARED_BUFFER 73 depends on PAGE_POOL 74 75config NET_SHAPER 76 bool 77 78config NET_CRC32C 79 bool 80 select CRC32 81 82menu "Networking options" 83 84source "net/packet/Kconfig" 85source "net/unix/Kconfig" 86source "net/tls/Kconfig" 87source "net/xfrm/Kconfig" 88source "net/iucv/Kconfig" 89source "net/smc/Kconfig" 90source "net/xdp/Kconfig" 91 92config NET_HANDSHAKE 93 bool 94 depends on SUNRPC || NVME_TARGET_TCP || NVME_TCP 95 default y 96 97config NET_HANDSHAKE_KUNIT_TEST 98 tristate "KUnit tests for the handshake upcall mechanism" if !KUNIT_ALL_TESTS 99 default KUNIT_ALL_TESTS 100 depends on KUNIT 101 help 102 This builds the KUnit tests for the handshake upcall mechanism. 103 104 KUnit tests run during boot and output the results to the debug 105 log in TAP format (https://testanything.org/). Only useful for 106 kernel devs running KUnit test harness and are not for inclusion 107 into a production build. 108 109 For more information on KUnit and unit tests in general, refer 110 to the KUnit documentation in Documentation/dev-tools/kunit/. 111 112config INET 113 bool "TCP/IP networking" 114 help 115 These are the protocols used on the Internet and on most local 116 Ethernets. It is highly recommended to say Y here (this will enlarge 117 your kernel by about 400 KB), since some programs (e.g. the X window 118 system) use TCP/IP even if your machine is not connected to any 119 other computer. You will get the so-called loopback device which 120 allows you to ping yourself (great fun, that!). 121 122 For an excellent introduction to Linux networking, please read the 123 Linux Networking HOWTO, available from 124 <http://www.tldp.org/docs.html#howto>. 125 126 If you say Y here and also to "/proc file system support" and 127 "Sysctl support" below, you can change various aspects of the 128 behavior of the TCP/IP code by writing to the (virtual) files in 129 /proc/sys/net/ipv4/*; the options are explained in the file 130 <file:Documentation/networking/ip-sysctl.rst>. 131 132 Short answer: say Y. 133 134if INET 135source "net/ipv4/Kconfig" 136source "net/ipv6/Kconfig" 137source "net/netlabel/Kconfig" 138source "net/mptcp/Kconfig" 139 140endif # if INET 141 142config NETWORK_SECMARK 143 bool "Security Marking" 144 help 145 This enables security marking of network packets, similar 146 to nfmark, but designated for security purposes. 147 If you are unsure how to answer this question, answer N. 148 149config NET_PTP_CLASSIFY 150 def_bool n 151 152config NETWORK_PHY_TIMESTAMPING 153 bool "Timestamping in PHY devices" 154 select NET_PTP_CLASSIFY 155 help 156 This allows timestamping of network packets by PHYs (or 157 other MII bus snooping devices) with hardware timestamping 158 capabilities. This option adds some overhead in the transmit 159 and receive paths. 160 161 If you are unsure how to answer this question, answer N. 162 163menuconfig NETFILTER 164 bool "Network packet filtering framework (Netfilter)" 165 help 166 Netfilter is a framework for filtering and mangling network packets 167 that pass through your Linux box. 168 169 The most common use of packet filtering is to run your Linux box as 170 a firewall protecting a local network from the Internet. The type of 171 firewall provided by this kernel support is called a "packet 172 filter", which means that it can reject individual network packets 173 based on type, source, destination etc. The other kind of firewall, 174 a "proxy-based" one, is more secure but more intrusive and more 175 bothersome to set up; it inspects the network traffic much more 176 closely, modifies it and has knowledge about the higher level 177 protocols, which a packet filter lacks. Moreover, proxy-based 178 firewalls often require changes to the programs running on the local 179 clients. Proxy-based firewalls don't need support by the kernel, but 180 they are often combined with a packet filter, which only works if 181 you say Y here. 182 183 You should also say Y here if you intend to use your Linux box as 184 the gateway to the Internet for a local network of machines without 185 globally valid IP addresses. This is called "masquerading": if one 186 of the computers on your local network wants to send something to 187 the outside, your box can "masquerade" as that computer, i.e. it 188 forwards the traffic to the intended outside destination, but 189 modifies the packets to make it look like they came from the 190 firewall box itself. It works both ways: if the outside host 191 replies, the Linux box will silently forward the traffic to the 192 correct local computer. This way, the computers on your local net 193 are completely invisible to the outside world, even though they can 194 reach the outside and can receive replies. It is even possible to 195 run globally visible servers from within a masqueraded local network 196 using a mechanism called portforwarding. Masquerading is also often 197 called NAT (Network Address Translation). 198 199 Another use of Netfilter is in transparent proxying: if a machine on 200 the local network tries to connect to an outside host, your Linux 201 box can transparently forward the traffic to a local server, 202 typically a caching proxy server. 203 204 Yet another use of Netfilter is building a bridging firewall. Using 205 a bridge with Network packet filtering enabled makes iptables "see" 206 the bridged traffic. For filtering on the lower network and Ethernet 207 protocols over the bridge, use ebtables (under bridge netfilter 208 configuration). 209 210 Various modules exist for netfilter which replace the previous 211 masquerading (ipmasqadm), packet filtering (ipchains), transparent 212 proxying, and portforwarding mechanisms. Please see 213 <file:Documentation/Changes> under "iptables" for the location of 214 these packages. 215 216if NETFILTER 217 218config NETFILTER_ADVANCED 219 bool "Advanced netfilter configuration" 220 depends on NETFILTER 221 default y 222 help 223 If you say Y here you can select between all the netfilter modules. 224 If you say N the more unusual ones will not be shown and the 225 basic ones needed by most people will default to 'M'. 226 227 If unsure, say Y. 228 229config BRIDGE_NETFILTER 230 tristate "Bridged IP/ARP packets filtering" 231 depends on BRIDGE 232 depends on NETFILTER && INET 233 depends on NETFILTER_ADVANCED 234 select NETFILTER_FAMILY_BRIDGE 235 select SKB_EXTENSIONS 236 help 237 Enabling this option will let arptables resp. iptables see bridged 238 ARP resp. IP traffic. If you want a bridging firewall, you probably 239 want this option enabled. 240 Enabling or disabling this option doesn't enable or disable 241 ebtables. 242 243 If unsure, say N. 244 245source "net/netfilter/Kconfig" 246source "net/ipv4/netfilter/Kconfig" 247source "net/ipv6/netfilter/Kconfig" 248source "net/bridge/netfilter/Kconfig" 249 250endif 251 252source "net/sctp/Kconfig" 253source "net/rds/Kconfig" 254source "net/tipc/Kconfig" 255source "net/atm/Kconfig" 256source "net/l2tp/Kconfig" 257source "net/802/Kconfig" 258source "net/bridge/Kconfig" 259source "net/dsa/Kconfig" 260source "net/8021q/Kconfig" 261source "net/llc/Kconfig" 262source "net/appletalk/Kconfig" 263source "net/x25/Kconfig" 264source "net/lapb/Kconfig" 265source "net/phonet/Kconfig" 266source "net/6lowpan/Kconfig" 267source "net/ieee802154/Kconfig" 268source "net/mac802154/Kconfig" 269source "net/sched/Kconfig" 270source "net/dcb/Kconfig" 271source "net/dns_resolver/Kconfig" 272source "net/batman-adv/Kconfig" 273source "net/openvswitch/Kconfig" 274source "net/vmw_vsock/Kconfig" 275source "net/netlink/Kconfig" 276source "net/mpls/Kconfig" 277source "net/nsh/Kconfig" 278source "net/hsr/Kconfig" 279source "net/switchdev/Kconfig" 280source "net/l3mdev/Kconfig" 281source "net/qrtr/Kconfig" 282source "net/ncsi/Kconfig" 283 284config PCPU_DEV_REFCNT 285 bool "Use percpu variables to maintain network device refcount" 286 depends on SMP 287 default y 288 help 289 network device refcount are using per cpu variables if this option is set. 290 This can be forced to N to detect underflows (with a performance drop). 291 292config MAX_SKB_FRAGS 293 int "Maximum number of fragments per skb_shared_info" 294 range 17 45 295 default 17 296 help 297 Having more fragments per skb_shared_info can help GRO efficiency. 298 This helps BIG TCP workloads, but might expose bugs in some 299 legacy drivers. 300 This also increases memory overhead of small packets, 301 and in drivers using build_skb(). 302 If unsure, say 17. 303 304config RPS 305 bool "Receive packet steering" 306 depends on SMP && SYSFS 307 default y 308 help 309 Software receive side packet steering (RPS) distributes the 310 load of received packet processing across multiple CPUs. 311 312config RFS_ACCEL 313 bool "Hardware acceleration of RFS" 314 depends on RPS 315 select CPU_RMAP 316 default y 317 help 318 Allowing drivers for multiqueue hardware with flow filter tables to 319 accelerate RFS. 320 321config SOCK_RX_QUEUE_MAPPING 322 bool 323 324config XPS 325 bool 326 depends on SMP 327 select SOCK_RX_QUEUE_MAPPING 328 default y 329 330config HWBM 331 bool 332 333config CGROUP_NET_PRIO 334 bool "Network priority cgroup" 335 depends on CGROUPS 336 select SOCK_CGROUP_DATA 337 help 338 Cgroup subsystem for use in assigning processes to network priorities on 339 a per-interface basis. 340 341config CGROUP_NET_CLASSID 342 bool "Network classid cgroup" 343 depends on CGROUPS 344 select SOCK_CGROUP_DATA 345 help 346 Cgroup subsystem for use as general purpose socket classid marker that is 347 being used in cls_cgroup and for netfilter matching. 348 349config NET_RX_BUSY_POLL 350 bool 351 default y if !PREEMPT_RT || (PREEMPT_RT && !NETCONSOLE) 352 353config BQL 354 bool 355 prompt "Enable Byte Queue Limits" 356 depends on SYSFS 357 select DQL 358 default y 359 360config BPF_STREAM_PARSER 361 bool "enable BPF STREAM_PARSER" 362 depends on INET 363 depends on BPF_SYSCALL 364 depends on CGROUP_BPF 365 select STREAM_PARSER 366 select NET_SOCK_MSG 367 help 368 Enabling this allows a TCP stream parser to be used with 369 BPF_MAP_TYPE_SOCKMAP. 370 371config NET_FLOW_LIMIT 372 bool "Net flow limit" 373 depends on RPS 374 default y 375 help 376 The network stack has to drop packets when a receive processing CPU's 377 backlog reaches netdev_max_backlog. If a few out of many active flows 378 generate the vast majority of load, drop their traffic earlier to 379 maintain capacity for the other flows. This feature provides servers 380 with many clients some protection against DoS by a single (spoofed) 381 flow that greatly exceeds average workload. 382 383menu "Network testing" 384 385config NET_PKTGEN 386 tristate "Packet Generator (USE WITH CAUTION)" 387 depends on INET && PROC_FS 388 help 389 This module will inject preconfigured packets, at a configurable 390 rate, out of a given interface. It is used for network interface 391 stress testing and performance analysis. If you don't understand 392 what was just said, you don't need it: say N. 393 394 Documentation on how to use the packet generator can be found 395 at <file:Documentation/networking/pktgen.rst>. 396 397 To compile this code as a module, choose M here: the 398 module will be called pktgen. 399 400config NET_DROP_MONITOR 401 tristate "Network packet drop alerting service" 402 depends on INET && TRACEPOINTS 403 help 404 This feature provides an alerting service to userspace in the 405 event that packets are discarded in the network stack. Alerts 406 are broadcast via netlink socket to any listening user space 407 process. If you don't need network drop alerts, or if you are ok 408 just checking the various proc files and other utilities for 409 drop statistics, say N here. 410 411endmenu 412 413endmenu 414 415source "net/ax25/Kconfig" 416source "net/can/Kconfig" 417source "net/bluetooth/Kconfig" 418source "net/rxrpc/Kconfig" 419source "net/kcm/Kconfig" 420source "net/strparser/Kconfig" 421source "net/mctp/Kconfig" 422 423config FIB_RULES 424 bool 425 426menuconfig WIRELESS 427 bool "Wireless" 428 depends on !S390 429 default y 430 431if WIRELESS 432 433source "net/wireless/Kconfig" 434source "net/mac80211/Kconfig" 435 436endif # WIRELESS 437 438source "net/rfkill/Kconfig" 439source "net/9p/Kconfig" 440source "net/caif/Kconfig" 441source "net/ceph/Kconfig" 442source "net/nfc/Kconfig" 443source "net/psample/Kconfig" 444source "net/ife/Kconfig" 445 446config LWTUNNEL 447 bool "Network light weight tunnels" 448 help 449 This feature provides an infrastructure to support light weight 450 tunnels like mpls. There is no netdevice associated with a light 451 weight tunnel endpoint. Tunnel encapsulation parameters are stored 452 with light weight tunnel state associated with fib routes. 453 454config LWTUNNEL_BPF 455 bool "Execute BPF program as route nexthop action" 456 depends on LWTUNNEL && INET 457 default y if LWTUNNEL=y 458 help 459 Allows to run BPF programs as a nexthop action following a route 460 lookup for incoming and outgoing packets. 461 462config DST_CACHE 463 bool 464 default n 465 466config GRO_CELLS 467 bool 468 default n 469 470config SOCK_VALIDATE_XMIT 471 bool 472 473config NET_IEEE8021Q_HELPERS 474 bool 475 476config NET_SELFTESTS 477 def_tristate PHYLIB 478 depends on PHYLIB && INET 479 480config NET_SOCK_MSG 481 bool 482 default n 483 help 484 The NET_SOCK_MSG provides a framework for plain sockets (e.g. TCP) or 485 ULPs (upper layer modules, e.g. TLS) to process L7 application data 486 with the help of BPF programs. 487 488config NET_DEVLINK 489 bool 490 default n 491 492config PAGE_POOL 493 bool 494 495config PAGE_POOL_STATS 496 default n 497 bool "Page pool stats" 498 depends on PAGE_POOL 499 help 500 Enable page pool statistics to track page allocation and recycling 501 in page pools. This option incurs additional CPU cost in allocation 502 and recycle paths and additional memory cost to store the statistics. 503 These statistics are only available if this option is enabled and if 504 the driver using the page pool supports exporting this data. 505 506 If unsure, say N. 507 508config FAILOVER 509 tristate "Generic failover module" 510 help 511 The failover module provides a generic interface for paravirtual 512 drivers to register a netdev and a set of ops with a failover 513 instance. The ops are used as event handlers that get called to 514 handle netdev register/unregister/link change/name change events 515 on slave pci ethernet devices with the same mac address as the 516 failover netdev. This enables paravirtual drivers to use a 517 VF as an accelerated low latency datapath. It also allows live 518 migration of VMs with direct attached VFs by failing over to the 519 paravirtual datapath when the VF is unplugged. 520 521config ETHTOOL_NETLINK 522 bool "Netlink interface for ethtool" 523 select DIMLIB 524 default y 525 help 526 An alternative userspace interface for ethtool based on generic 527 netlink. It provides better extensibility and some new features, 528 e.g. notification messages. 529 530config NETDEV_ADDR_LIST_TEST 531 tristate "Unit tests for device address list" 532 default KUNIT_ALL_TESTS 533 depends on KUNIT 534 535config NET_TEST 536 tristate "KUnit tests for networking" if !KUNIT_ALL_TESTS 537 depends on KUNIT 538 default KUNIT_ALL_TESTS 539 help 540 KUnit tests covering core networking infra, such as sk_buff. 541 542 If unsure, say N. 543 544endif # if NET 545