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. If you want to use more than one dummy 70 device at a time, you need to compile this driver as a module. 71 Instead of 'dummy', the devices will then be called 'dummy0', 72 'dummy1' etc. 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 MII 107 tristate "Generic Media Independent Interface device support" 108 help 109 Most ethernet controllers have MII transceiver either as an external 110 or internal device. It is safe to say Y or M here even if your 111 ethernet card lacks MII. 112 113source "drivers/ieee802154/Kconfig" 114 115config IFB 116 tristate "Intermediate Functional Block support" 117 depends on NET_CLS_ACT 118 ---help--- 119 This is an intermediate driver that allows sharing of 120 resources. 121 To compile this driver as a module, choose M here: the module 122 will be called ifb. If you want to use more than one ifb 123 device at a time, you need to compile this driver as a module. 124 Instead of 'ifb', the devices will then be called 'ifb0', 125 'ifb1' etc. 126 Look at the iproute2 documentation directory for usage etc 127 128source "drivers/net/team/Kconfig" 129 130config MACVLAN 131 tristate "MAC-VLAN support (EXPERIMENTAL)" 132 depends on EXPERIMENTAL 133 ---help--- 134 This allows one to create virtual interfaces that map packets to 135 or from specific MAC addresses to a particular interface. 136 137 Macvlan devices can be added using the "ip" command from the 138 iproute2 package starting with the iproute2-2.6.23 release: 139 140 "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan" 141 142 To compile this driver as a module, choose M here: the module 143 will be called macvlan. 144 145config MACVTAP 146 tristate "MAC-VLAN based tap driver (EXPERIMENTAL)" 147 depends on MACVLAN 148 help 149 This adds a specialized tap character device driver that is based 150 on the MAC-VLAN network interface, called macvtap. A macvtap device 151 can be added in the same way as a macvlan device, using 'type 152 macvlan', and then be accessed through the tap user space interface. 153 154 To compile this driver as a module, choose M here: the module 155 will be called macvtap. 156 157config NETCONSOLE 158 tristate "Network console logging support" 159 ---help--- 160 If you want to log kernel messages over the network, enable this. 161 See <file:Documentation/networking/netconsole.txt> for details. 162 163config NETCONSOLE_DYNAMIC 164 bool "Dynamic reconfiguration of logging targets" 165 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \ 166 !(NETCONSOLE=y && CONFIGFS_FS=m) 167 help 168 This option enables the ability to dynamically reconfigure target 169 parameters (interface, IP addresses, port numbers, MAC addresses) 170 at runtime through a userspace interface exported using configfs. 171 See <file:Documentation/networking/netconsole.txt> for details. 172 173config NETPOLL 174 def_bool NETCONSOLE 175 176config NETPOLL_TRAP 177 bool "Netpoll traffic trapping" 178 default n 179 depends on NETPOLL 180 181config NET_POLL_CONTROLLER 182 def_bool NETPOLL 183 184config RIONET 185 tristate "RapidIO Ethernet over messaging driver support" 186 depends on RAPIDIO 187 188config RIONET_TX_SIZE 189 int "Number of outbound queue entries" 190 depends on RIONET 191 default "128" 192 193config RIONET_RX_SIZE 194 int "Number of inbound queue entries" 195 depends on RIONET 196 default "128" 197 198config TUN 199 tristate "Universal TUN/TAP device driver support" 200 select CRC32 201 ---help--- 202 TUN/TAP provides packet reception and transmission for user space 203 programs. It can be viewed as a simple Point-to-Point or Ethernet 204 device, which instead of receiving packets from a physical media, 205 receives them from user space program and instead of sending packets 206 via physical media writes them to the user space program. 207 208 When a program opens /dev/net/tun, driver creates and registers 209 corresponding net device tunX or tapX. After a program closed above 210 devices, driver will automatically delete tunXX or tapXX device and 211 all routes corresponding to it. 212 213 Please read <file:Documentation/networking/tuntap.txt> for more 214 information. 215 216 To compile this driver as a module, choose M here: the module 217 will be called tun. 218 219 If you don't know what to use this for, you don't need it. 220 221config VETH 222 tristate "Virtual ethernet pair device" 223 ---help--- 224 This device is a local ethernet tunnel. Devices are created in pairs. 225 When one end receives the packet it appears on its pair and vice 226 versa. 227 228config VIRTIO_NET 229 tristate "Virtio network driver (EXPERIMENTAL)" 230 depends on EXPERIMENTAL && VIRTIO 231 ---help--- 232 This is the virtual network driver for virtio. It can be used with 233 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M. 234 235endif # NET_CORE 236 237config SUNGEM_PHY 238 tristate 239 240source "drivers/net/arcnet/Kconfig" 241 242source "drivers/atm/Kconfig" 243 244source "drivers/net/caif/Kconfig" 245 246source "drivers/net/dsa/Kconfig" 247 248source "drivers/net/ethernet/Kconfig" 249 250source "drivers/net/fddi/Kconfig" 251 252source "drivers/net/hippi/Kconfig" 253 254config NET_SB1000 255 tristate "General Instruments Surfboard 1000" 256 depends on PNP 257 ---help--- 258 This is a driver for the General Instrument (also known as 259 NextLevel) SURFboard 1000 internal 260 cable modem. This is an ISA card which is used by a number of cable 261 TV companies to provide cable modem access. It's a one-way 262 downstream-only cable modem, meaning that your upstream net link is 263 provided by your regular phone modem. 264 265 At present this driver only compiles as a module, so say M here if 266 you have this card. The module will be called sb1000. Then read 267 <file:Documentation/networking/README.sb1000> for information on how 268 to use this module, as it needs special ppp scripts for establishing 269 a connection. Further documentation and the necessary scripts can be 270 found at: 271 272 <http://www.jacksonville.net/~fventuri/> 273 <http://home.adelphia.net/~siglercm/sb1000.html> 274 <http://linuxpower.cx/~cable/> 275 276 If you don't have this card, of course say N. 277 278source "drivers/net/phy/Kconfig" 279 280source "drivers/net/plip/Kconfig" 281 282source "drivers/net/ppp/Kconfig" 283 284source "drivers/net/slip/Kconfig" 285 286source "drivers/s390/net/Kconfig" 287 288source "drivers/net/tokenring/Kconfig" 289 290source "drivers/net/usb/Kconfig" 291 292source "drivers/net/wireless/Kconfig" 293 294source "drivers/net/wimax/Kconfig" 295 296source "drivers/net/wan/Kconfig" 297 298config XEN_NETDEV_FRONTEND 299 tristate "Xen network device frontend driver" 300 depends on XEN 301 select XEN_XENBUS_FRONTEND 302 default y 303 help 304 This driver provides support for Xen paravirtual network 305 devices exported by a Xen network driver domain (often 306 domain 0). 307 308 The corresponding Linux backend driver is enabled by the 309 CONFIG_XEN_NETDEV_BACKEND option. 310 311 If you are compiling a kernel for use as Xen guest, you 312 should say Y here. To compile this driver as a module, chose 313 M here: the module will be called xen-netfront. 314 315config XEN_NETDEV_BACKEND 316 tristate "Xen backend network device" 317 depends on XEN_BACKEND 318 help 319 This driver allows the kernel to act as a Xen network driver 320 domain which exports paravirtual network devices to other 321 Xen domains. These devices can be accessed by any operating 322 system that implements a compatible front end. 323 324 The corresponding Linux frontend driver is enabled by the 325 CONFIG_XEN_NETDEV_FRONTEND configuration option. 326 327 The backend driver presents a standard network device 328 endpoint for each paravirtual network device to the driver 329 domain network stack. These can then be bridged or routed 330 etc in order to provide full network connectivity. 331 332 If you are compiling a kernel to run in a Xen network driver 333 domain (often this is domain 0) you should say Y here. To 334 compile this driver as a module, chose M here: the module 335 will be called xen-netback. 336 337config VMXNET3 338 tristate "VMware VMXNET3 ethernet driver" 339 depends on PCI && INET 340 help 341 This driver supports VMware's vmxnet3 virtual ethernet NIC. 342 To compile this driver as a module, choose M here: the 343 module will be called vmxnet3. 344 345source "drivers/net/hyperv/Kconfig" 346 347endif # NETDEVICES 348