blob: 654a5e94e0e7c4f227c93b75a7791c406c586d38 [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
Jeff Kirsher88491d82011-08-23 00:42:10 -070028config NET_CORE
29 default y
30 bool "Network core driver support"
Jamal Hadi Salim253af422006-01-08 22:34:25 -080031 ---help---
Jeff Kirsher88491d82011-08-23 00:42:10 -070032 You can say N here if you do not intend to use any of the
33 networking core drivers (i.e. VLAN, bridging, bonding, etc.)
34
35if NET_CORE
36
37config BONDING
38 tristate "Bonding driver support"
39 depends on INET
40 depends on IPV6 || IPV6=n
41 ---help---
42 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
43 Channels together. This is called 'Etherchannel' by Cisco,
44 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
45
46 The driver supports multiple bonding modes to allow for both high
47 performance and high availability operation.
48
49 Refer to <file:Documentation/networking/bonding.txt> for more
50 information.
51
Jamal Hadi Salim253af422006-01-08 22:34:25 -080052 To compile this driver as a module, choose M here: the module
Jeff Kirsher88491d82011-08-23 00:42:10 -070053 will be called bonding.
Jamal Hadi Salim253af422006-01-08 22:34:25 -080054
Linus Torvalds1da177e2005-04-16 15:20:36 -070055config DUMMY
56 tristate "Dummy net driver support"
Linus Torvalds1da177e2005-04-16 15:20:36 -070057 ---help---
58 This is essentially a bit-bucket device (i.e. traffic you send to
59 this device is consigned into oblivion) with a configurable IP
60 address. It is most commonly used in order to make your currently
61 inactive SLIP address seem like a real address for local programs.
62 If you use SLIP or PPP, you might want to say Y here. Since this
63 thing often comes in handy, the default is Y. It won't enlarge your
64 kernel either. What a deal. Read about it in the Network
65 Administrator's Guide, available from
66 <http://www.tldp.org/docs.html#guide>.
67
68 To compile this driver as a module, choose M here: the module
69 will be called dummy. If you want to use more than one dummy
70 device at a time, you need to compile this driver as a module.
71 Instead of 'dummy', the devices will then be called 'dummy0',
72 'dummy1' etc.
73
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
106config MII
107 tristate "Generic Media Independent Interface device support"
108 help
109 Most ethernet controllers have MII transceiver either as an external
110 or internal device. It is safe to say Y or M here even if your
111 ethernet card lacks MII.
112
113source "drivers/ieee802154/Kconfig"
114
115config IFB
116 tristate "Intermediate Functional Block support"
117 depends on NET_CLS_ACT
118 ---help---
119 This is an intermediate driver that allows sharing of
120 resources.
121 To compile this driver as a module, choose M here: the module
122 will be called ifb. If you want to use more than one ifb
123 device at a time, you need to compile this driver as a module.
124 Instead of 'ifb', the devices will then be called 'ifb0',
125 'ifb1' etc.
126 Look at the iproute2 documentation directory for usage etc
Linus Torvalds1da177e2005-04-16 15:20:36 -0700127
Patrick McHardyb863ceb2007-07-14 18:55:06 -0700128config MACVLAN
129 tristate "MAC-VLAN support (EXPERIMENTAL)"
130 depends on EXPERIMENTAL
131 ---help---
132 This allows one to create virtual interfaces that map packets to
133 or from specific MAC addresses to a particular interface.
134
Patrick McHardy3dbf8d52008-02-26 17:52:05 -0800135 Macvlan devices can be added using the "ip" command from the
136 iproute2 package starting with the iproute2-2.6.23 release:
137
138 "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
139
Patrick McHardyb863ceb2007-07-14 18:55:06 -0700140 To compile this driver as a module, choose M here: the module
141 will be called macvlan.
142
Arnd Bergmann20d29d72010-01-30 12:24:26 +0000143config MACVTAP
144 tristate "MAC-VLAN based tap driver (EXPERIMENTAL)"
145 depends on MACVLAN
146 help
147 This adds a specialized tap character device driver that is based
148 on the MAC-VLAN network interface, called macvtap. A macvtap device
149 can be added in the same way as a macvlan device, using 'type
150 macvlan', and then be accessed through the tap user space interface.
151
152 To compile this driver as a module, choose M here: the module
153 will be called macvtap.
154
Jeff Kirsher88491d82011-08-23 00:42:10 -0700155config NETCONSOLE
156 tristate "Network console logging support"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700157 ---help---
Jeff Kirsher88491d82011-08-23 00:42:10 -0700158 If you want to log kernel messages over the network, enable this.
159 See <file:Documentation/networking/netconsole.txt> for details.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700160
Jeff Kirsher88491d82011-08-23 00:42:10 -0700161config NETCONSOLE_DYNAMIC
162 bool "Dynamic reconfiguration of logging targets"
163 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
164 !(NETCONSOLE=y && CONFIGFS_FS=m)
165 help
166 This option enables the ability to dynamically reconfigure target
167 parameters (interface, IP addresses, port numbers, MAC addresses)
168 at runtime through a userspace interface exported using configfs.
169 See <file:Documentation/networking/netconsole.txt> for details.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700170
Jeff Kirsher88491d82011-08-23 00:42:10 -0700171config NETPOLL
172 def_bool NETCONSOLE
173
174config NETPOLL_TRAP
175 bool "Netpoll traffic trapping"
176 default n
177 depends on NETPOLL
178
179config NET_POLL_CONTROLLER
180 def_bool NETPOLL
181
182config RIONET
183 tristate "RapidIO Ethernet over messaging driver support"
184 depends on RAPIDIO
185
186config RIONET_TX_SIZE
187 int "Number of outbound queue entries"
188 depends on RIONET
189 default "128"
190
191config RIONET_RX_SIZE
192 int "Number of inbound queue entries"
193 depends on RIONET
194 default "128"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700195
196config TUN
197 tristate "Universal TUN/TAP device driver support"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700198 select CRC32
199 ---help---
200 TUN/TAP provides packet reception and transmission for user space
201 programs. It can be viewed as a simple Point-to-Point or Ethernet
202 device, which instead of receiving packets from a physical media,
203 receives them from user space program and instead of sending packets
204 via physical media writes them to the user space program.
205
206 When a program opens /dev/net/tun, driver creates and registers
207 corresponding net device tunX or tapX. After a program closed above
208 devices, driver will automatically delete tunXX or tapXX device and
209 all routes corresponding to it.
210
211 Please read <file:Documentation/networking/tuntap.txt> for more
212 information.
213
214 To compile this driver as a module, choose M here: the module
215 will be called tun.
216
217 If you don't know what to use this for, you don't need it.
218
Pavel Emelyanove314dbd2007-09-25 16:14:46 -0700219config VETH
Rusty Russell6a9a0252007-11-06 20:35:55 -0800220 tristate "Virtual ethernet pair device"
Pavel Emelyanove314dbd2007-09-25 16:14:46 -0700221 ---help---
Rusty Russell6a9a0252007-11-06 20:35:55 -0800222 This device is a local ethernet tunnel. Devices are created in pairs.
223 When one end receives the packet it appears on its pair and vice
224 versa.
Pavel Emelyanove314dbd2007-09-25 16:14:46 -0700225
Jeff Kirsher88491d82011-08-23 00:42:10 -0700226config VIRTIO_NET
227 tristate "Virtio network driver (EXPERIMENTAL)"
228 depends on EXPERIMENTAL && VIRTIO
229 ---help---
230 This is the virtual network driver for virtio. It can be used with
231 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
232
233endif # NET_CORE
234
235config SUNGEM_PHY
236 tristate
237
238source "drivers/net/arcnet/Kconfig"
239
240source "drivers/atm/Kconfig"
241
242source "drivers/net/caif/Kconfig"
243
244source "drivers/net/ethernet/Kconfig"
245
246source "drivers/net/fddi/Kconfig"
247
Paul Bollefecc7352011-11-08 10:31:10 +0000248source "drivers/net/hippi/Kconfig"
249
Linus Torvalds1da177e2005-04-16 15:20:36 -0700250config NET_SB1000
251 tristate "General Instruments Surfboard 1000"
Randy Dunlapcbcd2a42005-07-27 13:04:35 -0700252 depends on PNP
Linus Torvalds1da177e2005-04-16 15:20:36 -0700253 ---help---
254 This is a driver for the General Instrument (also known as
255 NextLevel) SURFboard 1000 internal
256 cable modem. This is an ISA card which is used by a number of cable
257 TV companies to provide cable modem access. It's a one-way
258 downstream-only cable modem, meaning that your upstream net link is
259 provided by your regular phone modem.
260
261 At present this driver only compiles as a module, so say M here if
262 you have this card. The module will be called sb1000. Then read
263 <file:Documentation/networking/README.sb1000> for information on how
264 to use this module, as it needs special ppp scripts for establishing
265 a connection. Further documentation and the necessary scripts can be
266 found at:
267
268 <http://www.jacksonville.net/~fventuri/>
269 <http://home.adelphia.net/~siglercm/sb1000.html>
270 <http://linuxpower.cx/~cable/>
271
272 If you don't have this card, of course say N.
273
Andy Fleming00db8182005-07-30 19:31:23 -0400274source "drivers/net/phy/Kconfig"
275
Jeff Kirsher18e635f2011-08-03 03:01:58 -0700276source "drivers/net/plip/Kconfig"
277
Jeff Kirsher88491d82011-08-23 00:42:10 -0700278source "drivers/net/ppp/Kconfig"
279
Jeff Kirsherb5451d72011-08-03 03:17:13 -0700280source "drivers/net/slip/Kconfig"
281
Jeff Kirsher88491d82011-08-23 00:42:10 -0700282source "drivers/s390/net/Kconfig"
283
Linus Torvalds1da177e2005-04-16 15:20:36 -0700284source "drivers/net/tokenring/Kconfig"
285
Jeff Kirsher88491d82011-08-23 00:42:10 -0700286source "drivers/net/usb/Kconfig"
287
Linus Torvalds1da177e2005-04-16 15:20:36 -0700288source "drivers/net/wireless/Kconfig"
289
Inaky Perez-Gonzalez143ee2d2008-12-23 16:18:48 -0800290source "drivers/net/wimax/Kconfig"
291
Linus Torvalds1da177e2005-04-16 15:20:36 -0700292source "drivers/net/wan/Kconfig"
293
Jeremy Fitzhardinge0d160212007-07-17 18:37:06 -0700294config XEN_NETDEV_FRONTEND
295 tristate "Xen network device frontend driver"
296 depends on XEN
Jeremy Fitzhardinge70030872009-03-27 16:28:34 -0700297 select XEN_XENBUS_FRONTEND
Jeremy Fitzhardinge0d160212007-07-17 18:37:06 -0700298 default y
299 help
Ian Campbellf942dc22011-03-15 00:06:18 +0000300 This driver provides support for Xen paravirtual network
301 devices exported by a Xen network driver domain (often
302 domain 0).
303
304 The corresponding Linux backend driver is enabled by the
305 CONFIG_XEN_NETDEV_BACKEND option.
306
307 If you are compiling a kernel for use as Xen guest, you
308 should say Y here. To compile this driver as a module, chose
309 M here: the module will be called xen-netfront.
310
311config XEN_NETDEV_BACKEND
312 tristate "Xen backend network device"
313 depends on XEN_BACKEND
314 help
315 This driver allows the kernel to act as a Xen network driver
316 domain which exports paravirtual network devices to other
317 Xen domains. These devices can be accessed by any operating
318 system that implements a compatible front end.
319
320 The corresponding Linux frontend driver is enabled by the
321 CONFIG_XEN_NETDEV_FRONTEND configuration option.
322
323 The backend driver presents a standard network device
324 endpoint for each paravirtual network device to the driver
325 domain network stack. These can then be bridged or routed
326 etc in order to provide full network connectivity.
327
328 If you are compiling a kernel to run in a Xen network driver
329 domain (often this is domain 0) you should say Y here. To
330 compile this driver as a module, chose M here: the module
331 will be called xen-netback.
Jeremy Fitzhardinge0d160212007-07-17 18:37:06 -0700332
Shreyas Bhatewarad1a890fa2009-10-13 00:15:51 -0700333config VMXNET3
Philippe De Muytere85eb112010-11-11 12:31:21 +0000334 tristate "VMware VMXNET3 ethernet driver"
335 depends on PCI && INET
336 help
337 This driver supports VMware's vmxnet3 virtual ethernet NIC.
338 To compile this driver as a module, choose M here: the
339 module will be called vmxnet3.
Shreyas Bhatewarad1a890fa2009-10-13 00:15:51 -0700340
Jan Engelhardtd1c0a652007-06-13 12:48:53 -0700341endif # NETDEVICES