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. 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>.
70 To compile this driver as a module, choose M here: the module
74 tristate "EQL (serial line load balancing) support"
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.
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>.
89 To compile this driver as a module, choose M here: the module
90 will be called eql. If unsure, say N.
93 bool "Fibre Channel driver support"
94 depends on SCSI && PCI
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.
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".
106 tristate "Intermediate Functional Block support"
107 depends on NET_CLS_ACT
109 This is an intermediate driver that allows sharing of
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',
116 Look at the iproute2 documentation directory for usage etc
118 source "drivers/net/team/Kconfig"
121 tristate "MAC-VLAN support"
123 This allows one to create virtual interfaces that map packets to
124 or from specific MAC addresses to a particular interface.
126 Macvlan devices can be added using the "ip" command from the
127 iproute2 package starting with the iproute2-2.6.23 release:
129 "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
131 To compile this driver as a module, choose M here: the module
132 will be called macvlan.
135 tristate "MAC-VLAN based tap driver"
139 This adds a specialized tap character device driver that is based
140 on the MAC-VLAN network interface, called macvtap. A macvtap device
141 can be added in the same way as a macvlan device, using 'type
142 macvtap', and then be accessed through the tap user space interface.
144 To compile this driver as a module, choose M here: the module
145 will be called macvtap.
149 tristate "IP-VLAN support"
152 depends on NET_L3_MASTER_DEV
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.
159 Ipvlan devices can be added using the "ip" command from the
160 iproute2 package starting with the iproute2-3.19 release:
162 "ip link add link <main-dev> [ NAME ] type ipvlan"
164 To compile this driver as a module, choose M here: the module
165 will be called ipvlan.
169 tristate "Virtual eXtensible Local Area Network (VXLAN)"
171 select NET_UDP_TUNNEL
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
179 To compile this driver as a module, choose M here: the module
180 will be called vxlan.
183 tristate "Generic Network Virtualization Encapsulation"
184 depends on INET && NET_UDP_TUNNEL
187 This allows one to create geneve virtual interfaces that provide
188 Layer 2 Networks over Layer 3 Networks. GENEVE is often used
189 to tunnel virtual network infrastructure in virtualized environments.
190 For more information see:
191 http://tools.ietf.org/html/draft-gross-geneve-02
193 To compile this driver as a module, choose M here: the module
194 will be called geneve.
197 tristate "GPRS Tunneling Protocol datapath (GTP-U)"
198 depends on INET && NET_UDP_TUNNEL
201 This allows one to create gtp virtual interfaces that provide
202 the GPRS Tunneling Protocol datapath (GTP-U). This tunneling protocol
203 is used to prevent subscribers from accessing mobile carrier core
204 network infrastructure. This driver requires a userspace software that
205 implements the signaling protocol (GTP-C) to update its PDP context
206 base, such as OpenGGSN <http://git.osmocom.org/openggsn/). This
207 tunneling protocol is implemented according to the GSM TS 09.60 and
208 3GPP TS 29.060 standards.
210 To compile this drivers as a module, choose M here: the module
214 tristate "IEEE 802.1AE MAC-level encryption (MACsec)"
219 MACsec is an encryption standard for Ethernet.
222 tristate "Network console logging support"
224 If you want to log kernel messages over the network, enable this.
225 See <file:Documentation/networking/netconsole.txt> for details.
227 config NETCONSOLE_DYNAMIC
228 bool "Dynamic reconfiguration of logging targets"
229 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
230 !(NETCONSOLE=y && CONFIGFS_FS=m)
232 This option enables the ability to dynamically reconfigure target
233 parameters (interface, IP addresses, port numbers, MAC addresses)
234 at runtime through a userspace interface exported using configfs.
235 See <file:Documentation/networking/netconsole.txt> for details.
241 config NET_POLL_CONTROLLER
245 tristate "Virtual Ethernet over NTB Transport"
246 depends on NTB_TRANSPORT
249 tristate "RapidIO Ethernet over messaging driver support"
252 config RIONET_TX_SIZE
253 int "Number of outbound queue entries"
257 config RIONET_RX_SIZE
258 int "Number of inbound queue entries"
263 tristate "Universal TUN/TAP device driver support"
267 TUN/TAP provides packet reception and transmission for user space
268 programs. It can be viewed as a simple Point-to-Point or Ethernet
269 device, which instead of receiving packets from a physical media,
270 receives them from user space program and instead of sending packets
271 via physical media writes them to the user space program.
273 When a program opens /dev/net/tun, driver creates and registers
274 corresponding net device tunX or tapX. After a program closed above
275 devices, driver will automatically delete tunXX or tapXX device and
276 all routes corresponding to it.
278 Please read <file:Documentation/networking/tuntap.txt> for more
281 To compile this driver as a module, choose M here: the module
284 If you don't know what to use this for, you don't need it.
286 config TUN_VNET_CROSS_LE
287 bool "Support for cross-endian vnet headers on little-endian kernels"
290 This option allows TUN/TAP and MACVTAP device drivers in a
291 little-endian kernel to parse vnet headers that come from a
292 big-endian legacy virtio device.
294 Userspace programs can control the feature using the TUNSETVNETBE
295 and TUNGETVNETBE ioctls.
297 Unless you have a little-endian system hosting a big-endian virtual
298 machine with a legacy virtio NIC, you should say N.
301 tristate "Virtual ethernet pair device"
303 This device is a local ethernet tunnel. Devices are created in pairs.
304 When one end receives the packet it appears on its pair and vice
308 tristate "Virtio network driver"
311 This is the virtual network driver for virtio. It can be used with
312 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
315 tristate "Virtual netlink monitoring device"
317 This option enables a monitoring net device for netlink skbs. The
318 purpose of this is to analyze netlink messages with packet sockets.
319 Thus applications like tcpdump will be able to see local netlink
320 messages if they tap into the netlink device, record pcaps for further
321 diagnostics, etc. This is mostly intended for developers or support
322 to debug netlink issues. If unsure, say N.
325 tristate "Virtual Routing and Forwarding (Lite)"
326 depends on IP_MULTIPLE_TABLES
327 depends on NET_L3_MASTER_DEV
328 depends on IPV6 || IPV6=n
329 depends on IPV6_MULTIPLE_TABLES || IPV6=n
331 This option enables the support for mapping interfaces into VRF's. The
332 support enables VRF devices.
339 source "drivers/net/arcnet/Kconfig"
341 source "drivers/atm/Kconfig"
343 source "drivers/net/caif/Kconfig"
345 source "drivers/net/dsa/Kconfig"
347 source "drivers/net/ethernet/Kconfig"
349 source "drivers/net/fddi/Kconfig"
351 source "drivers/net/hippi/Kconfig"
354 tristate "General Instruments Surfboard 1000"
357 This is a driver for the General Instrument (also known as
358 NextLevel) SURFboard 1000 internal
359 cable modem. This is an ISA card which is used by a number of cable
360 TV companies to provide cable modem access. It's a one-way
361 downstream-only cable modem, meaning that your upstream net link is
362 provided by your regular phone modem.
364 At present this driver only compiles as a module, so say M here if
365 you have this card. The module will be called sb1000. Then read
366 <file:Documentation/networking/README.sb1000> for information on how
367 to use this module, as it needs special ppp scripts for establishing
368 a connection. Further documentation and the necessary scripts can be
371 <http://www.jacksonville.net/~fventuri/>
372 <http://home.adelphia.net/~siglercm/sb1000.html>
373 <http://linuxpower.cx/~cable/>
375 If you don't have this card, of course say N.
377 source "drivers/net/phy/Kconfig"
379 source "drivers/net/plip/Kconfig"
381 source "drivers/net/ppp/Kconfig"
383 source "drivers/net/slip/Kconfig"
385 source "drivers/s390/net/Kconfig"
387 source "drivers/net/usb/Kconfig"
389 source "drivers/net/wireless/Kconfig"
391 source "drivers/net/wimax/Kconfig"
393 source "drivers/net/wan/Kconfig"
395 source "drivers/net/ieee802154/Kconfig"
397 config XEN_NETDEV_FRONTEND
398 tristate "Xen network device frontend driver"
400 select XEN_XENBUS_FRONTEND
403 This driver provides support for Xen paravirtual network
404 devices exported by a Xen network driver domain (often
407 The corresponding Linux backend driver is enabled by the
408 CONFIG_XEN_NETDEV_BACKEND option.
410 If you are compiling a kernel for use as Xen guest, you
411 should say Y here. To compile this driver as a module, chose
412 M here: the module will be called xen-netfront.
414 config XEN_NETDEV_BACKEND
415 tristate "Xen backend network device"
416 depends on XEN_BACKEND
418 This driver allows the kernel to act as a Xen network driver
419 domain which exports paravirtual network devices to other
420 Xen domains. These devices can be accessed by any operating
421 system that implements a compatible front end.
423 The corresponding Linux frontend driver is enabled by the
424 CONFIG_XEN_NETDEV_FRONTEND configuration option.
426 The backend driver presents a standard network device
427 endpoint for each paravirtual network device to the driver
428 domain network stack. These can then be bridged or routed
429 etc in order to provide full network connectivity.
431 If you are compiling a kernel to run in a Xen network driver
432 domain (often this is domain 0) you should say Y here. To
433 compile this driver as a module, chose M here: the module
434 will be called xen-netback.
437 tristate "VMware VMXNET3 ethernet driver"
438 depends on PCI && INET
440 This driver supports VMware's vmxnet3 virtual ethernet NIC.
441 To compile this driver as a module, choose M here: the
442 module will be called vmxnet3.
445 tristate "FUJITSU Extended Socket Network Device driver"
448 This driver provides support for Extended Socket network device
449 on Extended Partitioning of FUJITSU PRIMEQUEST 2000 E2 series.
451 source "drivers/net/hyperv/Kconfig"