2 # Network device configuration
8 bool "Network device support"
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 <http://www.tldp.org/guides.html>.
24 # All the following symbols are dependent on NETDEVICES - do not repeat
25 # that for each of the symbols.
29 tristate "Intermediate Functional Block support"
30 depends on NET_CLS_ACT
32 This is an intermediate driver that allows sharing of
34 To compile this driver as a module, choose M here: the module
35 will be called ifb. If you want to use more than one ifb
36 device at a time, you need to compile this driver as a module.
37 Instead of 'ifb', the devices will then be called 'ifb0',
39 Look at the iproute2 documentation directory for usage etc
42 tristate "Dummy net driver support"
44 This is essentially a bit-bucket device (i.e. traffic you send to
45 this device is consigned into oblivion) with a configurable IP
46 address. It is most commonly used in order to make your currently
47 inactive SLIP address seem like a real address for local programs.
48 If you use SLIP or PPP, you might want to say Y here. Since this
49 thing often comes in handy, the default is Y. It won't enlarge your
50 kernel either. What a deal. Read about it in the Network
51 Administrator's Guide, available from
52 <http://www.tldp.org/docs.html#guide>.
54 To compile this driver as a module, choose M here: the module
55 will be called dummy. If you want to use more than one dummy
56 device at a time, you need to compile this driver as a module.
57 Instead of 'dummy', the devices will then be called 'dummy0',
61 tristate "Bonding driver support"
63 depends on IPV6 || IPV6=n
65 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
66 Channels together. This is called 'Etherchannel' by Cisco,
67 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
69 The driver supports multiple bonding modes to allow for both high
70 performance and high availability operation.
72 Refer to <file:Documentation/networking/bonding.txt> for more
75 To compile this driver as a module, choose M here: the module
76 will be called bonding.
79 tristate "MAC-VLAN support (EXPERIMENTAL)"
80 depends on EXPERIMENTAL
82 This allows one to create virtual interfaces that map packets to
83 or from specific MAC addresses to a particular interface.
85 Macvlan devices can be added using the "ip" command from the
86 iproute2 package starting with the iproute2-2.6.23 release:
88 "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
90 To compile this driver as a module, choose M here: the module
91 will be called macvlan.
94 tristate "MAC-VLAN based tap driver (EXPERIMENTAL)"
97 This adds a specialized tap character device driver that is based
98 on the MAC-VLAN network interface, called macvtap. A macvtap device
99 can be added in the same way as a macvlan device, using 'type
100 macvlan', and then be accessed through the tap user space interface.
102 To compile this driver as a module, choose M here: the module
103 will be called macvtap.
106 tristate "EQL (serial line load balancing) support"
108 If you have two serial connections to some other computer (this
109 usually requires two modems and two telephone lines) and you use
110 SLIP (the protocol for sending Internet traffic over telephone
111 lines) or PPP (a better SLIP) on them, you can make them behave like
112 one double speed connection using this driver. Naturally, this has
113 to be supported at the other end as well, either with a similar EQL
114 Linux driver or with a Livingston Portmaster 2e.
116 Say Y if you want this and read
117 <file:Documentation/networking/eql.txt>. You may also want to read
118 section 6.2 of the NET-3-HOWTO, available from
119 <http://www.tldp.org/docs.html#howto>.
121 To compile this driver as a module, choose M here: the module
122 will be called eql. If unsure, say N.
125 tristate "Universal TUN/TAP device driver support"
128 TUN/TAP provides packet reception and transmission for user space
129 programs. It can be viewed as a simple Point-to-Point or Ethernet
130 device, which instead of receiving packets from a physical media,
131 receives them from user space program and instead of sending packets
132 via physical media writes them to the user space program.
134 When a program opens /dev/net/tun, driver creates and registers
135 corresponding net device tunX or tapX. After a program closed above
136 devices, driver will automatically delete tunXX or tapXX device and
137 all routes corresponding to it.
139 Please read <file:Documentation/networking/tuntap.txt> for more
142 To compile this driver as a module, choose M here: the module
145 If you don't know what to use this for, you don't need it.
148 tristate "Virtual ethernet pair device"
150 This device is a local ethernet tunnel. Devices are created in pairs.
151 When one end receives the packet it appears on its pair and vice
155 tristate "General Instruments Surfboard 1000"
158 This is a driver for the General Instrument (also known as
159 NextLevel) SURFboard 1000 internal
160 cable modem. This is an ISA card which is used by a number of cable
161 TV companies to provide cable modem access. It's a one-way
162 downstream-only cable modem, meaning that your upstream net link is
163 provided by your regular phone modem.
165 At present this driver only compiles as a module, so say M here if
166 you have this card. The module will be called sb1000. Then read
167 <file:Documentation/networking/README.sb1000> for information on how
168 to use this module, as it needs special ppp scripts for establishing
169 a connection. Further documentation and the necessary scripts can be
172 <http://www.jacksonville.net/~fventuri/>
173 <http://home.adelphia.net/~siglercm/sb1000.html>
174 <http://linuxpower.cx/~cable/>
176 If you don't have this card, of course say N.
178 source "drivers/net/arcnet/Kconfig"
181 tristate "Generic Media Independent Interface device support"
183 Most ethernet controllers have MII transceiver either as an external
184 or internal device. It is safe to say Y or M here even if your
185 ethernet card lacks MII.
187 source "drivers/net/phy/Kconfig"
196 source "drivers/net/ethernet/Kconfig"
198 source "drivers/net/fddi/Kconfig"
200 source "drivers/net/plip/Kconfig"
202 source "drivers/net/tokenring/Kconfig"
204 source "drivers/net/wireless/Kconfig"
206 source "drivers/net/wimax/Kconfig"
208 source "drivers/net/usb/Kconfig"
210 source "drivers/net/pcmcia/Kconfig"
212 source "drivers/net/ppp/Kconfig"
214 source "drivers/net/wan/Kconfig"
216 source "drivers/atm/Kconfig"
218 source "drivers/ieee802154/Kconfig"
220 source "drivers/s390/net/Kconfig"
222 source "drivers/net/caif/Kconfig"
224 config XEN_NETDEV_FRONTEND
225 tristate "Xen network device frontend driver"
227 select XEN_XENBUS_FRONTEND
230 This driver provides support for Xen paravirtual network
231 devices exported by a Xen network driver domain (often
234 The corresponding Linux backend driver is enabled by the
235 CONFIG_XEN_NETDEV_BACKEND option.
237 If you are compiling a kernel for use as Xen guest, you
238 should say Y here. To compile this driver as a module, chose
239 M here: the module will be called xen-netfront.
241 config XEN_NETDEV_BACKEND
242 tristate "Xen backend network device"
243 depends on XEN_BACKEND
245 This driver allows the kernel to act as a Xen network driver
246 domain which exports paravirtual network devices to other
247 Xen domains. These devices can be accessed by any operating
248 system that implements a compatible front end.
250 The corresponding Linux frontend driver is enabled by the
251 CONFIG_XEN_NETDEV_FRONTEND configuration option.
253 The backend driver presents a standard network device
254 endpoint for each paravirtual network device to the driver
255 domain network stack. These can then be bridged or routed
256 etc in order to provide full network connectivity.
258 If you are compiling a kernel to run in a Xen network driver
259 domain (often this is domain 0) you should say Y here. To
260 compile this driver as a module, chose M here: the module
261 will be called xen-netback.
264 tristate "RapidIO Ethernet over messaging driver support"
267 config RIONET_TX_SIZE
268 int "Number of outbound queue entries"
272 config RIONET_RX_SIZE
273 int "Number of inbound queue entries"
278 tristate "SLIP (serial line) support"
280 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
281 connect to your Internet service provider or to connect to some
282 other local Unix box or if you want to configure your Linux box as a
283 Slip/CSlip server for other people to dial in. SLIP (Serial Line
284 Internet Protocol) is a protocol used to send Internet traffic over
285 serial connections such as telephone lines or null modem cables;
286 nowadays, the protocol PPP is more commonly used for this same
289 Normally, your access provider has to support SLIP in order for you
290 to be able to use it, but there is now a SLIP emulator called SLiRP
291 around (available from
292 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
293 allows you to use SLIP over a regular dial up shell connection. If
294 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
295 NET-3-HOWTO, available from
296 <http://www.tldp.org/docs.html#howto>, explains how to
297 configure SLIP. Note that you don't need this option if you just
298 want to run term (term is a program which gives you almost full
299 Internet connectivity if you have a regular dial up shell account on
300 some Internet connected Unix computer. Read
301 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
302 support will enlarge your kernel by about 4 KB. If unsure, say N.
304 To compile this driver as a module, choose M here. The module
307 config SLIP_COMPRESSED
308 bool "CSLIP compressed headers"
312 This protocol is faster than SLIP because it uses compression on the
313 TCP/IP headers (not on the data itself), but it has to be supported
314 on both ends. Ask your access provider if you are not sure and
315 answer Y, just in case. You will still be able to use plain SLIP. If
316 you plan to use SLiRP, the SLIP emulator (available from
317 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
318 allows you to use SLIP over a regular dial up shell connection, you
319 definitely want to say Y here. The NET-3-HOWTO, available from
320 <http://www.tldp.org/docs.html#howto>, explains how to configure
321 CSLIP. This won't enlarge your kernel.
326 This option enables Van Jacobsen serial line header compression
330 bool "Keepalive and linefill"
333 Adds additional capabilities to the SLIP driver to support the
334 RELCOM line fill and keepalive monitoring. Ideal on poor quality
337 config SLIP_MODE_SLIP6
338 bool "Six bit SLIP encapsulation"
341 Just occasionally you may need to run IP over hostile serial
342 networks that don't pass all control characters or are only seven
343 bit. Saying Y here adds an extra mode you can use with SLIP:
344 "slip6". In this mode, SLIP will only send normal ASCII symbols over
345 the serial device. Naturally, this has to be supported at the other
346 end of the link as well. It's good enough, for example, to run IP
347 over the async ports of a Camtec JNT Pad. If unsure, say N.
350 bool "Fibre Channel driver support"
351 depends on SCSI && PCI
353 Fibre Channel is a high speed serial protocol mainly used to connect
354 large storage devices to the computer; it is compatible with and
355 intended to replace SCSI.
357 If you intend to use Fibre Channel, you need to have a Fibre channel
358 adaptor card in your computer; say Y here and to the driver for your
359 adaptor below. You also should have said Y to "SCSI support" and
360 "SCSI generic support".
363 tristate "Network console logging support"
365 If you want to log kernel messages over the network, enable this.
366 See <file:Documentation/networking/netconsole.txt> for details.
368 config NETCONSOLE_DYNAMIC
369 bool "Dynamic reconfiguration of logging targets"
370 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
371 !(NETCONSOLE=y && CONFIGFS_FS=m)
373 This option enables the ability to dynamically reconfigure target
374 parameters (interface, IP addresses, port numbers, MAC addresses)
375 at runtime through a userspace interface exported using configfs.
376 See <file:Documentation/networking/netconsole.txt> for details.
382 bool "Netpoll traffic trapping"
386 config NET_POLL_CONTROLLER
390 tristate "Virtio network driver (EXPERIMENTAL)"
391 depends on EXPERIMENTAL && VIRTIO
393 This is the virtual network driver for virtio. It can be used with
394 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
397 tristate "VMware VMXNET3 ethernet driver"
398 depends on PCI && INET
400 This driver supports VMware's vmxnet3 virtual ethernet NIC.
401 To compile this driver as a module, choose M here: the
402 module will be called vmxnet3.