xref: /openbmc/linux/drivers/net/Kconfig (revision ba61bb17)
1#
2# Network device configuration
3#
4
5menuconfig NETDEVICES
6	default y if UML
7	depends on NET
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
24# All the following symbols are dependent on NETDEVICES - do not repeat
25# that for each of the symbols.
26if NETDEVICES
27
28config MII
29	tristate
30
31config NET_CORE
32	default y
33	bool "Network core driver support"
34	---help---
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
38if NET_CORE
39
40config 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
55	  To compile this driver as a module, choose M here: the module
56	  will be called bonding.
57
58config DUMMY
59	tristate "Dummy net driver support"
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.
65	  If you use SLIP or PPP, you might want to say Y here. It won't
66	  enlarge your kernel. What a deal. Read about it in the Network
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
71	  will be called dummy.
72
73config EQUALIZER
74	tristate "EQL (serial line load balancing) support"
75	---help---
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.
83
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>.
88
89	  To compile this driver as a module, choose M here: the module
90	  will be called eql.  If unsure, say N.
91
92config 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".
104
105config 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.
111	  To compile this driver as a module, choose M here: the module
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
117
118source "drivers/net/team/Kconfig"
119
120config MACVLAN
121	tristate "MAC-VLAN support"
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
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
131	  To compile this driver as a module, choose M here: the module
132	  will be called macvlan.
133
134config MACVTAP
135	tristate "MAC-VLAN based tap driver"
136	depends on MACVLAN
137	depends on INET
138	select TAP
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
143	  macvtap', and then be accessed through the tap user space interface.
144
145	  To compile this driver as a module, choose M here: the module
146	  will be called macvtap.
147
148
149config IPVLAN
150    tristate "IP-VLAN support"
151    depends on INET
152    depends on IPV6 || !IPV6
153    depends on NETFILTER
154    select NET_L3_MASTER_DEV
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
162      iproute2 package starting with the iproute2-3.19 release:
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
169config 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.
182
183config VXLAN
184       tristate "Virtual eXtensible Local Area Network (VXLAN)"
185       depends on INET
186       select NET_UDP_TUNNEL
187       select GRO_CELLS
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
198config GENEVE
199       tristate "Generic Network Virtualization Encapsulation"
200       depends on INET && NET_UDP_TUNNEL
201       depends on IPV6 || !IPV6
202       select NET_IP_TUNNEL
203       select GRO_CELLS
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
214config 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
231config MACSEC
232	tristate "IEEE 802.1AE MAC-level encryption (MACsec)"
233	select CRYPTO
234	select CRYPTO_AES
235	select CRYPTO_GCM
236	select GRO_CELLS
237	---help---
238	   MACsec is an encryption standard for Ethernet.
239
240config NETCONSOLE
241	tristate "Network console logging support"
242	---help---
243	If you want to log kernel messages over the network, enable this.
244	See <file:Documentation/networking/netconsole.txt> for details.
245
246config 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.
255
256config NETPOLL
257	def_bool NETCONSOLE
258	select SRCU
259
260config NET_POLL_CONTROLLER
261	def_bool NETPOLL
262
263config NTB_NETDEV
264	tristate "Virtual Ethernet over NTB Transport"
265	depends on NTB_TRANSPORT
266
267config RIONET
268	tristate "RapidIO Ethernet over messaging driver support"
269	depends on RAPIDIO
270
271config RIONET_TX_SIZE
272	int "Number of outbound queue entries"
273	depends on RIONET
274	default "128"
275
276config RIONET_RX_SIZE
277	int "Number of inbound queue entries"
278	depends on RIONET
279	default "128"
280
281config TUN
282	tristate "Universal TUN/TAP device driver support"
283	depends on INET
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
305config 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
311config 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
325config VETH
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
330	  versa.
331
332config VIRTIO_NET
333	tristate "Virtio network driver"
334	depends on VIRTIO
335	select NET_FAILOVER
336	---help---
337	  This is the virtual network driver for virtio.  It can be used with
338	  QEMU based VMMs (like KVM or Xen).  Say Y or M.
339
340config 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
350config NET_VRF
351	tristate "Virtual Routing and Forwarding (Lite)"
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---
357	  This option enables the support for mapping interfaces into VRF's. The
358	  support enables VRF devices.
359
360config 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
368endif # NET_CORE
369
370config SUNGEM_PHY
371	tristate
372
373source "drivers/net/arcnet/Kconfig"
374
375source "drivers/atm/Kconfig"
376
377source "drivers/net/caif/Kconfig"
378
379source "drivers/net/dsa/Kconfig"
380
381source "drivers/net/ethernet/Kconfig"
382
383source "drivers/net/fddi/Kconfig"
384
385source "drivers/net/hippi/Kconfig"
386
387config NET_SB1000
388	tristate "General Instruments Surfboard 1000"
389	depends on PNP
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
411source "drivers/net/phy/Kconfig"
412
413source "drivers/net/plip/Kconfig"
414
415source "drivers/net/ppp/Kconfig"
416
417source "drivers/net/slip/Kconfig"
418
419source "drivers/s390/net/Kconfig"
420
421source "drivers/net/usb/Kconfig"
422
423source "drivers/net/wireless/Kconfig"
424
425source "drivers/net/wimax/Kconfig"
426
427source "drivers/net/wan/Kconfig"
428
429source "drivers/net/ieee802154/Kconfig"
430
431config XEN_NETDEV_FRONTEND
432	tristate "Xen network device frontend driver"
433	depends on XEN
434	select XEN_XENBUS_FRONTEND
435	default y
436	help
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
448config 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.
469
470config VMXNET3
471	tristate "VMware VMXNET3 ethernet driver"
472	depends on PCI && INET
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)
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.
480
481config 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
488config 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
500source "drivers/net/hyperv/Kconfig"
501
502config NETDEVSIM
503	tristate "Simulated networking device"
504	depends on DEBUG_FS
505	depends on MAY_USE_DEVLINK
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
514config 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
526endif # NETDEVICES
527