1
0

ppp 4.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279
  1. .TH PPP 8
  2. .SH NAME
  3. ppp, pppoe, pptp, pptpd \- point to point protocol
  4. .SH SYNOPSIS
  5. .B ip/ppp
  6. [
  7. .B -CPScdfu
  8. ] [
  9. .B -b
  10. .I baud
  11. ] [
  12. .B -k
  13. .I keyspec
  14. ] [
  15. .B -m
  16. .I mtu
  17. ] [
  18. .B -M
  19. .I chatfile
  20. ] [
  21. .B -p
  22. .I dev
  23. ] [
  24. .B -x
  25. .I netmntpt
  26. ] [
  27. .B -t
  28. .I modemcmd
  29. ] [
  30. .I local
  31. [
  32. .I remote
  33. ] ]
  34. .PP
  35. .B ip/pppoe
  36. [
  37. .B -dP
  38. ]
  39. [
  40. .B -m
  41. .I mtu
  42. ]
  43. [
  44. .B -x
  45. .I pppnetmntpt
  46. ]
  47. .I etherdir
  48. .PP
  49. .B ip/pptp
  50. [
  51. .B -dP
  52. ]
  53. [
  54. .B -k
  55. .I keyspec
  56. ]
  57. [
  58. .B -w
  59. .I window
  60. ]
  61. [
  62. .B -x
  63. .I pppnetmntpt
  64. ]
  65. .I server
  66. .PP
  67. .B ip/pptpd
  68. [
  69. .B -d
  70. ] [
  71. .B -p
  72. .I pppnetmtpt
  73. ] [
  74. .B -w
  75. .I window
  76. ] [
  77. .B -D
  78. .I fraction
  79. ]
  80. .I tcp-dir
  81. .SH DESCRIPTION
  82. The Point to Point Protocol is used to encapsulate Internet Protocol packets
  83. for transfer over serial lines or other protocol connections.
  84. .I Ppp
  85. can run either as a client or, with the
  86. .I \-S
  87. option, as a server. The only differences between a client and a server is
  88. that the server will not believe any local address the client tries to
  89. supply it and that the server always initiates the authentication of the
  90. client.
  91. .PP
  92. With no option,
  93. .I ppp
  94. communicates with the remote system via standard input and output.
  95. This is useful if a program wants to use
  96. .I ppp
  97. in a communications stream. However, the normal mode is to
  98. specify a communications device, usually a serial line with a modem.
  99. .PP
  100. PPP supports the following options:
  101. .TP
  102. .B b
  103. set the baud rate on the communications device
  104. .TP
  105. .B f
  106. make PPP add HDLC framing. This is necessary when using
  107. PPP over a serial line or a TCP connection
  108. .TP
  109. .B k
  110. add
  111. .I keyspec
  112. to the
  113. .IR factotum (4)
  114. key pattern when looking for a user name and password
  115. for authentication; the default key pattern is
  116. .B "proto=pass" "service=ppp"
  117. .TP
  118. .B m
  119. set the maximum transfer unit (default 1450)
  120. .TP
  121. .B P
  122. use this as the primary IP interface; set the default
  123. route through this interface and write its configuration
  124. to
  125. .B /net/ndb
  126. .TP
  127. .B p
  128. communicate over
  129. .I dev
  130. instead of standard I/O
  131. .TP
  132. .B u
  133. before starting the PPP porotcol with the remote end, shuttle
  134. bytes between the device and standard I/O until an EOF on standard
  135. input. This allows a user to start
  136. .I ppp
  137. and then type commands at a modem before
  138. .I ppp
  139. takes over
  140. .TP
  141. .B S
  142. run as a server
  143. .TP
  144. .B t
  145. before starting the PPP protocol, write
  146. .I modemcmd
  147. to the device
  148. .TP
  149. .B x
  150. use the IP stack mounted at
  151. .I netmntpt
  152. .TP
  153. .B M
  154. chat with the modem as specified in the chat file. Each line in
  155. the chat file contains a string that is transmitted to the modem
  156. and the response expected (e.g. 'AT' 'OK')
  157. .TP
  158. .B c
  159. disallow packet compression
  160. .TP
  161. .B C
  162. disallow ip header compression
  163. .PD
  164. .PP
  165. If both the
  166. .I local
  167. and
  168. .I remote
  169. addresses are specified, don't ask the other end for either
  170. or believe it if it supplies one. If either is missing, get
  171. it from the remote end.
  172. .PP
  173. .I Pppoe
  174. is a PPP over ethernet (PPPoE) client.
  175. It invokes
  176. .I ppp
  177. to start a PPP conversation which is
  178. tunneled in PPPoE packets on
  179. the ethernet device mounted at
  180. .I etherdir
  181. (default
  182. .BR /net/ether0 ).
  183. The options are:
  184. .TP
  185. .B A
  186. insist on an access concentrator named
  187. .I acname
  188. during PPPoE discovery
  189. .TP
  190. .B S
  191. insist on a service named
  192. .I srvname
  193. during PPPoE discovery
  194. .TP
  195. .B d
  196. write debugging output to standard error,
  197. and pass
  198. .B -d
  199. to
  200. .I ppp
  201. .TP
  202. .B m
  203. pass
  204. .B -m
  205. .I mtu
  206. to
  207. .IR ppp ,
  208. default 1492
  209. .TP
  210. .B k
  211. pass
  212. .B -k
  213. .I keyspec
  214. to
  215. .I ppp
  216. .TP
  217. .B x
  218. pass
  219. .B -x
  220. .I pppnetmntpt
  221. to
  222. .I ppp
  223. .PD
  224. .PP
  225. .I Pptp
  226. is a client for a PPTP encrypted tunnel.
  227. .I Server
  228. is the name of the server to dial.
  229. .I Pptp
  230. takes the same options as
  231. .IR pppoe ,
  232. except for the lack of a
  233. .B -m
  234. option and the addition of a
  235. .B -w
  236. option.
  237. The
  238. .B -w
  239. option specifies the local send window size
  240. (default 16) in packets.
  241. .PP
  242. .I Pptpd
  243. is the server side of a PPTP encrypted tunnel.
  244. .I Tcpdir
  245. is the directory of a TCP connection to the client.
  246. The TCP connection is used to control the tunnel while
  247. packets are sent back and forth using PPP inside of
  248. GRE packets.
  249. The options are:
  250. .TP
  251. .B d
  252. write debugging output to standard error.
  253. .TP
  254. .B p
  255. use the IP stack mounted at
  256. .I pppnetmtpt
  257. to terminate the PPP connection.
  258. .TP
  259. .B w
  260. set the receive window to
  261. .IR window .
  262. .TP
  263. .B D
  264. drop
  265. .I fraction
  266. of the received packets. This is used for testing.
  267. .PD
  268. .SH SOURCE
  269. .B /sys/src/cmd/ip/ppp
  270. .br
  271. .B /sys/src/cmd/ip/pptpd.c
  272. .br
  273. .B /sys/src/cmd/ip/pppoe.c
  274. .SH BUGS
  275. .I Ppp
  276. should use factotum to execute
  277. the client side of the challenge-reponse
  278. protocol, but instead it reads a password
  279. from factotum and runs the protocol itself.