blob: d18eb607bee66ab1f586059a44de4fefd94352da [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.
65 If you use SLIP or PPP, you might want to say Y here. Since this
66 thing often comes in handy, the default is Y. It won't enlarge your
67 kernel either. What a deal. Read about it in the Network
68 Administrator's Guide, available from
69 <http://www.tldp.org/docs.html#guide>.
70
71 To compile this driver as a module, choose M here: the module
Alan Cox9f486612012-05-14 03:57:31 +000072 will be called dummy.
Linus Torvalds1da177e2005-04-16 15:20:36 -070073
Jeff Kirsher88491d82011-08-23 00:42:10 -070074config EQUALIZER
75 tristate "EQL (serial line load balancing) support"
Linus Torvalds1da177e2005-04-16 15:20:36 -070076 ---help---
Jeff Kirsher88491d82011-08-23 00:42:10 -070077 If you have two serial connections to some other computer (this
78 usually requires two modems and two telephone lines) and you use
79 SLIP (the protocol for sending Internet traffic over telephone
80 lines) or PPP (a better SLIP) on them, you can make them behave like
81 one double speed connection using this driver. Naturally, this has
82 to be supported at the other end as well, either with a similar EQL
83 Linux driver or with a Livingston Portmaster 2e.
Linus Torvalds1da177e2005-04-16 15:20:36 -070084
Jeff Kirsher88491d82011-08-23 00:42:10 -070085 Say Y if you want this and read
86 <file:Documentation/networking/eql.txt>. You may also want to read
87 section 6.2 of the NET-3-HOWTO, available from
88 <http://www.tldp.org/docs.html#howto>.
Linus Torvalds1da177e2005-04-16 15:20:36 -070089
90 To compile this driver as a module, choose M here: the module
Jeff Kirsher88491d82011-08-23 00:42:10 -070091 will be called eql. If unsure, say N.
92
93config NET_FC
94 bool "Fibre Channel driver support"
95 depends on SCSI && PCI
96 help
97 Fibre Channel is a high speed serial protocol mainly used to connect
98 large storage devices to the computer; it is compatible with and
99 intended to replace SCSI.
100
101 If you intend to use Fibre Channel, you need to have a Fibre channel
102 adaptor card in your computer; say Y here and to the driver for your
103 adaptor below. You also should have said Y to "SCSI support" and
104 "SCSI generic support".
105
Jeff Kirsher88491d82011-08-23 00:42:10 -0700106config IFB
107 tristate "Intermediate Functional Block support"
108 depends on NET_CLS_ACT
109 ---help---
110 This is an intermediate driver that allows sharing of
111 resources.
112 To compile this driver as a module, choose M here: the module
113 will be called ifb. If you want to use more than one ifb
114 device at a time, you need to compile this driver as a module.
115 Instead of 'ifb', the devices will then be called 'ifb0',
116 'ifb1' etc.
117 Look at the iproute2 documentation directory for usage etc
Linus Torvalds1da177e2005-04-16 15:20:36 -0700118
Jiri Pirko3d249d42011-11-11 22:16:48 +0000119source "drivers/net/team/Kconfig"
120
Patrick McHardyb863ceb2007-07-14 18:55:06 -0700121config MACVLAN
Kees Cookbd085b92012-10-02 11:17:55 -0700122 tristate "MAC-VLAN support"
Patrick McHardyb863ceb2007-07-14 18:55:06 -0700123 ---help---
124 This allows one to create virtual interfaces that map packets to
125 or from specific MAC addresses to a particular interface.
126
Patrick McHardy3dbf8d52008-02-26 17:52:05 -0800127 Macvlan devices can be added using the "ip" command from the
128 iproute2 package starting with the iproute2-2.6.23 release:
129
130 "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
131
Patrick McHardyb863ceb2007-07-14 18:55:06 -0700132 To compile this driver as a module, choose M here: the module
133 will be called macvlan.
134
Arnd Bergmann20d29d72010-01-30 12:24:26 +0000135config MACVTAP
Kees Cookbd085b92012-10-02 11:17:55 -0700136 tristate "MAC-VLAN based tap driver"
Arnd Bergmann20d29d72010-01-30 12:24:26 +0000137 depends on MACVLAN
Ben Hutchingsde11b0e2014-10-31 03:10:31 +0000138 depends on INET
Arnd Bergmann20d29d72010-01-30 12:24:26 +0000139 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
Jan Luebbec7966b52014-02-10 21:40:51 +0100143 macvtap', and then be accessed through the tap user space interface.
Arnd Bergmann20d29d72010-01-30 12:24:26 +0000144
145 To compile this driver as a module, choose M here: the module
146 will be called macvtap.
147
Mahesh Bandewar2ad7bf32014-11-23 23:07:46 -0800148
149config IPVLAN
150 tristate "IP-VLAN support"
Mahesh Bandewar265de6d2014-11-26 21:13:45 -0800151 depends on INET
152 depends on IPV6
Mahesh Bandewar2ad7bf32014-11-23 23:07:46 -0800153 ---help---
154 This allows one to create virtual devices off of a main interface
155 and packets will be delivered based on the dest L3 (IPv6/IPv4 addr)
156 on packets. All interfaces (including the main interface) share L2
157 making it transparent to the connected L2 switch.
158
159 Ipvlan devices can be added using the "ip" command from the
Mahesh Bandewarf4c2b7a2015-02-18 15:15:57 -0800160 iproute2 package starting with the iproute2-3.19 release:
Mahesh Bandewar2ad7bf32014-11-23 23:07:46 -0800161
162 "ip link add link <main-dev> [ NAME ] type ipvlan"
163
164 To compile this driver as a module, choose M here: the module
165 will be called ipvlan.
166
167
stephen hemmingerd3428942012-10-01 12:32:35 +0000168config VXLAN
169 tristate "Virtual eXtensible Local Area Network (VXLAN)"
Kees Cookc9b20a52013-02-22 21:25:38 +0000170 depends on INET
Tom Herbert3ee64f32014-07-13 19:49:42 -0700171 select NET_UDP_TUNNEL
stephen hemmingerd3428942012-10-01 12:32:35 +0000172 ---help---
173 This allows one to create vxlan virtual interfaces that provide
174 Layer 2 Networks over Layer 3 Networks. VXLAN is often used
175 to tunnel virtual network infrastructure in virtualized environments.
176 For more information see:
177 http://tools.ietf.org/html/draft-mahalingam-dutt-dcops-vxlan-02
178
179 To compile this driver as a module, choose M here: the module
180 will be called vxlan.
181
John W. Linville2d07dc72015-05-13 12:57:30 -0400182config GENEVE
Pravin B Shelar371bd102015-08-26 23:46:54 -0700183 tristate "Generic Network Virtualization Encapsulation"
184 depends on INET && NET_UDP_TUNNEL
John W. Linville2d07dc72015-05-13 12:57:30 -0400185 select NET_IP_TUNNEL
186 ---help---
187 This allows one to create geneve virtual interfaces that provide
188 Layer 2 Networks over Layer 3 Networks. GENEVE is often used
189 to tunnel virtual network infrastructure in virtualized environments.
190 For more information see:
191 http://tools.ietf.org/html/draft-gross-geneve-02
192
193 To compile this driver as a module, choose M here: the module
194 will be called geneve.
195
Jeff Kirsher88491d82011-08-23 00:42:10 -0700196config NETCONSOLE
197 tristate "Network console logging support"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700198 ---help---
Jeff Kirsher88491d82011-08-23 00:42:10 -0700199 If you want to log kernel messages over the network, enable this.
200 See <file:Documentation/networking/netconsole.txt> for details.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700201
Jeff Kirsher88491d82011-08-23 00:42:10 -0700202config NETCONSOLE_DYNAMIC
203 bool "Dynamic reconfiguration of logging targets"
204 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
205 !(NETCONSOLE=y && CONFIGFS_FS=m)
206 help
207 This option enables the ability to dynamically reconfigure target
208 parameters (interface, IP addresses, port numbers, MAC addresses)
209 at runtime through a userspace interface exported using configfs.
210 See <file:Documentation/networking/netconsole.txt> for details.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700211
Jeff Kirsher88491d82011-08-23 00:42:10 -0700212config NETPOLL
213 def_bool NETCONSOLE
Pranith Kumar83fe27e2014-12-05 11:24:45 -0500214 select SRCU
Jeff Kirsher88491d82011-08-23 00:42:10 -0700215
Jeff Kirsher88491d82011-08-23 00:42:10 -0700216config NET_POLL_CONTROLLER
217 def_bool NETPOLL
218
Jon Mason548c2372012-11-16 19:27:13 -0700219config NTB_NETDEV
Allen Hubbeec110bc2015-05-07 06:45:21 -0400220 tristate "Virtual Ethernet over NTB Transport"
221 depends on NTB_TRANSPORT
Jon Mason548c2372012-11-16 19:27:13 -0700222
Jeff Kirsher88491d82011-08-23 00:42:10 -0700223config RIONET
224 tristate "RapidIO Ethernet over messaging driver support"
225 depends on RAPIDIO
226
227config RIONET_TX_SIZE
228 int "Number of outbound queue entries"
229 depends on RIONET
230 default "128"
231
232config RIONET_RX_SIZE
233 int "Number of inbound queue entries"
234 depends on RIONET
235 default "128"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700236
237config TUN
238 tristate "Universal TUN/TAP device driver support"
Ben Hutchingsde11b0e2014-10-31 03:10:31 +0000239 depends on INET
Linus Torvalds1da177e2005-04-16 15:20:36 -0700240 select CRC32
241 ---help---
242 TUN/TAP provides packet reception and transmission for user space
243 programs. It can be viewed as a simple Point-to-Point or Ethernet
244 device, which instead of receiving packets from a physical media,
245 receives them from user space program and instead of sending packets
246 via physical media writes them to the user space program.
247
248 When a program opens /dev/net/tun, driver creates and registers
249 corresponding net device tunX or tapX. After a program closed above
250 devices, driver will automatically delete tunXX or tapXX device and
251 all routes corresponding to it.
252
253 Please read <file:Documentation/networking/tuntap.txt> for more
254 information.
255
256 To compile this driver as a module, choose M here: the module
257 will be called tun.
258
259 If you don't know what to use this for, you don't need it.
260
Greg Kurz8b8e6582015-04-24 14:50:36 +0200261config TUN_VNET_CROSS_LE
262 bool "Support for cross-endian vnet headers on little-endian kernels"
263 default n
264 ---help---
265 This option allows TUN/TAP and MACVTAP device drivers in a
266 little-endian kernel to parse vnet headers that come from a
267 big-endian legacy virtio device.
268
269 Userspace programs can control the feature using the TUNSETVNETBE
270 and TUNGETVNETBE ioctls.
271
272 Unless you have a little-endian system hosting a big-endian virtual
273 machine with a legacy virtio NIC, you should say N.
274
Pavel Emelyanove314dbd2007-09-25 16:14:46 -0700275config VETH
Rusty Russell6a9a0252007-11-06 20:35:55 -0800276 tristate "Virtual ethernet pair device"
Pavel Emelyanove314dbd2007-09-25 16:14:46 -0700277 ---help---
Rusty Russell6a9a0252007-11-06 20:35:55 -0800278 This device is a local ethernet tunnel. Devices are created in pairs.
279 When one end receives the packet it appears on its pair and vice
280 versa.
Pavel Emelyanove314dbd2007-09-25 16:14:46 -0700281
Jeff Kirsher88491d82011-08-23 00:42:10 -0700282config VIRTIO_NET
Kees Cookbd085b92012-10-02 11:17:55 -0700283 tristate "Virtio network driver"
284 depends on VIRTIO
Jeff Kirsher88491d82011-08-23 00:42:10 -0700285 ---help---
286 This is the virtual network driver for virtio. It can be used with
287 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
288
Daniel Borkmanne4fc4082013-06-21 19:38:08 +0200289config NLMON
290 tristate "Virtual netlink monitoring device"
291 ---help---
292 This option enables a monitoring net device for netlink skbs. The
293 purpose of this is to analyze netlink messages with packet sockets.
294 Thus applications like tcpdump will be able to see local netlink
295 messages if they tap into the netlink device, record pcaps for further
296 diagnostics, etc. This is mostly intended for developers or support
297 to debug netlink issues. If unsure, say N.
298
David Ahern193125d2015-08-13 14:59:10 -0600299config NET_VRF
300 tristate "Virtual Routing and Forwarding (Lite)"
301 depends on IP_MULTIPLE_TABLES && IPV6_MULTIPLE_TABLES
302 ---help---
303 This option enables the support for mapping interfaces into VRF's. The
304 support enables VRF devices.
305
Jeff Kirsher88491d82011-08-23 00:42:10 -0700306endif # NET_CORE
307
308config SUNGEM_PHY
309 tristate
310
311source "drivers/net/arcnet/Kconfig"
312
313source "drivers/atm/Kconfig"
314
315source "drivers/net/caif/Kconfig"
316
Ben Hutchings3b158852011-11-27 17:08:33 +0000317source "drivers/net/dsa/Kconfig"
318
Jeff Kirsher88491d82011-08-23 00:42:10 -0700319source "drivers/net/ethernet/Kconfig"
320
321source "drivers/net/fddi/Kconfig"
322
Paul Bollefecc7352011-11-08 10:31:10 +0000323source "drivers/net/hippi/Kconfig"
324
Linus Torvalds1da177e2005-04-16 15:20:36 -0700325config NET_SB1000
326 tristate "General Instruments Surfboard 1000"
Randy Dunlapcbcd2a42005-07-27 13:04:35 -0700327 depends on PNP
Linus Torvalds1da177e2005-04-16 15:20:36 -0700328 ---help---
329 This is a driver for the General Instrument (also known as
330 NextLevel) SURFboard 1000 internal
331 cable modem. This is an ISA card which is used by a number of cable
332 TV companies to provide cable modem access. It's a one-way
333 downstream-only cable modem, meaning that your upstream net link is
334 provided by your regular phone modem.
335
336 At present this driver only compiles as a module, so say M here if
337 you have this card. The module will be called sb1000. Then read
338 <file:Documentation/networking/README.sb1000> for information on how
339 to use this module, as it needs special ppp scripts for establishing
340 a connection. Further documentation and the necessary scripts can be
341 found at:
342
343 <http://www.jacksonville.net/~fventuri/>
344 <http://home.adelphia.net/~siglercm/sb1000.html>
345 <http://linuxpower.cx/~cable/>
346
347 If you don't have this card, of course say N.
348
Andy Fleming00db8182005-07-30 19:31:23 -0400349source "drivers/net/phy/Kconfig"
350
Jeff Kirsher18e635f2011-08-03 03:01:58 -0700351source "drivers/net/plip/Kconfig"
352
Jeff Kirsher88491d82011-08-23 00:42:10 -0700353source "drivers/net/ppp/Kconfig"
354
Jeff Kirsherb5451d72011-08-03 03:17:13 -0700355source "drivers/net/slip/Kconfig"
356
Jeff Kirsher88491d82011-08-23 00:42:10 -0700357source "drivers/s390/net/Kconfig"
358
Jeff Kirsher88491d82011-08-23 00:42:10 -0700359source "drivers/net/usb/Kconfig"
360
Linus Torvalds1da177e2005-04-16 15:20:36 -0700361source "drivers/net/wireless/Kconfig"
362
Inaky Perez-Gonzalez143ee2d2008-12-23 16:18:48 -0800363source "drivers/net/wimax/Kconfig"
364
Linus Torvalds1da177e2005-04-16 15:20:36 -0700365source "drivers/net/wan/Kconfig"
366
alex.bluesman.smirnov@gmail.com0739d642012-08-26 05:10:11 +0000367source "drivers/net/ieee802154/Kconfig"
368
Jeremy Fitzhardinge0d160212007-07-17 18:37:06 -0700369config XEN_NETDEV_FRONTEND
370 tristate "Xen network device frontend driver"
371 depends on XEN
Jeremy Fitzhardinge70030872009-03-27 16:28:34 -0700372 select XEN_XENBUS_FRONTEND
Jeremy Fitzhardinge0d160212007-07-17 18:37:06 -0700373 default y
374 help
Ian Campbellf942dc22011-03-15 00:06:18 +0000375 This driver provides support for Xen paravirtual network
376 devices exported by a Xen network driver domain (often
377 domain 0).
378
379 The corresponding Linux backend driver is enabled by the
380 CONFIG_XEN_NETDEV_BACKEND option.
381
382 If you are compiling a kernel for use as Xen guest, you
383 should say Y here. To compile this driver as a module, chose
384 M here: the module will be called xen-netfront.
385
386config XEN_NETDEV_BACKEND
387 tristate "Xen backend network device"
388 depends on XEN_BACKEND
389 help
390 This driver allows the kernel to act as a Xen network driver
391 domain which exports paravirtual network devices to other
392 Xen domains. These devices can be accessed by any operating
393 system that implements a compatible front end.
394
395 The corresponding Linux frontend driver is enabled by the
396 CONFIG_XEN_NETDEV_FRONTEND configuration option.
397
398 The backend driver presents a standard network device
399 endpoint for each paravirtual network device to the driver
400 domain network stack. These can then be bridged or routed
401 etc in order to provide full network connectivity.
402
403 If you are compiling a kernel to run in a Xen network driver
404 domain (often this is domain 0) you should say Y here. To
405 compile this driver as a module, chose M here: the module
406 will be called xen-netback.
Jeremy Fitzhardinge0d160212007-07-17 18:37:06 -0700407
Shreyas Bhatewarad1a890fa2009-10-13 00:15:51 -0700408config VMXNET3
Philippe De Muytere85eb112010-11-11 12:31:21 +0000409 tristate "VMware VMXNET3 ethernet driver"
410 depends on PCI && INET
411 help
412 This driver supports VMware's vmxnet3 virtual ethernet NIC.
413 To compile this driver as a module, choose M here: the
414 module will be called vmxnet3.
Shreyas Bhatewarad1a890fa2009-10-13 00:15:51 -0700415
Taku Izumi658d4392015-08-21 17:29:17 +0900416config FUJITSU_ES
417 tristate "FUJITSU Extended Socket Network Device driver"
418 depends on ACPI
419 help
420 This driver provides support for Extended Socket network device
421 on Extended Partitioning of FUJITSU PRIMEQUEST 2000 E2 series.
422
Haiyang Zhang95fa0402011-11-28 13:35:35 -0800423source "drivers/net/hyperv/Kconfig"
424
Jan Engelhardtd1c0a652007-06-13 12:48:53 -0700425endif # NETDEVICES