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.
I have ipv4 and ipv6 addresses set up for most of my computers, all of the ones that are not servers. It's a given that dual stack networking is going to be the norm for years. For laptops which have wired and wireless nics, I have both addresses set up. As I pointed out in the other thread, this is problematic for ipv6 due to the DUID issue. Irrespective of whether licensing is based on hosts or ip addresses, having to configure multiple "hosts" due to limitations of configuration is unfortunate. In my opinion, it's preferable for all of the addresses pertaining to one host to be configured and managed as a group. A separate case would be for virtual machines, which I consider separate, even if they are using one physical nic.
I have ipv4 and ipv6 addresses set up for most of my computers, all of the ones that are not servers. It's a given that dual stack networking is going to be the norm for years. For laptops which have wired and wireless nics, I have both addresses set up. As I pointed out in the other thread, this is problematic for ipv6 due to the DUID issue. Irrespective of whether licensing is based on hosts or ip addresses, having to configure multiple "hosts" due to limitations of configuration is unfortunate. In my opinion, it's preferable for all of the addresses pertaining to one host to be configured and managed as a group. A separate case would be for virtual machines, which I consider separate, even if they are using one physical nic.
