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.
Thanks for raising this question. First of all the UTM is using ISC as DHCP server, and currently their implementation is to use only the duid for static mapping. So currently this is not supported. We will do further investigations.
Regards.
Currently it doesn't seem directly supported, hopefully they'll add that. *Maybe* it's possible to achieve this by some smart server configuration, we're trying a few things.
No this is not necessarily to consider a bug. There have been plenty discussions throughout the IPv6 community regarding that issue.
Just because the Microsoft DHCPv6 server implements it, does not mean it's a bug if it's missing somewhere else. Some other OSes allow to change the DUID per interface for example so they don't have this issue.
Thanks for raising this question. First of all the UTM is using ISC as DHCP server, and currently their implementation is to use only the duid for static mapping. So currently this is not supported. We will do further investigations.
Regards.
No this is not necessarily to consider a bug. There have been plenty discussions throughout the IPv6 community regarding that issue.
Just because the Microsoft DHCPv6 server implements it, does not mean it's a bug if it's missing somewhere else. Some other OSes allow to change the DUID per interface for example so they don't have this issue.
When I reported this in the other part of the forum, another user reported that the issue also affects mac os. I don't have any Linux systems with wired and wireless nics so I don't have any way to check that.
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?
