diff options
Diffstat (limited to 'drivers/net/Kconfig')
-rw-r--r-- | drivers/net/Kconfig | 170 |
1 files changed, 2 insertions, 168 deletions
diff --git a/drivers/net/Kconfig b/drivers/net/Kconfig index 7bdc22b59856..c5e2a3871dc5 100644 --- a/drivers/net/Kconfig +++ b/drivers/net/Kconfig | |||
@@ -207,6 +207,8 @@ source "drivers/net/usb/Kconfig" | |||
207 | 207 | ||
208 | source "drivers/net/pcmcia/Kconfig" | 208 | source "drivers/net/pcmcia/Kconfig" |
209 | 209 | ||
210 | source "drivers/net/ppp/Kconfig" | ||
211 | |||
210 | source "drivers/net/wan/Kconfig" | 212 | source "drivers/net/wan/Kconfig" |
211 | 213 | ||
212 | source "drivers/atm/Kconfig" | 214 | source "drivers/atm/Kconfig" |
@@ -337,174 +339,6 @@ config PLIP | |||
337 | will be called plip. If unsure, say Y or M, in case you buy | 339 | will be called plip. If unsure, say Y or M, in case you buy |
338 | a laptop later. | 340 | a laptop later. |
339 | 341 | ||
340 | config PPP | ||
341 | tristate "PPP (point-to-point protocol) support" | ||
342 | select SLHC | ||
343 | ---help--- | ||
344 | PPP (Point to Point Protocol) is a newer and better SLIP. It serves | ||
345 | the same purpose: sending Internet traffic over telephone (and other | ||
346 | serial) lines. Ask your access provider if they support it, because | ||
347 | otherwise you can't use it; most Internet access providers these | ||
348 | days support PPP rather than SLIP. | ||
349 | |||
350 | To use PPP, you need an additional program called pppd as described | ||
351 | in the PPP-HOWTO, available at | ||
352 | <http://www.tldp.org/docs.html#howto>. Make sure that you have | ||
353 | the version of pppd recommended in <file:Documentation/Changes>. | ||
354 | The PPP option enlarges your kernel by about 16 KB. | ||
355 | |||
356 | There are actually two versions of PPP: the traditional PPP for | ||
357 | asynchronous lines, such as regular analog phone lines, and | ||
358 | synchronous PPP which can be used over digital ISDN lines for | ||
359 | example. If you want to use PPP over phone lines or other | ||
360 | asynchronous serial lines, you need to say Y (or M) here and also to | ||
361 | the next option, "PPP support for async serial ports". For PPP over | ||
362 | synchronous lines, you should say Y (or M) here and to "Support | ||
363 | synchronous PPP", below. | ||
364 | |||
365 | If you said Y to "Version information on all symbols" above, then | ||
366 | you cannot compile the PPP driver into the kernel; you can then only | ||
367 | compile it as a module. To compile this driver as a module, choose M | ||
368 | here. The module will be called ppp_generic. | ||
369 | |||
370 | config PPP_MULTILINK | ||
371 | bool "PPP multilink support (EXPERIMENTAL)" | ||
372 | depends on PPP && EXPERIMENTAL | ||
373 | help | ||
374 | PPP multilink is a protocol (defined in RFC 1990) which allows you | ||
375 | to combine several (logical or physical) lines into one logical PPP | ||
376 | connection, so that you can utilize your full bandwidth. | ||
377 | |||
378 | This has to be supported at the other end as well and you need a | ||
379 | version of the pppd daemon which understands the multilink protocol. | ||
380 | |||
381 | If unsure, say N. | ||
382 | |||
383 | config PPP_FILTER | ||
384 | bool "PPP filtering" | ||
385 | depends on PPP | ||
386 | help | ||
387 | Say Y here if you want to be able to filter the packets passing over | ||
388 | PPP interfaces. This allows you to control which packets count as | ||
389 | activity (i.e. which packets will reset the idle timer or bring up | ||
390 | a demand-dialed link) and which packets are to be dropped entirely. | ||
391 | You need to say Y here if you wish to use the pass-filter and | ||
392 | active-filter options to pppd. | ||
393 | |||
394 | If unsure, say N. | ||
395 | |||
396 | config PPP_ASYNC | ||
397 | tristate "PPP support for async serial ports" | ||
398 | depends on PPP | ||
399 | select CRC_CCITT | ||
400 | ---help--- | ||
401 | Say Y (or M) here if you want to be able to use PPP over standard | ||
402 | asynchronous serial ports, such as COM1 or COM2 on a PC. If you use | ||
403 | a modem (not a synchronous or ISDN modem) to contact your ISP, you | ||
404 | need this option. | ||
405 | |||
406 | To compile this driver as a module, choose M here. | ||
407 | |||
408 | If unsure, say Y. | ||
409 | |||
410 | config PPP_SYNC_TTY | ||
411 | tristate "PPP support for sync tty ports" | ||
412 | depends on PPP | ||
413 | help | ||
414 | Say Y (or M) here if you want to be able to use PPP over synchronous | ||
415 | (HDLC) tty devices, such as the SyncLink adapter. These devices | ||
416 | are often used for high-speed leased lines like T1/E1. | ||
417 | |||
418 | To compile this driver as a module, choose M here. | ||
419 | |||
420 | config PPP_DEFLATE | ||
421 | tristate "PPP Deflate compression" | ||
422 | depends on PPP | ||
423 | select ZLIB_INFLATE | ||
424 | select ZLIB_DEFLATE | ||
425 | ---help--- | ||
426 | Support for the Deflate compression method for PPP, which uses the | ||
427 | Deflate algorithm (the same algorithm that gzip uses) to compress | ||
428 | each PPP packet before it is sent over the wire. The machine at the | ||
429 | other end of the PPP link (usually your ISP) has to support the | ||
430 | Deflate compression method as well for this to be useful. Even if | ||
431 | they don't support it, it is safe to say Y here. | ||
432 | |||
433 | To compile this driver as a module, choose M here. | ||
434 | |||
435 | config PPP_BSDCOMP | ||
436 | tristate "PPP BSD-Compress compression" | ||
437 | depends on PPP | ||
438 | ---help--- | ||
439 | Support for the BSD-Compress compression method for PPP, which uses | ||
440 | the LZW compression method to compress each PPP packet before it is | ||
441 | sent over the wire. The machine at the other end of the PPP link | ||
442 | (usually your ISP) has to support the BSD-Compress compression | ||
443 | method as well for this to be useful. Even if they don't support it, | ||
444 | it is safe to say Y here. | ||
445 | |||
446 | The PPP Deflate compression method ("PPP Deflate compression", | ||
447 | above) is preferable to BSD-Compress, because it compresses better | ||
448 | and is patent-free. | ||
449 | |||
450 | Note that the BSD compression code will always be compiled as a | ||
451 | module; it is called bsd_comp and will show up in the directory | ||
452 | modules once you have said "make modules". If unsure, say N. | ||
453 | |||
454 | config PPP_MPPE | ||
455 | tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)" | ||
456 | depends on PPP && EXPERIMENTAL | ||
457 | select CRYPTO | ||
458 | select CRYPTO_SHA1 | ||
459 | select CRYPTO_ARC4 | ||
460 | select CRYPTO_ECB | ||
461 | ---help--- | ||
462 | Support for the MPPE Encryption protocol, as employed by the | ||
463 | Microsoft Point-to-Point Tunneling Protocol. | ||
464 | |||
465 | See http://pptpclient.sourceforge.net/ for information on | ||
466 | configuring PPTP clients and servers to utilize this method. | ||
467 | |||
468 | config PPPOE | ||
469 | tristate "PPP over Ethernet (EXPERIMENTAL)" | ||
470 | depends on EXPERIMENTAL && PPP | ||
471 | help | ||
472 | Support for PPP over Ethernet. | ||
473 | |||
474 | This driver requires the latest version of pppd from the CVS | ||
475 | repository at cvs.samba.org. Alternatively, see the | ||
476 | RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>) | ||
477 | which contains instruction on how to use this driver (under | ||
478 | the heading "Kernel mode PPPoE"). | ||
479 | |||
480 | config PPTP | ||
481 | tristate "PPP over IPv4 (PPTP) (EXPERIMENTAL)" | ||
482 | depends on EXPERIMENTAL && PPP && NET_IPGRE_DEMUX | ||
483 | help | ||
484 | Support for PPP over IPv4.(Point-to-Point Tunneling Protocol) | ||
485 | |||
486 | This driver requires pppd plugin to work in client mode or | ||
487 | modified pptpd (poptop) to work in server mode. | ||
488 | See http://accel-pptp.sourceforge.net/ for information how to | ||
489 | utilize this module. | ||
490 | |||
491 | config PPPOATM | ||
492 | tristate "PPP over ATM" | ||
493 | depends on ATM && PPP | ||
494 | help | ||
495 | Support PPP (Point to Point Protocol) encapsulated in ATM frames. | ||
496 | This implementation does not yet comply with section 8 of RFC2364, | ||
497 | which can lead to bad results if the ATM peer loses state and | ||
498 | changes its encapsulation unilaterally. | ||
499 | |||
500 | config PPPOL2TP | ||
501 | tristate "PPP over L2TP (EXPERIMENTAL)" | ||
502 | depends on EXPERIMENTAL && L2TP && PPP | ||
503 | help | ||
504 | Support for PPP-over-L2TP socket family. L2TP is a protocol | ||
505 | used by ISPs and enterprises to tunnel PPP traffic over UDP | ||
506 | tunnels. L2TP is replacing PPTP for VPN uses. | ||
507 | |||
508 | config SLIP | 342 | config SLIP |
509 | tristate "SLIP (serial line) support" | 343 | tristate "SLIP (serial line) support" |
510 | ---help--- | 344 | ---help--- |