Kconfig revision cdd80bd4eece6109c15864e776b83c88c3bd891b
1# 2# Network device configuration 3# 4 5menuconfig NETDEVICES 6 default y if UML 7 depends on NET 8 bool "Network device support" 9 ---help--- 10 You can say N here if you don't intend to connect your Linux box to 11 any other computer at all. 12 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. 18 19 See also "The Linux Network Administrator's Guide" by Olaf Kirch and 20 Terry Dawson. Available at <http://www.tldp.org/guides.html>. 21 22 If unsure, say Y. 23 24# All the following symbols are dependent on NETDEVICES - do not repeat 25# that for each of the symbols. 26if NETDEVICES 27 28config IFB 29 tristate "Intermediate Functional Block support" 30 depends on NET_CLS_ACT 31 ---help--- 32 This is an intermediate driver that allows sharing of 33 resources. 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', 38 'ifb1' etc. 39 Look at the iproute2 documentation directory for usage etc 40 41config DUMMY 42 tristate "Dummy net driver support" 43 ---help--- 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>. 53 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', 58 'dummy1' etc. 59 60config BONDING 61 tristate "Bonding driver support" 62 depends on INET 63 depends on IPV6 || IPV6=n 64 ---help--- 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. 68 69 The driver supports multiple bonding modes to allow for both high 70 performance and high availability operation. 71 72 Refer to <file:Documentation/networking/bonding.txt> for more 73 information. 74 75 To compile this driver as a module, choose M here: the module 76 will be called bonding. 77 78config MACVLAN 79 tristate "MAC-VLAN support (EXPERIMENTAL)" 80 depends on EXPERIMENTAL 81 ---help--- 82 This allows one to create virtual interfaces that map packets to 83 or from specific MAC addresses to a particular interface. 84 85 Macvlan devices can be added using the "ip" command from the 86 iproute2 package starting with the iproute2-2.6.23 release: 87 88 "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan" 89 90 To compile this driver as a module, choose M here: the module 91 will be called macvlan. 92 93config MACVTAP 94 tristate "MAC-VLAN based tap driver (EXPERIMENTAL)" 95 depends on MACVLAN 96 help 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. 101 102 To compile this driver as a module, choose M here: the module 103 will be called macvtap. 104 105config EQUALIZER 106 tristate "EQL (serial line load balancing) support" 107 ---help--- 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. 115 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>. 120 121 To compile this driver as a module, choose M here: the module 122 will be called eql. If unsure, say N. 123 124config TUN 125 tristate "Universal TUN/TAP device driver support" 126 select CRC32 127 ---help--- 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. 133 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. 138 139 Please read <file:Documentation/networking/tuntap.txt> for more 140 information. 141 142 To compile this driver as a module, choose M here: the module 143 will be called tun. 144 145 If you don't know what to use this for, you don't need it. 146 147config VETH 148 tristate "Virtual ethernet pair device" 149 ---help--- 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 152 versa. 153 154config NET_SB1000 155 tristate "General Instruments Surfboard 1000" 156 depends on PNP 157 ---help--- 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. 164 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 170 found at: 171 172 <http://www.jacksonville.net/~fventuri/> 173 <http://home.adelphia.net/~siglercm/sb1000.html> 174 <http://linuxpower.cx/~cable/> 175 176 If you don't have this card, of course say N. 177 178source "drivers/net/arcnet/Kconfig" 179 180config MII 181 tristate "Generic Media Independent Interface device support" 182 help 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. 186 187source "drivers/net/phy/Kconfig" 188 189# 190# Ethernet 191# 192 193source "drivers/net/ethernet/Kconfig" 194 195menuconfig NET_ETHERNET 196 bool "Ethernet (10 or 100Mbit)" 197 depends on !UML 198 ---help--- 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. 201 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). 211 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. 217 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. 221 222if NET_ETHERNET 223 224config NET_PCI 225 bool "EISA, VLB, PCI and on board controllers" 226 depends on ISA || EISA || PCI 227 help 228 This is another class of network cards which attach directly to the 229 bus. If you have one of those, say Y and read the Ethernet-HOWTO, 230 available from <http://www.tldp.org/docs.html#howto>. 231 232 Note that the answer to this question doesn't directly affect the 233 kernel: saying N will just cause the configurator to skip all 234 the questions about this class of network cards. If you say Y, you 235 will be asked for your specific card in the following questions. If 236 you are unsure, say Y. 237 238config NET_POCKET 239 bool "Pocket and portable adapters" 240 depends on PARPORT 241 ---help--- 242 Cute little network (Ethernet) devices which attach to the parallel 243 port ("pocket adapters"), commonly used with laptops. If you have 244 one of those, say Y and read the Ethernet-HOWTO, available from 245 <http://www.tldp.org/docs.html#howto>. 246 247 If you want to plug a network (or some other) card into the PCMCIA 248 (or PC-card) slot of your laptop instead (PCMCIA is the standard for 249 credit card size extension cards used by all modern laptops), you 250 need the pcmcia-cs package (location contained in the file 251 <file:Documentation/Changes>) and you can say N here. 252 253 Laptop users should read the Linux Laptop home page at 254 <http://www.linux-on-laptops.com/> or 255 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>. 256 257 Note that the answer to this question doesn't directly affect the 258 kernel: saying N will just cause the configurator to skip all 259 the questions about this class of network devices. If you say Y, you 260 will be asked for your specific device in the following questions. 261 262endif # NET_ETHERNET 263 264# 265# Gigabit Ethernet 266# 267 268menuconfig NETDEV_1000 269 bool "Ethernet (1000 Mbit)" 270 depends on !UML 271 default y 272 ---help--- 273 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common 274 type of Local Area Network (LAN) in universities and companies. 275 276 Say Y here to get to see options for Gigabit Ethernet drivers. 277 This option alone does not add any kernel code. 278 Note that drivers supporting both 100 and 1000 MBit may be listed 279 under "Ethernet (10 or 100MBit)" instead. 280 281 If you say N, all options in this submenu will be skipped and disabled. 282 283if NETDEV_1000 284 285endif # NETDEV_1000 286 287# 288# 10 Gigabit Ethernet 289# 290 291menuconfig NETDEV_10000 292 bool "Ethernet (10000 Mbit)" 293 depends on !UML 294 default y 295 ---help--- 296 Say Y here to get to see options for 10 Gigabit Ethernet drivers. 297 This option alone does not add any kernel code. 298 299 If you say N, all options in this submenu will be skipped and disabled. 300 301if NETDEV_10000 302 303config MDIO 304 tristate 305 306config SUNGEM_PHY 307 tristate 308 309endif # NETDEV_10000 310 311source "drivers/net/tokenring/Kconfig" 312 313source "drivers/net/wireless/Kconfig" 314 315source "drivers/net/wimax/Kconfig" 316 317source "drivers/net/usb/Kconfig" 318 319source "drivers/net/pcmcia/Kconfig" 320 321source "drivers/net/wan/Kconfig" 322 323source "drivers/atm/Kconfig" 324 325source "drivers/ieee802154/Kconfig" 326 327source "drivers/s390/net/Kconfig" 328 329source "drivers/net/caif/Kconfig" 330 331config XEN_NETDEV_FRONTEND 332 tristate "Xen network device frontend driver" 333 depends on XEN 334 select XEN_XENBUS_FRONTEND 335 default y 336 help 337 This driver provides support for Xen paravirtual network 338 devices exported by a Xen network driver domain (often 339 domain 0). 340 341 The corresponding Linux backend driver is enabled by the 342 CONFIG_XEN_NETDEV_BACKEND option. 343 344 If you are compiling a kernel for use as Xen guest, you 345 should say Y here. To compile this driver as a module, chose 346 M here: the module will be called xen-netfront. 347 348config XEN_NETDEV_BACKEND 349 tristate "Xen backend network device" 350 depends on XEN_BACKEND 351 help 352 This driver allows the kernel to act as a Xen network driver 353 domain which exports paravirtual network devices to other 354 Xen domains. These devices can be accessed by any operating 355 system that implements a compatible front end. 356 357 The corresponding Linux frontend driver is enabled by the 358 CONFIG_XEN_NETDEV_FRONTEND configuration option. 359 360 The backend driver presents a standard network device 361 endpoint for each paravirtual network device to the driver 362 domain network stack. These can then be bridged or routed 363 etc in order to provide full network connectivity. 364 365 If you are compiling a kernel to run in a Xen network driver 366 domain (often this is domain 0) you should say Y here. To 367 compile this driver as a module, chose M here: the module 368 will be called xen-netback. 369 370config RIONET 371 tristate "RapidIO Ethernet over messaging driver support" 372 depends on RAPIDIO 373 374config RIONET_TX_SIZE 375 int "Number of outbound queue entries" 376 depends on RIONET 377 default "128" 378 379config RIONET_RX_SIZE 380 int "Number of inbound queue entries" 381 depends on RIONET 382 default "128" 383 384config FDDI 385 tristate "FDDI driver support" 386 depends on (PCI || EISA || TC) 387 help 388 Fiber Distributed Data Interface is a high speed local area network 389 design; essentially a replacement for high speed Ethernet. FDDI can 390 run over copper or fiber. If you are connected to such a network and 391 want a driver for the FDDI card in your computer, say Y here (and 392 then also Y to the driver for your FDDI card, below). Most people 393 will say N. 394 395config DEFXX 396 tristate "Digital DEFTA/DEFEA/DEFPA adapter support" 397 depends on FDDI && (PCI || EISA || TC) 398 ---help--- 399 This is support for the DIGITAL series of TURBOchannel (DEFTA), 400 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you 401 to a local FDDI network. 402 403 To compile this driver as a module, choose M here: the module 404 will be called defxx. If unsure, say N. 405 406config DEFXX_MMIO 407 bool 408 prompt "Use MMIO instead of PIO" if PCI || EISA 409 depends on DEFXX 410 default n if PCI || EISA 411 default y 412 ---help--- 413 This instructs the driver to use EISA or PCI memory-mapped I/O 414 (MMIO) as appropriate instead of programmed I/O ports (PIO). 415 Enabling this gives an improvement in processing time in parts 416 of the driver, but it may cause problems with EISA (DEFEA) 417 adapters. TURBOchannel does not have the concept of I/O ports, 418 so MMIO is always used for these (DEFTA) adapters. 419 420 If unsure, say N. 421 422config SKFP 423 tristate "SysKonnect FDDI PCI support" 424 depends on FDDI && PCI 425 select BITREVERSE 426 ---help--- 427 Say Y here if you have a SysKonnect FDDI PCI adapter. 428 The following adapters are supported by this driver: 429 - SK-5521 (SK-NET FDDI-UP) 430 - SK-5522 (SK-NET FDDI-UP DAS) 431 - SK-5541 (SK-NET FDDI-FP) 432 - SK-5543 (SK-NET FDDI-LP) 433 - SK-5544 (SK-NET FDDI-LP DAS) 434 - SK-5821 (SK-NET FDDI-UP64) 435 - SK-5822 (SK-NET FDDI-UP64 DAS) 436 - SK-5841 (SK-NET FDDI-FP64) 437 - SK-5843 (SK-NET FDDI-LP64) 438 - SK-5844 (SK-NET FDDI-LP64 DAS) 439 - Netelligent 100 FDDI DAS Fibre SC 440 - Netelligent 100 FDDI SAS Fibre SC 441 - Netelligent 100 FDDI DAS UTP 442 - Netelligent 100 FDDI SAS UTP 443 - Netelligent 100 FDDI SAS Fibre MIC 444 445 Read <file:Documentation/networking/skfp.txt> for information about 446 the driver. 447 448 Questions concerning this driver can be addressed to: 449 <linux@syskonnect.de> 450 451 To compile this driver as a module, choose M here: the module 452 will be called skfp. This is recommended. 453 454config HIPPI 455 bool "HIPPI driver support (EXPERIMENTAL)" 456 depends on EXPERIMENTAL && INET && PCI 457 help 458 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and 459 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI 460 can run over copper (25m) or fiber (300m on multi-mode or 10km on 461 single-mode). HIPPI networks are commonly used for clusters and to 462 connect to super computers. If you are connected to a HIPPI network 463 and have a HIPPI network card in your computer that you want to use 464 under Linux, say Y here (you must also remember to enable the driver 465 for your HIPPI card below). Most people will say N here. 466 467config ROADRUNNER 468 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)" 469 depends on HIPPI && PCI 470 help 471 Say Y here if this is your PCI HIPPI network card. 472 473 To compile this driver as a module, choose M here: the module 474 will be called rrunner. If unsure, say N. 475 476config ROADRUNNER_LARGE_RINGS 477 bool "Use large TX/RX rings (EXPERIMENTAL)" 478 depends on ROADRUNNER 479 help 480 If you say Y here, the RoadRunner driver will preallocate up to 2 MB 481 of additional memory to allow for fastest operation, both for 482 transmitting and receiving. This memory cannot be used by any other 483 kernel code or by user space programs. Say Y here only if you have 484 the memory. 485 486config PLIP 487 tristate "PLIP (parallel port) support" 488 depends on PARPORT 489 ---help--- 490 PLIP (Parallel Line Internet Protocol) is used to create a 491 reasonably fast mini network consisting of two (or, rarely, more) 492 local machines. A PLIP link from a Linux box is a popular means to 493 install a Linux distribution on a machine which doesn't have a 494 CD-ROM drive (a minimal system has to be transferred with floppies 495 first). The kernels on both machines need to have this PLIP option 496 enabled for this to work. 497 498 The PLIP driver has two modes, mode 0 and mode 1. The parallel 499 ports (the connectors at the computers with 25 holes) are connected 500 with "null printer" or "Turbo Laplink" cables which can transmit 4 501 bits at a time (mode 0) or with special PLIP cables, to be used on 502 bidirectional parallel ports only, which can transmit 8 bits at a 503 time (mode 1); you can find the wiring of these cables in 504 <file:Documentation/networking/PLIP.txt>. The cables can be up to 505 15m long. Mode 0 works also if one of the machines runs DOS/Windows 506 and has some PLIP software installed, e.g. the Crynwr PLIP packet 507 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>) 508 and winsock or NCSA's telnet. 509 510 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well 511 as the NET-3-HOWTO, both available from 512 <http://www.tldp.org/docs.html#howto>. Note that the PLIP 513 protocol has been changed and this PLIP driver won't work together 514 with the PLIP support in Linux versions 1.0.x. This option enlarges 515 your kernel by about 8 KB. 516 517 To compile this driver as a module, choose M here. The module 518 will be called plip. If unsure, say Y or M, in case you buy 519 a laptop later. 520 521config PPP 522 tristate "PPP (point-to-point protocol) support" 523 select SLHC 524 ---help--- 525 PPP (Point to Point Protocol) is a newer and better SLIP. It serves 526 the same purpose: sending Internet traffic over telephone (and other 527 serial) lines. Ask your access provider if they support it, because 528 otherwise you can't use it; most Internet access providers these 529 days support PPP rather than SLIP. 530 531 To use PPP, you need an additional program called pppd as described 532 in the PPP-HOWTO, available at 533 <http://www.tldp.org/docs.html#howto>. Make sure that you have 534 the version of pppd recommended in <file:Documentation/Changes>. 535 The PPP option enlarges your kernel by about 16 KB. 536 537 There are actually two versions of PPP: the traditional PPP for 538 asynchronous lines, such as regular analog phone lines, and 539 synchronous PPP which can be used over digital ISDN lines for 540 example. If you want to use PPP over phone lines or other 541 asynchronous serial lines, you need to say Y (or M) here and also to 542 the next option, "PPP support for async serial ports". For PPP over 543 synchronous lines, you should say Y (or M) here and to "Support 544 synchronous PPP", below. 545 546 If you said Y to "Version information on all symbols" above, then 547 you cannot compile the PPP driver into the kernel; you can then only 548 compile it as a module. To compile this driver as a module, choose M 549 here. The module will be called ppp_generic. 550 551config PPP_MULTILINK 552 bool "PPP multilink support (EXPERIMENTAL)" 553 depends on PPP && EXPERIMENTAL 554 help 555 PPP multilink is a protocol (defined in RFC 1990) which allows you 556 to combine several (logical or physical) lines into one logical PPP 557 connection, so that you can utilize your full bandwidth. 558 559 This has to be supported at the other end as well and you need a 560 version of the pppd daemon which understands the multilink protocol. 561 562 If unsure, say N. 563 564config PPP_FILTER 565 bool "PPP filtering" 566 depends on PPP 567 help 568 Say Y here if you want to be able to filter the packets passing over 569 PPP interfaces. This allows you to control which packets count as 570 activity (i.e. which packets will reset the idle timer or bring up 571 a demand-dialed link) and which packets are to be dropped entirely. 572 You need to say Y here if you wish to use the pass-filter and 573 active-filter options to pppd. 574 575 If unsure, say N. 576 577config PPP_ASYNC 578 tristate "PPP support for async serial ports" 579 depends on PPP 580 select CRC_CCITT 581 ---help--- 582 Say Y (or M) here if you want to be able to use PPP over standard 583 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use 584 a modem (not a synchronous or ISDN modem) to contact your ISP, you 585 need this option. 586 587 To compile this driver as a module, choose M here. 588 589 If unsure, say Y. 590 591config PPP_SYNC_TTY 592 tristate "PPP support for sync tty ports" 593 depends on PPP 594 help 595 Say Y (or M) here if you want to be able to use PPP over synchronous 596 (HDLC) tty devices, such as the SyncLink adapter. These devices 597 are often used for high-speed leased lines like T1/E1. 598 599 To compile this driver as a module, choose M here. 600 601config PPP_DEFLATE 602 tristate "PPP Deflate compression" 603 depends on PPP 604 select ZLIB_INFLATE 605 select ZLIB_DEFLATE 606 ---help--- 607 Support for the Deflate compression method for PPP, which uses the 608 Deflate algorithm (the same algorithm that gzip uses) to compress 609 each PPP packet before it is sent over the wire. The machine at the 610 other end of the PPP link (usually your ISP) has to support the 611 Deflate compression method as well for this to be useful. Even if 612 they don't support it, it is safe to say Y here. 613 614 To compile this driver as a module, choose M here. 615 616config PPP_BSDCOMP 617 tristate "PPP BSD-Compress compression" 618 depends on PPP 619 ---help--- 620 Support for the BSD-Compress compression method for PPP, which uses 621 the LZW compression method to compress each PPP packet before it is 622 sent over the wire. The machine at the other end of the PPP link 623 (usually your ISP) has to support the BSD-Compress compression 624 method as well for this to be useful. Even if they don't support it, 625 it is safe to say Y here. 626 627 The PPP Deflate compression method ("PPP Deflate compression", 628 above) is preferable to BSD-Compress, because it compresses better 629 and is patent-free. 630 631 Note that the BSD compression code will always be compiled as a 632 module; it is called bsd_comp and will show up in the directory 633 modules once you have said "make modules". If unsure, say N. 634 635config PPP_MPPE 636 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)" 637 depends on PPP && EXPERIMENTAL 638 select CRYPTO 639 select CRYPTO_SHA1 640 select CRYPTO_ARC4 641 select CRYPTO_ECB 642 ---help--- 643 Support for the MPPE Encryption protocol, as employed by the 644 Microsoft Point-to-Point Tunneling Protocol. 645 646 See http://pptpclient.sourceforge.net/ for information on 647 configuring PPTP clients and servers to utilize this method. 648 649config PPPOE 650 tristate "PPP over Ethernet (EXPERIMENTAL)" 651 depends on EXPERIMENTAL && PPP 652 help 653 Support for PPP over Ethernet. 654 655 This driver requires the latest version of pppd from the CVS 656 repository at cvs.samba.org. Alternatively, see the 657 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>) 658 which contains instruction on how to use this driver (under 659 the heading "Kernel mode PPPoE"). 660 661config PPTP 662 tristate "PPP over IPv4 (PPTP) (EXPERIMENTAL)" 663 depends on EXPERIMENTAL && PPP && NET_IPGRE_DEMUX 664 help 665 Support for PPP over IPv4.(Point-to-Point Tunneling Protocol) 666 667 This driver requires pppd plugin to work in client mode or 668 modified pptpd (poptop) to work in server mode. 669 See http://accel-pptp.sourceforge.net/ for information how to 670 utilize this module. 671 672config PPPOATM 673 tristate "PPP over ATM" 674 depends on ATM && PPP 675 help 676 Support PPP (Point to Point Protocol) encapsulated in ATM frames. 677 This implementation does not yet comply with section 8 of RFC2364, 678 which can lead to bad results if the ATM peer loses state and 679 changes its encapsulation unilaterally. 680 681config PPPOL2TP 682 tristate "PPP over L2TP (EXPERIMENTAL)" 683 depends on EXPERIMENTAL && L2TP && PPP 684 help 685 Support for PPP-over-L2TP socket family. L2TP is a protocol 686 used by ISPs and enterprises to tunnel PPP traffic over UDP 687 tunnels. L2TP is replacing PPTP for VPN uses. 688 689config SLIP 690 tristate "SLIP (serial line) support" 691 ---help--- 692 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to 693 connect to your Internet service provider or to connect to some 694 other local Unix box or if you want to configure your Linux box as a 695 Slip/CSlip server for other people to dial in. SLIP (Serial Line 696 Internet Protocol) is a protocol used to send Internet traffic over 697 serial connections such as telephone lines or null modem cables; 698 nowadays, the protocol PPP is more commonly used for this same 699 purpose. 700 701 Normally, your access provider has to support SLIP in order for you 702 to be able to use it, but there is now a SLIP emulator called SLiRP 703 around (available from 704 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which 705 allows you to use SLIP over a regular dial up shell connection. If 706 you plan to use SLiRP, make sure to say Y to CSLIP, below. The 707 NET-3-HOWTO, available from 708 <http://www.tldp.org/docs.html#howto>, explains how to 709 configure SLIP. Note that you don't need this option if you just 710 want to run term (term is a program which gives you almost full 711 Internet connectivity if you have a regular dial up shell account on 712 some Internet connected Unix computer. Read 713 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP 714 support will enlarge your kernel by about 4 KB. If unsure, say N. 715 716 To compile this driver as a module, choose M here. The module 717 will be called slip. 718 719config SLIP_COMPRESSED 720 bool "CSLIP compressed headers" 721 depends on SLIP 722 select SLHC 723 ---help--- 724 This protocol is faster than SLIP because it uses compression on the 725 TCP/IP headers (not on the data itself), but it has to be supported 726 on both ends. Ask your access provider if you are not sure and 727 answer Y, just in case. You will still be able to use plain SLIP. If 728 you plan to use SLiRP, the SLIP emulator (available from 729 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which 730 allows you to use SLIP over a regular dial up shell connection, you 731 definitely want to say Y here. The NET-3-HOWTO, available from 732 <http://www.tldp.org/docs.html#howto>, explains how to configure 733 CSLIP. This won't enlarge your kernel. 734 735config SLHC 736 tristate 737 help 738 This option enables Van Jacobsen serial line header compression 739 routines. 740 741config SLIP_SMART 742 bool "Keepalive and linefill" 743 depends on SLIP 744 help 745 Adds additional capabilities to the SLIP driver to support the 746 RELCOM line fill and keepalive monitoring. Ideal on poor quality 747 analogue lines. 748 749config SLIP_MODE_SLIP6 750 bool "Six bit SLIP encapsulation" 751 depends on SLIP 752 help 753 Just occasionally you may need to run IP over hostile serial 754 networks that don't pass all control characters or are only seven 755 bit. Saying Y here adds an extra mode you can use with SLIP: 756 "slip6". In this mode, SLIP will only send normal ASCII symbols over 757 the serial device. Naturally, this has to be supported at the other 758 end of the link as well. It's good enough, for example, to run IP 759 over the async ports of a Camtec JNT Pad. If unsure, say N. 760 761config NET_FC 762 bool "Fibre Channel driver support" 763 depends on SCSI && PCI 764 help 765 Fibre Channel is a high speed serial protocol mainly used to connect 766 large storage devices to the computer; it is compatible with and 767 intended to replace SCSI. 768 769 If you intend to use Fibre Channel, you need to have a Fibre channel 770 adaptor card in your computer; say Y here and to the driver for your 771 adaptor below. You also should have said Y to "SCSI support" and 772 "SCSI generic support". 773 774config NETCONSOLE 775 tristate "Network console logging support" 776 ---help--- 777 If you want to log kernel messages over the network, enable this. 778 See <file:Documentation/networking/netconsole.txt> for details. 779 780config NETCONSOLE_DYNAMIC 781 bool "Dynamic reconfiguration of logging targets" 782 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \ 783 !(NETCONSOLE=y && CONFIGFS_FS=m) 784 help 785 This option enables the ability to dynamically reconfigure target 786 parameters (interface, IP addresses, port numbers, MAC addresses) 787 at runtime through a userspace interface exported using configfs. 788 See <file:Documentation/networking/netconsole.txt> for details. 789 790config NETPOLL 791 def_bool NETCONSOLE 792 793config NETPOLL_TRAP 794 bool "Netpoll traffic trapping" 795 default n 796 depends on NETPOLL 797 798config NET_POLL_CONTROLLER 799 def_bool NETPOLL 800 801config VIRTIO_NET 802 tristate "Virtio network driver (EXPERIMENTAL)" 803 depends on EXPERIMENTAL && VIRTIO 804 ---help--- 805 This is the virtual network driver for virtio. It can be used with 806 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M. 807 808config VMXNET3 809 tristate "VMware VMXNET3 ethernet driver" 810 depends on PCI && INET 811 help 812 This driver supports VMware's vmxnet3 virtual ethernet NIC. 813 To compile this driver as a module, choose M here: the 814 module will be called vmxnet3. 815 816endif # NETDEVICES 817