What happened to udp-broadcast-relay-redux on 25.12?

me.yay · May 17, 2026, 6:26pm

I wanted to perform an Attended Sysupgrade from 25.12.3 to 25.12.4, and realized the upgrade fails because the package is missing.

Is there an alternative solution to relay broadcast messages from one subnet into another?

andyboeh · May 17, 2026, 7:10pm

It was removed:

me.yay · May 17, 2026, 7:14pm

I expected the answer, but hopped for a different one, since what appears to be the upstream repo is orphaned for more than years now.

pluffmud · May 19, 2026, 9:54pm

I was using this as well but managed to replace it with 'socat' . YMMV

me.yay · May 23, 2026, 4:43pm

I was not aware socat was able to receive broadcast messages. I might give it a try.

I was wondering if and how this nftables-based approach could be configured in OpenWRT:

github.com/udp-redux/udp-broadcast-relay-redux

The kernel itself can do this

opened 02:44AM - 08 Nov 20 UTC

squarooticus

In trying to debug my Google Cast issues last night, I discovered your daemon. I…t works great, presumably because it doesn't ingest and then create new mDNS payloads like avahi-daemon does. But then I realized nftables can do the same thing. To wit: ``` table ip mangle { chain prerouting { type filter hook prerouting priority mangle; policy accept; ip daddr 224.0.0.251 iif enp2s0.30 ip saddr set 192.168.1.1 dup to 224.0.0.251 device enp2s0.10 notrack ip daddr 224.0.0.251 iif enp2s0.10 ip saddr set 192.168.3.1 dup to 224.0.0.251 device enp2s0.30 notrack } } table ip6 mangle { chain prerouting { type filter hook prerouting priority mangle; policy accept; ip6 daddr ff02::fb iif enp2s0.30 ip6 saddr set fd20:1111:1111:1::1 dup to ff02::fb device enp2s0.10 notrack ip6 daddr ff02::fb iif enp2s0.10 ip6 saddr set fd20:1111:1111::3::1 dup to ff02::fb device enp2s0.30 notrack } } ``` The above repeats mDNS packets from enp2s0.10 to enp2s0.30 and vice versa. Works great. Kinda nuts how simple this is.

Looks like firewall includes could be a convenient way to configure it: