Lines Matching +full:on +full:- +full:device
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 && \
344 depends on NTB_TRANSPORT
348 depends on RAPIDIO
352 depends on RIONET
357 depends on RIONET
361 tristate "Universal TUN/TAP device driver support"
362 depends on INET
366 programs. It can be viewed as a simple Point-to-Point or Ethernet
367 device, which instead of receiving packets from a physical media,
372 corresponding net device tunX or tapX. After a program closed above
373 devices, driver will automatically delete tunXX or tapXX device and
388 interface for a virtual interface to re-use core tap functionality.
391 bool "Support for cross-endian vnet headers on little-endian kernels"
394 This option allows TUN/TAP and MACVTAP device drivers in a
395 little-endian kernel to parse vnet headers that come from a
396 big-endian legacy virtio device.
401 Unless you have a little-endian system hosting a big-endian virtual
405 tristate "Virtual ethernet pair device"
407 This device is a local ethernet tunnel. Devices are created in pairs.
408 When one end receives the packet it appears on its pair and vice
413 depends on VIRTIO
420 tristate "Virtual netlink monitoring device"
422 This option enables a monitoring net device for netlink skbs. The
425 messages if they tap into the netlink device, record pcaps for further
431 depends on IP_MULTIPLE_TABLES
432 depends on NET_L3_MASTER_DEV
433 depends on IPV6 || IPV6=n
434 depends on IPV6_MULTIPLE_TABLES || IPV6=n
440 tristate "Virtual vsock monitoring device"
441 depends on VHOST_VSOCK
443 This option enables a monitoring net device for vsock sockets. It is
449 depends on MHI_BUS
478 depends on PNP
483 TV companies to provide cable modem access. It's a one-way
484 downstream-only cable modem, meaning that your upstream net link is
490 information on how to use this module, as it needs special ppp
502 source "drivers/net/pse-pd/Kconfig"
531 tristate "Xen network device frontend driver"
532 depends on XEN
546 M here: the module will be called xen-netfront.
549 tristate "Xen backend network device"
550 depends on XEN_BACKEND
560 The backend driver presents a standard network device
561 endpoint for each paravirtual network device to the driver
568 will be called xen-netback.
572 depends on PCI && INET
573 depends on PAGE_SIZE_LESS_THAN_64KB
580 tristate "FUJITSU Extended Socket Network Device driver"
581 depends on ACPI
583 This driver provides support for Extended Socket network device
584 on Extended Partitioning of FUJITSU PRIMEQUEST 2000 E2 series.
588 depends on USB4 && INET
596 called thunderbolt-net.
601 tristate "Simulated networking device"
602 depends on DEBUG_FS
603 depends on INET
604 depends on IPV6 || IPV6=n
605 depends on PSAMPLE || PSAMPLE=n
610 HW-offload related.
629 depends on ISA