Kconfig - OpenGrok cross reference for /linux-6.8/drivers/net/Kconfig

1 # SPDX-License-Identifier: GPL-2.0-only
3 # Network device configuration
8 	depends on NET
9 	bool "Network device support"
25 # All the following symbols are dependent on NETDEVICES - do not repeat
43 	depends on INET
44 	depends on IPV6 || IPV6=n
45 	depends on TLS || TLS_DEVICE=n
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
77 	depends on NET && INET
78 	depends on IPV6 || !IPV6
79 	depends on !KMSAN # KMSAN doesn't support the crypto configs below
109 	depends on WIREGUARD
124 	  lines) or PPP (a better SLIP) on them, you can make them behave like
131 	  section 6.2 of the NET-3-HOWTO, available from
139 	depends on SCSI && PCI
152 	depends on NET_ACT_MIRRED || NFT_FWD_NETDEV
159 	  device at a time, you need to compile this driver as a module.
167 	tristate "MAC-VLAN support"
173 	  iproute2 package starting with the iproute2-2.6.23 release:
181 	tristate "MAC-VLAN based tap driver"
182 	depends on MACVLAN
183 	depends on INET
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
195 	depends on NETFILTER
196 	depends on IPVLAN
201 	tristate "IP-VLAN support"
202 	depends on INET
203 	depends on IPV6 || !IPV6
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
211 	  iproute2 package starting with the iproute2-3.19 release:
213 	  "ip link add link <main-dev> [ NAME ] type ipvlan"
219 	tristate "IP-VLAN based tap driver"
220 	depends on IPVLAN
221 	depends on INET
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
234 	depends on INET
242 	    http://tools.ietf.org/html/draft-mahalingam-dutt-dcops-vxlan-02
249 	depends on INET
250 	depends on IPV6 || !IPV6
258 	    http://tools.ietf.org/html/draft-gross-geneve-02
265 	depends on INET
266 	depends on IPV6 || !IPV6
277 	tristate "GPRS Tunneling Protocol datapath (GTP-U)"
278 	depends on INET
282 	  the GPRS Tunneling Protocol datapath (GTP-U). This tunneling protocol
285 	  implements the signaling protocol (GTP-C) to update its PDP context
295 	depends on INET && IP_MULTICAST
296 	depends on IPV6 || !IPV6
311 	tristate "IEEE 802.1AE MAC-level encryption (MACsec)"
327 	depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
337 	depends on NETCONSOLE
347 	depends on NETCONSOLE_EXTENDED_LOG
365 	depends on NTB_TRANSPORT
369 	depends on RAPIDIO
373 	depends on RIONET
378 	depends on RIONET
382 	tristate "Universal TUN/TAP device driver support"
383 	depends on INET
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,
393 	  corresponding net device tunX or tapX.  After a program closed above
394 	  devices, driver will automatically delete tunXX or tapXX device and
409 	  interface for a virtual interface to re-use core tap functionality.
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.
422 	  Unless you have a little-endian system hosting a big-endian virtual
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
435 	depends on VIRTIO
443 	tristate "Virtual netlink monitoring device"
445 	  This option enables a monitoring net device for netlink skbs. The
448 	  messages if they tap into the netlink device, record pcaps for further
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
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
472 	tristate "Virtual vsock monitoring device"
473 	depends on VHOST_VSOCK
475 	  This option enables a monitoring net device for vsock sockets. It is
481 	depends on MHI_BUS
510 	depends on PNP
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
522 	  information on how to use this module, as it needs special ppp
534 source "drivers/net/pse-pd/Kconfig"
563 	tristate "Xen network device frontend driver"
564 	depends on XEN
578 	  M here: the module will be called xen-netfront.
581 	tristate "Xen backend network device"
582 	depends on XEN_BACKEND
592 	  The backend driver presents a standard network device
593 	  endpoint for each paravirtual network device to the driver
600 	  will be called xen-netback.
604 	depends on PCI && INET
605 	depends on PAGE_SIZE_LESS_THAN_64KB
613 	tristate "FUJITSU Extended Socket Network Device driver"
614 	depends on ACPI
616 	  This driver provides support for Extended Socket network device
617 	  on Extended Partitioning of FUJITSU PRIMEQUEST 2000 E2 series.
623 	tristate "Simulated networking device"
624 	depends on DEBUG_FS
625 	depends on INET
626 	depends on IPV6 || IPV6=n
627 	depends on PSAMPLE || PSAMPLE=n
628 	depends on PTP_1588_CLOCK_MOCK || PTP_1588_CLOCK_MOCK=n
633 	  HW-offload related.
652 	depends on ISA