Commit | Line | Data |
---|---|---|
ec8f24b7 | 1 | # SPDX-License-Identifier: GPL-2.0-only |
1da177e4 LT |
2 | # |
3 | # Network device configuration | |
4 | # | |
5 | ||
d1c0a65f | 6 | menuconfig NETDEVICES |
ce2d2aed | 7 | default y if UML |
e0009820 | 8 | depends on NET |
1da177e4 | 9 | bool "Network device support" |
a7f7f624 | 10 | help |
1da177e4 LT |
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 | ||
1618cb0c RD |
25 | # All the following symbols are dependent on NETDEVICES - do not repeat |
26 | # that for each of the symbols. | |
27 | if NETDEVICES | |
cbcd2a4c | 28 | |
a1606c7d BH |
29 | config MII |
30 | tristate | |
31 | ||
88491d81 JK |
32 | config NET_CORE |
33 | default y | |
34 | bool "Network core driver support" | |
a7f7f624 | 35 | help |
88491d81 JK |
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 | ||
39 | if NET_CORE | |
40 | ||
41 | config BONDING | |
42 | tristate "Bonding driver support" | |
43 | depends on INET | |
44 | depends on IPV6 || IPV6=n | |
285715ac | 45 | depends on TLS || TLS_DEVICE=n |
a7f7f624 | 46 | help |
88491d81 JK |
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 | ||
a362032e | 54 | Refer to <file:Documentation/networking/bonding.rst> for more |
88491d81 JK |
55 | information. |
56 | ||
253af423 | 57 | To compile this driver as a module, choose M here: the module |
88491d81 | 58 | will be called bonding. |
253af423 | 59 | |
1da177e4 LT |
60 | config DUMMY |
61 | tristate "Dummy net driver support" | |
a7f7f624 | 62 | help |
1da177e4 LT |
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. | |
9f5db535 IB |
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 | |
1da177e4 LT |
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 | |
9f486619 | 73 | will be called dummy. |
1da177e4 | 74 | |
e7096c13 JD |
75 | config WIREGUARD |
76 | tristate "WireGuard secure network tunnel" | |
77 | depends on NET && INET | |
78 | depends on IPV6 || !IPV6 | |
440fed95 | 79 | depends on !KMSAN # KMSAN doesn't support the crypto configs below |
e7096c13 JD |
80 | select NET_UDP_TUNNEL |
81 | select DST_CACHE | |
82 | select CRYPTO | |
83 | select CRYPTO_LIB_CURVE25519 | |
84 | select CRYPTO_LIB_CHACHA20POLY1305 | |
e7096c13 JD |
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 | |
bce24739 | 89 | select CRYPTO_CHACHA20_NEON if ARM || (ARM64 && KERNEL_MODE_NEON) |
e7096c13 JD |
90 | select CRYPTO_POLY1305_NEON if ARM64 && KERNEL_MODE_NEON |
91 | select CRYPTO_POLY1305_ARM if ARM | |
a64bfe7a | 92 | select CRYPTO_BLAKE2S_ARM if ARM |
e7096c13 JD |
93 | select CRYPTO_CURVE25519_NEON if ARM && KERNEL_MODE_NEON |
94 | select CRYPTO_CHACHA_MIPS if CPU_MIPS32_R2 | |
6c810cf2 | 95 | select CRYPTO_POLY1305_MIPS if MIPS |
0d1f7008 | 96 | select CRYPTO_CHACHA_S390 if S390 |
e7096c13 JD |
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 | ||
107 | config 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 | ||
88491d81 JK |
118 | config EQUALIZER |
119 | tristate "EQL (serial line load balancing) support" | |
a7f7f624 | 120 | help |
88491d81 JK |
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. | |
1da177e4 | 128 | |
88491d81 | 129 | Say Y if you want this and read |
06df6572 | 130 | <file:Documentation/networking/eql.rst>. You may also want to read |
88491d81 JK |
131 | section 6.2 of the NET-3-HOWTO, available from |
132 | <http://www.tldp.org/docs.html#howto>. | |
1da177e4 | 133 | |
88491d81 JK |
134 | To compile this driver as a module, choose M here: the module |
135 | will be called eql. If unsure, say N. | |
136 | ||
137 | config 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". | |
1da177e4 | 149 | |
88491d81 JK |
150 | config IFB |
151 | tristate "Intermediate Functional Block support" | |
046178e7 | 152 | depends on NET_ACT_MIRRED || NFT_FWD_NETDEV |
2c64605b | 153 | select NET_REDIRECT |
a7f7f624 | 154 | help |
88491d81 JK |
155 | This is an intermediate driver that allows sharing of |
156 | resources. | |
1da177e4 | 157 | To compile this driver as a module, choose M here: the module |
88491d81 JK |
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 | |
1da177e4 | 163 | |
3d249d4c JP |
164 | source "drivers/net/team/Kconfig" |
165 | ||
b863ceb7 | 166 | config MACVLAN |
bd085b93 | 167 | tristate "MAC-VLAN support" |
a7f7f624 | 168 | help |
b863ceb7 PM |
169 | This allows one to create virtual interfaces that map packets to |
170 | or from specific MAC addresses to a particular interface. | |
171 | ||
3dbf8d56 PM |
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 | ||
b863ceb7 PM |
177 | To compile this driver as a module, choose M here: the module |
178 | will be called macvlan. | |
179 | ||
20d29d7a | 180 | config MACVTAP |
bd085b93 | 181 | tristate "MAC-VLAN based tap driver" |
20d29d7a | 182 | depends on MACVLAN |
de11b0e8 | 183 | depends on INET |
9a393b5d | 184 | select TAP |
20d29d7a AB |
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 | |
c7966b52 | 189 | macvtap', and then be accessed through the tap user space interface. |
20d29d7a AB |
190 | |
191 | To compile this driver as a module, choose M here: the module | |
192 | will be called macvtap. | |
193 | ||
c675e06a DB |
194 | config IPVLAN_L3S |
195 | depends on NETFILTER | |
a37d45b6 | 196 | depends on IPVLAN |
c675e06a DB |
197 | def_bool y |
198 | select NET_L3_MASTER_DEV | |
2ad7bf36 MB |
199 | |
200 | config IPVLAN | |
5421cf84 KK |
201 | tristate "IP-VLAN support" |
202 | depends on INET | |
203 | depends on IPV6 || !IPV6 | |
a7f7f624 | 204 | help |
5421cf84 KK |
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. | |
2ad7bf36 | 209 | |
5421cf84 KK |
210 | Ipvlan devices can be added using the "ip" command from the |
211 | iproute2 package starting with the iproute2-3.19 release: | |
2ad7bf36 | 212 | |
5421cf84 | 213 | "ip link add link <main-dev> [ NAME ] type ipvlan" |
2ad7bf36 | 214 | |
5421cf84 KK |
215 | To compile this driver as a module, choose M here: the module |
216 | will be called ipvlan. | |
2ad7bf36 | 217 | |
235a9d89 SG |
218 | config IPVTAP |
219 | tristate "IP-VLAN based tap driver" | |
220 | depends on IPVLAN | |
221 | depends on INET | |
222 | select TAP | |
a7f7f624 | 223 | help |
235a9d89 SG |
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. | |
2ad7bf36 | 231 | |
d342894c | 232 | config VXLAN |
5421cf84 KK |
233 | tristate "Virtual eXtensible Local Area Network (VXLAN)" |
234 | depends on INET | |
235 | select NET_UDP_TUNNEL | |
236 | select GRO_CELLS | |
a7f7f624 | 237 | help |
d342894c | 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 | ||
2d07dc79 | 247 | config GENEVE |
5421cf84 KK |
248 | tristate "Generic Network Virtualization Encapsulation" |
249 | depends on INET | |
250 | depends on IPV6 || !IPV6 | |
251 | select NET_UDP_TUNNEL | |
252 | select GRO_CELLS | |
a7f7f624 | 253 | help |
2d07dc79 JL |
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 | ||
571912c6 | 263 | config BAREUDP |
d6dd33ff MB |
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. | |
571912c6 | 275 | |
459aa660 PN |
276 | config GTP |
277 | tristate "GPRS Tunneling Protocol datapath (GTP-U)" | |
c22da366 MC |
278 | depends on INET |
279 | select NET_UDP_TUNNEL | |
a7f7f624 | 280 | help |
459aa660 PN |
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 | |
00649542 | 291 | will be called gtp. |
459aa660 | 292 | |
b9022b53 TY |
293 | config AMT |
294 | tristate "Automatic Multicast Tunneling (AMT)" | |
295 | depends on INET && IP_MULTICAST | |
9758aba8 | 296 | depends on IPV6 || !IPV6 |
b9022b53 TY |
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 | ||
c09440f7 SD |
310 | config MACSEC |
311 | tristate "IEEE 802.1AE MAC-level encryption (MACsec)" | |
ab2ed017 | 312 | select CRYPTO |
c09440f7 SD |
313 | select CRYPTO_AES |
314 | select CRYPTO_GCM | |
97e219b7 | 315 | select GRO_CELLS |
a7f7f624 | 316 | help |
c09440f7 SD |
317 | MACsec is an encryption standard for Ethernet. |
318 | ||
88491d81 JK |
319 | config NETCONSOLE |
320 | tristate "Network console logging support" | |
a7f7f624 | 321 | help |
5421cf84 | 322 | If you want to log kernel messages over the network, enable this. |
d9d6ef25 | 323 | See <file:Documentation/networking/netconsole.rst> for details. |
1da177e4 | 324 | |
88491d81 JK |
325 | config 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. | |
d9d6ef25 | 333 | See <file:Documentation/networking/netconsole.rst> for details. |
1da177e4 | 334 | |
fad361a2 BL |
335 | config 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 | ||
345 | config 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 | ||
88491d81 JK |
357 | config NETPOLL |
358 | def_bool NETCONSOLE | |
359 | ||
88491d81 JK |
360 | config NET_POLL_CONTROLLER |
361 | def_bool NETPOLL | |
362 | ||
548c237c | 363 | config NTB_NETDEV |
ec110bc7 AH |
364 | tristate "Virtual Ethernet over NTB Transport" |
365 | depends on NTB_TRANSPORT | |
548c237c | 366 | |
88491d81 JK |
367 | config RIONET |
368 | tristate "RapidIO Ethernet over messaging driver support" | |
369 | depends on RAPIDIO | |
370 | ||
371 | config RIONET_TX_SIZE | |
372 | int "Number of outbound queue entries" | |
373 | depends on RIONET | |
374 | default "128" | |
375 | ||
376 | config RIONET_RX_SIZE | |
377 | int "Number of inbound queue entries" | |
378 | depends on RIONET | |
379 | default "128" | |
1da177e4 LT |
380 | |
381 | config TUN | |
382 | tristate "Universal TUN/TAP device driver support" | |
de11b0e8 | 383 | depends on INET |
1da177e4 | 384 | select CRC32 |
a7f7f624 | 385 | help |
1da177e4 LT |
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 | ||
973d55e5 | 397 | Please read <file:Documentation/networking/tuntap.rst> for more |
1da177e4 LT |
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 | ||
9a393b5d SG |
405 | config TAP |
406 | tristate | |
a7f7f624 | 407 | help |
9a393b5d SG |
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 | ||
8b8e658b GK |
411 | config TUN_VNET_CROSS_LE |
412 | bool "Support for cross-endian vnet headers on little-endian kernels" | |
413 | default n | |
a7f7f624 | 414 | help |
8b8e658b GK |
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 | ||
e314dbdc | 425 | config VETH |
6a9a0250 | 426 | tristate "Virtual ethernet pair device" |
0ebab78c | 427 | select PAGE_POOL |
a7f7f624 | 428 | help |
6a9a0250 RR |
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. | |
e314dbdc | 432 | |
88491d81 | 433 | config VIRTIO_NET |
bd085b93 KC |
434 | tristate "Virtio network driver" |
435 | depends on VIRTIO | |
ba5e4426 | 436 | select NET_FAILOVER |
62087995 | 437 | select DIMLIB |
a7f7f624 | 438 | help |
88491d81 | 439 | This is the virtual network driver for virtio. It can be used with |
ecda85e7 | 440 | QEMU based VMMs (like KVM or Xen). Say Y or M. |
88491d81 | 441 | |
e4fc408e DB |
442 | config NLMON |
443 | tristate "Virtual netlink monitoring device" | |
a7f7f624 | 444 | help |
e4fc408e DB |
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 | ||
35dfaad7 DB |
452 | config 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 | ||
193125db DA |
461 | config NET_VRF |
462 | tristate "Virtual Routing and Forwarding (Lite)" | |
35402e31 | 463 | depends on IP_MULTIPLE_TABLES |
ee15ee5d | 464 | depends on NET_L3_MASTER_DEV |
35402e31 DA |
465 | depends on IPV6 || IPV6=n |
466 | depends on IPV6_MULTIPLE_TABLES || IPV6=n | |
a7f7f624 | 467 | help |
193125db DA |
468 | This option enables the support for mapping interfaces into VRF's. The |
469 | support enables VRF devices. | |
470 | ||
0b2e6644 | 471 | config VSOCKMON |
5421cf84 KK |
472 | tristate "Virtual vsock monitoring device" |
473 | depends on VHOST_VSOCK | |
a7f7f624 | 474 | help |
5421cf84 KK |
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. | |
0b2e6644 | 478 | |
3ffec6a1 LP |
479 | config 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 | |
7ffa7542 LP |
484 | QCOM based WWAN modems for IP or QMAP/rmnet protocol (like SDX55). |
485 | Say Y or M. | |
3ffec6a1 | 486 | |
88491d81 JK |
487 | endif # NET_CORE |
488 | ||
489 | config SUNGEM_PHY | |
490 | tristate | |
491 | ||
492 | source "drivers/net/arcnet/Kconfig" | |
493 | ||
494 | source "drivers/atm/Kconfig" | |
495 | ||
496 | source "drivers/net/caif/Kconfig" | |
497 | ||
3b158859 BH |
498 | source "drivers/net/dsa/Kconfig" |
499 | ||
88491d81 JK |
500 | source "drivers/net/ethernet/Kconfig" |
501 | ||
502 | source "drivers/net/fddi/Kconfig" | |
503 | ||
fecc7351 PB |
504 | source "drivers/net/hippi/Kconfig" |
505 | ||
08120d23 AE |
506 | source "drivers/net/ipa/Kconfig" |
507 | ||
1da177e4 LT |
508 | config NET_SB1000 |
509 | tristate "General Instruments Surfboard 1000" | |
cbcd2a4c | 510 | depends on PNP |
a7f7f624 | 511 | help |
1da177e4 LT |
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 | |
132db935 | 521 | <file:Documentation/networking/device_drivers/cable/sb1000.rst> for |
b255e500 JK |
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: | |
1da177e4 LT |
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 | ||
00db8189 AF |
532 | source "drivers/net/phy/Kconfig" |
533 | ||
3114b075 OR |
534 | source "drivers/net/pse-pd/Kconfig" |
535 | ||
d7786af5 VM |
536 | source "drivers/net/can/Kconfig" |
537 | ||
4b2e6930 JK |
538 | source "drivers/net/mctp/Kconfig" |
539 | ||
a9770eac AL |
540 | source "drivers/net/mdio/Kconfig" |
541 | ||
2fa4e4b7 AL |
542 | source "drivers/net/pcs/Kconfig" |
543 | ||
18e635f4 JK |
544 | source "drivers/net/plip/Kconfig" |
545 | ||
88491d81 JK |
546 | source "drivers/net/ppp/Kconfig" |
547 | ||
b5451d78 JK |
548 | source "drivers/net/slip/Kconfig" |
549 | ||
88491d81 JK |
550 | source "drivers/s390/net/Kconfig" |
551 | ||
88491d81 JK |
552 | source "drivers/net/usb/Kconfig" |
553 | ||
1da177e4 LT |
554 | source "drivers/net/wireless/Kconfig" |
555 | ||
1da177e4 LT |
556 | source "drivers/net/wan/Kconfig" |
557 | ||
0739d643 | 558 | source "drivers/net/ieee802154/Kconfig" |
559 | ||
9a44c1cc LP |
560 | source "drivers/net/wwan/Kconfig" |
561 | ||
0d160211 JF |
562 | config XEN_NETDEV_FRONTEND |
563 | tristate "Xen network device frontend driver" | |
564 | depends on XEN | |
7003087c | 565 | select XEN_XENBUS_FRONTEND |
6c5aa6fc | 566 | select PAGE_POOL |
0d160211 JF |
567 | default y |
568 | help | |
f942dc25 IC |
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 | ||
580 | config 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. | |
0d160211 | 601 | |
d1a890fa | 602 | config VMXNET3 |
e85eb117 PDM |
603 | tristate "VMware VMXNET3 ethernet driver" |
604 | depends on PCI && INET | |
00169a92 | 605 | depends on PAGE_SIZE_LESS_THAN_64KB |
54f00cce | 606 | select PAGE_POOL |
e85eb117 PDM |
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. | |
d1a890fa | 611 | |
658d439b TI |
612 | config 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 | |
02bc5eb9 | 617 | on Extended Partitioning of FUJITSU PRIMEQUEST 2000 E2 series. |
658d439b | 618 | |
0d0950a9 | 619 | source "drivers/net/thunderbolt/Kconfig" |
95fa0405 HZ |
620 | source "drivers/net/hyperv/Kconfig" |
621 | ||
83c9e13a JK |
622 | config NETDEVSIM |
623 | tristate "Simulated networking device" | |
624 | depends on DEBUG_FS | |
1f399fc7 | 625 | depends on INET |
48bb9eb4 | 626 | depends on IPV6 || IPV6=n |
a8700c3d | 627 | depends on PSAMPLE || PSAMPLE=n |
b63e78fc | 628 | depends on PTP_1588_CLOCK_MOCK || PTP_1588_CLOCK_MOCK=n |
f6b19b35 | 629 | select NET_DEVLINK |
83c9e13a JK |
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 | ||
cfc80d9a SS |
638 | config 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 | |
9437b629 | 646 | an alternate low latency datapath. It also enables live migration of |
cfc80d9a SS |
647 | a VM with direct attached VF by failing over to the paravirtual |
648 | datapath when the VF is unplugged. | |
649 | ||
4228c394 AB |
650 | config 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 | ||
d1c0a65f | 657 | endif # NETDEVICES |