How can I get this UDP relay package for casting across VLANs?

sfxdude

@tman222 I'd say if it works it's probably fine, but no harm in rebuilding for the new one.

josepr

Anyone has the binary avaliable for the sg-1100?

stephenw10

Obviously it would need to be compiled for aarch64. It might be simple enough a compile against FreeBSD 12.2 will work. You would need to be setup for cross-compiling or have am aarch64 build box.
Adding your comments to the feature request night be best.

Steve

Qinn

@tman222 said in How can I get this UDP relay package for casting across VLANs?:

udpbroadcastrelay

I think it is here https://freebsd.pkgs.org/12/freebsd-aarch64/udpbroadcastrelay-0.3.b.txz.html

I can't test it for aarch64, as I don't own one, but downloaded the am64 version copied it to pfSense 2.5.0 and did a

chmod 755 udpbroadcastrelay

Then excuted it and it performed nicely.

stephenw10

Oh that's interesting, I didn't realise it had been included upstream. Makes things a lot easier.

Though I had to upload it rather than fetch it directly:

[21.02-RELEASE][admin@2100-2.stevew.lan]/tmp: pkg add udpbroadcastrelay-0.3.b.txz 
Installing udpbroadcastrelay-0.3.b...
Extracting udpbroadcastrelay-0.3.b: 100%
[21.02-RELEASE][admin@2100-2.stevew.lan]/tmp: rehash
[21.02-RELEASE][admin@2100-2.stevew.lan]/tmp: udpbroadcastrelay 
usage: udpbroadcastrelay [--id ID] [--port udp-port]
       [--dev dev1] [--dev dev2] [--dev devX]
       [-s IP] [--multicast ip1] [--multicast ipX]
       [-t|--ttl-id] [-d] [-f]
       [-h|--help]

Edit: Looks like it was only added last week.

Steve

tman222

Cool, this is great news! I assume this link is for the amd64 version of the package?

https://pkgs.org/download/udpbroadcastrelay
https://freebsd.pkgs.org/12/freebsd-amd64/udpbroadcastrelay-0.3.b.txz.html

I actually just recently recompiled the udpbroadcastrelay source for pfSense 2.5.0 (FreeBSD 12.2 Stable) but will keep this link in mind for future versions. I'll also update my initial post in the thread above.

tman222

@stephenw10 - when installing the udpbroadcastrelay as a FreeBSD package, where on the file system is the binary located (will be needed for ShellCmd)? Thanks in advance.

bmeeks

@tman222 said in How can I get this UDP relay package for casting across VLANs?:

@stephenw10 - when installing the udpbroadcastrelay as a FreeBSD package, where on the file system is the binary located (will be needed for ShellCmd)? Thanks in advance.

Usually binary executables from packages go in /usr/local/bin and configuration files in /usr/local/etc. Any shell script provided with the package typically winds up in /usr/local/etc/rc.d. But these are not hard and fast rules - a package creator might deviate from the standard practice.

Qinn

@tman222 Do a

find / -name 'udpbroadcastrelay'

and you will find it's location.

Qinn

btw if you don't have the repository, then do a

 pkg add https://pkg.freebsd.org/FreeBSD:12:amd64/quarterly/All/udpbroadcastrelay-0.3.b.txz

for an AMD64 and then a

rehash

and a

 pkg info udpbroadcastrelay

shows it is nicely installed

[2.5.0-RELEASE][root@pfSense.localdomain]/: pkg info udpbroadcastrelay
udpbroadcastrelay-0.3.b
Name           : udpbroadcastrelay
Version        : 0.3.b
Installed on   : Wed Mar 17 11:54:50 2021 CET
Origin         : net/udpbroadcastrelay
Architecture   : FreeBSD:12:amd64
Prefix         : /usr/local
Categories     : net
Licenses       : GPLv2
Maintainer     : m.muenz@gmail.com
WWW            : https://github.com/marjohn56/udpbroadcastrelay
Comment        : UDP multicast/unicast relayer
Annotations    :
        FreeBSD_version: 1202000
Flat size      : 39.2KiB
Description    :
udpbroadcastrelay is a UDP multicast relayer. Its intended use is to
rebroadbcast udp packets on a specific port across interfaces, be those
interfaces physical or VLAN.

It is used where devices such as Sonos or Sky are spread accross
different subnets and are not able to detect the servers or devices.

WWW: https://github.com/marjohn56/udpbroadcastrelay

Itar

Hi,

can someone give me a hint how the command looks like for Shellcmd/command prompt (pfsense 2.5.0 / APU2C4)?
With "find / -name 'udpbroadcastrelay'" I could find udpbroadcastrelay in "/usr/local/sbin/".
With Putty and "/usr/local/sbin/udpbroadcastrelay --id 1 --port 5353 --dev igb1 --dev igb1.12 --multicast 224.0.0.251 -s 1.1.1.1 -f > /dev/null" everything works perfectly but not in pfSene (command prompt) itself.

tman222

@itar said in How can I get this UDP relay package for casting across VLANs?:

Hi,

can someone give me a hint how the command looks like for Shellcmd/command prompt (pfsense 2.5.0 / APU2C4)?
With "find / -name 'udpbroadcastrelay'" I could find udpbroadcastrelay in "/usr/local/sbin/".
With Putty and "/usr/local/sbin/udpbroadcastrelay --id 1 --port 5353 --dev igb1 --dev igb1.12 --multicast 224.0.0.251 -s 1.1.1.1 -f > /dev/null" everything works perfectly but not in pfSene (command prompt) itself.

Hi @itar - please take a look at my post above, I think you might be missing the /usr/bin/nohup command as part of the ShellCmd:

https://forum.netgate.com/topic/155698/how-can-i-get-this-udp-relay-package-for-casting-across-vlans/37

Itar

Hi tman222,

thank you very much!

I read your post, but I thought it would also work with "/usr/local/sbin" instead of "/root/udpbroadcastrelay/". Now I copied "udpbroadcastrelay" to root... and it works like a charm

tman222

@itar said in How can I get this UDP relay package for casting across VLANs?:

Hi tman222,

thank you very much!

I read your post, but I thought it would also work with "/usr/local/sbin" instead of "/root/udpbroadcastrelay/". Now I copied "udpbroadcastrelay" to root... and it works like a charm

Hi @Itar - I would have expected it to work from /usr/local/sbin as well as long as you have the /usr/local/nohup and call the executable by ./udpbroadcastrelay if needed (note the ./) The instructions above are bit dated back from when we had to compile the code manually to create the binary vs. installing it as a FreeBSD package.

Itar

Hi tman222,

no, I tried /usr/bin/nohup /usr/local/sbin/udpbroadcastrelay/./udpbroadcastrelay --id 1 --port 5353 --dev igb0 --dev igb1 --multicast 224.0.0.251 -s 1.1.1.1 -f > /dev/null but it didn't work.

Itar

This post is deleted!

tman222

@itar said in How can I get this UDP relay package for casting across VLANs?:

Hi tman222,

no, I tried /usr/bin/nohup /usr/local/sbin/udpbroadcastrelay/./udpbroadcastrelay --id 1 --port 5353 --dev igb0 --dev igb1 --multicast 224.0.0.251 -s 1.1.1.1 -f > /dev/null but it didn't work.

Hmmm - do either of these work?

/usr/bin/nohup /usr/local/sbin/./udpbroadcastrelay --id 1 --port 5353 --dev igb0 --dev igb1 --multicast 224.0.0.251 -s 1.1.1.1 -f > /dev/null

or

/usr/bin/nohup /usr/local/sbin/udpbroadcastrelay --id 1 --port 5353 --dev igb0 --dev igb1 --multicast 224.0.0.251 -s 1.1.1.1 -f > /dev/null

Itar

Ahhhhh,

/usr/bin/nohup /usr/local/sbin/udpbroadcastrelay --id 1 --port 5353 --dev igb0 --dev igb1 --multicast 224.0.0.251 -s 1.1.1.1 -f > /dev/null

is working!

Thanks!

CaptainCathode

Re: How can I get this UDP relay package for casting across VLANs?

So I just came across this thread after trying for over a day to get Sonos clients on my LAN subnet discovering the Sonos devices on an isolated IOT subnet using the PIMD package as a multicast reflector.

IOS clients that had previously been connected when everything was on the same subnet continue to work once the relevant firewall rules were setup, but new clients (Mac, Win10) can't discover the Sonos device.

I've removed PIMD, rebooted and installed the package as per the instructions above. I'm seeing the following error when trying to run the command (as root) with the debug option:

# udpbroadcastrelay --id 1 --port 1900 --dev igb1 --dev igb2 --multicast 239.255.255.250 -d
ID set to 1
Port set to 1900
ID: 1 (DSCP: 1, ToS: 0x04), Port 1900
igb1: 2 / 172.16.10.1 / 172.16.10.255
igb2: 3 / 172.16.20.1 / 172.16.20.255
found 2 interfaces total
IP_ADD_MEMBERSHIP:		172.16.10.1 239.255.255.250
IP_ADD_MEMBERSHIP:		172.16.20.1 239.255.255.250
bind: Address already in use
rcv bind

Not sure what would already be using 239.255.255.250:1900 or how to go about debugging from here.

Any pointers greatly appreciated

Qinn

did you do a ps to check if it is already running?