Hi,
I want to help with the emergency alert DRM exercise. I installed the windows software on a windows server that is on 24x7 but it is not on the same network as the HD HomeRun. The software says to make sure the HD HomeRun is connected to the internet which I believe it is. But, what I feel is that it can't find the device on the local network. Can I tell the software what address to find the HD HomeRun at? Or is my problem different?
Trying to run Emergency Alert software but says it found no devices
-
didyouexpectthat
- Posts: 1
- Joined: Wed Nov 11, 2026 8:27 pm
Re: Trying to run Emergency Alert software but says it found no devices
You need to put it on the same network. I have multiple VLANs and my hdhomerun sits on another VLAN/subnet, but I have a server on that same subnet I run the linux php script from.
Re: Trying to run Emergency Alert software but says it found no devices
Sigh, OK thanks. As you, I have many VLANs/subnets so I can segregate all my different devices depending on their purpose.
-
cyberhiker
- Posts: 5
- Joined: Mon Jan 07, 2008 9:10 pm
- x 1
Re: Trying to run Emergency Alert software but says it found no devices
I have the same issue (IoT devices that need internet access get their own VLAN, internal-only IoT get their own VLAN, sessions to IoT devices can only be initiated from the main VLAN). My TV/HD Flex 4K talk to each other but the HD HomeRun app on the main VLAN and EACapture do not find the device.
Too much effort to reconfigure for this test, unfortunately.
Too much effort to reconfigure for this test, unfortunately.
Re: Trying to run Emergency Alert software but says it found no devices
If your computer has a route to your HDHR across the VLANs, have Claude or GPT edit the Linux script to point directly at the device IP instead of using discovery/broadcast to find it.
I didn't want it to have access to my LAN so I put it in a Docker container and firewall restricted it to the WAN target (Silicondust server) and my HDHR LAN IP. I had to edit the Linux script since my firewall rules and being in a container broke the discovery (mDNS or whatever).
Even if you have a route to reach the HDHR on a different VLAN subnet, the broadcast packets won't cross VLANs unless you have a reflector, which is another option. If you are Windows only that's an option, use a broadcast packet relay to get them to cross the VLANs.
I didn't want it to have access to my LAN so I put it in a Docker container and firewall restricted it to the WAN target (Silicondust server) and my HDHR LAN IP. I had to edit the Linux script since my firewall rules and being in a container broke the discovery (mDNS or whatever).
Even if you have a route to reach the HDHR on a different VLAN subnet, the broadcast packets won't cross VLANs unless you have a reflector, which is another option. If you are Windows only that's an option, use a broadcast packet relay to get them to cross the VLANs.