Posted: Sat Apr 17, 2021 6:48 Post subject: R7000 : Hangs every 12 hours
My r7000 (with firmware : DD-WRT v3.0-r45955 std (03/09/21)) appears to hang every 12 hours. This is AFTER I introduced Pfsense into my network. A reboot fixes the issue temporarily.
Ive tried defaulting the firmware to its factory setting but the issue still persists.
Note : If I connect my ISP`s cable directly to the R7000, I dont see any issues.
My Current Setup at home
Internet ---> Pfsense ---> DDwrt ---> Clients
I followed some instructions on how to disable WAN, assign it to the switch, disable the firewall, disable DHCP, etc
Post hanging you would see symptoms like:
1) Pings stop working
2) Wifi and LAN dont work
3) GUI is in-accessible
I read somewhere that it might be possible that my R7000 is overwhelmed by the traffic coming from pfsense, and I`m not sure how to remedy that. I did also happen to read an article about increasing the Maximum ports, and decreasing the timeouts for TCP.
These are my current settings:
TCP Congestion Control : westwood
Maximum Ports : 32768
(Default: 4096, Range: 256 - 65536)
I enabled sysLog to see if I could catch anything (Dropped or Refused connections). But around the times it hangs, I dont see anything useful that would point to a cause.
Just a bunch of these that could mean anything:
Apr 17 11:20:19 daemon.err ntpclient[3483]: Failed resolving address to hostname 2.pool.ntp.org: Try again
Apr 17 11:20:19 daemon.err ntpclient[3483]: Failed resolving server 2.pool.ntp.org: Network is down
Can anyone please guide me as to how to diagnose the problem and fix it?
If you setup as a WAP the router is acting as a dumb switch so if setup correctly it is unlikely it is overpowered.
--> I thought so too, which is why I didnt mess around with any of the default settings
To be clear after resetting do not restore from a backup file, put settings in manually
Hi Egc, The router crashed again last night, close to midnight. Same symptoms as before.
Any leads on logs to go through? Curious to see whats causing it. The Syslogs strangely dont seem to have anything useful. And the dates (though NTP is setup correctly) seem incorrect or missing.
After rebooting the router, I`ve observed something strange : The router now only crashes every 24 hours....exactly at midnight. Step in the right direction I feel.
I`d still like to know if there are any logs I could setup on a remote server for this. After every reboot I notice the logs for the previous day vanish. Would be interesting to see what makes it hang.
Here are some of the logs from syslog watcher: (Older entries start from the bottom)
21-04-2021 00:00 Info _evalpid:ifconfig br0 down
21-04-2021 00:00 Info redial : ppp redial daemon trying to stop
21-04-2021 00:00 Info ntpclient : Network Time Protocol client trying to stop
21-04-2021 00:00 Info sputnik : daemon trying to stop
21-04-2021 00:00 Info listen : activity daemon trying to stop
21-04-2021 00:00 Info pptp : daemon trying to stop
21-04-2021 00:00 Info pppd : daemon trying to stop
21-04-2021 00:00 Debug route_del: if: dst: gw: (null) mask: (null)
21-04-2021 00:00 Info bpalogin : bpalogin trying to stop
21-04-2021 00:00 Info listen : connectivity listener trying to stop
21-04-2021 00:00 Info xl2tpd : daemon trying to stop
21-04-2021 00:00 Info pppd : daemon trying to stop
21-04-2021 00:00 Debug route_del: if: dst: gw: (null) mask: (null)
21-04-2021 00:00 Info pppd : pppoe daemon trying to stop
21-04-2021 00:00 Info pppd : pppoe process trying to stop
21-04-2021 00:00 Info _evalpid:wrtbwmon setup /tmp/bw.db
21-04-2021 00:00 Info _evalpid:rm -f /tmp/.fw_lock
21-04-2021 00:00 Info sfe : shortcut forwarding engine successfully started
21-04-2021 00:00 Alert fast-classifier: registered
21-04-2021 00:00 Alert fast-classifier (PBR safe v2.1.6b): starting up
21-04-2021 00:00 Debug system2:echo 1 > /sys/skip_to_bridge_ingress
21-04-2021 00:00 Info _evalpid:insmod fast-classifier
21-04-2021 00:00 Info _evalpid:insmod shortcut-fe-ipv6
21-04-2021 00:00 Info _evalpid:insmod shortcut-fe
21-04-2021 00:00 Info _evalpid:rmmod xt_ipp2p
21-04-2021 00:00 Info _evalpid:rmmod ipt_ipp2p
21-04-2021 00:00 Info _evalpid:rmmod xt_layer7
21-04-2021 00:00 Info _evalpid:rmmod ipt_layer7
21-04-2021 00:00 Info _evalpid:rmmod ipt_webstr
21-04-2021 00:00 Info _evalpid:iptables -t mangle -F
21-04-2021 00:00 Info _evalpid:iptables -t nat -F
21-04-2021 00:00 Info _evalpid:iptables -F
21-04-2021 00:00 Info sfe : shortcut forwarding engine successfully stopped
21-04-2021 00:00 Info _evalpid:rmmod shortcut-fe
21-04-2021 00:00 Info _evalpid:rmmod shortcut-fe-ipv6
21-04-2021 00:00 Alert fast-classifier: shutting down
21-04-2021 00:00 Info _evalpid:rmmod fast-classifier
21-04-2021 00:00 Info _evalpid:iptables -t raw -F
Lookks like a bunch of services going into a stop state. Dont see anything in the prior logs. Ill paste those below anyway, if anyone can see something I cannot:
20-04-2021 23:59 Info dhcpfwd : dhcp forwarder trying to stop
20-04-2021 23:59 Info _evalpid:/sbin/service wan stop
20-04-2021 23:53 Info _evalpid:filtersync
20-04-2021 23:53 Info cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19(ntp2.m-online.net) 88.99.174.22(static.88-99-174-22.clients.your-server.de))
20-04-2021 23:53 Info Time set from 212.18.3.19(ntp2.m-online.net) [212.18.3.19(ntp2.m-online.net)].
20-04-2021 23:53 Debug Connecting to 212.18.3.19(ntp2.m-online.net) [212.18.3.19(ntp2.m-online.net)] ...
20-04-2021 23:53 Notice Network up resolved address to hostname 212.18.3.19(ntp2.m-online.net)
20-04-2021 23:53 Error Failed resolving server 2.pool.ntp.org: Network is down
20-04-2021 23:53 Error Failed resolving address to hostname 2.pool.ntp.org: Try again
20-04-2021 23:53 Info _evalpid:ntpclient 2.pool.ntp.org 212.18.3.19(ntp2.m-online.net) 88.99.174.22(static.88-99-174-22.clients.your-server.de)
20-04-2021 23:53 Info ntpclient : Network Time Protocol client trying to stop
20-04-2021 23:53 Info _evalpid:/sbin/service ntpc stop
20-04-2021 23:53 Info _evalpid:stopservice ntpc -f
20-04-2021 22:53 Info _evalpid:filtersync
20-04-2021 22:53 Info cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19(ntp2.m-online.net) 88.99.174.22(static.88-99-174-22.clients.your-server.de))
20-04-2021 22:53 Info Time set from 212.18.3.19(ntp2.m-online.net) [212.18.3.19(ntp2.m-online.net)].
20-04-2021 22:53 Debug Connecting to 212.18.3.19(ntp2.m-online.net) [212.18.3.19(ntp2.m-online.net)] ...
20-04-2021 22:53 Notice Network up resolved address to hostname 212.18.3.19(ntp2.m-online.net)
20-04-2021 22:53 Error Failed resolving server 2.pool.ntp.org: Network is down
20-04-2021 22:53 Error Failed resolving address to hostname 2.pool.ntp.org: Try again
20-04-2021 22:53 Info _evalpid:ntpclient 2.pool.ntp.org 212.18.3.19(ntp2.m-online.net) 88.99.174.22(static.88-99-174-22.clients.your-server.de)
20-04-2021 22:53 Info ntpclient : Network Time Protocol client trying to stop
20-04-2021 22:53 Info _evalpid:/sbin/service ntpc stop
20-04-2021 22:53 Info _evalpid:stopservice ntpc -f
I checked the gateway logs on the pfsense box, at 12 Midnight. No sign of the Network going down. Its just strange that now it stops working on the dot of 12AM.
Its not a reboot really. The ddwrt router just hangs.
I tried the KeepALive option earlier, not really reliable.
Joined: 16 Nov 2015 Posts: 6447 Location: UK, London, just across the river..
Posted: Wed Apr 21, 2021 13:50 Post subject:
Do you by any chance, have a name for NTP server in the NTP time box..? Use IP instead of name or just try some other DDWRT NTP zone selection...if not use like Cloudflare NTP IP 162.159.200.123 or google NTP IP 216.239.35.8
I had something funny like this in the past, the NTP i used was sending a reboot signal at 0:00h or god knows what and how, but my router was doing the same crap...changed to goggle NTP time IP and happy days...
The other thing that comes to my mind is, if you have a cron script or other scripts that mess up with time...somehow...
egc wrote:
I would just do from CLI :
Code:
nvram erase && reboot
and setup manually, starting with only minimal settings according to the wiki
I do support that option too.. _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55819 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
@Alozaros : Thats very interesting ..... Did you figure it out through a set of logs?
I `m going to fill the "Server IP/Name" field with a Google NTP IP and see what happens. Followed by disabling it completely (just in case the prior step does nothing). Eh, besides, the ddwrt routers only an AP atm, so I dont see any harm. Based on what you experienced.....and those constant NTP errors you guys saw in the logs, this might be worth trying.