Version:  2.0.40 2.2.26 2.4.37 3.8 3.9 3.10 3.11 3.12 3.13 3.14 3.15 3.16 3.17 3.18 3.19 4.0 4.1 4.2 4.3 4.4 4.5


  1 #
  2 # Network device configuration
  3 #
  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.
 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.
 19           See also "The Linux Network Administrator's Guide" by Olaf Kirch and
 20           Terry Dawson. Available at <>.
 22           If unsure, say Y.
 24 # All the following symbols are dependent on NETDEVICES - do not repeat
 25 # that for each of the symbols.
 28 config MII
 29         tristate
 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.)
 38 if NET_CORE
 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.
 49           The driver supports multiple bonding modes to allow for both high
 50           performance and high availability operation.
 52           Refer to <file:Documentation/networking/bonding.txt> for more
 53           information.
 55           To compile this driver as a module, choose M here: the module
 56           will be called bonding.
 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. 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           <>.
 71           To compile this driver as a module, choose M here: the module
 72           will be called dummy.
 74 config 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.
 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           <>.
 90           To compile this driver as a module, choose M here: the module
 91           will be called eql.  If unsure, say N.
 93 config 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.
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".
106 config 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
119 source "drivers/net/team/Kconfig"
121 config 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.
127           Macvlan devices can be added using the "ip" command from the
128           iproute2 package starting with the iproute2-2.6.23 release:
130           "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
132           To compile this driver as a module, choose M here: the module
133           will be called macvlan.
135 config MACVTAP
136         tristate "MAC-VLAN based tap driver"
137         depends on MACVLAN
138         depends on INET
139         help
140           This adds a specialized tap character device driver that is based
141           on the MAC-VLAN network interface, called macvtap. A macvtap device
142           can be added in the same way as a macvlan device, using 'type
143           macvtap', and then be accessed through the tap user space interface.
145           To compile this driver as a module, choose M here: the module
146           will be called macvtap.
149 config IPVLAN
150     tristate "IP-VLAN support"
151     depends on INET
152     depends on IPV6
153     ---help---
154       This allows one to create virtual devices off of a main interface
155       and packets will be delivered based on the dest L3 (IPv6/IPv4 addr)
156       on packets. All interfaces (including the main interface) share L2
157       making it transparent to the connected L2 switch.
159       Ipvlan devices can be added using the "ip" command from the
160       iproute2 package starting with the iproute2-3.19 release:
162       "ip link add link <main-dev> [ NAME ] type ipvlan"
164       To compile this driver as a module, choose M here: the module
165       will be called ipvlan.
168 config VXLAN
169        tristate "Virtual eXtensible Local Area Network (VXLAN)"
170        depends on INET
171        select NET_UDP_TUNNEL
172        ---help---
173           This allows one to create vxlan virtual interfaces that provide
174           Layer 2 Networks over Layer 3 Networks. VXLAN is often used
175           to tunnel virtual network infrastructure in virtualized environments.
176           For more information see:
179           To compile this driver as a module, choose M here: the module
180           will be called vxlan.
182 config GENEVE
183        tristate "Generic Network Virtualization Encapsulation"
184        depends on INET && NET_UDP_TUNNEL
185        select NET_IP_TUNNEL
186        ---help---
187           This allows one to create geneve virtual interfaces that provide
188           Layer 2 Networks over Layer 3 Networks. GENEVE is often used
189           to tunnel virtual network infrastructure in virtualized environments.
190           For more information see:
193           To compile this driver as a module, choose M here: the module
194           will be called geneve.
196 config NETCONSOLE
197         tristate "Network console logging support"
198         ---help---
199         If you want to log kernel messages over the network, enable this.
200         See <file:Documentation/networking/netconsole.txt> for details.
203         bool "Dynamic reconfiguration of logging targets"
204         depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
205                         !(NETCONSOLE=y && CONFIGFS_FS=m)
206         help
207           This option enables the ability to dynamically reconfigure target
208           parameters (interface, IP addresses, port numbers, MAC addresses)
209           at runtime through a userspace interface exported using configfs.
210           See <file:Documentation/networking/netconsole.txt> for details.
212 config NETPOLL
213         def_bool NETCONSOLE
214         select SRCU
217         def_bool NETPOLL
219 config NTB_NETDEV
220         tristate "Virtual Ethernet over NTB Transport"
221         depends on NTB_TRANSPORT
223 config RIONET
224         tristate "RapidIO Ethernet over messaging driver support"
225         depends on RAPIDIO
227 config RIONET_TX_SIZE
228         int "Number of outbound queue entries"
229         depends on RIONET
230         default "128"
232 config RIONET_RX_SIZE
233         int "Number of inbound queue entries"
234         depends on RIONET
235         default "128"
237 config TUN
238         tristate "Universal TUN/TAP device driver support"
239         depends on INET
240         select CRC32
241         ---help---
242           TUN/TAP provides packet reception and transmission for user space
243           programs.  It can be viewed as a simple Point-to-Point or Ethernet
244           device, which instead of receiving packets from a physical media,
245           receives them from user space program and instead of sending packets
246           via physical media writes them to the user space program.
248           When a program opens /dev/net/tun, driver creates and registers
249           corresponding net device tunX or tapX.  After a program closed above
250           devices, driver will automatically delete tunXX or tapXX device and
251           all routes corresponding to it.
253           Please read <file:Documentation/networking/tuntap.txt> for more
254           information.
256           To compile this driver as a module, choose M here: the module
257           will be called tun.
259           If you don't know what to use this for, you don't need it.
261 config TUN_VNET_CROSS_LE
262         bool "Support for cross-endian vnet headers on little-endian kernels"
263         default n
264         ---help---
265           This option allows TUN/TAP and MACVTAP device drivers in a
266           little-endian kernel to parse vnet headers that come from a
267           big-endian legacy virtio device.
269           Userspace programs can control the feature using the TUNSETVNETBE
270           and TUNGETVNETBE ioctls.
272           Unless you have a little-endian system hosting a big-endian virtual
273           machine with a legacy virtio NIC, you should say N.
275 config VETH
276         tristate "Virtual ethernet pair device"
277         ---help---
278           This device is a local ethernet tunnel. Devices are created in pairs.
279           When one end receives the packet it appears on its pair and vice
280           versa.
282 config VIRTIO_NET
283         tristate "Virtio network driver"
284         depends on VIRTIO
285         ---help---
286           This is the virtual network driver for virtio.  It can be used with
287           lguest or QEMU based VMMs (like KVM or Xen).  Say Y or M.
289 config NLMON
290         tristate "Virtual netlink monitoring device"
291         ---help---
292           This option enables a monitoring net device for netlink skbs. The
293           purpose of this is to analyze netlink messages with packet sockets.
294           Thus applications like tcpdump will be able to see local netlink
295           messages if they tap into the netlink device, record pcaps for further
296           diagnostics, etc. This is mostly intended for developers or support
297           to debug netlink issues. If unsure, say N.
299 config NET_VRF
300         tristate "Virtual Routing and Forwarding (Lite)"
301         depends on IP_MULTIPLE_TABLES
302         depends on NET_L3_MASTER_DEV
303         depends on IPV6 || IPV6=n
304         depends on IPV6_MULTIPLE_TABLES || IPV6=n
305         ---help---
306           This option enables the support for mapping interfaces into VRF's. The
307           support enables VRF devices.
309 endif # NET_CORE
311 config SUNGEM_PHY
312         tristate
314 source "drivers/net/arcnet/Kconfig"
316 source "drivers/atm/Kconfig"
318 source "drivers/net/caif/Kconfig"
320 source "drivers/net/dsa/Kconfig"
322 source "drivers/net/ethernet/Kconfig"
324 source "drivers/net/fddi/Kconfig"
326 source "drivers/net/hippi/Kconfig"
328 config NET_SB1000
329         tristate "General Instruments Surfboard 1000"
330         depends on PNP
331         ---help---
332           This is a driver for the General Instrument (also known as
333           NextLevel) SURFboard 1000 internal
334           cable modem. This is an ISA card which is used by a number of cable
335           TV companies to provide cable modem access. It's a one-way
336           downstream-only cable modem, meaning that your upstream net link is
337           provided by your regular phone modem.
339           At present this driver only compiles as a module, so say M here if
340           you have this card. The module will be called sb1000. Then read
341           <file:Documentation/networking/README.sb1000> for information on how
342           to use this module, as it needs special ppp scripts for establishing
343           a connection. Further documentation and the necessary scripts can be
344           found at:
346           <>
347           <>
348           <>
350           If you don't have this card, of course say N.
352 source "drivers/net/phy/Kconfig"
354 source "drivers/net/plip/Kconfig"
356 source "drivers/net/ppp/Kconfig"
358 source "drivers/net/slip/Kconfig"
360 source "drivers/s390/net/Kconfig"
362 source "drivers/net/usb/Kconfig"
364 source "drivers/net/wireless/Kconfig"
366 source "drivers/net/wimax/Kconfig"
368 source "drivers/net/wan/Kconfig"
370 source "drivers/net/ieee802154/Kconfig"
373         tristate "Xen network device frontend driver"
374         depends on XEN
375         select XEN_XENBUS_FRONTEND
376         default y
377         help
378           This driver provides support for Xen paravirtual network
379           devices exported by a Xen network driver domain (often
380           domain 0).
382           The corresponding Linux backend driver is enabled by the
383           CONFIG_XEN_NETDEV_BACKEND option.
385           If you are compiling a kernel for use as Xen guest, you
386           should say Y here. To compile this driver as a module, chose
387           M here: the module will be called xen-netfront.
390         tristate "Xen backend network device"
391         depends on XEN_BACKEND
392         help
393           This driver allows the kernel to act as a Xen network driver
394           domain which exports paravirtual network devices to other
395           Xen domains. These devices can be accessed by any operating
396           system that implements a compatible front end.
398           The corresponding Linux frontend driver is enabled by the
399           CONFIG_XEN_NETDEV_FRONTEND configuration option.
401           The backend driver presents a standard network device
402           endpoint for each paravirtual network device to the driver
403           domain network stack. These can then be bridged or routed
404           etc in order to provide full network connectivity.
406           If you are compiling a kernel to run in a Xen network driver
407           domain (often this is domain 0) you should say Y here. To
408           compile this driver as a module, chose M here: the module
409           will be called xen-netback.
411 config VMXNET3
412         tristate "VMware VMXNET3 ethernet driver"
413         depends on PCI && INET
414         help
415           This driver supports VMware's vmxnet3 virtual ethernet NIC.
416           To compile this driver as a module, choose M here: the
417           module will be called vmxnet3.
419 config FUJITSU_ES
420         tristate "FUJITSU Extended Socket Network Device driver"
421         depends on ACPI
422         help
423           This driver provides support for Extended Socket network device
424           on Extended Partitioning of FUJITSU PRIMEQUEST 2000 E2 series.
426 source "drivers/net/hyperv/Kconfig"
428 endif # NETDEVICES

This page was automatically generated by LXR 0.3.1 (source).  •  Linux is a registered trademark of Linus Torvalds  •  Contact us