Technical article 105424

What do the different stages in PPP negotiation signify?

OpenServer 5.0.0OpenServer 5.0.2OpenServer 5.0.4OpenServer 5.0.5OpenServer 5.0.6UnixWare 7.0.0UnixWare 7.0.1UnixWare 7.1.1UnixWare 7.1.3Open UNIX 8

Written · Last revised

Problem

In looking over debugging output for my PPP connection, what is the significance of the various phases of the connection attempt?

Solution

The debug output is sent to different files depending upon the exact release of your operating system:

     OS                               Logfile
=====================================================
SCO UnixWare . . . . . . . . . . /var/adm/logs/osmlog
SCO OpenServer (5 and 3) . . . . /usr/adm/syslog
SCO Internet FastStart . . . . . /usr/adm/pppd.log

In all of these releases, you will see PPP negotiation involving a minimum of two stages, and possibly as many as four.

The negotiation stages, in order, are:

1. ICP (SCO OpenServer and UnixWare PPP only) 2. LCP 3. Authentication (optional) 4. IPCP

Examples of each phase of negotiation are shown below:

ICP (Internet Control Protocol):  negotiation between drivers
and devices internal to the local system running SCO PPP; no
configuration parameters are negotiated here.

Jan 13 14:05:40 in.pppd[249]: Link id(18):ICP:administrative open,Initial->Starting Jan 13 14:05:40 in.pppd[249]: Link id(18):ICP:low layer up,Starting->Req_sent Jan 13 14:05:40 in.pppd[249]: Link id(18):ICP:Send config_req Jan 13 14:05:40 in.pppd[249]: Link id(18):ICP:Receive config_req+,Req_sent->Ack_Sent Jan 13 14:05:40 in.pppd[249]: Link id(18):ICP:Send config_ack Jan 13 14:05:40 in.pppd[249]: Link id(18):ICP:Receive config_ack,Ack_Sent->Opened

LCP (Link Control Protocol): the PPP driver negotiates several parameters with the remote host: maximum receive units, asynchronous control character map, magic number, protocol field compression, and address-control field compression.

Jan 13 14:05:40 in.pppd[249]: Link id(18):LCP:low layer up,Initial->Closed
Jan 13 14:05:40 in.pppd[249]: Link id(18):LCP:administrative
open,Closed->Req_sent
Jan 13 14:05:40 in.pppd[249]: Link id(18):LCP:Send config_req
Jan 13 14:05:40 in.pppd[249]: Link id(18):LCP:Send option MRU 1500
Jan 13 14:05:40 in.pppd[249]: Link id(18):LCP:Send option ACCM 0
Jan 13 14:05:40 in.pppd[249]: Link id(18):LCP:Send option magic 83dec664
Jan 13 14:05:40 in.pppd[249]: Link id(18):LCP:Send option protocol compression
Jan 13 14:05:40 in.pppd[249]: Link id(18):LCP:Send option addr&ctl compression
Jan 13 14:05:40 in.pppd[249]: Link id(18):LCP:Receive
config_ack,Req_sent->Ack_Rcvd
Jan 13 14:05:42 in.pppd[249]: Link id(18):LCP:Receive option MRU 1500 (Ack)
Jan 13 14:05:42 in.pppd[249]: Link id(18):LCP:Receive option ACCM 0 (Ack)
Jan 13 14:05:42 in.pppd[249]: Link id(18):LCP:Receive option magic 221784f3(Ack)
Jan 13 14:05:42 in.pppd[249]: Link id(18):LCP:Receive option protocol
compression (Ack)
Jan 13 14:05:42 in.pppd[249]: Link id(18):LCP:Receive option addr&ctl
compression(Ack)
Jan 13 14:05:42 in.pppd[249]: Link id(18):LCP:Receive
config_req+,Ack_Rcvd->Opened
Jan 13 14:05:42 in.pppd[249]: Link id(18):LCP:Send config_ack
Jan 13 14:05:42 in.pppd[249]: Link id(18):LCP negotiated options:
Jan 13 14:05:42 in.pppd[249]: Link id(18):  local MRU:1500 remote MRU:1500
Jan 13 14:05:42 in.pppd[249]: Link id(18):  local ACCM:0 remote ACCM:0
Jan 13 14:05:42 in.pppd[249]: Link id(18):  local do protocol compression
Jan 13 14:05:42 in.pppd[249]: Link id(18):  remote do protocol compression
Jan 13 14:05:42 in.pppd[249]: Link id(18):  local do addr&ctl compression
Jan 13 14:05:42 in.pppd[249]: Link id(18):  remote do addr&ctl compression
Authentication (optional):  the remote host is authenticated
using PAP or CHAP if the local or remote side requires it.
Jan 13 14:05:42 in.pppd[249]: Link id(18):send a PAP_REQ packet:
Jan 13 14:05:42 in.pppd[249]: Link id(18):  PID:mugwump.i88.  isc.com
Jan 13 14:05:42 in.pppd[249]: Link id(18):  PWD:Bull
Jan 13 14:05:42 in.pppd[249]: Link id(18):receive a PAP_REQ packet:
Jan 13 14:05:42 in.pppd[249]: Link id(18):  PID:krusty.i88.  isc.com
Jan 13 14:05:42 in.pppd[249]: Link id(18):  PWD:Blazer
Jan 13 14:05:42 in.pppd[249]: received PPCID_PAP
Jan 13 14:05:42 in.pppd[249]: PPCID_PAP auth success
Jan 13 14:05:42 in.pppd[249]: sent PPCID_PAP
Jan 13 14:05:42 in.pppd[249]: Link id(18):send a PAP_ACK packet
Jan 13 14:05:42 in.pppd[249]: Link id(18):receive a PAP_ACK packet
Jan 13 14:05:42 in.pppd[249]: Link id(18):IPCP:low layer up, Initial->Closed
Jan 13 14:05:42 in.pppd[249]: Link id(18):IPCP:administrative
open,Closed->Req_sent
Jan 13 14:05:42 in.pppd[249]: Link id(18):IPCP:Send config_req
Jan 13 14:05:42 in.pppd[249]: received PPCID_PAP
Jan 13 14:05:42 in.pppd[249]: Link id(18):receive a PAP_REQ packet:
Jan 13 14:05:42 in.pppd[249]: Link id(18):  PID:krusty.i88.isc.com
Jan 13 14:05:42 in.pppd[249]: PPCID_PAP auth success
Jan 13 14:05:42 in.pppd[249]: sent PPCID_PAP
Jan 13 14:05:42 in.pppd[249]: Link id(18):  PWD:Blazer
Jan 13 14:05:42 in.pppd[249]: Link id(18):send a PAP_ACK packet
IPCP (Internet Protocol Control Protocol):  the PPP driver
negotiates Van Jacobsen TCP/IP header compression and local
and remote IP addresses for the connection.
Jan 13 14:05:42 in.pppd[249]: Link id(18):IPCP:low layer up,Initial->Closed
Jan 13 14:05:42 in.pppd[249]: Link id(18):IPCP:administrative
open,Closed->Req_sent
Jan 13 14:05:42 in.pppd[249]: Link id(18):IPCP:Send config_req
Jan 13 14:05:42 in.pppd[249]: Link id(18):IPCP:Send option vj compression with
MSI:15 CSI:1
Jan 13 14:05:42 in.pppd[249]: Link id(18):IPCP:Send option ip address:0.0.0.0
Jan 13 14:05:43 in.pppd[249]: Link id(18):IPCP:Receive option ip
address:207.12.13.6
Jan 13 14:05:43 in.pppd[249]: Link id(18):IPCP:Ack the received option ip
address
Jan 13 14:05:43 in.pppd[249]: Link id(18):IPCP:Receive option vj compression
MSI:15 CSI:1 (Ack)
Jan 13 14:05:43 in.pppd[249]: Link id(18):IPCP:Receive
config_req+,Req_sent->Ack_Sent
Jan 13 14:05:43 in.pppd[249]: Link id(18):IPCP:Send config_ack
Jan 13 14:05:43 in.pppd[249]: Link id(18):IPCP:Receive
config_nak/rej,Ack_Sent->Ack_Sent
Jan 13 14:05:43 in.pppd[249]: Link id(18):IPCP:Send config_req
Jan 13 14:05:43 in.pppd[249]: Link id(18):IPCP:Send option vj compression with
MSI:15 CSI:1
Jan 13 14:05:43 in.pppd[249]: Link id(18):IPCP:Remote Nak ip address with
207.12.13.17
Jan 13 14:05:43 in.pppd[249]: Link id(18):IPCP:Send option ip
address:207.12.13.17
Jan 13 14:05:44 in.pppd[249]: Link id(18):IPCP:Receive
config_ack,Ack_Sent->Opened
Jan 13 14:05:44 in.pppd[249]: Link id(18):IPCP negotiated options:
Jan 13 14:05:44 in.pppd[249]: Link id(18):  local address:207.12.13.17
Jan 13 14:05:44 in.pppd[249]: Link id(18):  remote address:207.12.13.6
Jan 13 14:05:44 in.pppd[249]: Link id(18):  local do vj compression MSI:16 CSI:1
Jan 13 14:05:44 in.pppd[249]: Link id(18):  remote do vj compression MSI:16
CSI:1
NOTES:    Before any PPP link is established and data can flow over the
          link, the PPP daemon must read the parameters in the link
          configuration and give these parameters to the PPP driver; the
          driver must negotiate with the remote host the characteristics of
          the link using the link parameters as a starting point.  If the
          local and remote hosts can agree on the characteristics to use for
          the link, the link is established.  If the two hosts cannot agree,
          the link fails.

The presence of an authentication stage depends on whether the local or remote side requires authentication.

The stage of negotiation is identified in each logfile entry by
the presence of "ICP", "LCP" or "IPCP", along with a time and date
stamp.  Log entries about the authentication stage do not have an
identifier as ICP, LCP, and IPCP do, but they do include either
the string "PAP" or "CHAP", which refer to the two authentication
protocols that SCO supports.
The flow of the log should progress from ICP, through LCP and
authentication, to IPCP.  If a failure (Nak) occurs at an earlier
stage, the later stages may still occur but the information will
be unusable because of the earlier failure.  It is also possible
that later stages may not occur and the connection will be
unsuccessful.

If authentication or IPCP entries appear for the link ID you are troubleshooting, then it is likely that the LCP stage was successful. As mentioned, however, it is possible for the LCP stage to finish negotiating with discrepancies in the local and remote values for ACCM, MRU, or link compression type.

If successful, the value of the parameters negotiated will be
listed in the logfile.  If no authentication or IPCP entries
appear, then a problem might exist with LCP negotiation.  Typical
problems at this stage are:
1) The local and remote hosts disagree about parameters.  If
   this occurs, you will see Nak and Reject entries.  A Nak or
   Reject will be present for a particular parameter.  Try
   changing the value of the parameter causing the Nak
   or rejection.
2) The local host does not receive any good packets from the
   remote host.  If this occurs, you will see many LCP entries
   that say "Send", but none that say "Receive".  Reasons that
   this might occur include:  a bad checksum in response packets
   from the remote host, badly formatted packets from the remote
   host, or no packets received from the remote host.
If IPCP entries appear for your interface, then the authentication
stage was either skipped (neither side requires authentication),
or successful.  If no IPCP entries appear and LCP appears to have
completed successfully (no Nak or Rejects on LCP stage packets),
then a problem is likely with authentication.  Look for an
authentication entry with a PAP or CHAP failure indicated.  Typical
problems here are the sending of an incorrect password or incorrect
packet ID.
If all of the preceding stages appear successful but the connection
still fails, the problem may be in the IPCP negotiation stage. The
typical problem at this stage is a disagreement about the Van
Jacobsen TCP/IP header compression or IP address parameters between
the local and remote systems.  If this occurs, you will see a Nak
or Reject entry for a particular parameter.  Try changing the
value of the parameter causing the Nak or rejection.

From the Xinuos technical article database, record 105424. Reproduced with permission. The original is at www.sco.com/ta/105424, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.