chrismurphy
24th March 2012, 10:01 PM
The simple question is, can anyone think of why mDNS would only work in one direction? The is, computer 1 resolves computer2.local fine. But computer 2 will not resolve computer1.local. Neither are running firewalls.
Detail version:
Happens with fully updated F17TC2, but regression indicates it behaves the same on F16 (as installed or updated).
I do not get bidirection resolution of mDNS hosts. For example two computers:
apple.local
f17s.local
From computer "apple" this command succeeds in connecting:
ssh chris@f17s.local
From computer "f17s" this command produces an error "ssh: Could not resolve hostname apple.local: Name or service not known"
ssh chris@apple.local
But if I use the actual IP, it works. On a 3rd computer running Mac OS, it resolves apple.local. So this seems to be either a missing setting or bug in F16/F17. Before I file a bug and post on the devel list, I thought I'd ask here first.
---------- Post added at 02:24 PM ---------- Previous post was at 01:44 PM ----------
I'm thinking this could be two different problems between F16 and F17. Now with F17 we have firewalld and I have no Firewall application to configure it. So I'm actually not sure this is a firewall problem with F17.
---------- Post added at 03:01 PM ---------- Previous post was at 02:24 PM ----------
Yeah, so missing now is the Firewall application. There isn't a GUI means of changing firewalld's defaults. And like iptables, it's blocking Avahi by default.
Detail version:
Happens with fully updated F17TC2, but regression indicates it behaves the same on F16 (as installed or updated).
I do not get bidirection resolution of mDNS hosts. For example two computers:
apple.local
f17s.local
From computer "apple" this command succeeds in connecting:
ssh chris@f17s.local
From computer "f17s" this command produces an error "ssh: Could not resolve hostname apple.local: Name or service not known"
ssh chris@apple.local
But if I use the actual IP, it works. On a 3rd computer running Mac OS, it resolves apple.local. So this seems to be either a missing setting or bug in F16/F17. Before I file a bug and post on the devel list, I thought I'd ask here first.
---------- Post added at 02:24 PM ---------- Previous post was at 01:44 PM ----------
I'm thinking this could be two different problems between F16 and F17. Now with F17 we have firewalld and I have no Firewall application to configure it. So I'm actually not sure this is a firewall problem with F17.
---------- Post added at 03:01 PM ---------- Previous post was at 02:24 PM ----------
Yeah, so missing now is the Firewall application. There isn't a GUI means of changing firewalld's defaults. And like iptables, it's blocking Avahi by default.