1 # SPDX-License-Identifier: GPL-2.0-only
3 # Network device configuration
9 bool "Network device support"
11 You can say N here if you don't intend to connect your Linux box to
12 any other computer at all.
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.
20 See also "The Linux Network Administrator's Guide" by Olaf Kirch and
21 Terry Dawson. Available at <http://www.tldp.org/guides.html>.
25 # All the following symbols are dependent on NETDEVICES - do not repeat
26 # that for each of the symbols.
34 bool "Network core driver support"
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.)
42 tristate "Bonding driver support"
44 depends on IPV6 || IPV6=n
45 depends on TLS || TLS_DEVICE=n
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.
51 The driver supports multiple bonding modes to allow for both high
52 performance and high availability operation.
54 Refer to <file:Documentation/networking/bonding.rst> for more
57 To compile this driver as a module, choose M here: the module
58 will be called bonding.
61 tristate "Dummy net driver support"
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>.
72 To compile this driver as a module, choose M here: the module
76 tristate "WireGuard secure network tunnel"
77 depends on NET && INET
78 depends on IPV6 || !IPV6
79 depends on !KMSAN # KMSAN doesn't support the crypto configs below
83 select CRYPTO_LIB_CURVE25519
84 select CRYPTO_LIB_CHACHA20POLY1305
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 CRYPTO_CHACHA20_NEON if ARM || (ARM64 && KERNEL_MODE_NEON)
90 select CRYPTO_POLY1305_NEON if ARM64 && KERNEL_MODE_NEON
91 select CRYPTO_POLY1305_ARM if ARM
92 select CRYPTO_BLAKE2S_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 MIPS
96 select CRYPTO_CHACHA_S390 if S390
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.
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.
107 config WIREGUARD_DEBUG
108 bool "Debugging checks and verbose messages"
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.
116 Say N here unless you know what you're doing.
119 tristate "EQL (serial line load balancing) support"
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.
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>.
134 To compile this driver as a module, choose M here: the module
135 will be called eql. If unsure, say N.
138 bool "Fibre Channel driver support"
139 depends on SCSI && PCI
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.
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".
151 tristate "Intermediate Functional Block support"
152 depends on NET_ACT_MIRRED || NFT_FWD_NETDEV
155 This is an intermediate driver that allows sharing of
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',
162 Look at the iproute2 documentation directory for usage etc
164 source "drivers/net/team/Kconfig"
167 tristate "MAC-VLAN support"
169 This allows one to create virtual interfaces that map packets to
170 or from specific MAC addresses to a particular interface.
172 Macvlan devices can be added using the "ip" command from the
173 iproute2 package starting with the iproute2-2.6.23 release:
175 "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
177 To compile this driver as a module, choose M here: the module
178 will be called macvlan.
181 tristate "MAC-VLAN based tap driver"
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.
191 To compile this driver as a module, choose M here: the module
192 will be called macvtap.
198 select NET_L3_MASTER_DEV
201 tristate "IP-VLAN support"
203 depends on IPV6 || !IPV6
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.
210 Ipvlan devices can be added using the "ip" command from the
211 iproute2 package starting with the iproute2-3.19 release:
213 "ip link add link <main-dev> [ NAME ] type ipvlan"
215 To compile this driver as a module, choose M here: the module
216 will be called ipvlan.
219 tristate "IP-VLAN based tap driver"
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.
229 To compile this driver as a module, choose M here: the module
230 will be called ipvtap.
233 tristate "Virtual eXtensible Local Area Network (VXLAN)"
235 select NET_UDP_TUNNEL
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
244 To compile this driver as a module, choose M here: the module
245 will be called vxlan.
248 tristate "Generic Network Virtualization Encapsulation"
250 depends on IPV6 || !IPV6
251 select NET_UDP_TUNNEL
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
260 To compile this driver as a module, choose M here: the module
261 will be called geneve.
264 tristate "Bare UDP Encapsulation"
266 depends on IPV6 || !IPV6
267 select NET_UDP_TUNNEL
270 This adds a bare UDP tunnel module for tunnelling different
271 kinds of traffic like MPLS, IP, etc. inside a UDP tunnel.
273 To compile this driver as a module, choose M here: the module
274 will be called bareudp.
277 tristate "GPRS Tunneling Protocol datapath (GTP-U)"
279 select NET_UDP_TUNNEL
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.
290 To compile this drivers as a module, choose M here: the module
294 tristate "Automatic Multicast Tunneling (AMT)"
295 depends on INET && IP_MULTICAST
296 depends on IPV6 || !IPV6
297 select NET_UDP_TUNNEL
299 This allows one to create AMT(Automatic Multicast Tunneling)
300 virtual interfaces that provide multicast tunneling.
301 There are two roles, Gateway, and Relay.
302 Gateway Encapsulates IGMP/MLD traffic from listeners to the Relay.
303 Gateway Decapsulates multicast traffic from the Relay to Listeners.
304 Relay Encapsulates multicast traffic from Sources to Gateway.
305 Relay Decapsulates IGMP/MLD traffic from Gateway.
307 To compile this drivers as a module, choose M here: the module
311 tristate "IEEE 802.1AE MAC-level encryption (MACsec)"
317 MACsec is an encryption standard for Ethernet.
320 tristate "Network console logging support"
322 If you want to log kernel messages over the network, enable this.
323 See <file:Documentation/networking/netconsole.rst> for details.
325 config NETCONSOLE_DYNAMIC
326 bool "Dynamic reconfiguration of logging targets"
327 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
328 !(NETCONSOLE=y && CONFIGFS_FS=m)
330 This option enables the ability to dynamically reconfigure target
331 parameters (interface, IP addresses, port numbers, MAC addresses)
332 at runtime through a userspace interface exported using configfs.
333 See <file:Documentation/networking/netconsole.rst> for details.
335 config NETCONSOLE_EXTENDED_LOG
336 bool "Set kernel extended message by default"
337 depends on NETCONSOLE
340 Set extended log support for netconsole message. If this option is
341 set, log messages are transmitted with extended metadata header in a
342 format similar to /dev/kmsg. See
343 <file:Documentation/networking/netconsole.rst> for details.
345 config NETCONSOLE_PREPEND_RELEASE
346 bool "Prepend kernel release version in the message by default"
347 depends on NETCONSOLE_EXTENDED_LOG
350 Set kernel release to be prepended to each netconsole message by
351 default. If this option is set, the kernel release is prepended into
352 the first field of every netconsole message, so, the netconsole
353 server/peer can easily identify what kernel release is logging each
354 message. See <file:Documentation/networking/netconsole.rst> for
360 config NET_POLL_CONTROLLER
364 tristate "Virtual Ethernet over NTB Transport"
365 depends on NTB_TRANSPORT
368 tristate "RapidIO Ethernet over messaging driver support"
371 config RIONET_TX_SIZE
372 int "Number of outbound queue entries"
376 config RIONET_RX_SIZE
377 int "Number of inbound queue entries"
382 tristate "Universal TUN/TAP device driver support"
386 TUN/TAP provides packet reception and transmission for user space
387 programs. It can be viewed as a simple Point-to-Point or Ethernet
388 device, which instead of receiving packets from a physical media,
389 receives them from user space program and instead of sending packets
390 via physical media writes them to the user space program.
392 When a program opens /dev/net/tun, driver creates and registers
393 corresponding net device tunX or tapX. After a program closed above
394 devices, driver will automatically delete tunXX or tapXX device and
395 all routes corresponding to it.
397 Please read <file:Documentation/networking/tuntap.rst> for more
400 To compile this driver as a module, choose M here: the module
403 If you don't know what to use this for, you don't need it.
408 This option is selected by any driver implementing tap user space
409 interface for a virtual interface to re-use core tap functionality.
411 config TUN_VNET_CROSS_LE
412 bool "Support for cross-endian vnet headers on little-endian kernels"
415 This option allows TUN/TAP and MACVTAP device drivers in a
416 little-endian kernel to parse vnet headers that come from a
417 big-endian legacy virtio device.
419 Userspace programs can control the feature using the TUNSETVNETBE
420 and TUNGETVNETBE ioctls.
422 Unless you have a little-endian system hosting a big-endian virtual
423 machine with a legacy virtio NIC, you should say N.
426 tristate "Virtual ethernet pair device"
429 This device is a local ethernet tunnel. Devices are created in pairs.
430 When one end receives the packet it appears on its pair and vice
434 tristate "Virtio network driver"
439 This is the virtual network driver for virtio. It can be used with
440 QEMU based VMMs (like KVM or Xen). Say Y or M.
443 tristate "Virtual netlink monitoring device"
445 This option enables a monitoring net device for netlink skbs. The
446 purpose of this is to analyze netlink messages with packet sockets.
447 Thus applications like tcpdump will be able to see local netlink
448 messages if they tap into the netlink device, record pcaps for further
449 diagnostics, etc. This is mostly intended for developers or support
450 to debug netlink issues. If unsure, say N.
453 bool "BPF-programmable network device"
454 depends on BPF_SYSCALL
456 The netkit device is a virtual networking device where BPF programs
457 can be attached to the device(s) transmission routine in order to
458 implement the driver's internal logic. The device can be configured
459 to operate in L3 or L2 mode. If unsure, say N.
462 tristate "Virtual Routing and Forwarding (Lite)"
463 depends on IP_MULTIPLE_TABLES
464 depends on NET_L3_MASTER_DEV
465 depends on IPV6 || IPV6=n
466 depends on IPV6_MULTIPLE_TABLES || IPV6=n
468 This option enables the support for mapping interfaces into VRF's. The
469 support enables VRF devices.
472 tristate "Virtual vsock monitoring device"
473 depends on VHOST_VSOCK
475 This option enables a monitoring net device for vsock sockets. It is
476 mostly intended for developers or support to debug vsock issues. If
480 tristate "MHI network driver"
483 This is the network driver for MHI bus. It can be used with
484 QCOM based WWAN modems for IP or QMAP/rmnet protocol (like SDX55).
492 source "drivers/net/arcnet/Kconfig"
494 source "drivers/atm/Kconfig"
496 source "drivers/net/caif/Kconfig"
498 source "drivers/net/dsa/Kconfig"
500 source "drivers/net/ethernet/Kconfig"
502 source "drivers/net/fddi/Kconfig"
504 source "drivers/net/hippi/Kconfig"
506 source "drivers/net/ipa/Kconfig"
509 tristate "General Instruments Surfboard 1000"
512 This is a driver for the General Instrument (also known as
513 NextLevel) SURFboard 1000 internal
514 cable modem. This is an ISA card which is used by a number of cable
515 TV companies to provide cable modem access. It's a one-way
516 downstream-only cable modem, meaning that your upstream net link is
517 provided by your regular phone modem.
519 At present this driver only compiles as a module, so say M here if
520 you have this card. The module will be called sb1000. Then read
521 <file:Documentation/networking/device_drivers/cable/sb1000.rst> for
522 information on how to use this module, as it needs special ppp
523 scripts for establishing a connection. Further documentation
524 and the necessary scripts can be found at:
526 <http://www.jacksonville.net/~fventuri/>
527 <http://home.adelphia.net/~siglercm/sb1000.html>
528 <http://linuxpower.cx/~cable/>
530 If you don't have this card, of course say N.
532 source "drivers/net/phy/Kconfig"
534 source "drivers/net/pse-pd/Kconfig"
536 source "drivers/net/can/Kconfig"
538 source "drivers/net/mctp/Kconfig"
540 source "drivers/net/mdio/Kconfig"
542 source "drivers/net/pcs/Kconfig"
544 source "drivers/net/plip/Kconfig"
546 source "drivers/net/ppp/Kconfig"
548 source "drivers/net/slip/Kconfig"
550 source "drivers/s390/net/Kconfig"
552 source "drivers/net/usb/Kconfig"
554 source "drivers/net/wireless/Kconfig"
556 source "drivers/net/wan/Kconfig"
558 source "drivers/net/ieee802154/Kconfig"
560 source "drivers/net/wwan/Kconfig"
562 config XEN_NETDEV_FRONTEND
563 tristate "Xen network device frontend driver"
565 select XEN_XENBUS_FRONTEND
569 This driver provides support for Xen paravirtual network
570 devices exported by a Xen network driver domain (often
573 The corresponding Linux backend driver is enabled by the
574 CONFIG_XEN_NETDEV_BACKEND option.
576 If you are compiling a kernel for use as Xen guest, you
577 should say Y here. To compile this driver as a module, chose
578 M here: the module will be called xen-netfront.
580 config XEN_NETDEV_BACKEND
581 tristate "Xen backend network device"
582 depends on XEN_BACKEND
584 This driver allows the kernel to act as a Xen network driver
585 domain which exports paravirtual network devices to other
586 Xen domains. These devices can be accessed by any operating
587 system that implements a compatible front end.
589 The corresponding Linux frontend driver is enabled by the
590 CONFIG_XEN_NETDEV_FRONTEND configuration option.
592 The backend driver presents a standard network device
593 endpoint for each paravirtual network device to the driver
594 domain network stack. These can then be bridged or routed
595 etc in order to provide full network connectivity.
597 If you are compiling a kernel to run in a Xen network driver
598 domain (often this is domain 0) you should say Y here. To
599 compile this driver as a module, chose M here: the module
600 will be called xen-netback.
603 tristate "VMware VMXNET3 ethernet driver"
604 depends on PCI && INET
605 depends on PAGE_SIZE_LESS_THAN_64KB
608 This driver supports VMware's vmxnet3 virtual ethernet NIC.
609 To compile this driver as a module, choose M here: the
610 module will be called vmxnet3.
613 tristate "FUJITSU Extended Socket Network Device driver"
616 This driver provides support for Extended Socket network device
617 on Extended Partitioning of FUJITSU PRIMEQUEST 2000 E2 series.
619 source "drivers/net/thunderbolt/Kconfig"
620 source "drivers/net/hyperv/Kconfig"
623 tristate "Simulated networking device"
626 depends on IPV6 || IPV6=n
627 depends on PSAMPLE || PSAMPLE=n
628 depends on PTP_1588_CLOCK_MOCK || PTP_1588_CLOCK_MOCK=n
631 This driver is a developer testing tool and software model that can
632 be used to test various control path networking APIs, especially
635 To compile this driver as a module, choose M here: the module
636 will be called netdevsim.
639 tristate "Failover driver"
642 This provides an automated failover mechanism via APIs to create
643 and destroy a failover master netdev and manages a primary and
644 standby slave netdevs that get registered via the generic failover
645 infrastructure. This can be used by paravirtual drivers to enable
646 an alternate low latency datapath. It also enables live migration of
647 a VM with direct attached VF by failing over to the paravirtual
648 datapath when the VF is unplugged.
650 config NETDEV_LEGACY_INIT
654 Drivers that call netdev_boot_setup_check() should select this
655 symbol, everything else no longer needs it.