You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I register a service and zeroconf is about to reply to queries it will try to send a response to all available network interfaces, however this doesn't seem to work correctly on Windows.
The message is sent multiple times to the loopback interface and not to any of the external interfaces.
I can therefore discover my service correctly on the local machine (using the dns-sd command line tool), but other machines cannot see the service.
If i look in Wireshark I can see that the incoming query is on my network interface but the replies are only ever sent to the loopback interface.
Is this a known problem? Any work-arounds or solutions?
The text was updated successfully, but these errors were encountered:
I will try the patches shortly, in the meantime I experimented a bit by setting the multicast interface in the joinUdp4Multicast() function in connection.go.
It seemed to do the trick in this specific case.
Example (added just before the return pkConn, nil:
When I register a service and zeroconf is about to reply to queries it will try to send a response to all available network interfaces, however this doesn't seem to work correctly on Windows.
The message is sent multiple times to the loopback interface and not to any of the external interfaces.
I can therefore discover my service correctly on the local machine (using the dns-sd command line tool), but other machines cannot see the service.
If i look in Wireshark I can see that the incoming query is on my network interface but the replies are only ever sent to the loopback interface.
Is this a known problem? Any work-arounds or solutions?
The text was updated successfully, but these errors were encountered: