Commit | Line | Data |
---|---|---|
1da177e4 LT |
1 | # |
2 | # Network device configuration | |
3 | # | |
4 | ||
d1c0a65f | 5 | menuconfig NETDEVICES |
ce2d2aed | 6 | default y if UML |
e0009820 | 7 | depends on NET |
1da177e4 LT |
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 | ||
1618cb0c RD |
24 | # All the following symbols are dependent on NETDEVICES - do not repeat |
25 | # that for each of the symbols. | |
26 | if NETDEVICES | |
cbcd2a4c | 27 | |
a1606c7d BH |
28 | config MII |
29 | tristate | |
30 | ||
88491d81 JK |
31 | config NET_CORE |
32 | default y | |
33 | bool "Network core driver support" | |
253af423 | 34 | ---help--- |
88491d81 JK |
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 | ||
38 | if NET_CORE | |
39 | ||
40 | config 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 | ||
253af423 | 55 | To compile this driver as a module, choose M here: the module |
88491d81 | 56 | will be called bonding. |
253af423 | 57 | |
1da177e4 LT |
58 | config DUMMY |
59 | tristate "Dummy net driver support" | |
1da177e4 LT |
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. 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 | |
9f486619 | 72 | will be called dummy. |
1da177e4 | 73 | |
88491d81 JK |
74 | config EQUALIZER |
75 | tristate "EQL (serial line load balancing) support" | |
1da177e4 | 76 | ---help--- |
88491d81 JK |
77 | 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. | |
1da177e4 | 84 | |
88491d81 JK |
85 | 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>. | |
1da177e4 | 89 | |
88491d81 JK |
90 | To compile this driver as a module, choose M here: the module |
91 | will be called eql. If unsure, say N. | |
92 | ||
93 | config 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". | |
1da177e4 | 105 | |
88491d81 JK |
106 | config 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. | |
1da177e4 | 112 | To compile this driver as a module, choose M here: the module |
88491d81 JK |
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 | |
1da177e4 | 118 | |
3d249d4c JP |
119 | source "drivers/net/team/Kconfig" |
120 | ||
b863ceb7 | 121 | config MACVLAN |
bd085b93 | 122 | tristate "MAC-VLAN support" |
b863ceb7 PM |
123 | ---help--- |
124 | This allows one to create virtual interfaces that map packets to | |
125 | or from specific MAC addresses to a particular interface. | |
126 | ||
3dbf8d56 PM |
127 | 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 | ||
b863ceb7 PM |
132 | To compile this driver as a module, choose M here: the module |
133 | will be called macvlan. | |
134 | ||
20d29d7a | 135 | config MACVTAP |
bd085b93 | 136 | tristate "MAC-VLAN based tap driver" |
20d29d7a | 137 | depends on MACVLAN |
de11b0e8 | 138 | depends on INET |
20d29d7a AB |
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 | |
c7966b52 | 143 | macvtap', and then be accessed through the tap user space interface. |
20d29d7a AB |
144 | |
145 | To compile this driver as a module, choose M here: the module | |
146 | will be called macvtap. | |
147 | ||
2ad7bf36 MB |
148 | |
149 | config IPVLAN | |
150 | tristate "IP-VLAN support" | |
265de6d1 MB |
151 | depends on INET |
152 | depends on IPV6 | |
2ad7bf36 MB |
153 | ---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 | |
f4c2b7a0 | 160 | iproute2 package starting with the iproute2-3.19 release: |
2ad7bf36 MB |
161 | |
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 | ||
d342894c | 168 | config VXLAN |
169 | tristate "Virtual eXtensible Local Area Network (VXLAN)" | |
c9b20a5e | 170 | depends on INET |
3ee64f39 | 171 | select NET_UDP_TUNNEL |
d342894c | 172 | ---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 | ||
88491d81 JK |
182 | config NETCONSOLE |
183 | tristate "Network console logging support" | |
1da177e4 | 184 | ---help--- |
88491d81 JK |
185 | If you want to log kernel messages over the network, enable this. |
186 | See <file:Documentation/networking/netconsole.txt> for details. | |
1da177e4 | 187 | |
88491d81 JK |
188 | config NETCONSOLE_DYNAMIC |
189 | bool "Dynamic reconfiguration of logging targets" | |
190 | depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \ | |
191 | !(NETCONSOLE=y && CONFIGFS_FS=m) | |
192 | help | |
193 | This option enables the ability to dynamically reconfigure target | |
194 | parameters (interface, IP addresses, port numbers, MAC addresses) | |
195 | at runtime through a userspace interface exported using configfs. | |
196 | See <file:Documentation/networking/netconsole.txt> for details. | |
1da177e4 | 197 | |
88491d81 JK |
198 | config NETPOLL |
199 | def_bool NETCONSOLE | |
83fe27ea | 200 | select SRCU |
88491d81 | 201 | |
88491d81 JK |
202 | config NET_POLL_CONTROLLER |
203 | def_bool NETPOLL | |
204 | ||
548c237c JM |
205 | config NTB_NETDEV |
206 | tristate "Virtual Ethernet over NTB" | |
207 | depends on NTB | |
208 | ||
88491d81 JK |
209 | config RIONET |
210 | tristate "RapidIO Ethernet over messaging driver support" | |
211 | depends on RAPIDIO | |
212 | ||
213 | config RIONET_TX_SIZE | |
214 | int "Number of outbound queue entries" | |
215 | depends on RIONET | |
216 | default "128" | |
217 | ||
218 | config RIONET_RX_SIZE | |
219 | int "Number of inbound queue entries" | |
220 | depends on RIONET | |
221 | default "128" | |
1da177e4 LT |
222 | |
223 | config TUN | |
224 | tristate "Universal TUN/TAP device driver support" | |
de11b0e8 | 225 | depends on INET |
1da177e4 LT |
226 | select CRC32 |
227 | ---help--- | |
228 | TUN/TAP provides packet reception and transmission for user space | |
229 | programs. It can be viewed as a simple Point-to-Point or Ethernet | |
230 | device, which instead of receiving packets from a physical media, | |
231 | receives them from user space program and instead of sending packets | |
232 | via physical media writes them to the user space program. | |
233 | ||
234 | When a program opens /dev/net/tun, driver creates and registers | |
235 | corresponding net device tunX or tapX. After a program closed above | |
236 | devices, driver will automatically delete tunXX or tapXX device and | |
237 | all routes corresponding to it. | |
238 | ||
239 | Please read <file:Documentation/networking/tuntap.txt> for more | |
240 | information. | |
241 | ||
242 | To compile this driver as a module, choose M here: the module | |
243 | will be called tun. | |
244 | ||
245 | If you don't know what to use this for, you don't need it. | |
246 | ||
e314dbdc | 247 | config VETH |
6a9a0250 | 248 | tristate "Virtual ethernet pair device" |
e314dbdc | 249 | ---help--- |
6a9a0250 RR |
250 | This device is a local ethernet tunnel. Devices are created in pairs. |
251 | When one end receives the packet it appears on its pair and vice | |
252 | versa. | |
e314dbdc | 253 | |
88491d81 | 254 | config VIRTIO_NET |
bd085b93 KC |
255 | tristate "Virtio network driver" |
256 | depends on VIRTIO | |
8cabd6a0 | 257 | select AVERAGE |
88491d81 JK |
258 | ---help--- |
259 | This is the virtual network driver for virtio. It can be used with | |
260 | lguest or QEMU based VMMs (like KVM or Xen). Say Y or M. | |
261 | ||
e4fc408e DB |
262 | config NLMON |
263 | tristate "Virtual netlink monitoring device" | |
264 | ---help--- | |
265 | This option enables a monitoring net device for netlink skbs. The | |
266 | purpose of this is to analyze netlink messages with packet sockets. | |
267 | Thus applications like tcpdump will be able to see local netlink | |
268 | messages if they tap into the netlink device, record pcaps for further | |
269 | diagnostics, etc. This is mostly intended for developers or support | |
270 | to debug netlink issues. If unsure, say N. | |
271 | ||
88491d81 JK |
272 | endif # NET_CORE |
273 | ||
274 | config SUNGEM_PHY | |
275 | tristate | |
276 | ||
277 | source "drivers/net/arcnet/Kconfig" | |
278 | ||
279 | source "drivers/atm/Kconfig" | |
280 | ||
281 | source "drivers/net/caif/Kconfig" | |
282 | ||
3b158859 BH |
283 | source "drivers/net/dsa/Kconfig" |
284 | ||
88491d81 JK |
285 | source "drivers/net/ethernet/Kconfig" |
286 | ||
287 | source "drivers/net/fddi/Kconfig" | |
288 | ||
fecc7351 PB |
289 | source "drivers/net/hippi/Kconfig" |
290 | ||
1da177e4 LT |
291 | config NET_SB1000 |
292 | tristate "General Instruments Surfboard 1000" | |
cbcd2a4c | 293 | depends on PNP |
1da177e4 LT |
294 | ---help--- |
295 | This is a driver for the General Instrument (also known as | |
296 | NextLevel) SURFboard 1000 internal | |
297 | cable modem. This is an ISA card which is used by a number of cable | |
298 | TV companies to provide cable modem access. It's a one-way | |
299 | downstream-only cable modem, meaning that your upstream net link is | |
300 | provided by your regular phone modem. | |
301 | ||
302 | At present this driver only compiles as a module, so say M here if | |
303 | you have this card. The module will be called sb1000. Then read | |
304 | <file:Documentation/networking/README.sb1000> for information on how | |
305 | to use this module, as it needs special ppp scripts for establishing | |
306 | a connection. Further documentation and the necessary scripts can be | |
307 | found at: | |
308 | ||
309 | <http://www.jacksonville.net/~fventuri/> | |
310 | <http://home.adelphia.net/~siglercm/sb1000.html> | |
311 | <http://linuxpower.cx/~cable/> | |
312 | ||
313 | If you don't have this card, of course say N. | |
314 | ||
00db8189 AF |
315 | source "drivers/net/phy/Kconfig" |
316 | ||
18e635f4 JK |
317 | source "drivers/net/plip/Kconfig" |
318 | ||
88491d81 JK |
319 | source "drivers/net/ppp/Kconfig" |
320 | ||
b5451d78 JK |
321 | source "drivers/net/slip/Kconfig" |
322 | ||
88491d81 JK |
323 | source "drivers/s390/net/Kconfig" |
324 | ||
88491d81 JK |
325 | source "drivers/net/usb/Kconfig" |
326 | ||
1da177e4 LT |
327 | source "drivers/net/wireless/Kconfig" |
328 | ||
143ee2d5 IPG |
329 | source "drivers/net/wimax/Kconfig" |
330 | ||
1da177e4 LT |
331 | source "drivers/net/wan/Kconfig" |
332 | ||
0739d643 | 333 | source "drivers/net/ieee802154/Kconfig" |
334 | ||
0d160211 JF |
335 | config XEN_NETDEV_FRONTEND |
336 | tristate "Xen network device frontend driver" | |
337 | depends on XEN | |
7003087c | 338 | select XEN_XENBUS_FRONTEND |
0d160211 JF |
339 | default y |
340 | help | |
f942dc25 IC |
341 | This driver provides support for Xen paravirtual network |
342 | devices exported by a Xen network driver domain (often | |
343 | domain 0). | |
344 | ||
345 | The corresponding Linux backend driver is enabled by the | |
346 | CONFIG_XEN_NETDEV_BACKEND option. | |
347 | ||
348 | If you are compiling a kernel for use as Xen guest, you | |
349 | should say Y here. To compile this driver as a module, chose | |
350 | M here: the module will be called xen-netfront. | |
351 | ||
352 | config XEN_NETDEV_BACKEND | |
353 | tristate "Xen backend network device" | |
354 | depends on XEN_BACKEND | |
355 | help | |
356 | This driver allows the kernel to act as a Xen network driver | |
357 | domain which exports paravirtual network devices to other | |
358 | Xen domains. These devices can be accessed by any operating | |
359 | system that implements a compatible front end. | |
360 | ||
361 | The corresponding Linux frontend driver is enabled by the | |
362 | CONFIG_XEN_NETDEV_FRONTEND configuration option. | |
363 | ||
364 | The backend driver presents a standard network device | |
365 | endpoint for each paravirtual network device to the driver | |
366 | domain network stack. These can then be bridged or routed | |
367 | etc in order to provide full network connectivity. | |
368 | ||
369 | If you are compiling a kernel to run in a Xen network driver | |
370 | domain (often this is domain 0) you should say Y here. To | |
371 | compile this driver as a module, chose M here: the module | |
372 | will be called xen-netback. | |
0d160211 | 373 | |
d1a890fa | 374 | config VMXNET3 |
e85eb117 PDM |
375 | tristate "VMware VMXNET3 ethernet driver" |
376 | depends on PCI && INET | |
377 | help | |
378 | This driver supports VMware's vmxnet3 virtual ethernet NIC. | |
379 | To compile this driver as a module, choose M here: the | |
380 | module will be called vmxnet3. | |
d1a890fa | 381 | |
95fa0405 HZ |
382 | source "drivers/net/hyperv/Kconfig" |
383 | ||
d1c0a65f | 384 | endif # NETDEVICES |