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