drivers/net/Kconfig

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