2 # Network device configuration
11 bool "Network device support"
13 You can say N here if you don't intend to connect your Linux box to
14 any other computer at all.
16 You'll have to say Y if your computer contains a network card that
17 you want to use under Linux. If you are going to run SLIP or PPP over
18 telephone line or null modem cable you need say Y here. Connecting
19 two machines with parallel ports using PLIP needs this, as well as
20 AX.25/KISS for sending Internet traffic over amateur radio links.
22 See also "The Linux Network Administrator's Guide" by Olaf Kirch and
23 Terry Dawson. Available at <http://www.tldp.org/guides.html>.
27 # All the following symbols are dependent on NETDEVICES - do not repeat
28 # that for each of the symbols.
32 tristate "Intermediate Functional Block support"
33 depends on NET_CLS_ACT
35 This is an intermediate driver that allows sharing of
37 To compile this driver as a module, choose M here: the module
38 will be called ifb. If you want to use more than one ifb
39 device at a time, you need to compile this driver as a module.
40 Instead of 'ifb', the devices will then be called 'ifb0',
42 Look at the iproute2 documentation directory for usage etc
45 tristate "Dummy net driver support"
47 This is essentially a bit-bucket device (i.e. traffic you send to
48 this device is consigned into oblivion) with a configurable IP
49 address. It is most commonly used in order to make your currently
50 inactive SLIP address seem like a real address for local programs.
51 If you use SLIP or PPP, you might want to say Y here. Since this
52 thing often comes in handy, the default is Y. It won't enlarge your
53 kernel either. What a deal. Read about it in the Network
54 Administrator's Guide, available from
55 <http://www.tldp.org/docs.html#guide>.
57 To compile this driver as a module, choose M here: the module
58 will be called dummy. If you want to use more than one dummy
59 device at a time, you need to compile this driver as a module.
60 Instead of 'dummy', the devices will then be called 'dummy0',
64 tristate "Bonding driver support"
66 depends on IPV6 || IPV6=n
68 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
69 Channels together. This is called 'Etherchannel' by Cisco,
70 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
72 The driver supports multiple bonding modes to allow for both high
73 performance and high availability operation.
75 Refer to <file:Documentation/networking/bonding.txt> for more
78 To compile this driver as a module, choose M here: the module
79 will be called bonding.
82 tristate "MAC-VLAN support (EXPERIMENTAL)"
83 depends on EXPERIMENTAL
85 This allows one to create virtual interfaces that map packets to
86 or from specific MAC addresses to a particular interface.
88 Macvlan devices can be added using the "ip" command from the
89 iproute2 package starting with the iproute2-2.6.23 release:
91 "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
93 To compile this driver as a module, choose M here: the module
94 will be called macvlan.
97 tristate "MAC-VLAN based tap driver (EXPERIMENTAL)"
100 This adds a specialized tap character device driver that is based
101 on the MAC-VLAN network interface, called macvtap. A macvtap device
102 can be added in the same way as a macvlan device, using 'type
103 macvlan', and then be accessed through the tap user space interface.
105 To compile this driver as a module, choose M here: the module
106 will be called macvtap.
109 tristate "EQL (serial line load balancing) support"
111 If you have two serial connections to some other computer (this
112 usually requires two modems and two telephone lines) and you use
113 SLIP (the protocol for sending Internet traffic over telephone
114 lines) or PPP (a better SLIP) on them, you can make them behave like
115 one double speed connection using this driver. Naturally, this has
116 to be supported at the other end as well, either with a similar EQL
117 Linux driver or with a Livingston Portmaster 2e.
119 Say Y if you want this and read
120 <file:Documentation/networking/eql.txt>. You may also want to read
121 section 6.2 of the NET-3-HOWTO, available from
122 <http://www.tldp.org/docs.html#howto>.
124 To compile this driver as a module, choose M here: the module
125 will be called eql. If unsure, say N.
128 tristate "Universal TUN/TAP device driver support"
131 TUN/TAP provides packet reception and transmission for user space
132 programs. It can be viewed as a simple Point-to-Point or Ethernet
133 device, which instead of receiving packets from a physical media,
134 receives them from user space program and instead of sending packets
135 via physical media writes them to the user space program.
137 When a program opens /dev/net/tun, driver creates and registers
138 corresponding net device tunX or tapX. After a program closed above
139 devices, driver will automatically delete tunXX or tapXX device and
140 all routes corresponding to it.
142 Please read <file:Documentation/networking/tuntap.txt> for more
145 To compile this driver as a module, choose M here: the module
148 If you don't know what to use this for, you don't need it.
151 tristate "Virtual ethernet pair device"
153 This device is a local ethernet tunnel. Devices are created in pairs.
154 When one end receives the packet it appears on its pair and vice
158 tristate "General Instruments Surfboard 1000"
161 This is a driver for the General Instrument (also known as
162 NextLevel) SURFboard 1000 internal
163 cable modem. This is an ISA card which is used by a number of cable
164 TV companies to provide cable modem access. It's a one-way
165 downstream-only cable modem, meaning that your upstream net link is
166 provided by your regular phone modem.
168 At present this driver only compiles as a module, so say M here if
169 you have this card. The module will be called sb1000. Then read
170 <file:Documentation/networking/README.sb1000> for information on how
171 to use this module, as it needs special ppp scripts for establishing
172 a connection. Further documentation and the necessary scripts can be
175 <http://www.jacksonville.net/~fventuri/>
176 <http://home.adelphia.net/~siglercm/sb1000.html>
177 <http://linuxpower.cx/~cable/>
179 If you don't have this card, of course say N.
181 source "drivers/net/arcnet/Kconfig"
184 tristate "Generic Media Independent Interface device support"
186 Most ethernet controllers have MII transceiver either as an external
187 or internal device. It is safe to say Y or M here even if your
188 ethernet card lacks MII.
190 source "drivers/net/phy/Kconfig"
196 source "drivers/net/ethernet/Kconfig"
198 menuconfig NET_ETHERNET
199 bool "Ethernet (10 or 100Mbit)"
202 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
203 type of Local Area Network (LAN) in universities and companies.
205 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
206 coaxial cable, linking computers in a chain), 10BASE-T or twisted
207 pair (10 Mbps over twisted pair cable, linking computers to central
208 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
209 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
210 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
211 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
212 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
213 Ethernet (1 Gbps over optical fiber or short copper links).
215 If your Linux machine will be connected to an Ethernet and you have
216 an Ethernet network interface card (NIC) installed in your computer,
217 say Y here and read the Ethernet-HOWTO, available from
218 <http://www.tldp.org/docs.html#howto>. You will then also have
219 to say Y to the driver for your particular NIC.
221 Note that the answer to this question won't directly affect the
222 kernel: saying N will just cause the configurator to skip all
223 the questions about Ethernet network cards. If unsure, say N.
228 tristate "Atmel MACB support"
229 depends on HAVE_NET_MACB
232 The Atmel MACB ethernet interface is found on many AT32 and AT91
233 parts. Say Y to include support for the MACB chip.
235 To compile this driver as a module, choose M here: the module
238 source "drivers/net/arm/Kconfig"
241 tristate "Renesas SuperH Ethernet support"
242 depends on SUPERH && \
243 (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712 || \
244 CPU_SUBTYPE_SH7763 || CPU_SUBTYPE_SH7619 || \
245 CPU_SUBTYPE_SH7724 || CPU_SUBTYPE_SH7757)
251 Renesas SuperH Ethernet device driver.
252 This driver supporting CPUs are:
253 - SH7710, SH7712, SH7763, SH7619, SH7724, and SH7757.
256 tristate "NetX Ethernet support"
260 This is support for the Hilscher netX builtin Ethernet ports
262 To compile this driver as a module, choose M here. The module
263 will be called netx-eth.
266 tristate "DM9000 support"
267 depends on ARM || BLACKFIN || MIPS
271 Support for DM9000 chipset.
273 To compile this driver as a module, choose M here. The module
274 will be called dm9000.
276 config DM9000_DEBUGLEVEL
277 int "DM9000 maximum debug level"
281 The maximum level of debugging code compiled into the DM9000
284 config DM9000_FORCE_SIMPLE_PHY_POLL
285 bool "Force simple NSR based PHY polling"
288 This configuration forces the DM9000 to use the NSR's LinkStatus
289 bit to determine if the link is up or down instead of the more
290 costly MII PHY reads. Note, this will not work if the chip is
291 operating with an external PHY.
294 tristate "ENC28J60 support"
295 depends on EXPERIMENTAL && SPI && NET_ETHERNET
298 Support for the Microchip EN28J60 ethernet chip.
300 To compile this driver as a module, choose M here. The module will be
303 config ENC28J60_WRITEVERIFY
304 bool "Enable write verify"
307 Enable the verify after the buffer write useful for debugging purpose.
311 tristate "OpenCores 10/100 Mbps Ethernet MAC support"
312 depends on NET_ETHERNET && HAS_IOMEM && HAS_DMA
318 Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC.
321 tristate "Aeroflex Gaisler GRETH Ethernet MAC support"
326 Say Y here if you want to use the Aeroflex Gaisler GRETH Ethernet MAC.
329 tristate "Dave ethernet support (DNET)"
330 depends on NET_ETHERNET && HAS_IOMEM
333 The Dave ethernet interface (DNET) is found on Qong Board FPGA.
334 Say Y to include support for the DNET chip.
336 To compile this driver as a module, choose M here: the module
340 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
341 depends on ISA || EISA || PCI
343 If you have a network (Ethernet) card of this type, say Y and read
344 the Ethernet-HOWTO, available from
345 <http://www.tldp.org/docs.html#howto>.
347 To compile this driver as a module, choose M here. The module
348 will be called hp100.
351 bool "EISA, VLB, PCI and on board controllers"
352 depends on ISA || EISA || PCI
354 This is another class of network cards which attach directly to the
355 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
356 available from <http://www.tldp.org/docs.html#howto>.
358 Note that the answer to this question doesn't directly affect the
359 kernel: saying N will just cause the configurator to skip all
360 the questions about this class of network cards. If you say Y, you
361 will be asked for your specific card in the following questions. If
362 you are unsure, say Y.
364 config ADAPTEC_STARFIRE
365 tristate "Adaptec Starfire/DuraLAN support"
366 depends on NET_PCI && PCI
370 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
371 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
372 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
375 To compile this driver as a module, choose M here: the module
376 will be called starfire. This is recommended.
379 tristate "nForce Ethernet support"
380 depends on NET_PCI && PCI
382 If you have a network (Ethernet) controller of this type, say Y and
383 read the Ethernet-HOWTO, available from
384 <http://www.tldp.org/docs.html#howto>.
386 To compile this driver as a module, choose M here. The module
387 will be called forcedeth.
390 tristate "Myson MTD-8xx PCI Ethernet support"
391 depends on NET_PCI && PCI
395 Say Y here to support the Myson MTD-800 family of PCI-based Ethernet
396 cards. <http://www.myson.com.tw/>
399 tristate "RDC R6040 Fast Ethernet Adapter support"
400 depends on NET_PCI && PCI
405 This is a driver for the R6040 Fast Ethernet MACs found in the
406 the RDC R-321x System-on-chips.
408 To compile this driver as a module, choose M here: the module
409 will be called r6040. This is recommended.
412 bool "Pocket and portable adapters"
415 Cute little network (Ethernet) devices which attach to the parallel
416 port ("pocket adapters"), commonly used with laptops. If you have
417 one of those, say Y and read the Ethernet-HOWTO, available from
418 <http://www.tldp.org/docs.html#howto>.
420 If you want to plug a network (or some other) card into the PCMCIA
421 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
422 credit card size extension cards used by all modern laptops), you
423 need the pcmcia-cs package (location contained in the file
424 <file:Documentation/Changes>) and you can say N here.
426 Laptop users should read the Linux Laptop home page at
427 <http://www.linux-on-laptops.com/> or
428 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
430 Note that the answer to this question doesn't directly affect the
431 kernel: saying N will just cause the configurator to skip all
432 the questions about this class of network devices. If you say Y, you
433 will be asked for your specific device in the following questions.
441 menuconfig NETDEV_1000
442 bool "Ethernet (1000 Mbit)"
446 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
447 type of Local Area Network (LAN) in universities and companies.
449 Say Y here to get to see options for Gigabit Ethernet drivers.
450 This option alone does not add any kernel code.
451 Note that drivers supporting both 100 and 1000 MBit may be listed
452 under "Ethernet (10 or 100MBit)" instead.
454 If you say N, all options in this submenu will be skipped and disabled.
461 # 10 Gigabit Ethernet
464 menuconfig NETDEV_10000
465 bool "Ethernet (10000 Mbit)"
469 Say Y here to get to see options for 10 Gigabit Ethernet drivers.
470 This option alone does not add any kernel code.
472 If you say N, all options in this submenu will be skipped and disabled.
484 source "drivers/net/tokenring/Kconfig"
486 source "drivers/net/wireless/Kconfig"
488 source "drivers/net/wimax/Kconfig"
490 source "drivers/net/usb/Kconfig"
492 source "drivers/net/pcmcia/Kconfig"
494 source "drivers/net/wan/Kconfig"
496 source "drivers/atm/Kconfig"
498 source "drivers/ieee802154/Kconfig"
500 source "drivers/s390/net/Kconfig"
502 source "drivers/net/caif/Kconfig"
505 tristate "Tilera GBE/XGBE network driver support"
510 This is a standard Linux network device driver for the
511 on-chip Tilera Gigabit Ethernet and XAUI interfaces.
513 To compile this driver as a module, choose M here: the module
514 will be called tile_net.
516 config XEN_NETDEV_FRONTEND
517 tristate "Xen network device frontend driver"
519 select XEN_XENBUS_FRONTEND
522 This driver provides support for Xen paravirtual network
523 devices exported by a Xen network driver domain (often
526 The corresponding Linux backend driver is enabled by the
527 CONFIG_XEN_NETDEV_BACKEND option.
529 If you are compiling a kernel for use as Xen guest, you
530 should say Y here. To compile this driver as a module, chose
531 M here: the module will be called xen-netfront.
533 config XEN_NETDEV_BACKEND
534 tristate "Xen backend network device"
535 depends on XEN_BACKEND
537 This driver allows the kernel to act as a Xen network driver
538 domain which exports paravirtual network devices to other
539 Xen domains. These devices can be accessed by any operating
540 system that implements a compatible front end.
542 The corresponding Linux frontend driver is enabled by the
543 CONFIG_XEN_NETDEV_FRONTEND configuration option.
545 The backend driver presents a standard network device
546 endpoint for each paravirtual network device to the driver
547 domain network stack. These can then be bridged or routed
548 etc in order to provide full network connectivity.
550 If you are compiling a kernel to run in a Xen network driver
551 domain (often this is domain 0) you should say Y here. To
552 compile this driver as a module, chose M here: the module
553 will be called xen-netback.
556 tristate "RapidIO Ethernet over messaging driver support"
559 config RIONET_TX_SIZE
560 int "Number of outbound queue entries"
564 config RIONET_RX_SIZE
565 int "Number of inbound queue entries"
570 tristate "FDDI driver support"
571 depends on (PCI || EISA || TC)
573 Fiber Distributed Data Interface is a high speed local area network
574 design; essentially a replacement for high speed Ethernet. FDDI can
575 run over copper or fiber. If you are connected to such a network and
576 want a driver for the FDDI card in your computer, say Y here (and
577 then also Y to the driver for your FDDI card, below). Most people
581 tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
582 depends on FDDI && (PCI || EISA || TC)
584 This is support for the DIGITAL series of TURBOchannel (DEFTA),
585 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
586 to a local FDDI network.
588 To compile this driver as a module, choose M here: the module
589 will be called defxx. If unsure, say N.
593 prompt "Use MMIO instead of PIO" if PCI || EISA
595 default n if PCI || EISA
598 This instructs the driver to use EISA or PCI memory-mapped I/O
599 (MMIO) as appropriate instead of programmed I/O ports (PIO).
600 Enabling this gives an improvement in processing time in parts
601 of the driver, but it may cause problems with EISA (DEFEA)
602 adapters. TURBOchannel does not have the concept of I/O ports,
603 so MMIO is always used for these (DEFTA) adapters.
608 tristate "SysKonnect FDDI PCI support"
609 depends on FDDI && PCI
612 Say Y here if you have a SysKonnect FDDI PCI adapter.
613 The following adapters are supported by this driver:
614 - SK-5521 (SK-NET FDDI-UP)
615 - SK-5522 (SK-NET FDDI-UP DAS)
616 - SK-5541 (SK-NET FDDI-FP)
617 - SK-5543 (SK-NET FDDI-LP)
618 - SK-5544 (SK-NET FDDI-LP DAS)
619 - SK-5821 (SK-NET FDDI-UP64)
620 - SK-5822 (SK-NET FDDI-UP64 DAS)
621 - SK-5841 (SK-NET FDDI-FP64)
622 - SK-5843 (SK-NET FDDI-LP64)
623 - SK-5844 (SK-NET FDDI-LP64 DAS)
624 - Netelligent 100 FDDI DAS Fibre SC
625 - Netelligent 100 FDDI SAS Fibre SC
626 - Netelligent 100 FDDI DAS UTP
627 - Netelligent 100 FDDI SAS UTP
628 - Netelligent 100 FDDI SAS Fibre MIC
630 Read <file:Documentation/networking/skfp.txt> for information about
633 Questions concerning this driver can be addressed to:
634 <linux@syskonnect.de>
636 To compile this driver as a module, choose M here: the module
637 will be called skfp. This is recommended.
640 bool "HIPPI driver support (EXPERIMENTAL)"
641 depends on EXPERIMENTAL && INET && PCI
643 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
644 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
645 can run over copper (25m) or fiber (300m on multi-mode or 10km on
646 single-mode). HIPPI networks are commonly used for clusters and to
647 connect to super computers. If you are connected to a HIPPI network
648 and have a HIPPI network card in your computer that you want to use
649 under Linux, say Y here (you must also remember to enable the driver
650 for your HIPPI card below). Most people will say N here.
653 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
654 depends on HIPPI && PCI
656 Say Y here if this is your PCI HIPPI network card.
658 To compile this driver as a module, choose M here: the module
659 will be called rrunner. If unsure, say N.
661 config ROADRUNNER_LARGE_RINGS
662 bool "Use large TX/RX rings (EXPERIMENTAL)"
663 depends on ROADRUNNER
665 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
666 of additional memory to allow for fastest operation, both for
667 transmitting and receiving. This memory cannot be used by any other
668 kernel code or by user space programs. Say Y here only if you have
672 tristate "PLIP (parallel port) support"
675 PLIP (Parallel Line Internet Protocol) is used to create a
676 reasonably fast mini network consisting of two (or, rarely, more)
677 local machines. A PLIP link from a Linux box is a popular means to
678 install a Linux distribution on a machine which doesn't have a
679 CD-ROM drive (a minimal system has to be transferred with floppies
680 first). The kernels on both machines need to have this PLIP option
681 enabled for this to work.
683 The PLIP driver has two modes, mode 0 and mode 1. The parallel
684 ports (the connectors at the computers with 25 holes) are connected
685 with "null printer" or "Turbo Laplink" cables which can transmit 4
686 bits at a time (mode 0) or with special PLIP cables, to be used on
687 bidirectional parallel ports only, which can transmit 8 bits at a
688 time (mode 1); you can find the wiring of these cables in
689 <file:Documentation/networking/PLIP.txt>. The cables can be up to
690 15m long. Mode 0 works also if one of the machines runs DOS/Windows
691 and has some PLIP software installed, e.g. the Crynwr PLIP packet
692 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
693 and winsock or NCSA's telnet.
695 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
696 as the NET-3-HOWTO, both available from
697 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
698 protocol has been changed and this PLIP driver won't work together
699 with the PLIP support in Linux versions 1.0.x. This option enlarges
700 your kernel by about 8 KB.
702 To compile this driver as a module, choose M here. The module
703 will be called plip. If unsure, say Y or M, in case you buy
707 tristate "PPP (point-to-point protocol) support"
710 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
711 the same purpose: sending Internet traffic over telephone (and other
712 serial) lines. Ask your access provider if they support it, because
713 otherwise you can't use it; most Internet access providers these
714 days support PPP rather than SLIP.
716 To use PPP, you need an additional program called pppd as described
717 in the PPP-HOWTO, available at
718 <http://www.tldp.org/docs.html#howto>. Make sure that you have
719 the version of pppd recommended in <file:Documentation/Changes>.
720 The PPP option enlarges your kernel by about 16 KB.
722 There are actually two versions of PPP: the traditional PPP for
723 asynchronous lines, such as regular analog phone lines, and
724 synchronous PPP which can be used over digital ISDN lines for
725 example. If you want to use PPP over phone lines or other
726 asynchronous serial lines, you need to say Y (or M) here and also to
727 the next option, "PPP support for async serial ports". For PPP over
728 synchronous lines, you should say Y (or M) here and to "Support
729 synchronous PPP", below.
731 If you said Y to "Version information on all symbols" above, then
732 you cannot compile the PPP driver into the kernel; you can then only
733 compile it as a module. To compile this driver as a module, choose M
734 here. The module will be called ppp_generic.
737 bool "PPP multilink support (EXPERIMENTAL)"
738 depends on PPP && EXPERIMENTAL
740 PPP multilink is a protocol (defined in RFC 1990) which allows you
741 to combine several (logical or physical) lines into one logical PPP
742 connection, so that you can utilize your full bandwidth.
744 This has to be supported at the other end as well and you need a
745 version of the pppd daemon which understands the multilink protocol.
753 Say Y here if you want to be able to filter the packets passing over
754 PPP interfaces. This allows you to control which packets count as
755 activity (i.e. which packets will reset the idle timer or bring up
756 a demand-dialed link) and which packets are to be dropped entirely.
757 You need to say Y here if you wish to use the pass-filter and
758 active-filter options to pppd.
763 tristate "PPP support for async serial ports"
767 Say Y (or M) here if you want to be able to use PPP over standard
768 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
769 a modem (not a synchronous or ISDN modem) to contact your ISP, you
772 To compile this driver as a module, choose M here.
777 tristate "PPP support for sync tty ports"
780 Say Y (or M) here if you want to be able to use PPP over synchronous
781 (HDLC) tty devices, such as the SyncLink adapter. These devices
782 are often used for high-speed leased lines like T1/E1.
784 To compile this driver as a module, choose M here.
787 tristate "PPP Deflate compression"
792 Support for the Deflate compression method for PPP, which uses the
793 Deflate algorithm (the same algorithm that gzip uses) to compress
794 each PPP packet before it is sent over the wire. The machine at the
795 other end of the PPP link (usually your ISP) has to support the
796 Deflate compression method as well for this to be useful. Even if
797 they don't support it, it is safe to say Y here.
799 To compile this driver as a module, choose M here.
802 tristate "PPP BSD-Compress compression"
805 Support for the BSD-Compress compression method for PPP, which uses
806 the LZW compression method to compress each PPP packet before it is
807 sent over the wire. The machine at the other end of the PPP link
808 (usually your ISP) has to support the BSD-Compress compression
809 method as well for this to be useful. Even if they don't support it,
810 it is safe to say Y here.
812 The PPP Deflate compression method ("PPP Deflate compression",
813 above) is preferable to BSD-Compress, because it compresses better
816 Note that the BSD compression code will always be compiled as a
817 module; it is called bsd_comp and will show up in the directory
818 modules once you have said "make modules". If unsure, say N.
821 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
822 depends on PPP && EXPERIMENTAL
828 Support for the MPPE Encryption protocol, as employed by the
829 Microsoft Point-to-Point Tunneling Protocol.
831 See http://pptpclient.sourceforge.net/ for information on
832 configuring PPTP clients and servers to utilize this method.
835 tristate "PPP over Ethernet (EXPERIMENTAL)"
836 depends on EXPERIMENTAL && PPP
838 Support for PPP over Ethernet.
840 This driver requires the latest version of pppd from the CVS
841 repository at cvs.samba.org. Alternatively, see the
842 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
843 which contains instruction on how to use this driver (under
844 the heading "Kernel mode PPPoE").
847 tristate "PPP over IPv4 (PPTP) (EXPERIMENTAL)"
848 depends on EXPERIMENTAL && PPP && NET_IPGRE_DEMUX
850 Support for PPP over IPv4.(Point-to-Point Tunneling Protocol)
852 This driver requires pppd plugin to work in client mode or
853 modified pptpd (poptop) to work in server mode.
854 See http://accel-pptp.sourceforge.net/ for information how to
858 tristate "PPP over ATM"
859 depends on ATM && PPP
861 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
862 This implementation does not yet comply with section 8 of RFC2364,
863 which can lead to bad results if the ATM peer loses state and
864 changes its encapsulation unilaterally.
867 tristate "PPP over L2TP (EXPERIMENTAL)"
868 depends on EXPERIMENTAL && L2TP && PPP
870 Support for PPP-over-L2TP socket family. L2TP is a protocol
871 used by ISPs and enterprises to tunnel PPP traffic over UDP
872 tunnels. L2TP is replacing PPTP for VPN uses.
875 tristate "SLIP (serial line) support"
877 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
878 connect to your Internet service provider or to connect to some
879 other local Unix box or if you want to configure your Linux box as a
880 Slip/CSlip server for other people to dial in. SLIP (Serial Line
881 Internet Protocol) is a protocol used to send Internet traffic over
882 serial connections such as telephone lines or null modem cables;
883 nowadays, the protocol PPP is more commonly used for this same
886 Normally, your access provider has to support SLIP in order for you
887 to be able to use it, but there is now a SLIP emulator called SLiRP
888 around (available from
889 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
890 allows you to use SLIP over a regular dial up shell connection. If
891 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
892 NET-3-HOWTO, available from
893 <http://www.tldp.org/docs.html#howto>, explains how to
894 configure SLIP. Note that you don't need this option if you just
895 want to run term (term is a program which gives you almost full
896 Internet connectivity if you have a regular dial up shell account on
897 some Internet connected Unix computer. Read
898 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
899 support will enlarge your kernel by about 4 KB. If unsure, say N.
901 To compile this driver as a module, choose M here. The module
904 config SLIP_COMPRESSED
905 bool "CSLIP compressed headers"
909 This protocol is faster than SLIP because it uses compression on the
910 TCP/IP headers (not on the data itself), but it has to be supported
911 on both ends. Ask your access provider if you are not sure and
912 answer Y, just in case. You will still be able to use plain SLIP. If
913 you plan to use SLiRP, the SLIP emulator (available from
914 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
915 allows you to use SLIP over a regular dial up shell connection, you
916 definitely want to say Y here. The NET-3-HOWTO, available from
917 <http://www.tldp.org/docs.html#howto>, explains how to configure
918 CSLIP. This won't enlarge your kernel.
923 This option enables Van Jacobsen serial line header compression
927 bool "Keepalive and linefill"
930 Adds additional capabilities to the SLIP driver to support the
931 RELCOM line fill and keepalive monitoring. Ideal on poor quality
934 config SLIP_MODE_SLIP6
935 bool "Six bit SLIP encapsulation"
938 Just occasionally you may need to run IP over hostile serial
939 networks that don't pass all control characters or are only seven
940 bit. Saying Y here adds an extra mode you can use with SLIP:
941 "slip6". In this mode, SLIP will only send normal ASCII symbols over
942 the serial device. Naturally, this has to be supported at the other
943 end of the link as well. It's good enough, for example, to run IP
944 over the async ports of a Camtec JNT Pad. If unsure, say N.
947 bool "Fibre Channel driver support"
948 depends on SCSI && PCI
950 Fibre Channel is a high speed serial protocol mainly used to connect
951 large storage devices to the computer; it is compatible with and
952 intended to replace SCSI.
954 If you intend to use Fibre Channel, you need to have a Fibre channel
955 adaptor card in your computer; say Y here and to the driver for your
956 adaptor below. You also should have said Y to "SCSI support" and
957 "SCSI generic support".
960 tristate "Network console logging support"
962 If you want to log kernel messages over the network, enable this.
963 See <file:Documentation/networking/netconsole.txt> for details.
965 config NETCONSOLE_DYNAMIC
966 bool "Dynamic reconfiguration of logging targets"
967 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
968 !(NETCONSOLE=y && CONFIGFS_FS=m)
970 This option enables the ability to dynamically reconfigure target
971 parameters (interface, IP addresses, port numbers, MAC addresses)
972 at runtime through a userspace interface exported using configfs.
973 See <file:Documentation/networking/netconsole.txt> for details.
979 bool "Netpoll traffic trapping"
983 config NET_POLL_CONTROLLER
987 tristate "Virtio network driver (EXPERIMENTAL)"
988 depends on EXPERIMENTAL && VIRTIO
990 This is the virtual network driver for virtio. It can be used with
991 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
994 tristate "VMware VMXNET3 ethernet driver"
995 depends on PCI && INET
997 This driver supports VMware's vmxnet3 virtual ethernet NIC.
998 To compile this driver as a module, choose M here: the
999 module will be called vmxnet3.