Some aspects of PPP behaviour can be configured through an INI file. For
the standard PPP operation, the INI file is
private/101f7989/esock/ppp.ini
. For incoming PPP, the INI file
used is private/101f7989/esock/pppd.ini
.
The file can have the following sections.
Where sections or entries are not present, defaults are applied.
Note that [ReadTimer]
and [InactiveTimer]
sections were used in v6.0, but are ignored later.
These settings affect all of LCP, CCP, IPCP and IPV6CP. The entries are in pairs: the first entry is a flag indicating whether the value in the second entry should be used or not. If the flag is not set, or no entry is present, a default value is used.
These settings relate to the Max-Failure counter described in RFC 1661, 4.6.
PPPEnableMaxFailure
: 0: PPPMaxFailureCount
disabled; 1: PPPMaxFailureCount
enabled.
PPPMaxFailureCount
: number of NAKs to receive before
rejecting an option. By default, a maximum count of 5 is used.
These settings relate to the Max-Configure counter described in RFC 1661, 4.6.
PPPEnableMaxRestart
: 0: PPPMaxRestartCount
disabled; 1: PPPMaxRestartCount
enabled.
PPPMaxRestartCount
: number of Configure-Request packets to
send without getting a valid response. By default, a maximum count of 10 is
used.
These settings relate to the Restart Timer counter described in RFC 1661, 4.6.
PPPEnableRestartTimer
: 0: PPPRestartPeriod
disabled; 1: PPPRestartPeriod
enabled.
PPPRestartPeriod
: timeout period in milliseconds. By
default, a maximum count of 3000 is used.
These settings control the buffering of PPP frames.
LoMark
: send buffer low water mark below which flow is
turned on. The default is 16.
HiMark
: send buffer high water mark above which flow is
turned off. The default is 32.
These settings can be overriden for a particular port. To do this,
create a section [link::<port-name>]
, e.g.
[link::comm::0]
, with LoMark
and HiMark
settings.
These settings relate to the Maximum-Receive-Unit (MRU) described in RFC 1661, 6.1.
PPPEnableMru
: 0: PPPMru
disabled; 1:
PPPMru
enabled.
PPPMru
: negotiate this value for the MRU. The default is
0.
These settings relate to the Async-Control-Character-Map (ACCM) described in RFC 1662, 7.1.
PPPEnableAccm
: 0: PPPAccm
disabled; 1:
PPPAccm
enabled.
PPPAccm
: negotiate this value for ACCM (XON/XOFF are added
to this, if necessary). The value should be specified in hex, for example,
PPPAccm=FFFFFF0F
. The default is 0.
These settings control the sending of LCP echo-request packets [RFC 1661, 5.8] that can be used in debugging, determining link quality, and performance testing. If the setting is enabled, an echo request will be sent to the server, and at each defined period, a check performed to see if an answer was received. The link will be closed if 4 out of 5 echo reply pairs fail (i.e. no reply is received from the server).
PPPEnableLRD
: 0: PPPLRDPeriod
disabled; 1:
PPPLRDPeriod
enabled.
PPPLRDPeriod
: period in seconds at which to send echo
request packets, and to check for replies.
These settings control logging. Logs are written in debug mode only,
and are done through the CommsDebugUtility logger, which by default logs to
C:\logs\log.txt
. PPP entries in this log are tagged "ppp".
Additionally, packets tagged "TcpDump" are dumped in binary form to the log.
These entries can be extracted with the tool splitlog.bat
, and
used as an input file for Ethereal. Ethereal is a general purpose packet
analyser that can parse a wide variety of protocols. It is freeware and can be
obtained from http://www.ethereal.com.
level
: level of logging performed. The recommended setting
is level=0
. This logs state machine transitions.
level=4
logs parsed PPP packets, while level=5
logs a
hex dump of PPP packets. These are slow, and superseded by tcpdump logging.
logFormat
: sets the format of the binary logging. The only
valid value is 0, which is also the default.
linkFormat
: sets what to log. Possible values are:
0: the entire PPP frame is logged. This is the default.
1: only IP frames are logged.