RT-AX88U Pro Dropping WAN Connection

[dcmonroe00]

I recently updated the firmware on my Asus RT-AX88U Pro to 3004.388.8_2. The router was working fine prior to the update, but immediately afterward, the WAN connection became unstable. It drops every few minutes, sometimes for just a couple of seconds, other times as long a minute. The LAN connection is fine, but internet drops. I tried reverting to version 3004_388.7_0, but that did not fix the connection problem. I've confirmed that the router is the issue by connecting a computer directly to my Netgear Nighthawk CM2050V modem, and the connection was fine, but when the router was put back in place the instability started again. Any suggestions would be greatly appreciated!

 

[ColinTaylor]

Log into the router and go to System Log > General Log to see why the connection is dropping.

 

[dcmonroe00]

Thanks for the response. I've looked at the log, and I'm not seeing any events that show a connection failure. However, I am running Net Uptime Monitor, and it is failing every few minutes, and activity keeps pausing every few minutes. As noted in the JPEG, I've had 24 failures in 56 minutes.

 

[ColinTaylor]

If there's nothing in the log that suggests the problem is upstream of the router. I know you said that the problem didn't happen when you plugged your PC into the modem so it maybe some sort of provisioning issue on the ISP side.

I suggest you log into the router using the PC that you previously connected to the modem. Then go to WAN - Internet Connection > Special Requirement from ISP. Click on the MAC Clone button which should populate the MAC Address field with that of your PC. Apply that change and wait a couple of minutes. Then power off the modem and the router. Wait a minute and turn on the modem. Wait another couple of minutes the allow the modem to fully boot up before turning the router back on.

 

[Don Draper]

I've been dealing with the same problem on my AX86U-Pro since the latest update. I've tried everything to troubleshoot. Had the ISP come out, and they even gave me a new modem, but no issues were found on their end. When I remove the AX86U from the setup, unbridge and use the modem directly, everything works fine. I've done factory resets, reverted to stock firmware, and tried a bunch of different settings, cables, but after a few hours, the router still drops Wi-Fi, loses internet access, or reboots. Right now, it's being looked at before the store will honor the extended warranty.

 

[dcmonroe00]

My experience matched yours. I've had Xfinity come out and troubleshoot. They could not replace the modem because I own it, but they said it has to be the modem or the router - there is no issue with the line. Since everything works when running directly through the modem, I am convinced it is the router. I am also convinced that the 3004.388.8_2 firmware update is the cause. Everything was running fine until the update, then immediately the dropped connection issue started.

 

[SadikP]

I thought I was the only one having this issue.

Updated to 3004_388.8_2 on my RT-AX11000.

Internet craps out every 12 or so hours.
I've even downgraded to some of the previous FW.
Downgraded to 3004.388.4 yesterday, I thought things were going well until it just dropped the WAN again just now.

Really need a fix for this. I know of another Asus user having the same issue.

 

[OzarkEdge]

I recently updated the firmware on my Asus RT-AX88U Pro to 3004.388.8_2. The router was working fine prior to the update, but immediately afterward, the WAN connection became unstable. It drops every few minutes, sometimes for just a couple of seconds, other times as long a minute. The LAN connection is fine, but internet drops. I tried reverting to version 3004_388.7_0, but that did not fix the connection problem. I've confirmed that the router is the issue by connecting a computer directly to my Netgear Nighthawk CM2050V modem, and the connection was fine, but when the router was put back in place the instability started again. Any suggestions would be greatly appreciated!

My RT-AX88U_Pro_3.0.0.6.102.33320 does not drop its Spectrum cable WAN connection.

OE

 

[dcmonroe00]

If there's nothing in the log that suggests the problem is upstream of the router. I know you said that the problem didn't happen when you plugged your PC into the modem so it maybe some sort of provisioning issue on the ISP side.

I suggest you log into the router using the PC that you previously connected to the modem. Then go to WAN - Internet Connection > Special Requirement from ISP. Click on the MAC Clone button which should populate the MAC Address field with that of your PC. Apply that change and wait a couple of minutes. Then power off the modem and the router. Wait a minute and turn on the modem. Wait another couple of minutes the allow the modem to fully boot up before turning the router back on.

Thank you so much for your suggestion! I tried it, and to my surprise, IT WORKED....for about a week. After several days of uninterrupted WAN access with the cloned MAC address, the problem started again. This is SUPER frustrating. If it truly is a provisioning issue, wouldn't I see connectivity problems with all other devices on the network? That is not the case - everything is up, or everything is down.

 

[ColinTaylor]

If it truly is a provisioning issue, wouldn't I see connectivity problems with all other devices on the network? That is not the case - everything is up, or everything is down.

Isn't that what you were describing - when the router has WAN issues it is effecting everything on your LAN (apart from local-only traffic)?

Check the logs on the modem.

Maybe also check the WAN lease duration (Network Map > Internet status > Lease time/expires). Perhaps the problem occurs when the lease has expired.

Does powering off the modem and waiting a few minutes before turning it back on fix the problem?

 

[dcmonroe00]

You are correct - when the WAN goes, it affects all LAN devices.

I've looked at the modem log and see nothing noteworthy there. I've also checked the lease time; it expires in 2 days. I've tried resetting the modem several times, leaving it unplugged for 5 minutes each time, but that does not fix the issue. The only thing that works is to run the modem directly to a PC, but of course, that doesn't help the other 50+ devices on my network.

 

[RMinNJ]

It sounds like some dhcp issue from your isp? Definitely try different cables also.

 

[Daniel Skupien]

I HAVE THIS EXACT PROBLEM WITH THIS ROUTER! I've been factory resetting my modem, my router, and nothing fixes this issue! I was about to post asking for help about this issue as well. Here's some my logs.

ct 26 02:10:00 wlceventd: wlceventd_proc_event(722): eth6: Assoc 8C:85:80:28:7B:5A, status: Successful (0), rssi:-43
Oct 26 02:11:20 acsd: eth6: COEX: downgraded chanspec 0x1803 to 0x1001: channel 2 used by exiting BSSs
Oct 26 02:22:46 WAN Connection: WAN was restored.
Oct 26 02:26:23 kernel: CPU: 0 PID: 2509 Comm: lighttpd Tainted: P O 4.19.183 #1
Oct 26 02:26:23 kernel: Hardware name: RTAX88U_PRO_gpy211 (DT)
Oct 26 02:26:23 kernel: pstate: 600b0010 (nZCv q A32 LE aif)
Oct 26 02:26:23 kernel: pc : 00000000f6bd498c
Oct 26 02:26:23 kernel: lr : 00000000f6bd4984
Oct 26 02:26:23 kernel: sp : 00000000fffc9ae0
Oct 26 02:26:23 kernel: x12: 00000000f6bec1dc
Oct 26 02:26:23 kernel: x11: 000000000110ef68 x10: 0000000001093190
Oct 26 02:26:23 kernel: x9 : 00000000010ac760 x8 : 0000000000000041
Oct 26 02:26:23 kernel: x7 : 0000000000000000 x6 : 00000000ffffffff
Oct 26 02:26:23 kernel: x5 : 00000000011da0e0 x4 : 00000000011dc6a8
Oct 26 02:26:23 kernel: x3 : 00000000011d20c8 x2 : 00000000011d2b88
Oct 26 02:26:23 kernel: x1 : 000000000000000a x0 : 0000000000000000
Oct 26 02:26:24 acsd: eth6: COEX: downgraded chanspec 0x1803 to 0x1001: channel 2 used by exiting BSSs
Oct 26 02:27:05 WAN Connection: WAN was restored.
Oct 26 02:27:59 kernel: NOHZ: local_softirq_pending 04
Oct 26 02:28:59 WAN Connection: WAN was restored.
Oct 26 02:34:17 WAN Connection: WAN was restored.
Oct 26 02:37:37 WAN Connection: WAN was restored.
Oct 26 02:41:03 WAN Connection: WAN was restored.
Oct 26 02:41:28 acsd: eth6: COEX: downgraded chanspec 0x1803 to 0x1001: channel 2 used by exiting BSSs
Oct 26 02:44:05 kernel: NOHZ: local_softirq_pending 04
Oct 26 02:50:10 WAN Connection: WAN was restored.
Oct 26 02:55:03 WAN Connection: WAN was restored.
Oct 26 02:56:05 kernel: NOHZ: local_softirq_pending 04
Oct 26 02:56:31 acsd: eth6: COEX: downgraded chanspec 0x1803 to 0x1001: channel 2 used by exiting BSSs
Oct 26 02:56:38 WAN Connection: WAN was restored.
Oct 26 02:58:02 WAN Connection: WAN was restored.
Oct 26 03:03:05 WAN Connection: WAN was restored.
Oct 26 03:04:47 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind 10:2C:B1:35:6B:37, status: 0, reason: Station requesting (re)association is not authenticated with responding station (9), rssi:-58
Oct 26 03:04:47 wlceventd: wlceventd_proc_event(662): eth6: Disassoc 10:2C:B1:35:6B:37, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:-58
Oct 26 03:04:58 wlceventd: wlceventd_proc_event(685): eth6: Auth 10:2C:B1:35:6B:37, status: Successful (0), rssi:0
Oct 26 03:04:58 wlceventd: wlceventd_proc_event(722): eth6: Assoc 10:2C:B1:35:6B:37, status: Successful (0), rssi:-58
Oct 26 03:06:44 WAN Connection: WAN was restored.
Oct 26 03:11:35 acsd: eth6: COEX: downgraded chanspec 0x1803 to 0x1001: channel 2 used by exiting BSSs
Oct 26 03:19:05 WAN Connection: WAN was restored.
Oct 26 03:23:06 WAN Connection: WAN was restored.
Oct 26 03:26:38 acsd: eth6: COEX: downgraded chanspec 0x1803 to 0x1001: channel 2 used by exiting BSSs
Oct 26 03:27:07 WAN Connection: WAN was restored.
Oct 26 03:41:42 acsd: eth6: COEX: downgraded chanspec 0x1803 to 0x1001: channel 2 used by exiting BSSs
Oct 26 03:47:58 WAN Connection: WAN was restored.
Oct 26 03:51:58 WAN Connection: WAN was restored.
Oct 26 03:56:45 acsd: eth6: COEX: downgraded chanspec 0x1803 to 0x1001: channel 2 used by exiting BSSs
Oct 26 03:56:58 kernel: NOHZ: local_softirq_pending 04
Oct 26 04:01:59 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind FC:B9:7E:6B:AF:1D, status: 0, reason: Station requesting (re)association is not authenticated with responding station (9), rssi:-74
Oct 26 04:01:59 wlceventd: wlceventd_proc_event(662): eth6: Disassoc FC:B9:7E:6B:AF:1D, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:-74
Oct 26 04:01:59 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind FC:B9:7E:6B:AF:1D, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Oct 26 04:01:59 wlceventd: wlceventd_proc_event(662): eth6: Disassoc FC:B9:7E:6B:AF:1D, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Oct 26 04:01:59 wlceventd: wlceventd_proc_event(685): eth6: Auth FC:B9:7E:6B:AF:1D, status: Successful (0), rssi:0
Oct 26 04:01:59 wlceventd: wlceventd_proc_event(722): eth6: Assoc FC:B9:7E:6B:AF:1D, status: Successful (0), rssi:-74
Oct 26 04:04:50 WAN Connection: WAN was restored.
Oct 26 04:10:09 WAN Connection: WAN was restored.
Oct 26 04:10:58 kernel: NOHZ: local_softirq_pending 08
Oct 26 04:11:49 acsd: eth6: COEX: downgraded chanspec 0x1803 to 0x1001: channel 2 used by exiting BSSs
Oct 26 04:13:12 WAN Connection: WAN was restored.
Oct 26 04:13:56 WAN Connection: WAN was restored.
Oct 26 04:16:00 WAN Connection: WAN was restored.
Oct 26 04:20:58 kernel: NOHZ: local_softirq_pending 04
Oct 26 04:25:34 WAN Connection: WAN was restored.
Oct 26 04:26:52 acsd: eth6: COEX: downgraded chanspec 0x1803 to 0x1001: channel 2 used by exiting BSSs
Oct 26 04:39:42 kernel: NOHZ: local_softirq_pending 04
Oct 26 04:41:55 acsd: eth6: COEX: downgraded chanspec 0x1803 to 0x1001: channel 2 used by exiting BSSs
Oct 26 04:43:00 WAN Connection: WAN was restored.
Oct 26 04:46:47 WAN Connection: WAN was restored.
Oct 26 04:53:11 ddns: IP address, server and hostname have not changed since the last update.
Oct 26 04:54:54 WAN Connection: WAN was restored.
Oct 26 04:55:42 kernel: NOHZ: local_softirq_pending 08
Oct 26 04:56:59 acsd: eth6: COEX: downgraded chanspec 0x1803 to 0x1001: channel 2 used by exiting BSSs
Oct 26 04:57:42 kernel: NOHZ: local_softirq_pending 04
Oct 26 05:01:53 WAN Connection: WAN was restored.
Oct 26 05:05:17 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind FC:B9:7E:6B:AF:1D, status: 0, reason: Station requesting (re)association is not authenticated with responding station (9), rssi:-73
Oct 26 05:05:17 wlceventd: wlceventd_proc_event(662): eth6: Disassoc FC:B9:7E:6B:AF:1D, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:-73
Oct 26 05:05:17 wlceventd: wlceventd_proc_event(685): eth6: Auth FC:B9:7E:6B:AF:1D, status: Successful (0), rssi:0
Oct 26 05:05:17 wlceventd: wlceventd_proc_event(722): eth6: Assoc FC:B9:7E:6B:AF:1D, status: Successful (0), rssi:-74
Oct 26 05:07:27 WAN Connection: WAN was restored.
Oct 26 05:10:12 WAN Connection: WAN was restored.
Oct 26 05:12:03 acsd: eth6: COEX: downgraded chanspec 0x1803 to 0x1001: channel 2 used by exiting BSSs
Oct 26 05:12:42 WAN Connection: WAN was restored.
Oct 26 05:14:54 WAN Connection: WAN was restored.
Oct 26 05:16:43 WAN Connection: WAN was restored.
Oct 26 05:23:38 WAN Connection: WAN was restored.
Oct 26 05:27:06 acsd: eth6: COEX: downgraded chanspec 0x1803 to 0x1001: channel 2 used by exiting BSSs
Oct 26 05:34:26 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind 80:6A:10:244:FD, status: 0, reason: Station requesting (re)association is not authenticated with responding station (9), rssi:-45
Oct 26 05:34:26 wlceventd: wlceventd_proc_event(662): eth6: Disassoc 80:6A:10:244:FD, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:-45
Oct 26 05:34:30 wlceventd: wlceventd_proc_event(685): eth6: Auth 80:6A:10:244:FD, status: Successful (0), rssi:0
Oct 26 05:34:30 wlceventd: wlceventd_proc_event(722): eth6: Assoc 80:6A:10:244:FD, status: Successful (0), rssi:-52
Oct 26 05:34:34 WAN Connection: WAN was restored.
Oct 26 05:42:10 acsd: eth6: COEX: downgraded chanspec 0x1803 to 0x1001: channel 2 used by exiting BSSs
Oct 26 05:57:13 acsd: eth6: COEX: downgraded chanspec 0x1803 to 0x1001: channel 2 used by exiting BSSs
Oct 26 06:12:14 WAN Connection: WAN was restored.
Oct 26 06:12:16 acsd: eth6: COEX: downgraded chanspec 0x1803 to 0x1001: channel 2 used by exiting BSSs
Oct 26 06:14:56 WAN Connection: WAN was restored.
Oct 26 06:20:28 WAN Connection: WAN was restored.
Oct 26 06:24:30 WAN Connection: WAN was restored.
Oct 26 06:27:19 acsd: eth6: COEX: downgraded chanspec 0x1803 to 0x1001: channel 2 used by exiting BSSs
Oct 26 06:32:02 WAN Connection: WAN was restored.
Oct 26 06:42:23 acsd: eth6: COEX: downgraded chanspec 0x1803 to 0x1001: channel 2 used by exiting BSSs

Absolutely no indication from what I can see as to why it's being dropped, just keeps saying WAN was restored.

I believe the issue started when I did an update as well because it worked well for like 2 months and then for past month this constant internet connection drop keeps happening, I just yesterday saw a newer firmware (the one from end of September) and installed it hoping it would fix it, at first it seemed it did but then I wake up to see those logs and those WAN restored messages again this morning.

 

[Daniel Skupien]

I HAVE THIS EXACT PROBLEM WITH THIS ROUTER! I've been factory resetting my modem, my router, and nothing fixes this issue! I was about to post asking for help about this issue as well. Here's some my logs.

ct 26 02:10:00 wlceventd: wlceventd_proc_event(722): eth6: Assoc 8C:85:80:28:7B:5A, status: Successful (0), rssi:-43
Oct 26 02:11:20 acsd: eth6: COEX: downgraded chanspec 0x1803 to 0x1001: channel 2 used by exiting BSSs
Oct 26 02:22:46 WAN Connection: WAN was restored.
Oct 26 02:26:23 kernel: CPU: 0 PID: 2509 Comm: lighttpd Tainted: P O 4.19.183 #1
Oct 26 02:26:23 kernel: Hardware name: RTAX88U_PRO_gpy211 (DT)
Oct 26 02:26:23 kernel: pstate: 600b0010 (nZCv q A32 LE aif)
Oct 26 02:26:23 kernel: pc : 00000000f6bd498c
Oct 26 02:26:23 kernel: lr : 00000000f6bd4984
Oct 26 02:26:23 kernel: sp : 00000000fffc9ae0
Oct 26 02:26:23 kernel: x12: 00000000f6bec1dc
Oct 26 02:26:23 kernel: x11: 000000000110ef68 x10: 0000000001093190
Oct 26 02:26:23 kernel: x9 : 00000000010ac760 x8 : 0000000000000041
Oct 26 02:26:23 kernel: x7 : 0000000000000000 x6 : 00000000ffffffff
Oct 26 02:26:23 kernel: x5 : 00000000011da0e0 x4 : 00000000011dc6a8
Oct 26 02:26:23 kernel: x3 : 00000000011d20c8 x2 : 00000000011d2b88
Oct 26 02:26:23 kernel: x1 : 000000000000000a x0 : 0000000000000000
Oct 26 02:26:24 acsd: eth6: COEX: downgraded chanspec 0x1803 to 0x1001: channel 2 used by exiting BSSs
Oct 26 02:27:05 WAN Connection: WAN was restored.
Oct 26 02:27:59 kernel: NOHZ: local_softirq_pending 04
Oct 26 02:28:59 WAN Connection: WAN was restored.
Oct 26 02:34:17 WAN Connection: WAN was restored.
Oct 26 02:37:37 WAN Connection: WAN was restored.
Oct 26 02:41:03 WAN Connection: WAN was restored.
Oct 26 02:41:28 acsd: eth6: COEX: downgraded chanspec 0x1803 to 0x1001: channel 2 used by exiting BSSs
Oct 26 02:44:05 kernel: NOHZ: local_softirq_pending 04
Oct 26 02:50:10 WAN Connection: WAN was restored.
Oct 26 02:55:03 WAN Connection: WAN was restored.
Oct 26 02:56:05 kernel: NOHZ: local_softirq_pending 04
Oct 26 02:56:31 acsd: eth6: COEX: downgraded chanspec 0x1803 to 0x1001: channel 2 used by exiting BSSs
Oct 26 02:56:38 WAN Connection: WAN was restored.
Oct 26 02:58:02 WAN Connection: WAN was restored.
Oct 26 03:03:05 WAN Connection: WAN was restored.
Oct 26 03:04:47 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind 10:2C:B1:35:6B:37, status: 0, reason: Station requesting (re)association is not authenticated with responding station (9), rssi:-58
Oct 26 03:04:47 wlceventd: wlceventd_proc_event(662): eth6: Disassoc 10:2C:B1:35:6B:37, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:-58
Oct 26 03:04:58 wlceventd: wlceventd_proc_event(685): eth6: Auth 10:2C:B1:35:6B:37, status: Successful (0), rssi:0
Oct 26 03:04:58 wlceventd: wlceventd_proc_event(722): eth6: Assoc 10:2C:B1:35:6B:37, status: Successful (0), rssi:-58
Oct 26 03:06:44 WAN Connection: WAN was restored.
Oct 26 03:11:35 acsd: eth6: COEX: downgraded chanspec 0x1803 to 0x1001: channel 2 used by exiting BSSs
Oct 26 03:19:05 WAN Connection: WAN was restored.
Oct 26 03:23:06 WAN Connection: WAN was restored.
Oct 26 03:26:38 acsd: eth6: COEX: downgraded chanspec 0x1803 to 0x1001: channel 2 used by exiting BSSs
Oct 26 03:27:07 WAN Connection: WAN was restored.
Oct 26 03:41:42 acsd: eth6: COEX: downgraded chanspec 0x1803 to 0x1001: channel 2 used by exiting BSSs
Oct 26 03:47:58 WAN Connection: WAN was restored.
Oct 26 03:51:58 WAN Connection: WAN was restored.
Oct 26 03:56:45 acsd: eth6: COEX: downgraded chanspec 0x1803 to 0x1001: channel 2 used by exiting BSSs
Oct 26 03:56:58 kernel: NOHZ: local_softirq_pending 04
Oct 26 04:01:59 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind FC:B9:7E:6B:AF:1D, status: 0, reason: Station requesting (re)association is not authenticated with responding station (9), rssi:-74
Oct 26 04:01:59 wlceventd: wlceventd_proc_event(662): eth6: Disassoc FC:B9:7E:6B:AF:1D, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:-74
Oct 26 04:01:59 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind FC:B9:7E:6B:AF:1D, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Oct 26 04:01:59 wlceventd: wlceventd_proc_event(662): eth6: Disassoc FC:B9:7E:6B:AF:1D, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Oct 26 04:01:59 wlceventd: wlceventd_proc_event(685): eth6: Auth FC:B9:7E:6B:AF:1D, status: Successful (0), rssi:0
Oct 26 04:01:59 wlceventd: wlceventd_proc_event(722): eth6: Assoc FC:B9:7E:6B:AF:1D, status: Successful (0), rssi:-74
Oct 26 04:04:50 WAN Connection: WAN was restored.
Oct 26 04:10:09 WAN Connection: WAN was restored.
Oct 26 04:10:58 kernel: NOHZ: local_softirq_pending 08
Oct 26 04:11:49 acsd: eth6: COEX: downgraded chanspec 0x1803 to 0x1001: channel 2 used by exiting BSSs
Oct 26 04:13:12 WAN Connection: WAN was restored.
Oct 26 04:13:56 WAN Connection: WAN was restored.
Oct 26 04:16:00 WAN Connection: WAN was restored.
Oct 26 04:20:58 kernel: NOHZ: local_softirq_pending 04
Oct 26 04:25:34 WAN Connection: WAN was restored.
Oct 26 04:26:52 acsd: eth6: COEX: downgraded chanspec 0x1803 to 0x1001: channel 2 used by exiting BSSs
Oct 26 04:39:42 kernel: NOHZ: local_softirq_pending 04
Oct 26 04:41:55 acsd: eth6: COEX: downgraded chanspec 0x1803 to 0x1001: channel 2 used by exiting BSSs
Oct 26 04:43:00 WAN Connection: WAN was restored.
Oct 26 04:46:47 WAN Connection: WAN was restored.
Oct 26 04:53:11 ddns: IP address, server and hostname have not changed since the last update.
Oct 26 04:54:54 WAN Connection: WAN was restored.
Oct 26 04:55:42 kernel: NOHZ: local_softirq_pending 08
Oct 26 04:56:59 acsd: eth6: COEX: downgraded chanspec 0x1803 to 0x1001: channel 2 used by exiting BSSs
Oct 26 04:57:42 kernel: NOHZ: local_softirq_pending 04
Oct 26 05:01:53 WAN Connection: WAN was restored.
Oct 26 05:05:17 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind FC:B9:7E:6B:AF:1D, status: 0, reason: Station requesting (re)association is not authenticated with responding station (9), rssi:-73
Oct 26 05:05:17 wlceventd: wlceventd_proc_event(662): eth6: Disassoc FC:B9:7E:6B:AF:1D, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:-73
Oct 26 05:05:17 wlceventd: wlceventd_proc_event(685): eth6: Auth FC:B9:7E:6B:AF:1D, status: Successful (0), rssi:0
Oct 26 05:05:17 wlceventd: wlceventd_proc_event(722): eth6: Assoc FC:B9:7E:6B:AF:1D, status: Successful (0), rssi:-74
Oct 26 05:07:27 WAN Connection: WAN was restored.
Oct 26 05:10:12 WAN Connection: WAN was restored.
Oct 26 05:12:03 acsd: eth6: COEX: downgraded chanspec 0x1803 to 0x1001: channel 2 used by exiting BSSs
Oct 26 05:12:42 WAN Connection: WAN was restored.
Oct 26 05:14:54 WAN Connection: WAN was restored.
Oct 26 05:16:43 WAN Connection: WAN was restored.
Oct 26 05:23:38 WAN Connection: WAN was restored.
Oct 26 05:27:06 acsd: eth6: COEX: downgraded chanspec 0x1803 to 0x1001: channel 2 used by exiting BSSs
Oct 26 05:34:26 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind 80:6A:10:244:FD, status: 0, reason: Station requesting (re)association is not authenticated with responding station (9), rssi:-45
Oct 26 05:34:26 wlceventd: wlceventd_proc_event(662): eth6: Disassoc 80:6A:10:244:FD, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:-45
Oct 26 05:34:30 wlceventd: wlceventd_proc_event(685): eth6: Auth 80:6A:10:244:FD, status: Successful (0), rssi:0
Oct 26 05:34:30 wlceventd: wlceventd_proc_event(722): eth6: Assoc 80:6A:10:244:FD, status: Successful (0), rssi:-52
Oct 26 05:34:34 WAN Connection: WAN was restored.
Oct 26 05:42:10 acsd: eth6: COEX: downgraded chanspec 0x1803 to 0x1001: channel 2 used by exiting BSSs
Oct 26 05:57:13 acsd: eth6: COEX: downgraded chanspec 0x1803 to 0x1001: channel 2 used by exiting BSSs
Oct 26 06:12:14 WAN Connection: WAN was restored.
Oct 26 06:12:16 acsd: eth6: COEX: downgraded chanspec 0x1803 to 0x1001: channel 2 used by exiting BSSs
Oct 26 06:14:56 WAN Connection: WAN was restored.
Oct 26 06:20:28 WAN Connection: WAN was restored.
Oct 26 06:24:30 WAN Connection: WAN was restored.
Oct 26 06:27:19 acsd: eth6: COEX: downgraded chanspec 0x1803 to 0x1001: channel 2 used by exiting BSSs
Oct 26 06:32:02 WAN Connection: WAN was restored.
Oct 26 06:42:23 acsd: eth6: COEX: downgraded chanspec 0x1803 to 0x1001: channel 2 used by exiting BSSs

Absolutely no indication from what I can see as to why it's being dropped, just keeps saying WAN was restored.

I believe the issue started when I did an update as well because it worked well for like 2 months and then for past month this constant internet connection drop keeps happening, I just yesterday saw a newer firmware (the one from end of September) and installed it hoping it would fix it, at first it seemed it did but then I wake up to see those logs and those WAN restored messages again this morning.

FYI, I have a Nighthawk Cm3000 as my modem.

 

[ColinTaylor]

@Daniel Skupien Try this as an experiment:

1. Unplug the ethernet cable between your modem and the router.
2. Reboot the router.
3. Log into the router's webUI and go to the AiCloud 2.0 section.
4. Turn off all features in this section.
5. Plug the modem's ethernet cable back in.

Monitor over time to see if the situation has improved.

 

[Daniel Skupien]

@Daniel Skupien Try this as an experiment:

1. Unplug the ethernet cable between your modem and the router.
2. Reboot the router.
3. Log into the router's webUI and go the the AiCloud 2.0 section.
4. Turn off all features in this section.
5. Plug the modem's ethernet cable back in.

Monitor over time to see if the situation has improved.

I'm willing to try anything at this point, I'm so fed up with this absolutely unreliable internet connection. I'm just now trying to use WAN Aggregation just to see if that could possibly do anything, it sucks because now my max speed went from 2300Mbps to 1500Mbps on my PC, but I need to figure out something to make this reliable, God only knows if Asus would do anything to actually help me with this in a more immediate way, I can't have no router for a week, don't want to spend money on a new one when this is only not even 3 months old.

 

[Daniel Skupien]

@Daniel Skupien Try this as an experiment:

1. Unplug the ethernet cable between your modem and the router.
2. Reboot the router.
3. Log into the router's webUI and go the the AiCloud 2.0 section.
4. Turn off all features in this section.
5. Plug the modem's ethernet cable back in.

Monitor over time to see if the situation has improved.

I switched back to regular single WAN 2.5Gbps port, the WAN Aggregation option didn't help anything.

I'm trying your suggestion now. I've also contacted Asus about just getting a new one, paying upfront, getting it, sending the old one, and then getting refunded. My Amazon return window for this thing closed a month ago.

 

[ColinTaylor]

@Daniel Skupien I'd also suggest that you go into the Wireless settings for 2.4GHz and change the "Channel bandwidth" to 20 MHz as it's clear from your log that your environment cannot maintain a 40 MHz bandwidth. If you have enabled "Web Access from WAN" (Administration - System) that should also be disabled.

 

[Daniel Skupien]

@Daniel Skupien I'd also suggest that you go into the Wireless settings for 2.4GHz and change the "Channel bandwidth" to 20 MHz as it's clear from your log that your environment cannot maintain a 40 MHz bandwidth. If you have enabled "Web Access from WAN" (Administration - System) that should also be disabled.

Thanks for noticing an issue with my 2.4ghz band, most things connected to it are IOT devices, haven't noticed too many issues but might explain an issue I remember having with a couple of those devices sometimes.

Good tip for second part for anyone to see, as for a long time I did used to use Web Acess from WAN for messing around with stuff while I traveled, until one day I noticed logs of several failed access attempts which told me people were trying to get in.

Thus far I have not had a internet drop, but as you can see in the logs it can be quite random, could go several minutes or a few hours without seeing WAN is restored message.

 

[Lucas Brasi]

I recently updated the firmware on my Asus RT-AX88U Pro to 3004.388.8_2. The router was working fine prior to the update, but immediately afterward, the WAN connection became unstable. It drops every few minutes, sometimes for just a couple of seconds, other times as long a minute. The LAN connection is fine, but internet drops. I tried reverting to version 3004_388.7_0, but that did not fix the connection problem. I've confirmed that the router is the issue by connecting a computer directly to my Netgear Nighthawk CM2050V modem, and the connection was fine, but when the router was put back in place the instability started again. Any suggestions would be greatly appreciated!

Who is your ISP? I'm thinking this may be an issue between Comcast and some ASUS routers. I've had the same problem with my RT-AX86U that started two or three weeks ago, out of the blue. I was already running the current Merlin firmware. I found few conversations regarding this issue online at the time, but more seem to be popping up. Everyone I've talked to seems to have Comcast, though that could just be due to their market share. Have you observed real-time traffic in the ASUS router app when this happens? A common theme is that there are these blasts of outgoing WAN traffic and the LAN has nothing going on. Mine pegs at near gigabit throughput, though my upload speed to Comcast is only around 24 mbps. After 10, 20, or 30 seconds or so, it stops, and everything starts working again. This screamed botnet exploit, so I factory reset my router, manually set it back up, and all was good until it returned a day later. In trying to resolve the issue, I first replaced my modem, which needed to be upgraded anyway. The problem still came back. I then bought a new RT-AX86U Pro (what can I say, I like this router), updated it to the latest factory firmware, manually set it up, kept all WAN access turned off, including AI Cloud, and everything worked for several days. Then the problem returned with a vengeance. Nothing in the logs could explain it, but the same blast was going from router to WAN, and nothing on the LAN side until it would stop. I called the ASUS tech support number, and they have a recording that they are aware of intermittent internet disconnects with some of their routers and say it is due to some server misconfiguration on their end, and they're working on it. I had a lot going on so I didn't go any further. I ended up hooking up a Nighthawk router, and my internet has been solid ever since. I figure I'll just keep an eye out for a new firmware release, and give it another try. That seems to be what others are doing as well. There's really nothing else I can think of to try.