Lines Matching +full:on +full:- +full:device

2 # Network device configuration
7 	depends on NET
8 	bool "Network device support"
9 	---help---
24 # All the following symbols are dependent on NETDEVICES - do not repeat
34 	---help---
42 	depends on INET
43 	depends on IPV6 || IPV6=n
44 	---help---
60 	---help---
61 	  This is essentially a bit-bucket device (i.e. traffic you send to
62 	  this device is consigned into oblivion) with a configurable IP
75 	---help---
79 	  lines) or PPP (a better SLIP) on them, you can make them behave like
86 	  section 6.2 of the NET-3-HOWTO, available from
94 	depends on SCSI && PCI
107 	depends on NET_CLS_ACT
108 	---help---
113 	  device at a time, you need to compile this driver as a module.
121 	tristate "MAC-VLAN support"
122 	---help---
127 	  iproute2 package starting with the iproute2-2.6.23 release:
135 	tristate "MAC-VLAN based tap driver"
136 	depends on MACVLAN
137 	depends on INET
140 	  This adds a specialized tap character device driver that is based
141 	  on the MAC-VLAN network interface, called macvtap. A macvtap device
142 	  can be added in the same way as a macvlan device, using 'type
150     tristate "IP-VLAN support"
151     depends on INET
152     depends on IPV6 || !IPV6
153     depends on NETFILTER
155     ---help---
157       and packets will be delivered based on the dest L3 (IPv6/IPv4 addr)
158       on packets. All interfaces (including the main interface) share L2
162       iproute2 package starting with the iproute2-3.19 release:
164       "ip link add link <main-dev> [ NAME ] type ipvlan"
170 	tristate "IP-VLAN based tap driver"
171 	depends on IPVLAN
172 	depends on INET
174 	---help---
175 	  This adds a specialized tap character device driver that is based
176 	  on the IP-VLAN network interface, called ipvtap. An ipvtap device
177 	  can be added in the same way as a ipvlan device, using 'type
185        depends on INET
188        ---help---
193 	    http://tools.ietf.org/html/draft-mahalingam-dutt-dcops-vxlan-02
200        depends on INET
201        depends on IPV6 || !IPV6
204        ---help---
209 	    http://tools.ietf.org/html/draft-gross-geneve-02
215 	tristate "GPRS Tunneling Protocol datapath (GTP-U)"
216 	depends on INET
218 	---help---
220 	  the GPRS Tunneling Protocol datapath (GTP-U). This tunneling protocol
223 	  implements the signaling protocol (GTP-C) to update its PDP context
232 	tristate "IEEE 802.1AE MAC-level encryption (MACsec)"
237 	---help---
242 	---help---
248 	depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
265 	depends on NTB_TRANSPORT
269 	depends on RAPIDIO
273 	depends on RIONET
278 	depends on RIONET
282 	tristate "Universal TUN/TAP device driver support"
283 	depends on INET
285 	---help---
287 	  programs.  It can be viewed as a simple Point-to-Point or Ethernet
288 	  device, which instead of receiving packets from a physical media,
293 	  corresponding net device tunX or tapX.  After a program closed above
294 	  devices, driver will automatically delete tunXX or tapXX device and
307 	---help---
309 	  interface for a virtual interface to re-use core tap functionality.
312 	bool "Support for cross-endian vnet headers on little-endian kernels"
314 	---help---
315 	  This option allows TUN/TAP and MACVTAP device drivers in a
316 	  little-endian kernel to parse vnet headers that come from a
317 	  big-endian legacy virtio device.
322 	  Unless you have a little-endian system hosting a big-endian virtual
326 	tristate "Virtual ethernet pair device"
327 	---help---
328 	  This device is a local ethernet tunnel. Devices are created in pairs.
329 	  When one end receives the packet it appears on its pair and vice
334 	depends on VIRTIO
336 	---help---
341 	tristate "Virtual netlink monitoring device"
342 	---help---
343 	  This option enables a monitoring net device for netlink skbs. The
346 	  messages if they tap into the netlink device, record pcaps for further
352 	depends on IP_MULTIPLE_TABLES
353 	depends on NET_L3_MASTER_DEV
354 	depends on IPV6 || IPV6=n
355 	depends on IPV6_MULTIPLE_TABLES || IPV6=n
356 	---help---
361     tristate "Virtual vsock monitoring device"
362     depends on VHOST_VSOCK
363     ---help---
364      This option enables a monitoring net device for vsock sockets. It is
389 	depends on PNP
390 	---help---
394 	  TV companies to provide cable modem access. It's a one-way
395 	  downstream-only cable modem, meaning that your upstream net link is
400 	  <file:Documentation/networking/README.sb1000> for information on how
432 	tristate "Xen network device frontend driver"
433 	depends on XEN
446 	  M here: the module will be called xen-netfront.
449 	tristate "Xen backend network device"
450 	depends on XEN_BACKEND
460 	  The backend driver presents a standard network device
461 	  endpoint for each paravirtual network device to the driver
468 	  will be called xen-netback.
472 	depends on PCI && INET
473 	depends on !(PAGE_SIZE_64KB || ARM64_64K_PAGES || \
482 	tristate "FUJITSU Extended Socket Network Device driver"
483 	depends on ACPI
485 	  This driver provides support for Extended Socket network device
486           on Extended Partitioning of FUJITSU PRIMEQUEST 2000 E2 series.
490 	depends on THUNDERBOLT && INET
498 	  called thunderbolt-net.
503 	tristate "Simulated networking device"
504 	depends on DEBUG_FS
505 	depends on MAY_USE_DEVLINK
509 	  HW-offload related.