Comment 11 for bug 1874021

Looking at jctl.txt things look normal, the server starts up, gets server startup complete and then adds the appropriate IP for wlan0. Config file looks normal.

Can you please try the following to collect extra debug info

(1) Start a tcpdump and leaving it running - tcpdump --no-promiscuous-mode -w lp1874021.pcap -i wlp1s0 port 5353 and udp
(2) Restart avahi; sudo systemctl restart avahi-daemon
(3) Wait 10 seconds, then try run "avahi-browse -av | tee -a lp1874021-browse.txt"
(4) Wait another 10 seconds
(5) Run: sudo killall -USR1 avahi-daemon # this dumps the avahi cache into the journal
(6) Quit avahi-browse
(7) Quit tcpdump
(8) Please then upload the lp1874021-browse.txt (copied output from avahi-browse), lp1874021.pcap (raw packet capture of mdns packets) and a copy of the output of "journalctl -u avahi-daemon"

As an extra test, after having done the above, you can try put the interface in promiscous mode and see if that fixes the problem. This can make Avahi work on bad network (usually wifi) drivers that do not correctly implement multicast.

(9) sudo tcpdump -w lp1874021-promisc.pcap -i wlp1s0 port 5353 and udp
(10) sudo systemctl restart avahi-daemon
(11) avahi-browse -av
(12) If the service still hasn't shown up, consider also then restarting whatever device is advertising the service you want to connect to. And note if it then appears after doing that.
(13) If you have the option, try to then plug in either or both devices via ethernet instead of WiFi.

If the services do start appearing at some point be sure to note which step you were at when that happened.

Please note that all of these files will contain information about mDNS services on your local network, typically this information is relatively OK to be public since it would be broadcast if you were on a public WiFi network - it can include names, mac addresses, etc. If that is a concern to you in terms of privacy then feel free to consider either attempting to sanitize the data (though that is difficult for the pcap file) or setting the bug to private although we much prefer not to set bugs to private if possible.