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