Configuring the Point-to-Point Protocol (PPP)

Testing manual dialup connectivity

To test an outgoing link made from a manual dialup endpoint:

  1. Turn on PPP driver, PPP daemon, and UUCP logging. See ``Logging PPP information''.

  2. Execute the following command:

    pppattach attachname

    attachname should be the value of the attach link parameter in the endpoint configuration entry for the link you are troubleshooting.

  3. Check to see if pppattach successfully built a network interface for this link by executing:

    ifconfig -a

    If an interface does exist for the link you are troubleshooting, go to the next step. If no interface was built, the local system was unable to establish a PPP link. To determine where the process broke, look in the syslog file where the PPP driver and PPP daemon log information has been collected. The following example logfile and the description below the example show the first steps PPP uses to achieve host-to-host connectivity. You can view the logfile to see if these steps have been successful. If these steps have been successful, go to ``Troubleshooting PPP negotiation'' to troubleshoot the PPP negotiation, which occurs after host-to-host connectivity has been established.

      1 Mar 14 09:44:27 pppd[396]: accept on socket 6
      2 Mar 14 09:44:27 pppd[409]: dial process sent pppd m_type=18, m_pid=409,
      3 m_tty='/dev/tty1A'
      4 Mar 14 09:44:27 pppd[396]: pppd_sockread s=7
      5 Mar 14 09:44:27 pppd[396]: Connected to remote system: tty=/dev/tty1A,
      6 pid=409
      7 Mar 14 09:44:27 pppd[396]: ppp_add_conn
      8 Mar 14 09:44:27 pppd[396]: Assigned link id for outgoing link (pid:409)
      9 is 1

    lines 2,3
    PPP daemon requests that UUCP establish a UUCP connection.

    UUCP connection made
    Not shown in this logfile is pppd's contacting of the UUCP facility to request a UUCP connection. This information is logged at the local host console.

    If the modem does not connect, check the /etc/ppphosts file to verify that the uucp parameter has the correct value for the remote host and that the value has an entry in the /usr/lib/uucp/Systems file. Verify that the entries in the /usr/lib/uucp/Devices and /usr/lib/uucp/Dialers files are correct for supporting the Systems file entry.

    If the modem does connect but then disconnects, you can also use the UUCP error codes and PPP debugging information to troubleshoot this problem. For example, if the UUCP error code says something like chat script failed, you can view the chat script dialogue between the local and remote hosts at the console.

    If you find that the modem connects but then disconnects after a short time, the problem probably lies with the PPP link parameter negotiation. To debug this type of problem, see ``Troubleshooting PPP negotiation''.

    lines 5,6
    If the UUCP facility successfully connects with the remote host, pppd receives this information along with the tty of the connection.

    line 7
    pppd links the tty of that connection under the PPP driver.

    lines 8,9
    The PPP daemon assigns an ID number (1) to the outgoing link.

  4. If execution of the pppattach command successfully builds a network interface, test the interface with the ping command:

    ping remote_host_IP_address

    remote_host_IP_address must be the IP address for the remote host that appeared in the network interface entry in the ifconfig display.

    If ping fails, it may fail with an error message. Below is one possible message:

       ping send: Network is unreachable
    This error message indicates that the network address of the remote host is different from that of the local host. Make sure that the network portion of the remote host's IP address is correct. (See ``IP address'' for a discussion of the network portion of the IP address.) For machines on the same network, the network part of the IP addresses for the local host and the remote host should match. If the machines are not on the same network, you need to configure a gateway to route packets between the two networks.

    Another possible message is:

       ping send: No route to host
    If this message appears, verify that there is a route to the remote host in the routing tables.

    If ping hangs with no response, make sure that the IP address used on the command line is correct.

    If ping is successful when using the IP address of the remote host, you may wish to test whether one can reach the remote host using the host names by which it should be reachable. See ``Using ping to test reachability using host names'' for the command, possible error message, and resolutions.

Next topic: Testing remote access
Previous topic: Testing automatic dialup connectivity

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