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
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
76 depends on NET && INET
77 depends on IPV6 || !IPV6
107 depends on WIREGUARD
122 lines) or PPP (a better SLIP) on them, you can make them behave like
129 section 6.2 of the NET-3-HOWTO, available from
137 depends on SCSI && PCI
150 depends on NET_ACT_MIRRED || NFT_FWD_NETDEV
157 device at a time, you need to compile this driver as a module.
165 tristate "MAC-VLAN support"
171 iproute2 package starting with the iproute2-2.6.23 release:
179 tristate "MAC-VLAN based tap driver"
180 depends on MACVLAN
181 depends on INET
184 This adds a specialized tap character device driver that is based
185 on the MAC-VLAN network interface, called macvtap. A macvtap device
186 can be added in the same way as a macvlan device, using 'type
193 depends on NETFILTER
194 depends on IPVLAN
199 tristate "IP-VLAN support"
200 depends on INET
201 depends on IPV6 || !IPV6
204 and packets will be delivered based on the dest L3 (IPv6/IPv4 addr)
205 on packets. All interfaces (including the main interface) share L2
209 iproute2 package starting with the iproute2-3.19 release:
211 "ip link add link <main-dev> [ NAME ] type ipvlan"
217 tristate "IP-VLAN based tap driver"
218 depends on IPVLAN
219 depends on INET
222 This adds a specialized tap character device driver that is based
223 on the IP-VLAN network interface, called ipvtap. An ipvtap device
224 can be added in the same way as a ipvlan device, using 'type
232 depends on INET
240 http://tools.ietf.org/html/draft-mahalingam-dutt-dcops-vxlan-02
247 depends on INET
248 depends on IPV6 || !IPV6
256 http://tools.ietf.org/html/draft-gross-geneve-02
263 depends on INET
264 depends on IPV6 || !IPV6
275 tristate "GPRS Tunneling Protocol datapath (GTP-U)"
276 depends on INET
280 the GPRS Tunneling Protocol datapath (GTP-U). This tunneling protocol
283 implements the signaling protocol (GTP-C) to update its PDP context
292 tristate "IEEE 802.1AE MAC-level encryption (MACsec)"
308 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
325 depends on NTB_TRANSPORT
329 depends on RAPIDIO
333 depends on RIONET
338 depends on RIONET
342 tristate "Universal TUN/TAP device driver support"
343 depends on INET
347 programs. It can be viewed as a simple Point-to-Point or Ethernet
348 device, which instead of receiving packets from a physical media,
353 corresponding net device tunX or tapX. After a program closed above
354 devices, driver will automatically delete tunXX or tapXX device and
369 interface for a virtual interface to re-use core tap functionality.
372 bool "Support for cross-endian vnet headers on little-endian kernels"
375 This option allows TUN/TAP and MACVTAP device drivers in a
376 little-endian kernel to parse vnet headers that come from a
377 big-endian legacy virtio device.
382 Unless you have a little-endian system hosting a big-endian virtual
386 tristate "Virtual ethernet pair device"
388 This device is a local ethernet tunnel. Devices are created in pairs.
389 When one end receives the packet it appears on its pair and vice
394 depends on VIRTIO
401 tristate "Virtual netlink monitoring device"
403 This option enables a monitoring net device for netlink skbs. The
406 messages if they tap into the netlink device, record pcaps for further
412 depends on IP_MULTIPLE_TABLES
413 depends on NET_L3_MASTER_DEV
414 depends on IPV6 || IPV6=n
415 depends on IPV6_MULTIPLE_TABLES || IPV6=n
421 tristate "Virtual vsock monitoring device"
422 depends on VHOST_VSOCK
424 This option enables a monitoring net device for vsock sockets. It is
451 depends on PNP
456 TV companies to provide cable modem access. It's a one-way
457 downstream-only cable modem, meaning that your upstream net link is
463 information on how to use this module, as it needs special ppp
498 tristate "Xen network device frontend driver"
499 depends on XEN
513 M here: the module will be called xen-netfront.
516 tristate "Xen backend network device"
517 depends on XEN_BACKEND
527 The backend driver presents a standard network device
528 endpoint for each paravirtual network device to the driver
535 will be called xen-netback.
539 depends on PCI && INET
540 depends on !(PAGE_SIZE_64KB || ARM64_64K_PAGES || \
549 tristate "FUJITSU Extended Socket Network Device driver"
550 depends on ACPI
552 This driver provides support for Extended Socket network device
553 on Extended Partitioning of FUJITSU PRIMEQUEST 2000 E2 series.
557 depends on USB4 && INET
565 called thunderbolt-net.
570 tristate "Simulated networking device"
571 depends on DEBUG_FS
572 depends on INET
573 depends on IPV6 || IPV6=n
578 HW-offload related.