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"
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 depends on IPV6 || !IPV6
154 select NET_L3_MASTER_DEV
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.
161 Ipvlan devices can be added using the "ip" command from the
162 iproute2 package starting with the iproute2-3.19 release:
164 "ip link add link <main-dev> [ NAME ] type ipvlan"
166 To compile this driver as a module, choose M here: the module
167 will be called ipvlan.
170 tristate "IP-VLAN based tap driver"
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.
180 To compile this driver as a module, choose M here: the module
181 will be called ipvtap.
184 tristate "Virtual eXtensible Local Area Network (VXLAN)"
186 select NET_UDP_TUNNEL
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
195 To compile this driver as a module, choose M here: the module
196 will be called vxlan.
199 tristate "Generic Network Virtualization Encapsulation"
200 depends on INET && NET_UDP_TUNNEL
201 depends on IPV6 || !IPV6
205 This allows one to create geneve virtual interfaces that provide
206 Layer 2 Networks over Layer 3 Networks. GENEVE is often used
207 to tunnel virtual network infrastructure in virtualized environments.
208 For more information see:
209 http://tools.ietf.org/html/draft-gross-geneve-02
211 To compile this driver as a module, choose M here: the module
212 will be called geneve.
215 tristate "GPRS Tunneling Protocol datapath (GTP-U)"
216 depends on INET && NET_UDP_TUNNEL
219 This allows one to create gtp virtual interfaces that provide
220 the GPRS Tunneling Protocol datapath (GTP-U). This tunneling protocol
221 is used to prevent subscribers from accessing mobile carrier core
222 network infrastructure. This driver requires a userspace software that
223 implements the signaling protocol (GTP-C) to update its PDP context
224 base, such as OpenGGSN <http://git.osmocom.org/openggsn/). This
225 tunneling protocol is implemented according to the GSM TS 09.60 and
226 3GPP TS 29.060 standards.
228 To compile this drivers as a module, choose M here: the module
232 tristate "IEEE 802.1AE MAC-level encryption (MACsec)"
238 MACsec is an encryption standard for Ethernet.
241 tristate "Network console logging support"
243 If you want to log kernel messages over the network, enable this.
244 See <file:Documentation/networking/netconsole.txt> for details.
246 config NETCONSOLE_DYNAMIC
247 bool "Dynamic reconfiguration of logging targets"
248 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
249 !(NETCONSOLE=y && CONFIGFS_FS=m)
251 This option enables the ability to dynamically reconfigure target
252 parameters (interface, IP addresses, port numbers, MAC addresses)
253 at runtime through a userspace interface exported using configfs.
254 See <file:Documentation/networking/netconsole.txt> for details.
260 config NET_POLL_CONTROLLER
264 tristate "Virtual Ethernet over NTB Transport"
265 depends on NTB_TRANSPORT
268 tristate "RapidIO Ethernet over messaging driver support"
271 config RIONET_TX_SIZE
272 int "Number of outbound queue entries"
276 config RIONET_RX_SIZE
277 int "Number of inbound queue entries"
282 tristate "Universal TUN/TAP device driver support"
286 TUN/TAP provides packet reception and transmission for user space
287 programs. It can be viewed as a simple Point-to-Point or Ethernet
288 device, which instead of receiving packets from a physical media,
289 receives them from user space program and instead of sending packets
290 via physical media writes them to the user space program.
292 When a program opens /dev/net/tun, driver creates and registers
293 corresponding net device tunX or tapX. After a program closed above
294 devices, driver will automatically delete tunXX or tapXX device and
295 all routes corresponding to it.
297 Please read <file:Documentation/networking/tuntap.txt> for more
300 To compile this driver as a module, choose M here: the module
303 If you don't know what to use this for, you don't need it.
308 This option is selected by any driver implementing tap user space
309 interface for a virtual interface to re-use core tap functionality.
311 config TUN_VNET_CROSS_LE
312 bool "Support for cross-endian vnet headers on little-endian kernels"
315 This option allows TUN/TAP and MACVTAP device drivers in a
316 little-endian kernel to parse vnet headers that come from a
317 big-endian legacy virtio device.
319 Userspace programs can control the feature using the TUNSETVNETBE
320 and TUNGETVNETBE ioctls.
322 Unless you have a little-endian system hosting a big-endian virtual
323 machine with a legacy virtio NIC, you should say N.
326 tristate "Virtual ethernet pair device"
328 This device is a local ethernet tunnel. Devices are created in pairs.
329 When one end receives the packet it appears on its pair and vice
333 tristate "Virtio network driver"
336 This is the virtual network driver for virtio. It can be used with
337 QEMU based VMMs (like KVM or Xen). Say Y or M.
340 tristate "Virtual netlink monitoring device"
342 This option enables a monitoring net device for netlink skbs. The
343 purpose of this is to analyze netlink messages with packet sockets.
344 Thus applications like tcpdump will be able to see local netlink
345 messages if they tap into the netlink device, record pcaps for further
346 diagnostics, etc. This is mostly intended for developers or support
347 to debug netlink issues. If unsure, say N.
350 tristate "Virtual Routing and Forwarding (Lite)"
351 depends on IP_MULTIPLE_TABLES
352 depends on NET_L3_MASTER_DEV
353 depends on IPV6 || IPV6=n
354 depends on IPV6_MULTIPLE_TABLES || IPV6=n
356 This option enables the support for mapping interfaces into VRF's. The
357 support enables VRF devices.
360 tristate "Virtual vsock monitoring device"
361 depends on VHOST_VSOCK
363 This option enables a monitoring net device for vsock sockets. It is
364 mostly intended for developers or support to debug vsock issues. If
372 source "drivers/net/arcnet/Kconfig"
374 source "drivers/atm/Kconfig"
376 source "drivers/net/caif/Kconfig"
378 source "drivers/net/dsa/Kconfig"
380 source "drivers/net/ethernet/Kconfig"
382 source "drivers/net/fddi/Kconfig"
384 source "drivers/net/hippi/Kconfig"
387 tristate "General Instruments Surfboard 1000"
390 This is a driver for the General Instrument (also known as
391 NextLevel) SURFboard 1000 internal
392 cable modem. This is an ISA card which is used by a number of cable
393 TV companies to provide cable modem access. It's a one-way
394 downstream-only cable modem, meaning that your upstream net link is
395 provided by your regular phone modem.
397 At present this driver only compiles as a module, so say M here if
398 you have this card. The module will be called sb1000. Then read
399 <file:Documentation/networking/README.sb1000> for information on how
400 to use this module, as it needs special ppp scripts for establishing
401 a connection. Further documentation and the necessary scripts can be
404 <http://www.jacksonville.net/~fventuri/>
405 <http://home.adelphia.net/~siglercm/sb1000.html>
406 <http://linuxpower.cx/~cable/>
408 If you don't have this card, of course say N.
410 source "drivers/net/phy/Kconfig"
412 source "drivers/net/plip/Kconfig"
414 source "drivers/net/ppp/Kconfig"
416 source "drivers/net/slip/Kconfig"
418 source "drivers/s390/net/Kconfig"
420 source "drivers/net/usb/Kconfig"
422 source "drivers/net/wireless/Kconfig"
424 source "drivers/net/wimax/Kconfig"
426 source "drivers/net/wan/Kconfig"
428 source "drivers/net/ieee802154/Kconfig"
430 config XEN_NETDEV_FRONTEND
431 tristate "Xen network device frontend driver"
433 select XEN_XENBUS_FRONTEND
436 This driver provides support for Xen paravirtual network
437 devices exported by a Xen network driver domain (often
440 The corresponding Linux backend driver is enabled by the
441 CONFIG_XEN_NETDEV_BACKEND option.
443 If you are compiling a kernel for use as Xen guest, you
444 should say Y here. To compile this driver as a module, chose
445 M here: the module will be called xen-netfront.
447 config XEN_NETDEV_BACKEND
448 tristate "Xen backend network device"
449 depends on XEN_BACKEND
451 This driver allows the kernel to act as a Xen network driver
452 domain which exports paravirtual network devices to other
453 Xen domains. These devices can be accessed by any operating
454 system that implements a compatible front end.
456 The corresponding Linux frontend driver is enabled by the
457 CONFIG_XEN_NETDEV_FRONTEND configuration option.
459 The backend driver presents a standard network device
460 endpoint for each paravirtual network device to the driver
461 domain network stack. These can then be bridged or routed
462 etc in order to provide full network connectivity.
464 If you are compiling a kernel to run in a Xen network driver
465 domain (often this is domain 0) you should say Y here. To
466 compile this driver as a module, chose M here: the module
467 will be called xen-netback.
470 tristate "VMware VMXNET3 ethernet driver"
471 depends on PCI && INET
472 depends on !(PAGE_SIZE_64KB || ARM64_64K_PAGES || \
473 IA64_PAGE_SIZE_64KB || MICROBLAZE_64K_PAGES || \
474 PARISC_PAGE_SIZE_64KB || PPC_64K_PAGES)
476 This driver supports VMware's vmxnet3 virtual ethernet NIC.
477 To compile this driver as a module, choose M here: the
478 module will be called vmxnet3.
481 tristate "FUJITSU Extended Socket Network Device driver"
484 This driver provides support for Extended Socket network device
485 on Extended Partitioning of FUJITSU PRIMEQUEST 2000 E2 series.
487 config THUNDERBOLT_NET
488 tristate "Networking over Thunderbolt cable"
489 depends on THUNDERBOLT && INET
491 Select this if you want to create network between two
492 computers over a Thunderbolt cable. The driver supports Apple
493 ThunderboltIP protocol and allows communication with any host
494 supporting the same protocol including Windows and macOS.
496 To compile this driver a module, choose M here. The module will be
497 called thunderbolt-net.
499 source "drivers/net/hyperv/Kconfig"
502 tristate "Simulated networking device"
504 depends on MAY_USE_DEVLINK
506 This driver is a developer testing tool and software model that can
507 be used to test various control path networking APIs, especially
510 To compile this driver as a module, choose M here: the module
511 will be called netdevsim.