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 tristate "OpenCores 10/100 Mbps Ethernet MAC support"
296 depends on NET_ETHERNET && HAS_IOMEM && HAS_DMA
302 Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC.
305 tristate "Aeroflex Gaisler GRETH Ethernet MAC support"
310 Say Y here if you want to use the Aeroflex Gaisler GRETH Ethernet MAC.
313 tristate "Dave ethernet support (DNET)"
314 depends on NET_ETHERNET && HAS_IOMEM
317 The Dave ethernet interface (DNET) is found on Qong Board FPGA.
318 Say Y to include support for the DNET chip.
320 To compile this driver as a module, choose M here: the module
324 bool "EISA, VLB, PCI and on board controllers"
325 depends on ISA || EISA || PCI
327 This is another class of network cards which attach directly to the
328 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
329 available from <http://www.tldp.org/docs.html#howto>.
331 Note that the answer to this question doesn't directly affect the
332 kernel: saying N will just cause the configurator to skip all
333 the questions about this class of network cards. If you say Y, you
334 will be asked for your specific card in the following questions. If
335 you are unsure, say Y.
338 bool "Pocket and portable adapters"
341 Cute little network (Ethernet) devices which attach to the parallel
342 port ("pocket adapters"), commonly used with laptops. If you have
343 one of those, say Y and read the Ethernet-HOWTO, available from
344 <http://www.tldp.org/docs.html#howto>.
346 If you want to plug a network (or some other) card into the PCMCIA
347 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
348 credit card size extension cards used by all modern laptops), you
349 need the pcmcia-cs package (location contained in the file
350 <file:Documentation/Changes>) and you can say N here.
352 Laptop users should read the Linux Laptop home page at
353 <http://www.linux-on-laptops.com/> or
354 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
356 Note that the answer to this question doesn't directly affect the
357 kernel: saying N will just cause the configurator to skip all
358 the questions about this class of network devices. If you say Y, you
359 will be asked for your specific device in the following questions.
367 menuconfig NETDEV_1000
368 bool "Ethernet (1000 Mbit)"
372 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
373 type of Local Area Network (LAN) in universities and companies.
375 Say Y here to get to see options for Gigabit Ethernet drivers.
376 This option alone does not add any kernel code.
377 Note that drivers supporting both 100 and 1000 MBit may be listed
378 under "Ethernet (10 or 100MBit)" instead.
380 If you say N, all options in this submenu will be skipped and disabled.
387 # 10 Gigabit Ethernet
390 menuconfig NETDEV_10000
391 bool "Ethernet (10000 Mbit)"
395 Say Y here to get to see options for 10 Gigabit Ethernet drivers.
396 This option alone does not add any kernel code.
398 If you say N, all options in this submenu will be skipped and disabled.
410 source "drivers/net/tokenring/Kconfig"
412 source "drivers/net/wireless/Kconfig"
414 source "drivers/net/wimax/Kconfig"
416 source "drivers/net/usb/Kconfig"
418 source "drivers/net/pcmcia/Kconfig"
420 source "drivers/net/wan/Kconfig"
422 source "drivers/atm/Kconfig"
424 source "drivers/ieee802154/Kconfig"
426 source "drivers/s390/net/Kconfig"
428 source "drivers/net/caif/Kconfig"
431 tristate "Tilera GBE/XGBE network driver support"
436 This is a standard Linux network device driver for the
437 on-chip Tilera Gigabit Ethernet and XAUI interfaces.
439 To compile this driver as a module, choose M here: the module
440 will be called tile_net.
442 config XEN_NETDEV_FRONTEND
443 tristate "Xen network device frontend driver"
445 select XEN_XENBUS_FRONTEND
448 This driver provides support for Xen paravirtual network
449 devices exported by a Xen network driver domain (often
452 The corresponding Linux backend driver is enabled by the
453 CONFIG_XEN_NETDEV_BACKEND option.
455 If you are compiling a kernel for use as Xen guest, you
456 should say Y here. To compile this driver as a module, chose
457 M here: the module will be called xen-netfront.
459 config XEN_NETDEV_BACKEND
460 tristate "Xen backend network device"
461 depends on XEN_BACKEND
463 This driver allows the kernel to act as a Xen network driver
464 domain which exports paravirtual network devices to other
465 Xen domains. These devices can be accessed by any operating
466 system that implements a compatible front end.
468 The corresponding Linux frontend driver is enabled by the
469 CONFIG_XEN_NETDEV_FRONTEND configuration option.
471 The backend driver presents a standard network device
472 endpoint for each paravirtual network device to the driver
473 domain network stack. These can then be bridged or routed
474 etc in order to provide full network connectivity.
476 If you are compiling a kernel to run in a Xen network driver
477 domain (often this is domain 0) you should say Y here. To
478 compile this driver as a module, chose M here: the module
479 will be called xen-netback.
482 tristate "RapidIO Ethernet over messaging driver support"
485 config RIONET_TX_SIZE
486 int "Number of outbound queue entries"
490 config RIONET_RX_SIZE
491 int "Number of inbound queue entries"
496 tristate "FDDI driver support"
497 depends on (PCI || EISA || TC)
499 Fiber Distributed Data Interface is a high speed local area network
500 design; essentially a replacement for high speed Ethernet. FDDI can
501 run over copper or fiber. If you are connected to such a network and
502 want a driver for the FDDI card in your computer, say Y here (and
503 then also Y to the driver for your FDDI card, below). Most people
507 tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
508 depends on FDDI && (PCI || EISA || TC)
510 This is support for the DIGITAL series of TURBOchannel (DEFTA),
511 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
512 to a local FDDI network.
514 To compile this driver as a module, choose M here: the module
515 will be called defxx. If unsure, say N.
519 prompt "Use MMIO instead of PIO" if PCI || EISA
521 default n if PCI || EISA
524 This instructs the driver to use EISA or PCI memory-mapped I/O
525 (MMIO) as appropriate instead of programmed I/O ports (PIO).
526 Enabling this gives an improvement in processing time in parts
527 of the driver, but it may cause problems with EISA (DEFEA)
528 adapters. TURBOchannel does not have the concept of I/O ports,
529 so MMIO is always used for these (DEFTA) adapters.
534 tristate "SysKonnect FDDI PCI support"
535 depends on FDDI && PCI
538 Say Y here if you have a SysKonnect FDDI PCI adapter.
539 The following adapters are supported by this driver:
540 - SK-5521 (SK-NET FDDI-UP)
541 - SK-5522 (SK-NET FDDI-UP DAS)
542 - SK-5541 (SK-NET FDDI-FP)
543 - SK-5543 (SK-NET FDDI-LP)
544 - SK-5544 (SK-NET FDDI-LP DAS)
545 - SK-5821 (SK-NET FDDI-UP64)
546 - SK-5822 (SK-NET FDDI-UP64 DAS)
547 - SK-5841 (SK-NET FDDI-FP64)
548 - SK-5843 (SK-NET FDDI-LP64)
549 - SK-5844 (SK-NET FDDI-LP64 DAS)
550 - Netelligent 100 FDDI DAS Fibre SC
551 - Netelligent 100 FDDI SAS Fibre SC
552 - Netelligent 100 FDDI DAS UTP
553 - Netelligent 100 FDDI SAS UTP
554 - Netelligent 100 FDDI SAS Fibre MIC
556 Read <file:Documentation/networking/skfp.txt> for information about
559 Questions concerning this driver can be addressed to:
560 <linux@syskonnect.de>
562 To compile this driver as a module, choose M here: the module
563 will be called skfp. This is recommended.
566 bool "HIPPI driver support (EXPERIMENTAL)"
567 depends on EXPERIMENTAL && INET && PCI
569 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
570 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
571 can run over copper (25m) or fiber (300m on multi-mode or 10km on
572 single-mode). HIPPI networks are commonly used for clusters and to
573 connect to super computers. If you are connected to a HIPPI network
574 and have a HIPPI network card in your computer that you want to use
575 under Linux, say Y here (you must also remember to enable the driver
576 for your HIPPI card below). Most people will say N here.
579 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
580 depends on HIPPI && PCI
582 Say Y here if this is your PCI HIPPI network card.
584 To compile this driver as a module, choose M here: the module
585 will be called rrunner. If unsure, say N.
587 config ROADRUNNER_LARGE_RINGS
588 bool "Use large TX/RX rings (EXPERIMENTAL)"
589 depends on ROADRUNNER
591 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
592 of additional memory to allow for fastest operation, both for
593 transmitting and receiving. This memory cannot be used by any other
594 kernel code or by user space programs. Say Y here only if you have
598 tristate "PLIP (parallel port) support"
601 PLIP (Parallel Line Internet Protocol) is used to create a
602 reasonably fast mini network consisting of two (or, rarely, more)
603 local machines. A PLIP link from a Linux box is a popular means to
604 install a Linux distribution on a machine which doesn't have a
605 CD-ROM drive (a minimal system has to be transferred with floppies
606 first). The kernels on both machines need to have this PLIP option
607 enabled for this to work.
609 The PLIP driver has two modes, mode 0 and mode 1. The parallel
610 ports (the connectors at the computers with 25 holes) are connected
611 with "null printer" or "Turbo Laplink" cables which can transmit 4
612 bits at a time (mode 0) or with special PLIP cables, to be used on
613 bidirectional parallel ports only, which can transmit 8 bits at a
614 time (mode 1); you can find the wiring of these cables in
615 <file:Documentation/networking/PLIP.txt>. The cables can be up to
616 15m long. Mode 0 works also if one of the machines runs DOS/Windows
617 and has some PLIP software installed, e.g. the Crynwr PLIP packet
618 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
619 and winsock or NCSA's telnet.
621 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
622 as the NET-3-HOWTO, both available from
623 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
624 protocol has been changed and this PLIP driver won't work together
625 with the PLIP support in Linux versions 1.0.x. This option enlarges
626 your kernel by about 8 KB.
628 To compile this driver as a module, choose M here. The module
629 will be called plip. If unsure, say Y or M, in case you buy
633 tristate "PPP (point-to-point protocol) support"
636 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
637 the same purpose: sending Internet traffic over telephone (and other
638 serial) lines. Ask your access provider if they support it, because
639 otherwise you can't use it; most Internet access providers these
640 days support PPP rather than SLIP.
642 To use PPP, you need an additional program called pppd as described
643 in the PPP-HOWTO, available at
644 <http://www.tldp.org/docs.html#howto>. Make sure that you have
645 the version of pppd recommended in <file:Documentation/Changes>.
646 The PPP option enlarges your kernel by about 16 KB.
648 There are actually two versions of PPP: the traditional PPP for
649 asynchronous lines, such as regular analog phone lines, and
650 synchronous PPP which can be used over digital ISDN lines for
651 example. If you want to use PPP over phone lines or other
652 asynchronous serial lines, you need to say Y (or M) here and also to
653 the next option, "PPP support for async serial ports". For PPP over
654 synchronous lines, you should say Y (or M) here and to "Support
655 synchronous PPP", below.
657 If you said Y to "Version information on all symbols" above, then
658 you cannot compile the PPP driver into the kernel; you can then only
659 compile it as a module. To compile this driver as a module, choose M
660 here. The module will be called ppp_generic.
663 bool "PPP multilink support (EXPERIMENTAL)"
664 depends on PPP && EXPERIMENTAL
666 PPP multilink is a protocol (defined in RFC 1990) which allows you
667 to combine several (logical or physical) lines into one logical PPP
668 connection, so that you can utilize your full bandwidth.
670 This has to be supported at the other end as well and you need a
671 version of the pppd daemon which understands the multilink protocol.
679 Say Y here if you want to be able to filter the packets passing over
680 PPP interfaces. This allows you to control which packets count as
681 activity (i.e. which packets will reset the idle timer or bring up
682 a demand-dialed link) and which packets are to be dropped entirely.
683 You need to say Y here if you wish to use the pass-filter and
684 active-filter options to pppd.
689 tristate "PPP support for async serial ports"
693 Say Y (or M) here if you want to be able to use PPP over standard
694 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
695 a modem (not a synchronous or ISDN modem) to contact your ISP, you
698 To compile this driver as a module, choose M here.
703 tristate "PPP support for sync tty ports"
706 Say Y (or M) here if you want to be able to use PPP over synchronous
707 (HDLC) tty devices, such as the SyncLink adapter. These devices
708 are often used for high-speed leased lines like T1/E1.
710 To compile this driver as a module, choose M here.
713 tristate "PPP Deflate compression"
718 Support for the Deflate compression method for PPP, which uses the
719 Deflate algorithm (the same algorithm that gzip uses) to compress
720 each PPP packet before it is sent over the wire. The machine at the
721 other end of the PPP link (usually your ISP) has to support the
722 Deflate compression method as well for this to be useful. Even if
723 they don't support it, it is safe to say Y here.
725 To compile this driver as a module, choose M here.
728 tristate "PPP BSD-Compress compression"
731 Support for the BSD-Compress compression method for PPP, which uses
732 the LZW compression method to compress each PPP packet before it is
733 sent over the wire. The machine at the other end of the PPP link
734 (usually your ISP) has to support the BSD-Compress compression
735 method as well for this to be useful. Even if they don't support it,
736 it is safe to say Y here.
738 The PPP Deflate compression method ("PPP Deflate compression",
739 above) is preferable to BSD-Compress, because it compresses better
742 Note that the BSD compression code will always be compiled as a
743 module; it is called bsd_comp and will show up in the directory
744 modules once you have said "make modules". If unsure, say N.
747 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
748 depends on PPP && EXPERIMENTAL
754 Support for the MPPE Encryption protocol, as employed by the
755 Microsoft Point-to-Point Tunneling Protocol.
757 See http://pptpclient.sourceforge.net/ for information on
758 configuring PPTP clients and servers to utilize this method.
761 tristate "PPP over Ethernet (EXPERIMENTAL)"
762 depends on EXPERIMENTAL && PPP
764 Support for PPP over Ethernet.
766 This driver requires the latest version of pppd from the CVS
767 repository at cvs.samba.org. Alternatively, see the
768 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
769 which contains instruction on how to use this driver (under
770 the heading "Kernel mode PPPoE").
773 tristate "PPP over IPv4 (PPTP) (EXPERIMENTAL)"
774 depends on EXPERIMENTAL && PPP && NET_IPGRE_DEMUX
776 Support for PPP over IPv4.(Point-to-Point Tunneling Protocol)
778 This driver requires pppd plugin to work in client mode or
779 modified pptpd (poptop) to work in server mode.
780 See http://accel-pptp.sourceforge.net/ for information how to
784 tristate "PPP over ATM"
785 depends on ATM && PPP
787 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
788 This implementation does not yet comply with section 8 of RFC2364,
789 which can lead to bad results if the ATM peer loses state and
790 changes its encapsulation unilaterally.
793 tristate "PPP over L2TP (EXPERIMENTAL)"
794 depends on EXPERIMENTAL && L2TP && PPP
796 Support for PPP-over-L2TP socket family. L2TP is a protocol
797 used by ISPs and enterprises to tunnel PPP traffic over UDP
798 tunnels. L2TP is replacing PPTP for VPN uses.
801 tristate "SLIP (serial line) support"
803 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
804 connect to your Internet service provider or to connect to some
805 other local Unix box or if you want to configure your Linux box as a
806 Slip/CSlip server for other people to dial in. SLIP (Serial Line
807 Internet Protocol) is a protocol used to send Internet traffic over
808 serial connections such as telephone lines or null modem cables;
809 nowadays, the protocol PPP is more commonly used for this same
812 Normally, your access provider has to support SLIP in order for you
813 to be able to use it, but there is now a SLIP emulator called SLiRP
814 around (available from
815 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
816 allows you to use SLIP over a regular dial up shell connection. If
817 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
818 NET-3-HOWTO, available from
819 <http://www.tldp.org/docs.html#howto>, explains how to
820 configure SLIP. Note that you don't need this option if you just
821 want to run term (term is a program which gives you almost full
822 Internet connectivity if you have a regular dial up shell account on
823 some Internet connected Unix computer. Read
824 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
825 support will enlarge your kernel by about 4 KB. If unsure, say N.
827 To compile this driver as a module, choose M here. The module
830 config SLIP_COMPRESSED
831 bool "CSLIP compressed headers"
835 This protocol is faster than SLIP because it uses compression on the
836 TCP/IP headers (not on the data itself), but it has to be supported
837 on both ends. Ask your access provider if you are not sure and
838 answer Y, just in case. You will still be able to use plain SLIP. If
839 you plan to use SLiRP, the SLIP emulator (available from
840 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
841 allows you to use SLIP over a regular dial up shell connection, you
842 definitely want to say Y here. The NET-3-HOWTO, available from
843 <http://www.tldp.org/docs.html#howto>, explains how to configure
844 CSLIP. This won't enlarge your kernel.
849 This option enables Van Jacobsen serial line header compression
853 bool "Keepalive and linefill"
856 Adds additional capabilities to the SLIP driver to support the
857 RELCOM line fill and keepalive monitoring. Ideal on poor quality
860 config SLIP_MODE_SLIP6
861 bool "Six bit SLIP encapsulation"
864 Just occasionally you may need to run IP over hostile serial
865 networks that don't pass all control characters or are only seven
866 bit. Saying Y here adds an extra mode you can use with SLIP:
867 "slip6". In this mode, SLIP will only send normal ASCII symbols over
868 the serial device. Naturally, this has to be supported at the other
869 end of the link as well. It's good enough, for example, to run IP
870 over the async ports of a Camtec JNT Pad. If unsure, say N.
873 bool "Fibre Channel driver support"
874 depends on SCSI && PCI
876 Fibre Channel is a high speed serial protocol mainly used to connect
877 large storage devices to the computer; it is compatible with and
878 intended to replace SCSI.
880 If you intend to use Fibre Channel, you need to have a Fibre channel
881 adaptor card in your computer; say Y here and to the driver for your
882 adaptor below. You also should have said Y to "SCSI support" and
883 "SCSI generic support".
886 tristate "Network console logging support"
888 If you want to log kernel messages over the network, enable this.
889 See <file:Documentation/networking/netconsole.txt> for details.
891 config NETCONSOLE_DYNAMIC
892 bool "Dynamic reconfiguration of logging targets"
893 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
894 !(NETCONSOLE=y && CONFIGFS_FS=m)
896 This option enables the ability to dynamically reconfigure target
897 parameters (interface, IP addresses, port numbers, MAC addresses)
898 at runtime through a userspace interface exported using configfs.
899 See <file:Documentation/networking/netconsole.txt> for details.
905 bool "Netpoll traffic trapping"
909 config NET_POLL_CONTROLLER
913 tristate "Virtio network driver (EXPERIMENTAL)"
914 depends on EXPERIMENTAL && VIRTIO
916 This is the virtual network driver for virtio. It can be used with
917 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
920 tristate "VMware VMXNET3 ethernet driver"
921 depends on PCI && INET
923 This driver supports VMware's vmxnet3 virtual ethernet NIC.
924 To compile this driver as a module, choose M here: the
925 module will be called vmxnet3.