AX RT-AX88U + Comcast Random Dropouts

[choover]

First I'll say that I'm an engineer by trade and understand the basics of networking. This problem however has eluded me for a long time (2 years)... and I need some help on what to try next.

My internet drops out quite randomly. I keep a log of each event but cant find any pattern to it. Drops out 4-5 times a month. It requires me to reboot both of my routers (which I can do via Asus app on phone over Wifi when still connected to my router, obviously without internet) but not required to reboot the modem to get internet to return. Wifi signals stay available, its a loss of internet connection (LAN goes out too). I'm going as far as monitoring the network log for which MAC address has been utilized most recently before a drop. No pattern... yet.

Long Background: Moved into a new home in 2020, installed my Motorola Surfboard modem with Comcast ISP, connected to a Netgear Blackhawk router and then downstream Ethernet connected to a second Netgear router on other side of house for full WiFi coverage (set as an access point). Previous home just had the one Netgear router, no additional access point, no issues there. Figured I'd troubleshoot hardware first. Replaced both Netgear routers with (2) Asus RT-AX88U, using Ethernet backhaul and second router set to access point mode. Dropouts still occurred, but I'll admit these routers are great to work with. Next I swapped the Motorola modem out for a Comcast rental modem. Figured if problem persists at least now they can help me troubleshoot (wishful thinking). Dropouts still occur.

I wish I could monitor my street signal for interference if I had an oscilloscope or something, but I don't. I can check logs or rig up some sort of test with instructions... please help end this madness!

Other notes and things I've tried:
-I have a couple static IPs
-Tried DHCP query option from aggressive, continuous, normal
-I've had Comcast test all the cables from the street to house
-Eliminated a cable splitter at home input, wasn't being used
-75ohm termination is used at modem from street coax
-During a dropout, I connected a laptop directly to modem and pinged 8.8.8.8 just fine, while routers were not working
-Replaced cable between modem and router during outage, router state did not change until I forced reboot via Asus app

Haven't tried but plan to soon:
-Swap routers, one to router other to access point
-Drop down to 1 router for awhile, remove access point
-Try merlin firmware

 

[Tech Junky]

First thing I would do is hard reset the devices and reconfigure them. Make sure you're running the latest FW on them as well. If everything is running OEM FW then keep it that way until you sort things out.

Now you mention Netgear x 2 and in the title it sounds like an Asus and you mention Merlin.

It's not a Comcast issue as you've proven that by bypassing your routers completely. I ditched my Netgear and went DIY instead because of their crappy updates that broke more stuff than fixed it seemed weekly.

 

[GHammer]

What does the router log show when this happens, before rebooting it?

 

[choover]

What does the router log show when this happens, before rebooting it?

Here's one from last month I saved:

Jul 18 07:52:00 wlceventd: wlceventd_proc_event(527): eth7: Auth 08:D4:0C:81:19:92, status: Successful (0), rssi:-22
Jul 18 07:52:00 wlceventd: wlceventd_proc_event(537): eth7: ReAssoc 08:D4:0C:81:19:92, status: Successful (0), rssi:-22
Jul 18 07:52:02 wlceventd: wlceventd_proc_event(491): eth7: Deauth_ind 74:D6:37:47:6F:57, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-55
Jul 18 07:52:02 wlceventd: wlceventd_proc_event(491): eth7: Deauth_ind 74:D6:37:47:6F:57, status: 0, reason: Previous authentication no longer valid (2), rssi:-55
Jul 18 07:52:02 kernel: eth0 (Int switch port: 3) (Logical Port: 3) (phyId: c) Link DOWN.
Jul 18 07:52:04 wlceventd: wlceventd_proc_event(491): eth7: Deauth_ind 08:D4:0C:81:19:92, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-22
Jul 18 07:52:05 wlceventd: wlceventd_proc_event(491): eth7: Deauth_ind 08:D4:0C:81:19:92, status: 0, reason: Unspecified reason (1), rssi:-22
Jul 18 07:52:05 wlceventd: wlceventd_proc_event(527): eth7: Auth 08:D4:0C:81:19:92, status: Successful (0), rssi:-22
Jul 18 07:52:05 wlceventd: wlceventd_proc_event(537): eth7: ReAssoc 08:D4:0C:81:19:92, status: Successful (0), rssi:-22
Jul 18 07:52:07 WAN Connection: WAN(0) link down.
Jul 18 07:52:09 wlceventd: wlceventd_proc_event(491): eth7: Deauth_ind 08:D4:0C:81:19:92, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-22
Jul 18 07:52:09 wlceventd: wlceventd_proc_event(491): eth7: Deauth_ind 08:D4:0C:81:19:92, status: 0, reason: Previous authentication no longer valid (2), rssi:-22
Jul 18 07:52:09 wlceventd: wlceventd_proc_event(527): eth7: Auth 08:D4:0C:81:19:92, status: Successful (0), rssi:0
Jul 18 07:52:09 wlceventd: wlceventd_proc_event(537): eth7: ReAssoc 08:D4:0C:81:19:92, status: Successful (0), rssi:-23
Jul 18 07:52:13 wlceventd: wlceventd_proc_event(491): eth7: Deauth_ind 08:D4:0C:81:19:92, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-25
Jul 18 07:52:14 wlceventd: wlceventd_proc_event(491): eth7: Deauth_ind 08:D4:0C:81:19:92, status: 0, reason: Previous authentication no longer valid (2), rssi:-25
Jul 18 07:52:20 kernel: eth0 (Int switch port: 3) (Logical Port: 3) (phyId: c) Link UP at 1000 mbps full duplex
Jul 18 07:52:22 WAN Connection: WAN(0) link up.
Jul 18 07:52:22 rc_service: wanduck 1029:notify_rc restart_wan_if 0
Jul 18 07:52:29 kernel: eth0 (Int switch port: 3) (Logical Port: 3) (phyId: c) Link DOWN.
Jul 18 07:52:32 kernel: eth0 (Int switch port: 3) (Logical Port: 3) (phyId: c) Link UP at 1000 mbps full duplex

 

[choover]

First thing I would do is hard reset the devices and reconfigure them. Make sure you're running the latest FW on them as well. If everything is running OEM FW then keep it that way until you sort things out.

Now you mention Netgear x 2 and in the title it sounds like an Asus and you mention Merlin.

It's not a Comcast issue as you've proven that by bypassing your routers completely. I ditched my Netgear and went DIY instead because of their crappy updates that broke more stuff than fixed it seemed weekly.

I have tried factory reset and reconfigure and they are always up to date firmware. I'm running two RT-AX88Us now, I was just noting Netgear in my problem description as I had the problem before I got my Asus routers.

 

[ColinTaylor]

Here's one from last month I saved:

If you post the output inside a CODE block it makes it more readable.

The device connected to the router's WAN port (presumably a modem) disconnected. Perhaps the modem rebooted itself or there's a faulty cable.

Jul 18 07:52:02 kernel: eth0 (Int switch port: 3) (Logical Port: 3) (phyId: c) Link DOWN.
Jul 18 07:52:07 WAN Connection: WAN(0) link down.
Jul 18 07:52:20 kernel: eth0 (Int switch port: 3) (Logical Port: 3) (phyId: c) Link UP at 1000 mbps full duplex
Jul 18 07:52:22 WAN Connection: WAN(0) link up.
Jul 18 07:52:22 rc_service: wanduck 1029:notify_rc restart_wan_if 0
Jul 18 07:52:29 kernel: eth0 (Int switch port: 3) (Logical Port: 3) (phyId: c) Link DOWN.
Jul 18 07:52:32 kernel: eth0 (Int switch port: 3) (Logical Port: 3) (phyId: c) Link UP at 1000 mbps full duplex

 

[sfx2000]

If you want to see what's happening on the modem side - go to 192.168.100.1 - if prompted for a password, try the serial number printed on the modem for Motorola surfboards.

 

[Tech Junky]

Motorola is usually admin/motorola but, can vary by model.

The logs look like the Asus being rebooted and the IF's coming up under normal processes.

 

[ColinTaylor]

The logs look like the Asus being rebooted and the IF's coming up under normal processes.

No, the boot up messages are different than that.

 

[choover]

Had another dropout this morning. Here's the logs. At 8:36 I believe all logs are after when I hit reboot on the app, once date code changes to May 4 that's the reboot sequence. Also, app looks like this:

.

Had this a little earlier: Aug 27 08:34:03 acsd: acsd_main_loop(1125): sync_id: 54758, status:1, misc.error/abort

Aug 27 08:34:58 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind C4:5B:BE:BC:70:40, status: 0, reason: 4-way handshake timeout (f), rssi:0
Aug 27 08:35:00 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 68:54:FD:5C:1A:ED, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-45
Aug 27 08:35:00 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 68:54:FD:5C:1A:ED, status: 0, reason: Unspecified reason (1), rssi:0
Aug 27 08:35:00 wlceventd: wlceventd_proc_event(527): eth6: Auth 68:54:FD:5C:1A:ED, status: Successful (0), rssi:0
Aug 27 08:35:00 wlceventd: wlceventd_proc_event(556): eth6: Assoc 68:54:FD:5C:1A:ED, status: Successful (0), rssi:-46
Aug 27 08:35:04 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 68:54:FD:5C:1A:ED, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-45
Aug 27 08:35:04 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 68:54:FD:5C:1A:ED, status: 0, reason: Unspecified reason (1), rssi:0
Aug 27 08:35:04 wlceventd: wlceventd_proc_event(527): eth6: Auth 68:54:FD:5C:1A:ED, status: Successful (0), rssi:0
Aug 27 08:35:04 wlceventd: wlceventd_proc_event(556): eth6: Assoc 68:54:FD:5C:1A:ED, status: Successful (0), rssi:-46
Aug 27 08:35:08 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 68:54:FD:5C:1A:ED, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-45
Aug 27 08:35:08 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 68:54:FD:5C:1A:ED, status: 0, reason: Unspecified reason (1), rssi:0
Aug 27 08:35:08 wlceventd: wlceventd_proc_event(527): eth6: Auth 68:54:FD:5C:1A:ED, status: Successful (0), rssi:0
Aug 27 08:35:08 wlceventd: wlceventd_proc_event(556): eth6: Assoc 68:54:FD:5C:1A:ED, status: Successful (0), rssi:-46
Aug 27 08:35:12 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 68:54:FD:5C:1A:ED, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-45
Aug 27 08:35:12 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 68:54:FD:5C:1A:ED, status: 0, reason: Unspecified reason (1), rssi:0
Aug 27 08:35:12 wlceventd: wlceventd_proc_event(527): eth6: Auth 68:54:FD:5C:1A:ED, status: Successful (0), rssi:0
Aug 27 08:35:12 wlceventd: wlceventd_proc_event(556): eth6: Assoc 68:54:FD:5C:1A:ED, status: Successful (0), rssi:-46
Aug 27 08:35:16 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 68:54:FD:5C:1A:ED, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-45
Aug 27 08:35:16 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 68:54:FD:5C:1A:ED, status: 0, reason: Unspecified reason (1), rssi:0
Aug 27 08:35:16 wlceventd: wlceventd_proc_event(527): eth6: Auth 68:54:FD:5C:1A:ED, status: Successful (0), rssi:0
Aug 27 08:35:16 wlceventd: wlceventd_proc_event(556): eth6: Assoc 68:54:FD:5C:1A:ED, status: Successful (0), rssi:-45
Aug 27 08:35:20 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 68:54:FD:5C:1A:ED, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-45
Aug 27 08:35:20 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 68:54:FD:5C:1A:ED, status: 0, reason: Unspecified reason (1), rssi:0
Aug 27 08:35:20 wlceventd: wlceventd_proc_event(527): eth6: Auth 68:54:FD:5C:1A:ED, status: Successful (0), rssi:0
Aug 27 08:35:20 wlceventd: wlceventd_proc_event(556): eth6: Assoc 68:54:FD:5C:1A:ED, status: Successful (0), rssi:-46
Aug 27 08:35:24 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 68:54:FD:5C:1A:ED, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-45
Aug 27 08:35:24 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 68:54:FD:5C:1A:ED, status: 0, reason: Unspecified reason (1), rssi:0
Aug 27 08:35:24 wlceventd: wlceventd_proc_event(527): eth6: Auth 68:54:FD:5C:1A:ED, status: Successful (0), rssi:0
Aug 27 08:35:24 wlceventd: wlceventd_proc_event(556): eth6: Assoc 68:54:FD:5C:1A:ED, status: Successful (0), rssi:-45
Aug 27 08:35:28 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 68:54:FD:5C:1A:ED, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-46
Aug 27 08:35:28 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 68:54:FD:5C:1A:ED, status: 0, reason: Unspecified reason (1), rssi:0
Aug 27 08:35:28 wlceventd: wlceventd_proc_event(527): eth6: Auth 68:54:FD:5C:1A:ED, status: Successful (0), rssi:0
Aug 27 08:35:28 wlceventd: wlceventd_proc_event(556): eth6: Assoc 68:54:FD:5C:1A:ED, status: Successful (0), rssi:-46
Aug 27 08:35:32 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 68:54:FD:5C:1A:ED, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-45
Aug 27 08:35:32 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 68:54:FD:5C:1A:ED, status: 0, reason: Unspecified reason (1), rssi:0
Aug 27 08:35:32 wlceventd: wlceventd_proc_event(527): eth6: Auth 68:54:FD:5C:1A:ED, status: Successful (0), rssi:0
Aug 27 08:35:32 wlceventd: wlceventd_proc_event(556): eth6: Assoc 68:54:FD:5C:1A:ED, status: Successful (0), rssi:-46
Aug 27 08:35:36 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 68:54:FD:5C:1A:ED, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-45
Aug 27 08:35:36 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 68:54:FD:5C:1A:ED, status: 0, reason: Unspecified reason (1), rssi:0
Aug 27 08:35:36 wlceventd: wlceventd_proc_event(527): eth6: Auth 68:54:FD:5C:1A:ED, status: Successful (0), rssi:0
Aug 27 08:35:36 wlceventd: wlceventd_proc_event(556): eth6: Assoc 68:54:FD:5C:1A:ED, status: Successful (0), rssi:-46
Aug 27 08:35:37 wlceventd: wlceventd_proc_event(527): eth6: Auth A4:08:01:AB:9F:1D, status: Successful (0), rssi:0
Aug 27 08:35:37 wlceventd: wlceventd_proc_event(556): eth6: Assoc A4:08:01:AB:9F:1D, status: Successful (0), rssi:-47
Aug 27 08:35:40 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 68:54:FD:5C:1A:ED, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-45
Aug 27 08:35:40 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 68:54:FD:5C:1A:ED, status: 0, reason: Unspecified reason (1), rssi:0
Aug 27 08:35:40 wlceventd: wlceventd_proc_event(527): eth6: Auth 68:54:FD:5C:1A:ED, status: Successful (0), rssi:0
Aug 27 08:35:40 wlceventd: wlceventd_proc_event(556): eth6: Assoc 68:54:FD:5C:1A:ED, status: Successful (0), rssi:-47
Aug 27 08:35:41 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind A4:08:01:AB:9F:1D, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-47
Aug 27 08:35:41 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind A4:08:01:AB:9F:1D, status: 0, reason: Previous authentication no longer valid (2), rssi:-47
Aug 27 08:35:44 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 68:54:FD:5C:1A:ED, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-45
Aug 27 08:35:44 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 68:54:FD:5C:1A:ED, status: 0, reason: Unspecified reason (1), rssi:0
Aug 27 08:35:44 wlceventd: wlceventd_proc_event(527): eth6: Auth 68:54:FD:5C:1A:ED, status: Successful (0), rssi:0
Aug 27 08:35:44 wlceventd: wlceventd_proc_event(556): eth6: Assoc 68:54:FD:5C:1A:ED, status: Successful (0), rssi:-46
Aug 27 08:35:48 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 68:54:FD:5C:1A:ED, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-45
Aug 27 08:35:48 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 68:54:FD:5C:1A:ED, status: 0, reason: Unspecified reason (1), rssi:0
Aug 27 08:35:48 wlceventd: wlceventd_proc_event(527): eth6: Auth 68:54:FD:5C:1A:ED, status: Successful (0), rssi:0
Aug 27 08:35:48 wlceventd: wlceventd_proc_event(556): eth6: Assoc 68:54:FD:5C:1A:ED, status: Successful (0), rssi:-46
Aug 27 08:35:52 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 68:54:FD:5C:1A:ED, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-46
Aug 27 08:35:52 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 68:54:FD:5C:1A:ED, status: 0, reason: Unspecified reason (1), rssi:0
Aug 27 08:35:52 wlceventd: wlceventd_proc_event(527): eth6: Auth 68:54:FD:5C:1A:ED, status: Successful (0), rssi:0
Aug 27 08:35:52 wlceventd: wlceventd_proc_event(556): eth6: Assoc 68:54:FD:5C:1A:ED, status: Successful (0), rssi:-46
Aug 27 08:35:56 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 68:54:FD:5C:1A:ED, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-45
Aug 27 08:35:56 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 68:54:FD:5C:1A:ED, status: 0, reason: Unspecified reason (1), rssi:0
Aug 27 08:35:56 wlceventd: wlceventd_proc_event(527): eth6: Auth 68:54:FD:5C:1A:ED, status: Successful (0), rssi:0
Aug 27 08:35:56 wlceventd: wlceventd_proc_event(556): eth6: Assoc 68:54:FD:5C:1A:ED, status: Successful (0), rssi:-46
Aug 27 08:36:00 rc_service: cfg_server 1922:notify_rc reboot

 

[choover]

One idea I have - can I configure my network to run two in router mode, both connected to separate modem jacks? How will the network work if both are running the same named WiFi signals?

This way if one connection goes unstable, the other should stay stable. Then I can troubleshoot router/cable/etc. If both go unstable, the common denominator is the modem. Is this a good idea to try?

 

[ColinTaylor]

At 8:36 I believe all logs are after when I hit reboot on the app...

That's not particularly helpful because it only starts 12 seconds prior to you rebooting the router. We need to see the logs from earlier, when the problem first occurs.

 

[choover]

That's not particularly helpful because it only starts 12 seconds prior to you rebooting the router. We need to see the logs from earlier, when the problem first occurs.

Updated post to prior reboot

 

[ColinTaylor]

Updated post to prior reboot

That still doesn't appear to cover the time period we're interested in, it only covers two minutes prior to you rebooting it. Just save the entire log and upload it to somewhere like pastebin.com and provide a link to it.