Am Dienstag, 5. Dezember 2017, 20:37:01 CET schrieb Richmond:
I got it working! (Well, on two out of three). And...
Fine! BTW, I looked into /etc/sysconfig/SuSEfirewall2.d/ and saw that there is indeed services/avahi. Some years ago, SuSEfirewall2 blocked the incoming answers when using ping but not avahi-resolve: https://lists.opensuse.org/archive/opensuse-security/2008-09/msg00011.html
[...] I switched the computer which listed nothing from wlan0 to eth0. Then it listed itself, but only with ipv4, not ipv6.
Does "systemctl status avahi-daemon" show lines like this? Dec 06 17:59:04 karl avahi-daemon[1124]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::xxxx:xxxx:xxxx:xxxx.
So I disabled ipv6 on both computers, and it all started working.
Strange. Maybe the WiFi router or access point blocks IPv6 multicast groups?
[...] However, adding a third computer wasn't so good. Although it appeared on the avahi-browse -a of the first two, it listed nothing itself.
So, it gets the requests from the other two computers and can respond but cannot send its own requests or receive the related responses. You could use iptraf or wireshark on the first and third computer to check what happens on "avahi-browse -a" issued on the third.
I am not sure why it is at the moment, but that third computer is on 42.2, so needs upgrading anyway. Maybe that will fix it.
Besides the SuSEfirewall2 issue, I've been using mDNS successfully for about ten years. At the moment, I am using it on 42.2 for accessing my NAS and printer via IPv4 and IPv6.
Danke schön. [...]
Gern geschehen! Gruß Jan -- You have not converted a man because you have silenced him. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org