evverx
commented
7 months ago What tools do I need to use to somehow track down or understand the source of this issue?
Could you run Wireshark with the port 5353 filter on redstar.local when another machine tries to resolve that name with avahi-resolve -n redstar.local? It should help to figure out whether mDNS packets with the queries reach that machine at all. If they do and avahi doesn't reply it would make sense to look at the logs to see what avahi registers and where.
Joining mDNS multicast group on interface ...
Registering new address record for ...
Server startup complete. Host name is ...
Leaving mDNS multicast group on interface ...If mDNS packets don't reach redstar.local it's unlikely to be an avahi issue. It could be that the network interfaces weren't reconfigured when the hotspot went down and up again or something like that.
Either way in its current form it's hard to tell what's going on. It would be great if you could run avahi in debug mode by appending --debug to the command line on at least two machines and run Wireshark on those machines when one of them tries to resolve the host name of the other machine and paste all that here.
lliendo
Hi there,
I'm opening this issue because I honestly don't know if I'm facing a bug, an inherently mis-configuration, bad luck or some cosmic rays ruining my setup. Here's the thing. Yesterday late at night I configured avahi (along with nsswitch) in Ubuntu and two other FreeBSD boxes. Everything was working just fine, when running
avahi-browse --all --resolve --ignore-local --terminateI was able to see all my configured hosts from all machines, even from Termux in a mobile phone.I'm primarily interested in just getting a list of available hosts in my local network, so I was actually satisfied with things working. I went to bed happily. Today after finishing my day I grabbed these hosts and for apparently no reason I simply can't see those hosts anymore. While yesterday a
ping redstar.localworked just fine now the host is unknown. Nothing. Nada. When runningavahi-browse --all --resolve --ignore-local --terminateall that I see is this (from any of my hosts in my network):Maybe is worth mentioning that I'm using my mobile phone as a hotspot for my local network and yesterday went out of battery (late at night), but I can't possibly see this as the source of the problem. I do not see any errors anywhere, simply hosts are no longer discovered at all. My
nsswitch.confconfig is as follows:On my Linux machine:
hosts: files mdns4_minimal [NOTFOUND=return] dns(Running avahi-daemon v0.7). On my FreeBSD machines (2 of them):hosts: files mdns4_minimal mdns4 [NOTFOUND=return] dns(Running avahi-daemon 0.8)Does anyone have a clue as to why a working setup would randomly stop working? After realizing avahi stopped resolving hostnames, I played a bit with the configuration from
/etc/avahi/avahi-daemon.confbut none of the changes that I made fixed the problem. What tools do I need to use to somehow track down or understand the source of this issue? Any help really appreciated. I haven't yet rebooted all machines (just the Linux, but the problem persists), so maybe I can still run something to see why this happens, any ideas are welcome.Thanks, Lucas.