1# SPDX-License-Identifier: GPL-2.0-only 2# 3# Network device configuration 4# 5 6menuconfig NETDEVICES 7 default y if UML 8 depends on NET 9 bool "Network device support" 10 ---help--- 11 You can say N here if you don't intend to connect your Linux box to 12 any other computer at all. 13 14 You'll have to say Y if your computer contains a network card that 15 you want to use under Linux. If you are going to run SLIP or PPP over 16 telephone line or null modem cable you need say Y here. Connecting 17 two machines with parallel ports using PLIP needs this, as well as 18 AX.25/KISS for sending Internet traffic over amateur radio links. 19 20 See also "The Linux Network Administrator's Guide" by Olaf Kirch and 21 Terry Dawson. Available at <http://www.tldp.org/guides.html>. 22 23 If unsure, say Y. 24 25# All the following symbols are dependent on NETDEVICES - do not repeat 26# that for each of the symbols. 27if NETDEVICES 28 29config MII 30 tristate 31 32config NET_CORE 33 default y 34 bool "Network core driver support" 35 ---help--- 36 You can say N here if you do not intend to use any of the 37 networking core drivers (i.e. VLAN, bridging, bonding, etc.) 38 39if NET_CORE 40 41config BONDING 42 tristate "Bonding driver support" 43 depends on INET 44 depends on IPV6 || IPV6=n 45 ---help--- 46 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet 47 Channels together. This is called 'Etherchannel' by Cisco, 48 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux. 49 50 The driver supports multiple bonding modes to allow for both high 51 performance and high availability operation. 52 53 Refer to <file:Documentation/networking/bonding.txt> for more 54 information. 55 56 To compile this driver as a module, choose M here: the module 57 will be called bonding. 58 59config DUMMY 60 tristate "Dummy net driver support" 61 ---help--- 62 This is essentially a bit-bucket device (i.e. traffic you send to 63 this device is consigned into oblivion) with a configurable IP 64 address. It is most commonly used in order to make your currently 65 inactive SLIP address seem like a real address for local programs. 66 If you use SLIP or PPP, you might want to say Y here. It won't 67 enlarge your kernel. What a deal. Read about it in the Network 68 Administrator's Guide, available from 69 <http://www.tldp.org/docs.html#guide>. 70 71 To compile this driver as a module, choose M here: the module 72 will be called dummy. 73 74config WIREGUARD 75 tristate "WireGuard secure network tunnel" 76 depends on NET && INET 77 depends on IPV6 || !IPV6 78 select NET_UDP_TUNNEL 79 select DST_CACHE 80 select CRYPTO 81 select CRYPTO_LIB_CURVE25519 82 select CRYPTO_LIB_CHACHA20POLY1305 83 select CRYPTO_LIB_BLAKE2S 84 select CRYPTO_CHACHA20_X86_64 if X86 && 64BIT 85 select CRYPTO_POLY1305_X86_64 if X86 && 64BIT 86 select CRYPTO_BLAKE2S_X86 if X86 && 64BIT 87 select CRYPTO_CURVE25519_X86 if X86 && 64BIT 88 select CRYPTO_CHACHA20_NEON if (ARM || ARM64) && KERNEL_MODE_NEON 89 select CRYPTO_POLY1305_NEON if ARM64 && KERNEL_MODE_NEON 90 select CRYPTO_POLY1305_ARM if ARM 91 select CRYPTO_CURVE25519_NEON if ARM && KERNEL_MODE_NEON 92 select CRYPTO_CHACHA_MIPS if CPU_MIPS32_R2 93 select CRYPTO_POLY1305_MIPS if CPU_MIPS32 || (CPU_MIPS64 && 64BIT) 94 help 95 WireGuard is a secure, fast, and easy to use replacement for IPSec 96 that uses modern cryptography and clever networking tricks. It's 97 designed to be fairly general purpose and abstract enough to fit most 98 use cases, while at the same time remaining extremely simple to 99 configure. See www.wireguard.com for more info. 100 101 It's safe to say Y or M here, as the driver is very lightweight and 102 is only in use when an administrator chooses to add an interface. 103 104config WIREGUARD_DEBUG 105 bool "Debugging checks and verbose messages" 106 depends on WIREGUARD 107 help 108 This will write log messages for handshake and other events 109 that occur for a WireGuard interface. It will also perform some 110 extra validation checks and unit tests at various points. This is 111 only useful for debugging. 112 113 Say N here unless you know what you're doing. 114 115config EQUALIZER 116 tristate "EQL (serial line load balancing) support" 117 ---help--- 118 If you have two serial connections to some other computer (this 119 usually requires two modems and two telephone lines) and you use 120 SLIP (the protocol for sending Internet traffic over telephone 121 lines) or PPP (a better SLIP) on them, you can make them behave like 122 one double speed connection using this driver. Naturally, this has 123 to be supported at the other end as well, either with a similar EQL 124 Linux driver or with a Livingston Portmaster 2e. 125 126 Say Y if you want this and read 127 <file:Documentation/networking/eql.txt>. You may also want to read 128 section 6.2 of the NET-3-HOWTO, available from 129 <http://www.tldp.org/docs.html#howto>. 130 131 To compile this driver as a module, choose M here: the module 132 will be called eql. If unsure, say N. 133 134config NET_FC 135 bool "Fibre Channel driver support" 136 depends on SCSI && PCI 137 help 138 Fibre Channel is a high speed serial protocol mainly used to connect 139 large storage devices to the computer; it is compatible with and 140 intended to replace SCSI. 141 142 If you intend to use Fibre Channel, you need to have a Fibre channel 143 adaptor card in your computer; say Y here and to the driver for your 144 adaptor below. You also should have said Y to "SCSI support" and 145 "SCSI generic support". 146 147config IFB 148 tristate "Intermediate Functional Block support" 149 depends on NET_CLS_ACT 150 ---help--- 151 This is an intermediate driver that allows sharing of 152 resources. 153 To compile this driver as a module, choose M here: the module 154 will be called ifb. If you want to use more than one ifb 155 device at a time, you need to compile this driver as a module. 156 Instead of 'ifb', the devices will then be called 'ifb0', 157 'ifb1' etc. 158 Look at the iproute2 documentation directory for usage etc 159 160source "drivers/net/team/Kconfig" 161 162config MACVLAN 163 tristate "MAC-VLAN support" 164 ---help--- 165 This allows one to create virtual interfaces that map packets to 166 or from specific MAC addresses to a particular interface. 167 168 Macvlan devices can be added using the "ip" command from the 169 iproute2 package starting with the iproute2-2.6.23 release: 170 171 "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan" 172 173 To compile this driver as a module, choose M here: the module 174 will be called macvlan. 175 176config MACVTAP 177 tristate "MAC-VLAN based tap driver" 178 depends on MACVLAN 179 depends on INET 180 select TAP 181 help 182 This adds a specialized tap character device driver that is based 183 on the MAC-VLAN network interface, called macvtap. A macvtap device 184 can be added in the same way as a macvlan device, using 'type 185 macvtap', and then be accessed through the tap user space interface. 186 187 To compile this driver as a module, choose M here: the module 188 will be called macvtap. 189 190config IPVLAN_L3S 191 depends on NETFILTER 192 depends on IPVLAN 193 def_bool y 194 select NET_L3_MASTER_DEV 195 196config IPVLAN 197 tristate "IP-VLAN support" 198 depends on INET 199 depends on IPV6 || !IPV6 200 ---help--- 201 This allows one to create virtual devices off of a main interface 202 and packets will be delivered based on the dest L3 (IPv6/IPv4 addr) 203 on packets. All interfaces (including the main interface) share L2 204 making it transparent to the connected L2 switch. 205 206 Ipvlan devices can be added using the "ip" command from the 207 iproute2 package starting with the iproute2-3.19 release: 208 209 "ip link add link <main-dev> [ NAME ] type ipvlan" 210 211 To compile this driver as a module, choose M here: the module 212 will be called ipvlan. 213 214config IPVTAP 215 tristate "IP-VLAN based tap driver" 216 depends on IPVLAN 217 depends on INET 218 select TAP 219 ---help--- 220 This adds a specialized tap character device driver that is based 221 on the IP-VLAN network interface, called ipvtap. An ipvtap device 222 can be added in the same way as a ipvlan device, using 'type 223 ipvtap', and then be accessed through the tap user space interface. 224 225 To compile this driver as a module, choose M here: the module 226 will be called ipvtap. 227 228config VXLAN 229 tristate "Virtual eXtensible Local Area Network (VXLAN)" 230 depends on INET 231 select NET_UDP_TUNNEL 232 select GRO_CELLS 233 ---help--- 234 This allows one to create vxlan virtual interfaces that provide 235 Layer 2 Networks over Layer 3 Networks. VXLAN is often used 236 to tunnel virtual network infrastructure in virtualized environments. 237 For more information see: 238 http://tools.ietf.org/html/draft-mahalingam-dutt-dcops-vxlan-02 239 240 To compile this driver as a module, choose M here: the module 241 will be called vxlan. 242 243config GENEVE 244 tristate "Generic Network Virtualization Encapsulation" 245 depends on INET 246 depends on IPV6 || !IPV6 247 select NET_UDP_TUNNEL 248 select GRO_CELLS 249 ---help--- 250 This allows one to create geneve virtual interfaces that provide 251 Layer 2 Networks over Layer 3 Networks. GENEVE is often used 252 to tunnel virtual network infrastructure in virtualized environments. 253 For more information see: 254 http://tools.ietf.org/html/draft-gross-geneve-02 255 256 To compile this driver as a module, choose M here: the module 257 will be called geneve. 258 259config GTP 260 tristate "GPRS Tunneling Protocol datapath (GTP-U)" 261 depends on INET 262 select NET_UDP_TUNNEL 263 ---help--- 264 This allows one to create gtp virtual interfaces that provide 265 the GPRS Tunneling Protocol datapath (GTP-U). This tunneling protocol 266 is used to prevent subscribers from accessing mobile carrier core 267 network infrastructure. This driver requires a userspace software that 268 implements the signaling protocol (GTP-C) to update its PDP context 269 base, such as OpenGGSN <http://git.osmocom.org/openggsn/). This 270 tunneling protocol is implemented according to the GSM TS 09.60 and 271 3GPP TS 29.060 standards. 272 273 To compile this drivers as a module, choose M here: the module 274 wil be called gtp. 275 276config MACSEC 277 tristate "IEEE 802.1AE MAC-level encryption (MACsec)" 278 select CRYPTO 279 select CRYPTO_AES 280 select CRYPTO_GCM 281 select GRO_CELLS 282 ---help--- 283 MACsec is an encryption standard for Ethernet. 284 285config NETCONSOLE 286 tristate "Network console logging support" 287 ---help--- 288 If you want to log kernel messages over the network, enable this. 289 See <file:Documentation/networking/netconsole.txt> for details. 290 291config NETCONSOLE_DYNAMIC 292 bool "Dynamic reconfiguration of logging targets" 293 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \ 294 !(NETCONSOLE=y && CONFIGFS_FS=m) 295 help 296 This option enables the ability to dynamically reconfigure target 297 parameters (interface, IP addresses, port numbers, MAC addresses) 298 at runtime through a userspace interface exported using configfs. 299 See <file:Documentation/networking/netconsole.txt> for details. 300 301config NETPOLL 302 def_bool NETCONSOLE 303 select SRCU 304 305config NET_POLL_CONTROLLER 306 def_bool NETPOLL 307 308config NTB_NETDEV 309 tristate "Virtual Ethernet over NTB Transport" 310 depends on NTB_TRANSPORT 311 312config RIONET 313 tristate "RapidIO Ethernet over messaging driver support" 314 depends on RAPIDIO 315 316config RIONET_TX_SIZE 317 int "Number of outbound queue entries" 318 depends on RIONET 319 default "128" 320 321config RIONET_RX_SIZE 322 int "Number of inbound queue entries" 323 depends on RIONET 324 default "128" 325 326config TUN 327 tristate "Universal TUN/TAP device driver support" 328 depends on INET 329 select CRC32 330 ---help--- 331 TUN/TAP provides packet reception and transmission for user space 332 programs. It can be viewed as a simple Point-to-Point or Ethernet 333 device, which instead of receiving packets from a physical media, 334 receives them from user space program and instead of sending packets 335 via physical media writes them to the user space program. 336 337 When a program opens /dev/net/tun, driver creates and registers 338 corresponding net device tunX or tapX. After a program closed above 339 devices, driver will automatically delete tunXX or tapXX device and 340 all routes corresponding to it. 341 342 Please read <file:Documentation/networking/tuntap.txt> for more 343 information. 344 345 To compile this driver as a module, choose M here: the module 346 will be called tun. 347 348 If you don't know what to use this for, you don't need it. 349 350config TAP 351 tristate 352 ---help--- 353 This option is selected by any driver implementing tap user space 354 interface for a virtual interface to re-use core tap functionality. 355 356config TUN_VNET_CROSS_LE 357 bool "Support for cross-endian vnet headers on little-endian kernels" 358 default n 359 ---help--- 360 This option allows TUN/TAP and MACVTAP device drivers in a 361 little-endian kernel to parse vnet headers that come from a 362 big-endian legacy virtio device. 363 364 Userspace programs can control the feature using the TUNSETVNETBE 365 and TUNGETVNETBE ioctls. 366 367 Unless you have a little-endian system hosting a big-endian virtual 368 machine with a legacy virtio NIC, you should say N. 369 370config VETH 371 tristate "Virtual ethernet pair device" 372 ---help--- 373 This device is a local ethernet tunnel. Devices are created in pairs. 374 When one end receives the packet it appears on its pair and vice 375 versa. 376 377config VIRTIO_NET 378 tristate "Virtio network driver" 379 depends on VIRTIO 380 select NET_FAILOVER 381 ---help--- 382 This is the virtual network driver for virtio. It can be used with 383 QEMU based VMMs (like KVM or Xen). Say Y or M. 384 385config NLMON 386 tristate "Virtual netlink monitoring device" 387 ---help--- 388 This option enables a monitoring net device for netlink skbs. The 389 purpose of this is to analyze netlink messages with packet sockets. 390 Thus applications like tcpdump will be able to see local netlink 391 messages if they tap into the netlink device, record pcaps for further 392 diagnostics, etc. This is mostly intended for developers or support 393 to debug netlink issues. If unsure, say N. 394 395config NET_VRF 396 tristate "Virtual Routing and Forwarding (Lite)" 397 depends on IP_MULTIPLE_TABLES 398 depends on NET_L3_MASTER_DEV 399 depends on IPV6 || IPV6=n 400 depends on IPV6_MULTIPLE_TABLES || IPV6=n 401 ---help--- 402 This option enables the support for mapping interfaces into VRF's. The 403 support enables VRF devices. 404 405config VSOCKMON 406 tristate "Virtual vsock monitoring device" 407 depends on VHOST_VSOCK 408 ---help--- 409 This option enables a monitoring net device for vsock sockets. It is 410 mostly intended for developers or support to debug vsock issues. If 411 unsure, say N. 412 413endif # NET_CORE 414 415config SUNGEM_PHY 416 tristate 417 418source "drivers/net/arcnet/Kconfig" 419 420source "drivers/atm/Kconfig" 421 422source "drivers/net/caif/Kconfig" 423 424source "drivers/net/dsa/Kconfig" 425 426source "drivers/net/ethernet/Kconfig" 427 428source "drivers/net/fddi/Kconfig" 429 430source "drivers/net/hippi/Kconfig" 431 432config NET_SB1000 433 tristate "General Instruments Surfboard 1000" 434 depends on PNP 435 ---help--- 436 This is a driver for the General Instrument (also known as 437 NextLevel) SURFboard 1000 internal 438 cable modem. This is an ISA card which is used by a number of cable 439 TV companies to provide cable modem access. It's a one-way 440 downstream-only cable modem, meaning that your upstream net link is 441 provided by your regular phone modem. 442 443 At present this driver only compiles as a module, so say M here if 444 you have this card. The module will be called sb1000. Then read 445 <file:Documentation/networking/device_drivers/sb1000.txt> for 446 information on how to use this module, as it needs special ppp 447 scripts for establishing a connection. Further documentation 448 and the necessary scripts can be found at: 449 450 <http://www.jacksonville.net/~fventuri/> 451 <http://home.adelphia.net/~siglercm/sb1000.html> 452 <http://linuxpower.cx/~cable/> 453 454 If you don't have this card, of course say N. 455 456source "drivers/net/phy/Kconfig" 457 458source "drivers/net/plip/Kconfig" 459 460source "drivers/net/ppp/Kconfig" 461 462source "drivers/net/slip/Kconfig" 463 464source "drivers/s390/net/Kconfig" 465 466source "drivers/net/usb/Kconfig" 467 468source "drivers/net/wireless/Kconfig" 469 470source "drivers/net/wimax/Kconfig" 471 472source "drivers/net/wan/Kconfig" 473 474source "drivers/net/ieee802154/Kconfig" 475 476config XEN_NETDEV_FRONTEND 477 tristate "Xen network device frontend driver" 478 depends on XEN 479 select XEN_XENBUS_FRONTEND 480 default y 481 help 482 This driver provides support for Xen paravirtual network 483 devices exported by a Xen network driver domain (often 484 domain 0). 485 486 The corresponding Linux backend driver is enabled by the 487 CONFIG_XEN_NETDEV_BACKEND option. 488 489 If you are compiling a kernel for use as Xen guest, you 490 should say Y here. To compile this driver as a module, chose 491 M here: the module will be called xen-netfront. 492 493config XEN_NETDEV_BACKEND 494 tristate "Xen backend network device" 495 depends on XEN_BACKEND 496 help 497 This driver allows the kernel to act as a Xen network driver 498 domain which exports paravirtual network devices to other 499 Xen domains. These devices can be accessed by any operating 500 system that implements a compatible front end. 501 502 The corresponding Linux frontend driver is enabled by the 503 CONFIG_XEN_NETDEV_FRONTEND configuration option. 504 505 The backend driver presents a standard network device 506 endpoint for each paravirtual network device to the driver 507 domain network stack. These can then be bridged or routed 508 etc in order to provide full network connectivity. 509 510 If you are compiling a kernel to run in a Xen network driver 511 domain (often this is domain 0) you should say Y here. To 512 compile this driver as a module, chose M here: the module 513 will be called xen-netback. 514 515config VMXNET3 516 tristate "VMware VMXNET3 ethernet driver" 517 depends on PCI && INET 518 depends on !(PAGE_SIZE_64KB || ARM64_64K_PAGES || \ 519 IA64_PAGE_SIZE_64KB || MICROBLAZE_64K_PAGES || \ 520 PARISC_PAGE_SIZE_64KB || PPC_64K_PAGES) 521 help 522 This driver supports VMware's vmxnet3 virtual ethernet NIC. 523 To compile this driver as a module, choose M here: the 524 module will be called vmxnet3. 525 526config FUJITSU_ES 527 tristate "FUJITSU Extended Socket Network Device driver" 528 depends on ACPI 529 help 530 This driver provides support for Extended Socket network device 531 on Extended Partitioning of FUJITSU PRIMEQUEST 2000 E2 series. 532 533config THUNDERBOLT_NET 534 tristate "Networking over Thunderbolt cable" 535 depends on THUNDERBOLT && INET 536 help 537 Select this if you want to create network between two 538 computers over a Thunderbolt cable. The driver supports Apple 539 ThunderboltIP protocol and allows communication with any host 540 supporting the same protocol including Windows and macOS. 541 542 To compile this driver a module, choose M here. The module will be 543 called thunderbolt-net. 544 545source "drivers/net/hyperv/Kconfig" 546 547config NETDEVSIM 548 tristate "Simulated networking device" 549 depends on DEBUG_FS 550 select NET_DEVLINK 551 help 552 This driver is a developer testing tool and software model that can 553 be used to test various control path networking APIs, especially 554 HW-offload related. 555 556 To compile this driver as a module, choose M here: the module 557 will be called netdevsim. 558 559config NET_FAILOVER 560 tristate "Failover driver" 561 select FAILOVER 562 help 563 This provides an automated failover mechanism via APIs to create 564 and destroy a failover master netdev and manages a primary and 565 standby slave netdevs that get registered via the generic failover 566 infrastructure. This can be used by paravirtual drivers to enable 567 an alternate low latency datapath. It also enables live migration of 568 a VM with direct attached VF by failing over to the paravirtual 569 datapath when the VF is unplugged. 570 571endif # NETDEVICES 572