-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
no response from avahi-daemon #81
Comments
If you were trying 0.15, it was broken. Please try 0.15.1 and see if that helps. |
hmmm i was running into issues with both 0.15 and the 0.14.x release. i'll give the 0.15.1 a try if it's in AUR and give box a reboot to see if that helps. |
I don't want to replicate the same issue, but this is exactly what I have stumbled upon. Ubuntu 20.04.3.
I have tried 0.15.1, compiled from source - same behavior so far. Using getent host whatever.local give no resolution of any .local host - while it does for normal dns names. To add to this issue - I have tried to catch some udp 5353 packets on this machine and it seems that there are no single packet going out to the multicast address during query. Avahi subsystem seem to work, because queried from MacOS 11.6 using Discovery tool I can browse services and I see a lot of 5353 udp traffic, as an example: |
yeah i still experiencing the same issues with my arch linux box. i have three macos virtual machines using qemu+kvm and all three of the virtual machines are able to discover other hosts on the network using the version of avahi i have installed is.
|
hello, i'm running arch linux with the bellow versions,
for debugging the avahi service on this arch linux box i'm using ping and starting the
avahi-daemon
in a foreground process.yields
i then try to ping archmbp.local using the below command,
in the foreground of the avahi daemon process the below is printed to STDOUT
and in the separate terminal process with the ping cmd it eventually times out i believe, and returns,
running,
strace ping archmbp.local
i'm obviously doing something wrong here, just not sure what it is.
i do have bridge networking setup on this box, which probably makes a difference.
The text was updated successfully, but these errors were encountered: