Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Dual Stack for PPPoE Access Networks Using DHCP

Configuring a DHCPv6 Local Server for DHCPv6 over PPPoE

To layer DHCPv6 above the PPPoE IPv6 family (inet6), create a DHCPv6 local server and associate DHCPv6 with the PPPoE interfaces by adding the PPPoE interfaces to the DHCPv6 local server configuration. Specify static and dynamic PPPoE interfaces as follows:

  • Dynamic—Use the pp0.0 (PPPoE) logical interface as a wildcard to indicate that a DHCPv6 binding can be made on top of a PPPoE interface.

  • Static—Use unit numbers to explicitly specify static interfaces; for example, pp0.2000.

To configure a DHCPv6 local server:

  1. Access the DHCPv6 local server configuration.
  2. Create a group for dynamic PPPoE interfaces and assign a name.

    The group feature groups a set of interfaces and then applies a common DHCP configuration to the named interface group.

  3. For dynamic PPPoE logical interfaces, add an interface.
  4. For static PPPoE, add a range of interfaces.

See Also

Configuring a PPPoE Dynamic Profile for Use with DHCP Addressing in a Dual-Stack Network

Configure a dynamic profile for IPv4 and IPv6 subscribers that access the network. The dynamic profile defines the attributes of the dynamic PPPoE logical subscriber interface.

To configure a PPPoE dynamic profile for both IPv4 and IPv6 subscribers:

  1. Create and name the dynamic profile.
  2. If you are using routing instances, add a routing instance to the profile, and add an interface to the routing instance.

    • Specify the $junos-routing-instance variable for the routing instance. The routing instance variable is dynamically replaced with the routing instance the accessing subscriber uses when connecting to the BNG.

    • Specify the $junos-interface-name variable for the interface. The interface variable is dynamically replaced with the interface that the accessing subscriber uses when connecting to the BNG.

  3. Add a PPPoE logical interface (pp0) to the profile, and specify $junos-interface-unit as the predefined variable to represent the logical unit number for the interface. The variable is dynamically replaced with the actual unit number supplied by the network when the subscriber logs in.
  4. Configure the IPv4 family for the pp0 interface as follows:

    • If you are not using routing instances, assign an unnumbered address. The unnumbered address enables the local address to be derived from the specified interface and allows IP processing on the interface without an explicit IP address assigned to the interface.

      For example:

    • If you are using routing instances, assign the predefined variable $junos-loopback-interface.

      For example:

  5. Configure the IPv6 family for the pp0 interface as follows:

    • If you are not using routing instances, assign an unnumbered address that specifies the loopback interface. The unnumbered address enables the local address to be derived from the loopback interface and allows IP processing on the interface without an explicit IP address assigned to the interface.

      For example:

    • If you are using routing instances, assign the predefined variable $junos-loopback-interface.

      For example:

  6. Specify $junos-underlying-interface as the predefined variable to represent the name of the underlying Ethernet interface on which the router creates the dynamic PPPoE logical interface. The variable is dynamically replaced with the actual name of the underlying interface.
  7. Define the router to act as a PPPoE server when a PPPoE logical interface is dynamically created.
  8. (Optional) Configure the PPP authentication protocol for the pp0 interface. Specify either chap or pap (or both).
  9. (Optional) Enable keepalives and set an interval for keepalives. We recommend an interval of 30 seconds. For example:

See Also

Related Documentation