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