Messages

Ok, I think I found a solution to this. Need to do some more thorough testing, but at least for the time being it seems stable. What helped me was to add the following rule to all interfaces that are part of the mdns relay, before the rule that sends traffic to the failover gateway group:

ALLOW from * to 224.0.0.251 port 5353, protocol UDP, IPv4

This should also work as a single floating rule instead of having to create the rule on all individual interfaces – something to be checked.

Did you ever manage to solve this issue? Facing the same problem here currently and trying to find some solution for it.

Recently, I've been wanting to setup a failover Multi-WAN and have followed the instructions here. Things worked, however I've noticed that the relay no longer responds how I want it to.

I just experienced the exact same issue. Switching back to the default gateway rule didn't even work for me directly. Had to completely reboot the box to get it running again. If anyone has a solution to this, I'd be very much interested.

Hi all,

I'm trying to find a solution to the following problem: I have two separate apartments behind the OPNsense firewall, each apartment with its own client-vlan and IoT-vlan. I want to relay udp packages between the client-vlan and IoT-vlan of each apartment, but not between both appartments (Apartment A should not see devices in apartment B and vice versa). I had this working with multicast-relay https://github.com/alsmith/multicast-relay on docker on the udm-pro, but would like to switch to OPNsense.

I have tried starting multiple instances of UDPBR on the different vlans/interfaces, but it's not letting me use the same port twice. Is there any way to get around this, seeing that I am using different interfaces?

Multicast-relay uses a single instance and lets the user specify in the ifFilter.json which subnets are allowed to talk to each other. Could this be an option for UDPBR?