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
108 depends on WIREGUARD
123 lines) or PPP (a better SLIP) on them, you can make them behave like
130 section 6.2 of the NET-3-HOWTO, available from
138 depends on SCSI && PCI
151 depends on NET_CLS_ACT
158 device at a time, you need to compile this driver as a module.
166 tristate "MAC-VLAN support"
172 iproute2 package starting with the iproute2-2.6.23 release:
180 tristate "MAC-VLAN based tap driver"
181 depends on MACVLAN
182 depends on INET
185 This adds a specialized tap character device driver that is based
186 on the MAC-VLAN network interface, called macvtap. A macvtap device
187 can be added in the same way as a macvlan device, using 'type
194 depends on NETFILTER
195 depends on IPVLAN
200 tristate "IP-VLAN support"
201 depends on INET
202 depends on IPV6 || !IPV6
205 and packets will be delivered based on the dest L3 (IPv6/IPv4 addr)
206 on packets. All interfaces (including the main interface) share L2
210 iproute2 package starting with the iproute2-3.19 release:
212 "ip link add link <main-dev> [ NAME ] type ipvlan"
218 tristate "IP-VLAN based tap driver"
219 depends on IPVLAN
220 depends on INET
223 This adds a specialized tap character device driver that is based
224 on the IP-VLAN network interface, called ipvtap. An ipvtap device
225 can be added in the same way as a ipvlan device, using 'type
233 depends on INET
241 http://tools.ietf.org/html/draft-mahalingam-dutt-dcops-vxlan-02
248 depends on INET
249 depends on IPV6 || !IPV6
257 http://tools.ietf.org/html/draft-gross-geneve-02
264 depends on INET
265 depends on IPV6 || !IPV6
276 tristate "GPRS Tunneling Protocol datapath (GTP-U)"
277 depends on INET
281 the GPRS Tunneling Protocol datapath (GTP-U). This tunneling protocol
284 implements the signaling protocol (GTP-C) to update its PDP context
293 tristate "IEEE 802.1AE MAC-level encryption (MACsec)"
309 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
326 depends on NTB_TRANSPORT
330 depends on RAPIDIO
334 depends on RIONET
339 depends on RIONET
343 tristate "Universal TUN/TAP device driver support"
344 depends on INET
348 programs. It can be viewed as a simple Point-to-Point or Ethernet
349 device, which instead of receiving packets from a physical media,
354 corresponding net device tunX or tapX. After a program closed above
355 devices, driver will automatically delete tunXX or tapXX device and
370 interface for a virtual interface to re-use core tap functionality.
373 bool "Support for cross-endian vnet headers on little-endian kernels"
376 This option allows TUN/TAP and MACVTAP device drivers in a
377 little-endian kernel to parse vnet headers that come from a
378 big-endian legacy virtio device.
383 Unless you have a little-endian system hosting a big-endian virtual
387 tristate "Virtual ethernet pair device"
389 This device is a local ethernet tunnel. Devices are created in pairs.
390 When one end receives the packet it appears on its pair and vice
395 depends on VIRTIO
402 tristate "Virtual netlink monitoring device"
404 This option enables a monitoring net device for netlink skbs. The
407 messages if they tap into the netlink device, record pcaps for further
413 depends on IP_MULTIPLE_TABLES
414 depends on NET_L3_MASTER_DEV
415 depends on IPV6 || IPV6=n
416 depends on IPV6_MULTIPLE_TABLES || IPV6=n
422 tristate "Virtual vsock monitoring device"
423 depends on VHOST_VSOCK
425 This option enables a monitoring net device for vsock sockets. It is
452 depends on PNP
457 TV companies to provide cable modem access. It's a one-way
458 downstream-only cable modem, meaning that your upstream net link is
464 information on how to use this module, as it needs special ppp
499 tristate "Xen network device frontend driver"
500 depends on XEN
514 M here: the module will be called xen-netfront.
517 tristate "Xen backend network device"
518 depends on XEN_BACKEND
528 The backend driver presents a standard network device
529 endpoint for each paravirtual network device to the driver
536 will be called xen-netback.
540 depends on PCI && INET
541 depends on !(PAGE_SIZE_64KB || ARM64_64K_PAGES || \
550 tristate "FUJITSU Extended Socket Network Device driver"
551 depends on ACPI
553 This driver provides support for Extended Socket network device
554 on Extended Partitioning of FUJITSU PRIMEQUEST 2000 E2 series.
558 depends on USB4 && INET
566 called thunderbolt-net.
571 tristate "Simulated networking device"
572 depends on DEBUG_FS
573 depends on INET
574 depends on IPV6 || IPV6=n
579 HW-offload related.