The system doesn't find others on the LAN

General system Newbie
1

Hi, I installed Ganymede version on my PC without problems, but at the end the system don’t find any other device on the LAN. It is therefore necessary to use the IP address to access to them. So I ask for an help.

I compared the system files with another PC that works correctly, and they seem to be the same. Avahi, wsdd, and nss-mdns are installed on both, and avahi-daemon and wsdd are running, but the command “avahi-browse --all --resolve --terminate” on the PC in question terminates without finding anything, while on the other it works correctly.
I also checked that firewalld is configured correctly.

However, when querying the status with the command systemctl status avahi-daemon, it reports:

Active: active (running) since Thu 2026-02-05 21:42:35 CET; 57min ago
 Invocation: 50a5a636410a4c4795b665e2e425d6fa
TriggeredBy: ● avahi-daemon.socket
   Main PID: 5747 (avahi-daemon)
     Status: "avahi-daemon 0.9-rc3 starting up."
      Tasks: 2 (limit: 18836)
     Memory: 1M (peak: 2.5M)
        CPU: 281ms
     CGroup: /system.slice/avahi-daemon.service
             ├─5747 "avahi-daemon: running [ThinkpadtT480s.local]"
             └─5754 "avahi-daemon: chroot helper"

feb 05 21:42:35 ThinkpadtT480s avahi-daemon[5747]: Registering new address record for 127.0.0.1 on lo.IPv4.
feb 05 21:42:35 ThinkpadtT480s avahi-daemon[5747]: Failed to parse address 'fe80::22b0:1ff:feeb:e26c%enp0s31f6', ignoring.
feb 05 21:42:35 ThinkpadtT480s avahi-daemon[5747]: Failed to parse address 'fe80::22b0:1ff:feeb:e26c%wlan0', ignoring.
feb 05 21:42:36 ThinkpadtT480s avahi-daemon[5747]: Server startup complete. Host name is ThinkpadtT480s.local. Local service cookie is 2251017878.
feb 05 21:42:39 ThinkpadtT480s avahi-daemon[5747]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.171.
feb 05 21:42:39 ThinkpadtT480s avahi-daemon[5747]: New relevant interface wlan0.IPv4 for mDNS.
feb 05 21:42:39 ThinkpadtT480s avahi-daemon[5747]: Registering new address record for 192.168.1.171 on wlan0.IPv4.
feb 05 21:42:40 ThinkpadtT480s avahi-daemon[5747]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::588c:b9ed:73a9:9042.
feb 05 21:42:40 ThinkpadtT480s avahi-daemon[5747]: New relevant interface wlan0.IPv6 for mDNS.

I don’t know why, but this could be the cause of the issue, If I well understood, It ignores the eth and wlan interfaces, so It will never find anything…

How can I fix it? Thanks

2

The output you shared there, from what I can tell, looks normal. It’s successfully registering both IPv4 and IPv6 (multicast) groups on the wlan0 interface.

Are the other systems on your network, where discovery is working, connected only via WiFi too?

Do you possibly have wireless client isolation active on your WiFi?

3

Actually if you’re able to connect to those systems via IP, then it’s likely not wireless client isolation :thinking:

4

At this moment I have a PC connetted via wifi and NAS via eth.

No wireless client isolation active on WiFi.

5

If you don’t mind a simple fix, and the NAS IP address is never going to change, you can simply add a record to your hosts file for the NAS:

(change the IP and hostname accordingly)

/etc/hosts

192.168.1.10   mynas

If you’re needing more dynamic local name resolution though (accessing other PC’s on changing IP addresses), then this option would be less appropriate.

6

I agree, but I prefer to completely solve the issue because the other PC works without those problems.

7

Have you opened the mdns service on your firewall? I found this was necessary for printer discovery, which is probably the same issue.

image
image870×600 56 KB

Or via command line (change home if necessary, to your interface’s active zone):

sudo firewall-cmd --zone=home --add-port 5353/udp --permanent
8

Yes, the firewall was already configured like this during installation. I had already checked.

9

And to clarify, is this working from other systems on your network?

If not, might the NAS not be registering the mdns service?

10

As I said, the other PCs on the network address all the devices present. The problem only affects the latest system installed.

11

You were right…I checked firewalld again, and unlike the first time I did it, mdsn was NOT flagged on the public zone. Now everything works. Thank you very much.