| 1 | # SPDX-License-Identifier: GPL-2.0-only |
| 2 | # |
| 3 | # Network device configuration |
| 4 | # |
| 5 | |
| 6 | menuconfig 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. |
| 27 | if NETDEVICES |
| 28 | |
| 29 | config MII |
| 30 | tristate |
| 31 | |
| 32 | config 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 | |
| 39 | if NET_CORE |
| 40 | |
| 41 | config BONDING |
| 42 | tristate "Bonding driver support" |
| 43 | depends on INET |
| 44 | depends on TLS || TLS_DEVICE=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.rst> for more |
| 54 | information. |
| 55 | |
| 56 | To compile this driver as a module, choose M here: the module |
| 57 | will be called bonding. |
| 58 | |
| 59 | config 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 | |
| 74 | config WIREGUARD |
| 75 | tristate "WireGuard secure network tunnel" |
| 76 | depends on NET && INET |
| 77 | select NET_UDP_TUNNEL |
| 78 | select DST_CACHE |
| 79 | select CRYPTO_LIB_CURVE25519 |
| 80 | select CRYPTO_LIB_CHACHA20POLY1305 |
| 81 | select CRYPTO_LIB_UTILS |
| 82 | help |
| 83 | WireGuard is a secure, fast, and easy to use replacement for IPSec |
| 84 | that uses modern cryptography and clever networking tricks. It's |
| 85 | designed to be fairly general purpose and abstract enough to fit most |
| 86 | use cases, while at the same time remaining extremely simple to |
| 87 | configure. See www.wireguard.com for more info. |
| 88 | |
| 89 | It's safe to say Y or M here, as the driver is very lightweight and |
| 90 | is only in use when an administrator chooses to add an interface. |
| 91 | |
| 92 | config WIREGUARD_DEBUG |
| 93 | bool "Debugging checks and verbose messages" |
| 94 | depends on WIREGUARD |
| 95 | help |
| 96 | This will write log messages for handshake and other events |
| 97 | that occur for a WireGuard interface. It will also perform some |
| 98 | extra validation checks and unit tests at various points. This is |
| 99 | only useful for debugging. |
| 100 | |
| 101 | Say N here unless you know what you're doing. |
| 102 | |
| 103 | config OVPN |
| 104 | tristate "OpenVPN data channel offload" |
| 105 | depends on NET && INET |
| 106 | select DST_CACHE |
| 107 | select NET_UDP_TUNNEL |
| 108 | select CRYPTO |
| 109 | select CRYPTO_AES |
| 110 | select CRYPTO_GCM |
| 111 | select CRYPTO_CHACHA20POLY1305 |
| 112 | select STREAM_PARSER |
| 113 | help |
| 114 | This module enhances the performance of the OpenVPN userspace software |
| 115 | by offloading the data channel processing to kernelspace. |
| 116 | |
| 117 | config 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.rst>. 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 | |
| 136 | config 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 | |
| 149 | config IFB |
| 150 | tristate "Intermediate Functional Block support" |
| 151 | depends on NET_ACT_MIRRED || NFT_FWD_NETDEV |
| 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 | |
| 163 | source "drivers/net/team/Kconfig" |
| 164 | |
| 165 | config 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 | |
| 179 | config 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 | |
| 193 | config IPVLAN_L3S |
| 194 | depends on NETFILTER |
| 195 | depends on IPVLAN |
| 196 | def_bool y |
| 197 | select NET_L3_MASTER_DEV |
| 198 | |
| 199 | config IPVLAN |
| 200 | tristate "IP-VLAN support" |
| 201 | depends on INET |
| 202 | help |
| 203 | This allows one to create virtual devices off of a main interface |
| 204 | and packets will be delivered based on the dest L3 (IPv6/IPv4 addr) |
| 205 | on packets. All interfaces (including the main interface) share L2 |
| 206 | making it transparent to the connected L2 switch. |
| 207 | |
| 208 | Ipvlan devices can be added using the "ip" command from the |
| 209 | iproute2 package starting with the iproute2-3.19 release: |
| 210 | |
| 211 | "ip link add link <main-dev> [ NAME ] type ipvlan" |
| 212 | |
| 213 | To compile this driver as a module, choose M here: the module |
| 214 | will be called ipvlan. |
| 215 | |
| 216 | config IPVTAP |
| 217 | tristate "IP-VLAN based tap driver" |
| 218 | depends on IPVLAN |
| 219 | depends on INET |
| 220 | select TAP |
| 221 | help |
| 222 | This adds a specialized tap character device driver that is based |
| 223 | on the IP-VLAN network interface, called ipvtap. An ipvtap device |
| 224 | can be added in the same way as a ipvlan device, using 'type |
| 225 | ipvtap', and then be accessed through the tap user space interface. |
| 226 | |
| 227 | To compile this driver as a module, choose M here: the module |
| 228 | will be called ipvtap. |
| 229 | |
| 230 | config VXLAN |
| 231 | tristate "Virtual eXtensible Local Area Network (VXLAN)" |
| 232 | depends on INET |
| 233 | select NET_UDP_TUNNEL |
| 234 | select GRO_CELLS |
| 235 | help |
| 236 | This allows one to create vxlan virtual interfaces that provide |
| 237 | Layer 2 Networks over Layer 3 Networks. VXLAN is often used |
| 238 | to tunnel virtual network infrastructure in virtualized environments. |
| 239 | For more information see: |
| 240 | http://tools.ietf.org/html/draft-mahalingam-dutt-dcops-vxlan-02 |
| 241 | |
| 242 | To compile this driver as a module, choose M here: the module |
| 243 | will be called vxlan. |
| 244 | |
| 245 | config GENEVE |
| 246 | tristate "Generic Network Virtualization Encapsulation" |
| 247 | depends on INET |
| 248 | select NET_UDP_TUNNEL |
| 249 | select GRO_CELLS |
| 250 | help |
| 251 | This allows one to create geneve virtual interfaces that provide |
| 252 | Layer 2 Networks over Layer 3 Networks. GENEVE is often used |
| 253 | to tunnel virtual network infrastructure in virtualized environments. |
| 254 | For more information see: |
| 255 | http://tools.ietf.org/html/draft-gross-geneve-02 |
| 256 | |
| 257 | To compile this driver as a module, choose M here: the module |
| 258 | will be called geneve. |
| 259 | |
| 260 | config BAREUDP |
| 261 | tristate "Bare UDP Encapsulation" |
| 262 | depends on INET |
| 263 | select NET_UDP_TUNNEL |
| 264 | select GRO_CELLS |
| 265 | help |
| 266 | This adds a bare UDP tunnel module for tunnelling different |
| 267 | kinds of traffic like MPLS, IP, etc. inside a UDP tunnel. |
| 268 | |
| 269 | To compile this driver as a module, choose M here: the module |
| 270 | will be called bareudp. |
| 271 | |
| 272 | config GTP |
| 273 | tristate "GPRS Tunneling Protocol datapath (GTP-U)" |
| 274 | depends on INET |
| 275 | select NET_UDP_TUNNEL |
| 276 | help |
| 277 | This allows one to create gtp virtual interfaces that provide |
| 278 | the GPRS Tunneling Protocol datapath (GTP-U). This tunneling protocol |
| 279 | is used to prevent subscribers from accessing mobile carrier core |
| 280 | network infrastructure. This driver requires a userspace software that |
| 281 | implements the signaling protocol (GTP-C) to update its PDP context |
| 282 | base, such as OpenGGSN <http://git.osmocom.org/openggsn/). This |
| 283 | tunneling protocol is implemented according to the GSM TS 09.60 and |
| 284 | 3GPP TS 29.060 standards. |
| 285 | |
| 286 | To compile this drivers as a module, choose M here: the module |
| 287 | will be called gtp. |
| 288 | |
| 289 | config PFCP |
| 290 | tristate "Packet Forwarding Control Protocol (PFCP)" |
| 291 | depends on INET |
| 292 | select NET_UDP_TUNNEL |
| 293 | help |
| 294 | This allows one to create PFCP virtual interfaces that allows to |
| 295 | set up software and hardware offload of PFCP packets. |
| 296 | Note that this module does not support PFCP protocol in the kernel space. |
| 297 | There is no support for parsing any PFCP messages. |
| 298 | |
| 299 | To compile this drivers as a module, choose M here: the module |
| 300 | will be called pfcp. |
| 301 | |
| 302 | config AMT |
| 303 | tristate "Automatic Multicast Tunneling (AMT)" |
| 304 | depends on INET && IP_MULTICAST |
| 305 | select NET_UDP_TUNNEL |
| 306 | help |
| 307 | This allows one to create AMT(Automatic Multicast Tunneling) |
| 308 | virtual interfaces that provide multicast tunneling. |
| 309 | There are two roles, Gateway, and Relay. |
| 310 | Gateway Encapsulates IGMP/MLD traffic from listeners to the Relay. |
| 311 | Gateway Decapsulates multicast traffic from the Relay to Listeners. |
| 312 | Relay Encapsulates multicast traffic from Sources to Gateway. |
| 313 | Relay Decapsulates IGMP/MLD traffic from Gateway. |
| 314 | |
| 315 | To compile this drivers as a module, choose M here: the module |
| 316 | will be called amt. |
| 317 | |
| 318 | config MACSEC |
| 319 | tristate "IEEE 802.1AE MAC-level encryption (MACsec)" |
| 320 | select CRYPTO |
| 321 | select CRYPTO_AES |
| 322 | select CRYPTO_GCM |
| 323 | select GRO_CELLS |
| 324 | help |
| 325 | MACsec is an encryption standard for Ethernet. |
| 326 | |
| 327 | config NETCONSOLE |
| 328 | tristate "Network console logging support" |
| 329 | depends on PRINTK |
| 330 | help |
| 331 | If you want to log kernel messages over the network, enable this. |
| 332 | See <file:Documentation/networking/netconsole.rst> for details. |
| 333 | |
| 334 | config NETCONSOLE_DYNAMIC |
| 335 | bool "Dynamic reconfiguration of logging targets" |
| 336 | depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \ |
| 337 | !(NETCONSOLE=y && CONFIGFS_FS=m) |
| 338 | select PRINTK_EXECUTION_CTX |
| 339 | help |
| 340 | This option enables the ability to dynamically reconfigure target |
| 341 | parameters (interface, IP addresses, port numbers, MAC addresses) |
| 342 | at runtime through a userspace interface exported using configfs. |
| 343 | See <file:Documentation/networking/netconsole.rst> for details. |
| 344 | |
| 345 | config NETCONSOLE_EXTENDED_LOG |
| 346 | bool "Set kernel extended message by default" |
| 347 | depends on NETCONSOLE |
| 348 | default n |
| 349 | help |
| 350 | Set extended log support for netconsole message. If this option is |
| 351 | set, log messages are transmitted with extended metadata header in a |
| 352 | format similar to /dev/kmsg. See |
| 353 | <file:Documentation/networking/netconsole.rst> for details. |
| 354 | |
| 355 | config NETCONSOLE_PREPEND_RELEASE |
| 356 | bool "Prepend kernel release version in the message by default" |
| 357 | depends on NETCONSOLE_EXTENDED_LOG |
| 358 | default n |
| 359 | help |
| 360 | Set kernel release to be prepended to each netconsole message by |
| 361 | default. If this option is set, the kernel release is prepended into |
| 362 | the first field of every netconsole message, so, the netconsole |
| 363 | server/peer can easily identify what kernel release is logging each |
| 364 | message. See <file:Documentation/networking/netconsole.rst> for |
| 365 | details. |
| 366 | |
| 367 | config NETPOLL |
| 368 | def_bool NETCONSOLE |
| 369 | |
| 370 | config NET_POLL_CONTROLLER |
| 371 | def_bool NETPOLL |
| 372 | |
| 373 | config NTB_NETDEV |
| 374 | tristate "Virtual Ethernet over NTB Transport" |
| 375 | depends on NTB_TRANSPORT |
| 376 | |
| 377 | config RIONET |
| 378 | tristate "RapidIO Ethernet over messaging driver support" |
| 379 | depends on RAPIDIO |
| 380 | |
| 381 | config RIONET_TX_SIZE |
| 382 | int "Number of outbound queue entries" |
| 383 | depends on RIONET |
| 384 | default "128" |
| 385 | |
| 386 | config RIONET_RX_SIZE |
| 387 | int "Number of inbound queue entries" |
| 388 | depends on RIONET |
| 389 | default "128" |
| 390 | |
| 391 | config TUN |
| 392 | tristate "Universal TUN/TAP device driver support" |
| 393 | depends on INET |
| 394 | select CRC32 |
| 395 | help |
| 396 | TUN/TAP provides packet reception and transmission for user space |
| 397 | programs. It can be viewed as a simple Point-to-Point or Ethernet |
| 398 | device, which instead of receiving packets from a physical media, |
| 399 | receives them from user space program and instead of sending packets |
| 400 | via physical media writes them to the user space program. |
| 401 | |
| 402 | When a program opens /dev/net/tun, driver creates and registers |
| 403 | corresponding net device tunX or tapX. After a program closed above |
| 404 | devices, driver will automatically delete tunXX or tapXX device and |
| 405 | all routes corresponding to it. |
| 406 | |
| 407 | Please read <file:Documentation/networking/tuntap.rst> for more |
| 408 | information. |
| 409 | |
| 410 | To compile this driver as a module, choose M here: the module |
| 411 | will be called tun. |
| 412 | |
| 413 | If you don't know what to use this for, you don't need it. |
| 414 | |
| 415 | config TAP |
| 416 | tristate |
| 417 | help |
| 418 | This option is selected by any driver implementing tap user space |
| 419 | interface for a virtual interface to re-use core tap functionality. |
| 420 | |
| 421 | config TUN_VNET_CROSS_LE |
| 422 | bool "Support for cross-endian vnet headers on little-endian kernels" |
| 423 | default n |
| 424 | help |
| 425 | This option allows TUN/TAP and MACVTAP device drivers in a |
| 426 | little-endian kernel to parse vnet headers that come from a |
| 427 | big-endian legacy virtio device. |
| 428 | |
| 429 | Userspace programs can control the feature using the TUNSETVNETBE |
| 430 | and TUNGETVNETBE ioctls. |
| 431 | |
| 432 | Unless you have a little-endian system hosting a big-endian virtual |
| 433 | machine with a legacy virtio NIC, you should say N. |
| 434 | |
| 435 | config VETH |
| 436 | tristate "Virtual ethernet pair device" |
| 437 | select PAGE_POOL |
| 438 | help |
| 439 | This device is a local ethernet tunnel. Devices are created in pairs. |
| 440 | When one end receives the packet it appears on its pair and vice |
| 441 | versa. |
| 442 | |
| 443 | config VIRTIO_NET |
| 444 | tristate "Virtio network driver" |
| 445 | depends on VIRTIO |
| 446 | select NET_FAILOVER |
| 447 | select DIMLIB |
| 448 | select PAGE_POOL |
| 449 | help |
| 450 | This is the virtual network driver for virtio. It can be used with |
| 451 | QEMU based VMMs (like KVM or Xen). Say Y or M. |
| 452 | |
| 453 | config NLMON |
| 454 | tristate "Virtual netlink monitoring device" |
| 455 | help |
| 456 | This option enables a monitoring net device for netlink skbs. The |
| 457 | purpose of this is to analyze netlink messages with packet sockets. |
| 458 | Thus applications like tcpdump will be able to see local netlink |
| 459 | messages if they tap into the netlink device, record pcaps for further |
| 460 | diagnostics, etc. This is mostly intended for developers or support |
| 461 | to debug netlink issues. If unsure, say N. |
| 462 | |
| 463 | config NETKIT |
| 464 | bool "BPF-programmable network device" |
| 465 | depends on BPF_SYSCALL |
| 466 | help |
| 467 | The netkit device is a virtual networking device where BPF programs |
| 468 | can be attached to the device(s) transmission routine in order to |
| 469 | implement the driver's internal logic. The device can be configured |
| 470 | to operate in L3 or L2 mode. If unsure, say N. |
| 471 | |
| 472 | config NET_VRF |
| 473 | tristate "Virtual Routing and Forwarding (Lite)" |
| 474 | depends on IP_MULTIPLE_TABLES |
| 475 | depends on NET_L3_MASTER_DEV |
| 476 | depends on IPV6_MULTIPLE_TABLES || IPV6=n |
| 477 | help |
| 478 | This option enables the support for mapping interfaces into VRF's. The |
| 479 | support enables VRF devices. |
| 480 | |
| 481 | config VSOCKMON |
| 482 | tristate "Virtual vsock monitoring device" |
| 483 | depends on VHOST_VSOCK |
| 484 | help |
| 485 | This option enables a monitoring net device for vsock sockets. It is |
| 486 | mostly intended for developers or support to debug vsock issues. If |
| 487 | unsure, say N. |
| 488 | |
| 489 | config MHI_NET |
| 490 | tristate "MHI network driver" |
| 491 | depends on MHI_BUS |
| 492 | help |
| 493 | This is the network driver for MHI bus. It can be used with |
| 494 | QCOM based WWAN modems for IP or QMAP/rmnet protocol (like SDX55). |
| 495 | Say Y or M. |
| 496 | |
| 497 | endif # NET_CORE |
| 498 | |
| 499 | config SUNGEM_PHY |
| 500 | tristate |
| 501 | |
| 502 | source "drivers/net/arcnet/Kconfig" |
| 503 | |
| 504 | source "drivers/atm/Kconfig" |
| 505 | |
| 506 | source "drivers/net/dsa/Kconfig" |
| 507 | |
| 508 | source "drivers/net/ethernet/Kconfig" |
| 509 | |
| 510 | source "drivers/net/fddi/Kconfig" |
| 511 | |
| 512 | source "drivers/net/ipa/Kconfig" |
| 513 | |
| 514 | source "drivers/net/phy/Kconfig" |
| 515 | |
| 516 | source "drivers/net/pse-pd/Kconfig" |
| 517 | |
| 518 | source "drivers/net/can/Kconfig" |
| 519 | |
| 520 | source "drivers/net/mctp/Kconfig" |
| 521 | |
| 522 | source "drivers/net/mdio/Kconfig" |
| 523 | |
| 524 | source "drivers/net/pcs/Kconfig" |
| 525 | |
| 526 | source "drivers/net/plip/Kconfig" |
| 527 | |
| 528 | source "drivers/net/ppp/Kconfig" |
| 529 | |
| 530 | source "drivers/net/slip/Kconfig" |
| 531 | |
| 532 | source "drivers/s390/net/Kconfig" |
| 533 | |
| 534 | source "drivers/net/usb/Kconfig" |
| 535 | |
| 536 | source "drivers/net/wireless/Kconfig" |
| 537 | |
| 538 | source "drivers/net/wan/Kconfig" |
| 539 | |
| 540 | source "drivers/net/ieee802154/Kconfig" |
| 541 | |
| 542 | source "drivers/net/wwan/Kconfig" |
| 543 | |
| 544 | config XEN_NETDEV_FRONTEND |
| 545 | tristate "Xen network device frontend driver" |
| 546 | depends on XEN |
| 547 | select XEN_XENBUS_FRONTEND |
| 548 | select PAGE_POOL |
| 549 | default y |
| 550 | help |
| 551 | This driver provides support for Xen paravirtual network |
| 552 | devices exported by a Xen network driver domain (often |
| 553 | domain 0). |
| 554 | |
| 555 | The corresponding Linux backend driver is enabled by the |
| 556 | CONFIG_XEN_NETDEV_BACKEND option. |
| 557 | |
| 558 | If you are compiling a kernel for use as Xen guest, you |
| 559 | should say Y here. To compile this driver as a module, chose |
| 560 | M here: the module will be called xen-netfront. |
| 561 | |
| 562 | config XEN_NETDEV_BACKEND |
| 563 | tristate "Xen backend network device" |
| 564 | depends on XEN_BACKEND |
| 565 | help |
| 566 | This driver allows the kernel to act as a Xen network driver |
| 567 | domain which exports paravirtual network devices to other |
| 568 | Xen domains. These devices can be accessed by any operating |
| 569 | system that implements a compatible front end. |
| 570 | |
| 571 | The corresponding Linux frontend driver is enabled by the |
| 572 | CONFIG_XEN_NETDEV_FRONTEND configuration option. |
| 573 | |
| 574 | The backend driver presents a standard network device |
| 575 | endpoint for each paravirtual network device to the driver |
| 576 | domain network stack. These can then be bridged or routed |
| 577 | etc in order to provide full network connectivity. |
| 578 | |
| 579 | If you are compiling a kernel to run in a Xen network driver |
| 580 | domain (often this is domain 0) you should say Y here. To |
| 581 | compile this driver as a module, chose M here: the module |
| 582 | will be called xen-netback. |
| 583 | |
| 584 | config VMXNET3 |
| 585 | tristate "VMware VMXNET3 ethernet driver" |
| 586 | depends on PCI && INET |
| 587 | depends on PAGE_SIZE_LESS_THAN_64KB |
| 588 | select PAGE_POOL |
| 589 | help |
| 590 | This driver supports VMware's vmxnet3 virtual ethernet NIC. |
| 591 | To compile this driver as a module, choose M here: the |
| 592 | module will be called vmxnet3. |
| 593 | |
| 594 | config FUJITSU_ES |
| 595 | tristate "FUJITSU Extended Socket Network Device driver" |
| 596 | depends on ACPI |
| 597 | help |
| 598 | This driver provides support for Extended Socket network device |
| 599 | on Extended Partitioning of FUJITSU PRIMEQUEST 2000 E2 series. |
| 600 | |
| 601 | source "drivers/net/thunderbolt/Kconfig" |
| 602 | source "drivers/net/hyperv/Kconfig" |
| 603 | |
| 604 | config NETDEVSIM |
| 605 | tristate "Simulated networking device" |
| 606 | depends on DEBUG_FS |
| 607 | depends on INET |
| 608 | depends on PSAMPLE || PSAMPLE=n |
| 609 | depends on PTP_1588_CLOCK_MOCK || PTP_1588_CLOCK_MOCK=n |
| 610 | select NET_DEVLINK |
| 611 | select PAGE_POOL |
| 612 | select NET_SHAPER |
| 613 | help |
| 614 | This driver is a developer testing tool and software model that can |
| 615 | be used to test various control path networking APIs, especially |
| 616 | HW-offload related. |
| 617 | |
| 618 | To compile this driver as a module, choose M here: the module |
| 619 | will be called netdevsim. |
| 620 | |
| 621 | config NET_FAILOVER |
| 622 | tristate "Failover driver" |
| 623 | select FAILOVER |
| 624 | help |
| 625 | This provides an automated failover mechanism via APIs to create |
| 626 | and destroy a failover master netdev and manages a primary and |
| 627 | standby slave netdevs that get registered via the generic failover |
| 628 | infrastructure. This can be used by paravirtual drivers to enable |
| 629 | an alternate low latency datapath. It also enables live migration of |
| 630 | a VM with direct attached VF by failing over to the paravirtual |
| 631 | datapath when the VF is unplugged. |
| 632 | |
| 633 | endif # NETDEVICES |