blob: 494b888a65681bde29911f13bea5ab02ed1c32d2 [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
138 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
stephen hemmingerd3428942012-10-01 12:32:35 +0000147config VXLAN
148 tristate "Virtual eXtensible Local Area Network (VXLAN)"
Kees Cookc9b20a52013-02-22 21:25:38 +0000149 depends on INET
Pravin B Shelare8171042013-03-25 14:49:46 +0000150 select NET_IP_TUNNEL
stephen hemmingerd3428942012-10-01 12:32:35 +0000151 ---help---
152 This allows one to create vxlan virtual interfaces that provide
153 Layer 2 Networks over Layer 3 Networks. VXLAN is often used
154 to tunnel virtual network infrastructure in virtualized environments.
155 For more information see:
156 http://tools.ietf.org/html/draft-mahalingam-dutt-dcops-vxlan-02
157
158 To compile this driver as a module, choose M here: the module
159 will be called vxlan.
160
Jeff Kirsher88491d82011-08-23 00:42:10 -0700161config NETCONSOLE
162 tristate "Network console logging support"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700163 ---help---
Jeff Kirsher88491d82011-08-23 00:42:10 -0700164 If you want to log kernel messages over the network, enable this.
165 See <file:Documentation/networking/netconsole.txt> for details.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700166
Jeff Kirsher88491d82011-08-23 00:42:10 -0700167config NETCONSOLE_DYNAMIC
168 bool "Dynamic reconfiguration of logging targets"
169 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
170 !(NETCONSOLE=y && CONFIGFS_FS=m)
171 help
172 This option enables the ability to dynamically reconfigure target
173 parameters (interface, IP addresses, port numbers, MAC addresses)
174 at runtime through a userspace interface exported using configfs.
175 See <file:Documentation/networking/netconsole.txt> for details.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700176
Jeff Kirsher88491d82011-08-23 00:42:10 -0700177config NETPOLL
178 def_bool NETCONSOLE
179
180config NETPOLL_TRAP
181 bool "Netpoll traffic trapping"
182 default n
183 depends on NETPOLL
184
185config NET_POLL_CONTROLLER
186 def_bool NETPOLL
187
Jon Mason548c2372012-11-16 19:27:13 -0700188config NTB_NETDEV
189 tristate "Virtual Ethernet over NTB"
190 depends on NTB
191
Jeff Kirsher88491d82011-08-23 00:42:10 -0700192config RIONET
193 tristate "RapidIO Ethernet over messaging driver support"
194 depends on RAPIDIO
195
196config RIONET_TX_SIZE
197 int "Number of outbound queue entries"
198 depends on RIONET
199 default "128"
200
201config RIONET_RX_SIZE
202 int "Number of inbound queue entries"
203 depends on RIONET
204 default "128"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700205
206config TUN
207 tristate "Universal TUN/TAP device driver support"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700208 select CRC32
209 ---help---
210 TUN/TAP provides packet reception and transmission for user space
211 programs. It can be viewed as a simple Point-to-Point or Ethernet
212 device, which instead of receiving packets from a physical media,
213 receives them from user space program and instead of sending packets
214 via physical media writes them to the user space program.
215
216 When a program opens /dev/net/tun, driver creates and registers
217 corresponding net device tunX or tapX. After a program closed above
218 devices, driver will automatically delete tunXX or tapXX device and
219 all routes corresponding to it.
220
221 Please read <file:Documentation/networking/tuntap.txt> for more
222 information.
223
224 To compile this driver as a module, choose M here: the module
225 will be called tun.
226
227 If you don't know what to use this for, you don't need it.
228
Pavel Emelyanove314dbd2007-09-25 16:14:46 -0700229config VETH
Rusty Russell6a9a0252007-11-06 20:35:55 -0800230 tristate "Virtual ethernet pair device"
Pavel Emelyanove314dbd2007-09-25 16:14:46 -0700231 ---help---
Rusty Russell6a9a0252007-11-06 20:35:55 -0800232 This device is a local ethernet tunnel. Devices are created in pairs.
233 When one end receives the packet it appears on its pair and vice
234 versa.
Pavel Emelyanove314dbd2007-09-25 16:14:46 -0700235
Jeff Kirsher88491d82011-08-23 00:42:10 -0700236config VIRTIO_NET
Kees Cookbd085b92012-10-02 11:17:55 -0700237 tristate "Virtio network driver"
238 depends on VIRTIO
Michael Dalton8cabd6a2014-01-17 01:27:08 -0800239 select AVERAGE
Jeff Kirsher88491d82011-08-23 00:42:10 -0700240 ---help---
241 This is the virtual network driver for virtio. It can be used with
242 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
243
Daniel Borkmanne4fc4082013-06-21 19:38:08 +0200244config NLMON
245 tristate "Virtual netlink monitoring device"
246 ---help---
247 This option enables a monitoring net device for netlink skbs. The
248 purpose of this is to analyze netlink messages with packet sockets.
249 Thus applications like tcpdump will be able to see local netlink
250 messages if they tap into the netlink device, record pcaps for further
251 diagnostics, etc. This is mostly intended for developers or support
252 to debug netlink issues. If unsure, say N.
253
Jeff Kirsher88491d82011-08-23 00:42:10 -0700254endif # NET_CORE
255
256config SUNGEM_PHY
257 tristate
258
259source "drivers/net/arcnet/Kconfig"
260
261source "drivers/atm/Kconfig"
262
263source "drivers/net/caif/Kconfig"
264
Ben Hutchings3b158852011-11-27 17:08:33 +0000265source "drivers/net/dsa/Kconfig"
266
Jeff Kirsher88491d82011-08-23 00:42:10 -0700267source "drivers/net/ethernet/Kconfig"
268
269source "drivers/net/fddi/Kconfig"
270
Paul Bollefecc7352011-11-08 10:31:10 +0000271source "drivers/net/hippi/Kconfig"
272
Linus Torvalds1da177e2005-04-16 15:20:36 -0700273config NET_SB1000
274 tristate "General Instruments Surfboard 1000"
Randy Dunlapcbcd2a42005-07-27 13:04:35 -0700275 depends on PNP
Linus Torvalds1da177e2005-04-16 15:20:36 -0700276 ---help---
277 This is a driver for the General Instrument (also known as
278 NextLevel) SURFboard 1000 internal
279 cable modem. This is an ISA card which is used by a number of cable
280 TV companies to provide cable modem access. It's a one-way
281 downstream-only cable modem, meaning that your upstream net link is
282 provided by your regular phone modem.
283
284 At present this driver only compiles as a module, so say M here if
285 you have this card. The module will be called sb1000. Then read
286 <file:Documentation/networking/README.sb1000> for information on how
287 to use this module, as it needs special ppp scripts for establishing
288 a connection. Further documentation and the necessary scripts can be
289 found at:
290
291 <http://www.jacksonville.net/~fventuri/>
292 <http://home.adelphia.net/~siglercm/sb1000.html>
293 <http://linuxpower.cx/~cable/>
294
295 If you don't have this card, of course say N.
296
Andy Fleming00db8182005-07-30 19:31:23 -0400297source "drivers/net/phy/Kconfig"
298
Jeff Kirsher18e635f2011-08-03 03:01:58 -0700299source "drivers/net/plip/Kconfig"
300
Jeff Kirsher88491d82011-08-23 00:42:10 -0700301source "drivers/net/ppp/Kconfig"
302
Jeff Kirsherb5451d72011-08-03 03:17:13 -0700303source "drivers/net/slip/Kconfig"
304
Jeff Kirsher88491d82011-08-23 00:42:10 -0700305source "drivers/s390/net/Kconfig"
306
Jeff Kirsher88491d82011-08-23 00:42:10 -0700307source "drivers/net/usb/Kconfig"
308
Linus Torvalds1da177e2005-04-16 15:20:36 -0700309source "drivers/net/wireless/Kconfig"
310
Inaky Perez-Gonzalez143ee2d2008-12-23 16:18:48 -0800311source "drivers/net/wimax/Kconfig"
312
Linus Torvalds1da177e2005-04-16 15:20:36 -0700313source "drivers/net/wan/Kconfig"
314
alex.bluesman.smirnov@gmail.com0739d642012-08-26 05:10:11 +0000315source "drivers/net/ieee802154/Kconfig"
316
Jeremy Fitzhardinge0d160212007-07-17 18:37:06 -0700317config XEN_NETDEV_FRONTEND
318 tristate "Xen network device frontend driver"
319 depends on XEN
Jeremy Fitzhardinge70030872009-03-27 16:28:34 -0700320 select XEN_XENBUS_FRONTEND
Jeremy Fitzhardinge0d160212007-07-17 18:37:06 -0700321 default y
322 help
Ian Campbellf942dc22011-03-15 00:06:18 +0000323 This driver provides support for Xen paravirtual network
324 devices exported by a Xen network driver domain (often
325 domain 0).
326
327 The corresponding Linux backend driver is enabled by the
328 CONFIG_XEN_NETDEV_BACKEND option.
329
330 If you are compiling a kernel for use as Xen guest, you
331 should say Y here. To compile this driver as a module, chose
332 M here: the module will be called xen-netfront.
333
334config XEN_NETDEV_BACKEND
335 tristate "Xen backend network device"
336 depends on XEN_BACKEND
337 help
338 This driver allows the kernel to act as a Xen network driver
339 domain which exports paravirtual network devices to other
340 Xen domains. These devices can be accessed by any operating
341 system that implements a compatible front end.
342
343 The corresponding Linux frontend driver is enabled by the
344 CONFIG_XEN_NETDEV_FRONTEND configuration option.
345
346 The backend driver presents a standard network device
347 endpoint for each paravirtual network device to the driver
348 domain network stack. These can then be bridged or routed
349 etc in order to provide full network connectivity.
350
351 If you are compiling a kernel to run in a Xen network driver
352 domain (often this is domain 0) you should say Y here. To
353 compile this driver as a module, chose M here: the module
354 will be called xen-netback.
Jeremy Fitzhardinge0d160212007-07-17 18:37:06 -0700355
Shreyas Bhatewarad1a890fa2009-10-13 00:15:51 -0700356config VMXNET3
Philippe De Muytere85eb112010-11-11 12:31:21 +0000357 tristate "VMware VMXNET3 ethernet driver"
358 depends on PCI && INET
359 help
360 This driver supports VMware's vmxnet3 virtual ethernet NIC.
361 To compile this driver as a module, choose M here: the
362 module will be called vmxnet3.
Shreyas Bhatewarad1a890fa2009-10-13 00:15:51 -0700363
Haiyang Zhang95fa0402011-11-28 13:35:35 -0800364source "drivers/net/hyperv/Kconfig"
365
Jan Engelhardtd1c0a652007-06-13 12:48:53 -0700366endif # NETDEVICES