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
I played a little with multicast-dns, but when i start/stop my bonjour service (mDnsresponder.exe) , it seems that no service/devices can be discovered (until i reboot my computer / shutdown bonjour).
Yet, reusseaddr is properly set on the socket. Is there any reason you could think of, for Apple bonjour Service to mess with multicast-dns ?
I've seend that mdnsreponder bind 5353 UDP on all network interfaces i'v got (and not on 0.0.0.0) -when you bind only 0.0.0.0, maybe some kind of priority rule ?
The text was updated successfully, but these errors were encountered:
na, i tried that, same result. What's stranger is that even after i close mdnsresponder.exe, it take time (3min+) before multicast-dns to start re-receiving answers
I played a little with multicast-dns, but when i start/stop my bonjour service (mDnsresponder.exe) , it seems that no service/devices can be discovered (until i reboot my computer / shutdown bonjour).
Yet, reusseaddr is properly set on the socket. Is there any reason you could think of, for Apple bonjour Service to mess with multicast-dns ?
I've seend that mdnsreponder bind 5353 UDP on all network interfaces i'v got (and not on 0.0.0.0) -when you bind only 0.0.0.0, maybe some kind of priority rule ?
The text was updated successfully, but these errors were encountered: