Bad router vs bad cable modem

[Mario64]

For the past 2-3 weeks at least once or twice per day my internet has gone down. By that I mean my devices stop responding and my AC-3100 status page shows Internet "disconnected". Even before COVID I work from home so stable internet is an absolute must for me.

I'm trying to determine if the problem is my AC-3100 or my cable modem. It's a SB-6183. I tried swapping in my old SB-6121 but still had the problem. This makes me suspect it's my router. Plus, the lights on my cable modem stay on so that seems to indicate the modem isn't losing connection.

Are there any keywords or phrases I can search for in the router system log which may point to which device is actually at fault here?

Thanks in advance for any help

 

[dosborne]

What firmware version are you running in the Asus router? When was the last time you reset it and reconfigured it manually? Is the firmware in your cable modem also up to date? Just to rule it out, have you tried a good quality, commercial, ethernet cable between the two devices?

 

[Mario64]

What firmware version are you running in the Asus router? When was the last time you reset it and reconfigured it manually? Is the firmware in your cable modem also up to date? Just to rule it out, have you tried a good quality, commercial, ethernet cable between the two devices?

AC-3100 firmware is 3.0.0.4.385_20457 which was just updated a few days ago. This issue preceded the update though. I had hoped that would fix it. Did not do a factory reset.
Modem firmware is controlled by Spectrum so I cannot touch it. I'm using the ethernet cable which came with the modem IIRC. I could change it out I suppose.

Oh and by the way, router logs will be useless. Since updating all I see now is this spam message over and over (MAC address redacted):
Apr 20 22:58:04 syslog: WLCEVENTD wlceventd_proc_event(466): eth2: Deauth_ind XX:XX:XX:XX:XX:XX, status: 0, reason: Class 3 frame received from nonassociated station (7)

 

[L&LD]

I would suggest an M&M Config and ideally a Nuclear Reset (please follow the link in my signature below) after flashing RMerlin v384.16_0 rather than continuing using stock.

 

[shoman94]

Why can't you just disconnect the router from the modem when it happens and connect a PC directly to see if it works? Then you know its the router for certain.

 

[Mario64]

Why can't you just disconnect the router from the modem when it happens and connect a PC directly to see if it works? Then you know its the router for certain.

Assuming the modem will provide the PC an IP address without a reboot of either device that would be an idea I suppose. However, today Spectrum came by and replaced the entire line from pole to my house and just inside. So far the numerous Uncorrectable errors I was seeing on the SB6183 are gone. I'm hopeful this was the fix but if not will start looking more closely at the AC-3100

 

[shoman94]

Assuming the modem will provide the PC an IP address without a reboot of either device that would be an idea I suppose. However, today Spectrum came by and replaced the entire line from pole to my house and just inside. So far the numerous Uncorrectable errors I was seeing on the SB6183 are gone. I'm hopeful this was the fix but if not will start looking more closely at the AC-3100

Could you see those errors in the log?

Sent from my Pixel 4 XL using Tapatalk

 

[Mario64]

Could you see those errors in the log?

Sent from my Pixel 4 XL using Tapatalk

This is what the router logs show when it goes down. Although you see WAN connection restored it really wasn't. Usually a full reboot of modem and router was required to fix this.

Apr 15 13:53:10 WAN Connection: ISP's DHCP did not function properly.
Apr 15 13:53:10 DualWAN: skip single wan wan_led_control - WANRED off
Apr 15 13:53:11 nat: apply redirect rules
Apr 15 13:53:15 WAN Connection: Ethernet link down.
Apr 15 13:53:25 WAN Connection: Ethernet link up.
Apr 15 13:53:25 rc_service: wanduck 260:notify_rc restart_wan_if 0
Apr 15 13:53:29 rc_service: udhcpc 28650:notify_rc start_firewall
Apr 15 13:53:30 miniupnpd[14533]: shutting down MiniUPnPd
Apr 15 13:53:31 wan: finish adding multi routes
Apr 15 13:53:31 rc_service: udhcpc 28650:notify_rc stop_upnp
Apr 15 13:53:31 rc_service: waitting "start_firewall" via udhcpc ...
Apr 15 13:53:31 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Apr 15 13:53:31 wan: finish adding multi routes
Apr 15 13:53:31 WAN Connection: ISP's DHCP did not function properly.
Apr 15 13:53:31 miniupnpd[28734]: version 1.9 started
Apr 15 13:53:31 miniupnpd[28734]: HTTP listening on port 34036
Apr 15 13:53:32 miniupnpd[28734]: Listening for NAT-PMP/PCP traffic on port 5351
Apr 15 13:53:32 rc_service: udhcpc 28650:notify_rc start_upnp
Apr 15 13:53:32 rc_service: waitting "stop_upnp" via udhcpc ...
Apr 15 13:53:32 miniupnpd[28734]: shutting down MiniUPnPd
Apr 15 13:53:33 miniupnpd[28769]: version 1.9 started
Apr 15 13:53:33 miniupnpd[28769]: HTTP listening on port 56425
Apr 15 13:53:33 miniupnpd[28769]: Listening for NAT-PMP/PCP traffic on port 5351
Apr 15 13:53:35 WAN Connection: WAN was restored.
Apr 15 13:53:51 BWDPI: fun bitmap = 83
Apr 15 13:53:51 A.QoS: qos_count=0, qos_check=0
Apr 15 13:53:54 rc_service: udhcpc 28650:notify_rc start_firewall
Apr 15 13:53:55 dhcp client: bound 192.168.100.11 via 192.168.100.1 during 20 seconds.
Apr 15 13:53:55 miniupnpd[28769]: shutting down MiniUPnPd
Apr 15 13:53:56 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Apr 15 13:53:57 miniupnpd[29833]: version 1.9 started
Apr 15 13:53:57 miniupnpd[29833]: HTTP listening on port 50107
Apr 15 13:53:57 miniupnpd[29833]: Listening for NAT-PMP/PCP traffic on port 5351
Apr 15 13:53:59 rc_service: udhcpc 30377:notify_rc start_firewall
Apr 15 13:54:00 miniupnpd[29833]: shutting down MiniUPnPd
Apr 15 13:54:01 wan: finish adding multi routes
Apr 15 13:54:01 rc_service: udhcpc 30377:notify_rc stop_upnp
Apr 15 13:54:01 rc_service: waitting "start_firewall" via udhcpc ...
Apr 15 13:54:01 wan: finish adding multi routes
Apr 15 13:54:01 WAN Connection: ISP's DHCP did not function properly.
Apr 15 13:54:01 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Apr 15 13:54:02 DualWAN: skip single wan wan_led_control - WANRED off
Apr 15 13:54:02 nat: apply redirect rules
Apr 15 13:54:02 miniupnpd[30713]: version 1.9 started
Apr 15 13:54:02 miniupnpd[30713]: HTTP listening on port 43051
Apr 15 13:54:02 miniupnpd[30713]: Listening for NAT-PMP/PCP traffic on port 5351
Apr 15 13:54:03 rc_service: udhcpc 30377:notify_rc start_upnp
Apr 15 13:54:03 rc_service: waitting "stop_upnp" via udhcpc ...
Apr 15 13:54:03 miniupnpd[30713]: shutting down MiniUPnPd
Apr 15 13:54:04 miniupnpd[30888]: version 1.9 started
Apr 15 13:54:04 miniupnpd[30888]: HTTP listening on port 58829
Apr 15 13:54:04 miniupnpd[30888]: Listening for NAT-PMP/PCP traffic on port 5351
Apr 15 13:54:05 WAN Connection: WAN was restored.