1 .\" manual page [] for pppd 2.3
2 .\" $Id: pppd.8,v 1.41 1999/07/21 00:24:32 paulus Exp $
4 .\" SS subsection heading
6 .\" IP indented paragraph
10 pppd \- Point to Point Protocol daemon
22 The Point-to-Point Protocol (PPP) provides a method for transmitting
23 datagrams over serial point-to-point links. PPP
24 is composed of three parts: a method for encapsulating datagrams over
25 serial links, an extensible Link Control Protocol (LCP), and
26 a family of Network Control Protocols (NCP) for establishing
27 and configuring different network-layer protocols.
29 The encapsulation scheme is provided by driver code in the kernel.
30 Pppd provides the basic LCP, authentication support, and an NCP for
31 establishing and configuring the Internet Protocol (IP) (called the IP
32 Control Protocol, IPCP).
33 .SH FREQUENTLY USED OPTIONS
36 Communicate over the named device. The string "/dev/" is prepended if
37 necessary. If no device name is given, or if the name of the terminal
38 connected to the standard input is given, pppd will use that terminal,
39 and will not fork to put itself in the background. A value for this
40 option from a privileged source cannot be overridden by a
44 Set the baud rate to <speed> (a decimal number). On systems such as
45 4.4BSD and NetBSD, any speed can be specified. Other systems
46 (e.g. SunOS) allow only a limited set of speeds.
49 Set the async character map to <map>. This map describes which
50 control characters cannot be successfully received over the serial
51 line. Pppd will ask the peer to send these characters as a 2-byte
52 escape sequence. The argument is a 32 bit hex number with each bit
53 representing a character to escape. Bit 0 (00000001) represents the
54 character 0x00; bit 31 (80000000) represents the character 0x1f or ^_.
55 If multiple \fIasyncmap\fR options are given, the values are ORed
56 together. If no \fIasyncmap\fR option is given, no async character
57 map will be negotiated for the receive direction; the peer should then
58 escape \fIall\fR control characters. To escape transmitted
59 characters, use the \fIescape\fR option.
62 Require the peer to authenticate itself before allowing network
63 packets to be sent or received. This option is the default if the
64 system has a default route. If neither this option nor the
65 \fInoauth\fR option is specified, pppd will only allow the peer to use
66 IP addresses to which the system does not already have a route.
69 Read options from the file /etc/ppp/peers/\fIname\fR. This file may
70 contain privileged options, such as \fInoauth\fR, even if pppd
71 is not being run by root. The \fIname\fR string may not begin with /
72 or include .. as a pathname component. The format of the options file
76 Use the executable or shell command specified by \fIscript\fR to set
77 up the serial line. This script would typically use the chat(8)
78 program to dial the modem and start the remote ppp session. A value
79 for this option from a privileged source cannot be overridden by a
83 Use hardware flow control (i.e. RTS/CTS) to control the flow of
84 data on the serial port. If neither the \fIcrtscts\fR, the
85 \fInocrtscts\fR, the \fIcdtrcts\fR nor the \fInocdtrcts\fR option
86 is given, the hardware flow control setting for the serial port is
88 Some serial ports (such as Macintosh serial ports) lack a true
89 RTS output. Such serial ports use this mode to implement
90 unidirectional flow control. The serial port will
91 suspend transmission when requested by the modem (via CTS)
92 but will be unable to request the modem stop sending to the
93 computer. This mode retains the ability to use DTR as
97 Use a non-standard hardware flow control (i.e. DTR/CTS) to control
98 the flow of data on the serial port. If neither the \fIcrtscts\fR,
99 the \fInocrtscts\fR, the \fIcdtrcts\fR nor the \fInocdtrcts\fR
100 option is given, the hardware flow control setting for the serial
101 port is left unchanged.
102 Some serial ports (such as Macintosh serial ports) lack a true
103 RTS output. Such serial ports use this mode to implement true
104 bi-directional flow control. The sacrifice is that this flow
105 control mode does not permit using DTR as a modem control line.
108 Add a default route to the system routing tables, using the peer as
109 the gateway, when IPCP negotiation is successfully completed.
110 This entry is removed when the PPP connection is broken. This option
111 is privileged if the \fInodefaultroute\fR option has been specified.
113 .B disconnect \fIscript
114 Run the executable or shell command specified by \fIscript\fR after
115 pppd has terminated the link. This script could, for example, issue
116 commands to the modem to cause it to hang up if hardware modem control
117 signals were not available. The disconnect script is not run if the
118 modem has already hung up. A value for this option from a privileged
119 source cannot be overridden by a non-privileged user.
121 .B escape \fIxx,yy,...
122 Specifies that certain characters should be escaped on transmission
123 (regardless of whether the peer requests them to be escaped with its
124 async control character map). The characters to be escaped are
125 specified as a list of hex numbers separated by commas. Note that
126 almost any character can be specified for the \fIescape\fR option,
127 unlike the \fIasyncmap\fR option which only allows control characters
128 to be specified. The characters which may not be escaped are those
129 with hex values 0x20 - 0x3f or 0x5e.
132 Read options from file \fIname\fR (the format is described below).
133 The file must be readable by the user who has invoked pppd.
136 Run the executable or shell command specified by \fIscript\fR to
137 initialize the serial line. This script would typically use the
138 chat(8) program to configure the modem to enable auto answer. A value
139 for this option from a privileged source cannot be overridden by a
143 Specifies that pppd should create a UUCP-style lock file for the
144 serial device to ensure exclusive access to the device.
147 Set the MRU [Maximum Receive Unit] value to \fIn\fR. Pppd
148 will ask the peer to send packets of no more than \fIn\fR bytes. The
149 minimum MRU value is 128. The default MRU value is 1500. A value of
150 296 is recommended for slow links (40 bytes for TCP/IP header + 256
154 Set the MTU [Maximum Transmit Unit] value to \fIn\fR. Unless the
155 peer requests a smaller value via MRU negotiation, pppd will
156 request that the kernel networking code send data packets of no more
157 than \fIn\fR bytes through the PPP network interface.
160 Enables the "passive" option in the LCP. With this option, pppd will
161 attempt to initiate a connection; if no reply is received from the
162 peer, pppd will then just wait passively for a valid LCP packet from
163 the peer, instead of exiting, as it would without this option.
166 .I <local_IP_address>\fB:\fI<remote_IP_address>
167 Set the local and/or remote interface IP addresses. Either one may be
168 omitted. The IP addresses can be specified with a host name or in
169 decimal dot notation (e.g. 150.234.56.78). The default local
170 address is the (first) IP address of the system (unless the
172 option is given). The remote address will be obtained from the peer
173 if not specified in any option. Thus, in simple cases, this option is
174 not required. If a local and/or remote IP address is specified with
176 will not accept a different value from the peer in the IPCP
177 negotiation, unless the \fIipcp-accept-local\fR and/or
178 \fIipcp-accept-remote\fR options are given, respectively.
180 .B active-filter \fIfilter-expression
181 Specifies a packet filter to be applied to data packets to determine
182 which packets are to be regarded as link activity, and therefore reset
183 the idle timer, or cause the link to be brought up in demand-dialling
184 mode. This option is useful in conjunction with the
185 \fBidle\fR option if there are packets being sent or received
186 regularly over the link (for example, routing information packets)
187 which would otherwise prevent the link from ever appearing to be idle.
188 The \fIfilter-expression\fR syntax is as described for tcpdump(1),
189 except that qualifiers which are inappropriate for a PPP link, such as
190 \fBether\fR and \fBarp\fR, are not permitted. Generally the filter
191 expression should be enclosed in single-quotes to prevent whitespace
192 in the expression from being interpreted by the shell. This option
193 is currently only available under NetBSD, and then only
194 if both the kernel and pppd were compiled with PPP_FILTER defined.
197 Request that the peer compress packets that it sends, using the
198 BSD-Compress scheme, with a maximum code size of \fInr\fR bits, and
199 agree to compress packets sent to the peer with a maximum code size of
200 \fInt\fR bits. If \fInt\fR is not specified, it defaults to the value
201 given for \fInr\fR. Values in the range 9 to 15 may be used for
202 \fInr\fR and \fInt\fR; larger values give better compression but
203 consume more kernel memory for compression dictionaries.
204 Alternatively, a value of 0 for \fInr\fR or \fInt\fR disables
205 compression in the corresponding direction. Use \fInobsdcomp\fR or
206 \fIbsdcomp 0\fR to disable BSD-Compress compression entirely.
208 .B chap-interval \fIn
209 If this option is given, pppd will rechallenge the peer every \fIn\fR
212 .B chap-max-challenge \fIn
213 Set the maximum number of CHAP challenge transmissions to \fIn\fR
217 Set the CHAP restart interval (retransmission timeout for challenges)
218 to \fIn\fR seconds (default 3).
221 Enables connection debugging facilities.
222 If this option is given, pppd will log the contents of all
223 control packets sent or received in a readable form. The packets are
224 logged through syslog with facility \fIdaemon\fR and level
225 \fIdebug\fR. This information can be directed to a file by setting up
226 /etc/syslog.conf appropriately (see syslog.conf(5)).
229 Disable asyncmap negotiation, forcing all control characters to be
230 escaped for both the transmit and the receive direction.
233 Disable MRU [Maximum Receive Unit] negotiation. With this option,
234 pppd will use the default MRU value of 1500 bytes for both the
235 transmit and receive direction.
238 Request that the peer compress packets that it sends, using the
239 Deflate scheme, with a maximum window size of \fI2**nr\fR bytes, and
240 agree to compress packets sent to the peer with a maximum window size
241 of \fI2**nt\fR bytes. If \fInt\fR is not specified, it defaults to
242 the value given for \fInr\fR. Values in the range 8 to 15 may be used
243 for \fInr\fR and \fInt\fR; larger values give better compression but
244 consume more kernel memory for compression dictionaries.
245 Alternatively, a value of 0 for \fInr\fR or \fInt\fR disables
246 compression in the corresponding direction. Use \fInodeflate\fR or
247 \fIdeflate 0\fR to disable Deflate compression entirely. (Note: pppd
248 requests Deflate compression in preference to BSD-Compress if the peer
252 Initiate the link only on demand, i.e. when data traffic is present.
253 With this option, the remote IP address must be specified by the user
254 on the command line or in an options file. Pppd will initially
255 configure the interface and enable it for IP traffic without
256 connecting to the peer. When traffic is available, pppd will
257 connect to the peer and perform negotiation, authentication, etc.
258 When this is completed, pppd will commence passing data packets
259 (i.e., IP packets) across the link.
261 The \fIdemand\fR option implies the \fIpersist\fR option. If this
262 behaviour is not desired, use the \fInopersist\fR option after the
263 \fIdemand\fR option. The \fIidle\fR and \fIholdoff\fR
264 options are also useful in conjuction with the \fIdemand\fR option.
267 Append the domain name \fId\fR to the local host name for authentication
268 purposes. For example, if gethostname() returns the name porsche, but
269 the fully qualified domain name is porsche.Quotron.COM, you could
270 specify \fIdomain Quotron.COM\fR. Pppd would then use the name
271 \fIporsche.Quotron.COM\fR for looking up secrets in the secrets file,
272 and as the default name to send to the peer when authenticating itself
273 to the peer. This option is privileged.
276 When logging the contents of PAP packets, this option causes pppd to
277 exclude the password string from the log.
280 Specifies how many seconds to wait before re-initiating the link after
281 it terminates. This option only has any effect if the \fIpersist\fR
282 or \fIdemand\fR option is used. The holdoff period is not applied if
283 the link was terminated because it was idle.
286 Specifies that pppd should disconnect if the link is idle for \fIn\fR
287 seconds. The link is idle when no data packets (i.e. IP packets) are
288 being sent or received. Note: it is not advisable to use this option
289 with the \fIpersist\fR option without the \fIdemand\fR option.
290 If the \fBactive-filter\fR
291 option is given, data packets which are rejected by the specified
292 activity filter also count as the link being idle.
295 With this option, pppd will accept the peer's idea of our local IP
296 address, even if the local IP address was specified in an option.
298 .B ipcp-accept-remote
299 With this option, pppd will accept the peer's idea of its (remote) IP
300 address, even if the remote IP address was specified in an option.
302 .B ipcp-max-configure \fIn
303 Set the maximum number of IPCP configure-request transmissions to
304 \fIn\fR (default 10).
306 .B ipcp-max-failure \fIn
307 Set the maximum number of IPCP configure-NAKs returned before starting
308 to send configure-Rejects instead to \fIn\fR (default 10).
310 .B ipcp-max-terminate \fIn
311 Set the maximum number of IPCP terminate-request transmissions to
315 Set the IPCP restart interval (retransmission timeout) to \fIn\fR
319 Provides an extra parameter to the ip-up and ip-down scripts. If this
320 option is given, the \fIstring\fR supplied is given as the 6th
321 parameter to those scripts.
324 Enable the IPXCP and IPX protocols. This option is presently only
325 supported under Linux, and only if your kernel has been configured to
329 Set the IPX network number in the IPXCP configure request frame to
330 \fIn\fR, a hexadecimal number (without a leading 0x). There is no
331 valid default. If this option is not specified, the network number is
332 obtained from the peer. If the peer does not have the network number,
333 the IPX protocol will not be started.
335 .B ipx-node \fIn\fB:\fIm
336 Set the IPX node numbers. The two node numbers are separated from each
337 other with a colon character. The first number \fIn\fR is the local
338 node number. The second number \fIm\fR is the peer's node number. Each
339 node number is a hexadecimal number, at most 10 digits long. The node
340 numbers on the ipx-network must be unique. There is no valid
341 default. If this option is not specified then the node numbers are
342 obtained from the peer.
344 .B ipx-router-name \fI<string>
345 Set the name of the router. This is a string and is sent to the peer
349 Set the routing protocol to be received by this option. More than one
350 instance of \fIipx-routing\fR may be specified. The '\fInone\fR'
351 option (0) may be specified as the only instance of ipx-routing. The
352 values may be \fI0\fR for \fINONE\fR, \fI2\fR for \fIRIP/SAP\fR, and
353 \fI4\fR for \fINLSP\fR.
355 .B ipxcp-accept-local
356 Accept the peer's NAK for the node number specified in the ipx-node
357 option. If a node number was specified, and non-zero, the default is
358 to insist that the value be used. If you include this option then you
359 will permit the peer to override the entry of the node number.
361 .B ipxcp-accept-network
362 Accept the peer's NAK for the network number specified in the
363 ipx-network option. If a network number was specified, and non-zero, the
364 default is to insist that the value be used. If you include this
365 option then you will permit the peer to override the entry of the node
368 .B ipxcp-accept-remote
369 Use the peer's network number specified in the configure request
370 frame. If a node number was specified for the peer and this option was
371 not specified, the peer will be forced to use the value which you have
374 .B ipxcp-max-configure \fIn
375 Set the maximum number of IPXCP configure request frames which the
376 system will send to \fIn\fR. The default is 10.
378 .B ipxcp-max-failure \fIn
379 Set the maximum number of IPXCP NAK frames which the local system will
380 send before it rejects the options. The default value is 3.
382 .B ipxcp-max-terminate \fIn
383 Set the maximum nuber of IPXCP terminate request frames before the
384 local system considers that the peer is not listening to them. The
388 Enable debugging code in the kernel-level PPP driver. The argument
389 \fIn\fR is a number which is the sum of the following values: 1 to
390 enable general debug messages, 2 to request that the contents of
391 received packets be printed, and 4 to request that the contents of
392 transmitted packets be printed. On most systems, messages printed by
393 the kernel are logged by syslog(1) to a file as directed in the
394 /etc/syslog.conf configuration file.
396 .B lcp-echo-failure \fIn
397 If this option is given, pppd will presume the peer to be dead
398 if \fIn\fR LCP echo-requests are sent without receiving a valid LCP
399 echo-reply. If this happens, pppd will terminate the
400 connection. Use of this option requires a non-zero value for the
401 \fIlcp-echo-interval\fR parameter. This option can be used to enable
402 pppd to terminate after the physical connection has been broken
403 (e.g., the modem has hung up) in situations where no hardware modem
404 control lines are available.
406 .B lcp-echo-interval \fIn
407 If this option is given, pppd will send an LCP echo-request frame to
408 the peer every \fIn\fR seconds. Normally the peer should respond to
409 the echo-request by sending an echo-reply. This option can be used
410 with the \fIlcp-echo-failure\fR option to detect that the peer is no
413 .B lcp-max-configure \fIn
414 Set the maximum number of LCP configure-request transmissions to
415 \fIn\fR (default 10).
417 .B lcp-max-failure \fIn
418 Set the maximum number of LCP configure-NAKs returned before starting
419 to send configure-Rejects instead to \fIn\fR (default 10).
421 .B lcp-max-terminate \fIn
422 Set the maximum number of LCP terminate-request transmissions to
426 Set the LCP restart interval (retransmission timeout) to \fIn\fR
430 Don't use the modem control lines. With this option, pppd will ignore
431 the state of the CD (Carrier Detect) signal from the modem and will
432 not change the state of the DTR (Data Terminal Ready) signal.
435 Send log messages to file descriptor \fIn\fR. Pppd will send log
436 messages to at most one file or file descriptor (as well as sending
437 the log messages to syslog), so this option and the \fBlogfile\fR
438 option are mutually exclusive. The default is for pppd to send log
439 messages to stdout (file descriptor 1), unless the serial port is
440 already open on stdout.
442 .B logfile \fIfilename
443 Append log messages to the file \fIfilename\fR (as well as sending the
444 log messages to syslog). The file is opened with the privileges of
445 the user who invoked pppd, in append mode.
447 Use the system password database for authenticating the peer using
448 PAP, and record the user in the system wtmp file. Note that the peer
449 must have an entry in the /etc/ppp/pap-secrets file as well as the
450 system password database to be allowed access.
453 Terminate the connection when it has been available for network
454 traffic for \fIn\fR seconds (i.e. \fIn\fR seconds after the first
455 network control protocol comes up).
458 Use the modem control lines. This option is the default. With this
459 option, pppd will wait for the CD (Carrier Detect) signal from the
460 modem to be asserted when opening the serial device (unless a connect
461 script is specified), and it will drop the DTR (Data Terminal Ready)
462 signal briefly when the connection is terminated and before executing
463 the connect script. On Ultrix, this option implies hardware flow
464 control, as for the \fIcrtscts\fR option.
467 If pppd is acting as a server for Microsoft Windows clients, this
468 option allows pppd to supply one or two DNS (Domain Name Server)
469 addresses to the clients. The first instance of this option specifies
470 the primary DNS address; the second instance (if given) specifies the
471 secondary DNS address. (This option was present in some older
472 versions of pppd under the name \fBdns-addr\fR.)
475 If pppd is acting as a server for Microsoft Windows or "Samba"
476 clients, this option allows pppd to supply one or two WINS (Windows
477 Internet Name Services) server addresses to the clients. The first
478 instance of this option specifies the primary WINS address; the second
479 instance (if given) specifies the secondary WINS address.
482 Set the name of the local system for authentication purposes to
483 \fIname\fR. This is a privileged option. With this option, pppd will
484 use lines in the secrets files which have \fIname\fR as the second
485 field when looking for a secret to use in authenticating the peer. In
486 addition, unless overridden with the \fIuser\fR option, \fIname\fR
487 will be used as the name to send to the peer when authenticating the
488 local system to the peer. (Note that pppd does not append the domain
492 Set the interface netmask to \fIn\fR, a 32 bit netmask in "decimal dot"
493 notation (e.g. 255.255.255.0). If this option is given, the value
494 specified is ORed with the default netmask. The default netmask is
495 chosen based on the negotiated remote IP address; it is the
496 appropriate network mask for the class of the remote IP address, ORed
497 with the netmasks for any non point-to-point network interfaces in the
498 system which are on the same network. (Note: on some platforms, pppd
499 will always use 255.255.255.255 for the netmask, if that is the only
500 appropriate value for a point-to-point interface.)
503 Disable Address/Control compression in both directions (send and
507 Do not require the peer to authenticate itself. This option is
511 Disables BSD-Compress compression; \fBpppd\fR will not request or
512 agree to compress packets using the BSD-Compress scheme.
515 Disable CCP (Compression Control Protocol) negotiation. This option
516 should only be required if the peer is buggy and gets confused by
517 requests from pppd for CCP negotiation.
520 Disable hardware flow control (i.e. RTS/CTS) on the serial port.
521 If neither the \fIcrtscts\fR nor the \fInocrtscts\fR nor the
522 \fIcdtrcts\fR nor the \fInodtrcts\fR option is given, the hardware
523 flow control setting for the serial port is left unchanged.
526 This option is a synonym for \fInocrtscts\fR. Either of these options will
527 disable both forms of hardware flow control.
530 Disable the \fIdefaultroute\fR option. The system administrator who
531 wishes to prevent users from creating default routes with pppd
532 can do so by placing this option in the /etc/ppp/options file.
535 Disables Deflate compression; pppd will not request or agree to
536 compress packets using the Deflate scheme.
539 Don't detach from the controlling terminal. Without this option, if a
540 serial device other than the terminal on the standard input is
541 specified, pppd will fork to become a background process.
544 Disable IPCP negotiation and IP communication. This option should
545 only be required if the peer is buggy and gets confused by requests
546 from pppd for IPCP negotiation.
549 Disables the default behaviour when no local IP address is specified,
550 which is to determine (if possible) the local IP address from the
551 hostname. With this option, the peer will have to supply the local IP
552 address during IPCP negotiation (unless it specified explicitly on the
553 command line or in an options file).
556 Disable the IPXCP and IPX protocols. This option should only be
557 required if the peer is buggy and gets confused by requests from pppd
558 for IPXCP negotiation.
561 Do not send log messages to a file or file descriptor. This option
562 cancels the \fBlogfd\fR and \fBlogfile\fR options.
564 Disable magic number negotiation. With this option, pppd cannot
565 detect a looped-back line. This option should only be needed if the
569 Disable protocol field compression negotiation in both the receive and
570 the transmit direction.
573 Exit once a connection has been made and terminated. This is the
574 default unless the \fIpersist\fR or \fIdemand\fR option has been
578 Do not accept or agree to Predictor-1 comprssion.
581 Disable the \fIproxyarp\fR option. The system administrator who
582 wishes to prevent users from creating proxy ARP entries with pppd can
583 do so by placing this option in the /etc/ppp/options file.
586 Normally, pppd requires a terminal device. With this option, pppd
587 will allocate itself a pseudo-tty master/slave pair and use the slave
588 as its terminal device. Pppd will create a child process to act as a
589 `character shunt' to transfer characters between the pseudo-tty master
590 and its standard input and output. Thus pppd will transmit characters
591 on its standard output and receive characters on its standard input
592 even if they are not terminal devices. This option increases the
593 latency and CPU overhead of transferring data over the ppp interface
594 as all of the characters sent and received must flow through the
595 character shunt process. An explicit device name may not be given if
599 Disable Van Jacobson style TCP/IP header compression in both the
600 transmit and the receive direction.
603 Disable the connection-ID compression option in Van Jacobson style
604 TCP/IP header compression. With this option, pppd will not omit the
605 connection-ID byte from Van Jacobson compressed TCP/IP headers, nor
606 ask the peer to do so.
609 Indicates that all secrets in the /etc/ppp/pap-secrets file which are
610 used for checking the identity of the peer are encrypted, and thus
611 pppd should not accept a password which, before encryption, is
612 identical to the secret from the /etc/ppp/pap-secrets file.
614 .B pap-max-authreq \fIn
615 Set the maximum number of PAP authenticate-request transmissions to
616 \fIn\fR (default 10).
619 Set the PAP restart interval (retransmission timeout) to \fIn\fR
623 Set the maximum time that pppd will wait for the peer to authenticate
624 itself with PAP to \fIn\fR seconds (0 means no limit).
626 .B pass-filter \fIfilter-expression
627 Specifies a packet filter to applied to data packets being sent or
628 received to determine which packets should be allowed to pass.
629 Packets which are rejected by the filter are silently discarded. This
630 option can be used to prevent specific network daemons (such as
631 routed) using up link bandwidth, or to provide a basic firewall
633 The \fIfilter-expression\fR syntax is as described for tcpdump(1),
634 except that qualifiers which are inappropriate for a PPP link, such as
635 \fBether\fR and \fBarp\fR, are not permitted. Generally the filter
636 expression should be enclosed in single-quotes to prevent whitespace
637 in the expression from being interpreted by the shell. Note that it
638 is possible to apply different constraints to incoming and outgoing
639 packets using the \fBinbound\fR and \fBoutbound\fR qualifiers. This
640 option is currently only available under NetBSD, and then only if both
641 the kernel and pppd were compiled with PPP_FILTER defined.
644 Do not exit after a connection is terminated; instead try to reopen
648 Request that the peer compress frames that it sends using Predictor-1
649 compression, and agree to compress transmitted frames with Predictor-1
650 if requested. This option has no effect unless the kernel driver
651 supports Predictor-1 compression.
653 .B privgroup \fIgroup-name
654 Allows members of group \fIgroup-name\fR to use privileged options.
655 This is a privileged option. Use of this option requires care as
656 there is no guarantee that members of \fIgroup-name\fR cannot use pppd
657 to become root themselves. Consider it equivalent to putting the
658 members of \fIgroup-name\fR in the kmem or disk group.
661 Add an entry to this system's ARP [Address Resolution Protocol] table
662 with the IP address of the peer and the Ethernet address of this
663 system. This will have the effect of making the peer appear to other
664 systems to be on the local ethernet.
667 Specifies that the command \fIscript\fR is to be used to communicate
668 rather than a specific terminal device. Pppd will allocate itself a
669 pseudo-tty master/slave pair and use the slave as its terminal
670 device. The \fIscript\fR will be run in a child process with the
671 pseudo-tty master as its standard input and output. An explicit
672 device name may not be given if this option is used.
675 With this option, pppd will accept all control characters from the
676 peer, including those marked in the receive asyncmap. Without this
677 option, pppd will discard those characters as specified in RFC1662.
678 This option should only be needed if the peer is buggy.
680 .B record \fIfilename
681 Specifies that pppd should record all characters sent and received to
682 a file named \fIfilename\fR. This file is opened in append mode,
683 using the user's user-ID and permissions. This option is implemented
684 using a pseudo-tty and a process to transfer characters between the
685 pseudo-tty and the real serial device, so it will increase the latency
686 and CPU overhead of transferring data over the ppp interface. The
687 characters are stored in a tagged format with timestamps, which can be
688 displayed in readable form using the pppdump(8) program.
690 .B remotename \fIname
691 Set the assumed name of the remote system for authentication purposes
695 With this option, pppd will not agree to authenticate itself to the
699 With this option, pppd will not agree to authenticate itself to the
703 Require the peer to authenticate itself using CHAP [Challenge
704 Handshake Authentication Protocol] authentication.
707 Require the peer to authenticate itself using PAP [Password
708 Authentication Protocol] authentication.
711 With this option, pppd will not transmit LCP packets to initiate a
712 connection until a valid LCP packet is received from the peer (as for
713 the `passive' option with ancient versions of pppd).
716 Use synchronous HDLC serial encoding instead of asynchronous.
717 The device used by pppd with this option must have sync support.
718 Currently supports Microgate SyncLink adapters
719 under Linux and FreeBSD 2.2.8 and later.
722 With this option, pppd will detach from its controlling terminal once
723 it has successfully established the ppp connection (to the point where
724 the first network control protocol, usually the IP control protocol,
728 Enforce the use of the hostname (with domain name appended, if given)
729 as the name of the local system for authentication purposes (overrides
730 the \fIname\fR option). This option is not normally needed since the
731 \fIname\fR option is privileged.
734 Ask the peer for up to 2 DNS server addresses. The addresses supplied
735 by the peer (if any) are passed to the /etc/ppp/ip-up script in the
736 environment variables DNS1 and DNS2.
739 Sets the name used for authenticating the local system to the peer to
743 Sets the number of connection slots to be used by the Van Jacobson
744 TCP/IP header compression and decompression code to \fIn\fR, which
745 must be between 2 and 16 (inclusive).
748 Run the executable or shell command specified by \fIscript\fR before
749 initiating PPP negotiation, after the connect script (if any) has
750 completed. A value for this option from a privileged source cannot be
751 overridden by a non-privileged user.
754 Use software flow control (i.e. XON/XOFF) to control the flow of data on
757 Options can be taken from files as well as the command line. Pppd
758 reads options from the files /etc/ppp/options, ~/.ppprc and
759 /etc/ppp/options.\fIttyname\fR (in that order) before processing the
760 options on the command line. (In fact, the command-line options are
761 scanned to find the terminal name before the options.\fIttyname\fR
762 file is read.) In forming the name of the options.\fIttyname\fR file,
763 the initial /dev/ is removed from the terminal name, and any remaining
764 / characters are replaced with dots.
766 An options file is parsed into a series of words, delimited by
767 whitespace. Whitespace can be included in a word by enclosing the
768 word in double-quotes ("). A backslash (\\) quotes the following character.
769 A hash (#) starts a comment, which continues until the end of the
770 line. There is no restriction on using the \fIfile\fR or \fIcall\fR
771 options within an options file.
774 provides system administrators with sufficient access control that PPP
775 access to a server machine can be provided to legitimate users without
776 fear of compromising the security of the server or the network it's
777 on. This control is provided through restrictions on which IP
778 addresses the peer may use, based on its authenticated identity (if
779 any), and through restrictions on which options a non-privileged user
780 may use. Several of pppd's options are privileged, in particular
781 those which permit potentially insecure configurations; these options
782 are only accepted in files which are under the control of the system
783 administrator, or if pppd is being run by root.
785 The default behaviour of pppd is to allow an unauthenticated peer to
786 use a given IP address only if the system does not already have a
787 route to that IP address. For example, a system with a
788 permanent connection to the wider internet will normally have a
789 default route, and thus all peers will have to authenticate themselves
790 in order to set up a connection. On such a system, the \fIauth\fR
791 option is the default. On the other hand, a system where the
792 PPP link is the only connection to the internet will not normally have
793 a default route, so the peer will be able to use almost any IP address
794 without authenticating itself.
796 As indicated above, some security-sensitive options are privileged,
797 which means that they may not be used by an ordinary non-privileged
798 user running a setuid-root pppd, either on the command line, in the
799 user's ~/.ppprc file, or in an options file read using the \fIfile\fR
800 option. Privileged options may be used in /etc/ppp/options file or in
801 an options file read using the \fIcall\fR option. If pppd is being
802 run by the root user, privileged options can be used without
805 When opening the device, pppd uses either the invoking user's user ID
806 or the root UID (that is, 0), depending on whether the device name was
807 specified by the user or the system administrator. If the device name
808 comes from a privileged source, that is, /etc/ppp/options or an
809 options file read using the \fIcall\fR option, pppd uses full root
810 privileges when opening the device. Thus, by creating an appropriate
811 file under /etc/ppp/peers, the system administrator can allow users to
812 establish a ppp connection via a device which they would not normally
813 have permission to access. Otherwise pppd uses the invoking user's
814 real UID when opening the device.
816 Authentication is the process whereby one peer convinces the other of
817 its identity. This involves the first peer sending its name to the
818 other, together with some kind of secret information which could only
819 come from the genuine authorized user of that name. In such an
820 exchange, we will call the first peer the "client" and the other the
821 "server". The client has a name by which it identifies itself to the
822 server, and the server also has a name by which it identifies itself
823 to the client. Generally the genuine client shares some secret (or
824 password) with the server, and authenticates itself by proving that it
825 knows that secret. Very often, the names used for authentication
826 correspond to the internet hostnames of the peers, but this is not
829 At present, pppd supports two authentication protocols: the Password
830 Authentication Protocol (PAP) and the Challenge Handshake
831 Authentication Protocol (CHAP). PAP involves the client sending its
832 name and a cleartext password to the server to authenticate itself.
833 In contrast, the server initiates the CHAP authentication exchange by
834 sending a challenge to the client (the challenge packet includes the
835 server's name). The client must respond with a response which
836 includes its name plus a hash value derived from the shared secret and
837 the challenge, in order to prove that it knows the secret.
839 The PPP protocol, being symmetrical, allows both peers to require the
840 other to authenticate itself. In that case, two separate and
841 independent authentication exchanges will occur. The two exchanges
842 could use different authentication protocols, and in principle,
843 different names could be used in the two exchanges.
845 The default behaviour of pppd is to agree to authenticate if
846 requested, and to not require authentication from the peer. However,
847 pppd will not agree to authenticate itself with a particular protocol
848 if it has no secrets which could be used to do so.
850 Pppd stores secrets for use in authentication in secrets
851 files (/etc/ppp/pap-secrets for PAP, /etc/ppp/chap-secrets for CHAP).
852 Both secrets files have the same format. The secrets files can
853 contain secrets for pppd to use in authenticating itself to other
854 systems, as well as secrets for pppd to use when authenticating other
857 Each line in a secrets file contains one secret. A given secret is
858 specific to a particular combination of client and server - it can
859 only be used by that client to authenticate itself to that server.
860 Thus each line in a secrets file has at least 3 fields: the name of
861 the client, the name of the server, and the secret. These fields may
862 be followed by a list of the IP addresses that the specified client
863 may use when connecting to the specified server.
865 A secrets file is parsed into words as for a options file, so the
866 client name, server name and secrets fields must each be one word,
867 with any embedded spaces or other special characters quoted or
868 escaped. Any following words on the same line are taken to be a list
869 of acceptable IP addresses for that client. If there are only 3 words
870 on the line, or if the first word is "-", then all IP addresses are
871 disallowed. To allow any address, use "*".
872 A word starting with "!" indicates that the
873 specified address is \fInot\fR acceptable. An address may be followed
874 by "/" and a number \fIn\fR, to indicate a whole subnet, i.e. all
875 addresses which have the same value in the most significant \fIn\fR
876 bits. Note that case is significant in the client and server names
879 If the secret starts with an `@', what follows is assumed to be the
880 name of a file from which to read the secret. A "*" as the client or
881 server name matches any name. When selecting a secret, pppd takes the
882 best match, i.e. the match with the fewest wildcards.
884 Thus a secrets file contains both secrets for use in authenticating
885 other hosts, plus secrets which we use for authenticating ourselves to
886 others. When pppd is authenticating the peer (checking the peer's
887 identity), it chooses a secret with the peer's name in the first
888 field and the name of the local system in the second field. The
889 name of the local system defaults to the hostname, with the domain
890 name appended if the \fIdomain\fR option is used. This default can be
891 overridden with the \fIname\fR option, except when the
892 \fIusehostname\fR option is used.
894 When pppd is choosing a secret to use in authenticating itself to the
895 peer, it first determines what name it is going to use to identify
896 itself to the peer. This name can be specified by the user with the
897 \fIuser\fR option. If this option is not used, the name defaults to
898 the name of the local system, determined as described in the previous
899 paragraph. Then pppd looks for a secret with this name in the first
900 field and the peer's name in the second field. Pppd will know the
901 name of the peer if CHAP authentication is being used, because the
902 peer will have sent it in the challenge packet. However, if PAP is being
903 used, pppd will have to determine the peer's name from the options
904 specified by the user. The user can specify the peer's name directly
905 with the \fIremotename\fR option. Otherwise, if the remote IP address
906 was specified by a name (rather than in numeric form), that name will
907 be used as the peer's name. Failing that, pppd will use the null
908 string as the peer's name.
910 When authenticating the peer with PAP, the supplied password is first
911 compared with the secret from the secrets file. If the password
912 doesn't match the secret, the password is encrypted using crypt() and
913 checked against the secret again. Thus secrets for authenticating the
914 peer can be stored in encrypted form if desired. If the
915 \fIpapcrypt\fR option is given, the first (unencrypted) comparison is
916 omitted, for better security.
918 Furthermore, if the \fIlogin\fR option was specified, the username and
919 password are also checked against the system password database. Thus,
920 the system administrator can set up the pap-secrets file to allow PPP
921 access only to certain users, and to restrict the set of IP addresses
922 that each user can use. Typically, when using the \fIlogin\fR option,
923 the secret in /etc/ppp/pap-secrets would be "", which will match any
924 password supplied by the peer. This avoids the need to have the same
925 secret in two places.
927 Authentication must be satisfactorily completed before IPCP (or any
928 other Network Control Protocol) can be started. If the peer is
929 required to authenticate itself, and fails to do so, pppd will
930 terminated the link (by closing LCP). If IPCP negotiates an
931 unacceptable IP address for the remote host, IPCP will be closed. IP
932 packets can only be sent or received when IPCP is open.
934 In some cases it is desirable to allow some hosts which can't
935 authenticate themselves to connect and use one of a restricted set of
936 IP addresses, even when the local host generally requires
937 authentication. If the peer refuses to authenticate itself when
938 requested, pppd takes that as equivalent to authenticating with PAP
939 using the empty string for the username and password. Thus, by adding
940 a line to the pap-secrets file which specifies the empty string for
941 the client and password, it is possible to allow restricted access to
942 hosts which refuse to authenticate themselves.
945 When IPCP negotiation is completed successfully, pppd will inform the
946 kernel of the local and remote IP addresses for the ppp interface.
947 This is sufficient to create a host route to the remote end of the
948 link, which will enable the peers to exchange IP packets.
949 Communication with other machines generally requires further
950 modification to routing tables and/or ARP (Address Resolution
951 Protocol) tables. In most cases the \fIdefaultroute\fR and/or
952 \fIproxyarp\fR options are sufficient for this, but in some cases
953 further intervention is required. The /etc/ppp/ip-up script can be
956 Sometimes it is desirable to add a default route through the remote
957 host, as in the case of a machine whose only connection to the
958 Internet is through the ppp interface. The \fIdefaultroute\fR option
959 causes pppd to create such a default route when IPCP comes up, and
960 delete it when the link is terminated.
962 In some cases it is desirable to use proxy ARP, for example on a
963 server machine connected to a LAN, in order to allow other hosts to
964 communicate with the remote host. The \fIproxyarp\fR option causes
965 pppd to look for a network interface on the same subnet as the remote
966 host (an interface supporting broadcast and ARP, which is up and not a
967 point-to-point or loopback interface). If found, pppd creates a
968 permanent, published ARP entry with the IP address of the remote host
969 and the hardware address of the network interface found.
971 When the \fIdemand\fR option is used, the interface IP addresses have
972 already been set at the point when IPCP comes up. If pppd has not
973 been able to negotiate the same addresses that it used to configure
974 the interface (for example when the peer is an ISP that uses dynamic
975 IP address assignment), pppd has to change the interface IP addresses
976 to the negotiated addresses. This may disrupt existing connections,
977 and the use of demand dialling with peers that do dynamic IP address
978 assignment is not recommended.
981 The following examples assume that the /etc/ppp/options file contains
982 the \fIauth\fR option (as in the default /etc/ppp/options file in the
985 Probably the most common use of pppd is to dial out to an ISP. This
986 can be done with a command such as
990 where the /etc/ppp/peers/isp file is set up by the system
991 administrator to contain something like this:
995 connect '/usr/sbin/chat -v -f /etc/ppp/chat-isp'
999 In this example, we are using chat to dial the ISP's modem and go
1000 through any logon sequence required. The /etc/ppp/chat-isp file
1001 contains the script used by chat; it could for example contain
1002 something like this:
1014 ABORT "Username/Password Incorrect"
1022 "name:" "^Umyuserid"
1024 "word:" "\\qmypassword"
1030 See the chat(8) man page for details of chat scripts.
1032 Pppd can also be used to provide a dial-in ppp service for users. If
1033 the users already have login accounts, the simplest way to set up the
1034 ppp service is to let the users log in to their accounts and run pppd
1035 (installed setuid-root) with a command such as
1039 To allow a user to use the PPP facilities, you need to allocate an IP
1040 address for that user's machine and create an entry in
1041 /etc/ppp/pap-secrets or /etc/ppp/chap-secrets (depending on which
1042 authentication method the PPP implementation on the user's machine
1043 supports), so that the user's
1044 machine can authenticate itself. For example, if Joe has a machine
1045 called "joespc" which is to be allowed to dial in to the machine
1046 called "server" and use the IP address joespc.my.net, you would add an
1047 entry like this to /etc/ppp/pap-secrets or /etc/ppp/chap-secrets:
1049 joespc server "joe's secret" joespc.my.net
1051 Alternatively, you can create a username called (for example) "ppp",
1052 whose login shell is pppd and whose home directory is /etc/ppp.
1053 Options to be used when pppd is run this way can be put in
1056 If your serial connection is any more complicated than a piece of
1057 wire, you may need to arrange for some control characters to be
1058 escaped. In particular, it is often useful to escape XON (^Q) and
1059 XOFF (^S), using \fIasyncmap a0000\fR. If the path includes a telnet,
1060 you probably should escape ^] as well (\fIasyncmap 200a0000\fR). If
1061 the path includes an rlogin, you will need to use the \fIescape ff\fR
1062 option on the end which is running the rlogin client, since many
1063 rlogin implementations are not transparent; they will remove the
1064 sequence [0xff, 0xff, 0x73, 0x73, followed by any 8 bytes] from the
1068 Messages are sent to the syslog daemon using facility LOG_DAEMON.
1069 (This can be overriden by recompiling pppd with the macro
1070 LOG_PPP defined as the desired facility.) In order to see the error
1071 and debug messages, you will need to edit your /etc/syslog.conf file
1072 to direct the messages to the desired output device or file.
1074 The \fIdebug\fR option causes the contents of all control packets sent
1075 or received to be logged, that is, all LCP, PAP, CHAP or IPCP packets.
1076 This can be useful if the PPP negotiation does not succeed or if
1077 authentication fails.
1078 If debugging is enabled at compile time, the \fIdebug\fR option also
1079 causes other debugging messages to be logged.
1081 Debugging can also be enabled or disabled by sending a SIGUSR1 signal
1082 to the pppd process. This signal acts as a toggle.
1084 The exit status of pppd is set to indicate whether any error was
1085 detected, or the reason for the link being terminated. The values
1089 Pppd has detached, or otherwise the connection was successfully
1090 established and terminated at the peer's request.
1093 An immediately fatal error of some kind occurred, such as an essential
1094 system call failing, or running out of virtual memory.
1097 An error was detected in processing the options given, such as two
1098 mutually exclusive options being used.
1101 Pppd is not setuid-root and the invoking user is not root.
1104 The kernel does not support PPP, for example, the PPP kernel driver is
1105 not included or cannot be loaded.
1108 Pppd terminated because it was sent a SIGINT, SIGTERM or SIGHUP
1112 The serial port could not be locked.
1115 The serial port could not be opened.
1118 The connect script failed (returned a non-zero exit status).
1121 The command specified as the argument to the \fIpty\fR option could
1125 The PPP negotiation failed, that is, it didn't reach the point where
1126 at least one network protocol (e.g. IP) was running.
1129 The peer system failed (or refused) to authenticate itself.
1132 The link was established successfully and terminated because it was
1136 The link was established successfully and terminated because the
1137 connect time limit was reached.
1140 Callback was negotiated and an incoming call should arrive shortly.
1143 The link was terminated because the peer is not responding to echo
1147 The link was terminated by the modem hanging up.
1150 The PPP negotiation failed because serial loopback was detected.
1153 The init script failed (returned a non-zero exit status).
1155 Pppd invokes scripts at various stages in its processing which can be
1156 used to perform site-specific ancillary processing. These scripts are
1157 usually shell scripts, but could be executable code files instead.
1158 Pppd does not wait for the scripts to finish. The scripts are
1159 executed as root (with the real and effective user-id set to 0), so
1160 that they can do things such as update routing tables or run
1161 privileged daemons. Be careful that the contents of these scripts do
1162 not compromise your system's security. Pppd runs the scripts with
1163 standard input, output and error redirected to /dev/null, and with an
1164 environment that is empty except for some environment variables that
1165 give information about the link. The environment variables that pppd
1169 The name of the serial tty device being used.
1172 The name of the network interface being used.
1175 The IP address for the local end of the link. This is only set when
1179 The IP address for the remote end of the link. This is only set when
1183 The authenticated name of the peer. This is only set if the peer
1184 authenticates itself.
1187 The baud rate of the tty device.
1190 The real user-id of the user who invoked pppd.
1193 The username of the real user-id that invoked pppd. This is always set.
1195 For the ip-down and auth-down scripts, pppd also sets the following
1196 variables giving statistics for the connection:
1199 The number of seconds from when the PPP negotiation started until the
1200 connection was terminated.
1203 The number of bytes sent (at the level of the serial port) during the
1207 The number of bytes received (at the level of the serial port) during
1210 Pppd invokes the following scripts, if they exist. It is not an error
1211 if they don't exist.
1214 A program or script which is executed after the remote system
1215 successfully authenticates itself. It is executed with the parameters
1217 \fIinterface-name peer-name user-name tty-device speed\fR
1219 Note that this script is not executed if the peer doesn't authenticate
1220 itself, for example when the \fInoauth\fR option is used.
1222 .B /etc/ppp/auth-down
1223 A program or script which is executed when the link goes down, if
1224 /etc/ppp/auth-up was previously executed. It is executed in the same
1225 manner with the same parameters as /etc/ppp/auth-up.
1228 A program or script which is executed when the link is available for
1229 sending and receiving IP packets (that is, IPCP has come up). It is
1230 executed with the parameters
1232 \fIinterface-name tty-device speed local-IP-address
1233 remote-IP-address ipparam\fR
1236 A program or script which is executed when the link is no longer
1237 available for sending and receiving IP packets. This script can be
1238 used for undoing the effects of the /etc/ppp/ip-up script. It is
1239 invoked in the same manner and with the same parameters as the ip-up
1243 A program or script which is executed when the link is available for
1244 sending and receiving IPX packets (that is, IPXCP has come up). It is
1245 executed with the parameters
1247 \fIinterface-name tty-device speed network-number local-IPX-node-address
1248 remote-IPX-node-address local-IPX-routing-protocol remote-IPX-routing-protocol
1249 local-IPX-router-name remote-IPX-router-name ipparam pppd-pid\fR
1251 The local-IPX-routing-protocol and remote-IPX-routing-protocol field
1252 may be one of the following:
1254 NONE to indicate that there is no routing protocol
1256 RIP to indicate that RIP/SAP should be used
1258 NLSP to indicate that Novell NLSP should be used
1260 RIP NLSP to indicate that both RIP/SAP and NLSP should be used
1262 .B /etc/ppp/ipx-down
1263 A program or script which is executed when the link is no longer
1264 available for sending and receiving IPX packets. This script can be
1265 used for undoing the effects of the /etc/ppp/ipx-up script. It is
1266 invoked in the same manner and with the same parameters as the ipx-up
1270 .B /var/run/ppp\fIn\fB.pid \fR(BSD or Linux), \fB/etc/ppp/ppp\fIn\fB.pid \fR(others)
1271 Process-ID for pppd process on ppp interface unit \fIn\fR.
1273 .B /etc/ppp/pap-secrets
1274 Usernames, passwords and IP addresses for PAP authentication. This
1275 file should be owned by root and not readable or writable by any other
1276 user. Pppd will log a warning if this is not the case.
1278 .B /etc/ppp/chap-secrets
1279 Names, secrets and IP addresses for CHAP authentication. As for
1280 /etc/ppp/pap-secrets, this file should be owned by root and not
1281 readable or writable by any other user. Pppd will log a warning if
1282 this is not the case.
1285 System default options for pppd, read before user default options or
1286 command-line options.
1289 User default options, read before /etc/ppp/options.\fIttyname\fR.
1291 .B /etc/ppp/options.\fIttyname
1292 System default options for the serial port being used, read after
1293 ~/.ppprc. In forming the \fIttyname\fR part of this
1294 filename, an initial /dev/ is stripped from the port name (if
1295 present), and any slashes in the remaining part are converted to
1299 A directory containing options files which may contain privileged
1300 options, even if pppd was invoked by a user other than root. The
1301 system administrator can create options files in this directory to
1302 permit non-privileged users to dial out without requiring the peer to
1303 authenticate, but only to certain trusted peers.
1308 \fICompressing TCP/IP headers for low-speed serial links.\fR
1313 .I The MD5 Message-Digest Algorithm.
1318 .I PPP Internet Protocol Control Protocol (IPCP).
1322 Lloyd, B.; Simpson, W.A.
1323 .I PPP authentication protocols.
1328 .I The Point\-to\-Point Protocol (PPP).
1333 .I PPP in HDLC-like Framing.
1336 The following signals have the specified effect when sent to pppd.
1339 These signals cause pppd to terminate the link (by closing LCP),
1340 restore the serial device settings, and exit.
1343 This signal causes pppd to terminate the link, restore the serial
1344 device settings, and close the serial device. If the \fIpersist\fR or
1345 \fIdemand\fR option has been specified, pppd will try to reopen the
1346 serial device and start another connection (after the holdoff period).
1347 Otherwise pppd will exit. If this signal is received during the
1348 holdoff period, it causes pppd to end the holdoff period immediately.
1351 This signal toggles the state of the \fIdebug\fR option.
1354 This signal causes pppd to renegotiate compression. This can be
1355 useful to re-enable compression after it has been disabled as a result
1356 of a fatal decompression error. (Fatal decompression errors generally
1357 indicate a bug in one or other implementation.)
1360 Paul Mackerras (Paul.Mackerras@cs.anu.edu.au), based on earlier work by
projects / ppp.git / blob