]>
Commit | Line | Data |
---|---|---|
1 | # | |
2 | # Network device configuration | |
3 | # | |
4 | ||
5 | menuconfig NETDEVICES | |
6 | default y if UML | |
7 | depends on NET | |
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 | ||
24 | # All the following symbols are dependent on NETDEVICES - do not repeat | |
25 | # that for each of the symbols. | |
26 | if NETDEVICES | |
27 | ||
28 | config MII | |
29 | tristate | |
30 | ||
31 | config NET_CORE | |
32 | default y | |
33 | bool "Network core driver support" | |
34 | ---help--- | |
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 | ||
55 | To compile this driver as a module, choose M here: the module | |
56 | will be called bonding. | |
57 | ||
58 | config DUMMY | |
59 | tristate "Dummy net driver support" | |
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. It won't | |
66 | enlarge your kernel. What a deal. Read about it in the Network | |
67 | 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 | |
71 | will be called dummy. | |
72 | ||
73 | config EQUALIZER | |
74 | tristate "EQL (serial line load balancing) support" | |
75 | ---help--- | |
76 | 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. | |
83 | ||
84 | 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>. | |
88 | ||
89 | To compile this driver as a module, choose M here: the module | |
90 | will be called eql. If unsure, say N. | |
91 | ||
92 | config 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 | ||
105 | config 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 | |
117 | ||
118 | source "drivers/net/team/Kconfig" | |
119 | ||
120 | config MACVLAN | |
121 | tristate "MAC-VLAN support" | |
122 | ---help--- | |
123 | This allows one to create virtual interfaces that map packets to | |
124 | or from specific MAC addresses to a particular interface. | |
125 | ||
126 | 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 | ||
131 | To compile this driver as a module, choose M here: the module | |
132 | will be called macvlan. | |
133 | ||
134 | config MACVTAP | |
135 | tristate "MAC-VLAN based tap driver" | |
136 | depends on MACVLAN | |
137 | depends on INET | |
138 | select TAP | |
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 | |
143 | macvtap', and then be accessed through the tap user space interface. | |
144 | ||
145 | To compile this driver as a module, choose M here: the module | |
146 | will be called macvtap. | |
147 | ||
148 | ||
149 | config IPVLAN | |
150 | tristate "IP-VLAN support" | |
151 | depends on INET | |
152 | depends on IPV6 | |
153 | depends on NETFILTER | |
154 | depends on NET_L3_MASTER_DEV | |
155 | ---help--- | |
156 | This allows one to create virtual devices off of a main interface | |
157 | and packets will be delivered based on the dest L3 (IPv6/IPv4 addr) | |
158 | on packets. All interfaces (including the main interface) share L2 | |
159 | making it transparent to the connected L2 switch. | |
160 | ||
161 | Ipvlan devices can be added using the "ip" command from the | |
162 | iproute2 package starting with the iproute2-3.19 release: | |
163 | ||
164 | "ip link add link <main-dev> [ NAME ] type ipvlan" | |
165 | ||
166 | To compile this driver as a module, choose M here: the module | |
167 | will be called ipvlan. | |
168 | ||
169 | config IPVTAP | |
170 | tristate "IP-VLAN based tap driver" | |
171 | depends on IPVLAN | |
172 | depends on INET | |
173 | select TAP | |
174 | ---help--- | |
175 | This adds a specialized tap character device driver that is based | |
176 | on the IP-VLAN network interface, called ipvtap. An ipvtap device | |
177 | can be added in the same way as a ipvlan device, using 'type | |
178 | ipvtap', and then be accessed through the tap user space interface. | |
179 | ||
180 | To compile this driver as a module, choose M here: the module | |
181 | will be called ipvtap. | |
182 | ||
183 | config VXLAN | |
184 | tristate "Virtual eXtensible Local Area Network (VXLAN)" | |
185 | depends on INET | |
186 | select NET_UDP_TUNNEL | |
187 | select GRO_CELLS | |
188 | ---help--- | |
189 | This allows one to create vxlan virtual interfaces that provide | |
190 | Layer 2 Networks over Layer 3 Networks. VXLAN is often used | |
191 | to tunnel virtual network infrastructure in virtualized environments. | |
192 | For more information see: | |
193 | http://tools.ietf.org/html/draft-mahalingam-dutt-dcops-vxlan-02 | |
194 | ||
195 | To compile this driver as a module, choose M here: the module | |
196 | will be called vxlan. | |
197 | ||
198 | config GENEVE | |
199 | tristate "Generic Network Virtualization Encapsulation" | |
200 | depends on INET && NET_UDP_TUNNEL | |
201 | select NET_IP_TUNNEL | |
202 | select GRO_CELLS | |
203 | ---help--- | |
204 | This allows one to create geneve virtual interfaces that provide | |
205 | Layer 2 Networks over Layer 3 Networks. GENEVE is often used | |
206 | to tunnel virtual network infrastructure in virtualized environments. | |
207 | For more information see: | |
208 | http://tools.ietf.org/html/draft-gross-geneve-02 | |
209 | ||
210 | To compile this driver as a module, choose M here: the module | |
211 | will be called geneve. | |
212 | ||
213 | config GTP | |
214 | tristate "GPRS Tunneling Protocol datapath (GTP-U)" | |
215 | depends on INET && NET_UDP_TUNNEL | |
216 | select NET_IP_TUNNEL | |
217 | ---help--- | |
218 | This allows one to create gtp virtual interfaces that provide | |
219 | the GPRS Tunneling Protocol datapath (GTP-U). This tunneling protocol | |
220 | is used to prevent subscribers from accessing mobile carrier core | |
221 | network infrastructure. This driver requires a userspace software that | |
222 | implements the signaling protocol (GTP-C) to update its PDP context | |
223 | base, such as OpenGGSN <http://git.osmocom.org/openggsn/). This | |
224 | tunneling protocol is implemented according to the GSM TS 09.60 and | |
225 | 3GPP TS 29.060 standards. | |
226 | ||
227 | To compile this drivers as a module, choose M here: the module | |
228 | wil be called gtp. | |
229 | ||
230 | config MACSEC | |
231 | tristate "IEEE 802.1AE MAC-level encryption (MACsec)" | |
232 | select CRYPTO | |
233 | select CRYPTO_AES | |
234 | select CRYPTO_GCM | |
235 | select GRO_CELLS | |
236 | ---help--- | |
237 | MACsec is an encryption standard for Ethernet. | |
238 | ||
239 | config NETCONSOLE | |
240 | tristate "Network console logging support" | |
241 | ---help--- | |
242 | If you want to log kernel messages over the network, enable this. | |
243 | See <file:Documentation/networking/netconsole.txt> for details. | |
244 | ||
245 | config NETCONSOLE_DYNAMIC | |
246 | bool "Dynamic reconfiguration of logging targets" | |
247 | depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \ | |
248 | !(NETCONSOLE=y && CONFIGFS_FS=m) | |
249 | help | |
250 | This option enables the ability to dynamically reconfigure target | |
251 | parameters (interface, IP addresses, port numbers, MAC addresses) | |
252 | at runtime through a userspace interface exported using configfs. | |
253 | See <file:Documentation/networking/netconsole.txt> for details. | |
254 | ||
255 | config NETPOLL | |
256 | def_bool NETCONSOLE | |
257 | select SRCU | |
258 | ||
259 | config NET_POLL_CONTROLLER | |
260 | def_bool NETPOLL | |
261 | ||
262 | config NTB_NETDEV | |
263 | tristate "Virtual Ethernet over NTB Transport" | |
264 | depends on NTB_TRANSPORT | |
265 | ||
266 | config RIONET | |
267 | tristate "RapidIO Ethernet over messaging driver support" | |
268 | depends on RAPIDIO | |
269 | ||
270 | config RIONET_TX_SIZE | |
271 | int "Number of outbound queue entries" | |
272 | depends on RIONET | |
273 | default "128" | |
274 | ||
275 | config RIONET_RX_SIZE | |
276 | int "Number of inbound queue entries" | |
277 | depends on RIONET | |
278 | default "128" | |
279 | ||
280 | config TUN | |
281 | tristate "Universal TUN/TAP device driver support" | |
282 | depends on INET | |
283 | select CRC32 | |
284 | ---help--- | |
285 | TUN/TAP provides packet reception and transmission for user space | |
286 | programs. It can be viewed as a simple Point-to-Point or Ethernet | |
287 | device, which instead of receiving packets from a physical media, | |
288 | receives them from user space program and instead of sending packets | |
289 | via physical media writes them to the user space program. | |
290 | ||
291 | When a program opens /dev/net/tun, driver creates and registers | |
292 | corresponding net device tunX or tapX. After a program closed above | |
293 | devices, driver will automatically delete tunXX or tapXX device and | |
294 | all routes corresponding to it. | |
295 | ||
296 | Please read <file:Documentation/networking/tuntap.txt> for more | |
297 | information. | |
298 | ||
299 | To compile this driver as a module, choose M here: the module | |
300 | will be called tun. | |
301 | ||
302 | If you don't know what to use this for, you don't need it. | |
303 | ||
304 | config TAP | |
305 | tristate | |
306 | ---help--- | |
307 | This option is selected by any driver implementing tap user space | |
308 | interface for a virtual interface to re-use core tap functionality. | |
309 | ||
310 | config TUN_VNET_CROSS_LE | |
311 | bool "Support for cross-endian vnet headers on little-endian kernels" | |
312 | default n | |
313 | ---help--- | |
314 | This option allows TUN/TAP and MACVTAP device drivers in a | |
315 | little-endian kernel to parse vnet headers that come from a | |
316 | big-endian legacy virtio device. | |
317 | ||
318 | Userspace programs can control the feature using the TUNSETVNETBE | |
319 | and TUNGETVNETBE ioctls. | |
320 | ||
321 | Unless you have a little-endian system hosting a big-endian virtual | |
322 | machine with a legacy virtio NIC, you should say N. | |
323 | ||
324 | config VETH | |
325 | tristate "Virtual ethernet pair device" | |
326 | ---help--- | |
327 | This device is a local ethernet tunnel. Devices are created in pairs. | |
328 | When one end receives the packet it appears on its pair and vice | |
329 | versa. | |
330 | ||
331 | config VIRTIO_NET | |
332 | tristate "Virtio network driver" | |
333 | depends on VIRTIO | |
334 | ---help--- | |
335 | This is the virtual network driver for virtio. It can be used with | |
336 | lguest or QEMU based VMMs (like KVM or Xen). Say Y or M. | |
337 | ||
338 | config NLMON | |
339 | tristate "Virtual netlink monitoring device" | |
340 | ---help--- | |
341 | This option enables a monitoring net device for netlink skbs. The | |
342 | purpose of this is to analyze netlink messages with packet sockets. | |
343 | Thus applications like tcpdump will be able to see local netlink | |
344 | messages if they tap into the netlink device, record pcaps for further | |
345 | diagnostics, etc. This is mostly intended for developers or support | |
346 | to debug netlink issues. If unsure, say N. | |
347 | ||
348 | config NET_VRF | |
349 | tristate "Virtual Routing and Forwarding (Lite)" | |
350 | depends on IP_MULTIPLE_TABLES | |
351 | depends on NET_L3_MASTER_DEV | |
352 | depends on IPV6 || IPV6=n | |
353 | depends on IPV6_MULTIPLE_TABLES || IPV6=n | |
354 | ---help--- | |
355 | This option enables the support for mapping interfaces into VRF's. The | |
356 | support enables VRF devices. | |
357 | ||
358 | config VSOCKMON | |
359 | tristate "Virtual vsock monitoring device" | |
360 | depends on VHOST_VSOCK | |
361 | ---help--- | |
362 | This option enables a monitoring net device for vsock sockets. It is | |
363 | mostly intended for developers or support to debug vsock issues. If | |
364 | unsure, say N. | |
365 | ||
366 | endif # NET_CORE | |
367 | ||
368 | config SUNGEM_PHY | |
369 | tristate | |
370 | ||
371 | source "drivers/net/arcnet/Kconfig" | |
372 | ||
373 | source "drivers/atm/Kconfig" | |
374 | ||
375 | source "drivers/net/caif/Kconfig" | |
376 | ||
377 | source "drivers/net/dsa/Kconfig" | |
378 | ||
379 | source "drivers/net/ethernet/Kconfig" | |
380 | ||
381 | source "drivers/net/fddi/Kconfig" | |
382 | ||
383 | source "drivers/net/hippi/Kconfig" | |
384 | ||
385 | config NET_SB1000 | |
386 | tristate "General Instruments Surfboard 1000" | |
387 | depends on PNP | |
388 | ---help--- | |
389 | This is a driver for the General Instrument (also known as | |
390 | NextLevel) SURFboard 1000 internal | |
391 | cable modem. This is an ISA card which is used by a number of cable | |
392 | TV companies to provide cable modem access. It's a one-way | |
393 | downstream-only cable modem, meaning that your upstream net link is | |
394 | provided by your regular phone modem. | |
395 | ||
396 | At present this driver only compiles as a module, so say M here if | |
397 | you have this card. The module will be called sb1000. Then read | |
398 | <file:Documentation/networking/README.sb1000> for information on how | |
399 | to use this module, as it needs special ppp scripts for establishing | |
400 | a connection. Further documentation and the necessary scripts can be | |
401 | found at: | |
402 | ||
403 | <http://www.jacksonville.net/~fventuri/> | |
404 | <http://home.adelphia.net/~siglercm/sb1000.html> | |
405 | <http://linuxpower.cx/~cable/> | |
406 | ||
407 | If you don't have this card, of course say N. | |
408 | ||
409 | source "drivers/net/phy/Kconfig" | |
410 | ||
411 | source "drivers/net/plip/Kconfig" | |
412 | ||
413 | source "drivers/net/ppp/Kconfig" | |
414 | ||
415 | source "drivers/net/slip/Kconfig" | |
416 | ||
417 | source "drivers/s390/net/Kconfig" | |
418 | ||
419 | source "drivers/net/usb/Kconfig" | |
420 | ||
421 | source "drivers/net/wireless/Kconfig" | |
422 | ||
423 | source "drivers/net/wimax/Kconfig" | |
424 | ||
425 | source "drivers/net/wan/Kconfig" | |
426 | ||
427 | source "drivers/net/ieee802154/Kconfig" | |
428 | ||
429 | config XEN_NETDEV_FRONTEND | |
430 | tristate "Xen network device frontend driver" | |
431 | depends on XEN | |
432 | select XEN_XENBUS_FRONTEND | |
433 | default y | |
434 | help | |
435 | This driver provides support for Xen paravirtual network | |
436 | devices exported by a Xen network driver domain (often | |
437 | domain 0). | |
438 | ||
439 | The corresponding Linux backend driver is enabled by the | |
440 | CONFIG_XEN_NETDEV_BACKEND option. | |
441 | ||
442 | If you are compiling a kernel for use as Xen guest, you | |
443 | should say Y here. To compile this driver as a module, chose | |
444 | M here: the module will be called xen-netfront. | |
445 | ||
446 | config XEN_NETDEV_BACKEND | |
447 | tristate "Xen backend network device" | |
448 | depends on XEN_BACKEND | |
449 | help | |
450 | This driver allows the kernel to act as a Xen network driver | |
451 | domain which exports paravirtual network devices to other | |
452 | Xen domains. These devices can be accessed by any operating | |
453 | system that implements a compatible front end. | |
454 | ||
455 | The corresponding Linux frontend driver is enabled by the | |
456 | CONFIG_XEN_NETDEV_FRONTEND configuration option. | |
457 | ||
458 | The backend driver presents a standard network device | |
459 | endpoint for each paravirtual network device to the driver | |
460 | domain network stack. These can then be bridged or routed | |
461 | etc in order to provide full network connectivity. | |
462 | ||
463 | If you are compiling a kernel to run in a Xen network driver | |
464 | domain (often this is domain 0) you should say Y here. To | |
465 | compile this driver as a module, chose M here: the module | |
466 | will be called xen-netback. | |
467 | ||
468 | config VMXNET3 | |
469 | tristate "VMware VMXNET3 ethernet driver" | |
470 | depends on PCI && INET | |
471 | depends on !(PAGE_SIZE_64KB || ARM64_64K_PAGES || \ | |
472 | IA64_PAGE_SIZE_64KB || MICROBLAZE_64K_PAGES || \ | |
473 | PARISC_PAGE_SIZE_64KB || PPC_64K_PAGES) | |
474 | help | |
475 | This driver supports VMware's vmxnet3 virtual ethernet NIC. | |
476 | To compile this driver as a module, choose M here: the | |
477 | module will be called vmxnet3. | |
478 | ||
479 | config FUJITSU_ES | |
480 | tristate "FUJITSU Extended Socket Network Device driver" | |
481 | depends on ACPI | |
482 | help | |
483 | This driver provides support for Extended Socket network device | |
484 | on Extended Partitioning of FUJITSU PRIMEQUEST 2000 E2 series. | |
485 | ||
486 | source "drivers/net/hyperv/Kconfig" | |
487 | ||
488 | endif # NETDEVICES |