DHCPv6 Relay allows CPE to obtain IPv6 Address or IPv6 delegated prefix from DHCPv6 Server.
This sequence diagram explains the flow of messages
CN/DN acting as DHCPv6 Relay inserts DHCPv6 options 37 (Remote Identifier) and 38 (Subscriber identifier) in all Relay-Forward messages. These options can be used by DHCPv6 server to allocate the correct IPv6 address / Prefix
DHCPv6 Relay should be selected in the IPv6 Layer CPE Addressing method at network level.
DHCPv6 Server address should be configured.
The ethernet port where CPE is connected.
By default, CN/DN ‘s MAC address is inserted in Option 37 Remote identifier. Additionally, any string can be configured. This string will be appended, delimited by “:” character.
Client ID of DHCPv6 request will be inserted as a subscriber ID. All DUI types i.e. DUID_LLT, DUID_EN, DUID_LL(RFC 3315) and DUI_UUID (RFC 6355) are supported.
For DUID_LL and DUID_LLT , MAC address portion will be copied as subscriber ID.
DUID_EN: Data starting from Enterprise id will be copied as subscriber id.
DUI_UUID: UUID data will be copied as subscriber id.
Additionally, any string can be configured. This string will be appended, delimited by “:” character.
By default, controller allocates a /64 prefix for the CN. CN’s IPv6 address is formed using this prefix. Source IPv6 address for the Relay-forward message will be this address. A different prefix can be configured in this field.
This feature is introduced in Release 1.1