Alcatel Speed Touch Wireless User Manual page 143

Local and/or remote
IP: STWireless PPP
server/client behavior
LCP echo (n) requests
PAP (n): used
authentication protocol
ACCOMP (n): used
PPP framing
3EC 17766 AAAA TCZZA Ed. 01
During the opening of a PPP session, IP addresses are negotiated
between the two PPP peers for the PPP connection. The Local IP',
and 'Remote IP' fields influence this negotiation.
Typically at the client side, the 'Local IP', and 'Remote IP' boxes are
left empty. This forces the client to ask the remote server for
addresses.
In case you want to set up the STWireless 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 STWireless 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.
If a PPP session is up, it can issue Link Control Protocol (LCP) echo
requests at regular intervals and expects LCP echo replies in
return.
This checkbox allows to turn on/off LCP echo request/replies by
respectively setting (n), or clearing the flag.
By default LCP echo is on (i.e. flagged n), allowing the local PPP
peer to detect communication errors, resulting in closing of the
PPP session.
The default PPP authentication protocol is Challenge Handshake
Authentication Protocol (CHAP).
Setting the PAP flag (n) will use Password Authentication
Protocol (PAP) instead.
Address and Control field COMPression (ACCOMP), sometimes
abbreviated as ACCM, is by default enabled, i.e. flagged (n).
This option flag should not be cleared, except in special
circumstances, i.e. where the remote PPP server expects to see
HDLC like framing (FF03 imposed to the PPP packet).
8 Data Services - PPP & IP Routing
143 / 362