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
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.
50 The driver supports multiple bonding modes to allow for both high
51 performance and high availability operation.
53 Refer to <file:Documentation/networking/bonding.txt> for more
56 To compile this driver as a module, choose M here: the module
57 will be called bonding.
60 tristate "Dummy net driver support"
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>.
71 To compile this driver as a module, choose M here: the module
75 tristate "EQL (serial line load balancing) support"
77 If you have two serial connections to some other computer (this
78 usually requires two modems and two telephone lines) and you use
79 SLIP (the protocol for sending Internet traffic over telephone
80 lines) or PPP (a better SLIP) on them, you can make them behave like
81 one double speed connection using this driver. Naturally, this has
82 to be supported at the other end as well, either with a similar EQL
83 Linux driver or with a Livingston Portmaster 2e.
85 Say Y if you want this and read
86 <file:Documentation/networking/eql.txt>. You may also want to read
87 section 6.2 of the NET-3-HOWTO, available from
88 <http://www.tldp.org/docs.html#howto>.
90 To compile this driver as a module, choose M here: the module
91 will be called eql. If unsure, say N.
94 bool "Fibre Channel driver support"
95 depends on SCSI && PCI
97 Fibre Channel is a high speed serial protocol mainly used to connect
98 large storage devices to the computer; it is compatible with and
99 intended to replace SCSI.
101 If you intend to use Fibre Channel, you need to have a Fibre channel
102 adaptor card in your computer; say Y here and to the driver for your
103 adaptor below. You also should have said Y to "SCSI support" and
104 "SCSI generic support".
107 tristate "Intermediate Functional Block support"
108 depends on NET_CLS_ACT
111 This is an intermediate driver that allows sharing of
113 To compile this driver as a module, choose M here: the module
114 will be called ifb. If you want to use more than one ifb
115 device at a time, you need to compile this driver as a module.
116 Instead of 'ifb', the devices will then be called 'ifb0',
118 Look at the iproute2 documentation directory for usage etc
120 source "drivers/net/team/Kconfig"
123 tristate "MAC-VLAN support"
125 This allows one to create virtual interfaces that map packets to
126 or from specific MAC addresses to a particular interface.
128 Macvlan devices can be added using the "ip" command from the
129 iproute2 package starting with the iproute2-2.6.23 release:
131 "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
133 To compile this driver as a module, choose M here: the module
134 will be called macvlan.
137 tristate "MAC-VLAN based tap driver"
142 This adds a specialized tap character device driver that is based
143 on the MAC-VLAN network interface, called macvtap. A macvtap device
144 can be added in the same way as a macvlan device, using 'type
145 macvtap', and then be accessed through the tap user space interface.
147 To compile this driver as a module, choose M here: the module
148 will be called macvtap.
154 select NET_L3_MASTER_DEV
157 tristate "IP-VLAN support"
159 depends on IPV6 || !IPV6
161 This allows one to create virtual devices off of a main interface
162 and packets will be delivered based on the dest L3 (IPv6/IPv4 addr)
163 on packets. All interfaces (including the main interface) share L2
164 making it transparent to the connected L2 switch.
166 Ipvlan devices can be added using the "ip" command from the
167 iproute2 package starting with the iproute2-3.19 release:
169 "ip link add link <main-dev> [ NAME ] type ipvlan"
171 To compile this driver as a module, choose M here: the module
172 will be called ipvlan.
175 tristate "IP-VLAN based tap driver"
180 This adds a specialized tap character device driver that is based
181 on the IP-VLAN network interface, called ipvtap. An ipvtap device
182 can be added in the same way as a ipvlan device, using 'type
183 ipvtap', and then be accessed through the tap user space interface.
185 To compile this driver as a module, choose M here: the module
186 will be called ipvtap.
189 tristate "Virtual eXtensible Local Area Network (VXLAN)"
191 select NET_UDP_TUNNEL
194 This allows one to create vxlan virtual interfaces that provide
195 Layer 2 Networks over Layer 3 Networks. VXLAN is often used
196 to tunnel virtual network infrastructure in virtualized environments.
197 For more information see:
198 http://tools.ietf.org/html/draft-mahalingam-dutt-dcops-vxlan-02
200 To compile this driver as a module, choose M here: the module
201 will be called vxlan.
204 tristate "Generic Network Virtualization Encapsulation"
206 depends on IPV6 || !IPV6
207 select NET_UDP_TUNNEL
210 This allows one to create geneve virtual interfaces that provide
211 Layer 2 Networks over Layer 3 Networks. GENEVE is often used
212 to tunnel virtual network infrastructure in virtualized environments.
213 For more information see:
214 http://tools.ietf.org/html/draft-gross-geneve-02
216 To compile this driver as a module, choose M here: the module
217 will be called geneve.
220 tristate "GPRS Tunneling Protocol datapath (GTP-U)"
222 select NET_UDP_TUNNEL
224 This allows one to create gtp virtual interfaces that provide
225 the GPRS Tunneling Protocol datapath (GTP-U). This tunneling protocol
226 is used to prevent subscribers from accessing mobile carrier core
227 network infrastructure. This driver requires a userspace software that
228 implements the signaling protocol (GTP-C) to update its PDP context
229 base, such as OpenGGSN <http://git.osmocom.org/openggsn/). This
230 tunneling protocol is implemented according to the GSM TS 09.60 and
231 3GPP TS 29.060 standards.
233 To compile this drivers as a module, choose M here: the module
237 tristate "IEEE 802.1AE MAC-level encryption (MACsec)"
243 MACsec is an encryption standard for Ethernet.
246 tristate "Network console logging support"
248 If you want to log kernel messages over the network, enable this.
249 See <file:Documentation/networking/netconsole.txt> for details.
251 config NETCONSOLE_DYNAMIC
252 bool "Dynamic reconfiguration of logging targets"
253 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
254 !(NETCONSOLE=y && CONFIGFS_FS=m)
256 This option enables the ability to dynamically reconfigure target
257 parameters (interface, IP addresses, port numbers, MAC addresses)
258 at runtime through a userspace interface exported using configfs.
259 See <file:Documentation/networking/netconsole.txt> for details.
265 config NET_POLL_CONTROLLER
269 tristate "Virtual Ethernet over NTB Transport"
270 depends on NTB_TRANSPORT
273 tristate "RapidIO Ethernet over messaging driver support"
276 config RIONET_TX_SIZE
277 int "Number of outbound queue entries"
281 config RIONET_RX_SIZE
282 int "Number of inbound queue entries"
287 tristate "Universal TUN/TAP device driver support"
291 TUN/TAP provides packet reception and transmission for user space
292 programs. It can be viewed as a simple Point-to-Point or Ethernet
293 device, which instead of receiving packets from a physical media,
294 receives them from user space program and instead of sending packets
295 via physical media writes them to the user space program.
297 When a program opens /dev/net/tun, driver creates and registers
298 corresponding net device tunX or tapX. After a program closed above
299 devices, driver will automatically delete tunXX or tapXX device and
300 all routes corresponding to it.
302 Please read <file:Documentation/networking/tuntap.txt> for more
305 To compile this driver as a module, choose M here: the module
308 If you don't know what to use this for, you don't need it.
313 This option is selected by any driver implementing tap user space
314 interface for a virtual interface to re-use core tap functionality.
316 config TUN_VNET_CROSS_LE
317 bool "Support for cross-endian vnet headers on little-endian kernels"
320 This option allows TUN/TAP and MACVTAP device drivers in a
321 little-endian kernel to parse vnet headers that come from a
322 big-endian legacy virtio device.
324 Userspace programs can control the feature using the TUNSETVNETBE
325 and TUNGETVNETBE ioctls.
327 Unless you have a little-endian system hosting a big-endian virtual
328 machine with a legacy virtio NIC, you should say N.
331 tristate "Virtual ethernet pair device"
333 This device is a local ethernet tunnel. Devices are created in pairs.
334 When one end receives the packet it appears on its pair and vice
338 tristate "Virtio network driver"
342 This is the virtual network driver for virtio. It can be used with
343 QEMU based VMMs (like KVM or Xen). Say Y or M.
346 tristate "Virtual netlink monitoring device"
348 This option enables a monitoring net device for netlink skbs. The
349 purpose of this is to analyze netlink messages with packet sockets.
350 Thus applications like tcpdump will be able to see local netlink
351 messages if they tap into the netlink device, record pcaps for further
352 diagnostics, etc. This is mostly intended for developers or support
353 to debug netlink issues. If unsure, say N.
356 tristate "Virtual Routing and Forwarding (Lite)"
357 depends on IP_MULTIPLE_TABLES
358 depends on NET_L3_MASTER_DEV
359 depends on IPV6 || IPV6=n
360 depends on IPV6_MULTIPLE_TABLES || IPV6=n
362 This option enables the support for mapping interfaces into VRF's. The
363 support enables VRF devices.
366 tristate "Virtual vsock monitoring device"
367 depends on VHOST_VSOCK
369 This option enables a monitoring net device for vsock sockets. It is
370 mostly intended for developers or support to debug vsock issues. If
378 source "drivers/net/arcnet/Kconfig"
380 source "drivers/atm/Kconfig"
382 source "drivers/net/caif/Kconfig"
384 source "drivers/net/dsa/Kconfig"
386 source "drivers/net/ethernet/Kconfig"
388 source "drivers/net/fddi/Kconfig"
390 source "drivers/net/hippi/Kconfig"
393 tristate "General Instruments Surfboard 1000"
396 This is a driver for the General Instrument (also known as
397 NextLevel) SURFboard 1000 internal
398 cable modem. This is an ISA card which is used by a number of cable
399 TV companies to provide cable modem access. It's a one-way
400 downstream-only cable modem, meaning that your upstream net link is
401 provided by your regular phone modem.
403 At present this driver only compiles as a module, so say M here if
404 you have this card. The module will be called sb1000. Then read
405 <file:Documentation/networking/device_drivers/sb1000.txt> for
406 information on how to use this module, as it needs special ppp
407 scripts for establishing a connection. Further documentation
408 and the necessary scripts can be found at:
410 <http://www.jacksonville.net/~fventuri/>
411 <http://home.adelphia.net/~siglercm/sb1000.html>
412 <http://linuxpower.cx/~cable/>
414 If you don't have this card, of course say N.
416 source "drivers/net/phy/Kconfig"
418 source "drivers/net/plip/Kconfig"
420 source "drivers/net/ppp/Kconfig"
422 source "drivers/net/slip/Kconfig"
424 source "drivers/s390/net/Kconfig"
426 source "drivers/net/usb/Kconfig"
428 source "drivers/net/wireless/Kconfig"
430 source "drivers/net/wimax/Kconfig"
432 source "drivers/net/wan/Kconfig"
434 source "drivers/net/ieee802154/Kconfig"
436 config XEN_NETDEV_FRONTEND
437 tristate "Xen network device frontend driver"
439 select XEN_XENBUS_FRONTEND
442 This driver provides support for Xen paravirtual network
443 devices exported by a Xen network driver domain (often
446 The corresponding Linux backend driver is enabled by the
447 CONFIG_XEN_NETDEV_BACKEND option.
449 If you are compiling a kernel for use as Xen guest, you
450 should say Y here. To compile this driver as a module, chose
451 M here: the module will be called xen-netfront.
453 config XEN_NETDEV_BACKEND
454 tristate "Xen backend network device"
455 depends on XEN_BACKEND
457 This driver allows the kernel to act as a Xen network driver
458 domain which exports paravirtual network devices to other
459 Xen domains. These devices can be accessed by any operating
460 system that implements a compatible front end.
462 The corresponding Linux frontend driver is enabled by the
463 CONFIG_XEN_NETDEV_FRONTEND configuration option.
465 The backend driver presents a standard network device
466 endpoint for each paravirtual network device to the driver
467 domain network stack. These can then be bridged or routed
468 etc in order to provide full network connectivity.
470 If you are compiling a kernel to run in a Xen network driver
471 domain (often this is domain 0) you should say Y here. To
472 compile this driver as a module, chose M here: the module
473 will be called xen-netback.
476 tristate "VMware VMXNET3 ethernet driver"
477 depends on PCI && INET
478 depends on !(PAGE_SIZE_64KB || ARM64_64K_PAGES || \
479 IA64_PAGE_SIZE_64KB || MICROBLAZE_64K_PAGES || \
480 PARISC_PAGE_SIZE_64KB || PPC_64K_PAGES)
482 This driver supports VMware's vmxnet3 virtual ethernet NIC.
483 To compile this driver as a module, choose M here: the
484 module will be called vmxnet3.
487 tristate "FUJITSU Extended Socket Network Device driver"
490 This driver provides support for Extended Socket network device
491 on Extended Partitioning of FUJITSU PRIMEQUEST 2000 E2 series.
493 config THUNDERBOLT_NET
494 tristate "Networking over Thunderbolt cable"
495 depends on THUNDERBOLT && INET
497 Select this if you want to create network between two
498 computers over a Thunderbolt cable. The driver supports Apple
499 ThunderboltIP protocol and allows communication with any host
500 supporting the same protocol including Windows and macOS.
502 To compile this driver a module, choose M here. The module will be
503 called thunderbolt-net.
505 source "drivers/net/hyperv/Kconfig"
508 tristate "Simulated networking device"
512 This driver is a developer testing tool and software model that can
513 be used to test various control path networking APIs, especially
516 To compile this driver as a module, choose M here: the module
517 will be called netdevsim.
520 tristate "Failover driver"
523 This provides an automated failover mechanism via APIs to create
524 and destroy a failover master netdev and manages a primary and
525 standby slave netdevs that get registered via the generic failover
526 infrastructure. This can be used by paravirtual drivers to enable
527 an alternate low latency datapath. It also enables live migration of
528 a VM with direct attached VF by failing over to the paravirtual
529 datapath when the VF is unplugged.