With dhcpv6_assignall '0' working as advertised it introduces a race condition between ULA and GUA on the same interface since the longest preferred lifetime corroborates to the client's interface where both, GUA and ULA are to be assigned.
Thus with dhcpv6_assignall '0' deployed it is observed that a stateful DHCPv6 client only gets ULA or GUA but not both, despite each serving different address spaces; basically rendering them mutually exclusive.
Is that the intended design or rather an unintended consequence?
It does not seem to make sense that ULA and GUA are becoming mutually exclusive as serving different purposes (address spaces).
With
dhcpv6_assignall '0'working as advertised it introduces a race condition between ULA and GUA on the same interface since the longest preferred lifetime corroborates to the client's interface where both, GUA and ULA are to be assigned.Thus with
dhcpv6_assignall '0'deployed it is observed that a stateful DHCPv6 client only gets ULA or GUA but not both, despite each serving different address spaces; basically rendering them mutually exclusive.Is that the intended design or rather an unintended consequence?
It does not seem to make sense that ULA and GUA are becoming mutually exclusive as serving different purposes (address spaces).