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