Panic when request interfaces are nil about dnssd HOT 6 CLOSED

So my debugger is showing the call ipv4.ReadFrom in mdns.go is calling through to payload_nocmsg.go in golang.net/x.net (note the this is the No CMsg variant).

From looking at the go:build statements, it looks like this is because the NoCMsg variant is always used on non-Unix platforms IE Windows like this issue is exhibiting on.

It looks like control messages are not implemented on Windows according to his bug: golang/go#20153

from dnssd.

I've submitted an MR which takes the first proposed approach above. This appears to resolve the issue in my testing but I'd be interested to understand the route of this issue further.

from dnssd.

cm is the control message and should include the network interface – see mdns.go.

We should investigate why this is nil.

from dnssd.

I can confirm, solution in PR fix work on Windows

from dnssd.

Thanks, @AlexxIT, @brutella would you consider merging the pull-request to work around the issue? It seems like it's sensible defensive programming, even though I agree it would be nice to have the underlying issue resolved.

from dnssd.

I have the same problem on Windows 10 Pro.

mdns.go It will get an error message in my system not implemented on windows/amd64 @rblenkinsopp @brutella

from dnssd.