ppp.Systems.4 (2010 09)

p
ppp.Systems(4) ppp.Systems(4)
NAME
ppp.Systems - PPP neighboring systems description file format
DESCRIPTION
The file
/etc/ppp/Systems
describes how to connect with neighboring systems via PPP.
Format
Entries are one to a line; blank lines are ignored. Comments begin with a
# and extend to the end of the
line. Upper/lower case distinctions are ignored in hostname specifications, but are significant elsewhere.
Fields on a line are separated by horizontal white space (blanks or tabs). If a chat script ends with a
backslash (
\), the next line is considered a continuation of the chat script. Continuations may only occur
in the midst of a chat script.
Each entry must contain six fields, in the following order:
name The hostname or IP address of the destination machine, which should be resolvable locally.
when A string that indicates the days of the week and the times of day when the system can be
called (for example, MoTuTh0800-1740). The day portion may be a list containing any of Su,
Mo, Tu, We, Th, Fr or Sa. The day may also be Wk for any weekday (same as MoTuWeThFr) or
Any for any day (same as SuMoTuWeThFrSa).
You can indicate hours in a range (for example, 0800-1230). If you do not specify a time, calls
will be allowed at any time.
Note that a time range that spans 0000 is permitted. For example, 0800-0600 means that all
times are allowed except times between 6 AM and 8 AM.
Multiple date specifications that are separated by a vertical bar (|) are allowed. For example,
Any0100-0600|Sa|Su means that the system can be called any day between 1 AM and 6 AM
or any time on Saturday and Sunday.
The entire (sequence of) days and times may be followed by a semicolon and up to three
decimal numbers separated by hyphens:
one If only one number follows the semicolon, it is used as the redial delay, which is the
initial time (in seconds) before a failed call will be retried. For example, Any;60
means call any time, but wait at least 60 seconds after a failure has occurred before
trying to call again. If a call retry fails,
pppd will double the delay before trying
again. If no initial retry delay is specified, 10 seconds is assumed.
two If two numbers follow the semicolon, the second number is used as the maximum
redial delay, which is the maximum time (in seconds) to delay before retrying a call.
The retry time will double with each unsuccessful call until it reaches this value, after
which the call will be retried every time the maximum number of seconds passes. If
no maximum retry delay is specified, 3600 seconds is assumed.
three If three numbers follow the semicolon, the first is used as the callback delay, the
second as the redial delay, and the third as the maximum redial delay. The callback
delay is the time (in seconds) to wait before attempting to re-establish a previously
active connection that ended because of an abrupt line disconnection (a Hangup or
SIGHUP event in the log file). The default is not to delay before calling back.
During the delay following an unsuccessful call, any level 7 debugging messages written to
pppd.log will have the message dial failed appended.
device If set to
ACU, any device in Devices with a matching speed may be used. The device’s dialer
chat script will be executed first, followed by the Systems chat script.
If set to the name of a device in the
/dev directory (tty00, cua, etc.), then there may be an
optional corresponding Direct entry in Devices, Dialers will not be consulted, and only
the Systems chat script will be executed.
If set to
tcp, then it must be followed by a slash, then the hostname or IP address of the sys-
tem that will serve as the destination of the PPP link, then another slash, then the socket
number on which to contact the remote PPP daemon.
speed The speed of the connection. If the device field is ACU, the speed field will be string matched
against entries in
Devices. Speeds must either be valid speed numbers or must begin with
them (2400, 38400, 19200-PEP, etc.). If the device field is tcp ... or telnet ..., the
HP-UX 11i Version 3: September 2010 1 Hewlett-Packard Company 1

Summary of content (4 pages)