Configuring the Point-to-Point Protocol (PPP)

Testing remote access

Establishing an incoming link to a remote access endpoint requires the following:

Both of the above activities are logged by default to the file /usr/adm/syslog. Following the above activities, communication occurs between the PPP shell and the PPP daemon; this activity is also logged to the same file. Below is a replication of a logfile showing the entries that appear when the above activities are successful.
  1 Feb 22 17:15:36 -ppp[350]: login on '/dev/tty1A'
  2 Feb 22 17:15:36 pppd[207]: accept on socket 5
  3 Feb 22 17:15:36 -ppp[350]: sent pppd m_type=16, m_pid=350,
  4 m_tty='/dev/tty1A'
  5 Feb 22 17:15:36 pppd[207]: pppd_sockread s=6
  6 Feb 22 17:15:36 pppd[207]: read m_type=16
  7 Feb 22 17:15:36 pppd[207]: Incoming call on '/dev/tty1A',
  8 pid=350, name=nppp
  9 Feb 22 17:15:37 pppd[207]: Connecting '/dev/tty1A' under PPP
 10 Feb 22 17:15:37 pppd[207]: Assigned link id for incoming
 11 link(login:nppp pid:350) is 80

remote host login
The remote host must perform a successful login to the local host before any PPP activity occurs. To troubleshoot these steps you should see the logging of information at the console.

line 1
The PPP shell (as represented by ``-ppp'') starts and informs the PPP daemon that a PPP login exists on /dev/tty1A.

line 2
The PPP daemon (represented by ``pppd'') acknowledges the login.

lines 3,4
The PPP shell passes additional information to the daemon.

lines 7-11
The PPP daemon acknowledges receipt of an incoming call, connects the tty under the PPP driver, and assigns an ID number to the incoming link.
If you know which tty the PPP link you are troubleshooting tried to login to or you know the login name the remote host used, you can search on either in the /usr/adm/syslog file to see if the above activities completed successfully. Success is achieved if pppd assigned a link ID.

If the PPP shell starts, it is most likely that the above activities will be successful. At this stage, most incoming link failures occur because the remote host is unable to login to the local host or because the login does not start a PPP shell because of incorrect configuration information. For a description of the required information, see ``Configuring an endpoint for remote access''.

If you find that pppd has successfully assigned a link ID for the PPP link you are troubleshooting, go to ``Troubleshooting PPP negotiation'' to continue troubleshooting.

Next topic: Verifying integrity of a dedicated serial line
Previous topic: Testing manual dialup connectivity

© 2003 Caldera International, Inc. All rights reserved.
SCO OpenServer Release 5.0.7 -- 11 February 2003