JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
System Administration Guide: Network Services     Oracle Solaris 11 Express 11/10
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)

Solaris PPP 4.0 Basics

Solaris PPP 4.0 Compatibility

Which Version of Solaris PPP to Use

Why Use Solaris PPP 4.0?

Solaris PPP 4.0 Upgrade Path

Where to Go for More Information About PPP

Professional Reference Books About PPP

Web Sites About PPP

Requests for Comments (RFCs) About PPP

Man Pages About PPP

PPP Configurations and Terminology

Dial-up PPP Overview

Parts of the Dial-up PPP Link

Using ISDN Terminal Adapters With a Dial-out Machine

What Happens During Dial-up Communications

Leased-Line PPP Overview

Comparison of Dial-up and Leased-Line Links

Parts of a Leased-Line PPP Link

What Happens During Leased-Line Communications

PPP Authentication

Authenticators and Authenticatees

PPP Authentication Protocols

Why Use PPP Authentication?

Support for DSL Users Through PPPoE

PPPoE Overview

Parts of a PPPoE Configuration

PPPoE Consumers

PPPoE at a Telephone Company

PPPoE at a Service Provider

Security on a PPPoE Tunnel

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)

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)



PPP Configurations and Terminology

This section introduces PPP configurations. The section also defines terms that are used in this guide.

Solaris PPP 4.0 supports a number of configurations.

Figure 15-1 Parts of the PPP Link

The diagram shows the parts of a basic PPP link, which is further described in the following context.

The previous figure shows a basic PPP link. The link has the following parts:

Dial-up PPP Overview

The most commonly used PPP configuration is the dial-up link. In a dial-up link, the local peer dials up the remote peer to establish the connection and run PPP. In the dial-up process, the local peer calls the remote peer's telephone number to initiate the link.

A common dial-up scenario includes a home computer that calls a peer at an ISP, configured to receive incoming calls. Another scenario is a corporate site where a local machine transmits data over a PPP link to a peer in another building.

In this guide, the local peer that initiates the dial-up connection is referred to as the dial-out machine. The peer that receives the incoming call is referred to as the dial-in server. This machine is actually the target peer of the dial-out machine and might or might not be a true server.

PPP is not a client-server protocol. Some PPP documents use the terms “client” and “server” to refer to telephone call establishment. A dial-in server is not a true server like a file server or name server. Dial-in server is a widely used PPP term because dial-in machines often “serve” network accessibility to more than one dial-out machine. Nevertheless, the dial-in server is the target peer of the dial-out machine.

Parts of the Dial-up PPP Link

See the following figure.

Figure 15-2 Basic Analog Dial-up PPP Link

The graphic shows a basic dial-up link between Locations 1 and 2, which is described in the following context.

The configuration for Location 1, the dial-out side of the link, is composed of the following elements:

The configuration for Location 2, the dial-in side of the link, is composed of the following elements:

Using ISDN Terminal Adapters With a Dial-out Machine

External ISDN TAs have faster speeds than modems, but you configure TAs in basically the same way. The major difference in configuring an ISDN TA is in the chat script, which requires commands specific to the TA's manufacturer. Refer to Chat Script for External ISDN TA for information about chat scripts for ISDN TAs.

What Happens During Dial-up Communications

PPP configuration files on both the dial-out and dial-in peers contain instructions for setting up the link. The following process occurs as the dial-up link is initiated.

  1. User or process on the dial-out machine runs the pppd command to start the link.

  2. Dial-out machine reads its PPP configuration files. The dial-out machine then sends instructions over the serial line to its modem, including the phone number of the dial-in server.

  3. Modem dials the phone number to establish a telephone connection with the modem on the dial-in server.

    The series of text strings that the dial-out machine sends to the modem and dial-in server are contained in a file called a chat script. If necessary, the dial-out machine sends commands to the dial-in server to invoke PPP on the server.

  4. Modem attached to the dial-in server begins link negotiation with the modem on the dial-out machine.

  5. When modem-to-modem negotiation is completed, the modem on the dial-out machine reports “CONNECT.”

  6. PPP on both peers enters Establish phase, where Link Control Protocol (LCP) negotiates basic link parameters and the use of authentication.

  7. If necessary, the peers authenticate each other.

  8. PPP's Network Control Protocols (NCPs) negotiate the use of network protocols, such as IPv4 or IPv6.

The dial-out machine can then run telnet or a similar command to a host that is reachable through the dial-in server.

Leased-Line PPP Overview

A hardwired, leased-line PPP configuration involves two peers that are connected by a link. This link consists of a switched or an unswitched digital service leased from a provider. Solaris PPP 4.0 works over any full-duplex, point-to-point leased-line medium. Typically, a company rents a hardwired link from a network provider to connect to an ISP or other remote site.

Comparison of Dial-up and Leased-Line Links

Both dial-up and leased-line links involve two peers that are connected by a communications medium. The next table summarizes the differences between the link types.

Leased Line
Dial-up Line
Always connected, unless a system administrator or power failure takes the leased-line down.
Initiated on demand, when a user tries to call a remote peer.
Uses synchronous and asynchronous communications. For asynchronous communications, a long-haul modem is often used.
Uses asynchronous communications.
Rented from a provider.
Uses existing telephone lines.
Requires synchronous units.
Uses less costly modems.
Requires synchronous ports, which are common on most SPARC systems. However, synchronous ports are not common on x86 systems and newer SPARC systems.
Uses standard serial interfaces that are included on most computers.
Parts of a Leased-Line PPP Link

See the following figure.

Figure 15-3 Basic Leased-Line Configuration

The graphic shows the parts of a leased-line-link, which are described in the following context.

The leased-line link contains the following parts:

What Happens During Leased-Line Communications

On most types of leased lines, peers do not actually dial each other. Rather, a company purchases a leased-line service to connect explicitly between two fixed locations. Sometimes the two peers at either end of the leased line are at different physical locations of the same company. Another scenario is a company that sets up a router on a leased line that is connected to an ISP.

Leased lines are less commonly used than dial-up links, though the hardwired links are easier to set up. Hardwired links do not require chat scripts. Authentication is often not used because both peers are known to each other when a line is leased. After the two peers initiate PPP over the link, the link stays active. A leased-line link remains active unless the line fails, or either peer explicitly terminates the link.

A peer on a leased line that runs Solaris PPP 4.0 uses most of the same configuration files that define a dial-up link.

The following process occurs to initiate communication over the leased line:

  1. Each peer machine runs the pppd command as part of the booting process or another administrative script.

  2. The peers read their PPP configuration files.

  3. The peers negotiate communications parameters.

  4. An IP link is established.