blob: db28e22edbf96a9f6a0525f1ea48ae6bd2924266 [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001#
2# Network device configuration
3#
4
Jan Engelhardtd1c0a652007-06-13 12:48:53 -07005menuconfig NETDEVICES
Paolo 'Blaisorblade' Giarrussoce2d2ae2006-01-18 17:42:59 -08006 default y if UML
Jan Engelhardte0009822007-07-21 19:11:35 -07007 depends on NET
Linus Torvalds1da177e2005-04-16 15:20:36 -07008 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
Randy Dunlap1618cb02006-09-25 23:11:21 -070024# All the following symbols are dependent on NETDEVICES - do not repeat
25# that for each of the symbols.
26if NETDEVICES
Randy Dunlapcbcd2a42005-07-27 13:04:35 -070027
Ben Hutchingsa1606c72013-06-18 03:24:51 +010028config MII
29 tristate
30
Jeff Kirsher88491d82011-08-23 00:42:10 -070031config NET_CORE
32 default y
33 bool "Network core driver support"
Jamal Hadi Salim253af422006-01-08 22:34:25 -080034 ---help---
Jeff Kirsher88491d82011-08-23 00:42:10 -070035 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
Jamal Hadi Salim253af422006-01-08 22:34:25 -080055 To compile this driver as a module, choose M here: the module
Jeff Kirsher88491d82011-08-23 00:42:10 -070056 will be called bonding.
Jamal Hadi Salim253af422006-01-08 22:34:25 -080057
Linus Torvalds1da177e2005-04-16 15:20:36 -070058config DUMMY
59 tristate "Dummy net driver support"
Linus Torvalds1da177e2005-04-16 15:20:36 -070060 ---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.
Ivan Babrou9f5db532016-04-23 12:58:03 +000065 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
Linus Torvalds1da177e2005-04-16 15:20:36 -070067 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
Alan Cox9f486612012-05-14 03:57:31 +000071 will be called dummy.
Linus Torvalds1da177e2005-04-16 15:20:36 -070072
Jeff Kirsher88491d82011-08-23 00:42:10 -070073config EQUALIZER
74 tristate "EQL (serial line load balancing) support"
Linus Torvalds1da177e2005-04-16 15:20:36 -070075 ---help---
Jeff Kirsher88491d82011-08-23 00:42:10 -070076 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.
Linus Torvalds1da177e2005-04-16 15:20:36 -070083
Jeff Kirsher88491d82011-08-23 00:42:10 -070084 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>.
Linus Torvalds1da177e2005-04-16 15:20:36 -070088
89 To compile this driver as a module, choose M here: the module
Jeff Kirsher88491d82011-08-23 00:42:10 -070090 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
Jeff Kirsher88491d82011-08-23 00:42:10 -0700105config 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
Linus Torvalds1da177e2005-04-16 15:20:36 -0700117
Jiri Pirko3d249d42011-11-11 22:16:48 +0000118source "drivers/net/team/Kconfig"
119
Patrick McHardyb863ceb2007-07-14 18:55:06 -0700120config MACVLAN
Kees Cookbd085b92012-10-02 11:17:55 -0700121 tristate "MAC-VLAN support"
Patrick McHardyb863ceb2007-07-14 18:55:06 -0700122 ---help---
123 This allows one to create virtual interfaces that map packets to
124 or from specific MAC addresses to a particular interface.
125
Patrick McHardy3dbf8d52008-02-26 17:52:05 -0800126 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
Patrick McHardyb863ceb2007-07-14 18:55:06 -0700131 To compile this driver as a module, choose M here: the module
132 will be called macvlan.
133
Arnd Bergmann20d29d72010-01-30 12:24:26 +0000134config MACVTAP
Kees Cookbd085b92012-10-02 11:17:55 -0700135 tristate "MAC-VLAN based tap driver"
Arnd Bergmann20d29d72010-01-30 12:24:26 +0000136 depends on MACVLAN
Ben Hutchingsde11b0e2014-10-31 03:10:31 +0000137 depends on INET
Arnd Bergmann20d29d72010-01-30 12:24:26 +0000138 help
139 This adds a specialized tap character device driver that is based
140 on the MAC-VLAN network interface, called macvtap. A macvtap device
141 can be added in the same way as a macvlan device, using 'type
Jan Luebbec7966b52014-02-10 21:40:51 +0100142 macvtap', and then be accessed through the tap user space interface.
Arnd Bergmann20d29d72010-01-30 12:24:26 +0000143
144 To compile this driver as a module, choose M here: the module
145 will be called macvtap.
146
Mahesh Bandewar2ad7bf32014-11-23 23:07:46 -0800147
148config IPVLAN
149 tristate "IP-VLAN support"
Mahesh Bandewar265de6d2014-11-26 21:13:45 -0800150 depends on INET
151 depends on IPV6
Mahesh Bandewarcf714ac2016-09-19 13:56:29 -0700152 depends on NETFILTER
Mahesh Bandewar4fbae7d2016-09-16 12:59:19 -0700153 depends on NET_L3_MASTER_DEV
Mahesh Bandewar2ad7bf32014-11-23 23:07:46 -0800154 ---help---
155 This allows one to create virtual devices off of a main interface
156 and packets will be delivered based on the dest L3 (IPv6/IPv4 addr)
157 on packets. All interfaces (including the main interface) share L2
158 making it transparent to the connected L2 switch.
159
160 Ipvlan devices can be added using the "ip" command from the
Mahesh Bandewarf4c2b7a2015-02-18 15:15:57 -0800161 iproute2 package starting with the iproute2-3.19 release:
Mahesh Bandewar2ad7bf32014-11-23 23:07:46 -0800162
163 "ip link add link <main-dev> [ NAME ] type ipvlan"
164
165 To compile this driver as a module, choose M here: the module
166 will be called ipvlan.
167
168
stephen hemmingerd3428942012-10-01 12:32:35 +0000169config VXLAN
170 tristate "Virtual eXtensible Local Area Network (VXLAN)"
Kees Cookc9b20a52013-02-22 21:25:38 +0000171 depends on INET
Tom Herbert3ee64f32014-07-13 19:49:42 -0700172 select NET_UDP_TUNNEL
stephen hemmingerd3428942012-10-01 12:32:35 +0000173 ---help---
174 This allows one to create vxlan virtual interfaces that provide
175 Layer 2 Networks over Layer 3 Networks. VXLAN is often used
176 to tunnel virtual network infrastructure in virtualized environments.
177 For more information see:
178 http://tools.ietf.org/html/draft-mahalingam-dutt-dcops-vxlan-02
179
180 To compile this driver as a module, choose M here: the module
181 will be called vxlan.
182
John W. Linville2d07dc72015-05-13 12:57:30 -0400183config GENEVE
Pravin B Shelar371bd102015-08-26 23:46:54 -0700184 tristate "Generic Network Virtualization Encapsulation"
185 depends on INET && NET_UDP_TUNNEL
John W. Linville2d07dc72015-05-13 12:57:30 -0400186 select NET_IP_TUNNEL
187 ---help---
188 This allows one to create geneve virtual interfaces that provide
189 Layer 2 Networks over Layer 3 Networks. GENEVE is often used
190 to tunnel virtual network infrastructure in virtualized environments.
191 For more information see:
192 http://tools.ietf.org/html/draft-gross-geneve-02
193
194 To compile this driver as a module, choose M here: the module
195 will be called geneve.
196
Pablo Neira459aa662016-05-09 00:55:48 +0200197config GTP
198 tristate "GPRS Tunneling Protocol datapath (GTP-U)"
199 depends on INET && NET_UDP_TUNNEL
200 select NET_IP_TUNNEL
201 ---help---
202 This allows one to create gtp virtual interfaces that provide
203 the GPRS Tunneling Protocol datapath (GTP-U). This tunneling protocol
204 is used to prevent subscribers from accessing mobile carrier core
205 network infrastructure. This driver requires a userspace software that
206 implements the signaling protocol (GTP-C) to update its PDP context
207 base, such as OpenGGSN <http://git.osmocom.org/openggsn/). This
208 tunneling protocol is implemented according to the GSM TS 09.60 and
209 3GPP TS 29.060 standards.
210
211 To compile this drivers as a module, choose M here: the module
212 wil be called gtp.
213
Sabrina Dubrocac09440f2016-03-11 18:07:33 +0100214config MACSEC
215 tristate "IEEE 802.1AE MAC-level encryption (MACsec)"
Arnd Bergmannab2ed012016-04-17 11:19:55 +0200216 select CRYPTO
Sabrina Dubrocac09440f2016-03-11 18:07:33 +0100217 select CRYPTO_AES
218 select CRYPTO_GCM
219 ---help---
220 MACsec is an encryption standard for Ethernet.
221
Jeff Kirsher88491d82011-08-23 00:42:10 -0700222config NETCONSOLE
223 tristate "Network console logging support"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700224 ---help---
Jeff Kirsher88491d82011-08-23 00:42:10 -0700225 If you want to log kernel messages over the network, enable this.
226 See <file:Documentation/networking/netconsole.txt> for details.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700227
Jeff Kirsher88491d82011-08-23 00:42:10 -0700228config NETCONSOLE_DYNAMIC
229 bool "Dynamic reconfiguration of logging targets"
230 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
231 !(NETCONSOLE=y && CONFIGFS_FS=m)
232 help
233 This option enables the ability to dynamically reconfigure target
234 parameters (interface, IP addresses, port numbers, MAC addresses)
235 at runtime through a userspace interface exported using configfs.
236 See <file:Documentation/networking/netconsole.txt> for details.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700237
Jeff Kirsher88491d82011-08-23 00:42:10 -0700238config NETPOLL
239 def_bool NETCONSOLE
Pranith Kumar83fe27e2014-12-05 11:24:45 -0500240 select SRCU
Jeff Kirsher88491d82011-08-23 00:42:10 -0700241
Jeff Kirsher88491d82011-08-23 00:42:10 -0700242config NET_POLL_CONTROLLER
243 def_bool NETPOLL
244
Jon Mason548c2372012-11-16 19:27:13 -0700245config NTB_NETDEV
Allen Hubbeec110bc2015-05-07 06:45:21 -0400246 tristate "Virtual Ethernet over NTB Transport"
247 depends on NTB_TRANSPORT
Jon Mason548c2372012-11-16 19:27:13 -0700248
Jeff Kirsher88491d82011-08-23 00:42:10 -0700249config RIONET
250 tristate "RapidIO Ethernet over messaging driver support"
251 depends on RAPIDIO
252
253config RIONET_TX_SIZE
254 int "Number of outbound queue entries"
255 depends on RIONET
256 default "128"
257
258config RIONET_RX_SIZE
259 int "Number of inbound queue entries"
260 depends on RIONET
261 default "128"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700262
263config TUN
264 tristate "Universal TUN/TAP device driver support"
Ben Hutchingsde11b0e2014-10-31 03:10:31 +0000265 depends on INET
Linus Torvalds1da177e2005-04-16 15:20:36 -0700266 select CRC32
267 ---help---
268 TUN/TAP provides packet reception and transmission for user space
269 programs. It can be viewed as a simple Point-to-Point or Ethernet
270 device, which instead of receiving packets from a physical media,
271 receives them from user space program and instead of sending packets
272 via physical media writes them to the user space program.
273
274 When a program opens /dev/net/tun, driver creates and registers
275 corresponding net device tunX or tapX. After a program closed above
276 devices, driver will automatically delete tunXX or tapXX device and
277 all routes corresponding to it.
278
279 Please read <file:Documentation/networking/tuntap.txt> for more
280 information.
281
282 To compile this driver as a module, choose M here: the module
283 will be called tun.
284
285 If you don't know what to use this for, you don't need it.
286
Greg Kurz8b8e6582015-04-24 14:50:36 +0200287config TUN_VNET_CROSS_LE
288 bool "Support for cross-endian vnet headers on little-endian kernels"
289 default n
290 ---help---
291 This option allows TUN/TAP and MACVTAP device drivers in a
292 little-endian kernel to parse vnet headers that come from a
293 big-endian legacy virtio device.
294
295 Userspace programs can control the feature using the TUNSETVNETBE
296 and TUNGETVNETBE ioctls.
297
298 Unless you have a little-endian system hosting a big-endian virtual
299 machine with a legacy virtio NIC, you should say N.
300
Pavel Emelyanove314dbd2007-09-25 16:14:46 -0700301config VETH
Rusty Russell6a9a0252007-11-06 20:35:55 -0800302 tristate "Virtual ethernet pair device"
Pavel Emelyanove314dbd2007-09-25 16:14:46 -0700303 ---help---
Rusty Russell6a9a0252007-11-06 20:35:55 -0800304 This device is a local ethernet tunnel. Devices are created in pairs.
305 When one end receives the packet it appears on its pair and vice
306 versa.
Pavel Emelyanove314dbd2007-09-25 16:14:46 -0700307
Jeff Kirsher88491d82011-08-23 00:42:10 -0700308config VIRTIO_NET
Kees Cookbd085b92012-10-02 11:17:55 -0700309 tristate "Virtio network driver"
310 depends on VIRTIO
Jeff Kirsher88491d82011-08-23 00:42:10 -0700311 ---help---
312 This is the virtual network driver for virtio. It can be used with
313 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
314
Daniel Borkmanne4fc4082013-06-21 19:38:08 +0200315config NLMON
316 tristate "Virtual netlink monitoring device"
317 ---help---
318 This option enables a monitoring net device for netlink skbs. The
319 purpose of this is to analyze netlink messages with packet sockets.
320 Thus applications like tcpdump will be able to see local netlink
321 messages if they tap into the netlink device, record pcaps for further
322 diagnostics, etc. This is mostly intended for developers or support
323 to debug netlink issues. If unsure, say N.
324
David Ahern193125d2015-08-13 14:59:10 -0600325config NET_VRF
326 tristate "Virtual Routing and Forwarding (Lite)"
David Ahern35402e32015-10-12 11:47:09 -0700327 depends on IP_MULTIPLE_TABLES
David Ahernee15ee52015-09-29 20:07:12 -0700328 depends on NET_L3_MASTER_DEV
David Ahern35402e32015-10-12 11:47:09 -0700329 depends on IPV6 || IPV6=n
330 depends on IPV6_MULTIPLE_TABLES || IPV6=n
David Ahern193125d2015-08-13 14:59:10 -0600331 ---help---
332 This option enables the support for mapping interfaces into VRF's. The
333 support enables VRF devices.
334
Jeff Kirsher88491d82011-08-23 00:42:10 -0700335endif # NET_CORE
336
337config SUNGEM_PHY
338 tristate
339
340source "drivers/net/arcnet/Kconfig"
341
342source "drivers/atm/Kconfig"
343
344source "drivers/net/caif/Kconfig"
345
Ben Hutchings3b158852011-11-27 17:08:33 +0000346source "drivers/net/dsa/Kconfig"
347
Jeff Kirsher88491d82011-08-23 00:42:10 -0700348source "drivers/net/ethernet/Kconfig"
349
350source "drivers/net/fddi/Kconfig"
351
Paul Bollefecc7352011-11-08 10:31:10 +0000352source "drivers/net/hippi/Kconfig"
353
Linus Torvalds1da177e2005-04-16 15:20:36 -0700354config NET_SB1000
355 tristate "General Instruments Surfboard 1000"
Randy Dunlapcbcd2a42005-07-27 13:04:35 -0700356 depends on PNP
Linus Torvalds1da177e2005-04-16 15:20:36 -0700357 ---help---
358 This is a driver for the General Instrument (also known as
359 NextLevel) SURFboard 1000 internal
360 cable modem. This is an ISA card which is used by a number of cable
361 TV companies to provide cable modem access. It's a one-way
362 downstream-only cable modem, meaning that your upstream net link is
363 provided by your regular phone modem.
364
365 At present this driver only compiles as a module, so say M here if
366 you have this card. The module will be called sb1000. Then read
367 <file:Documentation/networking/README.sb1000> for information on how
368 to use this module, as it needs special ppp scripts for establishing
369 a connection. Further documentation and the necessary scripts can be
370 found at:
371
372 <http://www.jacksonville.net/~fventuri/>
373 <http://home.adelphia.net/~siglercm/sb1000.html>
374 <http://linuxpower.cx/~cable/>
375
376 If you don't have this card, of course say N.
377
Andy Fleming00db8182005-07-30 19:31:23 -0400378source "drivers/net/phy/Kconfig"
379
Jeff Kirsher18e635f2011-08-03 03:01:58 -0700380source "drivers/net/plip/Kconfig"
381
Jeff Kirsher88491d82011-08-23 00:42:10 -0700382source "drivers/net/ppp/Kconfig"
383
Jeff Kirsherb5451d72011-08-03 03:17:13 -0700384source "drivers/net/slip/Kconfig"
385
Jeff Kirsher88491d82011-08-23 00:42:10 -0700386source "drivers/s390/net/Kconfig"
387
Jeff Kirsher88491d82011-08-23 00:42:10 -0700388source "drivers/net/usb/Kconfig"
389
Linus Torvalds1da177e2005-04-16 15:20:36 -0700390source "drivers/net/wireless/Kconfig"
391
Inaky Perez-Gonzalez143ee2d2008-12-23 16:18:48 -0800392source "drivers/net/wimax/Kconfig"
393
Linus Torvalds1da177e2005-04-16 15:20:36 -0700394source "drivers/net/wan/Kconfig"
395
alex.bluesman.smirnov@gmail.com0739d642012-08-26 05:10:11 +0000396source "drivers/net/ieee802154/Kconfig"
397
Jeremy Fitzhardinge0d160212007-07-17 18:37:06 -0700398config XEN_NETDEV_FRONTEND
399 tristate "Xen network device frontend driver"
400 depends on XEN
Jeremy Fitzhardinge70030872009-03-27 16:28:34 -0700401 select XEN_XENBUS_FRONTEND
Jeremy Fitzhardinge0d160212007-07-17 18:37:06 -0700402 default y
403 help
Ian Campbellf942dc22011-03-15 00:06:18 +0000404 This driver provides support for Xen paravirtual network
405 devices exported by a Xen network driver domain (often
406 domain 0).
407
408 The corresponding Linux backend driver is enabled by the
409 CONFIG_XEN_NETDEV_BACKEND option.
410
411 If you are compiling a kernel for use as Xen guest, you
412 should say Y here. To compile this driver as a module, chose
413 M here: the module will be called xen-netfront.
414
415config XEN_NETDEV_BACKEND
416 tristate "Xen backend network device"
417 depends on XEN_BACKEND
418 help
419 This driver allows the kernel to act as a Xen network driver
420 domain which exports paravirtual network devices to other
421 Xen domains. These devices can be accessed by any operating
422 system that implements a compatible front end.
423
424 The corresponding Linux frontend driver is enabled by the
425 CONFIG_XEN_NETDEV_FRONTEND configuration option.
426
427 The backend driver presents a standard network device
428 endpoint for each paravirtual network device to the driver
429 domain network stack. These can then be bridged or routed
430 etc in order to provide full network connectivity.
431
432 If you are compiling a kernel to run in a Xen network driver
433 domain (often this is domain 0) you should say Y here. To
434 compile this driver as a module, chose M here: the module
435 will be called xen-netback.
Jeremy Fitzhardinge0d160212007-07-17 18:37:06 -0700436
Shreyas Bhatewarad1a890fa2009-10-13 00:15:51 -0700437config VMXNET3
Philippe De Muytere85eb112010-11-11 12:31:21 +0000438 tristate "VMware VMXNET3 ethernet driver"
439 depends on PCI && INET
Arnd Bergmannad47e672017-02-17 16:08:30 +0100440 depends on !(PAGE_SIZE_64KB || ARM64_64K_PAGES || \
441 IA64_PAGE_SIZE_64KB || MICROBLAZE_64K_PAGES || \
442 PARISC_PAGE_SIZE_64KB || PPC_64K_PAGES)
Philippe De Muytere85eb112010-11-11 12:31:21 +0000443 help
444 This driver supports VMware's vmxnet3 virtual ethernet NIC.
445 To compile this driver as a module, choose M here: the
446 module will be called vmxnet3.
Shreyas Bhatewarad1a890fa2009-10-13 00:15:51 -0700447
Taku Izumi658d4392015-08-21 17:29:17 +0900448config FUJITSU_ES
449 tristate "FUJITSU Extended Socket Network Device driver"
450 depends on ACPI
451 help
452 This driver provides support for Extended Socket network device
453 on Extended Partitioning of FUJITSU PRIMEQUEST 2000 E2 series.
454
Haiyang Zhang95fa0402011-11-28 13:35:35 -0800455source "drivers/net/hyperv/Kconfig"
456
Jan Engelhardtd1c0a652007-06-13 12:48:53 -0700457endif # NETDEVICES