[linux-block.git] / drivers / net / Kconfig

#
# Network device configuration
#

menuconfig NETDEVICES
	default y if UML
	depends on NET
	bool "Network device support"
	---help---
	  You can say N here if you don't intend to connect your Linux box to
	  any other computer at all.

	  You'll have to say Y if your computer contains a network card that
	  you want to use under Linux. If you are going to run SLIP or PPP over
	  telephone line or null modem cable you need say Y here. Connecting
	  two machines with parallel ports using PLIP needs this, as well as
	  AX.25/KISS for sending Internet traffic over amateur radio links.

	  See also "The Linux Network Administrator's Guide" by Olaf Kirch and
	  Terry Dawson. Available at <http://www.tldp.org/guides.html>.

	  If unsure, say Y.

# All the following symbols are dependent on NETDEVICES - do not repeat
# that for each of the symbols.
if NETDEVICES

config MII
	tristate

config NET_CORE
	default y
	bool "Network core driver support"
	---help---
	  You can say N here if you do not intend to use any of the
	  networking core drivers (i.e. VLAN, bridging, bonding, etc.)

if NET_CORE

config BONDING
	tristate "Bonding driver support"
	depends on INET
	depends on IPV6 || IPV6=n
	---help---
	  Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
	  Channels together. This is called 'Etherchannel' by Cisco,
	  'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.

	  The driver supports multiple bonding modes to allow for both high
	  performance and high availability operation.

	  Refer to <file:Documentation/networking/bonding.txt> for more
	  information.

	  To compile this driver as a module, choose M here: the module
	  will be called bonding.

config DUMMY
	tristate "Dummy net driver support"
	---help---
	  This is essentially a bit-bucket device (i.e. traffic you send to
	  this device is consigned into oblivion) with a configurable IP
	  address. It is most commonly used in order to make your currently
	  inactive SLIP address seem like a real address for local programs.
	  If you use SLIP or PPP, you might want to say Y here. It won't
	  enlarge your kernel. What a deal. Read about it in the Network
	  Administrator's Guide, available from
	  <http://www.tldp.org/docs.html#guide>.

	  To compile this driver as a module, choose M here: the module
	  will be called dummy.

config EQUALIZER
	tristate "EQL (serial line load balancing) support"
	---help---
	  If you have two serial connections to some other computer (this
	  usually requires two modems and two telephone lines) and you use
	  SLIP (the protocol for sending Internet traffic over telephone
	  lines) or PPP (a better SLIP) on them, you can make them behave like
	  one double speed connection using this driver.  Naturally, this has
	  to be supported at the other end as well, either with a similar EQL
	  Linux driver or with a Livingston Portmaster 2e.

	  Say Y if you want this and read
	  <file:Documentation/networking/eql.txt>.  You may also want to read
	  section 6.2 of the NET-3-HOWTO, available from
	  <http://www.tldp.org/docs.html#howto>.

	  To compile this driver as a module, choose M here: the module
	  will be called eql.  If unsure, say N.

config NET_FC
	bool "Fibre Channel driver support"
	depends on SCSI && PCI
	help
	  Fibre Channel is a high speed serial protocol mainly used to connect
	  large storage devices to the computer; it is compatible with and
	  intended to replace SCSI.

	  If you intend to use Fibre Channel, you need to have a Fibre channel
	  adaptor card in your computer; say Y here and to the driver for your
	  adaptor below. You also should have said Y to "SCSI support" and
	  "SCSI generic support".

config IFB
	tristate "Intermediate Functional Block support"
	depends on NET_CLS_ACT
	---help---
	  This is an intermediate driver that allows sharing of
	  resources.
	  To compile this driver as a module, choose M here: the module
	  will be called ifb.  If you want to use more than one ifb
	  device at a time, you need to compile this driver as a module.
	  Instead of 'ifb', the devices will then be called 'ifb0',
	  'ifb1' etc.
	  Look at the iproute2 documentation directory for usage etc

source "drivers/net/team/Kconfig"

config MACVLAN
	tristate "MAC-VLAN support"
	---help---
	  This allows one to create virtual interfaces that map packets to
	  or from specific MAC addresses to a particular interface.

	  Macvlan devices can be added using the "ip" command from the
	  iproute2 package starting with the iproute2-2.6.23 release:

	  "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"

	  To compile this driver as a module, choose M here: the module
	  will be called macvlan.

config MACVTAP
	tristate "MAC-VLAN based tap driver"
	depends on MACVLAN
	depends on INET
	select TAP
	help
	  This adds a specialized tap character device driver that is based
	  on the MAC-VLAN network interface, called macvtap. A macvtap device
	  can be added in the same way as a macvlan device, using 'type
	  macvtap', and then be accessed through the tap user space interface.

	  To compile this driver as a module, choose M here: the module
	  will be called macvtap.


config IPVLAN
    tristate "IP-VLAN support"
    depends on INET
    depends on IPV6 || !IPV6
    depends on NETFILTER
    select NET_L3_MASTER_DEV
    ---help---
      This allows one to create virtual devices off of a main interface
      and packets will be delivered based on the dest L3 (IPv6/IPv4 addr)
      on packets. All interfaces (including the main interface) share L2
      making it transparent to the connected L2 switch.

      Ipvlan devices can be added using the "ip" command from the
      iproute2 package starting with the iproute2-3.19 release:

      "ip link add link <main-dev> [ NAME ] type ipvlan"

      To compile this driver as a module, choose M here: the module
      will be called ipvlan.

config IPVTAP
	tristate "IP-VLAN based tap driver"
	depends on IPVLAN
	depends on INET
	select TAP
	---help---
	  This adds a specialized tap character device driver that is based
	  on the IP-VLAN network interface, called ipvtap. An ipvtap device
	  can be added in the same way as a ipvlan device, using 'type
	  ipvtap', and then be accessed through the tap user space interface.

	  To compile this driver as a module, choose M here: the module
	  will be called ipvtap.

config VXLAN
       tristate "Virtual eXtensible Local Area Network (VXLAN)"
       depends on INET
       select NET_UDP_TUNNEL
       select GRO_CELLS
       ---help---
	  This allows one to create vxlan virtual interfaces that provide
	  Layer 2 Networks over Layer 3 Networks. VXLAN is often used
	  to tunnel virtual network infrastructure in virtualized environments.
	  For more information see:
	    http://tools.ietf.org/html/draft-mahalingam-dutt-dcops-vxlan-02

	  To compile this driver as a module, choose M here: the module
	  will be called vxlan.

config GENEVE
       tristate "Generic Network Virtualization Encapsulation"
       depends on INET && NET_UDP_TUNNEL
       depends on IPV6 || !IPV6
       select NET_IP_TUNNEL
       select GRO_CELLS
       ---help---
	  This allows one to create geneve virtual interfaces that provide
	  Layer 2 Networks over Layer 3 Networks. GENEVE is often used
	  to tunnel virtual network infrastructure in virtualized environments.
	  For more information see:
	    http://tools.ietf.org/html/draft-gross-geneve-02

	  To compile this driver as a module, choose M here: the module
	  will be called geneve.

config GTP
	tristate "GPRS Tunneling Protocol datapath (GTP-U)"
	depends on INET && NET_UDP_TUNNEL
	select NET_IP_TUNNEL
	---help---
	  This allows one to create gtp virtual interfaces that provide
	  the GPRS Tunneling Protocol datapath (GTP-U). This tunneling protocol
	  is used to prevent subscribers from accessing mobile carrier core
	  network infrastructure. This driver requires a userspace software that
	  implements the signaling protocol (GTP-C) to update its PDP context
	  base, such as OpenGGSN <http://git.osmocom.org/openggsn/). This
	  tunneling protocol is implemented according to the GSM TS 09.60 and
	  3GPP TS 29.060 standards.

	  To compile this drivers as a module, choose M here: the module
	  wil be called gtp.

config MACSEC
	tristate "IEEE 802.1AE MAC-level encryption (MACsec)"
	select CRYPTO
	select CRYPTO_AES
	select CRYPTO_GCM
	select GRO_CELLS
	---help---
	   MACsec is an encryption standard for Ethernet.

config NETCONSOLE
	tristate "Network console logging support"
	---help---
	If you want to log kernel messages over the network, enable this.
	See <file:Documentation/networking/netconsole.txt> for details.

config NETCONSOLE_DYNAMIC
	bool "Dynamic reconfiguration of logging targets"
	depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
			!(NETCONSOLE=y && CONFIGFS_FS=m)
	help
	  This option enables the ability to dynamically reconfigure target
	  parameters (interface, IP addresses, port numbers, MAC addresses)
	  at runtime through a userspace interface exported using configfs.
	  See <file:Documentation/networking/netconsole.txt> for details.

config NETPOLL
	def_bool NETCONSOLE
	select SRCU

config NET_POLL_CONTROLLER
	def_bool NETPOLL

config NTB_NETDEV
	tristate "Virtual Ethernet over NTB Transport"
	depends on NTB_TRANSPORT

config RIONET
	tristate "RapidIO Ethernet over messaging driver support"
	depends on RAPIDIO

config RIONET_TX_SIZE
	int "Number of outbound queue entries"
	depends on RIONET
	default "128"

config RIONET_RX_SIZE
	int "Number of inbound queue entries"
	depends on RIONET
	default "128"

config TUN
	tristate "Universal TUN/TAP device driver support"
	depends on INET
	select CRC32
	---help---
	  TUN/TAP provides packet reception and transmission for user space
	  programs.  It can be viewed as a simple Point-to-Point or Ethernet
	  device, which instead of receiving packets from a physical media,
	  receives them from user space program and instead of sending packets
	  via physical media writes them to the user space program.

	  When a program opens /dev/net/tun, driver creates and registers
	  corresponding net device tunX or tapX.  After a program closed above
	  devices, driver will automatically delete tunXX or tapXX device and
	  all routes corresponding to it.

	  Please read <file:Documentation/networking/tuntap.txt> for more
	  information.

	  To compile this driver as a module, choose M here: the module
	  will be called tun.

	  If you don't know what to use this for, you don't need it.

config TAP
	tristate
	---help---
	  This option is selected by any driver implementing tap user space
	  interface for a virtual interface to re-use core tap functionality.

config TUN_VNET_CROSS_LE
	bool "Support for cross-endian vnet headers on little-endian kernels"
	default n
	---help---
	  This option allows TUN/TAP and MACVTAP device drivers in a
	  little-endian kernel to parse vnet headers that come from a
	  big-endian legacy virtio device.

	  Userspace programs can control the feature using the TUNSETVNETBE
	  and TUNGETVNETBE ioctls.

	  Unless you have a little-endian system hosting a big-endian virtual
	  machine with a legacy virtio NIC, you should say N.

config VETH
	tristate "Virtual ethernet pair device"
	---help---
	  This device is a local ethernet tunnel. Devices are created in pairs.
	  When one end receives the packet it appears on its pair and vice
	  versa.

config VIRTIO_NET
	tristate "Virtio network driver"
	depends on VIRTIO
	select NET_FAILOVER
	---help---
	  This is the virtual network driver for virtio.  It can be used with
	  QEMU based VMMs (like KVM or Xen).  Say Y or M.

config NLMON
	tristate "Virtual netlink monitoring device"
	---help---
	  This option enables a monitoring net device for netlink skbs. The
	  purpose of this is to analyze netlink messages with packet sockets.
	  Thus applications like tcpdump will be able to see local netlink
	  messages if they tap into the netlink device, record pcaps for further
	  diagnostics, etc. This is mostly intended for developers or support
	  to debug netlink issues. If unsure, say N.

config NET_VRF
	tristate "Virtual Routing and Forwarding (Lite)"
	depends on IP_MULTIPLE_TABLES
	depends on NET_L3_MASTER_DEV
	depends on IPV6 || IPV6=n
	depends on IPV6_MULTIPLE_TABLES || IPV6=n
	---help---
	  This option enables the support for mapping interfaces into VRF's. The
	  support enables VRF devices.

config VSOCKMON
    tristate "Virtual vsock monitoring device"
    depends on VHOST_VSOCK
    ---help---
     This option enables a monitoring net device for vsock sockets. It is
     mostly intended for developers or support to debug vsock issues. If
     unsure, say N.

endif # NET_CORE

config SUNGEM_PHY
	tristate

source "drivers/net/arcnet/Kconfig"

source "drivers/atm/Kconfig"

source "drivers/net/caif/Kconfig"

source "drivers/net/dsa/Kconfig"

source "drivers/net/ethernet/Kconfig"

source "drivers/net/fddi/Kconfig"

source "drivers/net/hippi/Kconfig"

config NET_SB1000
	tristate "General Instruments Surfboard 1000"
	depends on PNP
	---help---
	  This is a driver for the General Instrument (also known as
	  NextLevel) SURFboard 1000 internal
	  cable modem. This is an ISA card which is used by a number of cable
	  TV companies to provide cable modem access. It's a one-way
	  downstream-only cable modem, meaning that your upstream net link is
	  provided by your regular phone modem.

	  At present this driver only compiles as a module, so say M here if
	  you have this card. The module will be called sb1000. Then read
	  <file:Documentation/networking/README.sb1000> for information on how
	  to use this module, as it needs special ppp scripts for establishing
	  a connection. Further documentation and the necessary scripts can be
	  found at:

	  <http://www.jacksonville.net/~fventuri/>
	  <http://home.adelphia.net/~siglercm/sb1000.html>
	  <http://linuxpower.cx/~cable/>

	  If you don't have this card, of course say N.

source "drivers/net/phy/Kconfig"

source "drivers/net/plip/Kconfig"

source "drivers/net/ppp/Kconfig"

source "drivers/net/slip/Kconfig"

source "drivers/s390/net/Kconfig"

source "drivers/net/usb/Kconfig"

source "drivers/net/wireless/Kconfig"

source "drivers/net/wimax/Kconfig"

source "drivers/net/wan/Kconfig"

source "drivers/net/ieee802154/Kconfig"

config XEN_NETDEV_FRONTEND
	tristate "Xen network device frontend driver"
	depends on XEN
	select XEN_XENBUS_FRONTEND
	default y
	help
	  This driver provides support for Xen paravirtual network
	  devices exported by a Xen network driver domain (often
	  domain 0).

	  The corresponding Linux backend driver is enabled by the
	  CONFIG_XEN_NETDEV_BACKEND option.

	  If you are compiling a kernel for use as Xen guest, you
	  should say Y here. To compile this driver as a module, chose
	  M here: the module will be called xen-netfront.

config XEN_NETDEV_BACKEND
	tristate "Xen backend network device"
	depends on XEN_BACKEND
	help
	  This driver allows the kernel to act as a Xen network driver
	  domain which exports paravirtual network devices to other
	  Xen domains. These devices can be accessed by any operating
	  system that implements a compatible front end.

	  The corresponding Linux frontend driver is enabled by the
	  CONFIG_XEN_NETDEV_FRONTEND configuration option.

	  The backend driver presents a standard network device
	  endpoint for each paravirtual network device to the driver
	  domain network stack. These can then be bridged or routed
	  etc in order to provide full network connectivity.

	  If you are compiling a kernel to run in a Xen network driver
	  domain (often this is domain 0) you should say Y here. To
	  compile this driver as a module, chose M here: the module
	  will be called xen-netback.

config VMXNET3
	tristate "VMware VMXNET3 ethernet driver"
	depends on PCI && INET
	depends on !(PAGE_SIZE_64KB || ARM64_64K_PAGES || \
		     IA64_PAGE_SIZE_64KB || MICROBLAZE_64K_PAGES || \
		     PARISC_PAGE_SIZE_64KB || PPC_64K_PAGES)
	help
	  This driver supports VMware's vmxnet3 virtual ethernet NIC.
	  To compile this driver as a module, choose M here: the
	  module will be called vmxnet3.

config FUJITSU_ES
	tristate "FUJITSU Extended Socket Network Device driver"
	depends on ACPI
	help
	  This driver provides support for Extended Socket network device
          on Extended Partitioning of FUJITSU PRIMEQUEST 2000 E2 series.

config THUNDERBOLT_NET
	tristate "Networking over Thunderbolt cable"
	depends on THUNDERBOLT && INET
	help
	  Select this if you want to create network between two
	  computers over a Thunderbolt cable. The driver supports Apple
	  ThunderboltIP protocol and allows communication with any host
	  supporting the same protocol including Windows and macOS.

	  To compile this driver a module, choose M here. The module will be
	  called thunderbolt-net.

source "drivers/net/hyperv/Kconfig"

config NETDEVSIM
	tristate "Simulated networking device"
	depends on DEBUG_FS
	depends on MAY_USE_DEVLINK
	help
	  This driver is a developer testing tool and software model that can
	  be used to test various control path networking APIs, especially
	  HW-offload related.

	  To compile this driver as a module, choose M here: the module
	  will be called netdevsim.

config NET_FAILOVER
	tristate "Failover driver"
	select FAILOVER
	help
	  This provides an automated failover mechanism via APIs to create
	  and destroy a failover master netdev and manages a primary and
	  standby slave netdevs that get registered via the generic failover
	  infrastructure. This can be used by paravirtual drivers to enable
	  an alternate low latency datapath. It alsoenables live migration of
	  a VM with direct attached VF by failing over to the paravirtual
	  datapath when the VF is unplugged.

endif # NETDEVICES
Commit	Line	Data
1da177e4 LT	1	#
	2	# Network device configuration
	3	#
	4
d1c0a65f	5	menuconfig NETDEVICES
ce2d2aed	6	default y if UML
e0009820	7	depends on NET
1da177e4 LT	8	bool "Network device support"
	9	---help---
	10	You can say N here if you don't intend to connect your Linux box to
	11	any other computer at all.
	12
	13	You'll have to say Y if your computer contains a network card that
	14	you want to use under Linux. If you are going to run SLIP or PPP over
	15	telephone line or null modem cable you need say Y here. Connecting
	16	two machines with parallel ports using PLIP needs this, as well as
	17	AX.25/KISS for sending Internet traffic over amateur radio links.
	18
	19	See also "The Linux Network Administrator's Guide" by Olaf Kirch and
	20	Terry Dawson. Available at <http://www.tldp.org/guides.html>.
	21
	22	If unsure, say Y.
	23
1618cb0c RD	24	# All the following symbols are dependent on NETDEVICES - do not repeat
	25	# that for each of the symbols.
	26	if NETDEVICES
cbcd2a4c	27
a1606c7d BH	28	config MII
	29	tristate
	30
88491d81 JK	31	config NET_CORE
	32	default y
	33	bool "Network core driver support"
253af423	34	---help---
88491d81 JK	35	You can say N here if you do not intend to use any of the
	36	networking core drivers (i.e. VLAN, bridging, bonding, etc.)
	37
	38	if NET_CORE
	39
	40	config BONDING
	41	tristate "Bonding driver support"
	42	depends on INET
	43	depends on IPV6 \|\| IPV6=n
	44	---help---
	45	Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
	46	Channels together. This is called 'Etherchannel' by Cisco,
	47	'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
	48
	49	The driver supports multiple bonding modes to allow for both high
	50	performance and high availability operation.
	51
	52	Refer to <file:Documentation/networking/bonding.txt> for more
	53	information.
	54
253af423	55	To compile this driver as a module, choose M here: the module
88491d81	56	will be called bonding.
253af423	57
1da177e4 LT	58	config DUMMY
1da177e4 LT	59	tristate "Dummy net driver support"
1da177e4 LT	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
	63	address. It is most commonly used in order to make your currently
	64	inactive SLIP address seem like a real address for local programs.
9f5db535 IB	65	If you use SLIP or PPP, you might want to say Y here. It won't
9f5db535 IB	66	enlarge your kernel. What a deal. Read about it in the Network
1da177e4 LT	67	Administrator's Guide, available from
	68	<http://www.tldp.org/docs.html#guide>.
	69
	70	To compile this driver as a module, choose M here: the module
9f486619	71	will be called dummy.
1da177e4	72
88491d81 JK	73	config EQUALIZER
88491d81 JK	74	tristate "EQL (serial line load balancing) support"
1da177e4	75	---help---
88491d81 JK	76	If you have two serial connections to some other computer (this
	77	usually requires two modems and two telephone lines) and you use
	78	SLIP (the protocol for sending Internet traffic over telephone
	79	lines) or PPP (a better SLIP) on them, you can make them behave like
	80	one double speed connection using this driver. Naturally, this has
	81	to be supported at the other end as well, either with a similar EQL
	82	Linux driver or with a Livingston Portmaster 2e.
1da177e4	83
88491d81 JK	84	Say Y if you want this and read
	85	<file:Documentation/networking/eql.txt>. You may also want to read
	86	section 6.2 of the NET-3-HOWTO, available from
	87	<http://www.tldp.org/docs.html#howto>.
1da177e4	88
88491d81 JK	89	To compile this driver as a module, choose M here: the module
	90	will be called eql. If unsure, say N.
	91
	92	config NET_FC
	93	bool "Fibre Channel driver support"
	94	depends on SCSI && PCI
	95	help
	96	Fibre Channel is a high speed serial protocol mainly used to connect
	97	large storage devices to the computer; it is compatible with and
	98	intended to replace SCSI.
	99
	100	If you intend to use Fibre Channel, you need to have a Fibre channel
	101	adaptor card in your computer; say Y here and to the driver for your
	102	adaptor below. You also should have said Y to "SCSI support" and
	103	"SCSI generic support".
1da177e4	104
88491d81 JK	105	config IFB
	106	tristate "Intermediate Functional Block support"
	107	depends on NET_CLS_ACT
	108	---help---
	109	This is an intermediate driver that allows sharing of
	110	resources.
1da177e4	111	To compile this driver as a module, choose M here: the module
88491d81 JK	112	will be called ifb. If you want to use more than one ifb
	113	device at a time, you need to compile this driver as a module.
	114	Instead of 'ifb', the devices will then be called 'ifb0',
	115	'ifb1' etc.
	116	Look at the iproute2 documentation directory for usage etc
1da177e4	117
3d249d4c JP	118	source "drivers/net/team/Kconfig"
3d249d4c JP	119
b863ceb7	120	config MACVLAN
bd085b93	121	tristate "MAC-VLAN support"
b863ceb7 PM	122	---help---
	123	This allows one to create virtual interfaces that map packets to
	124	or from specific MAC addresses to a particular interface.
	125
3dbf8d56 PM	126	Macvlan devices can be added using the "ip" command from the
	127	iproute2 package starting with the iproute2-2.6.23 release:
	128
	129	"ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
	130
b863ceb7 PM	131	To compile this driver as a module, choose M here: the module
	132	will be called macvlan.
	133
20d29d7a	134	config MACVTAP
bd085b93	135	tristate "MAC-VLAN based tap driver"
20d29d7a	136	depends on MACVLAN
de11b0e8	137	depends on INET
9a393b5d	138	select TAP
20d29d7a AB	139	help
	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
c7966b52	143	macvtap', and then be accessed through the tap user space interface.
20d29d7a AB	144
	145	To compile this driver as a module, choose M here: the module
	146	will be called macvtap.
	147
2ad7bf36 MB	148
	149	config IPVLAN
	150	tristate "IP-VLAN support"
265de6d1	151	depends on INET
7f897db3	152	depends on IPV6 \|\| !IPV6
cf714ac1	153	depends on NETFILTER
218798f4	154	select NET_L3_MASTER_DEV
2ad7bf36 MB	155	---help---
	156	This allows one to create virtual devices off of a main interface
	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
	159	making it transparent to the connected L2 switch.
	160
	161	Ipvlan devices can be added using the "ip" command from the
f4c2b7a0	162	iproute2 package starting with the iproute2-3.19 release:
2ad7bf36 MB	163
	164	"ip link add link <main-dev> [ NAME ] type ipvlan"
	165
	166	To compile this driver as a module, choose M here: the module
	167	will be called ipvlan.
	168
235a9d89 SG	169	config IPVTAP
	170	tristate "IP-VLAN based tap driver"
	171	depends on IPVLAN
	172	depends on INET
	173	select TAP
	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
	178	ipvtap', and then be accessed through the tap user space interface.
	179
	180	To compile this driver as a module, choose M here: the module
	181	will be called ipvtap.
2ad7bf36	182
d342894c	183	config VXLAN
d342894c	184	tristate "Virtual eXtensible Local Area Network (VXLAN)"
c9b20a5e	185	depends on INET
3ee64f39	186	select NET_UDP_TUNNEL
97e219b7	187	select GRO_CELLS
d342894c	188	---help---
	189	This allows one to create vxlan virtual interfaces that provide
	190	Layer 2 Networks over Layer 3 Networks. VXLAN is often used
	191	to tunnel virtual network infrastructure in virtualized environments.
	192	For more information see:
	193	http://tools.ietf.org/html/draft-mahalingam-dutt-dcops-vxlan-02
	194
	195	To compile this driver as a module, choose M here: the module
	196	will be called vxlan.
	197
2d07dc79	198	config GENEVE
371bd106 PS	199	tristate "Generic Network Virtualization Encapsulation"
371bd106 PS	200	depends on INET && NET_UDP_TUNNEL
094be092	201	depends on IPV6 \|\| !IPV6
2d07dc79	202	select NET_IP_TUNNEL
97e219b7	203	select GRO_CELLS
2d07dc79 JL	204	---help---
	205	This allows one to create geneve virtual interfaces that provide
	206	Layer 2 Networks over Layer 3 Networks. GENEVE is often used
	207	to tunnel virtual network infrastructure in virtualized environments.
	208	For more information see:
	209	http://tools.ietf.org/html/draft-gross-geneve-02
	210
	211	To compile this driver as a module, choose M here: the module
	212	will be called geneve.
	213
459aa660 PN	214	config GTP
	215	tristate "GPRS Tunneling Protocol datapath (GTP-U)"
	216	depends on INET && NET_UDP_TUNNEL
	217	select NET_IP_TUNNEL
	218	---help---
	219	This allows one to create gtp virtual interfaces that provide
	220	the GPRS Tunneling Protocol datapath (GTP-U). This tunneling protocol
	221	is used to prevent subscribers from accessing mobile carrier core
	222	network infrastructure. This driver requires a userspace software that
	223	implements the signaling protocol (GTP-C) to update its PDP context
	224	base, such as OpenGGSN <http://git.osmocom.org/openggsn/). This
	225	tunneling protocol is implemented according to the GSM TS 09.60 and
	226	3GPP TS 29.060 standards.
	227
	228	To compile this drivers as a module, choose M here: the module
	229	wil be called gtp.
	230
c09440f7 SD	231	config MACSEC
c09440f7 SD	232	tristate "IEEE 802.1AE MAC-level encryption (MACsec)"
ab2ed017	233	select CRYPTO
c09440f7 SD	234	select CRYPTO_AES
c09440f7 SD	235	select CRYPTO_GCM
97e219b7	236	select GRO_CELLS
c09440f7 SD	237	---help---
	238	MACsec is an encryption standard for Ethernet.
	239
88491d81 JK	240	config NETCONSOLE
88491d81 JK	241	tristate "Network console logging support"
1da177e4	242	---help---
88491d81 JK	243	If you want to log kernel messages over the network, enable this.
88491d81 JK	244	See <file:Documentation/networking/netconsole.txt> for details.
1da177e4	245
88491d81 JK	246	config NETCONSOLE_DYNAMIC
	247	bool "Dynamic reconfiguration of logging targets"
	248	depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
	249	!(NETCONSOLE=y && CONFIGFS_FS=m)
	250	help
	251	This option enables the ability to dynamically reconfigure target
	252	parameters (interface, IP addresses, port numbers, MAC addresses)
	253	at runtime through a userspace interface exported using configfs.
	254	See <file:Documentation/networking/netconsole.txt> for details.
1da177e4	255
88491d81 JK	256	config NETPOLL
88491d81 JK	257	def_bool NETCONSOLE
83fe27ea	258	select SRCU
88491d81	259
88491d81 JK	260	config NET_POLL_CONTROLLER
	261	def_bool NETPOLL
	262
548c237c	263	config NTB_NETDEV
ec110bc7 AH	264	tristate "Virtual Ethernet over NTB Transport"
ec110bc7 AH	265	depends on NTB_TRANSPORT
548c237c	266
88491d81 JK	267	config RIONET
	268	tristate "RapidIO Ethernet over messaging driver support"
	269	depends on RAPIDIO
	270
	271	config RIONET_TX_SIZE
	272	int "Number of outbound queue entries"
	273	depends on RIONET
	274	default "128"
	275
	276	config RIONET_RX_SIZE
	277	int "Number of inbound queue entries"
	278	depends on RIONET
	279	default "128"
1da177e4 LT	280
	281	config TUN
	282	tristate "Universal TUN/TAP device driver support"
de11b0e8	283	depends on INET
1da177e4 LT	284	select CRC32
	285	---help---
	286	TUN/TAP provides packet reception and transmission for user space
	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,
	289	receives them from user space program and instead of sending packets
	290	via physical media writes them to the user space program.
	291
	292	When a program opens /dev/net/tun, driver creates and registers
	293	corresponding net device tunX or tapX. After a program closed above
	294	devices, driver will automatically delete tunXX or tapXX device and
	295	all routes corresponding to it.
	296
	297	Please read <file:Documentation/networking/tuntap.txt> for more
	298	information.
	299
	300	To compile this driver as a module, choose M here: the module
	301	will be called tun.
	302
	303	If you don't know what to use this for, you don't need it.
	304
9a393b5d SG	305	config TAP
	306	tristate
	307	---help---
	308	This option is selected by any driver implementing tap user space
	309	interface for a virtual interface to re-use core tap functionality.
	310
8b8e658b GK	311	config TUN_VNET_CROSS_LE
	312	bool "Support for cross-endian vnet headers on little-endian kernels"
	313	default n
	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.
	318
	319	Userspace programs can control the feature using the TUNSETVNETBE
	320	and TUNGETVNETBE ioctls.
	321
	322	Unless you have a little-endian system hosting a big-endian virtual
	323	machine with a legacy virtio NIC, you should say N.
	324
e314dbdc	325	config VETH
6a9a0250	326	tristate "Virtual ethernet pair device"
e314dbdc	327	---help---
6a9a0250 RR	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
	330	versa.
e314dbdc	331
88491d81	332	config VIRTIO_NET
bd085b93 KC	333	tristate "Virtio network driver"
bd085b93 KC	334	depends on VIRTIO
ba5e4426	335	select NET_FAILOVER
88491d81 JK	336	---help---
88491d81 JK	337	This is the virtual network driver for virtio. It can be used with
ecda85e7	338	QEMU based VMMs (like KVM or Xen). Say Y or M.
88491d81	339
e4fc408e DB	340	config NLMON
	341	tristate "Virtual netlink monitoring device"
	342	---help---
	343	This option enables a monitoring net device for netlink skbs. The
	344	purpose of this is to analyze netlink messages with packet sockets.
	345	Thus applications like tcpdump will be able to see local netlink
	346	messages if they tap into the netlink device, record pcaps for further
	347	diagnostics, etc. This is mostly intended for developers or support
	348	to debug netlink issues. If unsure, say N.
	349
193125db DA	350	config NET_VRF
193125db DA	351	tristate "Virtual Routing and Forwarding (Lite)"
35402e31	352	depends on IP_MULTIPLE_TABLES
ee15ee5d	353	depends on NET_L3_MASTER_DEV
35402e31 DA	354	depends on IPV6 \|\| IPV6=n
35402e31 DA	355	depends on IPV6_MULTIPLE_TABLES \|\| IPV6=n
193125db DA	356	---help---
	357	This option enables the support for mapping interfaces into VRF's. The
	358	support enables VRF devices.
	359
0b2e6644 GG	360	config VSOCKMON
	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
	365	mostly intended for developers or support to debug vsock issues. If
	366	unsure, say N.
	367
88491d81 JK	368	endif # NET_CORE
	369
	370	config SUNGEM_PHY
	371	tristate
	372
	373	source "drivers/net/arcnet/Kconfig"
	374
	375	source "drivers/atm/Kconfig"
	376
	377	source "drivers/net/caif/Kconfig"
	378
3b158859 BH	379	source "drivers/net/dsa/Kconfig"
3b158859 BH	380
88491d81 JK	381	source "drivers/net/ethernet/Kconfig"
	382
	383	source "drivers/net/fddi/Kconfig"
	384
fecc7351 PB	385	source "drivers/net/hippi/Kconfig"
fecc7351 PB	386
1da177e4 LT	387	config NET_SB1000
1da177e4 LT	388	tristate "General Instruments Surfboard 1000"
cbcd2a4c	389	depends on PNP
1da177e4 LT	390	---help---
	391	This is a driver for the General Instrument (also known as
	392	NextLevel) SURFboard 1000 internal
	393	cable modem. This is an ISA card which is used by a number of cable
	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
	396	provided by your regular phone modem.
	397
	398	At present this driver only compiles as a module, so say M here if
	399	you have this card. The module will be called sb1000. Then read
	400	<file:Documentation/networking/README.sb1000> for information on how
	401	to use this module, as it needs special ppp scripts for establishing
	402	a connection. Further documentation and the necessary scripts can be
	403	found at:
	404
	405	<http://www.jacksonville.net/~fventuri/>
	406	<http://home.adelphia.net/~siglercm/sb1000.html>
	407	<http://linuxpower.cx/~cable/>
	408
	409	If you don't have this card, of course say N.
	410
00db8189 AF	411	source "drivers/net/phy/Kconfig"
00db8189 AF	412
18e635f4 JK	413	source "drivers/net/plip/Kconfig"
18e635f4 JK	414
88491d81 JK	415	source "drivers/net/ppp/Kconfig"
88491d81 JK	416
b5451d78 JK	417	source "drivers/net/slip/Kconfig"
b5451d78 JK	418
88491d81 JK	419	source "drivers/s390/net/Kconfig"
88491d81 JK	420
88491d81 JK	421	source "drivers/net/usb/Kconfig"
88491d81 JK	422
1da177e4 LT	423	source "drivers/net/wireless/Kconfig"
1da177e4 LT	424
143ee2d5 IPG	425	source "drivers/net/wimax/Kconfig"
143ee2d5 IPG	426
1da177e4 LT	427	source "drivers/net/wan/Kconfig"
1da177e4 LT	428
0739d643	429	source "drivers/net/ieee802154/Kconfig"
0739d643	430
0d160211 JF	431	config XEN_NETDEV_FRONTEND
	432	tristate "Xen network device frontend driver"
	433	depends on XEN
7003087c	434	select XEN_XENBUS_FRONTEND
0d160211 JF	435	default y
0d160211 JF	436	help
f942dc25 IC	437	This driver provides support for Xen paravirtual network
	438	devices exported by a Xen network driver domain (often
	439	domain 0).
	440
	441	The corresponding Linux backend driver is enabled by the
	442	CONFIG_XEN_NETDEV_BACKEND option.
	443
	444	If you are compiling a kernel for use as Xen guest, you
	445	should say Y here. To compile this driver as a module, chose
	446	M here: the module will be called xen-netfront.
	447
	448	config XEN_NETDEV_BACKEND
	449	tristate "Xen backend network device"
	450	depends on XEN_BACKEND
	451	help
	452	This driver allows the kernel to act as a Xen network driver
	453	domain which exports paravirtual network devices to other
	454	Xen domains. These devices can be accessed by any operating
	455	system that implements a compatible front end.
	456
	457	The corresponding Linux frontend driver is enabled by the
	458	CONFIG_XEN_NETDEV_FRONTEND configuration option.
	459
	460	The backend driver presents a standard network device
	461	endpoint for each paravirtual network device to the driver
	462	domain network stack. These can then be bridged or routed
	463	etc in order to provide full network connectivity.
	464
	465	If you are compiling a kernel to run in a Xen network driver
	466	domain (often this is domain 0) you should say Y here. To
	467	compile this driver as a module, chose M here: the module
	468	will be called xen-netback.
0d160211	469
d1a890fa	470	config VMXNET3
e85eb117 PDM	471	tristate "VMware VMXNET3 ethernet driver"
e85eb117 PDM	472	depends on PCI && INET
fbdf0e28 AB	473	depends on !(PAGE_SIZE_64KB \|\| ARM64_64K_PAGES \|\| \
	474	IA64_PAGE_SIZE_64KB \|\| MICROBLAZE_64K_PAGES \|\| \
	475	PARISC_PAGE_SIZE_64KB \|\| PPC_64K_PAGES)
e85eb117 PDM	476	help
	477	This driver supports VMware's vmxnet3 virtual ethernet NIC.
	478	To compile this driver as a module, choose M here: the
	479	module will be called vmxnet3.
d1a890fa	480
658d439b TI	481	config FUJITSU_ES
	482	tristate "FUJITSU Extended Socket Network Device driver"
	483	depends on ACPI
	484	help
	485	This driver provides support for Extended Socket network device
	486	on Extended Partitioning of FUJITSU PRIMEQUEST 2000 E2 series.
	487
e69b6c02 AL	488	config THUNDERBOLT_NET
	489	tristate "Networking over Thunderbolt cable"
	490	depends on THUNDERBOLT && INET
	491	help
	492	Select this if you want to create network between two
	493	computers over a Thunderbolt cable. The driver supports Apple
	494	ThunderboltIP protocol and allows communication with any host
	495	supporting the same protocol including Windows and macOS.
	496
	497	To compile this driver a module, choose M here. The module will be
	498	called thunderbolt-net.
	499
95fa0405 HZ	500	source "drivers/net/hyperv/Kconfig"
95fa0405 HZ	501
83c9e13a JK	502	config NETDEVSIM
	503	tristate "Simulated networking device"
	504	depends on DEBUG_FS
37923ed6	505	depends on MAY_USE_DEVLINK
83c9e13a JK	506	help
	507	This driver is a developer testing tool and software model that can
	508	be used to test various control path networking APIs, especially
	509	HW-offload related.
	510
	511	To compile this driver as a module, choose M here: the module
	512	will be called netdevsim.
	513
cfc80d9a SS	514	config NET_FAILOVER
	515	tristate "Failover driver"
	516	select FAILOVER
	517	help
	518	This provides an automated failover mechanism via APIs to create
	519	and destroy a failover master netdev and manages a primary and
	520	standby slave netdevs that get registered via the generic failover
	521	infrastructure. This can be used by paravirtual drivers to enable
	522	an alternate low latency datapath. It alsoenables live migration of
	523	a VM with direct attached VF by failing over to the paravirtual
	524	datapath when the VF is unplugged.
	525
d1c0a65f	526	endif # NETDEVICES