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