Asus RT-AX86S Dropping Connection at the same time every day

[ryfoo]

I have an Asus RT-AX86S running 388.2_2 that briefly (1-2 minutes duration) drops connection quite regularly, might be every day. If i'm honest i don't think it's related to the firmware and i suspect it's a configuration issue (i.e. my fault).

Here's what going on in the log (I have noticed that the time was set incorrectly - it was an hour out - i've rectified that now):

May 10 08:48:11 ntpd: Initial clock set
May 10 08:48:11 miniupnpd[1954]: HTTP listening on port 58653
May 10 08:48:11 miniupnpd[1954]: Listening for NAT-PMP/PCP traffic on port 5351
May 10 08:48:11 rc_service: udhcpc_wan 1778:notify_rc stop_samba
May 10 08:48:11 rc_service: udhcpc_wan 1778:notify_rc start_samba
May 10 08:48:11 rc_service: waitting "stop_samba" via udhcpc_wan ...
May 10 08:48:11 rc_service: ntpd_synced 1952:notify_rc restart_diskmon
May 10 08:48:11 rc_service: waitting "stop_samba" via udhcpc_wan ...
May 10 08:48:11 Samba_Server: smb daemon is stopped
May 10 08:48:12 rc_service: udhcpc_wan 1778:notify_rc stop_samba
May 10 08:48:12 rc_service: waitting "start_samba" via udhcpc_wan ...
May 10 08:48:12 dnsmasq[1514]: exiting on receipt of SIGTERM
May 10 08:48:12 dnsmasq[1963]: started, version 2.89 cachesize 1500
May 10 08:48:12 dnsmasq[1963]: asynchronous logging enabled, queue limit is 5 messages
May 10 08:48:12 dnsmasq-dhcp[1963]: DHCP, IP range 192.168.102.2 -- 192.168.102.254, lease time 1d
May 10 08:48:12 dnsmasq-dhcp[1963]: DHCP, IP range 192.168.101.2 -- 192.168.101.254, lease time 1d
May 10 08:48:12 dnsmasq-dhcp[1963]: DHCP, IP range 192.168.1.10 -- 192.168.1.254, lease time 1d
May 10 08:48:12 dnsmasq[1963]: read /etc/hosts - 22 names
May 10 08:48:12 dnsmasq[1963]: using nameserver 109.249.185.133#53
May 10 08:48:12 dnsmasq[1963]: using nameserver 109.249.185.134#53
May 10 08:48:12 dnsmasq[1963]: using nameserver 109.249.185.133#53 for domain local
May 10 08:48:12 dnsmasq[1963]: using nameserver 109.249.185.134#53 for domain local
May 10 08:48:12 dnsmasq[1963]: using nameserver 109.249.185.133#53
May 10 08:48:12 dnsmasq[1963]: using nameserver 109.249.185.134#53
May 10 08:48:12 dnsmasq[1963]: using nameserver 109.249.185.133#53 for domain local
May 10 08:48:12 dnsmasq[1963]: using nameserver 109.249.185.134#53 for domain local
May 10 08:48:13 kernel: cfg80211: Calling CRDA to update world regulatory domain
May 10 08:48:13 rc_service: udhcpc_wan 1778:notify_rc start_samba
May 10 08:48:13 rc_service: waitting "stop_samba" via udhcpc_wan ...
May 10 08:48:13 Samba_Server: smb daemon is stopped
May 10 08:48:14 dhcp_client: bound 10.46.218.201/255.255.255.254 via 10.46.218.200 for 864000 seconds.
May 10 08:48:14 dnsmasq[1963]: exiting on receipt of SIGTERM
May 10 08:48:14 dnsmasq[1978]: started, version 2.89 cachesize 1500
May 10 08:48:14 dnsmasq[1978]: asynchronous logging enabled, queue limit is 5 messages
May 10 08:48:14 dnsmasq-dhcp[1978]: DHCP, IP range 192.168.102.2 -- 192.168.102.254, lease time 1d
May 10 08:48:14 dnsmasq-dhcp[1978]: DHCP, IP range 192.168.101.2 -- 192.168.101.254, lease time 1d
May 10 08:48:14 dnsmasq-dhcp[1978]: DHCP, IP range 192.168.1.10 -- 192.168.1.254, lease time 1d
May 10 08:48:14 dnsmasq[1978]: read /etc/hosts - 22 names
May 10 08:48:14 dnsmasq[1978]: using nameserver 109.249.185.133#53
May 10 08:48:14 dnsmasq[1978]: using nameserver 109.249.185.134#53
May 10 08:48:14 dnsmasq[1978]: using nameserver 109.249.185.133#53 for domain local
May 10 08:48:14 dnsmasq[1978]: using nameserver 109.249.185.134#53 for domain local
May 10 08:48:14 dnsmasq[1978]: using nameserver 109.249.185.133#53
May 10 08:48:14 dnsmasq[1978]: using nameserver 109.249.185.134#53
May 10 08:48:14 dnsmasq[1978]: using nameserver 109.249.185.133#53 for domain local
May 10 08:48:14 dnsmasq[1978]: using nameserver 109.249.185.134#53 for domain local
May 10 08:48:15 disk_monitor: Finish
May 10 08:48:15 disk_monitor: be idle
May 10 08:48:16 kernel: cfg80211: Exceeded CRDA call max attempts. Not calling CRDA
May 10 08:48:42 crond[1522]: time disparity of 2636863 minutes detected
May 10 08:49:15 wlceventd: wlceventd_proc_event(530): eth6: Auth 54:2A:1B:FC:42:C6, status: Successful (0), rssi:-55
May 10 08:49:15 wlceventd: wlceventd_proc_event(559): eth6: Assoc 54:2A:1B:FC:42:C6, status: Successful (0), rssi:-55
May 10 08:49:15 hostapd: eth6: STA 54:2a:1b:fc:42:c6 IEEE 802.11: associated
May 10 08:49:15 hostapd: eth6: STA 54:2a:1b:fc:42:c6 RADIUS: starting accounting session 290487C7D721BCF0
May 10 08:49:15 hostapd: eth6: STA 54:2a:1b:fc:42:c6 WPA: pairwise key handshake completed (RSN)
May 10 08:49:19 wlceventd: wlceventd_proc_event(530): eth6: Auth 00:0E:58:C4:57:92, status: Successful (0), rssi:-86
May 10 08:49:19 hostapd: eth6: STA 00:0e:58:c4:57:92 IEEE 802.11: associated
May 10 08:49:19 wlceventd: wlceventd_proc_event(559): eth6: Assoc 00:0E:58:C4:57:92, status: Successful (0), rssi:-86
May 10 08:49:19 hostapd: eth6: STA 00:0e:58:c4:57:92 RADIUS: starting accounting session 43859A951739F4A1
May 10 08:49:19 hostapd: eth6: STA 00:0e:58:c4:57:92 WPA: pairwise key handshake completed (RSN)

 

[ColinTaylor]

It's probably an ISP issue but we'd need to see the log prior to this point in time.

 

[ryfoo]

Here's a chunk of the log from before, it's weird because it jumps from 10th may to 5th of may back to 10th again.

 

[ColinTaylor]

5th May 2018 is the default date the router has when it powers on and before it's been able to obtain the correct date and time from the internet.

Your router rebooted. There is no indication that it was manually/automatically rebooted or that it crashed, so it appears to have been powered off for a couple of minutes. Check your power cables.

 

[ryfoo]

5th May 2018 is the default date the router has when it powers on and before it's been able to obtain the correct date and time from the internet.

Your router rebooted. There is no indication that it was manually/automatically rebooted or that it crashed, so it appears to have been powered off for a couple of minutes. Check your power cables.

Thanks Colin. That's really interesting and makes sense from a behaviour perspective (with a few things).

 

[Viktor Jaep]

Thanks Colin. That's really interesting and makes sense from a behaviour perspective (with a few things).

You may also want to invest in an inexpensive UPS battery backup... putting your router on this (as well as your modem) will save you a lot of grief if your grid suffers from momentary spikes/brownouts...