tjh.dev
Linux kernel mirror (for testing)
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel
os
linux
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 OVPN
119 tristate "OpenVPN data channel offload"
120 depends on NET && INET
121 depends on IPV6 || !IPV6
122 select DST_CACHE
123 select NET_UDP_TUNNEL
124 select CRYPTO
125 select CRYPTO_AES
126 select CRYPTO_GCM
127 select CRYPTO_CHACHA20POLY1305
128 select STREAM_PARSER
129 help
130 This module enhances the performance of the OpenVPN userspace software
131 by offloading the data channel processing to kernelspace.
132
133config EQUALIZER
134 tristate "EQL (serial line load balancing) support"
135 help
136 If you have two serial connections to some other computer (this
137 usually requires two modems and two telephone lines) and you use
138 SLIP (the protocol for sending Internet traffic over telephone
139 lines) or PPP (a better SLIP) on them, you can make them behave like
140 one double speed connection using this driver. Naturally, this has
141 to be supported at the other end as well, either with a similar EQL
142 Linux driver or with a Livingston Portmaster 2e.
143
144 Say Y if you want this and read
145 <file:Documentation/networking/eql.rst>. You may also want to read
146 section 6.2 of the NET-3-HOWTO, available from
147 <http://www.tldp.org/docs.html#howto>.
148
149 To compile this driver as a module, choose M here: the module
150 will be called eql. If unsure, say N.
151
152config NET_FC
153 bool "Fibre Channel driver support"
154 depends on SCSI && PCI
155 help
156 Fibre Channel is a high speed serial protocol mainly used to connect
157 large storage devices to the computer; it is compatible with and
158 intended to replace SCSI.
159
160 If you intend to use Fibre Channel, you need to have a Fibre channel
161 adaptor card in your computer; say Y here and to the driver for your
162 adaptor below. You also should have said Y to "SCSI support" and
163 "SCSI generic support".
164
165config IFB
166 tristate "Intermediate Functional Block support"
167 depends on NET_ACT_MIRRED || NFT_FWD_NETDEV
168 select NET_REDIRECT
169 help
170 This is an intermediate driver that allows sharing of
171 resources.
172 To compile this driver as a module, choose M here: the module
173 will be called ifb. If you want to use more than one ifb
174 device at a time, you need to compile this driver as a module.
175 Instead of 'ifb', the devices will then be called 'ifb0',
176 'ifb1' etc.
177 Look at the iproute2 documentation directory for usage etc
178
179source "drivers/net/team/Kconfig"
180
181config MACVLAN
182 tristate "MAC-VLAN support"
183 help
184 This allows one to create virtual interfaces that map packets to
185 or from specific MAC addresses to a particular interface.
186
187 Macvlan devices can be added using the "ip" command from the
188 iproute2 package starting with the iproute2-2.6.23 release:
189
190 "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
191
192 To compile this driver as a module, choose M here: the module
193 will be called macvlan.
194
195config MACVTAP
196 tristate "MAC-VLAN based tap driver"
197 depends on MACVLAN
198 depends on INET
199 select TAP
200 help
201 This adds a specialized tap character device driver that is based
202 on the MAC-VLAN network interface, called macvtap. A macvtap device
203 can be added in the same way as a macvlan device, using 'type
204 macvtap', and then be accessed through the tap user space interface.
205
206 To compile this driver as a module, choose M here: the module
207 will be called macvtap.
208
209config IPVLAN_L3S
210 depends on NETFILTER
211 depends on IPVLAN
212 def_bool y
213 select NET_L3_MASTER_DEV
214
215config IPVLAN
216 tristate "IP-VLAN support"
217 depends on INET
218 depends on IPV6 || !IPV6
219 help
220 This allows one to create virtual devices off of a main interface
221 and packets will be delivered based on the dest L3 (IPv6/IPv4 addr)
222 on packets. All interfaces (including the main interface) share L2
223 making it transparent to the connected L2 switch.
224
225 Ipvlan devices can be added using the "ip" command from the
226 iproute2 package starting with the iproute2-3.19 release:
227
228 "ip link add link <main-dev> [ NAME ] type ipvlan"
229
230 To compile this driver as a module, choose M here: the module
231 will be called ipvlan.
232
233config IPVTAP
234 tristate "IP-VLAN based tap driver"
235 depends on IPVLAN
236 depends on INET
237 select TAP
238 help
239 This adds a specialized tap character device driver that is based
240 on the IP-VLAN network interface, called ipvtap. An ipvtap device
241 can be added in the same way as a ipvlan device, using 'type
242 ipvtap', and then be accessed through the tap user space interface.
243
244 To compile this driver as a module, choose M here: the module
245 will be called ipvtap.
246
247config VXLAN
248 tristate "Virtual eXtensible Local Area Network (VXLAN)"
249 depends on INET
250 select NET_UDP_TUNNEL
251 select GRO_CELLS
252 help
253 This allows one to create vxlan virtual interfaces that provide
254 Layer 2 Networks over Layer 3 Networks. VXLAN is often used
255 to tunnel virtual network infrastructure in virtualized environments.
256 For more information see:
257 http://tools.ietf.org/html/draft-mahalingam-dutt-dcops-vxlan-02
258
259 To compile this driver as a module, choose M here: the module
260 will be called vxlan.
261
262config GENEVE
263 tristate "Generic Network Virtualization Encapsulation"
264 depends on INET
265 depends on IPV6 || !IPV6
266 select NET_UDP_TUNNEL
267 select GRO_CELLS
268 help
269 This allows one to create geneve virtual interfaces that provide
270 Layer 2 Networks over Layer 3 Networks. GENEVE is often used
271 to tunnel virtual network infrastructure in virtualized environments.
272 For more information see:
273 http://tools.ietf.org/html/draft-gross-geneve-02
274
275 To compile this driver as a module, choose M here: the module
276 will be called geneve.
277
278config BAREUDP
279 tristate "Bare UDP Encapsulation"
280 depends on INET
281 depends on IPV6 || !IPV6
282 select NET_UDP_TUNNEL
283 select GRO_CELLS
284 help
285 This adds a bare UDP tunnel module for tunnelling different
286 kinds of traffic like MPLS, IP, etc. inside a UDP tunnel.
287
288 To compile this driver as a module, choose M here: the module
289 will be called bareudp.
290
291config GTP
292 tristate "GPRS Tunneling Protocol datapath (GTP-U)"
293 depends on INET
294 select NET_UDP_TUNNEL
295 help
296 This allows one to create gtp virtual interfaces that provide
297 the GPRS Tunneling Protocol datapath (GTP-U). This tunneling protocol
298 is used to prevent subscribers from accessing mobile carrier core
299 network infrastructure. This driver requires a userspace software that
300 implements the signaling protocol (GTP-C) to update its PDP context
301 base, such as OpenGGSN <http://git.osmocom.org/openggsn/). This
302 tunneling protocol is implemented according to the GSM TS 09.60 and
303 3GPP TS 29.060 standards.
304
305 To compile this drivers as a module, choose M here: the module
306 will be called gtp.
307
308config PFCP
309 tristate "Packet Forwarding Control Protocol (PFCP)"
310 depends on INET
311 select NET_UDP_TUNNEL
312 help
313 This allows one to create PFCP virtual interfaces that allows to
314 set up software and hardware offload of PFCP packets.
315 Note that this module does not support PFCP protocol in the kernel space.
316 There is no support for parsing any PFCP messages.
317
318 To compile this drivers as a module, choose M here: the module
319 will be called pfcp.
320
321config AMT
322 tristate "Automatic Multicast Tunneling (AMT)"
323 depends on INET && IP_MULTICAST
324 depends on IPV6 || !IPV6
325 select NET_UDP_TUNNEL
326 help
327 This allows one to create AMT(Automatic Multicast Tunneling)
328 virtual interfaces that provide multicast tunneling.
329 There are two roles, Gateway, and Relay.
330 Gateway Encapsulates IGMP/MLD traffic from listeners to the Relay.
331 Gateway Decapsulates multicast traffic from the Relay to Listeners.
332 Relay Encapsulates multicast traffic from Sources to Gateway.
333 Relay Decapsulates IGMP/MLD traffic from Gateway.
334
335 To compile this drivers as a module, choose M here: the module
336 will be called amt.
337
338config MACSEC
339 tristate "IEEE 802.1AE MAC-level encryption (MACsec)"
340 select CRYPTO
341 select CRYPTO_AES
342 select CRYPTO_GCM
343 select GRO_CELLS
344 help
345 MACsec is an encryption standard for Ethernet.
346
347config NETCONSOLE
348 tristate "Network console logging support"
349 help
350 If you want to log kernel messages over the network, enable this.
351 See <file:Documentation/networking/netconsole.rst> for details.
352
353config NETCONSOLE_DYNAMIC
354 bool "Dynamic reconfiguration of logging targets"
355 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
356 !(NETCONSOLE=y && CONFIGFS_FS=m)
357 help
358 This option enables the ability to dynamically reconfigure target
359 parameters (interface, IP addresses, port numbers, MAC addresses)
360 at runtime through a userspace interface exported using configfs.
361 See <file:Documentation/networking/netconsole.rst> for details.
362
363config NETCONSOLE_EXTENDED_LOG
364 bool "Set kernel extended message by default"
365 depends on NETCONSOLE
366 default n
367 help
368 Set extended log support for netconsole message. If this option is
369 set, log messages are transmitted with extended metadata header in a
370 format similar to /dev/kmsg. See
371 <file:Documentation/networking/netconsole.rst> for details.
372
373config NETCONSOLE_PREPEND_RELEASE
374 bool "Prepend kernel release version in the message by default"
375 depends on NETCONSOLE_EXTENDED_LOG
376 default n
377 help
378 Set kernel release to be prepended to each netconsole message by
379 default. If this option is set, the kernel release is prepended into
380 the first field of every netconsole message, so, the netconsole
381 server/peer can easily identify what kernel release is logging each
382 message. See <file:Documentation/networking/netconsole.rst> for
383 details.
384
385config NETPOLL
386 def_bool NETCONSOLE
387
388config NET_POLL_CONTROLLER
389 def_bool NETPOLL
390
391config NTB_NETDEV
392 tristate "Virtual Ethernet over NTB Transport"
393 depends on NTB_TRANSPORT
394
395config RIONET
396 tristate "RapidIO Ethernet over messaging driver support"
397 depends on RAPIDIO
398
399config RIONET_TX_SIZE
400 int "Number of outbound queue entries"
401 depends on RIONET
402 default "128"
403
404config RIONET_RX_SIZE
405 int "Number of inbound queue entries"
406 depends on RIONET
407 default "128"
408
409config TUN
410 tristate "Universal TUN/TAP device driver support"
411 depends on INET
412 select CRC32
413 help
414 TUN/TAP provides packet reception and transmission for user space
415 programs. It can be viewed as a simple Point-to-Point or Ethernet
416 device, which instead of receiving packets from a physical media,
417 receives them from user space program and instead of sending packets
418 via physical media writes them to the user space program.
419
420 When a program opens /dev/net/tun, driver creates and registers
421 corresponding net device tunX or tapX. After a program closed above
422 devices, driver will automatically delete tunXX or tapXX device and
423 all routes corresponding to it.
424
425 Please read <file:Documentation/networking/tuntap.rst> for more
426 information.
427
428 To compile this driver as a module, choose M here: the module
429 will be called tun.
430
431 If you don't know what to use this for, you don't need it.
432
433config TAP
434 tristate
435 help
436 This option is selected by any driver implementing tap user space
437 interface for a virtual interface to re-use core tap functionality.
438
439config TUN_VNET_CROSS_LE
440 bool "Support for cross-endian vnet headers on little-endian kernels"
441 default n
442 help
443 This option allows TUN/TAP and MACVTAP device drivers in a
444 little-endian kernel to parse vnet headers that come from a
445 big-endian legacy virtio device.
446
447 Userspace programs can control the feature using the TUNSETVNETBE
448 and TUNGETVNETBE ioctls.
449
450 Unless you have a little-endian system hosting a big-endian virtual
451 machine with a legacy virtio NIC, you should say N.
452
453config VETH
454 tristate "Virtual ethernet pair device"
455 select PAGE_POOL
456 help
457 This device is a local ethernet tunnel. Devices are created in pairs.
458 When one end receives the packet it appears on its pair and vice
459 versa.
460
461config VIRTIO_NET
462 tristate "Virtio network driver"
463 depends on VIRTIO
464 select NET_FAILOVER
465 select DIMLIB
466 help
467 This is the virtual network driver for virtio. It can be used with
468 QEMU based VMMs (like KVM or Xen). Say Y or M.
469
470config NLMON
471 tristate "Virtual netlink monitoring device"
472 help
473 This option enables a monitoring net device for netlink skbs. The
474 purpose of this is to analyze netlink messages with packet sockets.
475 Thus applications like tcpdump will be able to see local netlink
476 messages if they tap into the netlink device, record pcaps for further
477 diagnostics, etc. This is mostly intended for developers or support
478 to debug netlink issues. If unsure, say N.
479
480config NETKIT
481 bool "BPF-programmable network device"
482 depends on BPF_SYSCALL
483 help
484 The netkit device is a virtual networking device where BPF programs
485 can be attached to the device(s) transmission routine in order to
486 implement the driver's internal logic. The device can be configured
487 to operate in L3 or L2 mode. If unsure, say N.
488
489config NET_VRF
490 tristate "Virtual Routing and Forwarding (Lite)"
491 depends on IP_MULTIPLE_TABLES
492 depends on NET_L3_MASTER_DEV
493 depends on IPV6 || IPV6=n
494 depends on IPV6_MULTIPLE_TABLES || IPV6=n
495 help
496 This option enables the support for mapping interfaces into VRF's. The
497 support enables VRF devices.
498
499config VSOCKMON
500 tristate "Virtual vsock monitoring device"
501 depends on VHOST_VSOCK
502 help
503 This option enables a monitoring net device for vsock sockets. It is
504 mostly intended for developers or support to debug vsock issues. If
505 unsure, say N.
506
507config MHI_NET
508 tristate "MHI network driver"
509 depends on MHI_BUS
510 help
511 This is the network driver for MHI bus. It can be used with
512 QCOM based WWAN modems for IP or QMAP/rmnet protocol (like SDX55).
513 Say Y or M.
514
515endif # NET_CORE
516
517config SUNGEM_PHY
518 tristate
519
520source "drivers/net/arcnet/Kconfig"
521
522source "drivers/atm/Kconfig"
523
524source "drivers/net/caif/Kconfig"
525
526source "drivers/net/dsa/Kconfig"
527
528source "drivers/net/ethernet/Kconfig"
529
530source "drivers/net/fddi/Kconfig"
531
532source "drivers/net/hippi/Kconfig"
533
534source "drivers/net/ipa/Kconfig"
535
536source "drivers/net/phy/Kconfig"
537
538source "drivers/net/pse-pd/Kconfig"
539
540source "drivers/net/can/Kconfig"
541
542source "drivers/net/mctp/Kconfig"
543
544source "drivers/net/mdio/Kconfig"
545
546source "drivers/net/pcs/Kconfig"
547
548source "drivers/net/plip/Kconfig"
549
550source "drivers/net/ppp/Kconfig"
551
552source "drivers/net/slip/Kconfig"
553
554source "drivers/s390/net/Kconfig"
555
556source "drivers/net/usb/Kconfig"
557
558source "drivers/net/wireless/Kconfig"
559
560source "drivers/net/wan/Kconfig"
561
562source "drivers/net/ieee802154/Kconfig"
563
564source "drivers/net/wwan/Kconfig"
565
566config XEN_NETDEV_FRONTEND
567 tristate "Xen network device frontend driver"
568 depends on XEN
569 select XEN_XENBUS_FRONTEND
570 select PAGE_POOL
571 default y
572 help
573 This driver provides support for Xen paravirtual network
574 devices exported by a Xen network driver domain (often
575 domain 0).
576
577 The corresponding Linux backend driver is enabled by the
578 CONFIG_XEN_NETDEV_BACKEND option.
579
580 If you are compiling a kernel for use as Xen guest, you
581 should say Y here. To compile this driver as a module, chose
582 M here: the module will be called xen-netfront.
583
584config XEN_NETDEV_BACKEND
585 tristate "Xen backend network device"
586 depends on XEN_BACKEND
587 help
588 This driver allows the kernel to act as a Xen network driver
589 domain which exports paravirtual network devices to other
590 Xen domains. These devices can be accessed by any operating
591 system that implements a compatible front end.
592
593 The corresponding Linux frontend driver is enabled by the
594 CONFIG_XEN_NETDEV_FRONTEND configuration option.
595
596 The backend driver presents a standard network device
597 endpoint for each paravirtual network device to the driver
598 domain network stack. These can then be bridged or routed
599 etc in order to provide full network connectivity.
600
601 If you are compiling a kernel to run in a Xen network driver
602 domain (often this is domain 0) you should say Y here. To
603 compile this driver as a module, chose M here: the module
604 will be called xen-netback.
605
606config VMXNET3
607 tristate "VMware VMXNET3 ethernet driver"
608 depends on PCI && INET
609 depends on PAGE_SIZE_LESS_THAN_64KB
610 select PAGE_POOL
611 help
612 This driver supports VMware's vmxnet3 virtual ethernet NIC.
613 To compile this driver as a module, choose M here: the
614 module will be called vmxnet3.
615
616config FUJITSU_ES
617 tristate "FUJITSU Extended Socket Network Device driver"
618 depends on ACPI
619 help
620 This driver provides support for Extended Socket network device
621 on Extended Partitioning of FUJITSU PRIMEQUEST 2000 E2 series.
622
623source "drivers/net/thunderbolt/Kconfig"
624source "drivers/net/hyperv/Kconfig"
625
626config NETDEVSIM
627 tristate "Simulated networking device"
628 depends on DEBUG_FS
629 depends on INET
630 depends on IPV6 || IPV6=n
631 depends on PSAMPLE || PSAMPLE=n
632 depends on PTP_1588_CLOCK_MOCK || PTP_1588_CLOCK_MOCK=n
633 select NET_DEVLINK
634 select PAGE_POOL
635 select NET_SHAPER
636 help
637 This driver is a developer testing tool and software model that can
638 be used to test various control path networking APIs, especially
639 HW-offload related.
640
641 To compile this driver as a module, choose M here: the module
642 will be called netdevsim.
643
644config NET_FAILOVER
645 tristate "Failover driver"
646 select FAILOVER
647 help
648 This provides an automated failover mechanism via APIs to create
649 and destroy a failover master netdev and manages a primary and
650 standby slave netdevs that get registered via the generic failover
651 infrastructure. This can be used by paravirtual drivers to enable
652 an alternate low latency datapath. It also enables live migration of
653 a VM with direct attached VF by failing over to the paravirtual
654 datapath when the VF is unplugged.
655
656config NETDEV_LEGACY_INIT
657 bool
658 depends on ISA
659 help
660 Drivers that call netdev_boot_setup_check() should select this
661 symbol, everything else no longer needs it.
662
663endif # NETDEVICES