HDHomeRun any successful cases accross vlans?

Started by FullyBorked, March 04, 2026, 03:18:34 AM

Previous topic - Next topic
Been banging my head on the desk trying to solve this to no resolve. I have an HDHomeRun box in a seperate IoT vlan.  I've installad the udp broadcast relay plugin.  I have a floating firewall rule for UDP port 65001 for IoT and LAN networks and see allowed packets in the log. 

UDP Broacast relay config -

Port: 65001
Relay interface: IoT/LAN
Broadcast address: I've tried all kinds of combos even blank. I see traffic on 255.255.255.255 but I guess I can't use that in the plugin as it fails to start with that.  So what can I should I use here?
Source address: 1.1.1.1

Not sure how to troubleshoot this, I see allowed traffic, I see a single UDP 65001 packet from my computer, then two (return?) packets from the HDHomeRun box both UDP 65001.  But the app seems to not see the traffic. 

I welcome any help getting this figured out if it's possible. 

On UDPBroadcastRelay, leave the source and broadcast blank in your config. Set port as 65001.

Create a floating firewall rule and set the following:

Interfaces: select the same interfaces you put in the UDPBR config.
Protocol: UDP
Source: IP of HDR
Source Port: 65001
Dest: Net option for the network your device running the app is on.  Mine was LAN Net.

Good luck.

March 04, 2026, 04:30:08 PM #2 Last Edit: March 04, 2026, 04:37:52 PM by FullyBorked
Quote from: madj42 on March 04, 2026, 06:49:29 AMOn UDPBroadcastRelay, leave the source and broadcast blank in your config. Set port as 65001.

Create a floating firewall rule and set the following:

Interfaces: select the same interfaces you put in the UDPBR config.
Protocol: UDP
Source: IP of HDR
Source Port: 65001
Dest: Net option for the network your device running the app is on.  Mine was LAN Net.

Good luck.

So I got this to work but slightly different setup.  I left source and broadcast blank in my UDP config.  But then I had to have two floating rules, since the source and destination are  randomized once the 1.1.1.1 is removed from UDP plugin.  This seems odd, I can lock this down a bit with source and dest devices but not sure if this is correct. But it is working now. See screenshot. (or I guess image links don't work?) https://imgshare.cc/fl6hu4ux



Edit: changed these to interface rules instead of floating, since LAN has a destination port of 65001 and random source, then on return IoT has source as 65001 and random destination.  So that seemed to get this to work now.