Hyper-V network interface interferes with detection

[ctartamella]

I have a virtual ethernet card added on my system from the installation of Docker in Hyper-V. It is a NAT interface so it doesn't really go anywhere. When this interface is enabled, LifxNet is not able to detect lights on my network. As soon as I disable it, detection works perfectly. I'm not sure what other diagnostic info I can provide, so please let me know and I will be happy to help.

[logicallysynced]

LifxNet seems to use the UdpClient in System.Net.Sockets. I'm wondering if this issue is caused by the sockets class targeting the wrong (virtual) NIC on your VM by default?

https://github.com/dotMorten/LifxNet/blob/master/src/LifxNet/LifxClient.cs

https://stackoverflow.com/questions/1096142/broadcasting-udp-message-to-all-the-available-network-cards

[ctartamella]

That was my assumption. I've since gotten rid of Docker via Hyper-V for some other reasons (though this incompatibility played a part) but I can say it was pretty much a default install of Docker for Windows which created the issue. You may need to create a single instance of an image in order to force the creation of the network adapters to replicate this.