Loading...
1# SPDX-License-Identifier: GPL-2.0-only
2#
3# Network device configuration
4#
5
6menuconfig NETDEVICES
7 default y if UML
8 depends on NET
9 bool "Network device support"
10 help
11 You can say N here if you don't intend to connect your Linux box to
12 any other computer at all.
13
14 You'll have to say Y if your computer contains a network card that
15 you want to use under Linux. If you are going to run SLIP or PPP over
16 telephone line or null modem cable you need say Y here. Connecting
17 two machines with parallel ports using PLIP needs this, as well as
18 AX.25/KISS for sending Internet traffic over amateur radio links.
19
20 See also "The Linux Network Administrator's Guide" by Olaf Kirch and
21 Terry Dawson. Available at <http://www.tldp.org/guides.html>.
22
23 If unsure, say Y.
24
25# All the following symbols are dependent on NETDEVICES - do not repeat
26# that for each of the symbols.
27if NETDEVICES
28
29config MII
30 tristate
31
32config NET_CORE
33 default y
34 bool "Network core driver support"
35 help
36 You can say N here if you do not intend to use any of the
37 networking core drivers (i.e. VLAN, bridging, bonding, etc.)
38
39if NET_CORE
40
41config BONDING
42 tristate "Bonding driver support"
43 depends on INET
44 depends on IPV6 || IPV6=n
45 depends on TLS || TLS_DEVICE=n
46 help
47 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
48 Channels together. This is called 'Etherchannel' by Cisco,
49 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
50
51 The driver supports multiple bonding modes to allow for both high
52 performance and high availability operation.
53
54 Refer to <file:Documentation/networking/bonding.rst> for more
55 information.
56
57 To compile this driver as a module, choose M here: the module
58 will be called bonding.
59
60config DUMMY
61 tristate "Dummy net driver support"
62 help
63 This is essentially a bit-bucket device (i.e. traffic you send to
64 this device is consigned into oblivion) with a configurable IP
65 address. It is most commonly used in order to make your currently
66 inactive SLIP address seem like a real address for local programs.
67 If you use SLIP or PPP, you might want to say Y here. It won't
68 enlarge your kernel. What a deal. Read about it in the Network
69 Administrator's Guide, available from
70 <http://www.tldp.org/docs.html#guide>.
71
72 To compile this driver as a module, choose M here: the module
73 will be called dummy.
74
75config WIREGUARD
76 tristate "WireGuard secure network tunnel"
77 depends on NET && INET
78 depends on IPV6 || !IPV6
79 depends on !KMSAN # KMSAN doesn't support the crypto configs below
80 select NET_UDP_TUNNEL
81 select DST_CACHE
82 select CRYPTO
83 select CRYPTO_LIB_CURVE25519
84 select CRYPTO_LIB_CHACHA20POLY1305
85 select CRYPTO_CHACHA20_X86_64 if X86 && 64BIT
86 select CRYPTO_POLY1305_X86_64 if X86 && 64BIT
87 select CRYPTO_BLAKE2S_X86 if X86 && 64BIT
88 select CRYPTO_CURVE25519_X86 if X86 && 64BIT
89 select CRYPTO_CHACHA20_NEON if ARM || (ARM64 && KERNEL_MODE_NEON)
90 select CRYPTO_POLY1305_NEON if ARM64 && KERNEL_MODE_NEON
91 select CRYPTO_POLY1305_ARM if ARM
92 select CRYPTO_BLAKE2S_ARM if ARM
93 select CRYPTO_CURVE25519_NEON if ARM && KERNEL_MODE_NEON
94 select CRYPTO_CHACHA_MIPS if CPU_MIPS32_R2
95 select CRYPTO_POLY1305_MIPS if MIPS
96 select CRYPTO_CHACHA_S390 if S390
97 help
98 WireGuard is a secure, fast, and easy to use replacement for IPSec
99 that uses modern cryptography and clever networking tricks. It's
100 designed to be fairly general purpose and abstract enough to fit most
101 use cases, while at the same time remaining extremely simple to
102 configure. See www.wireguard.com for more info.
103
104 It's safe to say Y or M here, as the driver is very lightweight and
105 is only in use when an administrator chooses to add an interface.
106
107config WIREGUARD_DEBUG
108 bool "Debugging checks and verbose messages"
109 depends on WIREGUARD
110 help
111 This will write log messages for handshake and other events
112 that occur for a WireGuard interface. It will also perform some
113 extra validation checks and unit tests at various points. This is
114 only useful for debugging.
115
116 Say N here unless you know what you're doing.
117
118config EQUALIZER
119 tristate "EQL (serial line load balancing) support"
120 help
121 If you have two serial connections to some other computer (this
122 usually requires two modems and two telephone lines) and you use
123 SLIP (the protocol for sending Internet traffic over telephone
124 lines) or PPP (a better SLIP) on them, you can make them behave like
125 one double speed connection using this driver. Naturally, this has
126 to be supported at the other end as well, either with a similar EQL
127 Linux driver or with a Livingston Portmaster 2e.
128
129 Say Y if you want this and read
130 <file:Documentation/networking/eql.rst>. You may also want to read
131 section 6.2 of the NET-3-HOWTO, available from
132 <http://www.tldp.org/docs.html#howto>.
133
134 To compile this driver as a module, choose M here: the module
135 will be called eql. If unsure, say N.
136
137config NET_FC
138 bool "Fibre Channel driver support"
139 depends on SCSI && PCI
140 help
141 Fibre Channel is a high speed serial protocol mainly used to connect
142 large storage devices to the computer; it is compatible with and
143 intended to replace SCSI.
144
145 If you intend to use Fibre Channel, you need to have a Fibre channel
146 adaptor card in your computer; say Y here and to the driver for your
147 adaptor below. You also should have said Y to "SCSI support" and
148 "SCSI generic support".
149
150config IFB
151 tristate "Intermediate Functional Block support"
152 depends on NET_ACT_MIRRED || NFT_FWD_NETDEV
153 select NET_REDIRECT
154 help
155 This is an intermediate driver that allows sharing of
156 resources.
157 To compile this driver as a module, choose M here: the module
158 will be called ifb. If you want to use more than one ifb
159 device at a time, you need to compile this driver as a module.
160 Instead of 'ifb', the devices will then be called 'ifb0',
161 'ifb1' etc.
162 Look at the iproute2 documentation directory for usage etc
163
164source "drivers/net/team/Kconfig"
165
166config MACVLAN
167 tristate "MAC-VLAN support"
168 help
169 This allows one to create virtual interfaces that map packets to
170 or from specific MAC addresses to a particular interface.
171
172 Macvlan devices can be added using the "ip" command from the
173 iproute2 package starting with the iproute2-2.6.23 release:
174
175 "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
176
177 To compile this driver as a module, choose M here: the module
178 will be called macvlan.
179
180config MACVTAP
181 tristate "MAC-VLAN based tap driver"
182 depends on MACVLAN
183 depends on INET
184 select TAP
185 help
186 This adds a specialized tap character device driver that is based
187 on the MAC-VLAN network interface, called macvtap. A macvtap device
188 can be added in the same way as a macvlan device, using 'type
189 macvtap', and then be accessed through the tap user space interface.
190
191 To compile this driver as a module, choose M here: the module
192 will be called macvtap.
193
194config IPVLAN_L3S
195 depends on NETFILTER
196 depends on IPVLAN
197 def_bool y
198 select NET_L3_MASTER_DEV
199
200config IPVLAN
201 tristate "IP-VLAN support"
202 depends on INET
203 depends on IPV6 || !IPV6
204 help
205 This allows one to create virtual devices off of a main interface
206 and packets will be delivered based on the dest L3 (IPv6/IPv4 addr)
207 on packets. All interfaces (including the main interface) share L2
208 making it transparent to the connected L2 switch.
209
210 Ipvlan devices can be added using the "ip" command from the
211 iproute2 package starting with the iproute2-3.19 release:
212
213 "ip link add link <main-dev> [ NAME ] type ipvlan"
214
215 To compile this driver as a module, choose M here: the module
216 will be called ipvlan.
217
218config IPVTAP
219 tristate "IP-VLAN based tap driver"
220 depends on IPVLAN
221 depends on INET
222 select TAP
223 help
224 This adds a specialized tap character device driver that is based
225 on the IP-VLAN network interface, called ipvtap. An ipvtap device
226 can be added in the same way as a ipvlan device, using 'type
227 ipvtap', and then be accessed through the tap user space interface.
228
229 To compile this driver as a module, choose M here: the module
230 will be called ipvtap.
231
232config VXLAN
233 tristate "Virtual eXtensible Local Area Network (VXLAN)"
234 depends on INET
235 select NET_UDP_TUNNEL
236 select GRO_CELLS
237 help
238 This allows one to create vxlan virtual interfaces that provide
239 Layer 2 Networks over Layer 3 Networks. VXLAN is often used
240 to tunnel virtual network infrastructure in virtualized environments.
241 For more information see:
242 http://tools.ietf.org/html/draft-mahalingam-dutt-dcops-vxlan-02
243
244 To compile this driver as a module, choose M here: the module
245 will be called vxlan.
246
247config GENEVE
248 tristate "Generic Network Virtualization Encapsulation"
249 depends on INET
250 depends on IPV6 || !IPV6
251 select NET_UDP_TUNNEL
252 select GRO_CELLS
253 help
254 This allows one to create geneve virtual interfaces that provide
255 Layer 2 Networks over Layer 3 Networks. GENEVE is often used
256 to tunnel virtual network infrastructure in virtualized environments.
257 For more information see:
258 http://tools.ietf.org/html/draft-gross-geneve-02
259
260 To compile this driver as a module, choose M here: the module
261 will be called geneve.
262
263config BAREUDP
264 tristate "Bare UDP Encapsulation"
265 depends on INET
266 depends on IPV6 || !IPV6
267 select NET_UDP_TUNNEL
268 select GRO_CELLS
269 help
270 This adds a bare UDP tunnel module for tunnelling different
271 kinds of traffic like MPLS, IP, etc. inside a UDP tunnel.
272
273 To compile this driver as a module, choose M here: the module
274 will be called bareudp.
275
276config GTP
277 tristate "GPRS Tunneling Protocol datapath (GTP-U)"
278 depends on INET
279 select NET_UDP_TUNNEL
280 help
281 This allows one to create gtp virtual interfaces that provide
282 the GPRS Tunneling Protocol datapath (GTP-U). This tunneling protocol
283 is used to prevent subscribers from accessing mobile carrier core
284 network infrastructure. This driver requires a userspace software that
285 implements the signaling protocol (GTP-C) to update its PDP context
286 base, such as OpenGGSN <http://git.osmocom.org/openggsn/). This
287 tunneling protocol is implemented according to the GSM TS 09.60 and
288 3GPP TS 29.060 standards.
289
290 To compile this drivers as a module, choose M here: the module
291 will be called gtp.
292
293config AMT
294 tristate "Automatic Multicast Tunneling (AMT)"
295 depends on INET && IP_MULTICAST
296 depends on IPV6 || !IPV6
297 select NET_UDP_TUNNEL
298 help
299 This allows one to create AMT(Automatic Multicast Tunneling)
300 virtual interfaces that provide multicast tunneling.
301 There are two roles, Gateway, and Relay.
302 Gateway Encapsulates IGMP/MLD traffic from listeners to the Relay.
303 Gateway Decapsulates multicast traffic from the Relay to Listeners.
304 Relay Encapsulates multicast traffic from Sources to Gateway.
305 Relay Decapsulates IGMP/MLD traffic from Gateway.
306
307 To compile this drivers as a module, choose M here: the module
308 will be called amt.
309
310config MACSEC
311 tristate "IEEE 802.1AE MAC-level encryption (MACsec)"
312 select CRYPTO
313 select CRYPTO_AES
314 select CRYPTO_GCM
315 select GRO_CELLS
316 help
317 MACsec is an encryption standard for Ethernet.
318
319config NETCONSOLE
320 tristate "Network console logging support"
321 help
322 If you want to log kernel messages over the network, enable this.
323 See <file:Documentation/networking/netconsole.rst> for details.
324
325config NETCONSOLE_DYNAMIC
326 bool "Dynamic reconfiguration of logging targets"
327 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
328 !(NETCONSOLE=y && CONFIGFS_FS=m)
329 help
330 This option enables the ability to dynamically reconfigure target
331 parameters (interface, IP addresses, port numbers, MAC addresses)
332 at runtime through a userspace interface exported using configfs.
333 See <file:Documentation/networking/netconsole.rst> for details.
334
335config NETCONSOLE_EXTENDED_LOG
336 bool "Set kernel extended message by default"
337 depends on NETCONSOLE
338 default n
339 help
340 Set extended log support for netconsole message. If this option is
341 set, log messages are transmitted with extended metadata header in a
342 format similar to /dev/kmsg. See
343 <file:Documentation/networking/netconsole.rst> for details.
344
345config NETCONSOLE_PREPEND_RELEASE
346 bool "Prepend kernel release version in the message by default"
347 depends on NETCONSOLE_EXTENDED_LOG
348 default n
349 help
350 Set kernel release to be prepended to each netconsole message by
351 default. If this option is set, the kernel release is prepended into
352 the first field of every netconsole message, so, the netconsole
353 server/peer can easily identify what kernel release is logging each
354 message. See <file:Documentation/networking/netconsole.rst> for
355 details.
356
357config NETPOLL
358 def_bool NETCONSOLE
359
360config NET_POLL_CONTROLLER
361 def_bool NETPOLL
362
363config NTB_NETDEV
364 tristate "Virtual Ethernet over NTB Transport"
365 depends on NTB_TRANSPORT
366
367config RIONET
368 tristate "RapidIO Ethernet over messaging driver support"
369 depends on RAPIDIO
370
371config RIONET_TX_SIZE
372 int "Number of outbound queue entries"
373 depends on RIONET
374 default "128"
375
376config RIONET_RX_SIZE
377 int "Number of inbound queue entries"
378 depends on RIONET
379 default "128"
380
381config TUN
382 tristate "Universal TUN/TAP device driver support"
383 depends on INET
384 select CRC32
385 help
386 TUN/TAP provides packet reception and transmission for user space
387 programs. It can be viewed as a simple Point-to-Point or Ethernet
388 device, which instead of receiving packets from a physical media,
389 receives them from user space program and instead of sending packets
390 via physical media writes them to the user space program.
391
392 When a program opens /dev/net/tun, driver creates and registers
393 corresponding net device tunX or tapX. After a program closed above
394 devices, driver will automatically delete tunXX or tapXX device and
395 all routes corresponding to it.
396
397 Please read <file:Documentation/networking/tuntap.rst> for more
398 information.
399
400 To compile this driver as a module, choose M here: the module
401 will be called tun.
402
403 If you don't know what to use this for, you don't need it.
404
405config TAP
406 tristate
407 help
408 This option is selected by any driver implementing tap user space
409 interface for a virtual interface to re-use core tap functionality.
410
411config TUN_VNET_CROSS_LE
412 bool "Support for cross-endian vnet headers on little-endian kernels"
413 default n
414 help
415 This option allows TUN/TAP and MACVTAP device drivers in a
416 little-endian kernel to parse vnet headers that come from a
417 big-endian legacy virtio device.
418
419 Userspace programs can control the feature using the TUNSETVNETBE
420 and TUNGETVNETBE ioctls.
421
422 Unless you have a little-endian system hosting a big-endian virtual
423 machine with a legacy virtio NIC, you should say N.
424
425config VETH
426 tristate "Virtual ethernet pair device"
427 select PAGE_POOL
428 help
429 This device is a local ethernet tunnel. Devices are created in pairs.
430 When one end receives the packet it appears on its pair and vice
431 versa.
432
433config VIRTIO_NET
434 tristate "Virtio network driver"
435 depends on VIRTIO
436 select NET_FAILOVER
437 select DIMLIB
438 help
439 This is the virtual network driver for virtio. It can be used with
440 QEMU based VMMs (like KVM or Xen). Say Y or M.
441
442config NLMON
443 tristate "Virtual netlink monitoring device"
444 help
445 This option enables a monitoring net device for netlink skbs. The
446 purpose of this is to analyze netlink messages with packet sockets.
447 Thus applications like tcpdump will be able to see local netlink
448 messages if they tap into the netlink device, record pcaps for further
449 diagnostics, etc. This is mostly intended for developers or support
450 to debug netlink issues. If unsure, say N.
451
452config NETKIT
453 bool "BPF-programmable network device"
454 depends on BPF_SYSCALL
455 help
456 The netkit device is a virtual networking device where BPF programs
457 can be attached to the device(s) transmission routine in order to
458 implement the driver's internal logic. The device can be configured
459 to operate in L3 or L2 mode. If unsure, say N.
460
461config NET_VRF
462 tristate "Virtual Routing and Forwarding (Lite)"
463 depends on IP_MULTIPLE_TABLES
464 depends on NET_L3_MASTER_DEV
465 depends on IPV6 || IPV6=n
466 depends on IPV6_MULTIPLE_TABLES || IPV6=n
467 help
468 This option enables the support for mapping interfaces into VRF's. The
469 support enables VRF devices.
470
471config VSOCKMON
472 tristate "Virtual vsock monitoring device"
473 depends on VHOST_VSOCK
474 help
475 This option enables a monitoring net device for vsock sockets. It is
476 mostly intended for developers or support to debug vsock issues. If
477 unsure, say N.
478
479config MHI_NET
480 tristate "MHI network driver"
481 depends on MHI_BUS
482 help
483 This is the network driver for MHI bus. It can be used with
484 QCOM based WWAN modems for IP or QMAP/rmnet protocol (like SDX55).
485 Say Y or M.
486
487endif # NET_CORE
488
489config SUNGEM_PHY
490 tristate
491
492source "drivers/net/arcnet/Kconfig"
493
494source "drivers/atm/Kconfig"
495
496source "drivers/net/caif/Kconfig"
497
498source "drivers/net/dsa/Kconfig"
499
500source "drivers/net/ethernet/Kconfig"
501
502source "drivers/net/fddi/Kconfig"
503
504source "drivers/net/hippi/Kconfig"
505
506source "drivers/net/ipa/Kconfig"
507
508config NET_SB1000
509 tristate "General Instruments Surfboard 1000"
510 depends on PNP
511 help
512 This is a driver for the General Instrument (also known as
513 NextLevel) SURFboard 1000 internal
514 cable modem. This is an ISA card which is used by a number of cable
515 TV companies to provide cable modem access. It's a one-way
516 downstream-only cable modem, meaning that your upstream net link is
517 provided by your regular phone modem.
518
519 At present this driver only compiles as a module, so say M here if
520 you have this card. The module will be called sb1000. Then read
521 <file:Documentation/networking/device_drivers/cable/sb1000.rst> for
522 information on how to use this module, as it needs special ppp
523 scripts for establishing a connection. Further documentation
524 and the necessary scripts can be found at:
525
526 <http://www.jacksonville.net/~fventuri/>
527 <http://home.adelphia.net/~siglercm/sb1000.html>
528 <http://linuxpower.cx/~cable/>
529
530 If you don't have this card, of course say N.
531
532source "drivers/net/phy/Kconfig"
533
534source "drivers/net/pse-pd/Kconfig"
535
536source "drivers/net/can/Kconfig"
537
538source "drivers/net/mctp/Kconfig"
539
540source "drivers/net/mdio/Kconfig"
541
542source "drivers/net/pcs/Kconfig"
543
544source "drivers/net/plip/Kconfig"
545
546source "drivers/net/ppp/Kconfig"
547
548source "drivers/net/slip/Kconfig"
549
550source "drivers/s390/net/Kconfig"
551
552source "drivers/net/usb/Kconfig"
553
554source "drivers/net/wireless/Kconfig"
555
556source "drivers/net/wan/Kconfig"
557
558source "drivers/net/ieee802154/Kconfig"
559
560source "drivers/net/wwan/Kconfig"
561
562config XEN_NETDEV_FRONTEND
563 tristate "Xen network device frontend driver"
564 depends on XEN
565 select XEN_XENBUS_FRONTEND
566 select PAGE_POOL
567 default y
568 help
569 This driver provides support for Xen paravirtual network
570 devices exported by a Xen network driver domain (often
571 domain 0).
572
573 The corresponding Linux backend driver is enabled by the
574 CONFIG_XEN_NETDEV_BACKEND option.
575
576 If you are compiling a kernel for use as Xen guest, you
577 should say Y here. To compile this driver as a module, chose
578 M here: the module will be called xen-netfront.
579
580config XEN_NETDEV_BACKEND
581 tristate "Xen backend network device"
582 depends on XEN_BACKEND
583 help
584 This driver allows the kernel to act as a Xen network driver
585 domain which exports paravirtual network devices to other
586 Xen domains. These devices can be accessed by any operating
587 system that implements a compatible front end.
588
589 The corresponding Linux frontend driver is enabled by the
590 CONFIG_XEN_NETDEV_FRONTEND configuration option.
591
592 The backend driver presents a standard network device
593 endpoint for each paravirtual network device to the driver
594 domain network stack. These can then be bridged or routed
595 etc in order to provide full network connectivity.
596
597 If you are compiling a kernel to run in a Xen network driver
598 domain (often this is domain 0) you should say Y here. To
599 compile this driver as a module, chose M here: the module
600 will be called xen-netback.
601
602config VMXNET3
603 tristate "VMware VMXNET3 ethernet driver"
604 depends on PCI && INET
605 depends on PAGE_SIZE_LESS_THAN_64KB
606 select PAGE_POOL
607 help
608 This driver supports VMware's vmxnet3 virtual ethernet NIC.
609 To compile this driver as a module, choose M here: the
610 module will be called vmxnet3.
611
612config FUJITSU_ES
613 tristate "FUJITSU Extended Socket Network Device driver"
614 depends on ACPI
615 help
616 This driver provides support for Extended Socket network device
617 on Extended Partitioning of FUJITSU PRIMEQUEST 2000 E2 series.
618
619source "drivers/net/thunderbolt/Kconfig"
620source "drivers/net/hyperv/Kconfig"
621
622config NETDEVSIM
623 tristate "Simulated networking device"
624 depends on DEBUG_FS
625 depends on INET
626 depends on IPV6 || IPV6=n
627 depends on PSAMPLE || PSAMPLE=n
628 depends on PTP_1588_CLOCK_MOCK || PTP_1588_CLOCK_MOCK=n
629 select NET_DEVLINK
630 help
631 This driver is a developer testing tool and software model that can
632 be used to test various control path networking APIs, especially
633 HW-offload related.
634
635 To compile this driver as a module, choose M here: the module
636 will be called netdevsim.
637
638config NET_FAILOVER
639 tristate "Failover driver"
640 select FAILOVER
641 help
642 This provides an automated failover mechanism via APIs to create
643 and destroy a failover master netdev and manages a primary and
644 standby slave netdevs that get registered via the generic failover
645 infrastructure. This can be used by paravirtual drivers to enable
646 an alternate low latency datapath. It also enables live migration of
647 a VM with direct attached VF by failing over to the paravirtual
648 datapath when the VF is unplugged.
649
650config NETDEV_LEGACY_INIT
651 bool
652 depends on ISA
653 help
654 Drivers that call netdev_boot_setup_check() should select this
655 symbol, everything else no longer needs it.
656
657endif # NETDEVICES
1#
2# Network device configuration
3#
4
5menuconfig 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.
26if NETDEVICES
27
28config MII
29 tristate
30
31config 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
38if NET_CORE
39
40config 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
58config 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
73config 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
92config 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
105config 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
118source "drivers/net/team/Kconfig"
119
120config 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
134config MACVTAP
135 tristate "MAC-VLAN based tap driver"
136 depends on MACVLAN
137 depends on INET
138 help
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.
143
144 To compile this driver as a module, choose M here: the module
145 will be called macvtap.
146
147
148config IPVLAN
149 tristate "IP-VLAN support"
150 depends on INET
151 depends on IPV6
152 depends on NETFILTER
153 depends on NET_L3_MASTER_DEV
154 ---help---
155 This allows one to create virtual devices off of a main interface
156 and packets will be delivered based on the dest L3 (IPv6/IPv4 addr)
157 on packets. All interfaces (including the main interface) share L2
158 making it transparent to the connected L2 switch.
159
160 Ipvlan devices can be added using the "ip" command from the
161 iproute2 package starting with the iproute2-3.19 release:
162
163 "ip link add link <main-dev> [ NAME ] type ipvlan"
164
165 To compile this driver as a module, choose M here: the module
166 will be called ipvlan.
167
168
169config VXLAN
170 tristate "Virtual eXtensible Local Area Network (VXLAN)"
171 depends on INET
172 select NET_UDP_TUNNEL
173 ---help---
174 This allows one to create vxlan virtual interfaces that provide
175 Layer 2 Networks over Layer 3 Networks. VXLAN is often used
176 to tunnel virtual network infrastructure in virtualized environments.
177 For more information see:
178 http://tools.ietf.org/html/draft-mahalingam-dutt-dcops-vxlan-02
179
180 To compile this driver as a module, choose M here: the module
181 will be called vxlan.
182
183config GENEVE
184 tristate "Generic Network Virtualization Encapsulation"
185 depends on INET && NET_UDP_TUNNEL
186 select NET_IP_TUNNEL
187 ---help---
188 This allows one to create geneve virtual interfaces that provide
189 Layer 2 Networks over Layer 3 Networks. GENEVE is often used
190 to tunnel virtual network infrastructure in virtualized environments.
191 For more information see:
192 http://tools.ietf.org/html/draft-gross-geneve-02
193
194 To compile this driver as a module, choose M here: the module
195 will be called geneve.
196
197config GTP
198 tristate "GPRS Tunneling Protocol datapath (GTP-U)"
199 depends on INET && NET_UDP_TUNNEL
200 select NET_IP_TUNNEL
201 ---help---
202 This allows one to create gtp virtual interfaces that provide
203 the GPRS Tunneling Protocol datapath (GTP-U). This tunneling protocol
204 is used to prevent subscribers from accessing mobile carrier core
205 network infrastructure. This driver requires a userspace software that
206 implements the signaling protocol (GTP-C) to update its PDP context
207 base, such as OpenGGSN <http://git.osmocom.org/openggsn/). This
208 tunneling protocol is implemented according to the GSM TS 09.60 and
209 3GPP TS 29.060 standards.
210
211 To compile this drivers as a module, choose M here: the module
212 wil be called gtp.
213
214config MACSEC
215 tristate "IEEE 802.1AE MAC-level encryption (MACsec)"
216 select CRYPTO
217 select CRYPTO_AES
218 select CRYPTO_GCM
219 ---help---
220 MACsec is an encryption standard for Ethernet.
221
222config NETCONSOLE
223 tristate "Network console logging support"
224 ---help---
225 If you want to log kernel messages over the network, enable this.
226 See <file:Documentation/networking/netconsole.txt> for details.
227
228config NETCONSOLE_DYNAMIC
229 bool "Dynamic reconfiguration of logging targets"
230 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
231 !(NETCONSOLE=y && CONFIGFS_FS=m)
232 help
233 This option enables the ability to dynamically reconfigure target
234 parameters (interface, IP addresses, port numbers, MAC addresses)
235 at runtime through a userspace interface exported using configfs.
236 See <file:Documentation/networking/netconsole.txt> for details.
237
238config NETPOLL
239 def_bool NETCONSOLE
240 select SRCU
241
242config NET_POLL_CONTROLLER
243 def_bool NETPOLL
244
245config NTB_NETDEV
246 tristate "Virtual Ethernet over NTB Transport"
247 depends on NTB_TRANSPORT
248
249config RIONET
250 tristate "RapidIO Ethernet over messaging driver support"
251 depends on RAPIDIO
252
253config RIONET_TX_SIZE
254 int "Number of outbound queue entries"
255 depends on RIONET
256 default "128"
257
258config RIONET_RX_SIZE
259 int "Number of inbound queue entries"
260 depends on RIONET
261 default "128"
262
263config TUN
264 tristate "Universal TUN/TAP device driver support"
265 depends on INET
266 select CRC32
267 ---help---
268 TUN/TAP provides packet reception and transmission for user space
269 programs. It can be viewed as a simple Point-to-Point or Ethernet
270 device, which instead of receiving packets from a physical media,
271 receives them from user space program and instead of sending packets
272 via physical media writes them to the user space program.
273
274 When a program opens /dev/net/tun, driver creates and registers
275 corresponding net device tunX or tapX. After a program closed above
276 devices, driver will automatically delete tunXX or tapXX device and
277 all routes corresponding to it.
278
279 Please read <file:Documentation/networking/tuntap.txt> for more
280 information.
281
282 To compile this driver as a module, choose M here: the module
283 will be called tun.
284
285 If you don't know what to use this for, you don't need it.
286
287config TUN_VNET_CROSS_LE
288 bool "Support for cross-endian vnet headers on little-endian kernels"
289 default n
290 ---help---
291 This option allows TUN/TAP and MACVTAP device drivers in a
292 little-endian kernel to parse vnet headers that come from a
293 big-endian legacy virtio device.
294
295 Userspace programs can control the feature using the TUNSETVNETBE
296 and TUNGETVNETBE ioctls.
297
298 Unless you have a little-endian system hosting a big-endian virtual
299 machine with a legacy virtio NIC, you should say N.
300
301config VETH
302 tristate "Virtual ethernet pair device"
303 ---help---
304 This device is a local ethernet tunnel. Devices are created in pairs.
305 When one end receives the packet it appears on its pair and vice
306 versa.
307
308config VIRTIO_NET
309 tristate "Virtio network driver"
310 depends on VIRTIO
311 ---help---
312 This is the virtual network driver for virtio. It can be used with
313 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
314
315config NLMON
316 tristate "Virtual netlink monitoring device"
317 ---help---
318 This option enables a monitoring net device for netlink skbs. The
319 purpose of this is to analyze netlink messages with packet sockets.
320 Thus applications like tcpdump will be able to see local netlink
321 messages if they tap into the netlink device, record pcaps for further
322 diagnostics, etc. This is mostly intended for developers or support
323 to debug netlink issues. If unsure, say N.
324
325config NET_VRF
326 tristate "Virtual Routing and Forwarding (Lite)"
327 depends on IP_MULTIPLE_TABLES
328 depends on NET_L3_MASTER_DEV
329 depends on IPV6 || IPV6=n
330 depends on IPV6_MULTIPLE_TABLES || IPV6=n
331 ---help---
332 This option enables the support for mapping interfaces into VRF's. The
333 support enables VRF devices.
334
335endif # NET_CORE
336
337config SUNGEM_PHY
338 tristate
339
340source "drivers/net/arcnet/Kconfig"
341
342source "drivers/atm/Kconfig"
343
344source "drivers/net/caif/Kconfig"
345
346source "drivers/net/dsa/Kconfig"
347
348source "drivers/net/ethernet/Kconfig"
349
350source "drivers/net/fddi/Kconfig"
351
352source "drivers/net/hippi/Kconfig"
353
354config NET_SB1000
355 tristate "General Instruments Surfboard 1000"
356 depends on PNP
357 ---help---
358 This is a driver for the General Instrument (also known as
359 NextLevel) SURFboard 1000 internal
360 cable modem. This is an ISA card which is used by a number of cable
361 TV companies to provide cable modem access. It's a one-way
362 downstream-only cable modem, meaning that your upstream net link is
363 provided by your regular phone modem.
364
365 At present this driver only compiles as a module, so say M here if
366 you have this card. The module will be called sb1000. Then read
367 <file:Documentation/networking/README.sb1000> for information on how
368 to use this module, as it needs special ppp scripts for establishing
369 a connection. Further documentation and the necessary scripts can be
370 found at:
371
372 <http://www.jacksonville.net/~fventuri/>
373 <http://home.adelphia.net/~siglercm/sb1000.html>
374 <http://linuxpower.cx/~cable/>
375
376 If you don't have this card, of course say N.
377
378source "drivers/net/phy/Kconfig"
379
380source "drivers/net/plip/Kconfig"
381
382source "drivers/net/ppp/Kconfig"
383
384source "drivers/net/slip/Kconfig"
385
386source "drivers/s390/net/Kconfig"
387
388source "drivers/net/usb/Kconfig"
389
390source "drivers/net/wireless/Kconfig"
391
392source "drivers/net/wimax/Kconfig"
393
394source "drivers/net/wan/Kconfig"
395
396source "drivers/net/ieee802154/Kconfig"
397
398config XEN_NETDEV_FRONTEND
399 tristate "Xen network device frontend driver"
400 depends on XEN
401 select XEN_XENBUS_FRONTEND
402 default y
403 help
404 This driver provides support for Xen paravirtual network
405 devices exported by a Xen network driver domain (often
406 domain 0).
407
408 The corresponding Linux backend driver is enabled by the
409 CONFIG_XEN_NETDEV_BACKEND option.
410
411 If you are compiling a kernel for use as Xen guest, you
412 should say Y here. To compile this driver as a module, chose
413 M here: the module will be called xen-netfront.
414
415config XEN_NETDEV_BACKEND
416 tristate "Xen backend network device"
417 depends on XEN_BACKEND
418 help
419 This driver allows the kernel to act as a Xen network driver
420 domain which exports paravirtual network devices to other
421 Xen domains. These devices can be accessed by any operating
422 system that implements a compatible front end.
423
424 The corresponding Linux frontend driver is enabled by the
425 CONFIG_XEN_NETDEV_FRONTEND configuration option.
426
427 The backend driver presents a standard network device
428 endpoint for each paravirtual network device to the driver
429 domain network stack. These can then be bridged or routed
430 etc in order to provide full network connectivity.
431
432 If you are compiling a kernel to run in a Xen network driver
433 domain (often this is domain 0) you should say Y here. To
434 compile this driver as a module, chose M here: the module
435 will be called xen-netback.
436
437config VMXNET3
438 tristate "VMware VMXNET3 ethernet driver"
439 depends on PCI && INET
440 help
441 This driver supports VMware's vmxnet3 virtual ethernet NIC.
442 To compile this driver as a module, choose M here: the
443 module will be called vmxnet3.
444
445config FUJITSU_ES
446 tristate "FUJITSU Extended Socket Network Device driver"
447 depends on ACPI
448 help
449 This driver provides support for Extended Socket network device
450 on Extended Partitioning of FUJITSU PRIMEQUEST 2000 E2 series.
451
452source "drivers/net/hyperv/Kconfig"
453
454endif # NETDEVICES