Setting Up a PPPoE Tunnel (Tasks)
This chapter contains tasks for setting up the participants on either end of the PPPoE tunnel: the PPPoE client and PPPoE access server. Specific topics include the following:
The tasks use the scenario that was introduced in "Planning for DSL Support Over a PPPoE Tunnel" as an example. For an overview of PPPoE, refer to "Support for DSL Users Through PPPoE".
Major Tasks for Setting Up a PPPoE Tunnel (Task Maps)
The following tables list the major tasks for configuring PPPoE clients and the PPPoE access server. To implement PPPoE at your site, you need to set up only your end of the PPPoE tunnel, either the client side or access-server side.
Table 34-1 Task Map for Setting Up a PPPoE Client
Task | Description | For Instructions |
---|---|---|
1. Configure an interface for PPPoE | Define the Ethernet interface to be used for the PPPoE tunnel. | |
2. Configure information about the PPPoE access server | Define parameters for the access server at the service provider end of the PPPoE tunnel. | |
3. Set up the PPP configuration files | Define the PPP configuration files for the client, if you have not done so already. | |
4. Create the tunnel | Call the access server. |
Table 34-2 Task Map for Setting Up a PPPoE Access Server
Task | Description | For Instructions |
---|---|---|
1. Configure an interface for PPPoE | Define the Ethernet interface to be used for the PPPoE tunnel. | |
2. Configure the services that the access server offers | Describe the services that are provided so that they can be "discovered" by prospective PPPoE clients. | |
3. Set up the PPP configuration files | Define the PPP configuration files for the client, if you have not done so already. | |
4. (Optional) Restrict use of an interface | Use PPPoE options and PAP authentication to restrict use of a particular Ethernet interface to certain clients. | "How to Restrict the Use of an Interface to Particular Clients" |
Setting Up the PPPoE Client
To provide PPP service to client machines over a DSL modem, you must first configure PPPoE on the interface that is connected to the modem or hub. Then you need to change the PPP configuration files to define the access server on the opposite end of the PPPoE.
Prerequisites for Setting Up the PPPoE Client
Before you set up the PPPoE client, you must have done the following:
Installed Solaris 8 Update 6 release or later releases on the client machines to use the PPPoE tunnel
Contacted the service provider for information about its PPPoE access server
Had the telephone company or service provider assemble the devices that are used by the client machines (DSL modem, splitter, and so forth), or assembled them yourself
How to Configure an Interface for a PPPoE Client
Become superuser on the PPPoE client.
Add the name of the Ethernet interface with the DSL connection to the /etc/ppp/pppoe.if file.
For example, you add the following entry to /etc/ppp/pppoe.if for a PPPoE client that uses hme0 as the network interface that is connected to the DSL modem.
hme0
For more information about /etc/ppp/pppoe.if, go to "/etc/ppp/pppoe.if File".
Configure the interface for PPPoE use.
# /etc/init.d/pppd start
- (Optional)
Verify that the interface is now plumbed for PPPoE.
# /usr/sbin/sppptun query hme0:pppoe hme0:pppoed
You can also use the /usr/sbin/sppptun command to manually plumb interfaces PPPoE. For instructions, refer to "/usr/sbin/sppptun Command".
How to Define a PPPoE Access Server Peer
You define the access server in the /etc/ppp/peers/peer-name file. Many of the options that are used for the access server are also used to define the dial-in server in a dial-up scenario. For a detailed explanation of /etc/ppp/peers.peer-name, refer to "/etc/ppp/peers/peer-nameFile".
Become superuser on the PPPoE client.
Define the service provider's PPPoE access server in the /etc/ppp/peers/peer-name file.
For example, the following file, /etc/ppp/peers/dslserve, defines the access server dslserve at FarISP that are introduced in "Example--Configuration for a PPPoE Tunnel".
# cat /etc/ppp/peers/dslserve sppptun plugin pppoe.so connect "/usr/lib/inet/pppoec hme0" noccp noauth user Red password redsecret noipdefault defaultroute
For a definition of the options in this file, go to " /etc/ppp/peers/peer-nameFile for Defining an Access Server Peer".
Modify the other PPP configuration files on the PPPoE client.
Configure /etc/ppp/options as described in the instructions for configuring a dial-out machine in "Configuring the Dial-out Machine".
Create an /etc/ppp/options.sppptun file to describe PPP options for the serial port to which the interface that is plumbed for PPPoE is attached.
You can use any options available for the /etc/ppp/options.ttyname file that is described in "/etc/ppp/options.ttynameConfiguration File". You must name the file /etc/ppp/options.sppptun because sppptun is the specified device name in the pppd configuration.
Ensure that all users can start PPP on the client.
# touch /etc/ppp/options
Test if PPP can run over the DSL line.
# pppd debug updetach call dslserve
dslserve is the name that is given to the access server at the ISP that is shown in "Example--Configuration for a PPPoE Tunnel". The debug updetach option causes debugging information to display in a terminal window.
If PPP is running correctly, the terminal output shows the link coming as it becomes active. If PPP still does not run, try the following command to see if the servers are running correctly:
# /usr/lib/inet/pppoec -i hme0
Where to Go From Here
Task | For Instructions |
---|---|
Configure another PPPoE client | |
Learn more about PPPoE | |
Have users of configured PPPoE clients begin running PPP over the DSL line | Instruct the users to type pppd call ISP-server-name and then run an application or service. |
Troubleshoot PPPoE and PPP problems | |
Configure a PPPoE access server |