User Guide

Local and/or remote
IP: STPro PPP
server/client behavior
Primary and secondar
y
DNS server
LCP echo () requests
11 Configuration and Use - Routed PPPoA
115 / 288
3EC 36231 ABAA TCZZA Ed. 01
During the opening of a PPP session, IP addresses are negotiated
between the two PPP peers for the PPP entry. The 'Local IP' and
'Remote IP' fields influence this negotiation.
Typically at the client side, the 'Local IP' and 'Remote IP' fields are
left empty. This forces the client to ask the RAS for IP addresses.
In case you want to set up the STPro as PPP server, suitable values
for your network configuration must be supplied:
 Setting a local IP address
Forces the remote PPP client (if it allows to) to accept this IP
address as the STPro PPP session IP address.
 Setting a remote IP address
Forces the remote client (if it allows to) to accept this IP
address as its PPP session IP address.
These fields allow - optionally - to enter the IP address(es) of the
primary, and optionally the secondary, DNS server(s). If you supply
these IP addresses the STPro will negotiate these addresses with
the remote side of the PPP entry. If these fields are left blank the
remote side will supply the IP addresses of the primary and
secondary DNS servers.
See chapter 15 for more information on DNS.
If a PPP session is up, it can issue Link Control Protocol (LCP)
echo requests at regular intervals and expect LCP echo replies in
return.
This checkbox allows to turn on/off LCP echo request/replies by
respectively checking () or unchecking the 'LCP echo' checkbox.
By default LCP echo is on (i.e. flagged ) allowing the local PPP
peer to detect communication errors resulting in closing of the PPP
session.