UDP Broadcast Relay

Started by marjohn56, February 03, 2020, 06:34:50 PM

Previous topic - Next topic
September 14, 2022, 05:42:39 PM #165 Last Edit: September 16, 2022, 04:55:28 PM by QuaCKeReD
Hi All,

I have split my network into VLANs and am struggling to see Bonjour devices (else why would I be here? 😛 )

The 3 VLANs I am concerned with, that have Bonjour devices, are;
- VLAN1 - mgmt, 10.0.1.0/24
- VLAN10 - my devices, 10.0.10.0/24
- VLAN20 - service devices, 10.0.20.0/24

Main goal, at moment, is that I have an LG TV, advertising Apple TV, on VLAN20 that my iPhone on VLAN10 cannot 'see'.

I have installed and enabled the plugin as described for mDNS (running manually shows lots of '<-' and '->' lines, so mDNS traffic is being detected (?).

I currently have allow TCP any>any rules on each VLAN.

I have tried running a Bonjour browser on laptop, also VLAN10, and can see iPhone and other devices, all in VLAN10. But, nothing else.

Any help here would be greatly received 😀

EDIT - not sure how, but it seems VLAN10 sends to the broadcast address, and other VLANs send to their gateway?


SOLVED - For anyone else having similar issues in future;
- Installing the plugin and enabling on selected interfaces may be enough.
- The problems come when you have firewall blocking certain things. In my case this was the FireHOL block list which blocks RFC1918 networks, and AND 224.0.0.0/3 networks 😟
Adding a negation for these and it all magically works!
- No, seriously, it is magic and it is as easy as installing. Just be aware of what else you already have in place 😟
Unit: Protectli VP2410
CPU: Intel Celeron® J4125 Quad Core at 2 GHz (Burst up to 2.7 GHz)
RAM: 16GB DDR4
SSD: 256GB M.2 SATA

Broadband: Virgin Media VOLT
Down: 1.2Gbps
Up: 55Mbps

Quote from: marjohn56 on February 24, 2021, 12:11:26 AM
I've just found another document, a Cisco one... not sure it's totally correct.


https://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/7-6/chromecastDG76/ChromecastDG76.pdf. Interesting in they say you can cast to the chromecast, but not manage it.


Have you tried MDNS repeater? You can use it alongside UDPBR providing you don't use the same ports, mdns repeater uses port 5353 and 224.0.0.251

How would you run mdns and udpbr together? Would the ports need to be changed on udpbr? I followed your guide for casting from my phone to YouTube and it doesn't work for me. I'm using the exact rules you had for 5353 listening on the 2 interfaces one where the TV is and one where the phone is. Firewall is wide open for the TV to talk back to the phone.

Quote from: PigeonEgo on January 31, 2022, 04:50:22 AM
Quote from: guyp2k on December 30, 2021, 12:26:43 AM
Curious if anyone has had any success w/ Logitech Harmony Hubs? If so, would you mind sharing some specifics.

ROON and SONOS is working fine, but have been unable to setup the Logitech HUBs across VLANs.

NM, think it's working now, had to use multicast of 224.0.0.1 and port 5224.

Thanks

Can you share what your entry is to get Roon working? I have read on Roon forums that it needs port 9003, but that doesn't seem sufficient. I have Airplay and Sonos working, but not Roon.

Yes, added 9003 to UDPBR, selected interfaces/networks, and created a FW rule to allow my ROON server to talk to the other networks. That's about it and was a minimul effort.

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?

It seems that since upgrading to 23.1, my setup for SSDP which had been working reliably in 22.X is now only working for a short time and then silently stops working. The daemon is still running but packets are no longer forwarded between subnets.

If I change the config of udpbroadcastrelay in the UI to force a restart of the daemon it will work for a few minutes but then packets stop flowing stop again. For example, if I change the interfaces to something else and then back.

Has anyone else encountered this? I can't imagine what else could cause this besides udpbroadcastrelay having some issues.

March 05, 2023, 05:21:16 PM #170 Last Edit: March 09, 2023, 03:54:31 PM by driz
Hello, very new opnsense user here. I'm about 3 days in. UDP broadcast relay made casting to my TVs stupid simple, so thanks! I followed the guidance in this thread and it was working pretty quickly across VLANs. However, I was wondering if anyone has a situation similar to my other. I have some security cameras around the home, they are configured for multicast on 224.1.3.X (X being 1 through 10) on port 20016. When on the same vlan, i can subscribe to these feeds with udp://224.1.3.X:20016. I have some raspberry pis affixed to the back of monitors around the home all displaying these multicast feeds in a no WAN access vlan.

I would also to view the multicast feed from my PC which is in a different VLAN. I have IGMP setup on my trunk ports, the camera ports, my PC's port, and the router's port. in UDP Broadcast relay, i set the relay port to 20016, selected my two vlan interfaces, and individually put in each multicast ip the cameras are on. I have some pretty open rules for the camera IPs, their multicast IPs, and all the ports they might use. It's not working and I'm not seeing anything in the firewall logs. I am hoping someone else has attempted to do something similar and may have some advice? :)

-----
As an additional note, I found in Marjohn56's gh repo that udp broadcast relay supports --msearch dial, this support doesn't appear to have made it into the opnsense plugin yet. Unknown arg: --msearch
I'm a dev with linuxserver.io and general IT enthusiast

Hi, I'm also jumping on this thread to say first, it works pretty great with HomeKit and chromecast.
I have no issue using this 2 services but I tried to debug only one issue where in the google home app, I'm unable to configure my nest hub but I can see the player on the small dashboard card or in the media dashboard but when I click on the device, it says that I'm not on the same wifi (but time to time it works and I'm able to configure...).

When it works I can see on the firewall that my phone communicate with the nest port on 8443.
Has someone figured out this thing?

Quote from: driz on March 05, 2023, 05:21:16 PM
-----
As an additional note, I found in Marjohn56's gh repo that udp broadcast relay supports --msearch dial, this support doesn't appear to have made it into the opnsense plugin yet. Unknown arg: --msearch


I've not had much time to play with Opnsense or the plugins for quite a while, work has been a pig since the end of covid. The PR's to udpbroadcastrelay to add the --msearch dial features etc were submitted by others quite a while ago, and whilst I did merge the PR's recently I never got around to pushing them upstream to the Opnsense repo. Apart from that I had not compiled the update and tested it. I have now done so and running it on my system it appears to work fine, though I don't use the new features. I've attached it here so you can try it. It's substantially larger than the executable distributed with Opnsense but that's because of my compiler settings. Try it, if there's an issue it might take a while for me to take a look so back up the original which lives in /usr/local/bin so you can change back if needed.
OPNsense 24.7 - Qotom Q355G4 - ISP - Squirrel 1Gbps.

Team Rebellion Member

Hi all,

I'm currently using UDPBR as a relay for the Unifi Discovery Protocol, and things have been working swimmingly since day one of my opn deployment. 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 did a little investigation and found the following:

  • Wireshark shows that the packets are still being broadcast
  • Setting the "Default Allow LAN to any" rule's gateway to "default" makes things work (not an option due to the routing getting all wonky)

Has anyone successfully used UDPBR on a multi-WAN setup? I realize this might not be related to UDPBR at all, but just wanted to boomerang this here just in case.

June 17, 2023, 02:06:52 AM #174 Last Edit: June 17, 2023, 12:50:12 PM by satchafunkilus
Quote from: tissuelord on May 15, 2023, 04:47:34 AM
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.

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.

Hi,

I have got several VLANS in my home.
Two of them are "home" (my standard networ) and "IoT" (where I putt all my little internet of things devices).

I have two WiiM Mini Streamers in my IoT Network.
I now want to use the Symfonium app on my Android phone (home network) to stream my Jellyfin music to the WiiM Mini Streamer using the WiiMs functionalty as an UPNP renderer.

When I connect my mobile phone to the IoT Network, I can see the WiiMs as UPNP streaming targets.
When I am connected to my home network, I do not see them.

I now set up UDP Broadcast Relay as you can see in the attached scrrenshot.
I also opened the firewall between IoT and Home completetly (for testing).

However, I still don't see the WiiM Minis from my home network. However for the Chromcasts it works.

Any idea?

Not a direct answer, but instead of jellyfin music, have you considered Roon? https://roon.app/en/

I found a forum post about your WiiM mini and Vlans here, maybe that helps also: https://forum.wiimhome.com/threads/app-option-for-fixed-ip-devices-on-another-network.127/
Deciso DEC850v2

I can find the WiiM in the WiiM app. I think this works with the mDNS Multicast.

Only it cannot be discovered as an UPNP renderer. Seems to be different independent things that rely on different multicast of whatever...

August 26, 2023, 07:29:13 PM #179 Last Edit: August 26, 2023, 11:30:24 PM by otherego
post deleted