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"
193 source "drivers/net/ethernet/Kconfig"
195 menuconfig NET_ETHERNET
196 bool "Ethernet (10 or 100Mbit)"
199 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
200 type of Local Area Network (LAN) in universities and companies.
202 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
203 coaxial cable, linking computers in a chain), 10BASE-T or twisted
204 pair (10 Mbps over twisted pair cable, linking computers to central
205 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
206 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
207 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
208 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
209 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
210 Ethernet (1 Gbps over optical fiber or short copper links).
212 If your Linux machine will be connected to an Ethernet and you have
213 an Ethernet network interface card (NIC) installed in your computer,
214 say Y here and read the Ethernet-HOWTO, available from
215 <http://www.tldp.org/docs.html#howto>. You will then also have
216 to say Y to the driver for your particular NIC.
218 Note that the answer to this question won't directly affect the
219 kernel: saying N will just cause the configurator to skip all
220 the questions about Ethernet network cards. If unsure, say N.
225 tristate "Renesas SuperH Ethernet support"
226 depends on SUPERH && \
227 (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712 || \
228 CPU_SUBTYPE_SH7763 || CPU_SUBTYPE_SH7619 || \
229 CPU_SUBTYPE_SH7724 || CPU_SUBTYPE_SH7757)
235 Renesas SuperH Ethernet device driver.
236 This driver supporting CPUs are:
237 - SH7710, SH7712, SH7763, SH7619, SH7724, and SH7757.
240 tristate "NetX Ethernet support"
244 This is support for the Hilscher netX builtin Ethernet ports
246 To compile this driver as a module, choose M here. The module
247 will be called netx-eth.
250 tristate "DM9000 support"
251 depends on ARM || BLACKFIN || MIPS
255 Support for DM9000 chipset.
257 To compile this driver as a module, choose M here. The module
258 will be called dm9000.
260 config DM9000_DEBUGLEVEL
261 int "DM9000 maximum debug level"
265 The maximum level of debugging code compiled into the DM9000
268 config DM9000_FORCE_SIMPLE_PHY_POLL
269 bool "Force simple NSR based PHY polling"
272 This configuration forces the DM9000 to use the NSR's LinkStatus
273 bit to determine if the link is up or down instead of the more
274 costly MII PHY reads. Note, this will not work if the chip is
275 operating with an external PHY.
278 tristate "ENC28J60 support"
279 depends on EXPERIMENTAL && SPI && NET_ETHERNET
282 Support for the Microchip EN28J60 ethernet chip.
284 To compile this driver as a module, choose M here. The module will be
287 config ENC28J60_WRITEVERIFY
288 bool "Enable write verify"
291 Enable the verify after the buffer write useful for debugging purpose.
295 bool "EISA, VLB, PCI and on board controllers"
296 depends on ISA || EISA || PCI
298 This is another class of network cards which attach directly to the
299 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
300 available from <http://www.tldp.org/docs.html#howto>.
302 Note that the answer to this question doesn't directly affect the
303 kernel: saying N will just cause the configurator to skip all
304 the questions about this class of network cards. If you say Y, you
305 will be asked for your specific card in the following questions. If
306 you are unsure, say Y.
309 bool "Pocket and portable adapters"
312 Cute little network (Ethernet) devices which attach to the parallel
313 port ("pocket adapters"), commonly used with laptops. If you have
314 one of those, say Y and read the Ethernet-HOWTO, available from
315 <http://www.tldp.org/docs.html#howto>.
317 If you want to plug a network (or some other) card into the PCMCIA
318 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
319 credit card size extension cards used by all modern laptops), you
320 need the pcmcia-cs package (location contained in the file
321 <file:Documentation/Changes>) and you can say N here.
323 Laptop users should read the Linux Laptop home page at
324 <http://www.linux-on-laptops.com/> or
325 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
327 Note that the answer to this question doesn't directly affect the
328 kernel: saying N will just cause the configurator to skip all
329 the questions about this class of network devices. If you say Y, you
330 will be asked for your specific device in the following questions.
338 menuconfig NETDEV_1000
339 bool "Ethernet (1000 Mbit)"
343 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
344 type of Local Area Network (LAN) in universities and companies.
346 Say Y here to get to see options for Gigabit Ethernet drivers.
347 This option alone does not add any kernel code.
348 Note that drivers supporting both 100 and 1000 MBit may be listed
349 under "Ethernet (10 or 100MBit)" instead.
351 If you say N, all options in this submenu will be skipped and disabled.
358 # 10 Gigabit Ethernet
361 menuconfig NETDEV_10000
362 bool "Ethernet (10000 Mbit)"
366 Say Y here to get to see options for 10 Gigabit Ethernet drivers.
367 This option alone does not add any kernel code.
369 If you say N, all options in this submenu will be skipped and disabled.
381 source "drivers/net/tokenring/Kconfig"
383 source "drivers/net/wireless/Kconfig"
385 source "drivers/net/wimax/Kconfig"
387 source "drivers/net/usb/Kconfig"
389 source "drivers/net/pcmcia/Kconfig"
391 source "drivers/net/wan/Kconfig"
393 source "drivers/atm/Kconfig"
395 source "drivers/ieee802154/Kconfig"
397 source "drivers/s390/net/Kconfig"
399 source "drivers/net/caif/Kconfig"
402 tristate "Tilera GBE/XGBE network driver support"
407 This is a standard Linux network device driver for the
408 on-chip Tilera Gigabit Ethernet and XAUI interfaces.
410 To compile this driver as a module, choose M here: the module
411 will be called tile_net.
413 config XEN_NETDEV_FRONTEND
414 tristate "Xen network device frontend driver"
416 select XEN_XENBUS_FRONTEND
419 This driver provides support for Xen paravirtual network
420 devices exported by a Xen network driver domain (often
423 The corresponding Linux backend driver is enabled by the
424 CONFIG_XEN_NETDEV_BACKEND option.
426 If you are compiling a kernel for use as Xen guest, you
427 should say Y here. To compile this driver as a module, chose
428 M here: the module will be called xen-netfront.
430 config XEN_NETDEV_BACKEND
431 tristate "Xen backend network device"
432 depends on XEN_BACKEND
434 This driver allows the kernel to act as a Xen network driver
435 domain which exports paravirtual network devices to other
436 Xen domains. These devices can be accessed by any operating
437 system that implements a compatible front end.
439 The corresponding Linux frontend driver is enabled by the
440 CONFIG_XEN_NETDEV_FRONTEND configuration option.
442 The backend driver presents a standard network device
443 endpoint for each paravirtual network device to the driver
444 domain network stack. These can then be bridged or routed
445 etc in order to provide full network connectivity.
447 If you are compiling a kernel to run in a Xen network driver
448 domain (often this is domain 0) you should say Y here. To
449 compile this driver as a module, chose M here: the module
450 will be called xen-netback.
453 tristate "RapidIO Ethernet over messaging driver support"
456 config RIONET_TX_SIZE
457 int "Number of outbound queue entries"
461 config RIONET_RX_SIZE
462 int "Number of inbound queue entries"
467 tristate "FDDI driver support"
468 depends on (PCI || EISA || TC)
470 Fiber Distributed Data Interface is a high speed local area network
471 design; essentially a replacement for high speed Ethernet. FDDI can
472 run over copper or fiber. If you are connected to such a network and
473 want a driver for the FDDI card in your computer, say Y here (and
474 then also Y to the driver for your FDDI card, below). Most people
478 tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
479 depends on FDDI && (PCI || EISA || TC)
481 This is support for the DIGITAL series of TURBOchannel (DEFTA),
482 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
483 to a local FDDI network.
485 To compile this driver as a module, choose M here: the module
486 will be called defxx. If unsure, say N.
490 prompt "Use MMIO instead of PIO" if PCI || EISA
492 default n if PCI || EISA
495 This instructs the driver to use EISA or PCI memory-mapped I/O
496 (MMIO) as appropriate instead of programmed I/O ports (PIO).
497 Enabling this gives an improvement in processing time in parts
498 of the driver, but it may cause problems with EISA (DEFEA)
499 adapters. TURBOchannel does not have the concept of I/O ports,
500 so MMIO is always used for these (DEFTA) adapters.
505 tristate "SysKonnect FDDI PCI support"
506 depends on FDDI && PCI
509 Say Y here if you have a SysKonnect FDDI PCI adapter.
510 The following adapters are supported by this driver:
511 - SK-5521 (SK-NET FDDI-UP)
512 - SK-5522 (SK-NET FDDI-UP DAS)
513 - SK-5541 (SK-NET FDDI-FP)
514 - SK-5543 (SK-NET FDDI-LP)
515 - SK-5544 (SK-NET FDDI-LP DAS)
516 - SK-5821 (SK-NET FDDI-UP64)
517 - SK-5822 (SK-NET FDDI-UP64 DAS)
518 - SK-5841 (SK-NET FDDI-FP64)
519 - SK-5843 (SK-NET FDDI-LP64)
520 - SK-5844 (SK-NET FDDI-LP64 DAS)
521 - Netelligent 100 FDDI DAS Fibre SC
522 - Netelligent 100 FDDI SAS Fibre SC
523 - Netelligent 100 FDDI DAS UTP
524 - Netelligent 100 FDDI SAS UTP
525 - Netelligent 100 FDDI SAS Fibre MIC
527 Read <file:Documentation/networking/skfp.txt> for information about
530 Questions concerning this driver can be addressed to:
531 <linux@syskonnect.de>
533 To compile this driver as a module, choose M here: the module
534 will be called skfp. This is recommended.
537 bool "HIPPI driver support (EXPERIMENTAL)"
538 depends on EXPERIMENTAL && INET && PCI
540 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
541 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
542 can run over copper (25m) or fiber (300m on multi-mode or 10km on
543 single-mode). HIPPI networks are commonly used for clusters and to
544 connect to super computers. If you are connected to a HIPPI network
545 and have a HIPPI network card in your computer that you want to use
546 under Linux, say Y here (you must also remember to enable the driver
547 for your HIPPI card below). Most people will say N here.
550 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
551 depends on HIPPI && PCI
553 Say Y here if this is your PCI HIPPI network card.
555 To compile this driver as a module, choose M here: the module
556 will be called rrunner. If unsure, say N.
558 config ROADRUNNER_LARGE_RINGS
559 bool "Use large TX/RX rings (EXPERIMENTAL)"
560 depends on ROADRUNNER
562 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
563 of additional memory to allow for fastest operation, both for
564 transmitting and receiving. This memory cannot be used by any other
565 kernel code or by user space programs. Say Y here only if you have
569 tristate "PLIP (parallel port) support"
572 PLIP (Parallel Line Internet Protocol) is used to create a
573 reasonably fast mini network consisting of two (or, rarely, more)
574 local machines. A PLIP link from a Linux box is a popular means to
575 install a Linux distribution on a machine which doesn't have a
576 CD-ROM drive (a minimal system has to be transferred with floppies
577 first). The kernels on both machines need to have this PLIP option
578 enabled for this to work.
580 The PLIP driver has two modes, mode 0 and mode 1. The parallel
581 ports (the connectors at the computers with 25 holes) are connected
582 with "null printer" or "Turbo Laplink" cables which can transmit 4
583 bits at a time (mode 0) or with special PLIP cables, to be used on
584 bidirectional parallel ports only, which can transmit 8 bits at a
585 time (mode 1); you can find the wiring of these cables in
586 <file:Documentation/networking/PLIP.txt>. The cables can be up to
587 15m long. Mode 0 works also if one of the machines runs DOS/Windows
588 and has some PLIP software installed, e.g. the Crynwr PLIP packet
589 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
590 and winsock or NCSA's telnet.
592 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
593 as the NET-3-HOWTO, both available from
594 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
595 protocol has been changed and this PLIP driver won't work together
596 with the PLIP support in Linux versions 1.0.x. This option enlarges
597 your kernel by about 8 KB.
599 To compile this driver as a module, choose M here. The module
600 will be called plip. If unsure, say Y or M, in case you buy
604 tristate "PPP (point-to-point protocol) support"
607 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
608 the same purpose: sending Internet traffic over telephone (and other
609 serial) lines. Ask your access provider if they support it, because
610 otherwise you can't use it; most Internet access providers these
611 days support PPP rather than SLIP.
613 To use PPP, you need an additional program called pppd as described
614 in the PPP-HOWTO, available at
615 <http://www.tldp.org/docs.html#howto>. Make sure that you have
616 the version of pppd recommended in <file:Documentation/Changes>.
617 The PPP option enlarges your kernel by about 16 KB.
619 There are actually two versions of PPP: the traditional PPP for
620 asynchronous lines, such as regular analog phone lines, and
621 synchronous PPP which can be used over digital ISDN lines for
622 example. If you want to use PPP over phone lines or other
623 asynchronous serial lines, you need to say Y (or M) here and also to
624 the next option, "PPP support for async serial ports". For PPP over
625 synchronous lines, you should say Y (or M) here and to "Support
626 synchronous PPP", below.
628 If you said Y to "Version information on all symbols" above, then
629 you cannot compile the PPP driver into the kernel; you can then only
630 compile it as a module. To compile this driver as a module, choose M
631 here. The module will be called ppp_generic.
634 bool "PPP multilink support (EXPERIMENTAL)"
635 depends on PPP && EXPERIMENTAL
637 PPP multilink is a protocol (defined in RFC 1990) which allows you
638 to combine several (logical or physical) lines into one logical PPP
639 connection, so that you can utilize your full bandwidth.
641 This has to be supported at the other end as well and you need a
642 version of the pppd daemon which understands the multilink protocol.
650 Say Y here if you want to be able to filter the packets passing over
651 PPP interfaces. This allows you to control which packets count as
652 activity (i.e. which packets will reset the idle timer or bring up
653 a demand-dialed link) and which packets are to be dropped entirely.
654 You need to say Y here if you wish to use the pass-filter and
655 active-filter options to pppd.
660 tristate "PPP support for async serial ports"
664 Say Y (or M) here if you want to be able to use PPP over standard
665 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
666 a modem (not a synchronous or ISDN modem) to contact your ISP, you
669 To compile this driver as a module, choose M here.
674 tristate "PPP support for sync tty ports"
677 Say Y (or M) here if you want to be able to use PPP over synchronous
678 (HDLC) tty devices, such as the SyncLink adapter. These devices
679 are often used for high-speed leased lines like T1/E1.
681 To compile this driver as a module, choose M here.
684 tristate "PPP Deflate compression"
689 Support for the Deflate compression method for PPP, which uses the
690 Deflate algorithm (the same algorithm that gzip uses) to compress
691 each PPP packet before it is sent over the wire. The machine at the
692 other end of the PPP link (usually your ISP) has to support the
693 Deflate compression method as well for this to be useful. Even if
694 they don't support it, it is safe to say Y here.
696 To compile this driver as a module, choose M here.
699 tristate "PPP BSD-Compress compression"
702 Support for the BSD-Compress compression method for PPP, which uses
703 the LZW compression method to compress each PPP packet before it is
704 sent over the wire. The machine at the other end of the PPP link
705 (usually your ISP) has to support the BSD-Compress compression
706 method as well for this to be useful. Even if they don't support it,
707 it is safe to say Y here.
709 The PPP Deflate compression method ("PPP Deflate compression",
710 above) is preferable to BSD-Compress, because it compresses better
713 Note that the BSD compression code will always be compiled as a
714 module; it is called bsd_comp and will show up in the directory
715 modules once you have said "make modules". If unsure, say N.
718 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
719 depends on PPP && EXPERIMENTAL
725 Support for the MPPE Encryption protocol, as employed by the
726 Microsoft Point-to-Point Tunneling Protocol.
728 See http://pptpclient.sourceforge.net/ for information on
729 configuring PPTP clients and servers to utilize this method.
732 tristate "PPP over Ethernet (EXPERIMENTAL)"
733 depends on EXPERIMENTAL && PPP
735 Support for PPP over Ethernet.
737 This driver requires the latest version of pppd from the CVS
738 repository at cvs.samba.org. Alternatively, see the
739 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
740 which contains instruction on how to use this driver (under
741 the heading "Kernel mode PPPoE").
744 tristate "PPP over IPv4 (PPTP) (EXPERIMENTAL)"
745 depends on EXPERIMENTAL && PPP && NET_IPGRE_DEMUX
747 Support for PPP over IPv4.(Point-to-Point Tunneling Protocol)
749 This driver requires pppd plugin to work in client mode or
750 modified pptpd (poptop) to work in server mode.
751 See http://accel-pptp.sourceforge.net/ for information how to
755 tristate "PPP over ATM"
756 depends on ATM && PPP
758 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
759 This implementation does not yet comply with section 8 of RFC2364,
760 which can lead to bad results if the ATM peer loses state and
761 changes its encapsulation unilaterally.
764 tristate "PPP over L2TP (EXPERIMENTAL)"
765 depends on EXPERIMENTAL && L2TP && PPP
767 Support for PPP-over-L2TP socket family. L2TP is a protocol
768 used by ISPs and enterprises to tunnel PPP traffic over UDP
769 tunnels. L2TP is replacing PPTP for VPN uses.
772 tristate "SLIP (serial line) support"
774 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
775 connect to your Internet service provider or to connect to some
776 other local Unix box or if you want to configure your Linux box as a
777 Slip/CSlip server for other people to dial in. SLIP (Serial Line
778 Internet Protocol) is a protocol used to send Internet traffic over
779 serial connections such as telephone lines or null modem cables;
780 nowadays, the protocol PPP is more commonly used for this same
783 Normally, your access provider has to support SLIP in order for you
784 to be able to use it, but there is now a SLIP emulator called SLiRP
785 around (available from
786 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
787 allows you to use SLIP over a regular dial up shell connection. If
788 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
789 NET-3-HOWTO, available from
790 <http://www.tldp.org/docs.html#howto>, explains how to
791 configure SLIP. Note that you don't need this option if you just
792 want to run term (term is a program which gives you almost full
793 Internet connectivity if you have a regular dial up shell account on
794 some Internet connected Unix computer. Read
795 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
796 support will enlarge your kernel by about 4 KB. If unsure, say N.
798 To compile this driver as a module, choose M here. The module
801 config SLIP_COMPRESSED
802 bool "CSLIP compressed headers"
806 This protocol is faster than SLIP because it uses compression on the
807 TCP/IP headers (not on the data itself), but it has to be supported
808 on both ends. Ask your access provider if you are not sure and
809 answer Y, just in case. You will still be able to use plain SLIP. If
810 you plan to use SLiRP, the SLIP emulator (available from
811 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
812 allows you to use SLIP over a regular dial up shell connection, you
813 definitely want to say Y here. The NET-3-HOWTO, available from
814 <http://www.tldp.org/docs.html#howto>, explains how to configure
815 CSLIP. This won't enlarge your kernel.
820 This option enables Van Jacobsen serial line header compression
824 bool "Keepalive and linefill"
827 Adds additional capabilities to the SLIP driver to support the
828 RELCOM line fill and keepalive monitoring. Ideal on poor quality
831 config SLIP_MODE_SLIP6
832 bool "Six bit SLIP encapsulation"
835 Just occasionally you may need to run IP over hostile serial
836 networks that don't pass all control characters or are only seven
837 bit. Saying Y here adds an extra mode you can use with SLIP:
838 "slip6". In this mode, SLIP will only send normal ASCII symbols over
839 the serial device. Naturally, this has to be supported at the other
840 end of the link as well. It's good enough, for example, to run IP
841 over the async ports of a Camtec JNT Pad. If unsure, say N.
844 bool "Fibre Channel driver support"
845 depends on SCSI && PCI
847 Fibre Channel is a high speed serial protocol mainly used to connect
848 large storage devices to the computer; it is compatible with and
849 intended to replace SCSI.
851 If you intend to use Fibre Channel, you need to have a Fibre channel
852 adaptor card in your computer; say Y here and to the driver for your
853 adaptor below. You also should have said Y to "SCSI support" and
854 "SCSI generic support".
857 tristate "Network console logging support"
859 If you want to log kernel messages over the network, enable this.
860 See <file:Documentation/networking/netconsole.txt> for details.
862 config NETCONSOLE_DYNAMIC
863 bool "Dynamic reconfiguration of logging targets"
864 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
865 !(NETCONSOLE=y && CONFIGFS_FS=m)
867 This option enables the ability to dynamically reconfigure target
868 parameters (interface, IP addresses, port numbers, MAC addresses)
869 at runtime through a userspace interface exported using configfs.
870 See <file:Documentation/networking/netconsole.txt> for details.
876 bool "Netpoll traffic trapping"
880 config NET_POLL_CONTROLLER
884 tristate "Virtio network driver (EXPERIMENTAL)"
885 depends on EXPERIMENTAL && VIRTIO
887 This is the virtual network driver for virtio. It can be used with
888 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
891 tristate "VMware VMXNET3 ethernet driver"
892 depends on PCI && INET
894 This driver supports VMware's vmxnet3 virtual ethernet NIC.
895 To compile this driver as a module, choose M here: the
896 module will be called vmxnet3.