Related Documentation
- J, M, MX, T Series
- PPPoE Overview
- M, MX Series
- Understanding PPPoE Service Name Tables
- Configuring PPPoE Service Name Tables
- Assigning an ACI/ARI Pair to a Service Name and Configuring the Action Taken When the Client Request Includes ACI/ARI Information
- Assigning a Dynamic Profile and Routing Instance to a Service Name or ACI/ARI Pair for Dynamic PPPoE Interface Creation
- Limiting the Number of Active PPPoE Sessions Established with a Specified Service Name
- Additional Information
- Ethernet Interfaces
Configuring the Action Taken When the Client Request Includes an Empty Service Name Tag
You can configure the action taken by the PPPoE underlying interface when it receives a PADI packet that includes a zero-length (empty) service name tag. The empty service is present by default in every PPPoE service name table.
To indicate that it can service the client request, the interface returns a PADO packet in response to the PADI packet. By default, the interface immediately responds to the request; this is the terminate action. Alternatively, you can configure the drop action to ignore (drop) the PADI packet, or the delay action to set a delay between receipt of the PADI packet and transmission of the PADO packet.
(Optional) To configure the action taken for the empty service in response to a PADI packet from a PPPoE client:
- Specify the action.
You can also accomplish the following optional tasks when you configure the empty service:
- Specify the agent circuit identifier (ACI) and agent remote identifier (ARI) information to determines the action taken by the PPPoE underlying interface when it receives a PADI packet with matching ACI/ARI information.
- Specify a dynamic profile and routing instance with which the router instantiates a dynamic PPPoE subscriber interface.
- Limit the number of active PPPoE sessions that the router can establish with the empty service.
Related Documentation
- J, M, MX, T Series
- PPPoE Overview
- M, MX Series
- Understanding PPPoE Service Name Tables
- Configuring PPPoE Service Name Tables
- Assigning an ACI/ARI Pair to a Service Name and Configuring the Action Taken When the Client Request Includes ACI/ARI Information
- Assigning a Dynamic Profile and Routing Instance to a Service Name or ACI/ARI Pair for Dynamic PPPoE Interface Creation
- Limiting the Number of Active PPPoE Sessions Established with a Specified Service Name
- Additional Information
- Ethernet Interfaces
Published: 2013-08-01
Related Documentation
- J, M, MX, T Series
- PPPoE Overview
- M, MX Series
- Understanding PPPoE Service Name Tables
- Configuring PPPoE Service Name Tables
- Assigning an ACI/ARI Pair to a Service Name and Configuring the Action Taken When the Client Request Includes ACI/ARI Information
- Assigning a Dynamic Profile and Routing Instance to a Service Name or ACI/ARI Pair for Dynamic PPPoE Interface Creation
- Limiting the Number of Active PPPoE Sessions Established with a Specified Service Name
- Additional Information
- Ethernet Interfaces
