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. Since this 66 thing often comes in handy, the default is Y. It won't enlarge your 67 kernel either. 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 74config EQUALIZER 75 tristate "EQL (serial line load balancing) support" 76 ---help--- 77 If you have two serial connections to some other computer (this 78 usually requires two modems and two telephone lines) and you use 79 SLIP (the protocol for sending Internet traffic over telephone 80 lines) or PPP (a better SLIP) on them, you can make them behave like 81 one double speed connection using this driver. Naturally, this has 82 to be supported at the other end as well, either with a similar EQL 83 Linux driver or with a Livingston Portmaster 2e. 84 85 Say Y if you want this and read 86 <file:Documentation/networking/eql.txt>. You may also want to read 87 section 6.2 of the NET-3-HOWTO, available from 88 <http://www.tldp.org/docs.html#howto>. 89 90 To compile this driver as a module, choose M here: the module 91 will be called eql. If unsure, say N. 92 93config NET_FC 94 bool "Fibre Channel driver support" 95 depends on SCSI && PCI 96 help 97 Fibre Channel is a high speed serial protocol mainly used to connect 98 large storage devices to the computer; it is compatible with and 99 intended to replace SCSI. 100 101 If you intend to use Fibre Channel, you need to have a Fibre channel 102 adaptor card in your computer; say Y here and to the driver for your 103 adaptor below. You also should have said Y to "SCSI support" and 104 "SCSI generic support". 105 106config IFB 107 tristate "Intermediate Functional Block support" 108 depends on NET_CLS_ACT 109 ---help--- 110 This is an intermediate driver that allows sharing of 111 resources. 112 To compile this driver as a module, choose M here: the module 113 will be called ifb. If you want to use more than one ifb 114 device at a time, you need to compile this driver as a module. 115 Instead of 'ifb', the devices will then be called 'ifb0', 116 'ifb1' etc. 117 Look at the iproute2 documentation directory for usage etc 118 119source "drivers/net/team/Kconfig" 120 121config MACVLAN 122 tristate "MAC-VLAN support" 123 ---help--- 124 This allows one to create virtual interfaces that map packets to 125 or from specific MAC addresses to a particular interface. 126 127 Macvlan devices can be added using the "ip" command from the 128 iproute2 package starting with the iproute2-2.6.23 release: 129 130 "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan" 131 132 To compile this driver as a module, choose M here: the module 133 will be called macvlan. 134 135config MACVTAP 136 tristate "MAC-VLAN based tap driver" 137 depends on MACVLAN 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 147config VXLAN 148 tristate "Virtual eXtensible Local Area Network (VXLAN)" 149 depends on INET 150 select NET_IP_TUNNEL 151 select NET_UDP_TUNNEL 152 ---help--- 153 This allows one to create vxlan virtual interfaces that provide 154 Layer 2 Networks over Layer 3 Networks. VXLAN is often used 155 to tunnel virtual network infrastructure in virtualized environments. 156 For more information see: 157 http://tools.ietf.org/html/draft-mahalingam-dutt-dcops-vxlan-02 158 159 To compile this driver as a module, choose M here: the module 160 will be called vxlan. 161 162config NETCONSOLE 163 tristate "Network console logging support" 164 ---help--- 165 If you want to log kernel messages over the network, enable this. 166 See <file:Documentation/networking/netconsole.txt> for details. 167 168config NETCONSOLE_DYNAMIC 169 bool "Dynamic reconfiguration of logging targets" 170 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \ 171 !(NETCONSOLE=y && CONFIGFS_FS=m) 172 help 173 This option enables the ability to dynamically reconfigure target 174 parameters (interface, IP addresses, port numbers, MAC addresses) 175 at runtime through a userspace interface exported using configfs. 176 See <file:Documentation/networking/netconsole.txt> for details. 177 178config NETPOLL 179 def_bool NETCONSOLE 180 181config NET_POLL_CONTROLLER 182 def_bool NETPOLL 183 184config NTB_NETDEV 185 tristate "Virtual Ethernet over NTB" 186 depends on NTB 187 188config RIONET 189 tristate "RapidIO Ethernet over messaging driver support" 190 depends on RAPIDIO 191 192config RIONET_TX_SIZE 193 int "Number of outbound queue entries" 194 depends on RIONET 195 default "128" 196 197config RIONET_RX_SIZE 198 int "Number of inbound queue entries" 199 depends on RIONET 200 default "128" 201 202config TUN 203 tristate "Universal TUN/TAP device driver support" 204 select CRC32 205 ---help--- 206 TUN/TAP provides packet reception and transmission for user space 207 programs. It can be viewed as a simple Point-to-Point or Ethernet 208 device, which instead of receiving packets from a physical media, 209 receives them from user space program and instead of sending packets 210 via physical media writes them to the user space program. 211 212 When a program opens /dev/net/tun, driver creates and registers 213 corresponding net device tunX or tapX. After a program closed above 214 devices, driver will automatically delete tunXX or tapXX device and 215 all routes corresponding to it. 216 217 Please read <file:Documentation/networking/tuntap.txt> for more 218 information. 219 220 To compile this driver as a module, choose M here: the module 221 will be called tun. 222 223 If you don't know what to use this for, you don't need it. 224 225config VETH 226 tristate "Virtual ethernet pair device" 227 ---help--- 228 This device is a local ethernet tunnel. Devices are created in pairs. 229 When one end receives the packet it appears on its pair and vice 230 versa. 231 232config VIRTIO_NET 233 tristate "Virtio network driver" 234 depends on VIRTIO 235 select AVERAGE 236 ---help--- 237 This is the virtual network driver for virtio. It can be used with 238 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M. 239 240config NLMON 241 tristate "Virtual netlink monitoring device" 242 ---help--- 243 This option enables a monitoring net device for netlink skbs. The 244 purpose of this is to analyze netlink messages with packet sockets. 245 Thus applications like tcpdump will be able to see local netlink 246 messages if they tap into the netlink device, record pcaps for further 247 diagnostics, etc. This is mostly intended for developers or support 248 to debug netlink issues. If unsure, say N. 249 250endif # NET_CORE 251 252config SUNGEM_PHY 253 tristate 254 255source "drivers/net/arcnet/Kconfig" 256 257source "drivers/atm/Kconfig" 258 259source "drivers/net/caif/Kconfig" 260 261source "drivers/net/dsa/Kconfig" 262 263source "drivers/net/ethernet/Kconfig" 264 265source "drivers/net/fddi/Kconfig" 266 267source "drivers/net/hippi/Kconfig" 268 269config NET_SB1000 270 tristate "General Instruments Surfboard 1000" 271 depends on PNP 272 ---help--- 273 This is a driver for the General Instrument (also known as 274 NextLevel) SURFboard 1000 internal 275 cable modem. This is an ISA card which is used by a number of cable 276 TV companies to provide cable modem access. It's a one-way 277 downstream-only cable modem, meaning that your upstream net link is 278 provided by your regular phone modem. 279 280 At present this driver only compiles as a module, so say M here if 281 you have this card. The module will be called sb1000. Then read 282 <file:Documentation/networking/README.sb1000> for information on how 283 to use this module, as it needs special ppp scripts for establishing 284 a connection. Further documentation and the necessary scripts can be 285 found at: 286 287 <http://www.jacksonville.net/~fventuri/> 288 <http://home.adelphia.net/~siglercm/sb1000.html> 289 <http://linuxpower.cx/~cable/> 290 291 If you don't have this card, of course say N. 292 293source "drivers/net/phy/Kconfig" 294 295source "drivers/net/plip/Kconfig" 296 297source "drivers/net/ppp/Kconfig" 298 299source "drivers/net/slip/Kconfig" 300 301source "drivers/s390/net/Kconfig" 302 303source "drivers/net/usb/Kconfig" 304 305source "drivers/net/wireless/Kconfig" 306 307source "drivers/net/wimax/Kconfig" 308 309source "drivers/net/wan/Kconfig" 310 311source "drivers/net/ieee802154/Kconfig" 312 313config XEN_NETDEV_FRONTEND 314 tristate "Xen network device frontend driver" 315 depends on XEN 316 select XEN_XENBUS_FRONTEND 317 default y 318 help 319 This driver provides support for Xen paravirtual network 320 devices exported by a Xen network driver domain (often 321 domain 0). 322 323 The corresponding Linux backend driver is enabled by the 324 CONFIG_XEN_NETDEV_BACKEND option. 325 326 If you are compiling a kernel for use as Xen guest, you 327 should say Y here. To compile this driver as a module, chose 328 M here: the module will be called xen-netfront. 329 330config XEN_NETDEV_BACKEND 331 tristate "Xen backend network device" 332 depends on XEN_BACKEND 333 help 334 This driver allows the kernel to act as a Xen network driver 335 domain which exports paravirtual network devices to other 336 Xen domains. These devices can be accessed by any operating 337 system that implements a compatible front end. 338 339 The corresponding Linux frontend driver is enabled by the 340 CONFIG_XEN_NETDEV_FRONTEND configuration option. 341 342 The backend driver presents a standard network device 343 endpoint for each paravirtual network device to the driver 344 domain network stack. These can then be bridged or routed 345 etc in order to provide full network connectivity. 346 347 If you are compiling a kernel to run in a Xen network driver 348 domain (often this is domain 0) you should say Y here. To 349 compile this driver as a module, chose M here: the module 350 will be called xen-netback. 351 352config VMXNET3 353 tristate "VMware VMXNET3 ethernet driver" 354 depends on PCI && INET 355 help 356 This driver supports VMware's vmxnet3 virtual ethernet NIC. 357 To compile this driver as a module, choose M here: the 358 module will be called vmxnet3. 359 360source "drivers/net/hyperv/Kconfig" 361 362endif # NETDEVICES 363