UDP Broadcast Relay beta package

[marjohn56]

@Franco - Yes, sorry, didn't see your post..  for some reason I appear not to be getting email notifications.

[guest25283]

Shall we release this plugin as stable 1.0 version?

Cheers,
Franco

I just joined this forum, and am planning to switch from pfSense to OPNsense.
I currently have SONOS on a VLAN using PIMD, and this is one of the key requirements for me before switching to OPNsense. Happy to see this being released to a stable version

[franco]

Forgot about this... will be officially released in 20.7.1.


Cheers,
Franco

[guest25283]

Forgot about this... will be officially released in 20.7.1.


Cheers,
Franco

Great news Franco, looking forward

[marjohn56]

Forgot about this... will be officially released in 20.7.1.

Maybe.... 🤞

[franco]

Looks like a "definitively maybe" to me. 

https://github.com/opnsense/plugins/commit/34ce960535

[guest25283]

Now this is devotion! You guys rock .

[abraxxa]

Just migrated my printer to its own vlan and started to use this package successfully to forward MDNS for Bonjour/AirPrint discovery. 

There seems to be only IPv4 support, do you plan adding IPv6 support?

[marjohn56]

I doubt it.

[chelming]

Do I need to add firewall rules to make this work? I added the SSDP and mDNS to UDP Broadcast Relay and I can see my three Roku devices for casting and can select them in the Roku app after about a 7 second delay.

I cannot see any of my chromecast devices.

All of my IOT devices are on the 40_IOT net and my phone is on the 10_Trusted net.

UDP Broadcast Relay setup:


my firewall rules are pretty non-existant and the same on both interfaces:


mDNS Repeater is currently disabled. I tried adding an allow in rule on the 10_Trusted net for all traffic whose source is 40_IOT and that didn't work either.

I can see all the chromecasts, google devices and speaker groups in wireshark from 10_Trusted:
11   11.823222   192.168.10.1   224.0.0.251   MDNS   419   Standard query response 0x0000 PTR Google-Home-Mini-6b0461727bacfded14f5c854c4d4437f._googlecast._tcp.local TXT, cache flush SRV, cache flush 0 0 8009 6b046172-7bac-fded-14f5-c854c4d4437f.local A, cache flush 192.168.40.27

Any ideas?

[TheLinuxGuy]

Do I need to add firewall rules to make this work?

did you figure this out and if FW rules were needed?

[marjohn56]

Yes, you will need rules. There is no way of knowing the address of the server responding an another LAN/VLAN OR the port it will respond on. Therefore you need ideally to have the server at a static address. For example, I use it for Sky, same ports as Sonos, so I have one rule on my IOT VLAN which allows the server to send traffic back to my primary VLAN. As I don't know what port it will use to send back to the client I have to allow all ports from that server, which I have also given a static address.