Session
When Discovery is successfully completed, both the host and the selected remote
AC have the information they need to build their point-to-point connection over
Ethernet.
The only parameter that you can configure is the number of PPPoE sessions.
NOTE:
The router supports dynamic PPPoE interfaces. Also, profiles support PPPoE
interfaces. See “Configuring Dynamic Interfaces” on page 515 and “Configuring
Dynamic Interfaces Using Bulk Configuration” on page 623, for more information.
PPPoE Service Name Tables
PPPoE clients use service name tags, as defined in RFC 2516, to request that an AC
support certain services. The client includes a custom service name tag in the PADI
packet that it broadcasts to remote ACs. Alternatively, the client can include an empty
service name tag of zero length to indicate that any service is acceptable, or an
unknown service name tag to represent a service not yet configured in the PPPoE
service name table.
On receipt of a PADI packet that it can serve, the AC responds with a PADO packet.
The PADO packet contains a service name tag that is identical to the one in the PADI,
as well as one or more additional service name tags indicating other services that
the AC offers.
A PPPoE service name table consists of one or more service name entries and their
associated action. The PPPoE service name table can include three types of service
name tags:
■
Custom service name tag (serviceName)
— A service entry that represents a
specific client service that an AC can support. The length of the custom service
name tag can be up to 31 alphanumeric characters; for example, myQoSClass
or my ISPService. You can optionally associate an action (
drop
or
terminate
)
with a custom service. The default action for a custom service is
terminate
.
■
Empty service name tag (empty-service-name)
— A service entry of zero length
that is used to represent any service. The router either responds with a PADO
packet to all PADI requests containing an empty service name tag, or denies
(drops) all PADI requests based on the action configured for the service.
■
Unknown service name tag (unknown-service-name)
— A service entry that
has not been configured in the PPPoE service name table. When a PPPoE client
includes an unknown service name tag in the PPPoE service name table, the
router responds based on the action (
drop
or
terminate
) associated with the
unknown service name entry.
The default action associated with the unknown service name tag depends on
the PPPoE service name table configuration. If all the services in the table are
configured to
drop
, the default action for the unknown service name tag is
terminate
. If all the services in the table are configured to
terminate
, the default
Overview
■
377
Chapter 12: Configuring Point-to-Point Protocol over Ethernet
Summary of Contents for JUNOSE 11.1.X - LINK LAYER CONFIGURATION 4-7-2010
Page 6: ...vi...
Page 8: ...viii JUNOSe 11 1 x Link Layer Configuration Guide...
Page 26: ...xxvi List of Figures JUNOSe 11 1 x Link Layer Configuration Guide...
Page 34: ...2 Chapters JUNOSe 11 1 x Link Layer Configuration Guide...
Page 230: ...198 Monitoring VLAN and S VLAN Subinterfaces JUNOSe 11 1 x Link Layer Configuration Guide...
Page 258: ...226 Monitoring 802 3ad Link Aggregation JUNOSe 11 1 x Link Layer Configuration Guide...
Page 334: ...302 Troubleshooting JUNOSe 11 1 x Link Layer Configuration Guide...
Page 394: ...362 Monitoring Multiclass MLPPP JUNOSe 11 1 x Link Layer Configuration Guide...
Page 406: ...374 Monitoring POS JUNOSe 11 1 x Link Layer Configuration Guide...
Page 468: ...436 Troubleshooting JUNOSe 11 1 x Link Layer Configuration Guide...
Page 498: ...466 Monitoring Bridged Ethernet JUNOSe 11 1 x Link Layer Configuration Guide...
Page 546: ...514 Monitoring Cisco HDLC JUNOSe 11 1 x Link Layer Configuration Guide...
Page 747: ...Part 2 Index Index on page 717 Index 715...
Page 748: ...716 Index JUNOSe 11 1 x Link Layer Configuration Guide...
Page 774: ...742 Index JUNOSe 11 1 x Link Layer Configuration Guide...