UDP Broadcast Relay

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

Previous topic - Next topic
Opnsense.. Ports.. pulls.. also on mirc
OPNsense 24.7 - Qotom Q355G4 - ISP - Squirrel 1Gbps.

Team Rebellion Member

Hi,
I would like to test your plugin.
Can you tell me where to get and how to install it? Is there a ready to install binary or do I have to setup a OpenBSD build machine and compile it?

February 26, 2020, 10:14:27 PM #17 Last Edit: February 26, 2020, 10:16:03 PM by marjohn56
OPNsense 24.7 - Qotom Q355G4 - ISP - Squirrel 1Gbps.

Team Rebellion Member

April 06, 2020, 05:30:39 AM #18 Last Edit: April 06, 2020, 05:36:06 AM by samsonmcnulty
Sorry to hijack but I figured this would be the best place to post this:
I'm trying to enable port 5353 for chromecast etc, but the service won't start. Relevant log locations? same for port 1900.
Quick edit, Disabling the mdns repeater service allows me to start the 5353 forwarder but 1900 still doesn't start


April 06, 2020, 08:06:06 AM #20 Last Edit: April 06, 2020, 09:43:19 AM by samsonmcnulty
Quote from: mimugmail on April 06, 2020, 06:00:37 AM
Upnp plugin?

Yes! good catch. needs nat pnp disabled correct?
Edit: Rather, What needs to be configured for them to play nicely together?
Edit 2: nvm, I helped myself to some quick google-fu and found out what I was doing wrong. Of course the 1900 port won't work...smh its for upnp lol

How can I install this on my opnsense and try it out for sonos? make gives a gcc error.

pkg install os-udpbroadcastrelay-devel

via console

Thanks. I was able to figure it out slightly before the response. So i have this weird result with sonos.

IOS App for sonos works fine. (UDP 1900 or 1901)
MacOS App  for sonos seems to only work if i'm fwd'ing UDP 1900. If I try to use 1901, the result is the app opens, it sees my controller for a moment, and then disconnects and starts searching and then ultimately cannot find it again. Every time. very repeatable.

I doubt it has anything to do with pimd or udpbroadcastrelay, however it's very weird that it only happens on the MacOS App for me.

Thoughts?

Hi,

thx for that great plugin, cause it helped much to get Airplay working between my VLANS. I tried mDNS and IGMP Proxy before, but never worked for me.

Now I'm trying to get DLNA working as well. I use minidlna as server in my LAN and wanna use serveral clients/players in my IOT VLAN.

I tried the port 1900 and the address 239.255.255.250 mentioned in one of the first posts, but I still couldn't connect to the server. Is there any other plugin needed for DLNA? What else I'm missing, maybe some ports on the firewall?

Thanks in advance
Torsten

June 09, 2020, 10:56:12 PM #25 Last Edit: June 09, 2020, 11:09:13 PM by xboarder56
I noticed when trying to launch the plugin I cannot successfully launch it. Running it from the CLI I get the following error. Note: This is caused by miniupnpd (Killed it and the process started okay afterwards)

root@OPNsense:/ # /usr/local/etc/rc.d/os-udpbroadcastrelay start
osudpbroadcastrelay is not running.
Starting osudpbroadcastrelay.
bind: Address already in use
rcv bind
/usr/local/etc/rc.d/os-udpbroadcastrelay: WARNING: failed to start osudpbroadcastrelay

I also noticed another issue with the the black theme on opnsense you cannot read any of the plugin info at all.

https://imgur.com/a/eUPetuU

There was a fix for the theme, try going to plugins and updating it.
OPNsense 24.7 - Qotom Q355G4 - ISP - Squirrel 1Gbps.

Team Rebellion Member

@all: thanks for the nice work in preparing and delivering this pkg to opnsense.

I'm struggling however to get it to work. I've browsed the various webpages, the github repo and this forum, but still haven't found my answer. The thing I see is an error message in the 'General' logfile: /usr/local/etc/rc.d/os-udpbroadcastrelay: WARNING: failed to start osudpbroadcastrelay.
Trying to get some more information I tried starting the relay using '/usr/local/etc/rc.d/os-udpbroadcastrelay start' as root. The result was a somewhat more explicit message: IP_ADD_MEMBERSHIP on rcv: Invalid argument.
What I don't know at the moment if this message is the result of something missing in my installation or the result of my usage (and lack of understanding) of this pkg. To describe the setup: I've just updated opnsense to OPNsense 20.7.2-amd64. The system is running on an APU2D4 since 6+ months and completely stable.
I'm segmented my network using vlan's (x.x.0.x as the main LAN and x.x.100.x as the (wifi) guest network). Normally guests don't have access to the normal lan.
I'm running a couple a squeezeboxes and the LMS server in the x.x.0.x LAN. I'm using the iPeng app on an iPhone to control the server (Logitech LMS) and thus the SB's. I would like to control however LMS even when my iPhone is in the guest network.
iPeng (like any normal LMS/Squeezebox client) sends out a UDP server discovery request towards port 3483 as a network broadcast (x.x.100.255:3483). Any listening server responds the address of the server via a UDP answer. And after that it uses a couple of TCP ports (3483 and 9000) to handle the rest of the protocol.
My thought was to use udpbroadcastrelay to forward the initial UDP broadcast to the main LAN). For now I've come up with the following settings:
- Relay Port: 3483
- Relay interfaces: the names of the two LAN's in Opnsense
- Broadcast Address: x.x.100.255
- Source address: 1.1.1.2
- Instance ID: 1
- Use TTL for ID: <blank>

Any hints/tips/answers much appreciated...

forget the broadcast address, the source address, leave them blank, just put the port and lan interfaces and try that. you'll likely as not need firewall rules too, but First just see if it fires up.
OPNsense 24.7 - Qotom Q355G4 - ISP - Squirrel 1Gbps.

Team Rebellion Member

September 10, 2020, 02:47:39 PM #29 Last Edit: September 10, 2020, 03:51:40 PM by pumo
Hi, I got this work with one chromecast (xiaomi mibox s). however sometimes it disappears. And it did take sometime to get it appear to android tablet..
My phones and tablets are in LAN vlan and try to put chromecast devices to IoT vlan.
I did add Sony android tv to same vlan as mibox, but it doesnt work even if I waited over night.
Should I make firewall rule for port 5353, and to point where and to which side?
My LAN is allowed to pass all vlans, but IOT is only allowed to internet and 53 to my pihole which is in LAN.

Edit: strange I installed igmp proxy plugin to opnsense and upstream to IOT vlan, sony tvbs chromecast is also working now from iot vlan! Even stranger that google chromecast troublehshooter advice to disable igmp proxy. So igmp proxy for sony tv(android 8) and broadcast relay for mi box (android 9).
But enough for me like this  :D