Loading...
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 select TAP
139 help
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.
144
145 To compile this driver as a module, choose M here: the module
146 will be called macvtap.
147
148
149config IPVLAN
150 tristate "IP-VLAN support"
151 depends on INET
152 depends on IPV6 || !IPV6
153 depends on NETFILTER
154 select NET_L3_MASTER_DEV
155 ---help---
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.
160
161 Ipvlan devices can be added using the "ip" command from the
162 iproute2 package starting with the iproute2-3.19 release:
163
164 "ip link add link <main-dev> [ NAME ] type ipvlan"
165
166 To compile this driver as a module, choose M here: the module
167 will be called ipvlan.
168
169config IPVTAP
170 tristate "IP-VLAN based tap driver"
171 depends on IPVLAN
172 depends on INET
173 select TAP
174 ---help---
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.
179
180 To compile this driver as a module, choose M here: the module
181 will be called ipvtap.
182
183config VXLAN
184 tristate "Virtual eXtensible Local Area Network (VXLAN)"
185 depends on INET
186 select NET_UDP_TUNNEL
187 select GRO_CELLS
188 ---help---
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
194
195 To compile this driver as a module, choose M here: the module
196 will be called vxlan.
197
198config GENEVE
199 tristate "Generic Network Virtualization Encapsulation"
200 depends on INET && NET_UDP_TUNNEL
201 select NET_IP_TUNNEL
202 select GRO_CELLS
203 ---help---
204 This allows one to create geneve virtual interfaces that provide
205 Layer 2 Networks over Layer 3 Networks. GENEVE is often used
206 to tunnel virtual network infrastructure in virtualized environments.
207 For more information see:
208 http://tools.ietf.org/html/draft-gross-geneve-02
209
210 To compile this driver as a module, choose M here: the module
211 will be called geneve.
212
213config GTP
214 tristate "GPRS Tunneling Protocol datapath (GTP-U)"
215 depends on INET && NET_UDP_TUNNEL
216 select NET_IP_TUNNEL
217 ---help---
218 This allows one to create gtp virtual interfaces that provide
219 the GPRS Tunneling Protocol datapath (GTP-U). This tunneling protocol
220 is used to prevent subscribers from accessing mobile carrier core
221 network infrastructure. This driver requires a userspace software that
222 implements the signaling protocol (GTP-C) to update its PDP context
223 base, such as OpenGGSN <http://git.osmocom.org/openggsn/). This
224 tunneling protocol is implemented according to the GSM TS 09.60 and
225 3GPP TS 29.060 standards.
226
227 To compile this drivers as a module, choose M here: the module
228 wil be called gtp.
229
230config MACSEC
231 tristate "IEEE 802.1AE MAC-level encryption (MACsec)"
232 select CRYPTO
233 select CRYPTO_AES
234 select CRYPTO_GCM
235 select GRO_CELLS
236 ---help---
237 MACsec is an encryption standard for Ethernet.
238
239config NETCONSOLE
240 tristate "Network console logging support"
241 ---help---
242 If you want to log kernel messages over the network, enable this.
243 See <file:Documentation/networking/netconsole.txt> for details.
244
245config NETCONSOLE_DYNAMIC
246 bool "Dynamic reconfiguration of logging targets"
247 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
248 !(NETCONSOLE=y && CONFIGFS_FS=m)
249 help
250 This option enables the ability to dynamically reconfigure target
251 parameters (interface, IP addresses, port numbers, MAC addresses)
252 at runtime through a userspace interface exported using configfs.
253 See <file:Documentation/networking/netconsole.txt> for details.
254
255config NETPOLL
256 def_bool NETCONSOLE
257 select SRCU
258
259config NET_POLL_CONTROLLER
260 def_bool NETPOLL
261
262config NTB_NETDEV
263 tristate "Virtual Ethernet over NTB Transport"
264 depends on NTB_TRANSPORT
265
266config RIONET
267 tristate "RapidIO Ethernet over messaging driver support"
268 depends on RAPIDIO
269
270config RIONET_TX_SIZE
271 int "Number of outbound queue entries"
272 depends on RIONET
273 default "128"
274
275config RIONET_RX_SIZE
276 int "Number of inbound queue entries"
277 depends on RIONET
278 default "128"
279
280config TUN
281 tristate "Universal TUN/TAP device driver support"
282 depends on INET
283 select CRC32
284 ---help---
285 TUN/TAP provides packet reception and transmission for user space
286 programs. It can be viewed as a simple Point-to-Point or Ethernet
287 device, which instead of receiving packets from a physical media,
288 receives them from user space program and instead of sending packets
289 via physical media writes them to the user space program.
290
291 When a program opens /dev/net/tun, driver creates and registers
292 corresponding net device tunX or tapX. After a program closed above
293 devices, driver will automatically delete tunXX or tapXX device and
294 all routes corresponding to it.
295
296 Please read <file:Documentation/networking/tuntap.txt> for more
297 information.
298
299 To compile this driver as a module, choose M here: the module
300 will be called tun.
301
302 If you don't know what to use this for, you don't need it.
303
304config TAP
305 tristate
306 ---help---
307 This option is selected by any driver implementing tap user space
308 interface for a virtual interface to re-use core tap functionality.
309
310config TUN_VNET_CROSS_LE
311 bool "Support for cross-endian vnet headers on little-endian kernels"
312 default n
313 ---help---
314 This option allows TUN/TAP and MACVTAP device drivers in a
315 little-endian kernel to parse vnet headers that come from a
316 big-endian legacy virtio device.
317
318 Userspace programs can control the feature using the TUNSETVNETBE
319 and TUNGETVNETBE ioctls.
320
321 Unless you have a little-endian system hosting a big-endian virtual
322 machine with a legacy virtio NIC, you should say N.
323
324config VETH
325 tristate "Virtual ethernet pair device"
326 ---help---
327 This device is a local ethernet tunnel. Devices are created in pairs.
328 When one end receives the packet it appears on its pair and vice
329 versa.
330
331config VIRTIO_NET
332 tristate "Virtio network driver"
333 depends on VIRTIO
334 ---help---
335 This is the virtual network driver for virtio. It can be used with
336 QEMU based VMMs (like KVM or Xen). Say Y or M.
337
338config NLMON
339 tristate "Virtual netlink monitoring device"
340 ---help---
341 This option enables a monitoring net device for netlink skbs. The
342 purpose of this is to analyze netlink messages with packet sockets.
343 Thus applications like tcpdump will be able to see local netlink
344 messages if they tap into the netlink device, record pcaps for further
345 diagnostics, etc. This is mostly intended for developers or support
346 to debug netlink issues. If unsure, say N.
347
348config NET_VRF
349 tristate "Virtual Routing and Forwarding (Lite)"
350 depends on IP_MULTIPLE_TABLES
351 depends on NET_L3_MASTER_DEV
352 depends on IPV6 || IPV6=n
353 depends on IPV6_MULTIPLE_TABLES || IPV6=n
354 ---help---
355 This option enables the support for mapping interfaces into VRF's. The
356 support enables VRF devices.
357
358config VSOCKMON
359 tristate "Virtual vsock monitoring device"
360 depends on VHOST_VSOCK
361 ---help---
362 This option enables a monitoring net device for vsock sockets. It is
363 mostly intended for developers or support to debug vsock issues. If
364 unsure, say N.
365
366endif # NET_CORE
367
368config SUNGEM_PHY
369 tristate
370
371source "drivers/net/arcnet/Kconfig"
372
373source "drivers/atm/Kconfig"
374
375source "drivers/net/caif/Kconfig"
376
377source "drivers/net/dsa/Kconfig"
378
379source "drivers/net/ethernet/Kconfig"
380
381source "drivers/net/fddi/Kconfig"
382
383source "drivers/net/hippi/Kconfig"
384
385config NET_SB1000
386 tristate "General Instruments Surfboard 1000"
387 depends on PNP
388 ---help---
389 This is a driver for the General Instrument (also known as
390 NextLevel) SURFboard 1000 internal
391 cable modem. This is an ISA card which is used by a number of cable
392 TV companies to provide cable modem access. It's a one-way
393 downstream-only cable modem, meaning that your upstream net link is
394 provided by your regular phone modem.
395
396 At present this driver only compiles as a module, so say M here if
397 you have this card. The module will be called sb1000. Then read
398 <file:Documentation/networking/README.sb1000> for information on how
399 to use this module, as it needs special ppp scripts for establishing
400 a connection. Further documentation and the necessary scripts can be
401 found at:
402
403 <http://www.jacksonville.net/~fventuri/>
404 <http://home.adelphia.net/~siglercm/sb1000.html>
405 <http://linuxpower.cx/~cable/>
406
407 If you don't have this card, of course say N.
408
409source "drivers/net/phy/Kconfig"
410
411source "drivers/net/plip/Kconfig"
412
413source "drivers/net/ppp/Kconfig"
414
415source "drivers/net/slip/Kconfig"
416
417source "drivers/s390/net/Kconfig"
418
419source "drivers/net/usb/Kconfig"
420
421source "drivers/net/wireless/Kconfig"
422
423source "drivers/net/wimax/Kconfig"
424
425source "drivers/net/wan/Kconfig"
426
427source "drivers/net/ieee802154/Kconfig"
428
429config XEN_NETDEV_FRONTEND
430 tristate "Xen network device frontend driver"
431 depends on XEN
432 select XEN_XENBUS_FRONTEND
433 default y
434 help
435 This driver provides support for Xen paravirtual network
436 devices exported by a Xen network driver domain (often
437 domain 0).
438
439 The corresponding Linux backend driver is enabled by the
440 CONFIG_XEN_NETDEV_BACKEND option.
441
442 If you are compiling a kernel for use as Xen guest, you
443 should say Y here. To compile this driver as a module, chose
444 M here: the module will be called xen-netfront.
445
446config XEN_NETDEV_BACKEND
447 tristate "Xen backend network device"
448 depends on XEN_BACKEND
449 help
450 This driver allows the kernel to act as a Xen network driver
451 domain which exports paravirtual network devices to other
452 Xen domains. These devices can be accessed by any operating
453 system that implements a compatible front end.
454
455 The corresponding Linux frontend driver is enabled by the
456 CONFIG_XEN_NETDEV_FRONTEND configuration option.
457
458 The backend driver presents a standard network device
459 endpoint for each paravirtual network device to the driver
460 domain network stack. These can then be bridged or routed
461 etc in order to provide full network connectivity.
462
463 If you are compiling a kernel to run in a Xen network driver
464 domain (often this is domain 0) you should say Y here. To
465 compile this driver as a module, chose M here: the module
466 will be called xen-netback.
467
468config VMXNET3
469 tristate "VMware VMXNET3 ethernet driver"
470 depends on PCI && INET
471 depends on !(PAGE_SIZE_64KB || ARM64_64K_PAGES || \
472 IA64_PAGE_SIZE_64KB || MICROBLAZE_64K_PAGES || \
473 PARISC_PAGE_SIZE_64KB || PPC_64K_PAGES)
474 help
475 This driver supports VMware's vmxnet3 virtual ethernet NIC.
476 To compile this driver as a module, choose M here: the
477 module will be called vmxnet3.
478
479config FUJITSU_ES
480 tristate "FUJITSU Extended Socket Network Device driver"
481 depends on ACPI
482 help
483 This driver provides support for Extended Socket network device
484 on Extended Partitioning of FUJITSU PRIMEQUEST 2000 E2 series.
485
486config THUNDERBOLT_NET
487 tristate "Networking over Thunderbolt cable"
488 depends on THUNDERBOLT && INET
489 help
490 Select this if you want to create network between two
491 computers over a Thunderbolt cable. The driver supports Apple
492 ThunderboltIP protocol and allows communication with any host
493 supporting the same protocol including Windows and macOS.
494
495 To compile this driver a module, choose M here. The module will be
496 called thunderbolt-net.
497
498source "drivers/net/hyperv/Kconfig"
499
500config NETDEVSIM
501 tristate "Simulated networking device"
502 depends on DEBUG_FS
503 depends on MAY_USE_DEVLINK
504 help
505 This driver is a developer testing tool and software model that can
506 be used to test various control path networking APIs, especially
507 HW-offload related.
508
509 To compile this driver as a module, choose M here: the module
510 will be called netdevsim.
511
512endif # NETDEVICES
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 NETPOLL
336 def_bool NETCONSOLE
337 select SRCU
338
339config NET_POLL_CONTROLLER
340 def_bool NETPOLL
341
342config NTB_NETDEV
343 tristate "Virtual Ethernet over NTB Transport"
344 depends on NTB_TRANSPORT
345
346config RIONET
347 tristate "RapidIO Ethernet over messaging driver support"
348 depends on RAPIDIO
349
350config RIONET_TX_SIZE
351 int "Number of outbound queue entries"
352 depends on RIONET
353 default "128"
354
355config RIONET_RX_SIZE
356 int "Number of inbound queue entries"
357 depends on RIONET
358 default "128"
359
360config TUN
361 tristate "Universal TUN/TAP device driver support"
362 depends on INET
363 select CRC32
364 help
365 TUN/TAP provides packet reception and transmission for user space
366 programs. It can be viewed as a simple Point-to-Point or Ethernet
367 device, which instead of receiving packets from a physical media,
368 receives them from user space program and instead of sending packets
369 via physical media writes them to the user space program.
370
371 When a program opens /dev/net/tun, driver creates and registers
372 corresponding net device tunX or tapX. After a program closed above
373 devices, driver will automatically delete tunXX or tapXX device and
374 all routes corresponding to it.
375
376 Please read <file:Documentation/networking/tuntap.rst> for more
377 information.
378
379 To compile this driver as a module, choose M here: the module
380 will be called tun.
381
382 If you don't know what to use this for, you don't need it.
383
384config TAP
385 tristate
386 help
387 This option is selected by any driver implementing tap user space
388 interface for a virtual interface to re-use core tap functionality.
389
390config TUN_VNET_CROSS_LE
391 bool "Support for cross-endian vnet headers on little-endian kernels"
392 default n
393 help
394 This option allows TUN/TAP and MACVTAP device drivers in a
395 little-endian kernel to parse vnet headers that come from a
396 big-endian legacy virtio device.
397
398 Userspace programs can control the feature using the TUNSETVNETBE
399 and TUNGETVNETBE ioctls.
400
401 Unless you have a little-endian system hosting a big-endian virtual
402 machine with a legacy virtio NIC, you should say N.
403
404config VETH
405 tristate "Virtual ethernet pair device"
406 help
407 This device is a local ethernet tunnel. Devices are created in pairs.
408 When one end receives the packet it appears on its pair and vice
409 versa.
410
411config VIRTIO_NET
412 tristate "Virtio network driver"
413 depends on VIRTIO
414 select NET_FAILOVER
415 help
416 This is the virtual network driver for virtio. It can be used with
417 QEMU based VMMs (like KVM or Xen). Say Y or M.
418
419config NLMON
420 tristate "Virtual netlink monitoring device"
421 help
422 This option enables a monitoring net device for netlink skbs. The
423 purpose of this is to analyze netlink messages with packet sockets.
424 Thus applications like tcpdump will be able to see local netlink
425 messages if they tap into the netlink device, record pcaps for further
426 diagnostics, etc. This is mostly intended for developers or support
427 to debug netlink issues. If unsure, say N.
428
429config NET_VRF
430 tristate "Virtual Routing and Forwarding (Lite)"
431 depends on IP_MULTIPLE_TABLES
432 depends on NET_L3_MASTER_DEV
433 depends on IPV6 || IPV6=n
434 depends on IPV6_MULTIPLE_TABLES || IPV6=n
435 help
436 This option enables the support for mapping interfaces into VRF's. The
437 support enables VRF devices.
438
439config VSOCKMON
440 tristate "Virtual vsock monitoring device"
441 depends on VHOST_VSOCK
442 help
443 This option enables a monitoring net device for vsock sockets. It is
444 mostly intended for developers or support to debug vsock issues. If
445 unsure, say N.
446
447config MHI_NET
448 tristate "MHI network driver"
449 depends on MHI_BUS
450 help
451 This is the network driver for MHI bus. It can be used with
452 QCOM based WWAN modems for IP or QMAP/rmnet protocol (like SDX55).
453 Say Y or M.
454
455endif # NET_CORE
456
457config SUNGEM_PHY
458 tristate
459
460source "drivers/net/arcnet/Kconfig"
461
462source "drivers/atm/Kconfig"
463
464source "drivers/net/caif/Kconfig"
465
466source "drivers/net/dsa/Kconfig"
467
468source "drivers/net/ethernet/Kconfig"
469
470source "drivers/net/fddi/Kconfig"
471
472source "drivers/net/hippi/Kconfig"
473
474source "drivers/net/ipa/Kconfig"
475
476config NET_SB1000
477 tristate "General Instruments Surfboard 1000"
478 depends on PNP
479 help
480 This is a driver for the General Instrument (also known as
481 NextLevel) SURFboard 1000 internal
482 cable modem. This is an ISA card which is used by a number of cable
483 TV companies to provide cable modem access. It's a one-way
484 downstream-only cable modem, meaning that your upstream net link is
485 provided by your regular phone modem.
486
487 At present this driver only compiles as a module, so say M here if
488 you have this card. The module will be called sb1000. Then read
489 <file:Documentation/networking/device_drivers/cable/sb1000.rst> for
490 information on how to use this module, as it needs special ppp
491 scripts for establishing a connection. Further documentation
492 and the necessary scripts can be found at:
493
494 <http://www.jacksonville.net/~fventuri/>
495 <http://home.adelphia.net/~siglercm/sb1000.html>
496 <http://linuxpower.cx/~cable/>
497
498 If you don't have this card, of course say N.
499
500source "drivers/net/phy/Kconfig"
501
502source "drivers/net/pse-pd/Kconfig"
503
504source "drivers/net/can/Kconfig"
505
506source "drivers/net/mctp/Kconfig"
507
508source "drivers/net/mdio/Kconfig"
509
510source "drivers/net/pcs/Kconfig"
511
512source "drivers/net/plip/Kconfig"
513
514source "drivers/net/ppp/Kconfig"
515
516source "drivers/net/slip/Kconfig"
517
518source "drivers/s390/net/Kconfig"
519
520source "drivers/net/usb/Kconfig"
521
522source "drivers/net/wireless/Kconfig"
523
524source "drivers/net/wan/Kconfig"
525
526source "drivers/net/ieee802154/Kconfig"
527
528source "drivers/net/wwan/Kconfig"
529
530config XEN_NETDEV_FRONTEND
531 tristate "Xen network device frontend driver"
532 depends on XEN
533 select XEN_XENBUS_FRONTEND
534 select PAGE_POOL
535 default y
536 help
537 This driver provides support for Xen paravirtual network
538 devices exported by a Xen network driver domain (often
539 domain 0).
540
541 The corresponding Linux backend driver is enabled by the
542 CONFIG_XEN_NETDEV_BACKEND option.
543
544 If you are compiling a kernel for use as Xen guest, you
545 should say Y here. To compile this driver as a module, chose
546 M here: the module will be called xen-netfront.
547
548config XEN_NETDEV_BACKEND
549 tristate "Xen backend network device"
550 depends on XEN_BACKEND
551 help
552 This driver allows the kernel to act as a Xen network driver
553 domain which exports paravirtual network devices to other
554 Xen domains. These devices can be accessed by any operating
555 system that implements a compatible front end.
556
557 The corresponding Linux frontend driver is enabled by the
558 CONFIG_XEN_NETDEV_FRONTEND configuration option.
559
560 The backend driver presents a standard network device
561 endpoint for each paravirtual network device to the driver
562 domain network stack. These can then be bridged or routed
563 etc in order to provide full network connectivity.
564
565 If you are compiling a kernel to run in a Xen network driver
566 domain (often this is domain 0) you should say Y here. To
567 compile this driver as a module, chose M here: the module
568 will be called xen-netback.
569
570config VMXNET3
571 tristate "VMware VMXNET3 ethernet driver"
572 depends on PCI && INET
573 depends on PAGE_SIZE_LESS_THAN_64KB
574 help
575 This driver supports VMware's vmxnet3 virtual ethernet NIC.
576 To compile this driver as a module, choose M here: the
577 module will be called vmxnet3.
578
579config FUJITSU_ES
580 tristate "FUJITSU Extended Socket Network Device driver"
581 depends on ACPI
582 help
583 This driver provides support for Extended Socket network device
584 on Extended Partitioning of FUJITSU PRIMEQUEST 2000 E2 series.
585
586config USB4_NET
587 tristate "Networking over USB4 and Thunderbolt cables"
588 depends on USB4 && INET
589 help
590 Select this if you want to create network between two computers
591 over a USB4 and Thunderbolt cables. The driver supports Apple
592 ThunderboltIP protocol and allows communication with any host
593 supporting the same protocol including Windows and macOS.
594
595 To compile this driver a module, choose M here. The module will be
596 called thunderbolt-net.
597
598source "drivers/net/hyperv/Kconfig"
599
600config NETDEVSIM
601 tristate "Simulated networking device"
602 depends on DEBUG_FS
603 depends on INET
604 depends on IPV6 || IPV6=n
605 depends on PSAMPLE || PSAMPLE=n
606 select NET_DEVLINK
607 help
608 This driver is a developer testing tool and software model that can
609 be used to test various control path networking APIs, especially
610 HW-offload related.
611
612 To compile this driver as a module, choose M here: the module
613 will be called netdevsim.
614
615config NET_FAILOVER
616 tristate "Failover driver"
617 select FAILOVER
618 help
619 This provides an automated failover mechanism via APIs to create
620 and destroy a failover master netdev and manages a primary and
621 standby slave netdevs that get registered via the generic failover
622 infrastructure. This can be used by paravirtual drivers to enable
623 an alternate low latency datapath. It also enables live migration of
624 a VM with direct attached VF by failing over to the paravirtual
625 datapath when the VF is unplugged.
626
627config NETDEV_LEGACY_INIT
628 bool
629 depends on ISA
630 help
631 Drivers that call netdev_boot_setup_check() should select this
632 symbol, everything else no longer needs it.
633
634endif # NETDEVICES