2 # Network device configuration
8 bool "Network device support"
10 You can say N here if you don't intend to connect your Linux box to
11 any other computer at all.
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.
19 See also "The Linux Network Administrator's Guide" by Olaf Kirch and
20 Terry Dawson. Available at <http://www.tldp.org/guides.html>.
24 # All the following symbols are dependent on NETDEVICES - do not repeat
25 # that for each of the symbols.
33 bool "Network core driver support"
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.)
41 tristate "Bonding driver support"
43 depends on IPV6 || IPV6=n
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.
49 The driver supports multiple bonding modes to allow for both high
50 performance and high availability operation.
52 Refer to <file:Documentation/networking/bonding.txt> for more
55 To compile this driver as a module, choose M here: the module
56 will be called bonding.
59 tristate "Dummy net driver support"
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>.
71 To compile this driver as a module, choose M here: the module
75 tristate "EQL (serial line load balancing) support"
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.
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>.
90 To compile this driver as a module, choose M here: the module
91 will be called eql. If unsure, say N.
94 bool "Fibre Channel driver support"
95 depends on SCSI && PCI
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.
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".
107 tristate "Intermediate Functional Block support"
108 depends on NET_CLS_ACT
110 This is an intermediate driver that allows sharing of
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',
117 Look at the iproute2 documentation directory for usage etc
119 source "drivers/net/team/Kconfig"
122 tristate "MAC-VLAN support"
124 This allows one to create virtual interfaces that map packets to
125 or from specific MAC addresses to a particular interface.
127 Macvlan devices can be added using the "ip" command from the
128 iproute2 package starting with the iproute2-2.6.23 release:
130 "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
132 To compile this driver as a module, choose M here: the module
133 will be called macvlan.
136 tristate "MAC-VLAN based tap driver"
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.
145 To compile this driver as a module, choose M here: the module
146 will be called macvtap.
149 tristate "Virtual eXtensible Local Area Network (VXLAN)"
153 This allows one to create vxlan virtual interfaces that provide
154 Layer 2 Networks over Layer 3 Networks. VXLAN is often used
155 to tunnel virtual network infrastructure in virtualized environments.
156 For more information see:
157 http://tools.ietf.org/html/draft-mahalingam-dutt-dcops-vxlan-02
159 To compile this driver as a module, choose M here: the module
160 will be called vxlan.
163 tristate "Network console logging support"
165 If you want to log kernel messages over the network, enable this.
166 See <file:Documentation/networking/netconsole.txt> for details.
168 config NETCONSOLE_DYNAMIC
169 bool "Dynamic reconfiguration of logging targets"
170 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
171 !(NETCONSOLE=y && CONFIGFS_FS=m)
173 This option enables the ability to dynamically reconfigure target
174 parameters (interface, IP addresses, port numbers, MAC addresses)
175 at runtime through a userspace interface exported using configfs.
176 See <file:Documentation/networking/netconsole.txt> for details.
182 bool "Netpoll traffic trapping"
186 config NET_POLL_CONTROLLER
190 tristate "Virtual Ethernet over NTB"
194 tristate "RapidIO Ethernet over messaging driver support"
197 config RIONET_TX_SIZE
198 int "Number of outbound queue entries"
202 config RIONET_RX_SIZE
203 int "Number of inbound queue entries"
208 tristate "Universal TUN/TAP device driver support"
212 TUN/TAP provides packet reception and transmission for user space
213 programs. It can be viewed as a simple Point-to-Point or Ethernet
214 device, which instead of receiving packets from a physical media,
215 receives them from user space program and instead of sending packets
216 via physical media writes them to the user space program.
218 When a program opens /dev/net/tun, driver creates and registers
219 corresponding net device tunX or tapX. After a program closed above
220 devices, driver will automatically delete tunXX or tapXX device and
221 all routes corresponding to it.
223 Please read <file:Documentation/networking/tuntap.txt> for more
226 To compile this driver as a module, choose M here: the module
229 If you don't know what to use this for, you don't need it.
232 tristate "Virtual ethernet pair device"
234 This device is a local ethernet tunnel. Devices are created in pairs.
235 When one end receives the packet it appears on its pair and vice
239 tristate "Virtio network driver"
243 This is the virtual network driver for virtio. It can be used with
244 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
247 tristate "Virtual netlink monitoring device"
249 This option enables a monitoring net device for netlink skbs. The
250 purpose of this is to analyze netlink messages with packet sockets.
251 Thus applications like tcpdump will be able to see local netlink
252 messages if they tap into the netlink device, record pcaps for further
253 diagnostics, etc. This is mostly intended for developers or support
254 to debug netlink issues. If unsure, say N.
261 source "drivers/net/arcnet/Kconfig"
263 source "drivers/atm/Kconfig"
265 source "drivers/net/caif/Kconfig"
267 source "drivers/net/dsa/Kconfig"
269 source "drivers/net/ethernet/Kconfig"
271 source "drivers/net/fddi/Kconfig"
273 source "drivers/net/hippi/Kconfig"
276 tristate "General Instruments Surfboard 1000"
279 This is a driver for the General Instrument (also known as
280 NextLevel) SURFboard 1000 internal
281 cable modem. This is an ISA card which is used by a number of cable
282 TV companies to provide cable modem access. It's a one-way
283 downstream-only cable modem, meaning that your upstream net link is
284 provided by your regular phone modem.
286 At present this driver only compiles as a module, so say M here if
287 you have this card. The module will be called sb1000. Then read
288 <file:Documentation/networking/README.sb1000> for information on how
289 to use this module, as it needs special ppp scripts for establishing
290 a connection. Further documentation and the necessary scripts can be
293 <http://www.jacksonville.net/~fventuri/>
294 <http://home.adelphia.net/~siglercm/sb1000.html>
295 <http://linuxpower.cx/~cable/>
297 If you don't have this card, of course say N.
299 source "drivers/net/phy/Kconfig"
301 source "drivers/net/plip/Kconfig"
303 source "drivers/net/ppp/Kconfig"
305 source "drivers/net/slip/Kconfig"
307 source "drivers/s390/net/Kconfig"
309 source "drivers/net/usb/Kconfig"
311 source "drivers/net/wireless/Kconfig"
313 source "drivers/net/wimax/Kconfig"
315 source "drivers/net/wan/Kconfig"
317 source "drivers/net/ieee802154/Kconfig"
319 config XEN_NETDEV_FRONTEND
320 tristate "Xen network device frontend driver"
322 select XEN_XENBUS_FRONTEND
325 This driver provides support for Xen paravirtual network
326 devices exported by a Xen network driver domain (often
329 The corresponding Linux backend driver is enabled by the
330 CONFIG_XEN_NETDEV_BACKEND option.
332 If you are compiling a kernel for use as Xen guest, you
333 should say Y here. To compile this driver as a module, chose
334 M here: the module will be called xen-netfront.
336 config XEN_NETDEV_BACKEND
337 tristate "Xen backend network device"
338 depends on XEN_BACKEND
340 This driver allows the kernel to act as a Xen network driver
341 domain which exports paravirtual network devices to other
342 Xen domains. These devices can be accessed by any operating
343 system that implements a compatible front end.
345 The corresponding Linux frontend driver is enabled by the
346 CONFIG_XEN_NETDEV_FRONTEND configuration option.
348 The backend driver presents a standard network device
349 endpoint for each paravirtual network device to the driver
350 domain network stack. These can then be bridged or routed
351 etc in order to provide full network connectivity.
353 If you are compiling a kernel to run in a Xen network driver
354 domain (often this is domain 0) you should say Y here. To
355 compile this driver as a module, chose M here: the module
356 will be called xen-netback.
359 tristate "VMware VMXNET3 ethernet driver"
360 depends on PCI && INET
362 This driver supports VMware's vmxnet3 virtual ethernet NIC.
363 To compile this driver as a module, choose M here: the
364 module will be called vmxnet3.
366 source "drivers/net/hyperv/Kconfig"