JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
System Administration Guide: Network Services     Oracle Solaris 10 8/11 Information Library
search filter icon
search icon

Document Information


Part I Network Services Topics

1.  Network Service (Overview)

2.  Managing Web Cache Servers

3.  Time-Related Services

Part II Accessing Network File Systems Topics

4.  Managing Network File Systems (Overview)

5.  Network File System Administration (Tasks)

6.  Accessing Network File Systems (Reference)

Part III SLP Topics

7.  SLP (Overview)

8.  Planning and Enabling SLP (Tasks)

9.  Administering SLP (Tasks)

10.  Incorporating Legacy Services

11.  SLP (Reference)

Part IV Mail Services Topics

12.  Mail Services (Overview)

13.  Mail Services (Tasks)

14.  Mail Services (Reference)

Part V Serial Networking Topics

15.  Solaris PPP 4.0 (Overview)

16.  Planning for the PPP Link (Tasks)

17.  Setting Up a Dial-up PPP Link (Tasks)

18.  Setting Up a Leased-Line PPP Link (Tasks)

Setting Up a Leased Line (Task Map)

Configuring Synchronous Devices on the Leased Line

Prerequisites for Synchronous Devices Setup

How to Configure Synchronous Devices

Configuring a Machine on the Leased Line

Prerequisites for Configuring the Local Machine on a Leased Line

How to Configure a Machine on a Leased Line

19.  Setting Up PPP Authentication (Tasks)

20.  Setting Up a PPPoE Tunnel (Tasks)

21.  Fixing Common PPP Problems (Tasks)

22.  Solaris PPP 4.0 (Reference)

23.  Migrating From Asynchronous Solaris PPP to Solaris PPP 4.0 (Tasks)

24.  UUCP (Overview)

25.  Administering UUCP (Tasks)

26.  UUCP (Reference)

Part VI Working With Remote Systems Topics

27.  Working With Remote Systems (Overview)

28.  Administering the FTP Server (Tasks)

29.  Accessing Remote Systems (Tasks)

Part VII Monitoring Network Services Topics

30.  Monitoring Network Performance (Tasks)



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:

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.

  2. Add an entry for the remote peer in the router's /etc/hosts file.
    # cat /etc/hosts
    # Internet host table
    #       localhost  local2-peer        loghost  local1-net 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'

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

    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.
    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.
    Gives the device name of synchronous interface.
    Establishes synchronous encoding for the link.
    Establishes that the local system does not need to demand authentication from the peer. However, the peer could still demand authentication.
    Defines the IP addresses of the local peer and the remote peer, separated by a colon.
    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.
    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
    if [ -f /var/run/ ] &&
       /usr/bin/kill -s 0 `/bin/cat /var/run/`
            /usr/bin/pppd call farISP

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

    Code Sample
    if [ -f /var/run/ ] && /usr/bin/kill -s 0 `/bin/cat /var/run/`
    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 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

    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.