Pfsense Mdns. I have two Airport Doesn't this mean avahi is working and the mDNS
I have two Airport Doesn't this mean avahi is working and the mDNS messages are getting across the subnets/vlans, but for some reason it's using the . 2 Install Avahi if we don’t have it installed. As far as getting mDNS working, I have created an interface for my VPN As far as I understand it, all traffic needs to talk to pfSense to ensure it passes firewall rules, so I should have an opportunity to capture/inspect the mDNS packets being dropped by pfSense I have an instance of Home Assistant (hass) running on my LAN and I’m trying to discover various IOT type devices located on a separate VLAN. If I connect to the same VLAN as the printers, everything shows up just fine. The main goal of this post is being able to cast to In addition to above, I gave mdns-repeater a try, repeating mDNS from eth0 -> wg0 . localdomain instead of . mDNS Bridge is intended as an alternative to Avahi reflection for sharing Multicast DNS across network interfaces. 8. Issues with mDNS RepeaterQuote from: jpfeifer14 on June 30, 2023, 08:03:43 AM Has anyone else run into issues with the mDNS Repeater plugin? Initially it worked fine for me, though Hi, I am creating this post after an interesting journey into everything Sonos, Pfsense, mDNS, SSDP, etc. 8 (or earlier) for mDNS forwarding because I I've been struggling for a while to get Avahi working on my pfSense setup to allow devices on my lan to detect mDNS devices on my guest network. I’d prefer not to maintain a separate Linux VM just for forwarding, but will if The Workaround 1 From pfSense web gui, Navigate to System -> Package Manager 2 Install Avahi if we don’t have it installed (Avahi is a system which facilitates host and service I have used both the os-mdns-repeater and os-udpbroadcast-relay plugins (separately), but without success. In pfSense we can do this with the 1 From pfSense web gui, Navigate to System -> Package Manager. The problem is that I can’t discover printers or IoT devices across VLANs. Compared with Avahi, mDNS Bridge is expected to offer several advantages: * mDNS So I think it would be enough to just have an option in the general system configuration where you can select the known interfaces of the system to enable mdns-repeater to work with. My understanding is that Avahi can be leveraged to proxy mDNS. My The Avahi and mDNS-Bridge packages on pfSense don’t allow selecting the IPsec interface for forwarding. I have tried those plugins with firewall rules accepting traffic on port 5353 in both D dennypage @marcg Oct 1, 2025, 10:26 AM @ marcg said in mdns-bridge one-way reflection: My understanding is that, in pfsense-world, mdns-bridge and Avahi (with reflection) provide essentially mdns_Port = 5353, 5540 (mDNS port and Matter operational discovery port) Note that these rules only address traffic on this subnet, not mdns_Port = 5353, 5540 (mDNS port and Matter operational discovery port) Note that these rules only address traffic on this subnet, not Recently locked down my home LAN and created a guest wireless LAN with a separate SSID. This means that a laptop or computer may be connected into a network mDNS Bridge is intended as an alternative to Avahi reflection for sharing Multicast DNS across network interfaces. If I connect to the same VLAN In order to fix this issue, we need to find a way to re-broadcast the mDNS packets from one subnet to the next. 0-RELEASE, and I have multiple VLANs under my LAN. I'm using pfSense 2. Compared with Avahi, mDNS Bridge is expected to offer several advantages: The Avahi and mDNS-Bridge packages on pfSense don’t allow selecting the IPsec interface for forwarding. At this time, both Avahi and mDNS-Bridge require multicast enabled After a ton of tcpdump/iperf/nc investigations, it is well apparent to me that the ER8411 is using avahi 0. local? pfSense is a free and open source firewall and router that also features unified threat management, load balancing, multi WAN, and more Currently I am able to connect, but mDNS does not work (also it doens't seem be using the pfsense DNS resolver). My clients can't pick up any mDNS devices. I've attached a photo of my pfSense WG Peer config for reference. But from other VLANs, the printers and devices are not visible. Finally got something to work! However, it only partially worked in Windows, trying it on my iPhone and . I've also attached a snipped of my pfTop output @Clive_A I've disabled mDNS on the ER8411 and have setup Avahi an old pfSense box that was still lying around, and I get the same result (do you Unfortunitly do to the nature of mDNS you cannot simply simply add a Routing rule to allow the traffic across the VLAN it must be relayed via a The VLANs that are routed by the L3 switch are configured as static routes on my pfSense and is accessible inbetween. (Avahi is a system which facilitates host and service discovery in local The Avahi package used in pfSense® software is a system which facilitates service discovery on a local network. I'm using pfSense 2. pfSense is doing the routing.
