UDP Broadcast Relay beta package

[marjohn56]

There are now so many people running this now and I'm sending out a couple of PM links a day, so I'm just going to post it here. One day it will get officially taken up and will appear in the plugins. In the meantime should something change then I will update the pkg accordingly and post here.

You can grab it here. https://www.dropbox.com/s/no60byvyspab9m0/os-os-udpbroadcastrelay-devel-0.5_0.6.txz?dl=0

To install, copy the file to a your opnsense instance /tmp folder. Go to the shell, cd to the /tmp folder and issue the following command.

pkg install os-*.txz

You should then have a new menu item in services.

This is an updated version of udpbroadcastrelay that uses a new method of reflection detection. This can be overridden using the Use TTL for ID option, it then resorts to it's former operation, however the new method appears to work fine, so you should be able to leave that option un-ticked.

It now also supports multiple multicast addresses on the same port.

Add the relay you want, here are the values for some common ones. the --dev items refer to your interfaces, in the UDP Broadcast Relay menu you just select the interfaces from the dropdown box in the menu.

Syncthing discoveryudp_vars="--id 1 --port 21027 --dev igb1 --dev igb2"

mDNS / Multicast DNS (Chromecast Discovery + Bonjour + More)udp_vars="--id 1 --port 5353 --dev eth0 --dev eth1 --multicast 224.0.0.251 -s 1.1.1.1"(Chromecast requires broadcasts to originate from an address on its subnet)

SSDP (Roku Discovery, Sonos + More) --id 1 --port 1900 --dev eth0 --dev eth1 --multicast 239.255.255.250"


Lifx Bulb Discovery --id 1 --port 56700 --dev eth0 --dev eth1

Broadlink IR Emitter Discovery --id 1 --port 80 --dev eth0 --dev eth1


Warcraft 3 Server Discovery --id 1 --port 6112 --dev eth0 --dev eth1"

Once you have created the instance(s) you'll need to start them for the first time from the services widget in the lobby, just click on the start button that will have appeared there. After that you can start and stop them from the UDP Broadcast Relay menu itself.


NB - each instance should have a unique ID, 1 2 3 etc...

[jhenderson0107]

I'd like to try using the package, but the dropbox link appears broken.  Thank you in advance for your assistance. 

[marjohn56]

Just checked it and its working fine.


I did notice that dropbox now opens the txz file, but just click the download button and you get the full txz file to install.

[mimugmail]

I'd like to try using the package, but the dropbox link appears broken.  Thank you in advance for your assistance.

pkg install os-udpbroadcastrelay-devel

[marjohn56]

is he running on dev? I did not see that.

[mimugmail]

This also works in production :)

[marjohn56]

OK, never knew that. So although you cannot see it in production plugins you can install it from the shell, you learn something new every day - currently I'm learning to do brain surgery...

[Gauss23]

Hi,

I just tested the current devel version of the plugin.

I was searching for a replacement for mDNS-repeater because I had timeouts after 5 minutes. The device is not reachable anymore from other networks after that period.

I tested the udp broadcast relay plugin with mDNS and it was working. Altough I needed to leave away the 1.1.1.1 or 1.1.1.2 as source address. With 1.1.1.1 it had the same timeouts like mDNS-repeater and with 1.1.1.2 the devices (HP with Bonjour service) didn´t show up on other networks.
With empty source address it´s working without timeouts.

As I don´t have a Chromecast I can´t test if this would fail in my setup.

Thank you very much for this plugin. Good work so far!

[GreenMatter]

I've installed the package and all (almost all) works well, except onkyo broadcast.
I know onkyo sends broadcast using port 10102. I wasn't sure of broadcast address and with use of tcpdump I managed to observe that once broadcast address is set to 239.255.255.250 mobile devices in other subnets are able to send packets over respective subnet's broadcast address to onkyo receiver. Unfortunately, it doesn't allow for onkyo app to find and login to receiver.
I did try to set source address, use TTL for ID and nothing helps. Required ports in firewall are open between subnets. What am I missing?

[marjohn56]

Some manufacturers do weird things. Onkyo was not on the list of systems known to work with the original daemon. I'm afraid you might have to contact Onkyo and find out from them how they communicate with their apps if you can find nothing on the www.

[GreenMatter]

I'm afraid you might have to contact Onkyo and find out from them how they communicate with their apps if you can find nothing on the www.

Thanks for a prompt reply. I've contacted them but the only thing I got was the answer from guy who used typical FAQ sheet and told me that all devices must be in one subnet. No technical info at all. I'll try one more time to contact Onkyo, maybe this time I'll be more lucky...

[namnnumbr]

Thanks for providing this package!

I have followed the instructions to install and set up, but I cannot find my Sonos speakers over Airplay across VLANs.  I actually believe this to be an issue with my switch (TP-Link T1700G-28TQ).  Are there L2 and/or L3 settings I should consider while trying to configure the switch?

My network is a router-on-a-stick topology, with OPNsense trunked to the T1700 with Home and IoT VLANs.  The T1700 switch is trunked to another switch with equivalent native vlan and vlan setup to which the WAP is connected.

[marjohn56]

Good question to which i do not have an answer. The way to prove or disprove is to use the port mirroring feature and see if the packets are being relayed across the VLANs. I use DLink switches and using port mirroring I am able to see the UDP packets being relayed. If you have set it UDPBroadcastRelay correctly, and it's pretty difficult not to, then you should be able to use Wireshark to see them. I would not have thought you needed to do any extra settings on the switches, mine are just set to basic settings with the VLANs set up and it works.

[franco]

Shall we release this plugin as stable 1.0 version?


Cheers,
Franco

[samsonmcnulty]

I'd love to step in and say "Hell yes" lol