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

19.  Setting Up PPP Authentication (Tasks)

20.  Setting Up a PPPoE Tunnel (Tasks)

Major Tasks for Setting Up a PPPoE Tunnel (Task Maps)

Setting Up the PPPoE Client

Prerequisites for Setting Up the PPPoE Client

How to Configure an Interface for a PPPoE Client

How to Define a PPPoE Access Server Peer

Setting Up a PPPoE Access Server

How to Set Up a PPPoE Access Server

How to Modify an Existing /etc/ppp/pppoe File

How to Restrict the Use of an Interface to Particular Clients

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)



Setting Up a PPPoE Access Server

If your company is a service provider, you can offer Internet and other services to clients that reach your site through DSL connections. The procedure involves determining which interfaces on the server to involve in the PPPoE tunnel and defining which services are made available to the users.

How to Set Up a PPPoE Access Server

Use this procedure to define the Ethernet interface to be used for the PPPoE tunnel and to configure the services that the access server offers.

  1. Become an administrator on the access server.

    For more information, see How to Obtain Administrative Rights in Oracle Solaris Administration: Security Services.

  2. Add the name of the Ethernet interfaces that are dedicated to the PPPoE tunnels to the /etc/ppp/pppoe.if file.

    For example, you would use the following /etc/ppp/pppoe.if file for the access server dslserve that is shown in Example of a Configuration for a PPPoE Tunnel.

    # cat /etc/ppp/pppoe.if
  3. Define global services that are provided by the access server in the /etc/ppp/pppoe file.

    The following /etc/ppp/pppoe file lists the services that are provided by access server dslserve, which was shown in Figure 16-5.

    device hme1,hme2
    service internet
        pppd "proxyarp"
    service debugging
        pppd "debug proxyarp"

    In the file example, Internet service is announced for dslserve's Ethernet interfaces hme1 and hme2. Debugging is turned on for PPP links on the Ethernet interfaces.

  4. Set up the PPP configuration files in the same way that you would for a dial-in server.

    For more information, refer to Creating an IP Addressing Scheme for Callers.

  5. Start the pppoed daemon.
    # /etc/init.d/pppd start

    pppd also plumbs the interfaces that are listed in /etc/ppp/pppoe.if.

  6. (Optional) Verify that the interfaces on the server are plumbed for PPPoE.
    # /usr/sbin/sppptun query

    The previous sample shows that interfaces hme1 and hme2 are currently plumbed for PPPoE. You can also use the /usr/sbin/sppptun command to manually plumb interfaces for PPPoE. For instructions, refer to /usr/sbin/sppptun Command.

How to Modify an Existing /etc/ppp/pppoe File

  1. Become an administrator on the access server.

    For more information, see How to Obtain Administrative Rights in Oracle Solaris Administration: Security Services.

  2. Modify /etc/ppp/pppoe, as needed.
  3. Cause the pppoed daemon to recognize the new services.
    # pkill -HUP pppoed

How to Restrict the Use of an Interface to Particular Clients

The next procedure shows how to restrict an interface to a group of PPPoE clients. Before performing this task, you need to obtain the real Ethernet MAC addresses of the clients you are assigning to the interface.

Note - Some systems allow you to change the MAC address on the Ethernet interface. You should view this ability as a convenience factor, not a security measure.

Using the example that is shown in Example of a Configuration for a PPPoE Tunnel, these steps show how to reserve one of dslserve's interfaces, hme1, for clients at MiddleCo.

  1. Configure the access server's interfaces and define the services, as shown in How to Set Up a PPPoE Access Server.
  2. Create entries for clients in the server's /etc/ethers database.

    Here is a sample entry for clients Red, Blue, and Yellow.

    8:0:20:1:40:30 redether
    8:0:20:1:40:10 yellowether
    8:0:20:1:40:25 blueether

    The sample assigns the symbolic names redether, yellowether, and blueether to the Ethernet addresses of clients Red, Yellow, and Blue. The assignment of symbolic names to the MAC addresses is optional.

  3. Restrict services that are provided on a specific interface by defining the following information in the /etc/ppp/pppoe.device file.

    In this file, device is the name of the device to be defined.

    # cat /etc/ppp/pppoe.hme1
    service internet
         pppd "name dslserve-hme1"
         clients redether,yellowether,blueether

    dslserve-hme1 is the access server's name, which is used in matching entries in the pap-secrets file. The clients option restricts the use of interface hme1 to clients with the symbolic Ethernet names redether, yellowether, and blueether.

    If you did not define symbolic names for client's MAC addresses in /etc/ethers, you can use the numeric addresses as arguments for the clients option. Wildcards are allowed.

    For example, you can specify the numeric address clients 8:0:20:*:*:*. By using wildcards, all matching addresses in /etc/ethers are accepted.

  4. Create the /etc/ppp/pap-secrets file for the access server:
    Red dslserve-hme1 redpasswd *
    Blue dslserve-hme1 bluepasswd *
    Yellow dslserve-hme1 yellowpassd *

    The entries are the PAP names and passwords of clients that are allowed to run PPP over dslserve's hme1 interface.

    For more information about PAP authentication, see Configuring PAP Authentication.

See Also

The following list provides references to related information.