UDP Broadcast Relay

[ntc4231g7]

thank for all information.

[neuling10]

I use the UDP Broadcast Relay successfully for AirPrint and AirPlay - thank you very much for this very helpful plugin   :D

Unfortunately, I am unable to connect to my Somneo WakeUp Light using the Philips SleepMapper iOS app. Has anyone managed to set up VLAN broadcasting with the WakeUp Light?

[neuling10]

Another question: Is there any way to find out the required broadcast address and port?

My household devices also require multicast routing. mDNS and SSDP unfortunately doesn't work

[neuling10]

I use the UDP Broadcast Relay successfully for AirPrint and AirPlay - thank you very much for this very helpful plugin   :D

Unfortunately, I am unable to connect to my Somneo WakeUp Light using the Philips SleepMapper iOS app. Has anyone managed to set up VLAN broadcasting with the WakeUp Light?

Problem solved: A firewall rule was missing on LAN and VLAN net:
IPv4 ICMP   VLAN Netzwerk   *   Diese Firewall   *   *   *

[ooopppnnn]

Hey,

First thank you very much for the plugin!

I noticed that on your github you added support for --allowcidr and --blockcidr. Can I use it somehow with the opnsense plugin? I can't find them in the UI but maybe I can manually edit something to also add these?
Any plans on adding them to the plugin?

Thanks

[Onkel-tobi]

Hi all,

anyone who has airplay with Sonos running via udp broadcast relay?
For me it is not working.
A different device than Sonos (Denon) is working fine on the same plan, but with the Sonos its different.
I can see the device via airplay but connection is not possible.
Any hints? / anyone who has this running?

regards,
Tobias

[space_ranger]

Anyone know how to debug this not starting?

the error is

Code Select Expand

Notice root /usr/local/etc/rc.d/os-udpbroadcastrelay: WARNING: failed to start osudpbroadcastrelay

I've found a github thread saying wire guard was an issue but I don't use it. Other than that error I cant work out whats wrong.

Running     Opnsense 24.7.10_2 at present

[nolith]

Anyone know how to debug this not starting?

the error is

Code Select Expand

Notice root /usr/local/etc/rc.d/os-udpbroadcastrelay: WARNING: failed to start osudpbroadcastrelay
I've found a github thread saying wire guard was an issue but I don't use it. Other than that error I cant work out whats wrong.

Running     Opnsense 24.7.10_2 at present

I had the same problem, in my case I wanted to support mDNS on port 5353, but it was already occupied by Unbound because I run AdGuard on port 53.

I had to move Unbound to port 5354 and then I could start the relay

[xkpx]

Anyone know how to debug this not starting?

the error is

Code Select Expand

Notice root /usr/local/etc/rc.d/os-udpbroadcastrelay: WARNING: failed to start osudpbroadcastrelay
I've found a github thread saying wire guard was an issue but I don't use it. Other than that error I cant work out whats wrong.

Running     Opnsense 24.7.10_2 at present

I had the same problem, in my case I wanted to support mDNS on port 5353, but it was already occupied by Unbound because I run AdGuard on port 53.

I had to move Unbound to port 5354 and then I could start the relay

Same issue here but 5354 doesn't help either.

Code Select Expand

2024-12-31T19:43:13 Error configd.py [b8fe79e4-0d81-47ea-94b1-c43ffa3b6680] returned exit status 1
2024-12-31T19:43:13 Notice configd.py [b8fe79e4-0d81-47ea-94b1-c43ffa3b6680] starting udpbroadcastrelay instance

[Rvh]

Anyone know how to debug this not starting?

the error is

Code Select Expand

Notice root /usr/local/etc/rc.d/os-udpbroadcastrelay: WARNING: failed to start osudpbroadcastrelay
I've found a github thread saying wire guard was an issue but I don't use it. Other than that error I cant work out whats wrong.

Running     Opnsense 24.7.10_2 at present

I had the same problem, in my case I wanted to support mDNS on port 5353, but it was already occupied by Unbound because I run AdGuard on port 53.

I had to move Unbound to port 5354 and then I could start the relay

Same issue here but 5354 doesn't help either.

Code Select Expand

2024-12-31T19:43:13 Error configd.py [b8fe79e4-0d81-47ea-94b1-c43ffa3b6680] returned exit status 1
2024-12-31T19:43:13 Notice configd.py [b8fe79e4-0d81-47ea-94b1-c43ffa3b6680] starting udpbroadcastrelay instance

I'm having the same issue after updating to the 25.1.x version of opnsense. I had it working before. I'm trying to get steamlink to work across 2 VLANs on port 27036, configured with source address as 1.1.1.2, and broadcast address of 255.255.255.255. Is there any way to get a more specific error message as to why I'm getting:

Code Select Expand

Notice root /usr/local/etc/rc.d/os-udpbroadcastrelay: WARNING: failed to start osudpbroadcastrelay
I'm not really sure where to start with debugging, especially as the configuration was working fine before the firmware update.

[mightyi]

I'm been fighting with getting my Sky devices to behave properly on the separate VLAN for a few weeks; finally after reading this thread i've got it working using UDPBR. Have to say great work on the application, it's the only one i've found to successfully work so far!

I've also got a few other devices going into the Streaming VLAN: Sonos speakers, nVidia Shield, Yamaha AV Amp, couple of LG TVs, Amazon Fire TVs and a couple of Apple Pods. This means I'll be running a near full complement of stuff, including Airplay/Bonjour, mDNS, DLNA SSDP etc.  I've also got a separate IoT VLAN which will soon be housing Meross smart plugs, sockets, twinkly lights etc - I've seen nothing so far about what protocols are needed for the Twinkly app to work correctly - that's picky at the best of times!

I've got my firewall rules pretty restrictive with multiple VLANS (Security/Streaming/IoT/Management/Internal LAN); although internal LAN is configured to allow all traffic to other VLANs. To make things even more complex, i'm using a Unifi PoE 2.5GBe switch and multiple Unifi APs on the network. 

I added the default rule to allow anything from the Sky Q boxes to the LAN, and added several relay rules in UDPBR:
239.255.255.20:1900; 239.255.255.250:9131; 239.255.255.250:51200; and 224.0.0.51/224.0.0.251:5353 (source 1.1.1.1).  I had to add the extra options as the Sky Q box was failing on requests (even though it appeared to be working ok on the app). I also found that putting 1.1.1.1 instead of blank resulted in the connection failing - but what i've now got is a weird problem, where the media servers (running Plex and Emby) are staying on the internal network, but need to talk to the shield and the firesticks (and later the TVs and a hifi network streamer). It seems the media servers are getting a bit confused because they are getting bounced requests to the broadcast address of the Streaming device VLAN - the only way i can remove that is to add a specific rule in the Streaming FW rules to allow it.  is this expected behaviour?  As I have a default allow any rule to the streaming VLAN I expected that to also encompass the broadcast IP - but i would not have expected to have to allow the traffic specifically for broadcast IPs?
I also seem to be seeing some multicast traffic from the shield to 255.255.255.250: 51200, 1901 and 9131 which i don't recognise? Has anyone setup like this with Emby/PLEX and come across this issue and a workaround?

On a final point; i've found i've had to add specific floating rules in to allow multicast traffic to come through in order for it to be processed by UDPBR - while i expected it not to handle the outbound client request, I didn't think i needed to add specific rules to allow the traffic into the interface in the first place? 

Any tips on what i need to configure for my IoT and Media Servers would really be appreciated!

[mightyi]

A Small update; i have managed to get Plex and Emby working via an Amazon Fire Stick over the VLANs, which is great.
for reference, you need to open up 32400/udp from the fire tv to the media server for plex, and 8096/8920 TCP for Emby (7359/U) for server discovery.

But i've just run into a weird problem!  whilst the i-apps work perfectly for Sky Q, when i try to connect to the Sky Q box from the windows app on an internal LAN PC, it hangs, before telling me it needs to be connected to a sky Q box for recordings.  No rejects in the firewall when this happens, lost of 1900 and multiple requests back from each sky Q/mini box - but it fails.

Can't see why they would be different!

[marjohn56]

Sky Q is why I originally put this package together. 😊

I suspect you need to add a firewall entry on your PC. Windows will block the responses from the Q box as it's coming from an address on a different VLAN.

Open windows firewall, Select Advanced Settings

Select Inbound Rules
New Rule

Name: Sky Q Pass
Enabled: Ticked

Protocol and Ports Tab
Proto Type: Any

Ports: Local and Remote: Any

Scope Tab
Local IP address: Any
Remote IP: YOUR Q BOX IP - In my case 10.4.15.91

Advanced Tab:
Specify profiles to which this rule apples
Tick all of them

That should do you.

[Rvh]

I managed to get it working by removing the 1.1.1.2 as source address and instead leave it blank.

[marjohn56]

I managed to get it working by removing the 1.1.1.2 as source address and instead leave it blank.

Source address is not required for Sky SSDP which is what the OP was asking about.

It's covered in the documentation.