I wrote an Ansible playbook to get mDNS working with Untangle

[willquill]

Got a link to that github?

I still can't post links here - not enough posts, but I put the obfuscated URL in my OP that started this thread. Here it is again: (https)://github.com/willquill/untangle-mdns

[jcoffin]

Got a link to that github?

https://github.com/willquill/untangle-mdns

[dashpuppy]

I still can't post links here - not enough posts, but I put the obfuscated URL in my OP that started this thread. Here it is again: https://github.com/willquill/untangle-mdns

Fixed

[willquill]

I just updated the GitHub repo so the Ansible playbook will now install libnss-mdns for hostname resolution as well as avahi-browse for troubleshooting. I also added a troubleshooting section to my README and a note that you must enable UDP 5353 between the subnets as well.

I confirmed that avahi-browse is functional and that libnss-mdns made the required changes after running the playbook, but I'm unable to resolve hostnames. So I think some more work is needed to make this fully functional, but it's on its way there.

For the sake of all of our time and not duplicating things, I'm going to stop updating this thread with every little update. You can visit and subscribe to the issue where this is being discussed for any further updates: https://github.com/willquill/untangle-mdns/issues/1

Once this issue is fully resolved, I'll update this thread if it's still open.

[diothar]

The link to github is in his first post, he just couldn't post it without obfuscating it. But it's there. To close the loop here, I got the ansible to work but was struggling with the reflection amongst the subnets.

I ended up installing avahi on a linux distro and got it working from that box instead of untangle. I do wish untangle would start supporting mdns reflection from the firewall, though.

[diothar]

First, I responded to your GitHub issue. Thank you for creating it there! That will help others find the info more easily.

Here's what I posted to GitHub:



With regard to this - "I'm not able to ping across my subnets still." - that is expected behavior, as my playbook only enables mDNS on the various interfaces. It does not create any firewall rules or allow any specific TCP/UDP ports or ICMP traffic. You should be able to get ping working across the subnets with a firewall rule or a filter rule in Config > Network > Filter Rules that allows the ICMP protocol between subnets.

Ping uses the ICMP protocol and operates at layer 3, so it wouldn't have anything to do with VLANs, specifically - it only cares about subnets, like allowing ICMP from 192.168.10.0/24 to 192.168.69.0/24. There's no way to allow ICMP from "VLAN 10 to VLAN 69" as VLANs operate at layer 2 via tagged frames (as opposed to network packets).

Yup, I understand what a ping is. You misunderstand my test. My test was to see if mdns discovery worked. Simple as that. ping blah.local from different subnets resulted in a response indicating it could not resolve the hostname. Switch subnets, ping blah.local worked fine, and I could see the traffic in a pcap. This told me mdns wasn't working. Nothing to do with the ping, but it's a perfect way to see if the hostname resolution was working.

When I finally got avahi working on a linux box, the exact same test worked.