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