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