DHCPv6 uses the DUID to set a static ipv6 address. This is a bug. On Windows 7, hosts with wired and wireless nics (such as laptop computers), the DHCPv6 Unique ID (DUID) is not unique. This means there is no way to uniquely set static ipv6 addresses for both nics. Apparently this also affects MacOs hosts. UTM should use the DHCPv6 IAID instead of the DUID, because it is a unique id for wired and wireless nics.
A workaround for your laptops could be to use a different subnet for wi-fi. The DHCP server then can differentiate the client NICs by DUID+Subnet until DUID+IAID support has been introduced.
A workaround for your laptops could be to use a different subnet for wi-fi. The DHCP server then can differentiate the client NICs by DUID+Subnet until DUID+IAID support has been introduced.
Understand a fix for this didn't get into 9.2. Is it on the list for the next release?
A workaround for your laptops could be to use a different subnet for wi-fi. The DHCP server then can differentiate the client NICs by DUID+Subnet until DUID+IAID support has been introduced.
Understand a fix for this didn't get into 9.2. Is it on the list for the next release?
