Part I Network Services Topics
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)
8. Planning and Enabling SLP (Tasks)
10. Incorporating Legacy Services
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
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)
25. Administering UUCP (Tasks)
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
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.
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
Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.
# 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.
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.
|
# 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.
|
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.
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.