Hey guys,
I'm not sure if you take report for plugins but since the upgrade to 26.1 the updbroadcastrelay plugin refuses to start. Trying to run it manually I get these errors. I use to run it manually for debugging rules so I know it used to work.
/usr/local/sbin/udpbroadcastrelay --id 1 --dev vlan0.2 --dev vlan0.4 --dev vlan0.5 --dev vtnet1 --port 21027 --multicast 255.255.255.255 -d
udpbroadcastrelay v1.3.00 built on Jan 14 2026 03:29:25
Debugging Mode enabled
ID set to 1
Port set to 21027
ID: 1 (DSCP: 1, ToS: 0x04), Port 21027
vlan0.2: 9 / 192.168.2.1 / 192.168.2.255
vlan0.4: 11 / 192.168.4.1 / 192.168.4.255
vlan0.5: 12 / 192.168.5.1 / 192.168.5.255
vtnet1: 2 / 192.168.10.1 / 192.168.10.255
found 4 interfaces total
IP_ADD_MEMBERSHIP: 192.168.2.1 255.255.255.255
IP_ADD_MEMBERSHIP on rcv: Invalid argument
Let me know if you need more info to debug.
Thanks for the amazing work you're doing !
LeTic
To some degree this seems similar to https://forum.opnsense.org/index.php?topic=50520.0
Some people tested the old kernel and found it not to work either, which is a bit weird still.
We're chasing a bug that prevents interface settings from migrating causing at least 2 different distinctive errors. Not sure if there's a third and fourth one with this daemon and miniupnpd.
To be sure... can you run this from the console?
# pluginctl -m
Cheers,
Franco
It works on my system after upgrade.
the migration or udpbroadcast or both? ;)
works for me in 26.1, service running and devices are discovered
Migrated today and udpbroadcastrelay is happily starting here on my Protectli VP2420.
Quote from: letic on January 30, 2026, 09:28:15 AMvlan0.2: 9 / 192.168.2.1 / 192.168.2.255
vlan0.4: 11 / 192.168.4.1 / 192.168.4.255
vlan0.5: 12 / 192.168.5.1 / 192.168.5.255
Slightly offtopic, but even tho this isn't a CISCO device their
'Best Practice Guides' do advise to skip VLAN 0 to 5 when setting up your network so when you feel like it please look into that and decide if you want to change your network setup or not :)
Quote from: franco on January 30, 2026, 10:35:58 AMTo be sure... can you run this from the console?
# pluginctl -m
Thanks Franco for the feedback. I ran it but it didn't return anything and it didn't change the behaviour.
I tried the patch from here (https://forum.opnsense.org/index.php?msg=258554) as you were referencing this issue but it didn't solve it for me. Still get
IP_ADD_MEMBERSHIP: 192.168.4.1 255.255.255.255
IP_ADD_MEMBERSHIP on rcv: Invalid argument
I only get this if I try to run it manually. The daemon seems up and running now.
Quote from: nero355 on January 30, 2026, 03:32:01 PMeven tho this isn't a CISCO device their 'Best Practice Guides' do advise to skip VLAN 0 to 5 when setting up your network
Cisco/CCNA best practices do not say to "skip VLAN 0-5." VLAN 0 is a special 802.1Q priority-tag concept and the common guidance is to avoid VLAN 1 for production/management and to change the native VLAN to an unused VLAN. VLANs 2–5 are valid and routinely used.
Quote from: nelox on February 02, 2026, 02:08:27 AMCisco/CCNA best practices do not say to "skip VLAN 0-5."
It was either 0-4 or 0-5 when I took my CCNA somewhere in 2013/2014 so maybe things have changed by now... dunno... :)