Periodic blips with my Firewire Gold
I have the following setup:
Verizon FiOS ONT --> Firewire Gold (router mode) --> switch --> eero
Recently, I noticed occasional blips where I lose internet connectivity on my wifi devices and my wired connections. The blips last for a few minutes.
I had two noticeable blips in the last few days. One on Jan 3 around 20:00 and another around Jan 5 around 22:45. I decided to check the logs, and I noticed the following entries in syslog
Jan 3 20:00:45 firewalla systemd[1]: Started FireRouter DNS.
Jan 3 20:01:45 firewalla systemd[1]: Started FireRouter DNS.
Jan 3 20:02:45 firewalla systemd[1]: Started FireRouter DNS.
Jan 3 20:03:48 firewalla systemd[1]: Started FireRouter DNS.
Jan 3 20:05:45 firewalla systemd[1]: Started FireRouter DNS.
...
Jan 5 18:58:54 firewalla systemd[1]: Started FireRouter DNS.
Jan 5 19:03:56 firewalla systemd[1]: Started FireRouter DNS.
Jan 5 19:05:54 firewalla systemd[1]: Started FireRouter DNS.
Jan 5 22:15:07 firewalla systemd[1]: Started FireRouter DNS.
Jan 5 22:36:09 firewalla systemd[1]: Started FireRouter DNS.
Jan 5 22:37:10 firewalla systemd[1]: Started FireRouter DNS.
Jan 5 22:39:08 firewalla systemd[1]: Started FireRouter DNS.
Jan 5 22:43:08 firewalla systemd[1]: Started FireRouter DNS.
Jan 5 22:45:09 firewalla systemd[1]: Started FireRouter DNS.
Jan 5 22:51:49 firewalla systemd[1]: Started FireRouter DNS.
Jan 5 22:51:54 firewalla systemd[1]: Started FireRouter DHCP.
It seems to want to restart the FireRouter DNS more frequently when there is an issue, and connectivity did not return to normal until it has restarted 3-4 times in the short span.
Why is it restarting at all? Memory issues? Or something else? If so, what could it be?
Any help would be greatly appreciated
-
The "FireRouter DNS" service restart usually happens if
1. The local DNS self-check does not get a reply
2. The DNS configuration is changed due to a new rule being applied, or a new domain being learnt and added to a category
Please also check if the upstream WAN DNS is working properly at that time by checking the log file
cat ~/.forever/router*.log | grep "WanConnCheckSensor"
If you see the following output:
Failed to do DNS test using xx.xx.xx.xx on eth0 Command failed: dig -4 +short +time=3 +tries=2 @xx.xx.xx.xx github.com
It usually indicates the DNS server from WAN does not work at that time
-
The grep check returns nothing, but looking at ~/.forever/main.log, i see the following entries
2021-01-05 22:43:02 ERROR Dnsmasq: Failed to resolve all domains on 192.168.146.1.
2021-01-05 22:43:50 ERROR Dnsmasq: Failed to resolve firewalla.encipher.io on 192.168.146.1 ;; connection timed out; no servers could be reached
2021-01-05 22:44:50 ERROR Dnsmasq: Failed to resolve firewalla.encipher.io on 192.168.146.1 ;; connection timed out; no servers could be reached
2021-01-05 22:44:56 ERROR Dnsmasq: Failed to resolve github.com on 192.168.146.1 ;; connection timed out; no servers could be reached
2021-01-05 22:45:02 ERROR Dnsmasq: Failed to resolve google.com on 192.168.146.1 ;; connection timed out; no servers could be reached
2021-01-05 22:45:02 ERROR Dnsmasq: Failed to resolve all domains on 192.168.146.1.
2021-01-05 22:46:50 ERROR Dnsmasq: Failed to resolve firewalla.encipher.io on 192.168.146.1 ;; connection timed out; no servers could be reached
2021-01-05 22:47:50 ERROR Dnsmasq: Failed to resolve firewalla.encipher.io on 192.168.146.1 ;; connection timed out; no servers could be reached
2021-01-05 22:47:57 ERROR Dnsmasq: Failed to resolve github.com on 192.168.146.1 ;; connection timed out; no servers could be reached
2021-01-05 22:49:50 ERROR Dnsmasq: Failed to resolve firewalla.encipher.io on 192.168.146.1 ;; connection timed out; no servers could be reached
2021-01-05 22:49:57 ERROR Dnsmasq: Failed to resolve github.com on 192.168.146.1 ;; connection timed out; no servers could be reached
2021-01-05 22:51:50 ERROR Dnsmasq: Failed to resolve firewalla.encipher.io on 192.168.146.1 ;; connection timed out; no servers could be reached -
Thanks for the feedback. You can send an email to help@firewalla.com to open a support ticket if you would like us to do more troubleshooting.
Please sign in to leave a comment.
Comments
3 comments