UDP Broadcast Relay

[Greelan]

There are other options, I could remove some of the info from the entry, question is, what should stay and what should be hidden.

I think Use ID as TTL could probably be removed, and shortening the headings for other entries would also help (eg Port rather than Listen Port). What about also the “dynamic display” approach that eg the firewall rules adopt - items are variably hidden based on the width of the display, but not removed from the list outright so that they still appear if the display is wide enough?

[marjohn56]

I've done that on my local version already, changed Listen Port etc.. also hidden Source Address. I've just done a clean install on my test machine, it's been a while since it was clean - now I'm struggling to switch to the dev branch.. something odd is going on.

[NKnusperer]

Hi guys, does someone know how do I get device discovery working when using a Samsung TV?
When I'am in the same subnet I can cast from Chrome or the YouTube app to "[TV] Samsung".

Based on this article [1] I assumed that DIAL is used for this, but enabling SSDP has no effect.

Any ideas?

[1] https://blog.oakbits.com/google-cast-protocol-discovery-and-connection.html

EDIT:
Using this script [2] devices in the same subnet are discovered but not in another VLAN with the SSDP relay (which is used by the script).

[2] https://gist.github.com/jcarbaugh/e08dcfe61ece0e7eea12

[klipsch]

Just wanted to thank the community and @bertoforth / @marjohn56 for this great plugin/service.

Have been able to successfully use 7 VLANs of segregation - chromecasts, yamaha receivers, Anthem pre/pro, BubbleUPnP, unRaid, server/services, HD Homerun, cameras, etc. all logically separated in their corresponding VLANs created for my purposes - while having the convenience of being able to use my primary wireless LAN to cast, discover, stream, etc.

The UDP Broadcast Relay with point/click/type has really made things easy and prevented me from going down the scripted socat route.

Thank you again

[sorano]

Just wanted to thank the community and @bertoforth / @marjohn56 for this great plugin/service.

Have been able to successfully use 7 VLANs of segregation - chromecasts, yamaha receivers, Anthem pre/pro, BubbleUPnP, unRaid, server/services, HD Homerun, cameras, etc. all logically separated in their corresponding VLANs created for my purposes - while having the convenience of being able to use my primary wireless LAN to cast, discover, stream, etc.

The UDP Broadcast Relay with point/click/type has really made things easy and prevented me from going down the scripted socat route.

Thank you again

Awesome, would you mind sharing your config for HD Homerun?

[thereturn]

Just want to say thank you for this app, got airplay working across VLANs, i had to leave the source address in the plugin empty though it would not show my sonos via airplay with 1.1.1.1 or 1.1.1.2.

[marjohn56]

Glad it's working for you. Sadly I have had no time over the last few months to even look at Opnsense, in fact I've only just updated the system to 21.7 I've been that busy. Fortunately it's very stable and just carries on regardless.

[dave]

anyone figured out how to get Win10 miracast working?

I've got the relay running and can see it in action using tcpdump.
I've set rules on both my LAN and main WLAN (which is a vlan) allowing any traffic in both directions (cause i'm lazy).

Win10 can't see my Roku (which does have all the necessary services enabled)....?

Win10's on eth, but apparently 10's supported eth to wlan miracast sinced 1703...

[dave]

ignore me:  https://docs.microsoft.com/en-us/surface-hub/miracast-over-infrastructure

[AegeanDad]

First, THANK YOU!

I have two homes, both running OPNSense. Site-to-Site WireGuard VPN. Both sites have their own respective LAN and WG interfaces set up. Both sites have gateways set up for the WireGuard traffic (GWs are required and must be designated as "Far Gateways" for selective routing). FW rules on both sides allow all from their respective WG interfaces. Both sites have "Disable Routes" enabled in the Local Configuration; all routing is selectively handled via firewall rules based on either source or destination IPs. Outbound NAT is set up on both sides to assign the WG interface IP to outgoing packets. Endpoint Allowed IPs on both sides have 0.0.0.0/0.

So far, all the discussions in this forum pertain to relaying UDP broadcasts across multiple VLANs. Is there any reason why this wonderful plugin would not work when one of the interfaces is a VPN interface, and specifically WireGuard? Is there any specific configuration needed to make it work? 

Also, why do some relay setup lines appear in yellow (vs. Green) in OPNSense? Yellow ones show their services inactive on the dashboard. I assume incorrect configuration of some sort but can't tell what is wrong with them.

[bead16]

I posted a variation of this on reddit, but thought I might get a bit more traction here.

I have udp broadcast relay setup and working. As a new user to opnsense I was pleasantly surprised how easy it was to get up and running.

Everything was working great until I tried to cast from netflix on my android. Casting from all other apps on my phone is fine.

It appears that netflix is using ipv6 for mDNS on more recent chromecasts (my gen1 chromecast is discovered by netflix ok). As udp broadcast relay doesn't support ipv6 at the moment, I have to connect to my IoT vlan to cast netflix which doesn't go down well with the family.

I've tried blocking and rejecting all ipv6 udp to see if netflix would fall back to ipv4, but no joy. All of my devices are connected via ipv4, so don't mind nuking ipv6 for now.

Is ipv6 support on the roadmap for udp broadcast relay?

Any other suggestions of things I can try?

TIA

[mimugmail]

Can you open an issue in GitHub about V6 support please? I know the plugin allows only v4 but unsure about the daemon itself

[bead16]

Thanks mimugmail. Assuming you meant here: https://github.com/marjohn56/udpbroadcastrelay, all done.

[mimugmail]

opnsense/plugins

[mcbatranu]

First of all, thank you for this plugin!
I managed to install it offline after a lot of searching for the source files. I am new to OPNSense and to FreeBSD in general and finding those 2 files was not easy for me. 
The issue that I have now is that in my case, I need to use the broadcast address 255.255.255.255 as it is hard-coded by the application, but when I try to set this address in the plugin, the plugin stops after the Save button is pressed and does not start anymore even if I try to start it from the System > Diagnostics > Services area.
In the General log:
/usr/local/etc/rc.d/os-udpbroadcastrelay: WARNING: failed to start osudpbroadcastrelay

It looks like this address is not supported and it may be a value validity check inside the plugin that does not expect this one and gives an error.
Is there a reason why this address is not accepted by the plugin, or maybe, are there some other settings outside this plugin that could cause this issue?