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