Kconfig - OpenGrok cross reference for /linux-6.12.1/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
308 	depends on INET && IP_MULTICAST
309 	depends on IPV6 || !IPV6
324 	tristate "IEEE 802.1AE MAC-level encryption (MACsec)"
340 	depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
350 	depends on NETCONSOLE
360 	depends on NETCONSOLE_EXTENDED_LOG
378 	depends on NTB_TRANSPORT
382 	depends on RAPIDIO
386 	depends on RIONET
391 	depends on RIONET
395 	tristate "Universal TUN/TAP device driver support"
396 	depends on INET
400 	  programs.  It can be viewed as a simple Point-to-Point or Ethernet
401 	  device, which instead of receiving packets from a physical media,
406 	  corresponding net device tunX or tapX.  After a program closed above
407 	  devices, driver will automatically delete tunXX or tapXX device and
422 	  interface for a virtual interface to re-use core tap functionality.
425 	bool "Support for cross-endian vnet headers on little-endian kernels"
428 	  This option allows TUN/TAP and MACVTAP device drivers in a
429 	  little-endian kernel to parse vnet headers that come from a
430 	  big-endian legacy virtio device.
435 	  Unless you have a little-endian system hosting a big-endian virtual
439 	tristate "Virtual ethernet pair device"
442 	  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 vice
448 	depends on VIRTIO
456 	tristate "Virtual netlink monitoring device"
458 	  This option enables a monitoring net device for netlink skbs. The
461 	  messages if they tap into the netlink device, record pcaps for further
466 	bool "BPF-programmable network device"
467 	depends on BPF_SYSCALL
469 	  The netkit device is a virtual networking device where BPF programs
470 	  can be attached to the device(s) transmission routine in order to
471 	  implement the driver's internal logic. The device can be configured
476 	depends on IP_MULTIPLE_TABLES
477 	depends on NET_L3_MASTER_DEV
478 	depends on IPV6 || IPV6=n
479 	depends on IPV6_MULTIPLE_TABLES || IPV6=n
485 	tristate "Virtual vsock monitoring device"
486 	depends on VHOST_VSOCK
488 	  This option enables a monitoring net device for vsock sockets. It is
494 	depends on MHI_BUS
523 	depends on ISA && PNP
528 	  TV companies to provide cable modem access. It's a one-way
529 	  downstream-only cable modem, meaning that your upstream net link is
535 	  information on how to use this module, as it needs special ppp
547 source "drivers/net/pse-pd/Kconfig"
576 	tristate "Xen network device frontend driver"
577 	depends on XEN
591 	  M here: the module will be called xen-netfront.
594 	tristate "Xen backend network device"
595 	depends on XEN_BACKEND
605 	  The backend driver presents a standard network device
606 	  endpoint for each paravirtual network device to the driver
613 	  will be called xen-netback.
617 	depends on PCI && INET
618 	depends on PAGE_SIZE_LESS_THAN_64KB
626 	tristate "FUJITSU Extended Socket Network Device driver"
627 	depends on ACPI
629 	  This driver provides support for Extended Socket network device
630 	  on Extended Partitioning of FUJITSU PRIMEQUEST 2000 E2 series.
636 	tristate "Simulated networking device"
637 	depends on DEBUG_FS
638 	depends on INET
639 	depends on IPV6 || IPV6=n
640 	depends on PSAMPLE || PSAMPLE=n
641 	depends on PTP_1588_CLOCK_MOCK || PTP_1588_CLOCK_MOCK=n
647 	  HW-offload related.
666 	depends on ISA