Quote from: Monviech (Cedrik) on August 25, 2026, 04:22:41 PMI know I could download the package and extract it but not having the source code browsable (since its in a private repo) is a bit meh.
Quote from: Tinus on August 25, 2026, 05:52:21 PMIf a machine wants to resolve an mDNS name, it sends a multicast message to port 5353. All the other machines see this message, and the ones that want to claim that name respond with a multicast message to port 5353.
What the relay does is simply listen to all these messages and for every message that comes in on one of the configured interfaces, repeat it on all of the other configured interfaces.
So with simple firewall rules you can't really distinguish between the requests and replies and what you want to achieve is not possible. You would have to use a different relay that allows you to be more selective. I don't know if that exists and if the results would be what you want.
Quote from: Patrick M. Hausen on August 25, 2026, 06:47:13 PMAssign a static IP address to your printer in your Fritzbox and create a DNS override for your internal systems to use instead if mDNS?
QuoteIf I'm following that sequence right, it sounds like your broke something (probably your dnsmasq DHCP config) before resetting the ISC DHCP config (and maybe the clients were still clinging onto old leases, or something). Maybe you could try resetting the ISC DHCP config again, and hopefully dnsmasq is still functional from the 2-days-ago snapshot.....
<?xml version="1.0"?>
<opnsense>
<version>11.2</version>
.
<cert uuid="3d19c8be-0d2c-4267-bfd2-f322c88a6dcf">
<refid>a1b2c3d4e5f6</refid>
<descr>Text Description</descr>
<caref>a1b2c3d4e5f60</caref>
<crt>[Very long continuous string of the public key of this certificate]</crt>
<csr/>
<prv>[Very long continuous string of the private key of this certificate]</prv>
</cert>