Configuring a Machine on the Leased Line

The task in this section explains how to set up a router to function as the local peer on your end of a leased line. The task uses the leased line that was introduced in Example of a Configuration for a Leased-Line Link as an example.

Prerequisites for Configuring the Local Machine on a Leased Line

Before you perform the next procedure, you must have completed the following:

• Set up and configure the synchronous devices for the link, as described in Configuring Synchronous Devices on the Leased Line

• Obtained the root password for the local machine on the leased line

• Set up the local machine to run as a router on the network or networks to use the services of the leased-line provider

How to Configure a Machine on a Leased Line

1. Become superuser on the local machine (router) or assume an equivalent role.

   Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services. To configure a role with the Primary Administrator profile, see Chapter 2, Working With the Solaris Management Console (Tasks), in System Administration Guide: Basic Administration.

2. Add an entry for the remote peer in the router's /etc/hosts file.

   # cat /etc/hosts
   #
   # Internet host table
   #
   127.0.0.1       localhost
   192.168.130.10  local2-peer        loghost
   192.168.130.11  local1-net
   10.0.0.25 farISP

   The example /etc/hosts file is for the local router at the fictitious LocalCorp. Note the IP address and host name for the remote peer farISP at the service provider.

3. Create the file /etc/ppp/peers/peer-name to hold information about the provider's peer.

   For this example leased-line link, you create the file /etc/ppp/peers/farISP.

   # cat /etc/ppp/peers/farISP
   init '/etc/ppp/conf_hsi'
   local
   /dev/hihp1
   sync
   noauth
   192.168.130.10:10.0.0.25
   passive
   persist
   noccp
   nopcomp
   novj
   noaccomp

   The following table explains the options and parameters that are used in /etc/ppp/peers/farISP.

   Option	Definition
   init '/etc/ppp/conf_hsi'	Starts the link. init then configures the HSI interface by using the parameters in the script /etc/ppp/conf_hsi.
   local	Tells the pppd daemon not to change the state of the Data Terminal Ready (DTR) signal. Also tells pppd to ignore the Data Carrier Detect (DCD) input signal.
   /dev/hihp1	Gives the device name of synchronous interface.
   sync	Establishes synchronous encoding for the link.
   noauth	Establishes that the local system does not need to demand authentication from the peer. However, the peer could still demand authentication.
   192.168.130.10:10.0.0.25	Defines the IP addresses of the local peer and the remote peer, separated by a colon.
   passive	Tells the pppd daemon on the local machine to go quiet after issuing maximum number of LCP Configure-Requests and to wait for the peer to start.
   persist	Tells the pppd daemon to try to restart the link after a connection ends.
   noccp, nopcomp, novj, noaccomp	Disables the Compression Control Protocol (CCP), Protocol Field compression, Van Jacobson compression, and address and control field compression, respectively. These forms of compression accelerate transmissions on a dial-up link but could slow down a leased line.

4. Create an initialization script that is called demand, which creates the PPP link as part of the booting process.

   # cat /etc/ppp/demand
   #!/bin/sh
   if [ -f /var/run/ppp-demand.pid ] &&
      /usr/bin/kill -s 0 `/bin/cat /var/run/ppp-demand.pid`
   then
           :
   else
           /usr/bin/pppd call farISP
   fi

   The demand script contains the pppd command for establishing a leased-line link. The following table explains the content of $PPPDIR/demand.

   Code Sample	Explanation
   if [ -f /var/run/ppp-demand.pid ] && /usr/bin/kill -s 0 `/bin/cat /var/run/ppp-demand.pid`	These lines check to see if pppd is running. If pppd is running, it does not need to be started.
   /usr/bin/pppd call farISP	This line launches pppd. pppd reads the options from /etc/ppp/options. The call farISP option on the command line causes it to read /etc/ppp/peers/farISP, also.

   The Solaris PPP 4.0 startup script /etc/rc2.d/S47pppd invokes the demand script as part of the Solaris booting process. The following lines in /etc/rc2.dS47pppd search for the presence of a file that is called $PPPDIR/demand.

       if [ -f $PPPDIR/demand ]; then
                   . $PPPDIR/demand
           fi
           

   If found, $PPPDIR/demand is executed. During the course of executing $PPPDIR/demand, the link is established.

   ---

   Note - To reach machines outside the local network, have users run telnet, ftp, rsh, or similar commands.

   ---

See Also

If you have followed all the procedures in this chapter, you have completed the configuration of the leased-line link. The following list provides references to related information.

• To find troubleshooting information, see Fixing Leased-Line Problems.

• To learn more about the files and options that are used in this chapter, see Using PPP Options in Files and on the Command Line.