I'm starting on linux and trying to connect to my HDHR Quattro (not sure that's the full name, ATSC1.0 x 4, model hdhomerun5_atsc). I was able to make a connection directly using its IP address and determine its ID, but the "hdhomerun_config discover" command does not find it, and using the ID that I found in hdhomerun_config commands also doesn't work.
I moved to windows and installed the HDHR software (not the app store stuff) to try to check/upgrade the firmware. It installs fine, but at startup it also fails to find the device. All my devices and computers are on the same /24 subnet, no fancy VLANs or anything else is going on. I can ping the device fine and address it directly from the command line. Is there any way to "nudge" the firmware upgrade software towards the actual device IP so it can work its magic?
Discovery not working
Re: Discovery not working
hdhomerun_config ip.address.of.hdhomerun upgrade /path/to/firmware.bin
Substitute actual things, of course. Longer term, check the firewall. Discovery of the HDHomeRun works by sending out a broadcast to the network, which the HDHomeRun then responds to. The Windows Firewall is smart enough to recognize that the response is associated with the broadcast that went out and automatically allows it through, while Linux's firewall is not that smart. Best to allow all incoming traffic from the IP or MAC address of the HDHomeRun, and if you use IP address, make sure to reserve it in your router/DHCP server so it doesn't change if the power goes out or something.
On the Windows side, any third-party firewalls or VPNs in use? Third party firewalls are not always as smart about the above as the Windows Firewall is (or have the option to allow it or not and may default to not), while most VPNs block access to the local network while connected as an added layer of security.
Substitute actual things, of course. Longer term, check the firewall. Discovery of the HDHomeRun works by sending out a broadcast to the network, which the HDHomeRun then responds to. The Windows Firewall is smart enough to recognize that the response is associated with the broadcast that went out and automatically allows it through, while Linux's firewall is not that smart. Best to allow all incoming traffic from the IP or MAC address of the HDHomeRun, and if you use IP address, make sure to reserve it in your router/DHCP server so it doesn't change if the power goes out or something.
On the Windows side, any third-party firewalls or VPNs in use? Third party firewalls are not always as smart about the above as the Windows Firewall is (or have the option to allow it or not and may default to not), while most VPNs block access to the local network while connected as an added layer of security.