3 ppp, pppoe, pptp, pptpd \- point-to-point protocol
96 The Point-to-Point Protocol is used to encapsulate Internet Protocol packets
98 for transfer over serial lines or other protocol connections.
100 can run either as a client or, with the
102 option, as a server. The only differences between a client and a server is
103 that the server will not believe any local address the client tries to
104 supply it and that the server always initiates the authentication of the
109 communicates with the remote system via standard input and output.
110 This is useful if a program wants to use
112 in a communications stream. However, the normal mode is to
113 specify a communications device, usually a serial line with a modem.
116 supports the following options:
119 as server, don't request authentication from the client
122 set the baud rate on the communications device
125 disallow packet compression
128 disallow IP header compression
131 make PPP add HDLC framing. This is necessary when using
132 PPP over a serial line or a TCP connection
139 key pattern when looking for a user name and password
140 for authentication; the default key pattern is
141 .B "proto=pass" "service=ppp"
144 set the maximum transfer unit (default 1450)
147 chat with the modem as specified in the chat file. Each line in
148 the chat file contains a string that is transmitted to the modem
149 and the response expected (e.g. 'AT' 'OK')
152 use this as the primary IP interface; set the default
153 route through this interface and write its configuration
160 instead of standard I/O
166 before starting the PPP protocol, write
171 before starting the PPP protocol with the remote end, shuttle
172 bytes between the device and standard I/O until an EOF on standard
173 input. This allows a user to start
175 and then type commands at a modem before
180 use the IP stack mounted at
188 addresses are specified, don't ask the other end for either
189 or believe it if it supplies one. If either is missing, get
190 it from the remote end.
193 is a PPP over ethernet (PPPoE) client.
196 to start a PPP conversation which is
197 tunneled in PPPoE packets on
198 the ethernet device mounted at
207 insist on an access concentrator named
209 during PPPoE discovery
212 write debugging output to standard error,
219 insist on a service named
221 during PPPoE discovery
224 The other options are relayed to
228 is a client for a PPTP encrypted tunnel.
230 is the name of the server to dial.
232 takes the same options as
234 except for the lack of a
236 option and the addition of a
241 option specifies the local send window size
242 (default 16) in packets.
245 is the server side of a PPTP encrypted tunnel.
247 is the directory of a TCP connection to the client.
248 The TCP connection is used to control the tunnel while
249 packets are sent back and forth using PPP inside of
254 write debugging output to standard error.
259 of the received packets. This is used for testing.
262 use the IP stack mounted at
264 to terminate the PPP connection.
267 set the receive window to
271 .B /sys/src/cmd/ip/ppp
273 .B /sys/src/cmd/ip/pptpd.c
275 .B /sys/src/cmd/ip/pppoe.c
282 should use factotum to execute
283 the client side of the challenge-reponse
284 protocol, but instead it reads a password
285 from factotum and runs the protocol itself.