672 lines · plain
1# SPDX-License-Identifier: GPL-2.0-only2#3# Network device configuration4#5 6menuconfig NETDEVICES7 default y if UML8 depends on NET9 bool "Network device support"10 help11 You can say N here if you don't intend to connect your Linux box to12 any other computer at all.13 14 You'll have to say Y if your computer contains a network card that15 you want to use under Linux. If you are going to run SLIP or PPP over16 telephone line or null modem cable you need say Y here. Connecting17 two machines with parallel ports using PLIP needs this, as well as18 AX.25/KISS for sending Internet traffic over amateur radio links.19 20 See also "The Linux Network Administrator's Guide" by Olaf Kirch and21 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 repeat26# that for each of the symbols.27if NETDEVICES28 29config MII30 tristate31 32config NET_CORE33 default y34 bool "Network core driver support"35 help36 You can say N here if you do not intend to use any of the37 networking core drivers (i.e. VLAN, bridging, bonding, etc.)38 39if NET_CORE40 41config BONDING42 tristate "Bonding driver support"43 depends on INET44 depends on IPV6 || IPV6=n45 depends on TLS || TLS_DEVICE=n46 help47 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet48 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 high52 performance and high availability operation.53 54 Refer to <file:Documentation/networking/bonding.rst> for more55 information.56 57 To compile this driver as a module, choose M here: the module58 will be called bonding.59 60config DUMMY61 tristate "Dummy net driver support"62 help63 This is essentially a bit-bucket device (i.e. traffic you send to64 this device is consigned into oblivion) with a configurable IP65 address. It is most commonly used in order to make your currently66 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't68 enlarge your kernel. What a deal. Read about it in the Network69 Administrator's Guide, available from70 <http://www.tldp.org/docs.html#guide>.71 72 To compile this driver as a module, choose M here: the module73 will be called dummy.74 75config WIREGUARD76 tristate "WireGuard secure network tunnel"77 depends on NET && INET78 depends on IPV6 || !IPV679 depends on !KMSAN # KMSAN doesn't support the crypto configs below80 select NET_UDP_TUNNEL81 select DST_CACHE82 select CRYPTO83 select CRYPTO_LIB_CURVE2551984 select CRYPTO_LIB_CHACHA20POLY130585 select CRYPTO_CHACHA20_X86_64 if X86 && 64BIT86 select CRYPTO_POLY1305_X86_64 if X86 && 64BIT87 select CRYPTO_BLAKE2S_X86 if X86 && 64BIT88 select CRYPTO_CURVE25519_X86 if X86 && 64BIT89 select CRYPTO_CHACHA20_NEON if ARM || (ARM64 && KERNEL_MODE_NEON)90 select CRYPTO_POLY1305_NEON if ARM64 && KERNEL_MODE_NEON91 select CRYPTO_POLY1305_ARM if ARM92 select CRYPTO_BLAKE2S_ARM if ARM93 select CRYPTO_CURVE25519_NEON if ARM && KERNEL_MODE_NEON94 select CRYPTO_CHACHA_MIPS if CPU_MIPS32_R295 select CRYPTO_POLY1305_MIPS if MIPS96 select CRYPTO_CHACHA_S390 if S39097 help98 WireGuard is a secure, fast, and easy to use replacement for IPSec99 that uses modern cryptography and clever networking tricks. It's100 designed to be fairly general purpose and abstract enough to fit most101 use cases, while at the same time remaining extremely simple to102 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 and105 is only in use when an administrator chooses to add an interface.106 107config WIREGUARD_DEBUG108 bool "Debugging checks and verbose messages"109 depends on WIREGUARD110 help111 This will write log messages for handshake and other events112 that occur for a WireGuard interface. It will also perform some113 extra validation checks and unit tests at various points. This is114 only useful for debugging.115 116 Say N here unless you know what you're doing.117 118config EQUALIZER119 tristate "EQL (serial line load balancing) support"120 help121 If you have two serial connections to some other computer (this122 usually requires two modems and two telephone lines) and you use123 SLIP (the protocol for sending Internet traffic over telephone124 lines) or PPP (a better SLIP) on them, you can make them behave like125 one double speed connection using this driver. Naturally, this has126 to be supported at the other end as well, either with a similar EQL127 Linux driver or with a Livingston Portmaster 2e.128 129 Say Y if you want this and read130 <file:Documentation/networking/eql.rst>. You may also want to read131 section 6.2 of the NET-3-HOWTO, available from132 <http://www.tldp.org/docs.html#howto>.133 134 To compile this driver as a module, choose M here: the module135 will be called eql. If unsure, say N.136 137config NET_FC138 bool "Fibre Channel driver support"139 depends on SCSI && PCI140 help141 Fibre Channel is a high speed serial protocol mainly used to connect142 large storage devices to the computer; it is compatible with and143 intended to replace SCSI.144 145 If you intend to use Fibre Channel, you need to have a Fibre channel146 adaptor card in your computer; say Y here and to the driver for your147 adaptor below. You also should have said Y to "SCSI support" and148 "SCSI generic support".149 150config IFB151 tristate "Intermediate Functional Block support"152 depends on NET_ACT_MIRRED || NFT_FWD_NETDEV153 select NET_REDIRECT154 help155 This is an intermediate driver that allows sharing of156 resources.157 To compile this driver as a module, choose M here: the module158 will be called ifb. If you want to use more than one ifb159 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 etc163 164source "drivers/net/team/Kconfig"165 166config MACVLAN167 tristate "MAC-VLAN support"168 help169 This allows one to create virtual interfaces that map packets to170 or from specific MAC addresses to a particular interface.171 172 Macvlan devices can be added using the "ip" command from the173 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 module178 will be called macvlan.179 180config MACVTAP181 tristate "MAC-VLAN based tap driver"182 depends on MACVLAN183 depends on INET184 select TAP185 help186 This adds a specialized tap character device driver that is based187 on the MAC-VLAN network interface, called macvtap. A macvtap device188 can be added in the same way as a macvlan device, using 'type189 macvtap', and then be accessed through the tap user space interface.190 191 To compile this driver as a module, choose M here: the module192 will be called macvtap.193 194config IPVLAN_L3S195 depends on NETFILTER196 depends on IPVLAN197 def_bool y198 select NET_L3_MASTER_DEV199 200config IPVLAN201 tristate "IP-VLAN support"202 depends on INET203 depends on IPV6 || !IPV6204 help205 This allows one to create virtual devices off of a main interface206 and packets will be delivered based on the dest L3 (IPv6/IPv4 addr)207 on packets. All interfaces (including the main interface) share L2208 making it transparent to the connected L2 switch.209 210 Ipvlan devices can be added using the "ip" command from the211 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 module216 will be called ipvlan.217 218config IPVTAP219 tristate "IP-VLAN based tap driver"220 depends on IPVLAN221 depends on INET222 select TAP223 help224 This adds a specialized tap character device driver that is based225 on the IP-VLAN network interface, called ipvtap. An ipvtap device226 can be added in the same way as a ipvlan device, using 'type227 ipvtap', and then be accessed through the tap user space interface.228 229 To compile this driver as a module, choose M here: the module230 will be called ipvtap.231 232config VXLAN233 tristate "Virtual eXtensible Local Area Network (VXLAN)"234 depends on INET235 select NET_UDP_TUNNEL236 select GRO_CELLS237 help238 This allows one to create vxlan virtual interfaces that provide239 Layer 2 Networks over Layer 3 Networks. VXLAN is often used240 to tunnel virtual network infrastructure in virtualized environments.241 For more information see:242 http://tools.ietf.org/html/draft-mahalingam-dutt-dcops-vxlan-02243 244 To compile this driver as a module, choose M here: the module245 will be called vxlan.246 247config GENEVE248 tristate "Generic Network Virtualization Encapsulation"249 depends on INET250 depends on IPV6 || !IPV6251 select NET_UDP_TUNNEL252 select GRO_CELLS253 help254 This allows one to create geneve virtual interfaces that provide255 Layer 2 Networks over Layer 3 Networks. GENEVE is often used256 to tunnel virtual network infrastructure in virtualized environments.257 For more information see:258 http://tools.ietf.org/html/draft-gross-geneve-02259 260 To compile this driver as a module, choose M here: the module261 will be called geneve.262 263config BAREUDP264 tristate "Bare UDP Encapsulation"265 depends on INET266 depends on IPV6 || !IPV6267 select NET_UDP_TUNNEL268 select GRO_CELLS269 help270 This adds a bare UDP tunnel module for tunnelling different271 kinds of traffic like MPLS, IP, etc. inside a UDP tunnel.272 273 To compile this driver as a module, choose M here: the module274 will be called bareudp.275 276config GTP277 tristate "GPRS Tunneling Protocol datapath (GTP-U)"278 depends on INET279 select NET_UDP_TUNNEL280 help281 This allows one to create gtp virtual interfaces that provide282 the GPRS Tunneling Protocol datapath (GTP-U). This tunneling protocol283 is used to prevent subscribers from accessing mobile carrier core284 network infrastructure. This driver requires a userspace software that285 implements the signaling protocol (GTP-C) to update its PDP context286 base, such as OpenGGSN <http://git.osmocom.org/openggsn/). This287 tunneling protocol is implemented according to the GSM TS 09.60 and288 3GPP TS 29.060 standards.289 290 To compile this drivers as a module, choose M here: the module291 will be called gtp.292 293config PFCP294 tristate "Packet Forwarding Control Protocol (PFCP)"295 depends on INET296 select NET_UDP_TUNNEL297 help298 This allows one to create PFCP virtual interfaces that allows to299 set up software and hardware offload of PFCP packets.300 Note that this module does not support PFCP protocol in the kernel space.301 There is no support for parsing any PFCP messages.302 303 To compile this drivers as a module, choose M here: the module304 will be called pfcp.305 306config AMT307 tristate "Automatic Multicast Tunneling (AMT)"308 depends on INET && IP_MULTICAST309 depends on IPV6 || !IPV6310 select NET_UDP_TUNNEL311 help312 This allows one to create AMT(Automatic Multicast Tunneling)313 virtual interfaces that provide multicast tunneling.314 There are two roles, Gateway, and Relay.315 Gateway Encapsulates IGMP/MLD traffic from listeners to the Relay.316 Gateway Decapsulates multicast traffic from the Relay to Listeners.317 Relay Encapsulates multicast traffic from Sources to Gateway.318 Relay Decapsulates IGMP/MLD traffic from Gateway.319 320 To compile this drivers as a module, choose M here: the module321 will be called amt.322 323config MACSEC324 tristate "IEEE 802.1AE MAC-level encryption (MACsec)"325 select CRYPTO326 select CRYPTO_AES327 select CRYPTO_GCM328 select GRO_CELLS329 help330 MACsec is an encryption standard for Ethernet.331 332config NETCONSOLE333 tristate "Network console logging support"334 help335 If you want to log kernel messages over the network, enable this.336 See <file:Documentation/networking/netconsole.rst> for details.337 338config NETCONSOLE_DYNAMIC339 bool "Dynamic reconfiguration of logging targets"340 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \341 !(NETCONSOLE=y && CONFIGFS_FS=m)342 help343 This option enables the ability to dynamically reconfigure target344 parameters (interface, IP addresses, port numbers, MAC addresses)345 at runtime through a userspace interface exported using configfs.346 See <file:Documentation/networking/netconsole.rst> for details.347 348config NETCONSOLE_EXTENDED_LOG349 bool "Set kernel extended message by default"350 depends on NETCONSOLE351 default n352 help353 Set extended log support for netconsole message. If this option is354 set, log messages are transmitted with extended metadata header in a355 format similar to /dev/kmsg. See356 <file:Documentation/networking/netconsole.rst> for details.357 358config NETCONSOLE_PREPEND_RELEASE359 bool "Prepend kernel release version in the message by default"360 depends on NETCONSOLE_EXTENDED_LOG361 default n362 help363 Set kernel release to be prepended to each netconsole message by364 default. If this option is set, the kernel release is prepended into365 the first field of every netconsole message, so, the netconsole366 server/peer can easily identify what kernel release is logging each367 message. See <file:Documentation/networking/netconsole.rst> for368 details.369 370config NETPOLL371 def_bool NETCONSOLE372 373config NET_POLL_CONTROLLER374 def_bool NETPOLL375 376config NTB_NETDEV377 tristate "Virtual Ethernet over NTB Transport"378 depends on NTB_TRANSPORT379 380config RIONET381 tristate "RapidIO Ethernet over messaging driver support"382 depends on RAPIDIO383 384config RIONET_TX_SIZE385 int "Number of outbound queue entries"386 depends on RIONET387 default "128"388 389config RIONET_RX_SIZE390 int "Number of inbound queue entries"391 depends on RIONET392 default "128"393 394config TUN395 tristate "Universal TUN/TAP device driver support"396 depends on INET397 select CRC32398 help399 TUN/TAP provides packet reception and transmission for user space400 programs. It can be viewed as a simple Point-to-Point or Ethernet401 device, which instead of receiving packets from a physical media,402 receives them from user space program and instead of sending packets403 via physical media writes them to the user space program.404 405 When a program opens /dev/net/tun, driver creates and registers406 corresponding net device tunX or tapX. After a program closed above407 devices, driver will automatically delete tunXX or tapXX device and408 all routes corresponding to it.409 410 Please read <file:Documentation/networking/tuntap.rst> for more411 information.412 413 To compile this driver as a module, choose M here: the module414 will be called tun.415 416 If you don't know what to use this for, you don't need it.417 418config TAP419 tristate420 help421 This option is selected by any driver implementing tap user space422 interface for a virtual interface to re-use core tap functionality.423 424config TUN_VNET_CROSS_LE425 bool "Support for cross-endian vnet headers on little-endian kernels"426 default n427 help428 This option allows TUN/TAP and MACVTAP device drivers in a429 little-endian kernel to parse vnet headers that come from a430 big-endian legacy virtio device.431 432 Userspace programs can control the feature using the TUNSETVNETBE433 and TUNGETVNETBE ioctls.434 435 Unless you have a little-endian system hosting a big-endian virtual436 machine with a legacy virtio NIC, you should say N.437 438config VETH439 tristate "Virtual ethernet pair device"440 select PAGE_POOL441 help442 This device is a local ethernet tunnel. Devices are created in pairs.443 When one end receives the packet it appears on its pair and vice444 versa.445 446config VIRTIO_NET447 tristate "Virtio network driver"448 depends on VIRTIO449 select NET_FAILOVER450 select DIMLIB451 help452 This is the virtual network driver for virtio. It can be used with453 QEMU based VMMs (like KVM or Xen). Say Y or M.454 455config NLMON456 tristate "Virtual netlink monitoring device"457 help458 This option enables a monitoring net device for netlink skbs. The459 purpose of this is to analyze netlink messages with packet sockets.460 Thus applications like tcpdump will be able to see local netlink461 messages if they tap into the netlink device, record pcaps for further462 diagnostics, etc. This is mostly intended for developers or support463 to debug netlink issues. If unsure, say N.464 465config NETKIT466 bool "BPF-programmable network device"467 depends on BPF_SYSCALL468 help469 The netkit device is a virtual networking device where BPF programs470 can be attached to the device(s) transmission routine in order to471 implement the driver's internal logic. The device can be configured472 to operate in L3 or L2 mode. If unsure, say N.473 474config NET_VRF475 tristate "Virtual Routing and Forwarding (Lite)"476 depends on IP_MULTIPLE_TABLES477 depends on NET_L3_MASTER_DEV478 depends on IPV6 || IPV6=n479 depends on IPV6_MULTIPLE_TABLES || IPV6=n480 help481 This option enables the support for mapping interfaces into VRF's. The482 support enables VRF devices.483 484config VSOCKMON485 tristate "Virtual vsock monitoring device"486 depends on VHOST_VSOCK487 help488 This option enables a monitoring net device for vsock sockets. It is489 mostly intended for developers or support to debug vsock issues. If490 unsure, say N.491 492config MHI_NET493 tristate "MHI network driver"494 depends on MHI_BUS495 help496 This is the network driver for MHI bus. It can be used with497 QCOM based WWAN modems for IP or QMAP/rmnet protocol (like SDX55).498 Say Y or M.499 500endif # NET_CORE501 502config SUNGEM_PHY503 tristate504 505source "drivers/net/arcnet/Kconfig"506 507source "drivers/atm/Kconfig"508 509source "drivers/net/caif/Kconfig"510 511source "drivers/net/dsa/Kconfig"512 513source "drivers/net/ethernet/Kconfig"514 515source "drivers/net/fddi/Kconfig"516 517source "drivers/net/hippi/Kconfig"518 519source "drivers/net/ipa/Kconfig"520 521config NET_SB1000522 tristate "General Instruments Surfboard 1000"523 depends on ISA && PNP524 help525 This is a driver for the General Instrument (also known as526 NextLevel) SURFboard 1000 internal527 cable modem. This is an ISA card which is used by a number of cable528 TV companies to provide cable modem access. It's a one-way529 downstream-only cable modem, meaning that your upstream net link is530 provided by your regular phone modem.531 532 At present this driver only compiles as a module, so say M here if533 you have this card. The module will be called sb1000. Then read534 <file:Documentation/networking/device_drivers/cable/sb1000.rst> for535 information on how to use this module, as it needs special ppp536 scripts for establishing a connection. Further documentation537 and the necessary scripts can be found at:538 539 <http://www.jacksonville.net/~fventuri/>540 <http://home.adelphia.net/~siglercm/sb1000.html>541 <http://linuxpower.cx/~cable/>542 543 If you don't have this card, of course say N.544 545source "drivers/net/phy/Kconfig"546 547source "drivers/net/pse-pd/Kconfig"548 549source "drivers/net/can/Kconfig"550 551source "drivers/net/mctp/Kconfig"552 553source "drivers/net/mdio/Kconfig"554 555source "drivers/net/pcs/Kconfig"556 557source "drivers/net/plip/Kconfig"558 559source "drivers/net/ppp/Kconfig"560 561source "drivers/net/slip/Kconfig"562 563source "drivers/s390/net/Kconfig"564 565source "drivers/net/usb/Kconfig"566 567source "drivers/net/wireless/Kconfig"568 569source "drivers/net/wan/Kconfig"570 571source "drivers/net/ieee802154/Kconfig"572 573source "drivers/net/wwan/Kconfig"574 575config XEN_NETDEV_FRONTEND576 tristate "Xen network device frontend driver"577 depends on XEN578 select XEN_XENBUS_FRONTEND579 select PAGE_POOL580 default y581 help582 This driver provides support for Xen paravirtual network583 devices exported by a Xen network driver domain (often584 domain 0).585 586 The corresponding Linux backend driver is enabled by the587 CONFIG_XEN_NETDEV_BACKEND option.588 589 If you are compiling a kernel for use as Xen guest, you590 should say Y here. To compile this driver as a module, chose591 M here: the module will be called xen-netfront.592 593config XEN_NETDEV_BACKEND594 tristate "Xen backend network device"595 depends on XEN_BACKEND596 help597 This driver allows the kernel to act as a Xen network driver598 domain which exports paravirtual network devices to other599 Xen domains. These devices can be accessed by any operating600 system that implements a compatible front end.601 602 The corresponding Linux frontend driver is enabled by the603 CONFIG_XEN_NETDEV_FRONTEND configuration option.604 605 The backend driver presents a standard network device606 endpoint for each paravirtual network device to the driver607 domain network stack. These can then be bridged or routed608 etc in order to provide full network connectivity.609 610 If you are compiling a kernel to run in a Xen network driver611 domain (often this is domain 0) you should say Y here. To612 compile this driver as a module, chose M here: the module613 will be called xen-netback.614 615config VMXNET3616 tristate "VMware VMXNET3 ethernet driver"617 depends on PCI && INET618 depends on PAGE_SIZE_LESS_THAN_64KB619 select PAGE_POOL620 help621 This driver supports VMware's vmxnet3 virtual ethernet NIC.622 To compile this driver as a module, choose M here: the623 module will be called vmxnet3.624 625config FUJITSU_ES626 tristate "FUJITSU Extended Socket Network Device driver"627 depends on ACPI628 help629 This driver provides support for Extended Socket network device630 on Extended Partitioning of FUJITSU PRIMEQUEST 2000 E2 series.631 632source "drivers/net/thunderbolt/Kconfig"633source "drivers/net/hyperv/Kconfig"634 635config NETDEVSIM636 tristate "Simulated networking device"637 depends on DEBUG_FS638 depends on INET639 depends on IPV6 || IPV6=n640 depends on PSAMPLE || PSAMPLE=n641 depends on PTP_1588_CLOCK_MOCK || PTP_1588_CLOCK_MOCK=n642 select NET_DEVLINK643 select PAGE_POOL644 help645 This driver is a developer testing tool and software model that can646 be used to test various control path networking APIs, especially647 HW-offload related.648 649 To compile this driver as a module, choose M here: the module650 will be called netdevsim.651 652config NET_FAILOVER653 tristate "Failover driver"654 select FAILOVER655 help656 This provides an automated failover mechanism via APIs to create657 and destroy a failover master netdev and manages a primary and658 standby slave netdevs that get registered via the generic failover659 infrastructure. This can be used by paravirtual drivers to enable660 an alternate low latency datapath. It also enables live migration of661 a VM with direct attached VF by failing over to the paravirtual662 datapath when the VF is unplugged.663 664config NETDEV_LEGACY_INIT665 bool666 depends on ISA667 help668 Drivers that call netdev_boot_setup_check() should select this669 symbol, everything else no longer needs it.670 671endif # NETDEVICES672