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 "Korina (IDT RC32434) Ethernet support"
242 depends on NET_ETHERNET && MIKROTIK_RB532
244 If you have a Mikrotik RouterBoard 500 or IDT RC32434
245 based system say Y. Otherwise say N.
248 tristate "MIPS simulator Network device"
251 The MIPSNET device is a simple Ethernet network device which is
252 emulated by the MIPS Simulator.
253 If you are not using a MIPSsim or are unsure, say N.
256 tristate "Renesas SuperH Ethernet support"
257 depends on SUPERH && \
258 (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712 || \
259 CPU_SUBTYPE_SH7763 || CPU_SUBTYPE_SH7619 || \
260 CPU_SUBTYPE_SH7724 || CPU_SUBTYPE_SH7757)
266 Renesas SuperH Ethernet device driver.
267 This driver supporting CPUs are:
268 - SH7710, SH7712, SH7763, SH7619, SH7724, and SH7757.
271 tristate "Blackfin on-chip MAC support"
272 depends on NET_ETHERNET && (BF516 || BF518 || BF526 || BF527 || BF536 || BF537)
276 select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE
278 This is the driver for Blackfin on-chip mac device. Say Y if you want it
279 compiled into the kernel. This driver is also available as a module
280 ( = code which can be inserted in and removed from the running kernel
281 whenever you want). The module will be called bfin_mac.
283 config BFIN_MAC_USE_L1
284 bool "Use L1 memory for rx/tx packets"
285 depends on BFIN_MAC && (BF527 || BF537)
288 To get maximum network performance, you should use L1 memory as rx/tx buffers.
289 Say N here if you want to reserve L1 memory for other uses.
291 config BFIN_TX_DESC_NUM
292 int "Number of transmit buffer packets"
294 range 6 10 if BFIN_MAC_USE_L1
298 Set the number of buffer packets used in driver.
300 config BFIN_RX_DESC_NUM
301 int "Number of receive buffer packets"
303 range 20 100 if BFIN_MAC_USE_L1
307 Set the number of buffer packets used in driver.
309 config BFIN_MAC_USE_HWSTAMP
310 bool "Use IEEE 1588 hwstamp"
311 depends on BFIN_MAC && BF518
314 To support the IEEE 1588 Precision Time Protocol (PTP), select y here
317 tristate "NetX Ethernet support"
321 This is support for the Hilscher netX builtin Ethernet ports
323 To compile this driver as a module, choose M here. The module
324 will be called netx-eth.
327 tristate "DM9000 support"
328 depends on ARM || BLACKFIN || MIPS
332 Support for DM9000 chipset.
334 To compile this driver as a module, choose M here. The module
335 will be called dm9000.
337 config DM9000_DEBUGLEVEL
338 int "DM9000 maximum debug level"
342 The maximum level of debugging code compiled into the DM9000
345 config DM9000_FORCE_SIMPLE_PHY_POLL
346 bool "Force simple NSR based PHY polling"
349 This configuration forces the DM9000 to use the NSR's LinkStatus
350 bit to determine if the link is up or down instead of the more
351 costly MII PHY reads. Note, this will not work if the chip is
352 operating with an external PHY.
355 tristate "ENC28J60 support"
356 depends on EXPERIMENTAL && SPI && NET_ETHERNET
359 Support for the Microchip EN28J60 ethernet chip.
361 To compile this driver as a module, choose M here. The module will be
364 config ENC28J60_WRITEVERIFY
365 bool "Enable write verify"
368 Enable the verify after the buffer write useful for debugging purpose.
372 tristate "OpenCores 10/100 Mbps Ethernet MAC support"
373 depends on NET_ETHERNET && HAS_IOMEM && HAS_DMA
379 Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC.
382 tristate "Aeroflex Gaisler GRETH Ethernet MAC support"
387 Say Y here if you want to use the Aeroflex Gaisler GRETH Ethernet MAC.
390 tristate "Dave ethernet support (DNET)"
391 depends on NET_ETHERNET && HAS_IOMEM
394 The Dave ethernet interface (DNET) is found on Qong Board FPGA.
395 Say Y to include support for the DNET chip.
397 To compile this driver as a module, choose M here: the module
401 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
402 depends on ISA || EISA || PCI
404 If you have a network (Ethernet) card of this type, say Y and read
405 the Ethernet-HOWTO, available from
406 <http://www.tldp.org/docs.html#howto>.
408 To compile this driver as a module, choose M here. The module
409 will be called hp100.
412 bool "EISA, VLB, PCI and on board controllers"
413 depends on ISA || EISA || PCI
415 This is another class of network cards which attach directly to the
416 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
417 available from <http://www.tldp.org/docs.html#howto>.
419 Note that the answer to this question doesn't directly affect the
420 kernel: saying N will just cause the configurator to skip all
421 the questions about this class of network cards. If you say Y, you
422 will be asked for your specific card in the following questions. If
423 you are unsure, say Y.
425 config ADAPTEC_STARFIRE
426 tristate "Adaptec Starfire/DuraLAN support"
427 depends on NET_PCI && PCI
431 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
432 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
433 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
436 To compile this driver as a module, choose M here: the module
437 will be called starfire. This is recommended.
440 tristate "nForce Ethernet support"
441 depends on NET_PCI && PCI
443 If you have a network (Ethernet) controller of this type, say Y and
444 read the Ethernet-HOWTO, available from
445 <http://www.tldp.org/docs.html#howto>.
447 To compile this driver as a module, choose M here. The module
448 will be called forcedeth.
451 tristate "Myson MTD-8xx PCI Ethernet support"
452 depends on NET_PCI && PCI
456 Say Y here to support the Myson MTD-800 family of PCI-based Ethernet
457 cards. <http://www.myson.com.tw/>
460 tristate "RDC R6040 Fast Ethernet Adapter support"
461 depends on NET_PCI && PCI
466 This is a driver for the R6040 Fast Ethernet MACs found in the
467 the RDC R-321x System-on-chips.
469 To compile this driver as a module, choose M here: the module
470 will be called r6040. This is recommended.
473 bool "Pocket and portable adapters"
476 Cute little network (Ethernet) devices which attach to the parallel
477 port ("pocket adapters"), commonly used with laptops. If you have
478 one of those, say Y and read the Ethernet-HOWTO, available from
479 <http://www.tldp.org/docs.html#howto>.
481 If you want to plug a network (or some other) card into the PCMCIA
482 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
483 credit card size extension cards used by all modern laptops), you
484 need the pcmcia-cs package (location contained in the file
485 <file:Documentation/Changes>) and you can say N here.
487 Laptop users should read the Linux Laptop home page at
488 <http://www.linux-on-laptops.com/> or
489 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
491 Note that the answer to this question doesn't directly affect the
492 kernel: saying N will just cause the configurator to skip all
493 the questions about this class of network devices. If you say Y, you
494 will be asked for your specific device in the following questions.
497 tristate "Lantiq SoC ETOP driver"
498 depends on SOC_TYPE_XWAY
500 Support for the MII0 inside the Lantiq SoC
508 menuconfig NETDEV_1000
509 bool "Ethernet (1000 Mbit)"
513 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
514 type of Local Area Network (LAN) in universities and companies.
516 Say Y here to get to see options for Gigabit Ethernet drivers.
517 This option alone does not add any kernel code.
518 Note that drivers supporting both 100 and 1000 MBit may be listed
519 under "Ethernet (10 or 100MBit)" instead.
521 If you say N, all options in this submenu will be skipped and disabled.
526 tristate "IP1000 Gigabit Ethernet support"
527 depends on PCI && EXPERIMENTAL
530 This driver supports IP1000 gigabit Ethernet cards.
532 To compile this driver as a module, choose M here: the module
533 will be called ipg. This is recommended.
538 # 10 Gigabit Ethernet
541 menuconfig NETDEV_10000
542 bool "Ethernet (10000 Mbit)"
546 Say Y here to get to see options for 10 Gigabit Ethernet drivers.
547 This option alone does not add any kernel code.
549 If you say N, all options in this submenu will be skipped and disabled.
561 source "drivers/net/tokenring/Kconfig"
563 source "drivers/net/wireless/Kconfig"
565 source "drivers/net/wimax/Kconfig"
567 source "drivers/net/usb/Kconfig"
569 source "drivers/net/pcmcia/Kconfig"
571 source "drivers/net/wan/Kconfig"
573 source "drivers/atm/Kconfig"
575 source "drivers/ieee802154/Kconfig"
577 source "drivers/s390/net/Kconfig"
579 source "drivers/net/caif/Kconfig"
582 tristate "Tilera GBE/XGBE network driver support"
587 This is a standard Linux network device driver for the
588 on-chip Tilera Gigabit Ethernet and XAUI interfaces.
590 To compile this driver as a module, choose M here: the module
591 will be called tile_net.
593 config XEN_NETDEV_FRONTEND
594 tristate "Xen network device frontend driver"
596 select XEN_XENBUS_FRONTEND
599 This driver provides support for Xen paravirtual network
600 devices exported by a Xen network driver domain (often
603 The corresponding Linux backend driver is enabled by the
604 CONFIG_XEN_NETDEV_BACKEND option.
606 If you are compiling a kernel for use as Xen guest, you
607 should say Y here. To compile this driver as a module, chose
608 M here: the module will be called xen-netfront.
610 config XEN_NETDEV_BACKEND
611 tristate "Xen backend network device"
612 depends on XEN_BACKEND
614 This driver allows the kernel to act as a Xen network driver
615 domain which exports paravirtual network devices to other
616 Xen domains. These devices can be accessed by any operating
617 system that implements a compatible front end.
619 The corresponding Linux frontend driver is enabled by the
620 CONFIG_XEN_NETDEV_FRONTEND configuration option.
622 The backend driver presents a standard network device
623 endpoint for each paravirtual network device to the driver
624 domain network stack. These can then be bridged or routed
625 etc in order to provide full network connectivity.
627 If you are compiling a kernel to run in a Xen network driver
628 domain (often this is domain 0) you should say Y here. To
629 compile this driver as a module, chose M here: the module
630 will be called xen-netback.
633 tristate "RapidIO Ethernet over messaging driver support"
636 config RIONET_TX_SIZE
637 int "Number of outbound queue entries"
641 config RIONET_RX_SIZE
642 int "Number of inbound queue entries"
647 tristate "FDDI driver support"
648 depends on (PCI || EISA || TC)
650 Fiber Distributed Data Interface is a high speed local area network
651 design; essentially a replacement for high speed Ethernet. FDDI can
652 run over copper or fiber. If you are connected to such a network and
653 want a driver for the FDDI card in your computer, say Y here (and
654 then also Y to the driver for your FDDI card, below). Most people
658 tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
659 depends on FDDI && (PCI || EISA || TC)
661 This is support for the DIGITAL series of TURBOchannel (DEFTA),
662 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
663 to a local FDDI network.
665 To compile this driver as a module, choose M here: the module
666 will be called defxx. If unsure, say N.
670 prompt "Use MMIO instead of PIO" if PCI || EISA
672 default n if PCI || EISA
675 This instructs the driver to use EISA or PCI memory-mapped I/O
676 (MMIO) as appropriate instead of programmed I/O ports (PIO).
677 Enabling this gives an improvement in processing time in parts
678 of the driver, but it may cause problems with EISA (DEFEA)
679 adapters. TURBOchannel does not have the concept of I/O ports,
680 so MMIO is always used for these (DEFTA) adapters.
685 tristate "SysKonnect FDDI PCI support"
686 depends on FDDI && PCI
689 Say Y here if you have a SysKonnect FDDI PCI adapter.
690 The following adapters are supported by this driver:
691 - SK-5521 (SK-NET FDDI-UP)
692 - SK-5522 (SK-NET FDDI-UP DAS)
693 - SK-5541 (SK-NET FDDI-FP)
694 - SK-5543 (SK-NET FDDI-LP)
695 - SK-5544 (SK-NET FDDI-LP DAS)
696 - SK-5821 (SK-NET FDDI-UP64)
697 - SK-5822 (SK-NET FDDI-UP64 DAS)
698 - SK-5841 (SK-NET FDDI-FP64)
699 - SK-5843 (SK-NET FDDI-LP64)
700 - SK-5844 (SK-NET FDDI-LP64 DAS)
701 - Netelligent 100 FDDI DAS Fibre SC
702 - Netelligent 100 FDDI SAS Fibre SC
703 - Netelligent 100 FDDI DAS UTP
704 - Netelligent 100 FDDI SAS UTP
705 - Netelligent 100 FDDI SAS Fibre MIC
707 Read <file:Documentation/networking/skfp.txt> for information about
710 Questions concerning this driver can be addressed to:
711 <linux@syskonnect.de>
713 To compile this driver as a module, choose M here: the module
714 will be called skfp. This is recommended.
717 bool "HIPPI driver support (EXPERIMENTAL)"
718 depends on EXPERIMENTAL && INET && PCI
720 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
721 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
722 can run over copper (25m) or fiber (300m on multi-mode or 10km on
723 single-mode). HIPPI networks are commonly used for clusters and to
724 connect to super computers. If you are connected to a HIPPI network
725 and have a HIPPI network card in your computer that you want to use
726 under Linux, say Y here (you must also remember to enable the driver
727 for your HIPPI card below). Most people will say N here.
730 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
731 depends on HIPPI && PCI
733 Say Y here if this is your PCI HIPPI network card.
735 To compile this driver as a module, choose M here: the module
736 will be called rrunner. If unsure, say N.
738 config ROADRUNNER_LARGE_RINGS
739 bool "Use large TX/RX rings (EXPERIMENTAL)"
740 depends on ROADRUNNER
742 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
743 of additional memory to allow for fastest operation, both for
744 transmitting and receiving. This memory cannot be used by any other
745 kernel code or by user space programs. Say Y here only if you have
749 tristate "PLIP (parallel port) support"
752 PLIP (Parallel Line Internet Protocol) is used to create a
753 reasonably fast mini network consisting of two (or, rarely, more)
754 local machines. A PLIP link from a Linux box is a popular means to
755 install a Linux distribution on a machine which doesn't have a
756 CD-ROM drive (a minimal system has to be transferred with floppies
757 first). The kernels on both machines need to have this PLIP option
758 enabled for this to work.
760 The PLIP driver has two modes, mode 0 and mode 1. The parallel
761 ports (the connectors at the computers with 25 holes) are connected
762 with "null printer" or "Turbo Laplink" cables which can transmit 4
763 bits at a time (mode 0) or with special PLIP cables, to be used on
764 bidirectional parallel ports only, which can transmit 8 bits at a
765 time (mode 1); you can find the wiring of these cables in
766 <file:Documentation/networking/PLIP.txt>. The cables can be up to
767 15m long. Mode 0 works also if one of the machines runs DOS/Windows
768 and has some PLIP software installed, e.g. the Crynwr PLIP packet
769 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
770 and winsock or NCSA's telnet.
772 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
773 as the NET-3-HOWTO, both available from
774 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
775 protocol has been changed and this PLIP driver won't work together
776 with the PLIP support in Linux versions 1.0.x. This option enlarges
777 your kernel by about 8 KB.
779 To compile this driver as a module, choose M here. The module
780 will be called plip. If unsure, say Y or M, in case you buy
784 tristate "PPP (point-to-point protocol) support"
787 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
788 the same purpose: sending Internet traffic over telephone (and other
789 serial) lines. Ask your access provider if they support it, because
790 otherwise you can't use it; most Internet access providers these
791 days support PPP rather than SLIP.
793 To use PPP, you need an additional program called pppd as described
794 in the PPP-HOWTO, available at
795 <http://www.tldp.org/docs.html#howto>. Make sure that you have
796 the version of pppd recommended in <file:Documentation/Changes>.
797 The PPP option enlarges your kernel by about 16 KB.
799 There are actually two versions of PPP: the traditional PPP for
800 asynchronous lines, such as regular analog phone lines, and
801 synchronous PPP which can be used over digital ISDN lines for
802 example. If you want to use PPP over phone lines or other
803 asynchronous serial lines, you need to say Y (or M) here and also to
804 the next option, "PPP support for async serial ports". For PPP over
805 synchronous lines, you should say Y (or M) here and to "Support
806 synchronous PPP", below.
808 If you said Y to "Version information on all symbols" above, then
809 you cannot compile the PPP driver into the kernel; you can then only
810 compile it as a module. To compile this driver as a module, choose M
811 here. The module will be called ppp_generic.
814 bool "PPP multilink support (EXPERIMENTAL)"
815 depends on PPP && EXPERIMENTAL
817 PPP multilink is a protocol (defined in RFC 1990) which allows you
818 to combine several (logical or physical) lines into one logical PPP
819 connection, so that you can utilize your full bandwidth.
821 This has to be supported at the other end as well and you need a
822 version of the pppd daemon which understands the multilink protocol.
830 Say Y here if you want to be able to filter the packets passing over
831 PPP interfaces. This allows you to control which packets count as
832 activity (i.e. which packets will reset the idle timer or bring up
833 a demand-dialed link) and which packets are to be dropped entirely.
834 You need to say Y here if you wish to use the pass-filter and
835 active-filter options to pppd.
840 tristate "PPP support for async serial ports"
844 Say Y (or M) here if you want to be able to use PPP over standard
845 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
846 a modem (not a synchronous or ISDN modem) to contact your ISP, you
849 To compile this driver as a module, choose M here.
854 tristate "PPP support for sync tty ports"
857 Say Y (or M) here if you want to be able to use PPP over synchronous
858 (HDLC) tty devices, such as the SyncLink adapter. These devices
859 are often used for high-speed leased lines like T1/E1.
861 To compile this driver as a module, choose M here.
864 tristate "PPP Deflate compression"
869 Support for the Deflate compression method for PPP, which uses the
870 Deflate algorithm (the same algorithm that gzip uses) to compress
871 each PPP packet before it is sent over the wire. The machine at the
872 other end of the PPP link (usually your ISP) has to support the
873 Deflate compression method as well for this to be useful. Even if
874 they don't support it, it is safe to say Y here.
876 To compile this driver as a module, choose M here.
879 tristate "PPP BSD-Compress compression"
882 Support for the BSD-Compress compression method for PPP, which uses
883 the LZW compression method to compress each PPP packet before it is
884 sent over the wire. The machine at the other end of the PPP link
885 (usually your ISP) has to support the BSD-Compress compression
886 method as well for this to be useful. Even if they don't support it,
887 it is safe to say Y here.
889 The PPP Deflate compression method ("PPP Deflate compression",
890 above) is preferable to BSD-Compress, because it compresses better
893 Note that the BSD compression code will always be compiled as a
894 module; it is called bsd_comp and will show up in the directory
895 modules once you have said "make modules". If unsure, say N.
898 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
899 depends on PPP && EXPERIMENTAL
905 Support for the MPPE Encryption protocol, as employed by the
906 Microsoft Point-to-Point Tunneling Protocol.
908 See http://pptpclient.sourceforge.net/ for information on
909 configuring PPTP clients and servers to utilize this method.
912 tristate "PPP over Ethernet (EXPERIMENTAL)"
913 depends on EXPERIMENTAL && PPP
915 Support for PPP over Ethernet.
917 This driver requires the latest version of pppd from the CVS
918 repository at cvs.samba.org. Alternatively, see the
919 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
920 which contains instruction on how to use this driver (under
921 the heading "Kernel mode PPPoE").
924 tristate "PPP over IPv4 (PPTP) (EXPERIMENTAL)"
925 depends on EXPERIMENTAL && PPP && NET_IPGRE_DEMUX
927 Support for PPP over IPv4.(Point-to-Point Tunneling Protocol)
929 This driver requires pppd plugin to work in client mode or
930 modified pptpd (poptop) to work in server mode.
931 See http://accel-pptp.sourceforge.net/ for information how to
935 tristate "PPP over ATM"
936 depends on ATM && PPP
938 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
939 This implementation does not yet comply with section 8 of RFC2364,
940 which can lead to bad results if the ATM peer loses state and
941 changes its encapsulation unilaterally.
944 tristate "PPP over L2TP (EXPERIMENTAL)"
945 depends on EXPERIMENTAL && L2TP && PPP
947 Support for PPP-over-L2TP socket family. L2TP is a protocol
948 used by ISPs and enterprises to tunnel PPP traffic over UDP
949 tunnels. L2TP is replacing PPTP for VPN uses.
952 tristate "SLIP (serial line) support"
954 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
955 connect to your Internet service provider or to connect to some
956 other local Unix box or if you want to configure your Linux box as a
957 Slip/CSlip server for other people to dial in. SLIP (Serial Line
958 Internet Protocol) is a protocol used to send Internet traffic over
959 serial connections such as telephone lines or null modem cables;
960 nowadays, the protocol PPP is more commonly used for this same
963 Normally, your access provider has to support SLIP in order for you
964 to be able to use it, but there is now a SLIP emulator called SLiRP
965 around (available from
966 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
967 allows you to use SLIP over a regular dial up shell connection. If
968 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
969 NET-3-HOWTO, available from
970 <http://www.tldp.org/docs.html#howto>, explains how to
971 configure SLIP. Note that you don't need this option if you just
972 want to run term (term is a program which gives you almost full
973 Internet connectivity if you have a regular dial up shell account on
974 some Internet connected Unix computer. Read
975 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
976 support will enlarge your kernel by about 4 KB. If unsure, say N.
978 To compile this driver as a module, choose M here. The module
981 config SLIP_COMPRESSED
982 bool "CSLIP compressed headers"
986 This protocol is faster than SLIP because it uses compression on the
987 TCP/IP headers (not on the data itself), but it has to be supported
988 on both ends. Ask your access provider if you are not sure and
989 answer Y, just in case. You will still be able to use plain SLIP. If
990 you plan to use SLiRP, the SLIP emulator (available from
991 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
992 allows you to use SLIP over a regular dial up shell connection, you
993 definitely want to say Y here. The NET-3-HOWTO, available from
994 <http://www.tldp.org/docs.html#howto>, explains how to configure
995 CSLIP. This won't enlarge your kernel.
1000 This option enables Van Jacobsen serial line header compression
1004 bool "Keepalive and linefill"
1007 Adds additional capabilities to the SLIP driver to support the
1008 RELCOM line fill and keepalive monitoring. Ideal on poor quality
1011 config SLIP_MODE_SLIP6
1012 bool "Six bit SLIP encapsulation"
1015 Just occasionally you may need to run IP over hostile serial
1016 networks that don't pass all control characters or are only seven
1017 bit. Saying Y here adds an extra mode you can use with SLIP:
1018 "slip6". In this mode, SLIP will only send normal ASCII symbols over
1019 the serial device. Naturally, this has to be supported at the other
1020 end of the link as well. It's good enough, for example, to run IP
1021 over the async ports of a Camtec JNT Pad. If unsure, say N.
1024 bool "Fibre Channel driver support"
1025 depends on SCSI && PCI
1027 Fibre Channel is a high speed serial protocol mainly used to connect
1028 large storage devices to the computer; it is compatible with and
1029 intended to replace SCSI.
1031 If you intend to use Fibre Channel, you need to have a Fibre channel
1032 adaptor card in your computer; say Y here and to the driver for your
1033 adaptor below. You also should have said Y to "SCSI support" and
1034 "SCSI generic support".
1037 tristate "Network console logging support"
1039 If you want to log kernel messages over the network, enable this.
1040 See <file:Documentation/networking/netconsole.txt> for details.
1042 config NETCONSOLE_DYNAMIC
1043 bool "Dynamic reconfiguration of logging targets"
1044 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
1045 !(NETCONSOLE=y && CONFIGFS_FS=m)
1047 This option enables the ability to dynamically reconfigure target
1048 parameters (interface, IP addresses, port numbers, MAC addresses)
1049 at runtime through a userspace interface exported using configfs.
1050 See <file:Documentation/networking/netconsole.txt> for details.
1056 bool "Netpoll traffic trapping"
1060 config NET_POLL_CONTROLLER
1064 tristate "Virtio network driver (EXPERIMENTAL)"
1065 depends on EXPERIMENTAL && VIRTIO
1067 This is the virtual network driver for virtio. It can be used with
1068 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
1071 tristate "VMware VMXNET3 ethernet driver"
1072 depends on PCI && INET
1074 This driver supports VMware's vmxnet3 virtual ethernet NIC.
1075 To compile this driver as a module, choose M here: the
1076 module will be called vmxnet3.