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