Recordings stopped after router reset

[dennis48755]

Hello,

I did a factory reset on my WatchGuard firewall router Saturday and my task to record SNL Saturday night failed. Rat's, it was an especially good one.

Before the reset I looked and did not see any configuration changes I had previously related to the HDHomeRun.

In my NAS HDHomeRun folder, the logs (since the reset) contain...

HDHomeRun RECORD 20200907 Linux 995852B7-1BE7-436C-8F7C-EC9DD0D6D6EC
20201210-00:00:00 Recording: transition from Live channel 213 ab70f56a to Live channel 213 07909bf1
20201210-00:00:00 Recording: recording stated Live channel 213 07909bf1
20201210-00:00:01 Recorded: directory /data/HDHomeRun/ with 42 subdirs and 0 recordings
20201210-00:00:59 Recording: sending discover using local ip 192.168.92.36
20201210-00:00:59 Recording: sending discover using local ip 192.168.92.36
20201210-00:01:00 Recording: discover response from 995852B7-1BE7-436C-8F7C-EC9DD0D6D6EC http://192.168.92.36:35075
20201210-00:01:00 Recording: discover response from 13101B6C http://192.168.92.208:80
20201210-00:01:00 Recorded: recorded sync to record-api.hdhomerun.com
20201210-00:01:00 Recording: event download from record-api.hdhomerun.com
20201210-00:01:00 Recording: 13101B6C lineup request success (found 540 channels)
20201210-00:01:15 Recording: myhdhomerun_files webclient error 2 dns failed
20201210-00:01:15 Recorded: recorded sync failed
20201210-00:01:42 Status: Resource: nbk=1 dmk=1770
20201210-00:01:42 Status: Disk read: MB=56 MB/s=214 worst=1
20201210-00:01:42 Status: Disk write: MB=56 MB/s=37 worst=470
20201210-00:01:42 Status: Streaming: Live channel 213 to 192.168.92.7 (5128MB)
20201210-00:01:45 Recording: myhdhomerun_record webclient error 2 dns failed
20201210-00:01:45 Recording: event download failed
20201210-00:01:45 Recording: disk space available = 826GB
20201210-00:01:45 Recording: current time = Thu Dec 10 00:01:45 2020 (correction of 0s)
20201210-00:01:45 Recording: no timer events planned

Do I have to make changes to the router?

I do have DNS Servers 1.1.1.1 & 8.8.8.8 defined

Dennis

[dennis48755]

nickk,

Could you please look at Ticket #: #142894 regarding this issue.

Would you consider the responses to my inquires good support? I don't.

Dennis

Added: I have the ability to get WatchGuard technical support involved, but I need information from SiliconDust as to protocols, ports, addresses, etc to ask them to help me.

[NedS]

nickk,

Could you please look at Ticket #: #142894 regarding this issue.

Would you consider the responses to my inquires good support? I don't.

Dennis

Added: I have the ability to get WatchGuard technical support involved, but I need information from SiliconDust as to protocols, ports, addresses, etc to ask them to help me.

You've been speaking with me in that support ticket. You added a firewall appliance to your network and things stopped working. I've informed you that something on your network is preventing the HDHomeRun and DVR software form being able to communicate outward to our servers. There are no ports to forward. This is outgoing communication from the HDHomeRun to our servers, not incoming communication. Whatever firewall you've installed is most likely doing that. It is blocking the HDHomeRun from the internet.

[dddcooke]

what is the address that HDHR device is looking for IP or SND name please. I too just put a new FW in this week and having the same issue.

thanks!
Dave

[dennis48755]

Dave,

[removed by moderator]

My problem turned out to be that my NAS could not communicate with any DNS servers.

I was under the misimpression that the gateway address should be one of the defined DNS Servers. Normally with my static addressed devices, I would define my gateway as one DNS servers and Googles 8.8.8.8 as the secondary. But when I configured my NAS I accidentally omitted the second entry and had only my gateway address defined.

This did not cause a problem with my previous FW (Netgear FVS336Gv3) because it forwarded the DNS server request to the WAN/ISP.

However, WatchGuard does not, not without changing a setting that defaults to off. I can tell you where this setting is if this appears to be your issue.

But instead of enabling this option, I chose to correct the settings in my devices, and have changed all my devices to have 8.8.8.8 & 1.1.1.1 DNS servers defined.

Dennis