Kconfig 6.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179
  1. #
  2. # PPP network device configuration
  3. #
  4. config PPP
  5. tristate "PPP (point-to-point protocol) support"
  6. select SLHC
  7. ---help---
  8. PPP (Point to Point Protocol) is a newer and better SLIP. It serves
  9. the same purpose: sending Internet traffic over telephone (and other
  10. serial) lines. Ask your access provider if they support it, because
  11. otherwise you can't use it; most Internet access providers these
  12. days support PPP rather than SLIP.
  13. To use PPP, you need an additional program called pppd as described
  14. in the PPP-HOWTO, available at
  15. <http://www.tldp.org/docs.html#howto>. Make sure that you have
  16. the version of pppd recommended in <file:Documentation/Changes>.
  17. The PPP option enlarges your kernel by about 16 KB.
  18. There are actually two versions of PPP: the traditional PPP for
  19. asynchronous lines, such as regular analog phone lines, and
  20. synchronous PPP which can be used over digital ISDN lines for
  21. example. If you want to use PPP over phone lines or other
  22. asynchronous serial lines, you need to say Y (or M) here and also to
  23. the next option, "PPP support for async serial ports". For PPP over
  24. synchronous lines, you should say Y (or M) here and to "Support
  25. synchronous PPP", below.
  26. If you said Y to "Version information on all symbols" above, then
  27. you cannot compile the PPP driver into the kernel; you can then only
  28. compile it as a module. To compile this driver as a module, choose M
  29. here. The module will be called ppp_generic.
  30. if PPP
  31. config PPP_BSDCOMP
  32. tristate "PPP BSD-Compress compression"
  33. depends on PPP
  34. ---help---
  35. Support for the BSD-Compress compression method for PPP, which uses
  36. the LZW compression method to compress each PPP packet before it is
  37. sent over the wire. The machine at the other end of the PPP link
  38. (usually your ISP) has to support the BSD-Compress compression
  39. method as well for this to be useful. Even if they don't support it,
  40. it is safe to say Y here.
  41. The PPP Deflate compression method ("PPP Deflate compression",
  42. above) is preferable to BSD-Compress, because it compresses better
  43. and is patent-free.
  44. Note that the BSD compression code will always be compiled as a
  45. module; it is called bsd_comp and will show up in the directory
  46. modules once you have said "make modules". If unsure, say N.
  47. config PPP_DEFLATE
  48. tristate "PPP Deflate compression"
  49. depends on PPP
  50. select ZLIB_INFLATE
  51. select ZLIB_DEFLATE
  52. ---help---
  53. Support for the Deflate compression method for PPP, which uses the
  54. Deflate algorithm (the same algorithm that gzip uses) to compress
  55. each PPP packet before it is sent over the wire. The machine at the
  56. other end of the PPP link (usually your ISP) has to support the
  57. Deflate compression method as well for this to be useful. Even if
  58. they don't support it, it is safe to say Y here.
  59. To compile this driver as a module, choose M here.
  60. config PPP_FILTER
  61. bool "PPP filtering"
  62. depends on PPP
  63. ---help---
  64. Say Y here if you want to be able to filter the packets passing over
  65. PPP interfaces. This allows you to control which packets count as
  66. activity (i.e. which packets will reset the idle timer or bring up
  67. a demand-dialed link) and which packets are to be dropped entirely.
  68. You need to say Y here if you wish to use the pass-filter and
  69. active-filter options to pppd.
  70. If unsure, say N.
  71. config PPP_MPPE
  72. tristate "PPP MPPE compression (encryption)"
  73. depends on PPP
  74. select CRYPTO
  75. select CRYPTO_SHA1
  76. select CRYPTO_ARC4
  77. select CRYPTO_ECB
  78. ---help---
  79. Support for the MPPE Encryption protocol, as employed by the
  80. Microsoft Point-to-Point Tunneling Protocol.
  81. See http://pptpclient.sourceforge.net/ for information on
  82. configuring PPTP clients and servers to utilize this method.
  83. config PPP_MULTILINK
  84. bool "PPP multilink support"
  85. depends on PPP
  86. ---help---
  87. PPP multilink is a protocol (defined in RFC 1990) which allows you
  88. to combine several (logical or physical) lines into one logical PPP
  89. connection, so that you can utilize your full bandwidth.
  90. This has to be supported at the other end as well and you need a
  91. version of the pppd daemon which understands the multilink protocol.
  92. If unsure, say N.
  93. config PPPOATM
  94. tristate "PPP over ATM"
  95. depends on ATM && PPP
  96. ---help---
  97. Support PPP (Point to Point Protocol) encapsulated in ATM frames.
  98. This implementation does not yet comply with section 8 of RFC2364,
  99. which can lead to bad results if the ATM peer loses state and
  100. changes its encapsulation unilaterally.
  101. config PPPOE
  102. tristate "PPP over Ethernet"
  103. depends on PPP
  104. ---help---
  105. Support for PPP over Ethernet.
  106. This driver requires the latest version of pppd from the CVS
  107. repository at cvs.samba.org. Alternatively, see the
  108. RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
  109. which contains instruction on how to use this driver (under
  110. the heading "Kernel mode PPPoE").
  111. config PPTP
  112. tristate "PPP over IPv4 (PPTP)"
  113. depends on PPP && NET_IPGRE_DEMUX
  114. ---help---
  115. Support for PPP over IPv4.(Point-to-Point Tunneling Protocol)
  116. This driver requires pppd plugin to work in client mode or
  117. modified pptpd (poptop) to work in server mode.
  118. See http://accel-pptp.sourceforge.net/ for information how to
  119. utilize this module.
  120. config PPPOL2TP
  121. tristate "PPP over L2TP"
  122. depends on L2TP && PPP
  123. ---help---
  124. Support for PPP-over-L2TP socket family. L2TP is a protocol
  125. used by ISPs and enterprises to tunnel PPP traffic over UDP
  126. tunnels. L2TP is replacing PPTP for VPN uses.
  127. if TTY
  128. config PPP_ASYNC
  129. tristate "PPP support for async serial ports"
  130. depends on PPP
  131. select CRC_CCITT
  132. ---help---
  133. Say Y (or M) here if you want to be able to use PPP over standard
  134. asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
  135. a modem (not a synchronous or ISDN modem) to contact your ISP, you
  136. need this option.
  137. To compile this driver as a module, choose M here.
  138. If unsure, say Y.
  139. config PPP_SYNC_TTY
  140. tristate "PPP support for sync tty ports"
  141. depends on PPP
  142. ---help---
  143. Say Y (or M) here if you want to be able to use PPP over synchronous
  144. (HDLC) tty devices, such as the SyncLink adapter. These devices
  145. are often used for high-speed leased lines like T1/E1.
  146. To compile this driver as a module, choose M here.
  147. endif # TTY
  148. endif # PPP