For hosts with wired and wireless nics, utm does not allow multiple ip addresses to be set. For ipv4, where the unique mac addresses can be used to identify the wired and wireless nics, utm only allows one ipv4. If a laptop is connected to the network using the wired nic, then using the wireless nic, there will be an address collision. The only workaround is to allocate two hosts, one for wired and one for wireless. This is a duplication of effort and also wastes licences. It should be possible to assign as many addresses to a host as there are nics. This bug affects both ipv4 and ipv6, although with the DUID bug, there is no way to uniquely identify multiple nics.
Hi, ISTM the licensing part would discourage many customers from implementing IPv6. Maybe the license counter could not count both IPv4 and IPv6 where the MAC is the same? Barry
The problem with DHCPv6 is that there is no such thing like a MAC address in the standard and protocol. For that reason it's also not possible to do static mappings using a MAC address with DHCPv6.
The problem with DHCPv6 is that there is no such thing like a MAC address in the standard and protocol. For that reason it's also not possible to do static mappings using a MAC address with DHCPv6.
True, there is not a mechanism to use the MAC address, but dhcpv6 has the IAID, which is unique. If utm used the IAID instead of the DUID, it would be possible to use it to set unique addresses for wired and wireless interfaces.
The problem with DHCPv6 is that there is no such thing like a MAC address in the standard and protocol. For that reason it's also not possible to do static mappings using a MAC address with DHCPv6.
True, there is not a mechanism to use the MAC address, but dhcpv6 has the IAID, which is unique. If utm used the IAID instead of the DUID, it would be possible to use it to set unique addresses for wired and wireless interfaces.
