summary |
shortlog |
log |
commit | commitdiff |
tree
raw |
patch |
inline | side by side (from parent 1:
4ed9d22)
Without this patch "-" is rendered as the endash in unicode
consoles and then bad things happen. From Marco d'Itri.
.\" -*- nroff -*-
.\" manual page [] for chat 1.8
.\" -*- nroff -*-
.\" manual page [] for chat 1.8
-.\" $Id: chat.8,v 1.10 2002/01/11 18:02:45 etbe Exp $
+.\" $Id: chat.8,v 1.11 2004/11/13 12:22:49 paulus Exp $
.\" SH section heading
.\" SS subsection heading
.\" LP paragraph
.\" SH section heading
.\" SS subsection heading
.\" LP paragraph
the remote's \fIpppd\fR process.
.SH OPTIONS
.TP
the remote's \fIpppd\fR process.
.SH OPTIONS
.TP
Read the chat script from the chat \fIfile\fR. The use of this option
is mutually exclusive with the chat script parameters. The user must
have read access to the file. Multiple lines are permitted in the
file. Space or horizontal tab characters should be used to separate
the strings.
.TP
Read the chat script from the chat \fIfile\fR. The use of this option
is mutually exclusive with the chat script parameters. The user must
have read access to the file. Multiple lines are permitted in the
file. Space or horizontal tab characters should be used to separate
the strings.
.TP
Set the timeout for the expected string to be received. If the string
is not received within the time limit then the reply string is not
sent. An alternate reply may be sent or the script will fail if there
is no alternate reply string. A failed script will cause the
\fIchat\fR program to terminate with a non-zero error code.
.TP
Set the timeout for the expected string to be received. If the string
is not received within the time limit then the reply string is not
sent. An alternate reply may be sent or the script will fail if there
is no alternate reply string. A failed script will cause the
\fIchat\fR program to terminate with a non-zero error code.
.TP
Set the file for output of the report strings. If you use the keyword
\fIREPORT\fR, the resulting strings are written to this file. If this
option is not used and you still use \fIREPORT\fR keywords, the
\fIstderr\fR file is used for the report strings.
.TP
Set the file for output of the report strings. If you use the keyword
\fIREPORT\fR, the resulting strings are written to this file. If this
option is not used and you still use \fIREPORT\fR keywords, the
\fIstderr\fR file is used for the report strings.
.TP
Start with the echo option turned on. Echoing may also be turned on
or off at specific points in the chat script by using the \fIECHO\fR
keyword. When echoing is enabled, all output from the modem is echoed
to \fIstderr\fR.
.TP
Start with the echo option turned on. Echoing may also be turned on
or off at specific points in the chat script by using the \fIECHO\fR
keyword. When echoing is enabled, all output from the modem is echoed
to \fIstderr\fR.
.TP
Enables environment variable substituion within chat scripts using the
standard \fI$xxx\fR syntax.
.TP
Enables environment variable substituion within chat scripts using the
standard \fI$xxx\fR syntax.
.TP
Request that the \fIchat\fR script be executed in a verbose mode. The
\fIchat\fR program will then log the execution state of the chat
script as well as all text received from the modem and the output
strings sent to the modem. The default is to log through the SYSLOG;
Request that the \fIchat\fR script be executed in a verbose mode. The
\fIchat\fR program will then log the execution state of the chat
script as well as all text received from the modem and the output
strings sent to the modem. The default is to log through the SYSLOG;
-the logging method may be altered with the -S and -s flags.
+the logging method may be altered with the \-S and \-s flags.
Request that the \fIchat\fR script be executed in a stderr verbose
mode. The \fIchat\fR program will then log all text received from the
modem and the output strings sent to the modem to the stderr device. This
device is usually the local console at the station running the chat or
pppd program.
.TP
Request that the \fIchat\fR script be executed in a stderr verbose
mode. The \fIchat\fR program will then log all text received from the
modem and the output strings sent to the modem to the stderr device. This
device is usually the local console at the station running the chat or
pppd program.
.TP
-.B -s
-Use stderr. All log messages from '-v' and all error messages will be
+.B \-s
+Use stderr. All log messages from '\-v' and all error messages will be
Do not use the SYSLOG. By default, error messages are sent to the
Do not use the SYSLOG. By default, error messages are sent to the
-SYSLOG. The use of -S will prevent both log messages from '-v' and
+SYSLOG. The use of \-S will prevent both log messages from '\-v' and
error messages from being sent to the SYSLOG.
.TP
error messages from being sent to the SYSLOG.
.TP
+.B \-T \fI<phone number>
Pass in an arbitary string, usually a phone number, that will be
substituted for the \\T substitution metacharacter in a send string.
.TP
Pass in an arbitary string, usually a phone number, that will be
substituted for the \\T substitution metacharacter in a send string.
.TP
-.B -U \fI<phone number 2>
+.B \-U \fI<phone number 2>
Pass in a second string, usually a phone number, that will be
substituted for the \\U substitution metacharacter in a send string.
This is useful when dialing an ISDN terminal adapter that requires two
numbers.
.TP
.B script
Pass in a second string, usually a phone number, that will be
substituted for the \\U substitution metacharacter in a send string.
This is useful when dialing an ISDN terminal adapter that requires two
numbers.
.TP
.B script
-If the script is not specified in a file with the \fI-f\fR option then
+If the script is not specified in a file with the \fI\-f\fR option then
the script is included as parameters to the \fIchat\fR program.
.SH CHAT SCRIPT
.LP
The \fIchat\fR script defines the communications.
.LP
the script is included as parameters to the \fIchat\fR program.
.SH CHAT SCRIPT
.LP
The \fIchat\fR script defines the communications.
.LP
-A script consists of one or more "expect-send" pairs of strings,
-separated by spaces, with an optional "subexpect-subsend" string pair,
+A script consists of one or more "expect\-send" pairs of strings,
+separated by spaces, with an optional "subexpect\-subsend" string pair,
separated by a dash as in the following example:
.IP
separated by a dash as in the following example:
.IP
-ogin:-BREAK-ogin: ppp ssword: hello2u2
+ogin:\-BREAK\-ogin: ppp ssword: hello2u2
.LP
This line indicates that the \fIchat\fR program should expect the string
"ogin:". If it fails to receive a login prompt within the time interval
.LP
This line indicates that the \fIchat\fR program should expect the string
"ogin:". If it fails to receive a login prompt within the time interval
should include sub-expect sequences should the original string not be
received. For example, consider the following script:
.IP
should include sub-expect sequences should the original string not be
received. For example, consider the following script:
.IP
-ogin:--ogin: ppp ssword: hello2u2
+ogin:\-\-ogin: ppp ssword: hello2u2
.LP
This would be a better script than the simple one used earlier. This would look
for the same login: prompt, however, if one was not received, a single
.LP
This would be a better script than the simple one used earlier. This would look
for the same login: prompt, however, if one was not received, a single
at the terminal via standard error. If \fBchat\fR is being run by
pppd, and pppd is running as a daemon (detached from its controlling
terminal), standard error will normally be redirected to the file
at the terminal via standard error. If \fBchat\fR is being run by
pppd, and pppd is running as a daemon (detached from its controlling
terminal), standard error will normally be redirected to the file
-/etc/ppp/connect-errors.
+/etc/ppp/connect\-errors.
.LP
\fBSAY\fR strings must be enclosed in single or double quotes. If
carriage return and line feed are needed in the string to be output,
.LP
\fBSAY\fR strings must be enclosed in single or double quotes. If
carriage return and line feed are needed in the string to be output,
ATDT5551212 to dial the telephone. The expected string is
\fICONNECT\fR. If the string \fICONNECT\fR is received the remainder
of the script is executed. In addition the program will write to the
ATDT5551212 to dial the telephone. The expected string is
\fICONNECT\fR. If the string \fICONNECT\fR is received the remainder
of the script is executed. In addition the program will write to the
-expect-file the string "CONNECT" plus any characters which follow it
+expect\-file the string "CONNECT" plus any characters which follow it
such as the connection rate.
.SH CLR_REPORT STRINGS
This sequence allows for clearing previously set \fBREPORT\fR strings.
such as the connection rate.
.SH CLR_REPORT STRINGS
This sequence allows for clearing previously set \fBREPORT\fR strings.
entries so that new strings can use that space.
.SH ECHO
The echo options controls whether the output from the modem is echoed
entries so that new strings can use that space.
.SH ECHO
The echo options controls whether the output from the modem is echoed
-to \fIstderr\fR. This option may be set with the \fI-e\fR option, but
-it can also be controlled by the \fIECHO\fR keyword. The "expect-send"
+to \fIstderr\fR. This option may be set with the \fI\-e\fR option, but
+it can also be controlled by the \fIECHO\fR keyword. The "expect\-send"
pair \fIECHO\fR \fION\fR enables echoing, and \fIECHO\fR \fIOFF\fR
disables it. With this keyword you can select which parts of the
conversation should be visible. For instance, with the following
pair \fIECHO\fR \fION\fR enables echoing, and \fIECHO\fR \fIOFF\fR
disables it. With this keyword you can select which parts of the
conversation should be visible. For instance, with the following
.br
ABORT "NO CARRIER"
.br
.br
ABORT "NO CARRIER"
.br
-ogin:--BREAK--ogin: real_account
+ogin:\-\-BREAK\-\-ogin: real_account
.br
\fIetc ...\fR
.LP
.SH TIMEOUT
.br
\fIetc ...\fR
.LP
.SH TIMEOUT
-The initial timeout value is 45 seconds. This may be changed using the \fB-t\fR
+The initial timeout value is 45 seconds. This may be changed using the \fB\-t\fR
parameter.
.LP
To change the timeout value for the next expect string, the following
example may be used:
.IP
parameter.
.LP
To change the timeout value for the next expect string, the following
example may be used:
.IP
-ATZ OK ATDT5551212 CONNECT TIMEOUT 10 ogin:--ogin: TIMEOUT 5 assword: hello2u2
+ATZ OK ATDT5551212 CONNECT TIMEOUT 10 ogin:\-\-ogin: TIMEOUT 5 assword: hello2u2
.LP
This will change the timeout to 10 seconds when it expects the login:
prompt. The timeout is then changed to 5 seconds when it looks for the
.LP
This will change the timeout to 10 seconds when it expects the login:
prompt. The timeout is then changed to 5 seconds when it looks for the
Send or expect a tab character.
.TP
.B \\\\T
Send or expect a tab character.
.TP
.B \\\\T
-Send the phone number string as specified with the \fI-T\fR option
+Send the phone number string as specified with the \fI\-T\fR option
.I (not valid in expect.)
.TP
.B \\\\U
.I (not valid in expect.)
.TP
.B \\\\U
-Send the phone number 2 string as specified with the \fI-U\fR option
+Send the phone number 2 string as specified with the \fI\-U\fR option
.I (not valid in expect.)
.TP
.B \\\\\\\\
.I (not valid in expect.)
.TP
.B \\\\\\\\
For example, the character DC1 (17) is shown as \^^Q.
.I (some characters are not valid in expect.)
.SH ENVIRONMENT VARIABLES
For example, the character DC1 (17) is shown as \^^Q.
.I (some characters are not valid in expect.)
.SH ENVIRONMENT VARIABLES
-Environment variables are available within chat scripts, if the \fI-E\fR
+Environment variables are available within chat scripts, if the \fI\-E\fR
option was specified in the command line. The metacharacter \fI$\fR is used
to introduce the name of the environment variable to substitute. If the
substition fails, because the requested environment variable is not set,
option was specified in the command line. The metacharacter \fI$\fR is used
to introduce the name of the environment variable to substitute. If the
substition fails, because the requested environment variable is not set,
.TP
.B 3
A timeout event occurred when there was an \fIexpect\fR string without
.TP
.B 3
A timeout event occurred when there was an \fIexpect\fR string without
-having a "-subsend" string. This may mean that you did not program the
+having a "\-subsend" string. This may mean that you did not program the
script correctly for the condition or that some unexpected event has
occurred and the expected string could not be found.
.TP
script correctly for the condition or that some unexpected event has
occurred and the expected string could not be found.
.TP
.\" manual page [] for pppd 2.4
.\" manual page [] for pppd 2.4
-.\" $Id: pppd.8,v 1.82 2004/11/13 12:04:02 paulus Exp $
+.\" $Id: pppd.8,v 1.83 2004/11/13 12:22:49 paulus Exp $
.\" SH section heading
.\" SS subsection heading
.\" LP paragraph
.\" SH section heading
.\" SS subsection heading
.\" LP paragraph
almost any character can be specified for the \fIescape\fR option,
unlike the \fIasyncmap\fR option which only allows control characters
to be specified. The characters which may not be escaped are those
almost any character can be specified for the \fIescape\fR option,
unlike the \fIasyncmap\fR option which only allows control characters
to be specified. The characters which may not be escaped are those
-with hex values 0x20 \- 0x3f or 0x5e.
+with hex values 0x20 - 0x3f or 0x5e.
.TP
.B file \fIname
Read options from file \fIname\fR (the format is described below).
.TP
.B file \fIname
Read options from file \fIname\fR (the format is described below).
not required. If a local and/or remote IP address is specified with
this option, pppd
will not accept a different value from the peer in the IPCP
not required. If a local and/or remote IP address is specified with
this option, pppd
will not accept a different value from the peer in the IPCP
-negotiation, unless the \fIipcp-accept-local\fR and/or
-\fIipcp-accept-remote\fR options are given, respectively.
+negotiation, unless the \fIipcp\-accept\-local\fR and/or
+\fIipcp\-accept\-remote\fR options are given, respectively.
.TP
.B ipv6 \fI<local_interface_identifier>\fR,\fI<remote_interface_identifier>
Set the local and/or remote 64-bit interface identifier. Either one may be
omitted. The identifier must be specified in standard ascii notation of
IPv6 addresses (e.g. ::dead:beef). If the
.TP
.B ipv6 \fI<local_interface_identifier>\fR,\fI<remote_interface_identifier>
Set the local and/or remote 64-bit interface identifier. Either one may be
omitted. The identifier must be specified in standard ascii notation of
IPv6 addresses (e.g. ::dead:beef). If the
+\fIipv6cp\-use\-ipaddr\fR
option is given, the local identifier is the local IPv4 address (see above).
option is given, the local identifier is the local IPv4 address (see above).
-On systems which supports a unique persistent id, such as EUI-48 derived
-from the Ethernet MAC address, \fIipv6cp-use-persistent\fR option can be
+On systems which supports a unique persistent id, such as EUI\-48 derived
+from the Ethernet MAC address, \fIipv6cp\-use\-persistent\fR option can be
used to replace the \fIipv6 <local>,<remote>\fR option. Otherwise the
identifier is randomized.
.TP
used to replace the \fIipv6 <local>,<remote>\fR option. Otherwise the
identifier is randomized.
.TP
-.B active-filter \fIfilter-expression
+.B active\-filter \fIfilter\-expression
Specifies a packet filter to be applied to data packets to determine
which packets are to be regarded as link activity, and therefore reset
the idle timer, or cause the link to be brought up in demand-dialling
Specifies a packet filter to be applied to data packets to determine
which packets are to be regarded as link activity, and therefore reset
the idle timer, or cause the link to be brought up in demand-dialling
\fBidle\fR option if there are packets being sent or received
regularly over the link (for example, routing information packets)
which would otherwise prevent the link from ever appearing to be idle.
\fBidle\fR option if there are packets being sent or received
regularly over the link (for example, routing information packets)
which would otherwise prevent the link from ever appearing to be idle.
-The \fIfilter-expression\fR syntax is as described for tcpdump(1),
+The \fIfilter\-expression\fR syntax is as described for tcpdump(1),
except that qualifiers which are inappropriate for a PPP link, such as
\fBether\fR and \fBarp\fR, are not permitted. Generally the filter
expression should be enclosed in single-quotes to prevent whitespace
except that qualifiers which are inappropriate for a PPP link, such as
\fBether\fR and \fBarp\fR, are not permitted. Generally the filter
expression should be enclosed in single-quotes to prevent whitespace
is possible to apply different constraints to incoming and outgoing
packets using the \fBinbound\fR and \fBoutbound\fR qualifiers.
.TP
is possible to apply different constraints to incoming and outgoing
packets using the \fBinbound\fR and \fBoutbound\fR qualifiers.
.TP
-.B allow-ip \fIaddress(es)
+.B allow\-ip \fIaddress(es)
Allow peers to use the given IP address or subnet without
authenticating themselves. The parameter is parsed as for each
element of the list of allowed IP addresses in the secrets files (see
the AUTHENTICATION section below).
.TP
Allow peers to use the given IP address or subnet without
authenticating themselves. The parameter is parsed as for each
element of the list of allowed IP addresses in the secrets files (see
the AUTHENTICATION section below).
.TP
-.B allow-number \fInumber
+.B allow\-number \fInumber
Allow peers to connect from the given telephone number. A trailing
`*' character will match all numbers beginning with the leading part.
.TP
Allow peers to connect from the given telephone number. A trailing
`*' character will match all numbers beginning with the leading part.
.TP
bi-directional flow control. The sacrifice is that this flow
control mode does not permit using DTR as a modem control line.
.TP
bi-directional flow control. The sacrifice is that this flow
control mode does not permit using DTR as a modem control line.
.TP
If this option is given, pppd will rechallenge the peer every \fIn\fR
seconds.
.TP
If this option is given, pppd will rechallenge the peer every \fIn\fR
seconds.
.TP
-.B chap-max-challenge \fIn
+.B chap\-max\-challenge \fIn
Set the maximum number of CHAP challenge transmissions to \fIn\fR
(default 10).
.TP
Set the maximum number of CHAP challenge transmissions to \fIn\fR
(default 10).
.TP
Set the CHAP restart interval (retransmission timeout for challenges)
to \fIn\fR seconds (default 3).
.TP
Set the CHAP restart interval (retransmission timeout for challenges)
to \fIn\fR seconds (default 3).
.TP
When exiting, wait for up to \fIn\fR seconds for any child processes
(such as the command specified with the \fBpty\fR command) to exit
before exiting. At the end of the timeout, pppd will send a SIGTERM
When exiting, wait for up to \fIn\fR seconds for any child processes
(such as the command specified with the \fBpty\fR command) to exit
before exiting. At the end of the timeout, pppd will send a SIGTERM
no timeout, that is, pppd will wait until all child processes have
exited.
.TP
no timeout, that is, pppd will wait until all child processes have
exited.
.TP
Wait for up to \fIn\fR milliseconds after the connect script finishes for
a valid PPP packet from the peer. At the end of this time, or when a
valid PPP packet is received from the peer, pppd will commence
Wait for up to \fIn\fR milliseconds after the connect script finishes for
a valid PPP packet from the peer. At the end of this time, or when a
valid PPP packet is received from the peer, pppd will commence
\fIdebug\fR. This information can be directed to a file by setting up
/etc/syslog.conf appropriately (see syslog.conf(5)).
.TP
\fIdebug\fR. This information can be directed to a file by setting up
/etc/syslog.conf appropriately (see syslog.conf(5)).
.TP
Disable asyncmap negotiation, forcing all control characters to be
escaped for both the transmit and the receive direction.
.TP
Disable asyncmap negotiation, forcing all control characters to be
escaped for both the transmit and the receive direction.
.TP
Disable MRU [Maximum Receive Unit] negotiation. With this option,
pppd will use the default MRU value of 1500 bytes for both the
transmit and receive direction.
Disable MRU [Maximum Receive Unit] negotiation. With this option,
pppd will use the default MRU value of 1500 bytes for both the
transmit and receive direction.
network interface. This option is currently only available under
Linux.
.TP
network interface. This option is currently only available under
Linux.
.TP
If this option is given and pppd authenticates the peer with EAP
(i.e., is the server), pppd will restart EAP authentication every
If this option is given and pppd authenticates the peer with EAP
(i.e., is the server), pppd will restart EAP authentication every
-\fIn\fR seconds. For EAP SRP-SHA1, see also the \fBsrp-interval\fR
+\fIn\fR seconds. For EAP SRP\-SHA1, see also the \fBsrp\-interval\fR
option, which enables lightweight rechallenge.
.TP
option, which enables lightweight rechallenge.
.TP
Set the maximum number of EAP Requests to which pppd will respond (as
a client) without hearing EAP Success or Failure. (Default is 20.)
.TP
Set the maximum number of EAP Requests to which pppd will respond (as
a client) without hearing EAP Success or Failure. (Default is 20.)
.TP
Set the maximum number of EAP Requests that pppd will issue (as a
server) while attempting authentication. (Default is 10.)
.TP
Set the maximum number of EAP Requests that pppd will issue (as a
server) while attempting authentication. (Default is 10.)
.TP
Set the retransmit timeout for EAP Requests when acting as a server
(authenticator). (Default is 3 seconds.)
.TP
Set the retransmit timeout for EAP Requests when acting as a server
(authenticator). (Default is 3 seconds.)
.TP
Set the maximum time to wait for the peer to send an EAP Request when
acting as a client (authenticatee). (Default is 20 seconds.)
.TP
Set the maximum time to wait for the peer to send an EAP Request when
acting as a client (authenticatee). (Default is 20 seconds.)
.TP
When logging the contents of PAP packets, this option causes pppd to
exclude the password string from the log. This is the default.
.TP
When logging the contents of PAP packets, this option causes pppd to
exclude the password string from the log. This is the default.
.TP
seconds. The link is idle when no data packets (i.e. IP packets) are
being sent or received. Note: it is not advisable to use this option
with the \fIpersist\fR option without the \fIdemand\fR option.
seconds. The link is idle when no data packets (i.e. IP packets) are
being sent or received. Note: it is not advisable to use this option
with the \fIpersist\fR option without the \fIdemand\fR option.
-If the \fBactive-filter\fR
+If the \fBactive\-filter\fR
option is given, data packets which are rejected by the specified
activity filter also count as the link being idle.
.TP
option is given, data packets which are rejected by the specified
activity filter also count as the link being idle.
.TP
With this option, pppd will accept the peer's idea of our local IP
address, even if the local IP address was specified in an option.
.TP
With this option, pppd will accept the peer's idea of our local IP
address, even if the local IP address was specified in an option.
.TP
With this option, pppd will accept the peer's idea of its (remote) IP
address, even if the remote IP address was specified in an option.
.TP
With this option, pppd will accept the peer's idea of its (remote) IP
address, even if the remote IP address was specified in an option.
.TP
-.B ipcp-max-configure \fIn
+.B ipcp\-max\-configure \fIn
Set the maximum number of IPCP configure-request transmissions to
\fIn\fR (default 10).
.TP
Set the maximum number of IPCP configure-request transmissions to
\fIn\fR (default 10).
.TP
-.B ipcp-max-failure \fIn
+.B ipcp\-max\-failure \fIn
Set the maximum number of IPCP configure-NAKs returned before starting
to send configure-Rejects instead to \fIn\fR (default 10).
.TP
Set the maximum number of IPCP configure-NAKs returned before starting
to send configure-Rejects instead to \fIn\fR (default 10).
.TP
-.B ipcp-max-terminate \fIn
+.B ipcp\-max\-terminate \fIn
Set the maximum number of IPCP terminate-request transmissions to
\fIn\fR (default 3).
.TP
Set the maximum number of IPCP terminate-request transmissions to
\fIn\fR (default 3).
.TP
Set the IPCP restart interval (retransmission timeout) to \fIn\fR
seconds (default 3).
.TP
.B ipparam \fIstring
Set the IPCP restart interval (retransmission timeout) to \fIn\fR
seconds (default 3).
.TP
.B ipparam \fIstring
-Provides an extra parameter to the ip-up and ip-down scripts. If this
+Provides an extra parameter to the ip\-up and ip\-down scripts. If this
option is given, the \fIstring\fR supplied is given as the 6th
parameter to those scripts.
.TP
option is given, the \fIstring\fR supplied is given as the 6th
parameter to those scripts.
.TP
-.B ipv6cp-max-configure \fIn
+.B ipv6cp\-max\-configure \fIn
Set the maximum number of IPv6CP configure-request transmissions to
\fIn\fR (default 10).
.TP
Set the maximum number of IPv6CP configure-request transmissions to
\fIn\fR (default 10).
.TP
-.B ipv6cp-max-failure \fIn
+.B ipv6cp\-max\-failure \fIn
Set the maximum number of IPv6CP configure-NAKs returned before starting
to send configure-Rejects instead to \fIn\fR (default 10).
.TP
Set the maximum number of IPv6CP configure-NAKs returned before starting
to send configure-Rejects instead to \fIn\fR (default 10).
.TP
-.B ipv6cp-max-terminate \fIn
+.B ipv6cp\-max\-terminate \fIn
Set the maximum number of IPv6CP terminate-request transmissions to
\fIn\fR (default 3).
.TP
Set the maximum number of IPv6CP terminate-request transmissions to
\fIn\fR (default 3).
.TP
Set the IPv6CP restart interval (retransmission timeout) to \fIn\fR
seconds (default 3).
.TP
Set the IPv6CP restart interval (retransmission timeout) to \fIn\fR
seconds (default 3).
.TP
supported under Linux, and only if your kernel has been configured to
include IPX support.
.TP
supported under Linux, and only if your kernel has been configured to
include IPX support.
.TP
Set the IPX network number in the IPXCP configure request frame to
\fIn\fR, a hexadecimal number (without a leading 0x). There is no
valid default. If this option is not specified, the network number is
obtained from the peer. If the peer does not have the network number,
the IPX protocol will not be started.
.TP
Set the IPX network number in the IPXCP configure request frame to
\fIn\fR, a hexadecimal number (without a leading 0x). There is no
valid default. If this option is not specified, the network number is
obtained from the peer. If the peer does not have the network number,
the IPX protocol will not be started.
.TP
-.B ipx-node \fIn\fB:\fIm
+.B ipx\-node \fIn\fB:\fIm
Set the IPX node numbers. The two node numbers are separated from each
other with a colon character. The first number \fIn\fR is the local
node number. The second number \fIm\fR is the peer's node number. Each
node number is a hexadecimal number, at most 10 digits long. The node
Set the IPX node numbers. The two node numbers are separated from each
other with a colon character. The first number \fIn\fR is the local
node number. The second number \fIm\fR is the peer's node number. Each
node number is a hexadecimal number, at most 10 digits long. The node
-numbers on the ipx-network must be unique. There is no valid
+numbers on the ipx\-network must be unique. There is no valid
default. If this option is not specified then the node numbers are
obtained from the peer.
.TP
default. If this option is not specified then the node numbers are
obtained from the peer.
.TP
-.B ipx-router-name \fI<string>
+.B ipx\-router\-name \fI<string>
Set the name of the router. This is a string and is sent to the peer
as information data.
.TP
Set the name of the router. This is a string and is sent to the peer
as information data.
.TP
Set the routing protocol to be received by this option. More than one
Set the routing protocol to be received by this option. More than one
-instance of \fIipx-routing\fR may be specified. The '\fInone\fR'
-option (0) may be specified as the only instance of ipx-routing. The
+instance of \fIipx\-routing\fR may be specified. The '\fInone\fR'
+option (0) may be specified as the only instance of ipx\-routing. The
values may be \fI0\fR for \fINONE\fR, \fI2\fR for \fIRIP/SAP\fR, and
\fI4\fR for \fINLSP\fR.
.TP
values may be \fI0\fR for \fINONE\fR, \fI2\fR for \fIRIP/SAP\fR, and
\fI4\fR for \fINLSP\fR.
.TP
-.B ipxcp-accept-local
-Accept the peer's NAK for the node number specified in the ipx-node
+.B ipxcp\-accept\-local
+Accept the peer's NAK for the node number specified in the ipx\-node
option. If a node number was specified, and non-zero, the default is
to insist that the value be used. If you include this option then you
will permit the peer to override the entry of the node number.
.TP
option. If a node number was specified, and non-zero, the default is
to insist that the value be used. If you include this option then you
will permit the peer to override the entry of the node number.
.TP
+.B ipxcp\-accept\-network
Accept the peer's NAK for the network number specified in the
Accept the peer's NAK for the network number specified in the
-ipx-network option. If a network number was specified, and non-zero, the
+ipx\-network option. If a network number was specified, and non-zero, the
default is to insist that the value be used. If you include this
option then you will permit the peer to override the entry of the node
number.
.TP
default is to insist that the value be used. If you include this
option then you will permit the peer to override the entry of the node
number.
.TP
+.B ipxcp\-accept\-remote
Use the peer's network number specified in the configure request
frame. If a node number was specified for the peer and this option was
not specified, the peer will be forced to use the value which you have
specified.
.TP
Use the peer's network number specified in the configure request
frame. If a node number was specified for the peer and this option was
not specified, the peer will be forced to use the value which you have
specified.
.TP
-.B ipxcp-max-configure \fIn
+.B ipxcp\-max\-configure \fIn
Set the maximum number of IPXCP configure request frames which the
system will send to \fIn\fR. The default is 10.
.TP
Set the maximum number of IPXCP configure request frames which the
system will send to \fIn\fR. The default is 10.
.TP
-.B ipxcp-max-failure \fIn
+.B ipxcp\-max\-failure \fIn
Set the maximum number of IPXCP NAK frames which the local system will
send before it rejects the options. The default value is 3.
.TP
Set the maximum number of IPXCP NAK frames which the local system will
send before it rejects the options. The default value is 3.
.TP
-.B ipxcp-max-terminate \fIn
+.B ipxcp\-max\-terminate \fIn
Set the maximum nuber of IPXCP terminate request frames before the
local system considers that the peer is not listening to them. The
default value is 3.
Set the maximum nuber of IPXCP terminate request frames before the
local system considers that the peer is not listening to them. The
default value is 3.
dynamic IP address option (i.e. set /proc/sys/net/ipv4/ip_dynaddr to
1) in demand mode if the local address changes.
.TP
dynamic IP address option (i.e. set /proc/sys/net/ipv4/ip_dynaddr to
1) in demand mode if the local address changes.
.TP
-.B lcp-echo-failure \fIn
+.B lcp\-echo\-failure \fIn
If this option is given, pppd will presume the peer to be dead
If this option is given, pppd will presume the peer to be dead
-if \fIn\fR LCP echo-requests are sent without receiving a valid LCP
-echo-reply. If this happens, pppd will terminate the
+if \fIn\fR LCP echo\-requests are sent without receiving a valid LCP
+echo\-reply. If this happens, pppd will terminate the
connection. Use of this option requires a non-zero value for the
connection. Use of this option requires a non-zero value for the
-\fIlcp-echo-interval\fR parameter. This option can be used to enable
+\fIlcp\-echo\-interval\fR parameter. This option can be used to enable
pppd to terminate after the physical connection has been broken
(e.g., the modem has hung up) in situations where no hardware modem
control lines are available.
.TP
pppd to terminate after the physical connection has been broken
(e.g., the modem has hung up) in situations where no hardware modem
control lines are available.
.TP
-.B lcp-echo-interval \fIn
-If this option is given, pppd will send an LCP echo-request frame to
+.B lcp\-echo\-interval \fIn
+If this option is given, pppd will send an LCP echo\-request frame to
the peer every \fIn\fR seconds. Normally the peer should respond to
the peer every \fIn\fR seconds. Normally the peer should respond to
-the echo-request by sending an echo-reply. This option can be used
-with the \fIlcp-echo-failure\fR option to detect that the peer is no
+the echo\-request by sending an echo\-reply. This option can be used
+with the \fIlcp\-echo\-failure\fR option to detect that the peer is no
-.B lcp-max-configure \fIn
+.B lcp\-max\-configure \fIn
Set the maximum number of LCP configure-request transmissions to
\fIn\fR (default 10).
.TP
Set the maximum number of LCP configure-request transmissions to
\fIn\fR (default 10).
.TP
+.B lcp\-max\-failure \fIn
Set the maximum number of LCP configure-NAKs returned before starting
to send configure-Rejects instead to \fIn\fR (default 10).
.TP
Set the maximum number of LCP configure-NAKs returned before starting
to send configure-Rejects instead to \fIn\fR (default 10).
.TP
-.B lcp-max-terminate \fIn
+.B lcp\-max\-terminate \fIn
Set the maximum number of LCP terminate-request transmissions to
\fIn\fR (default 3).
.TP
Set the maximum number of LCP terminate-request transmissions to
\fIn\fR (default 3).
.TP
Set the LCP restart interval (retransmission timeout) to \fIn\fR
seconds (default 3).
.TP
.B linkname \fIname\fR
Sets the logical name of the link to \fIname\fR. Pppd will create a
Set the LCP restart interval (retransmission timeout) to \fIn\fR
seconds (default 3).
.TP
.B linkname \fIname\fR
Sets the logical name of the link to \fIname\fR. Pppd will create a
-file named \fBppp-\fIname\fB.pid\fR in /var/run (or /etc/ppp on some
+file named \fBppp\-\fIname\fB.pid\fR in /var/run (or /etc/ppp on some
systems) containing its process ID. This can be useful in determining
which instance of pppd is responsible for the link to a given peer
system. This is a privileged option.
systems) containing its process ID. This can be useful in determining
which instance of pppd is responsible for the link to a given peer
system. This is a privileged option.
.B login
Use the system password database for authenticating the peer using
PAP, and record the user in the system wtmp file. Note that the peer
.B login
Use the system password database for authenticating the peer using
PAP, and record the user in the system wtmp file. Note that the peer
-must have an entry in the /etc/ppp/pap-secrets file as well as the
+must have an entry in the /etc/ppp/pap\-secrets file as well as the
system password database to be allowed access.
.TP
.B maxconnect \fIn
system password database to be allowed access.
.TP
.B maxconnect \fIn
Enables the use of PPP multilink; this is an alias for the `multilink'
option. This option is currently only available under Linux.
.TP
Enables the use of PPP multilink; this is an alias for the `multilink'
option. This option is currently only available under Linux.
.TP
Allow MPPE to use stateful mode. Stateless mode is still attempted first.
The default is to disallow stateful mode.
.TP
Allow MPPE to use stateful mode. Stateless mode is still attempted first.
The default is to disallow stateful mode.
.TP
currently only available under Linux, and only has any effect if
multilink is enabled (see the multilink option).
.TP
currently only available under Linux, and only has any effect if
multilink is enabled (see the multilink option).
.TP
If pppd is acting as a server for Microsoft Windows clients, this
option allows pppd to supply one or two DNS (Domain Name Server)
addresses to the clients. The first instance of this option specifies
the primary DNS address; the second instance (if given) specifies the
secondary DNS address. (This option was present in some older
If pppd is acting as a server for Microsoft Windows clients, this
option allows pppd to supply one or two DNS (Domain Name Server)
addresses to the clients. The first instance of this option specifies
the primary DNS address; the second instance (if given) specifies the
secondary DNS address. (This option was present in some older
-versions of pppd under the name \fBdns-addr\fR.)
+versions of pppd under the name \fBdns\-addr\fR.)
If pppd is acting as a server for Microsoft Windows or "Samba"
clients, this option allows pppd to supply one or two WINS (Windows
Internet Name Services) server addresses to the clients. The first
If pppd is acting as a server for Microsoft Windows or "Samba"
clients, this option allows pppd to supply one or two WINS (Windows
Internet Name Services) server addresses to the clients. The first
.B nomppe
Disables MPPE (Microsoft Point to Point Encryption). This is the default.
.TP
.B nomppe
Disables MPPE (Microsoft Point to Point Encryption). This is the default.
.TP
-.B nomppe-40
-Disable 40\-bit encryption with MPPE.
+.B nomppe\-40
+Disable 40-bit encryption with MPPE.
-.B nomppe-128
-Disable 128\-bit encryption with MPPE.
+.B nomppe\-128
+Disable 128-bit encryption with MPPE.
Disable MPPE stateful mode. This is the default.
.TP
.B nompshortseq
Disable MPPE stateful mode. This is the default.
.TP
.B nompshortseq
specified.
.TP
.B nopredictor1
specified.
.TP
.B nopredictor1
-Do not accept or agree to Predictor-1 compression.
+Do not accept or agree to Predictor\-1 compression.
.TP
.B noproxyarp
Disable the \fIproxyarp\fR option. The system administrator who
.TP
.B noproxyarp
Disable the \fIproxyarp\fR option. The system administrator who
ask the peer to do so.
.TP
.B papcrypt
ask the peer to do so.
.TP
.B papcrypt
-Indicates that all secrets in the /etc/ppp/pap-secrets file which are
+Indicates that all secrets in the /etc/ppp/pap\-secrets file which are
used for checking the identity of the peer are encrypted, and thus
pppd should not accept a password which, before encryption, is
used for checking the identity of the peer are encrypted, and thus
pppd should not accept a password which, before encryption, is
-identical to the secret from the /etc/ppp/pap-secrets file.
+identical to the secret from the /etc/ppp/pap\-secrets file.
+.B pap\-max\-authreq \fIn
Set the maximum number of PAP authenticate-request transmissions to
\fIn\fR (default 10).
.TP
Set the maximum number of PAP authenticate-request transmissions to
\fIn\fR (default 10).
.TP
Set the PAP restart interval (retransmission timeout) to \fIn\fR
seconds (default 3).
.TP
Set the PAP restart interval (retransmission timeout) to \fIn\fR
seconds (default 3).
.TP
Set the maximum time that pppd will wait for the peer to authenticate
itself with PAP to \fIn\fR seconds (0 means no limit).
.TP
Set the maximum time that pppd will wait for the peer to authenticate
itself with PAP to \fIn\fR seconds (0 means no limit).
.TP
-.B pass-filter \fIfilter-expression
+.B pass\-filter \fIfilter\-expression
Specifies a packet filter to applied to data packets being sent or
received to determine which packets should be allowed to pass.
Packets which are rejected by the filter are silently discarded. This
option can be used to prevent specific network daemons (such as
routed) using up link bandwidth, or to provide a very basic firewall
capability.
Specifies a packet filter to applied to data packets being sent or
received to determine which packets should be allowed to pass.
Packets which are rejected by the filter are silently discarded. This
option can be used to prevent specific network daemons (such as
routed) using up link bandwidth, or to provide a very basic firewall
capability.
-The \fIfilter-expression\fR syntax is as described for tcpdump(1),
+The \fIfilter\-expression\fR syntax is as described for tcpdump(1),
except that qualifiers which are inappropriate for a PPP link, such as
\fBether\fR and \fBarp\fR, are not permitted. Generally the filter
expression should be enclosed in single-quotes to prevent whitespace
except that qualifiers which are inappropriate for a PPP link, such as
\fBether\fR and \fBarp\fR, are not permitted. Generally the filter
expression should be enclosed in single-quotes to prevent whitespace
option is currently only available under Linux, and requires that the
kernel was configured to include PPP filtering support (CONFIG_PPP_FILTER).
.TP
option is currently only available under Linux, and requires that the
kernel was configured to include PPP filtering support (CONFIG_PPP_FILTER).
.TP
-.B password \fIpassword-string
+.B password \fIpassword\-string
Specifies the password to use for authenticating to the peer. Use
of this option is discouraged, as the password is likely to be visible
to other users on the system (for example, by using ps(1)).
Specifies the password to use for authenticating to the peer. Use
of this option is discouraged, as the password is likely to be visible
to other users on the system (for example, by using ps(1)).
if requested. This option has no effect unless the kernel driver
supports Predictor-1 compression.
.TP
if requested. This option has no effect unless the kernel driver
supports Predictor-1 compression.
.TP
-.B privgroup \fIgroup-name
-Allows members of group \fIgroup-name\fR to use privileged options.
+.B privgroup \fIgroup\-name
+Allows members of group \fIgroup\-name\fR to use privileged options.
This is a privileged option. Use of this option requires care as
This is a privileged option. Use of this option requires care as
-there is no guarantee that members of \fIgroup-name\fR cannot use pppd
+there is no guarantee that members of \fIgroup\-name\fR cannot use pppd
to become root themselves. Consider it equivalent to putting the
to become root themselves. Consider it equivalent to putting the
-members of \fIgroup-name\fR in the kmem or disk group.
+members of \fIgroup\-name\fR in the kmem or disk group.
.TP
.B proxyarp
Add an entry to this system's ARP [Address Resolution Protocol] table
.TP
.B proxyarp
Add an entry to this system's ARP [Address Resolution Protocol] table
\fIrecord\fR option is used in conjuction with the \fIpty\fR option,
the child process will have pipes on its standard input and output.)
.TP
\fIrecord\fR option is used in conjuction with the \fIpty\fR option,
the child process will have pipes on its standard input and output.)
.TP
With this option, pppd will accept all control characters from the
peer, including those marked in the receive asyncmap. Without this
option, pppd will discard those characters as specified in RFC1662.
With this option, pppd will accept all control characters from the
peer, including those marked in the receive asyncmap. Without this
option, pppd will discard those characters as specified in RFC1662.
Set the assumed telephone number of the remote system for authentication
purposes to \fInumber\fR.
.TP
Set the assumed telephone number of the remote system for authentication
purposes to \fInumber\fR.
.TP
With this option, pppd will not agree to authenticate itself to the
peer using CHAP.
.TP
With this option, pppd will not agree to authenticate itself to the
peer using CHAP.
.TP
With this option, pppd will not agree to authenticate itself to the
With this option, pppd will not agree to authenticate itself to the
With this option, pppd will not agree to authenticate itself to the
With this option, pppd will not agree to authenticate itself to the
With this option, pppd will not agree to authenticate itself to the
peer using EAP.
.TP
With this option, pppd will not agree to authenticate itself to the
peer using EAP.
.TP
With this option, pppd will not agree to authenticate itself to the
peer using PAP.
.TP
With this option, pppd will not agree to authenticate itself to the
peer using PAP.
.TP
Require the peer to authenticate itself using CHAP [Challenge
Handshake Authentication Protocol] authentication.
.TP
Require the peer to authenticate itself using CHAP [Challenge
Handshake Authentication Protocol] authentication.
.TP
Require the use of MPPE (Microsoft Point to Point Encryption). This
option disables all other compression types. This option enables
Require the use of MPPE (Microsoft Point to Point Encryption). This
option disables all other compression types. This option enables
-both 40\-bit and 128\-bit encryption. In order for MPPE to successfully
-come up, you must have authenticated with either MS-CHAP or MS-CHAPv2.
+both 40-bit and 128-bit encryption. In order for MPPE to successfully
+come up, you must have authenticated with either MS\-CHAP or MS\-CHAPv2.
This option is presently only supported under Linux, and only if your
kernel has been configured to include MPPE support.
.TP
This option is presently only supported under Linux, and only if your
kernel has been configured to include MPPE support.
.TP
-.B require-mppe-40
-Require the use of MPPE, with 40\-bit encryption.
+.B require\-mppe\-40
+Require the use of MPPE, with 40-bit encryption.
-.B require-mppe-128
-Require the use of MPPE, with 128\-bit encryption.
+.B require\-mppe\-128
+Require the use of MPPE, with 128-bit encryption.
-.B require-mschap
-Require the peer to authenticate itself using MS-CHAP [Microsoft Challenge
+.B require\-mschap
+Require the peer to authenticate itself using MS\-CHAP [Microsoft Challenge
Handshake Authentication Protocol] authentication.
.TP
Handshake Authentication Protocol] authentication.
.TP
-.B require-mschap-v2
-Require the peer to authenticate itself using MS-CHAPv2 [Microsoft Challenge
+.B require\-mschap\-v2
+Require the peer to authenticate itself using MS\-CHAPv2 [Microsoft Challenge
Handshake Authentication Protocol, Version 2] authentication.
.TP
Handshake Authentication Protocol, Version 2] authentication.
.TP
Require the peer to authenticate itself using EAP [Extensible
Authentication Protocol] authentication.
.TP
Require the peer to authenticate itself using EAP [Extensible
Authentication Protocol] authentication.
.TP
Require the peer to authenticate itself using PAP [Password
Authentication Protocol] authentication.
.TP
Require the peer to authenticate itself using PAP [Password
Authentication Protocol] authentication.
.TP
When logging the contents of PAP packets, this option causes pppd to
show the password string in the log message.
.TP
When logging the contents of PAP packets, this option causes pppd to
show the password string in the log message.
.TP
connection until a valid LCP packet is received from the peer (as for
the `passive' option with ancient versions of pppd).
.TP
connection until a valid LCP packet is received from the peer (as for
the `passive' option with ancient versions of pppd).
.TP
-.B srp-interval \fIn
-If this parameter is given and pppd uses EAP SRP-SHA1 to authenticate
+.B srp\-interval \fIn
+If this parameter is given and pppd uses EAP SRP\-SHA1 to authenticate
the peer (i.e., is the server), then pppd will use the optional
lightweight SRP rechallenge mechanism at intervals of \fIn\fR
the peer (i.e., is the server), then pppd will use the optional
lightweight SRP rechallenge mechanism at intervals of \fIn\fR
-seconds. This option is faster than \fBeap-interval\fR
-reauthentication because it uses a hash-based mechanism and does not
+seconds. This option is faster than \fBeap\-interval\fR
+reauthentication because it uses a hash\-based mechanism and does not
derive a new session key.
.TP
derive a new session key.
.TP
-.B srp-pn-secret \fIstring
+.B srp\-pn\-secret \fIstring
Set the long-term pseudonym-generating secret for the server. This
value is optional and if set, needs to be known at the server
(authenticator) side only, and should be different for each server (or
Set the long-term pseudonym-generating secret for the server. This
value is optional and if set, needs to be known at the server
(authenticator) side only, and should be different for each server (or
generate a key to encrypt and decrypt the client's identity contained
in the pseudonym.
.TP
generate a key to encrypt and decrypt the client's identity contained
in the pseudonym.
.TP
-.B srp-use-pseudonym
-When operating as an EAP SRP-SHA1 client, attempt to use the pseudonym
+.B srp\-use\-pseudonym
+When operating as an EAP SRP\-SHA1 client, attempt to use the pseudonym
stored in ~/.ppp_psuedonym first as the identity, and save in this
file any pseudonym offered by the peer during authentication.
.TP
stored in ~/.ppp_psuedonym first as the identity, and save in this
file any pseudonym offered by the peer during authentication.
.TP
.TP
.B usepeerdns
Ask the peer for up to 2 DNS server addresses. The addresses supplied
.TP
.B usepeerdns
Ask the peer for up to 2 DNS server addresses. The addresses supplied
-by the peer (if any) are passed to the /etc/ppp/ip-up script in the
+by the peer (if any) are passed to the /etc/ppp/ip\-up script in the
environment variables DNS1 and DNS2, and the environment variable
USEPEERDNS will be set to 1. In addition, pppd will create an
/etc/ppp/resolv.conf file containing one or two nameserver lines with
environment variables DNS1 and DNS2, and the environment variable
USEPEERDNS will be set to 1. In addition, pppd will create an
/etc/ppp/resolv.conf file containing one or two nameserver lines with
Sets the name used for authenticating the local system to the peer to
\fIname\fR.
.TP
Sets the name used for authenticating the local system to the peer to
\fIname\fR.
.TP
Sets the number of connection slots to be used by the Van Jacobson
TCP/IP header compression and decompression code to \fIn\fR, which
must be between 2 and 16 (inclusive).
Sets the number of connection slots to be used by the Van Jacobson
TCP/IP header compression and decompression code to \fIn\fR, which
must be between 2 and 16 (inclusive).
with a response which includes its name plus a hash value derived from
the shared secret and the challenge, in order to prove that it knows
the secret. EAP supports CHAP-style authentication, and also includes
with a response which includes its name plus a hash value derived from
the shared secret and the challenge, in order to prove that it knows
the secret. EAP supports CHAP-style authentication, and also includes
-the SRP-SHA1 mechanism, which is resistant to dictionary-based attacks
+the SRP\-SHA1 mechanism, which is resistant to dictionary-based attacks
and does not require a cleartext password on the server side.
.LP
The PPP protocol, being symmetrical, allows both peers to require the
and does not require a cleartext password on the server side.
.LP
The PPP protocol, being symmetrical, allows both peers to require the
if it has no secrets which could be used to do so.
.LP
Pppd stores secrets for use in authentication in secrets
if it has no secrets which could be used to do so.
.LP
Pppd stores secrets for use in authentication in secrets
-files (/etc/ppp/pap-secrets for PAP, /etc/ppp/chap-secrets for CHAP,
-MS-CHAP, MS-CHAPv2, and EAP MD5-Challenge, and /etc/ppp/srp-secrets
-for EAP SRP-SHA1).
+files (/etc/ppp/pap\-secrets for PAP, /etc/ppp/chap\-secrets for CHAP,
+MS\-CHAP, MS\-CHAPv2, and EAP MD5-Challenge, and /etc/ppp/srp\-secrets
+for EAP SRP\-SHA1).
All secrets files have the same format. The secrets files can
contain secrets for pppd to use in authenticating itself to other
systems, as well as secrets for pppd to use when authenticating other
systems to itself.
.LP
Each line in a secrets file contains one secret. A given secret is
All secrets files have the same format. The secrets files can
contain secrets for pppd to use in authenticating itself to other
systems, as well as secrets for pppd to use when authenticating other
systems to itself.
.LP
Each line in a secrets file contains one secret. A given secret is
-specific to a particular combination of client and server \- it can
+specific to a particular combination of client and server - it can
only be used by that client to authenticate itself to that server.
Thus each line in a secrets file has at least 3 fields: the name of
the client, the name of the server, and the secret. These fields may
only be used by that client to authenticate itself to that server.
Thus each line in a secrets file has at least 3 fields: the name of
the client, the name of the server, and the secret. These fields may
.LP
Any following words on the same line are taken to be a list of
acceptable IP addresses for that client. If there are only 3 words on
.LP
Any following words on the same line are taken to be a list of
acceptable IP addresses for that client. If there are only 3 words on
-the line, or if the first word is "-", then all IP addresses are
+the line, or if the first word is "\-", then all IP addresses are
disallowed. To allow any address, use "*". A word starting with "!"
indicates that the specified address is \fInot\fR acceptable. An
address may be followed by "/" and a number \fIn\fR, to indicate a
disallowed. To allow any address, use "*". A word starting with "!"
indicates that the specified address is \fInot\fR acceptable. An
address may be followed by "/" and a number \fIn\fR, to indicate a
name of the local system defaults to the hostname, with the domain
name appended if the \fIdomain\fR option is used. This default can be
overridden with the \fIname\fR option, except when the
name of the local system defaults to the hostname, with the domain
name appended if the \fIdomain\fR option is used. This default can be
overridden with the \fIname\fR option, except when the
-\fIusehostname\fR option is used. (For EAP SRP-SHA1, see the
-srp-entry(8) utility for generating proper validator entries to be
+\fIusehostname\fR option is used. (For EAP SRP\-SHA1, see the
+srp\-entry(8) utility for generating proper validator entries to be
used in the "secret" field.)
.LP
When pppd is choosing a secret to use in authenticating itself to the
used in the "secret" field.)
.LP
When pppd is choosing a secret to use in authenticating itself to the
.LP
Furthermore, if the \fIlogin\fR option was specified, the username and
password are also checked against the system password database. Thus,
.LP
Furthermore, if the \fIlogin\fR option was specified, the username and
password are also checked against the system password database. Thus,
-the system administrator can set up the pap-secrets file to allow PPP
+the system administrator can set up the pap\-secrets file to allow PPP
access only to certain users, and to restrict the set of IP addresses
that each user can use. Typically, when using the \fIlogin\fR option,
access only to certain users, and to restrict the set of IP addresses
that each user can use. Typically, when using the \fIlogin\fR option,
-the secret in /etc/ppp/pap-secrets would be "", which will match any
+the secret in /etc/ppp/pap\-secrets would be "", which will match any
password supplied by the peer. This avoids the need to have the same
secret in two places.
.LP
password supplied by the peer. This avoids the need to have the same
secret in two places.
.LP
authentication. If the peer refuses to authenticate itself when
requested, pppd takes that as equivalent to authenticating with PAP
using the empty string for the username and password. Thus, by adding
authentication. If the peer refuses to authenticate itself when
requested, pppd takes that as equivalent to authenticating with PAP
using the empty string for the username and password. Thus, by adding
-a line to the pap-secrets file which specifies the empty string for
+a line to the pap\-secrets file which specifies the empty string for
the client and password, it is possible to allow restricted access to
hosts which refuse to authenticate themselves.
.SH ROUTING
the client and password, it is possible to allow restricted access to
hosts which refuse to authenticate themselves.
.SH ROUTING
modification to routing tables and/or ARP (Address Resolution
Protocol) tables. In most cases the \fIdefaultroute\fR and/or
\fIproxyarp\fR options are sufficient for this, but in some cases
modification to routing tables and/or ARP (Address Resolution
Protocol) tables. In most cases the \fIdefaultroute\fR and/or
\fIproxyarp\fR options are sufficient for this, but in some cases
-further intervention is required. The /etc/ppp/ip-up script can be
+further intervention is required. The /etc/ppp/ip\-up script can be
used for this.
.LP
Sometimes it is desirable to add a default route through the remote
used for this.
.LP
Sometimes it is desirable to add a default route through the remote
endpoint discriminator is a block of data which is hopefully unique
for each peer. Several types of data can be used, including
locally-assigned strings of bytes, IP addresses, MAC addresses,
endpoint discriminator is a block of data which is hopefully unique
for each peer. Several types of data can be used, including
locally-assigned strings of bytes, IP addresses, MAC addresses,
-randomly strings of bytes, or E-164 phone numbers. The endpoint
+randomly strings of bytes, or E\-164 phone numbers. The endpoint
discriminator sent to the peer by pppd can be set using the endpoint
option.
.LP
discriminator sent to the peer by pppd can be set using the endpoint
option.
.LP
.IP
ttyS0 19200 crtscts
.br
.IP
ttyS0 19200 crtscts
.br
-connect '/usr/sbin/chat -v -f /etc/ppp/chat-isp'
+connect '/usr/sbin/chat \-v \-f /etc/ppp/chat\-isp'
.br
noauth
.LP
In this example, we are using chat to dial the ISP's modem and go
.br
noauth
.LP
In this example, we are using chat to dial the ISP's modem and go
-through any logon sequence required. The /etc/ppp/chat-isp file
+through any logon sequence required. The /etc/ppp/chat\-isp file
contains the script used by chat; it could for example contain
something like this:
.IP
contains the script used by chat; it could for example contain
something like this:
.IP
.br
"ispts" "\\q^Uppp"
.br
.br
"ispts" "\\q^Uppp"
.br
.LP
See the chat(8) man page for details of chat scripts.
.LP
.LP
See the chat(8) man page for details of chat scripts.
.LP
.LP
To allow a user to use the PPP facilities, you need to allocate an IP
address for that user's machine and create an entry in
.LP
To allow a user to use the PPP facilities, you need to allocate an IP
address for that user's machine and create an entry in
-/etc/ppp/pap-secrets, /etc/ppp/chap-secrets, or /etc/ppp/srp-secrets
+/etc/ppp/pap\-secrets, /etc/ppp/chap\-secrets, or /etc/ppp/srp\-secrets
(depending on which authentication method the PPP implementation on
the user's machine supports), so that the user's machine can
authenticate itself. For example, if Joe has a machine called
"joespc" that is to be allowed to dial in to the machine called
"server" and use the IP address joespc.my.net, you would add an entry
(depending on which authentication method the PPP implementation on
the user's machine supports), so that the user's machine can
authenticate itself. For example, if Joe has a machine called
"joespc" that is to be allowed to dial in to the machine called
"server" and use the IP address joespc.my.net, you would add an entry
-like this to /etc/ppp/pap-secrets or /etc/ppp/chap-secrets:
+like this to /etc/ppp/pap\-secrets or /etc/ppp/chap\-secrets:
.IP
joespc server "joe's secret" joespc.my.net
.LP
.IP
joespc server "joe's secret" joespc.my.net
.LP
-(See srp-entry(8) for a means to generate the server's entry when
-SRP-SHA1 is in use.)
+(See srp\-entry(8) for a means to generate the server's entry when
+SRP\-SHA1 is in use.)
Alternatively, you can create a username called (for example) "ppp",
whose login shell is pppd and whose home directory is /etc/ppp.
Options to be used when pppd is run this way can be put in
Alternatively, you can create a username called (for example) "ppp",
whose login shell is pppd and whose home directory is /etc/ppp.
Options to be used when pppd is run this way can be put in
Pppd invokes the following scripts, if they exist. It is not an error
if they don't exist.
.TP
Pppd invokes the following scripts, if they exist. It is not an error
if they don't exist.
.TP
A program or script which is executed after the remote system
successfully authenticates itself. It is executed with the parameters
.IP
A program or script which is executed after the remote system
successfully authenticates itself. It is executed with the parameters
.IP
-\fIinterface-name peer-name user-name tty-device speed\fR
+\fIinterface\-name peer\-name user\-name tty\-device speed\fR
.IP
Note that this script is not executed if the peer doesn't authenticate
itself, for example when the \fInoauth\fR option is used.
.TP
.IP
Note that this script is not executed if the peer doesn't authenticate
itself, for example when the \fInoauth\fR option is used.
.TP
A program or script which is executed when the link goes down, if
A program or script which is executed when the link goes down, if
-/etc/ppp/auth-up was previously executed. It is executed in the same
-manner with the same parameters as /etc/ppp/auth-up.
+/etc/ppp/auth\-up was previously executed. It is executed in the same
+manner with the same parameters as /etc/ppp/auth\-up.
A program or script which is executed when the link is available for
sending and receiving IP packets (that is, IPCP has come up). It is
executed with the parameters
.IP
A program or script which is executed when the link is available for
sending and receiving IP packets (that is, IPCP has come up). It is
executed with the parameters
.IP
-\fIinterface-name tty-device speed local-IP-address
-remote-IP-address ipparam\fR
+\fIinterface\-name tty\-device speed local\-IP\-address
+remote\-IP\-address ipparam\fR
A program or script which is executed when the link is no longer
available for sending and receiving IP packets. This script can be
A program or script which is executed when the link is no longer
available for sending and receiving IP packets. This script can be
-used for undoing the effects of the /etc/ppp/ip-up script. It is
-invoked in the same manner and with the same parameters as the ip-up
+used for undoing the effects of the /etc/ppp/ip\-up script. It is
+invoked in the same manner and with the same parameters as the ip\-up
-.B /etc/ppp/ipv6-up
-Like /etc/ppp/ip-up, except that it is executed when the link is available
+.B /etc/ppp/ipv6\-up
+Like /etc/ppp/ip\-up, except that it is executed when the link is available
for sending and receiving IPv6 packets. It is executed with the parameters
.IP
for sending and receiving IPv6 packets. It is executed with the parameters
.IP
-\fIinterface-name tty-device speed local-link-local-address
-remote-link-local-address ipparam\fR
+\fIinterface\-name tty\-device speed local\-link\-local\-address
+remote\-link\-local\-address ipparam\fR
-.B /etc/ppp/ipv6-down
-Similar to /etc/ppp/ip-down, but it is executed when IPv6 packets can no
+.B /etc/ppp/ipv6\-down
+Similar to /etc/ppp/ip\-down, but it is executed when IPv6 packets can no
longer be transmitted on the link. It is executed with the same parameters
longer be transmitted on the link. It is executed with the same parameters
A program or script which is executed when the link is available for
sending and receiving IPX packets (that is, IPXCP has come up). It is
executed with the parameters
.IP
A program or script which is executed when the link is available for
sending and receiving IPX packets (that is, IPXCP has come up). It is
executed with the parameters
.IP
-\fIinterface-name tty-device speed network-number local-IPX-node-address
-remote-IPX-node-address local-IPX-routing-protocol remote-IPX-routing-protocol
-local-IPX-router-name remote-IPX-router-name ipparam pppd-pid\fR
+\fIinterface\-name tty\-device speed network\-number local\-IPX\-node\-address
+remote\-IPX\-node\-address local\-IPX\-routing\-protocol remote\-IPX\-routing\-protocol
+local\-IPX\-router\-name remote\-IPX\-router\-name ipparam pppd\-pid\fR
-The local-IPX-routing-protocol and remote-IPX-routing-protocol field
+The local\-IPX\-routing\-protocol and remote\-IPX\-routing\-protocol field
may be one of the following:
.IP
NONE to indicate that there is no routing protocol
may be one of the following:
.IP
NONE to indicate that there is no routing protocol
.br
RIP NLSP to indicate that both RIP/SAP and NLSP should be used
.TP
.br
RIP NLSP to indicate that both RIP/SAP and NLSP should be used
.TP
A program or script which is executed when the link is no longer
available for sending and receiving IPX packets. This script can be
A program or script which is executed when the link is no longer
available for sending and receiving IPX packets. This script can be
-used for undoing the effects of the /etc/ppp/ipx-up script. It is
-invoked in the same manner and with the same parameters as the ipx-up
+used for undoing the effects of the /etc/ppp/ipx\-up script. It is
+invoked in the same manner and with the same parameters as the ipx\-up
script.
.SH FILES
.TP
.B /var/run/ppp\fIn\fB.pid \fR(BSD or Linux), \fB/etc/ppp/ppp\fIn\fB.pid \fR(others)
Process-ID for pppd process on ppp interface unit \fIn\fR.
.TP
script.
.SH FILES
.TP
.B /var/run/ppp\fIn\fB.pid \fR(BSD or Linux), \fB/etc/ppp/ppp\fIn\fB.pid \fR(others)
Process-ID for pppd process on ppp interface unit \fIn\fR.
.TP
-.B /var/run/ppp-\fIname\fB.pid \fR(BSD or Linux),
-\fB/etc/ppp/ppp-\fIname\fB.pid \fR(others)
+.B /var/run/ppp\-\fIname\fB.pid \fR(BSD or Linux),
+\fB/etc/ppp/ppp\-\fIname\fB.pid \fR(others)
Process-ID for pppd process for logical link \fIname\fR (see the
\fIlinkname\fR option).
.TP
Process-ID for pppd process for logical link \fIname\fR (see the
\fIlinkname\fR option).
.TP
be examined by external programs to obtain information about running
pppd instances, the interfaces and devices they are using, IP address
assignments, etc.
be examined by external programs to obtain information about running
pppd instances, the interfaces and devices they are using, IP address
assignments, etc.
+.B /etc/ppp/pap\-secrets
Usernames, passwords and IP addresses for PAP authentication. This
file should be owned by root and not readable or writable by any other
user. Pppd will log a warning if this is not the case.
.TP
Usernames, passwords and IP addresses for PAP authentication. This
file should be owned by root and not readable or writable by any other
user. Pppd will log a warning if this is not the case.
.TP
-.B /etc/ppp/chap-secrets
-Names, secrets and IP addresses for CHAP/MS-CHAP/MS-CHAPv2 authentication.
-As for /etc/ppp/pap-secrets, this file should be owned by root and not
+.B /etc/ppp/chap\-secrets
+Names, secrets and IP addresses for CHAP/MS\-CHAP/MS\-CHAPv2 authentication.
+As for /etc/ppp/pap\-secrets, this file should be owned by root and not
readable or writable by any other user. Pppd will log a warning if
this is not the case.
.TP
readable or writable by any other user. Pppd will log a warning if
this is not the case.
.TP
+.B /etc/ppp/srp\-secrets
Names, secrets, and IP addresses for EAP authentication. As for
Names, secrets, and IP addresses for EAP authentication. As for
-/etc/ppp/pap-secrets, this file should be owned by root and not
+/etc/ppp/pap\-secrets, this file should be owned by root and not
readable or writable by any other user. Pppd will log a warning if
this is not the case.
.TP
.B ~/.ppp_pseudonym
readable or writable by any other user. Pppd will log a warning if
this is not the case.
.TP
.B ~/.ppp_pseudonym
-Saved client-side SRP-SHA1 pseudonym. See the \fIsrp-use-pseudonym\fR
+Saved client-side SRP\-SHA1 pseudonym. See the \fIsrp\-use\-pseudonym\fR
option for details.
.TP
.B /etc/ppp/options
option for details.
.TP
.B /etc/ppp/options
.TP
.B RFC1661
Simpson, W.A.
.TP
.B RFC1661
Simpson, W.A.
-.I The Point\-to\-Point Protocol (PPP).
+.I The Point-to-Point Protocol (PPP).
July 1994.
.TP
.B RFC1662
July 1994.
.TP
.B RFC1662
.I The SRP Authentication and Key Exchange System
September 2000.
.TP
.I The SRP Authentication and Key Exchange System
September 2000.
.TP
-.B draft-ietf-pppext-eap-srp-03.txt
+.B draft\-ietf\-pppext\-eap\-srp\-03.txt
-.I EAP SRP-SHA1 Authentication Protocol.
+.I EAP SRP\-SHA1 Authentication Protocol.
July 2001.
.SH NOTES
Some limited degree of control can be exercised over a running pppd
July 2001.
.SH NOTES
Some limited degree of control can be exercised over a running pppd
.\" manual page [] for srp-entry
.\" manual page [] for srp-entry
-.\" $Id: srp-entry.8,v 1.1 2002/11/02 19:48:13 carlsonj Exp $
+.\" $Id: srp-entry.8,v 1.2 2004/11/13 12:22:49 paulus Exp $
.\" SH section heading
.\" SS subsection heading
.\" LP paragraph
.\" SH section heading
.\" SS subsection heading
.\" LP paragraph
.\" TP hanging label
.TH SRP-ENTRY 8
.SH NAME
.\" TP hanging label
.TH SRP-ENTRY 8
.SH NAME
-srp-entry \- Generate a SRP-SHA1 Server Entry
+srp\-entry \- Generate a SRP\-SHA1 Server Entry
] [
.I clientname
]
.SH DESCRIPTION
.LP
This utility generates an entry suitable for use in the
] [
.I clientname
]
.SH DESCRIPTION
.LP
This utility generates an entry suitable for use in the
-/etc/ppp/srp-secrets file on a PPP EAP SRP-SHA1 authenticator
+/etc/ppp/srp\-secrets file on a PPP EAP SRP\-SHA1 authenticator
("server"). This file has the same basic layout as the other pppd(8)
("server"). This file has the same basic layout as the other pppd(8)
-authentication files, /etc/ppp/pap-secrets and /etc/ppp/chap-secrets.
+authentication files, /etc/ppp/pap\-secrets and /etc/ppp/chap\-secrets.
Thus, the entry generated has at least four main fields separated by
spaces. The first field is the authenticatee ("client") name. The
second is the server name. The third is the secret. The fourth is
Thus, the entry generated has at least four main fields separated by
spaces. The first field is the authenticatee ("client") name. The
second is the server name. The third is the secret. The fourth is
The third field has three subfields, separated by colons. The first
subfield is the index of the modulus and generator from SRP's
/etc/tpasswd.conf. The special value 0 is used to represent the
The third field has three subfields, separated by colons. The first
subfield is the index of the modulus and generator from SRP's
/etc/tpasswd.conf. The special value 0 is used to represent the
-well-known modulus and generator specified in the EAP SRP-SHA1 draft.
+well-known modulus and generator specified in the EAP SRP\-SHA1 draft.
The second subfield is the password validator. The third is the
password salt. These latter two values are encoded in base64 notation.
.SH OPTIONS
.TP
The second subfield is the password validator. The third is the
password salt. These latter two values are encoded in base64 notation.
.SH OPTIONS
.TP
Specifies the modulus/generator index in /etc/tpasswd.conf. In order
to use this option, you will need to run the "tconf" utility from the
SRP package to generate local entries for this file. Note that if
Specifies the modulus/generator index in /etc/tpasswd.conf. In order
to use this option, you will need to run the "tconf" utility from the
SRP package to generate local entries for this file. Note that if
.I <clientname>
Specifies the client name. The password validator is a hashed
combination of the client's name and password, and both are required.
.I <clientname>
Specifies the client name. The password validator is a hashed
combination of the client's name and password, and both are required.
-If the client name is not supplied on the command line, srp-entry will
+If the client name is not supplied on the command line, srp\-entry will
prompt for the client name first.
.SH FILES
.TP
prompt for the client name first.
.SH FILES
.TP
+.B /etc/ppp/srp\-secrets
Usernames, passwords and IP addresses for SRP authentication. This
file should be owned by root and not readable or writable by any other
user. Pppd will log a warning if this is not the case. Note that
Usernames, passwords and IP addresses for SRP authentication. This
file should be owned by root and not readable or writable by any other
user. Pppd will log a warning if this is not the case. Note that
-srp-entry does not write to this file. The user is responsible for
-copying the output of srp-entry into this file.
+srp\-entry does not write to this file. The user is responsible for
+copying the output of srp\-entry into this file.
.TP
.B /etc/tpasswd.conf
Indexed copies of tested modulus/generator combinations; part of the
.TP
.B /etc/tpasswd.conf
Indexed copies of tested modulus/generator combinations; part of the
.I PPP Extensible Authentication Protocol (EAP).
March 1998.
.TP
.I PPP Extensible Authentication Protocol (EAP).
March 1998.
.TP
-.B draft-ietf-pppext-eap-srp-03.txt
+.B draft\-ietf\-pppext\-eap\-srp\-03.txt
-.I EAP SRP-SHA1 Authentication Protocol.
+.I EAP SRP\-SHA1 Authentication Protocol.
July 2001.
.TP
.B RFC2945
July 2001.
.TP
.B RFC2945
-.\" @(#) $Id: pppdump.8,v 1.1 1999/04/01 11:44:55 paulus Exp $
+.\" @(#) $Id: pppdump.8,v 1.2 2004/11/13 12:22:49 paulus Exp $
.TH PPPDUMP 8 "1 April 1999"
.SH NAME
pppdump \- convert PPP record file to readable format
.SH SYNOPSIS
.B pppdump
[
.TH PPPDUMP 8 "1 April 1999"
.SH NAME
pppdump \- convert PPP record file to readable format
.SH SYNOPSIS
.B pppdump
[
.PP
The options are as follows:
.TP
.PP
The options are as follows:
.TP
Prints the bytes sent and received in hexadecimal. If neither this
Prints the bytes sent and received in hexadecimal. If neither this
-option nor the \fB-p\fR option is specified, the bytes are printed as
+option nor the \fB\-p\fR option is specified, the bytes are printed as
the characters themselves, with non-printing and non-ASCII characters
printed as escape sequences.
.TP
the characters themselves, with non-printing and non-ASCII characters
printed as escape sequences.
.TP
Collects the bytes sent and received into PPP packets, interpreting
the async HDLC framing and escape characters and checking the FCS
(frame check sequence) of each packet. The packets are printed as hex
values and as characters (non-printable characters are printed as
`.').
.TP
Collects the bytes sent and received into PPP packets, interpreting
the async HDLC framing and escape characters and checking the FCS
(frame check sequence) of each packet. The packets are printed as hex
values and as characters (non-printable characters are printed as
`.').
.TP
-.B -d
-With the \fB-p\fR option, this option causes
+.B \-d
+With the \fB\-p\fR option, this option causes
.B pppdump
to decompress packets which have been compressed with the BSD-Compress
or Deflate methods.
.TP
.B pppdump
to decompress packets which have been compressed with the BSD-Compress
or Deflate methods.
.TP
Reverses the direction indicators, so that `sent' is printed for
bytes or packets received, and `rcvd' is printed for bytes or packets
sent.
.TP
Reverses the direction indicators, so that `sent' is printed for
bytes or packets received, and `rcvd' is printed for bytes or packets
sent.
.TP
Use \fImru\fR as the MRU (maximum receive unit) for both directions of
Use \fImru\fR as the MRU (maximum receive unit) for both directions of
-the link when checking for over-length PPP packets (with the \fB-p\fR
+the link when checking for over-length PPP packets (with the \fB\-p\fR
option).
.SH SEE ALSO
pppd(8)
option).
.SH SEE ALSO
pppd(8)
-.\" @(#) $Id: pppstats.8,v 1.3 1996/07/01 01:22:35 paulus Exp $
+.\" @(#) $Id: pppstats.8,v 1.4 2004/11/13 12:22:49 paulus Exp $
.TH PPPSTATS 8 "26 June 1995"
.SH NAME
pppstats \- print PPP statistics
.SH SYNOPSIS
.B pppstats
[
.TH PPPSTATS 8 "26 June 1995"
.SH NAME
pppstats \- print PPP statistics
.SH SYNOPSIS
.B pppstats
[
.I <secs>
] [
.I interface
.I <secs>
] [
.I interface
.SH DESCRIPTION
The
.B pppstats
.SH DESCRIPTION
The
.B pppstats
-utility reports PPP-related statistics at regular intervals for the
+utility reports PPP\-related statistics at regular intervals for the
specified PPP interface. If the interface is unspecified, it will
default to ppp0.
The display is split horizontally
specified PPP interface. If the interface is unspecified, it will
default to ppp0.
The display is split horizontally
.PP
The options are as follows:
.TP
.PP
The options are as follows:
.TP
Display absolute values rather than deltas. With this option, all
reports show statistics for the time since the link was initiated.
Without this option, the second and subsequent reports show statistics
for the time since the last report.
.TP
Display absolute values rather than deltas. With this option, all
reports show statistics for the time since the link was initiated.
Without this option, the second and subsequent reports show statistics
for the time since the last report.
.TP
Repeat the display
.I count
times. If this option is not specified, the default repeat count is 1
if the
Repeat the display
.I count
times. If this option is not specified, the default repeat count is 1
if the
option is not specified, otherwise infinity.
.TP
option is not specified, otherwise infinity.
.TP
Display additional statistics summarizing the compression ratio
achieved by the packet compression algorithm in use.
.TP
Display additional statistics summarizing the compression ratio
achieved by the packet compression algorithm in use.
.TP
Display additional statistics relating to the performance of the Van
Jacobson TCP header compression algorithm.
.TP
Display additional statistics relating to the performance of the Van
Jacobson TCP header compression algorithm.
.TP
Pause
.I wait
seconds between each display. If this option is not specified, the
default interval is 5 seconds.
.TP
Pause
.I wait
seconds between each display. If this option is not specified, the
default interval is 5 seconds.
.TP
Instead of the standard display, show statistics indicating the
performance of the packet compression algorithm in use.
.PP
The following fields are printed on the input side when the
Instead of the standard display, show statistics indicating the
performance of the packet compression algorithm in use.
.PP
The following fields are printed on the input side when the
option is not used:
.TP
.B IN
option is not used:
.TP
.B IN
.B VJUNC
The number of header-uncompressed TCP packets received by this
interface. Not reported when the
.B VJUNC
The number of header-uncompressed TCP packets received by this
interface. Not reported when the
option is specified.
.TP
.B VJERR
The number of corrupted or bogus header-compressed TCP packets
received by this interface. Not reported when the
option is specified.
.TP
.B VJERR
The number of corrupted or bogus header-compressed TCP packets
received by this interface. Not reported when the
option is specified.
.TP
.B VJTOSS
The number of VJ header-compressed TCP packets dropped on reception by
this interface because of preceding errors. Only reported when the
option is specified.
.TP
.B VJTOSS
The number of VJ header-compressed TCP packets dropped on reception by
this interface because of preceding errors. Only reported when the
option is specified.
.TP
.B NON-VJ
The total number of non-TCP packets received by this interface. Only
reported when the
option is specified.
.TP
.B NON-VJ
The total number of non-TCP packets received by this interface. Only
reported when the
option is specified.
.TP
.B RATIO
option is specified.
.TP
.B RATIO
packet compression scheme in use, defined as the uncompressed size
divided by the compressed size.
Only reported when the
packet compression scheme in use, defined as the uncompressed size
divided by the compressed size.
Only reported when the
option is specified.
.TP
.B UBYTE
The total number of bytes received, after decompression of compressed
packets. Only reported when the
option is specified.
.TP
.B UBYTE
The total number of bytes received, after decompression of compressed
packets. Only reported when the
option is specified.
.PP
The following fields are printed on the output side:
option is specified.
.PP
The following fields are printed on the output side:
The number of TCP packets transmitted from this interface with
VJ-uncompressed TCP headers.
Not reported when the
The number of TCP packets transmitted from this interface with
VJ-uncompressed TCP headers.
Not reported when the
option is specified.
.TP
.B NON-VJ
The total number of non-TCP packets transmitted from this interface.
Not reported when the
option is specified.
.TP
.B NON-VJ
The total number of non-TCP packets transmitted from this interface.
Not reported when the
option is specified.
.TP
.B VJSRCH
The number of searches for the cached header entry for a VJ header
compressed TCP packet. Only reported when the
option is specified.
.TP
.B VJSRCH
The number of searches for the cached header entry for a VJ header
compressed TCP packet. Only reported when the
option is specified.
.TP
.B VJMISS
The number of failed searches for the cached header entry for a
VJ header compressed TCP packet. Only reported when the
option is specified.
.TP
.B VJMISS
The number of failed searches for the cached header entry for a
VJ header compressed TCP packet. Only reported when the
option is specified.
.TP
.B RATIO
option is specified.
.TP
.B RATIO
packet compression scheme in use, defined as the size
before compression divided by the compressed size.
Only reported when the
packet compression scheme in use, defined as the size
before compression divided by the compressed size.
Only reported when the
option is specified.
.TP
.B UBYTE
The total number of bytes to be transmitted, before packet compression
is applied. Only reported when the
option is specified.
.TP
.B UBYTE
The total number of bytes to be transmitted, before packet compression
is applied. Only reported when the
option is specified.
.PP
When the
option is specified.
.PP
When the
option is specified,
.Nm pppstats
instead displays the following fields, relating to the packet
option is specified,
.Nm pppstats
instead displays the following fields, relating to the packet
pon, poff, plog \- starts up, shuts down or lists the log of PPP connections
.SH SYNOPSIS
.B pon
pon, poff, plog \- starts up, shuts down or lists the log of PPP connections
.SH SYNOPSIS
.B pon
-[ isp-name [ options ] ]
+[ isp\-name [ options ] ]
-[ -r ] [ -d ] [ -c ] [ -a ] [ -h ] [ isp-name ]
+[ \-r ] [ \-d ] [ \-c ] [ \-a ] [ \-h ] [ isp\-name ]
.br
.B plog
[ arguments ]
.br
.B plog
[ arguments ]
\fBpon\fP, invoked without arguments, runs the \fI/etc/ppp/ppp_on_boot\fP
file, if it exists and is executable. Otherwise, a PPP connection will be
started using configuration from \fI/etc/ppp/peers/provider\fP.
\fBpon\fP, invoked without arguments, runs the \fI/etc/ppp/ppp_on_boot\fP
file, if it exists and is executable. Otherwise, a PPP connection will be
started using configuration from \fI/etc/ppp/peers/provider\fP.
-This is the default behaviour unless an \fBisp-name\fP argument is given.
+This is the default behaviour unless an \fBisp\-name\fP argument is given.
.PP
For instance, to use ISP configuration "myisp" run:
.IP
.PP
For instance, to use ISP configuration "myisp" run:
.IP
to renegotiate compression.
.TP
.B "\-a"
to renegotiate compression.
.TP
.B "\-a"
-stops all running ppp connections. If the argument \fBisp-name\fP
+stops all running ppp connections. If the argument \fBisp\-name\fP
is given it will be ignored.
.TP
.B "\-h"
is given it will be ignored.
.TP
.B "\-h"
pppd-generated information in one logfile, that plog can show, you need the
following line in your \fI/etc/syslog.conf\fP file:
.PP
pppd-generated information in one logfile, that plog can show, you need the
following line in your \fI/etc/syslog.conf\fP file:
.PP
-local2.* -/var/log/ppp.log
+local2.* \-/var/log/ppp.log
.RE
.SH FILES
.TP
.I /etc/ppp/options
PPPd system options file.
.TP
.RE
.SH FILES
.TP
.I /etc/ppp/options
PPPd system options file.
.TP
+.I /etc/ppp/pap\-secrets
System PAP passwords file.
.TP
System PAP passwords file.
.TP
-.I /etc/ppp/chap-secrets
+.I /etc/ppp/chap\-secrets
System CHAP passwords file.
.TP
.I /etc/ppp/peers/
System CHAP passwords file.
.TP
.I /etc/ppp/peers/