Understanding Pppoe Service Name Tables; Interaction Among Pppoe Clients And Routers During The Discovery Stage; Components Of Pppoe Service Name Tables; Benefits Of Configuring Pppoe Service Name Tables - Juniper JUNOS 10.1 - CONFIGURATION GUIDE 1-2010 Configuration Manual

it responds to the challenge. If you do not include the
always challenges its peer.
For more information about CHAP, see "Configuring the PPP Challenge Handshake
Authentication Protocol" on page 124.

Understanding PPPoE Service Name Tables

On an M120 router or M320 router acting as a remote access concentrator (AC), also
referred to as a PPPoE server, you can configure up to 16 PPPoE service name tables
and assign the service name tables to underlying PPPoE interfaces. A PPPoE service
name table defines the set of services, also referred to as service name tags, that the
router can provide to a PPPoE client.

Interaction Among PPPoE Clients and Routers During the Discovery Stage

In networks with mesh topologies, PPPoE clients are often connected to multiple
PPPoE servers (remote ACs). During the PPPoE discovery stage, a PPPoE client
identifies the Ethernet MAC address of the remote AC that can service its request,
and establishes a unique PPPoE session identifier for a connection to that AC.
The following steps describe, at a high level, how the PPPoE client and the remote
AC (router) use the PPPoE service name table to interact during the PPPoE discovery
stage:
1.
2.
Interaction Among PPPoE Clients and Routers During the Discovery
Stage on page 827
Components of PPPoE Service Name Tables on page 828
Benefits of Configuring PPPoE Service Name Tables on page 829
The PPPoE client broadcasts a PPPoE Active Discovery Initiation (PADI) control
packet to all remote ACs in the network to request that an AC support certain
services.
The PADI packet must contain either, but not both, of the following:
One and only one nonzero-length service name tag that represents a specific
client service
One and only one empty (zero-length) service name tag that represents an
unspecified service
One or more remote ACs respond to the PADI packet by sending a PPPoE Active
Discovery Offer (PADO) packet to the client, indicating that the AC can service
the client request.
To determine whether it can service a particular client request, the router matches
the service name tag received in the PADI packet against the service name tags
configured in its service name table. If a matching service name tag is found in
the PPPoE service name table, the router sends the client a PADO packet that
includes the name of the AC from which it was sent. If no matching service name
tag is found in the PPPoE service name table, the router drops the PADI request
and does not send a PADO response to the client.
Chapter 57: Configuring Point-to-Point Protocol over Ethernet
passive
Understanding PPPoE Service Name Tables
statement, the interface
827