WPP support for IPv6

WPP support for IPv6 includes the following:

• WPP over IPv6; for example, a BNG and portal can exchange WPP messages over IPv6

• User client access portal over IPv6

• Dual-stack IPoE sessions. This means that the user client can be a dual-stack device, such as:

  • IPv4 only

  • IPv6 only

  • IPv4 and IPv6

  For IPv6, the client can use a DHCPv6 IANA or SLAAC address to access the portal.

  Only the first address assignment of an IPoE session triggers WPP authentication. Subsequent address assignments in the same session do not require authentication. If IPoE reauthentication is enabled, when the system requires reauthentication of the client, the system restores the SLA profile or subscriber profile session to the initial WPP profile. This causes the client to be redirected to the portal again to authenticate.

• WPP portal redundancy (portal-group) for IPv6 portal and dual-stack IPoE session

• WPP LUDB support for dual-stack IPoE sessions

• WPP MCS redundancy for dual-stack IPoE sessions

• Triggered dual-stack IPoE sessions for Layer 3 access

  For these types of sessions, by default, each address of same client creates a separate IPoE session unless the ipoe-session-policy circuit-id-from-auth command is enabled and the RADIUS server returns a circuit ID during WPP-triggered RADIUS authentication.