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.
150 tristate "IP-VLAN support"
152 This allows one to create virtual devices off of a main interface
153 and packets will be delivered based on the dest L3 (IPv6/IPv4 addr)
154 on packets. All interfaces (including the main interface) share L2
155 making it transparent to the connected L2 switch.
157 Ipvlan devices can be added using the "ip" command from the
158 iproute2 package starting with the iproute2-X.Y.ZZ release:
160 "ip link add link <main-dev> [ NAME ] type ipvlan"
162 To compile this driver as a module, choose M here: the module
163 will be called ipvlan.
167 tristate "Virtual eXtensible Local Area Network (VXLAN)"
169 select NET_UDP_TUNNEL
171 This allows one to create vxlan virtual interfaces that provide
172 Layer 2 Networks over Layer 3 Networks. VXLAN is often used
173 to tunnel virtual network infrastructure in virtualized environments.
174 For more information see:
175 http://tools.ietf.org/html/draft-mahalingam-dutt-dcops-vxlan-02
177 To compile this driver as a module, choose M here: the module
178 will be called vxlan.
181 tristate "Network console logging support"
183 If you want to log kernel messages over the network, enable this.
184 See <file:Documentation/networking/netconsole.txt> for details.
186 config NETCONSOLE_DYNAMIC
187 bool "Dynamic reconfiguration of logging targets"
188 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
189 !(NETCONSOLE=y && CONFIGFS_FS=m)
191 This option enables the ability to dynamically reconfigure target
192 parameters (interface, IP addresses, port numbers, MAC addresses)
193 at runtime through a userspace interface exported using configfs.
194 See <file:Documentation/networking/netconsole.txt> for details.
199 config NET_POLL_CONTROLLER
203 tristate "Virtual Ethernet over NTB"
207 tristate "RapidIO Ethernet over messaging driver support"
210 config RIONET_TX_SIZE
211 int "Number of outbound queue entries"
215 config RIONET_RX_SIZE
216 int "Number of inbound queue entries"
221 tristate "Universal TUN/TAP device driver support"
225 TUN/TAP provides packet reception and transmission for user space
226 programs. It can be viewed as a simple Point-to-Point or Ethernet
227 device, which instead of receiving packets from a physical media,
228 receives them from user space program and instead of sending packets
229 via physical media writes them to the user space program.
231 When a program opens /dev/net/tun, driver creates and registers
232 corresponding net device tunX or tapX. After a program closed above
233 devices, driver will automatically delete tunXX or tapXX device and
234 all routes corresponding to it.
236 Please read <file:Documentation/networking/tuntap.txt> for more
239 To compile this driver as a module, choose M here: the module
242 If you don't know what to use this for, you don't need it.
245 tristate "Virtual ethernet pair device"
247 This device is a local ethernet tunnel. Devices are created in pairs.
248 When one end receives the packet it appears on its pair and vice
252 tristate "Virtio network driver"
256 This is the virtual network driver for virtio. It can be used with
257 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
260 tristate "Virtual netlink monitoring device"
262 This option enables a monitoring net device for netlink skbs. The
263 purpose of this is to analyze netlink messages with packet sockets.
264 Thus applications like tcpdump will be able to see local netlink
265 messages if they tap into the netlink device, record pcaps for further
266 diagnostics, etc. This is mostly intended for developers or support
267 to debug netlink issues. If unsure, say N.
274 source "drivers/net/arcnet/Kconfig"
276 source "drivers/atm/Kconfig"
278 source "drivers/net/caif/Kconfig"
280 source "drivers/net/dsa/Kconfig"
282 source "drivers/net/ethernet/Kconfig"
284 source "drivers/net/fddi/Kconfig"
286 source "drivers/net/hippi/Kconfig"
289 tristate "General Instruments Surfboard 1000"
292 This is a driver for the General Instrument (also known as
293 NextLevel) SURFboard 1000 internal
294 cable modem. This is an ISA card which is used by a number of cable
295 TV companies to provide cable modem access. It's a one-way
296 downstream-only cable modem, meaning that your upstream net link is
297 provided by your regular phone modem.
299 At present this driver only compiles as a module, so say M here if
300 you have this card. The module will be called sb1000. Then read
301 <file:Documentation/networking/README.sb1000> for information on how
302 to use this module, as it needs special ppp scripts for establishing
303 a connection. Further documentation and the necessary scripts can be
306 <http://www.jacksonville.net/~fventuri/>
307 <http://home.adelphia.net/~siglercm/sb1000.html>
308 <http://linuxpower.cx/~cable/>
310 If you don't have this card, of course say N.
312 source "drivers/net/phy/Kconfig"
314 source "drivers/net/plip/Kconfig"
316 source "drivers/net/ppp/Kconfig"
318 source "drivers/net/slip/Kconfig"
320 source "drivers/s390/net/Kconfig"
322 source "drivers/net/usb/Kconfig"
324 source "drivers/net/wireless/Kconfig"
326 source "drivers/net/wimax/Kconfig"
328 source "drivers/net/wan/Kconfig"
330 source "drivers/net/ieee802154/Kconfig"
332 config XEN_NETDEV_FRONTEND
333 tristate "Xen network device frontend driver"
335 select XEN_XENBUS_FRONTEND
338 This driver provides support for Xen paravirtual network
339 devices exported by a Xen network driver domain (often
342 The corresponding Linux backend driver is enabled by the
343 CONFIG_XEN_NETDEV_BACKEND option.
345 If you are compiling a kernel for use as Xen guest, you
346 should say Y here. To compile this driver as a module, chose
347 M here: the module will be called xen-netfront.
349 config XEN_NETDEV_BACKEND
350 tristate "Xen backend network device"
351 depends on XEN_BACKEND
353 This driver allows the kernel to act as a Xen network driver
354 domain which exports paravirtual network devices to other
355 Xen domains. These devices can be accessed by any operating
356 system that implements a compatible front end.
358 The corresponding Linux frontend driver is enabled by the
359 CONFIG_XEN_NETDEV_FRONTEND configuration option.
361 The backend driver presents a standard network device
362 endpoint for each paravirtual network device to the driver
363 domain network stack. These can then be bridged or routed
364 etc in order to provide full network connectivity.
366 If you are compiling a kernel to run in a Xen network driver
367 domain (often this is domain 0) you should say Y here. To
368 compile this driver as a module, chose M here: the module
369 will be called xen-netback.
372 tristate "VMware VMXNET3 ethernet driver"
373 depends on PCI && INET
375 This driver supports VMware's vmxnet3 virtual ethernet NIC.
376 To compile this driver as a module, choose M here: the
377 module will be called vmxnet3.
379 source "drivers/net/hyperv/Kconfig"