Rt-ax86U disconnects frequently

[pb9]

Unfortunately, the disconnections are happening again this morning both via Ethernet and Wireless. I am a Newbie and don't know how to capture the detailed logs. Kindly advice next steps. Also, I changed the message log level to "debug" . Thanks

Mar 28 08:31:37 wlceventd: wlceventd_proc_event(505): eth7: Auth D0:25:98:C0:21:27, status: Successful (0)
Mar 28 08:31:37 wlceventd: wlceventd_proc_event(534): eth7: Assoc D0:25:98:C0:21:27, status: Successful (0)
Mar 28 08:31:37 hostapd: eth7: STA d0:25:98:c0:21:27 IEEE 802.11: associated
Mar 28 08:31:41 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind D0:25:98:C0:21:27, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Mar 28 08:31:41 hostapd: eth7: STA d0:25:98:c0:21:27 IEEE 802.11: disassociated
Mar 28 08:31:41 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind D0:25:98:C0:21:27, status: 0, reason: Previous authentication no longer valid (2)
Mar 28 08:31:41 hostapd: eth7: STA d0:25:98:c0:21:27 IEEE 802.11: disassociated
Mar 28 08:39:34 hostapd: eth7: STA c8:58:c0:dd:ef:4b WPA: group key handshake completed (RSN)
Mar 28 08:39:34 hostapd: eth7: STA 7c:27:bc:b0:63:9b WPA: group key handshake completed (RSN)
Mar 28 08:39:34 hostapd: eth7: STA 72:72:12:60:36:f9 WPA: group key handshake completed (RSN)
Mar 28 08:49:41 wlceventd: wlceventd_proc_event(486): eth7: Disassoc 72:72:12:60:36:F9, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Mar 28 08:49:41 wlceventd: wlceventd_proc_event(486): eth7: Disassoc 72:72:12:60:36:F9, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Mar 28 08:49:41 hostapd: eth7: STA 72:72:12:60:36:f9 IEEE 802.11: disassociated
Mar 28 08:49:41 hostapd: eth7: STA 72:72:12:60:36:f9 IEEE 802.11: disassociated
Mar 28 08:49:47 wlceventd: wlceventd_proc_event(505): eth7: Auth 72:72:12:60:36:F9, status: Successful (0)
Mar 28 08:49:47 wlceventd: wlceventd_proc_event(534): eth7: Assoc 72:72:12:60:36:F9, status: Successful (0)
Mar 28 08:49:47 hostapd: eth7: STA 72:72:12:60:36:f9 IEEE 802.11: associated
Mar 28 08:49:47 hostapd: eth7: STA 72:72:12:60:36:f9 RADIUS: starting accounting session 6A4EFE43638B8D3B
Mar 28 08:49:47 hostapd: eth7: STA 72:72:12:60:36:f9 WPA: pairwise key handshake completed (RSN)
Mar 28 08:49:47 dnsmasq-dhcp[3507]: DHCPREQUEST(br0) 192.168.50.179 72:72:12:60:36:f9
Mar 28 08:49:47 dnsmasq-dhcp[3507]: DHCPACK(br0) 192.168.50.179 72:72:12:60:36:f9
Mar 28 09:13:00 wlceventd: wlceventd_proc_event(505): eth7: Auth 98:2C:BC:26:32:E3, status: Successful (0)
Mar 28 09:13:00 wlceventd: wlceventd_proc_event(534): eth7: Assoc 98:2C:BC:26:32:E3, status: Successful (0)
Mar 28 09:13:00 hostapd: eth7: STA 98:2c:bc:26:32:e3 IEEE 802.11: associated
Mar 28 09:13:04 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 98:2C:BC:26:32:E3, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Mar 28 09:13:04 hostapd: eth7: STA 98:2c:bc:26:32:e3 IEEE 802.11: disassociated
Mar 28 09:13:04 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 98:2C:BC:26:32:E3, status: 0, reason: Unspecified reason (1)
Mar 28 09:13:04 wlceventd: wlceventd_proc_event(505): eth7: Auth 98:2C:BC:26:32:E3, status: Successful (0)
Mar 28 09:13:04 wlceventd: wlceventd_proc_event(515): eth7: ReAssoc 98:2C:BC:26:32:E3, status: Successful (0)
Mar 28 09:13:04 hostapd: eth7: STA 98:2c:bc:26:32:e3 IEEE 802.11: associated
Mar 28 09:13:09 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 98:2C:BC:26:32:E3, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Mar 28 09:13:09 hostapd: eth7: STA 98:2c:bc:26:32:e3 IEEE 802.11: disassociated
Mar 28 09:13:09 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 98:2C:BC:26:32:E3, status: 0, reason: Unspecified reason (1)
Mar 28 09:13:09 wlceventd: wlceventd_proc_event(505): eth7: Auth 98:2C:BC:26:32:E3, status: Successful (0)
Mar 28 09:13:09 wlceventd: wlceventd_proc_event(515): eth7: ReAssoc 98:2C:BC:26:32:E3, status: Successful (0)
Mar 28 09:13:09 hostapd: eth7: STA 98:2c:bc:26:32:e3 IEEE 802.11: associated
Mar 28 09:13:13 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 98:2C:BC:26:32:E3, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Mar 28 09:13:13 hostapd: eth7: STA 98:2c:bc:26:32:e3 IEEE 802.11: disassociated
Mar 28 09:13:13 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 98:2C:BC:26:32:E3, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Mar 28 09:13:13 hostapd: eth7: STA 98:2c:bc:26:32:e3 IEEE 802.11: disassociated
Mar 28 09:13:13 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 98:2C:BC:26:32:E3, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Mar 28 09:13:13 hostapd: eth7: STA 98:2c:bc:26:32:e3 IEEE 802.11: disassociated
Mar 28 09:13:13 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 98:2C:BC:26:32:E3, status: 0, reason: Unspecified reason (1)
Mar 28 09:13:13 wlceventd: wlceventd_proc_event(505): eth7: Auth 98:2C:BC:26:32:E3, status: Successful (0)
Mar 28 09:13:13 wlceventd: wlceventd_proc_event(515): eth7: ReAssoc 98:2C:BC:26:32:E3, status: Successful (0)
Mar 28 09:13:13 hostapd: eth7: STA 98:2c:bc:26:32:e3 IEEE 802.11: associated
Mar 28 09:13:17 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 98:2C:BC:26:32:E3, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Mar 28 09:13:17 hostapd: eth7: STA 98:2c:bc:26:32:e3 IEEE 802.11: disassociated
Mar 28 09:13:18 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 98:2C:BC:26:32:E3, status: 0, reason: Previous authentication no longer valid (2)
Mar 28 09:13:18 hostapd: eth7: STA 98:2c:bc:26:32:e3 IEEE 802.11: disassociated
Mar 28 09:13:18 wlceventd: wlceventd_proc_event(505): eth7: Auth 98:2C:BC:26:32:E3, status: Successful (0)
Mar 28 09:13:18 wlceventd: wlceventd_proc_event(515): eth7: ReAssoc 98:2C:BC:26:32:E3, status: Successful (0)
Mar 28 09:13:18 hostapd: eth7: STA 98:2c:bc:26:32:e3 IEEE 802.11: associated
Mar 28 09:13:22 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 98:2C:BC:26:32:E3, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Mar 28 09:13:22 hostapd: eth7: STA 98:2c:bc:26:32:e3 IEEE 802.11: disassociated
Mar 28 09:13:23 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 98:2C:BC:26:32:E3, status: 0, reason: Previous authentication no longer valid (2)
Mar 28 09:13:23 hostapd: eth7: STA 98:2c:bc:26:32:e3 IEEE 802.11: disassociated
Mar 28 09:13:38 wlceventd: wlceventd_proc_event(505): eth7: Auth 98:2C:BC:26:32:E3, status: Successful (0)
Mar 28 09:13:38 wlceventd: wlceventd_proc_event(534): eth7: Assoc 98:2C:BC:26:32:E3, status: Successful (0)
Mar 28 09:13:38 hostapd: eth7: STA 98:2c:bc:26:32:e3 IEEE 802.11: associated
Mar 28 09:13:38 hostapd: eth7: STA 98:2c:bc:26:32:e3 RADIUS: starting accounting session 22AFC505EA08BB24
Mar 28 09:13:38 hostapd: eth7: STA 98:2c:bc:26:32:e3 WPA: pairwise key handshake completed (RSN)
Mar 28 09:13:41 dnsmasq-dhcp[3507]: DHCPDISCOVER(br0) 98:2c:bc:26:32:e3
Mar 28 09:13:41 dnsmasq-dhcp[3507]: DHCPOFFER(br0) 192.168.50.148 98:2c:bc:26:32:e3
Mar 28 09:13:41 dnsmasq-dhcp[3507]: DHCPREQUEST(br0) 192.168.50.148 98:2c:bc:26:32:e3
Mar 28 09:13:41 dnsmasq-dhcp[3507]: Ignoring domain txaus.ds.sjhs.com for DHCP host name TXAUSLTCD154572
Mar 28 09:13:41 dnsmasq-dhcp[3507]: DHCPACK(br0) 192.168.50.148 98:2c:bc:26:32:e3 TXAUSLTCD154572
Mar 28 09:13:41 dnsmasq-dhcp[3507]: DHCPINFORM(br0) 192.168.50.148 98:2c:bc:26:32:e3
Mar 28 09:13:41 dnsmasq-dhcp[3507]: DHCPACK(br0) 192.168.50.148 98:2c:bc:26:32:e3 TXAUSLTCD154572

 

[pb9]

So, the disconnects still seem to happen but it is odd that my teams has not disconnected while this was happening. It is been about an hour now and the router seems to have settled on Channel 10 for 2.4GHz and Channel 48 for 5GHz.
It has settled down somewhat. Even if the disconnections happen, I don't notice them unless I look for them. The disconnect happens and comes back within a couple of seconds - maybe that's what keeps the Teams meeting connected and I don't notice it. If this happens while streaming from Netflix, etc. I wouldn't even know.

I might be wrong, but the disconnects seem to be happening when I see the following messages.

 

[ColinTaylor]

Unfortunately, the disconnections are happening again this morning both via Ethernet and Wireless.

If it's happening to Ethernet devices then this is not a WiFi issue, or possibly it's multiple issues. I would try to diagnose the Ethernet problem first rather than wasting more time with WiFi.

Also, I changed the message log level to "debug".

This is wrong. Change "Default message log level" back to "notice" and then set "Log only messages more urgent than" to "all" for maximum information.

 

[pb9]

This is wrong. Change "Default message log level" back to "notice" and then set "Log only messages more urgent than" to "all" for maximum information.

Changed the log settings as you recommended above. Thanks.

 

[pb9]

If it's happening to Ethernet devices then this is not a WiFi issue, or possibly it's multiple issues. I would try to diagnose the Ethernet problem first rather than wasting more time with WiFi.

If it's happening to Ethernet devices then this is not a WiFi issue, or possibly it's multiple issues. I would try to diagnose the Ethernet problem first rather than wasting more time with WiFi.

What is the next step you recommend then? Please note my message above that the disconnects seem to happen when I get the below messages

Mar 28 10:48:26 acsd: acs_set_chspec: 0x100a (10) for reason APCS_CSTIMER
Mar 28 10:48:26 acsd: eth6: selected_chspec is 0x100a (10)
Mar 28 10:48:26 acsd: eth6: Adjusted channel spec: 0x100a (10)
Mar 28 10:48:26 acsd: eth6: selected channel spec: 0x100a (10)
Mar 28 10:48:26 acsd: eth6 Performing CSA on chspec 0x100a
Mar 28 10:58:26 kernel: httpd (1331): drop_caches: 1

 

[ColinTaylor]

What is the next step you recommend then? Please note my message above that the disconnects seem to happen when I get the below messages

Mar 28 10:48:26 acsd: acs_set_chspec: 0x100a (10) for reason APCS_CSTIMER
Mar 28 10:48:26 acsd: eth6: selected_chspec is 0x100a (10)
Mar 28 10:48:26 acsd: eth6: Adjusted channel spec: 0x100a (10)
Mar 28 10:48:26 acsd: eth6: selected channel spec: 0x100a (10)
Mar 28 10:48:26 acsd: eth6 Performing CSA on chspec 0x100a
Mar 28 10:58:26 kernel: httpd (1331): drop_caches: 1

Those are all WiFi messages. There's nothing there related to Ethernet.

 

[pb9]

Those are all WiFi messages. There's nothing there related to Ethernet.

Ok. What I meant to say was, I see wifi reconnecting 1 min after these messages pop up in the log.
I had disconnected Ethernet and switched to wifi when I noticed first time that ethernet was dropping too. I will connect to Ethernet again and collect the log. Thanks.

 

[TexasFlood]

So, the disconnects still seem to happen but it is odd that my teams has not disconnected while this was happening. It is been about an hour now and the router seems to have settled on Channel 10 for 2.4GHz and Channel 48 for 5GHz.
It has settled down somewhat. Even if the disconnections happen, I don't notice them unless I look for them. The disconnect happens and comes back within a couple of seconds - maybe that's what keeps the Teams meeting connected and I don't notice it. If this happens while streaming from Netflix, etc. I wouldn't even know.

I might be wrong, but the disconnects seem to be happening when I see the following messages.

Mar 28 09:59:56 acsd: eth6: selected_chspec is 0x1004 (4)
Mar 28 09:59:56 acsd: eth6: Adjusted channel spec: 0x1004 (4)
Mar 28 09:59:56 acsd: eth6: selected channel spec: 0x1004 (4)
Mar 28 09:59:56 acsd: eth6 Performing CSA on chspec 0x1004
Mar 28 10:15:00 acsd: acs_set_chspec: 0x1002 (2) for reason APCS_CSTIMER
Mar 28 10:15:00 acsd: eth6: selected_chspec is 0x1002 (2)
Mar 28 10:15:00 acsd: eth6: Adjusted channel spec: 0x1002 (2)
Mar 28 10:15:00 acsd: eth6: selected channel spec: 0x1002 (2)
Mar 28 10:15:00 acsd: eth6 Performing CSA on chspec 0x1002

Mine settled on channel 48 for 5Ghz pretty quickly and has stayed there. Rightly or wrongly, I have a longstanding distrust of auto selection for 2.4Ghz for manually selected channel 11 for that.

 

[pb9]

Mine settled on channel 48 for 5Ghz pretty quickly and has stayed there. Rightly or wrongly, I have a longstanding distrust of auto selection for 2.4Ghz for manually selected channel 11 for that.

Do you have to disable smart connect to select a particular channel for 2.4?

 

[pb9]

Mine settled on channel 48 for 5Ghz pretty quickly and has stayed there. Rightly or wrongly, I have a longstanding distrust of auto selection for 2.4Ghz for manually selected channel 11 for that.

This is what I have currently for my wireless settings. Changed after you mentioned channel 11.

 

[pb9]

Kind of worried about the above settings though. I had some interference on 160MHz channel a couple of weeks ago and I unchecked it. I hope smart connect can take care of that. So in my settings currently I have Smart Connect on but 2.4GHz set to 20MHz/Channel 11 but 5 GHz set to Auto(using Smart connect?) . Will this work or should I have Smart connect off to set a particular channel. By the way, I have had my Laptop connected to Ethernet for the last 1 hr and no disconnect issues so far. Thanks.

 

[bbunge]

Kind of worried about the above settings though. I had some interference on 160MHz channel a couple of weeks ago and I unchecked it. I hope smart connect can take care of that. So in my settings currently I have Smart Connect on but 2.4GHz set to 20MHz/Channel 11 but 5 GHz set to Auto(using Smart connect?) . Will this work or should I have Smart connect off to set a particular channel. By the way, I have had my Laptop connected to Ethernet for the last 1 hr and no disconnect issues so far. Thanks.

Those settings are pretty much what I have used for months with no issues. I do let the 2.4 GHz do Auto channel at 20 MHz. I use WPA2/WPA3-Personal. WPS is disabled. I use Guest 1 on 2.4 GHz with WPA2-Personal for my IoT clients.
The 2.4 GHz in my neighborhood is rather crowded and the neighbors are not knowledgeable enough to use just channels 1, 6 or 11. So I let the router choose.
My 5 GHz usually runs at 80 MHz (on channel 44 or 48) but will switch up to 160 GHz when the AX laptops connect. I do not use DFS channels as my Roku's use WIFI remotes that can't use DFS.

I am beginning to wonder if your connection issues are DNS failures. Ignore the log! DO your clients really disconnect from the router? Or do they stutter or pause when connecting to web sites?

 

[pb9]

I am beginning to wonder if your connection issues are DNS failures. Ignore the log! DO your clients really disconnect from the router? Or do they stutter or pause when connecting to web sites?

I do see the connections dropping. They have to reconnect to the Wifi(and then log on to the VPN for my office Laptop).

After rebooting the Modem and Router though, I have not had any Ethernet disconnection. I started off with Ethernet in the morning and the disconnects started happening. Then I switched to Wireless until a couple of hours ago. Then I rebooted both the modem and router. Then connected via Ethernet and the connection was pretty stable for more than an hour. Then switched to wireless from Ethernet and I thought I saw a blip in the connection but have no way to tell. Other than that one blip connection has been pretty stable for the last 2 hours after the Modem/Router reboot.

 

[TexasFlood]

Now sure if I had to disable smart connect, but I did disable it. I'd read some advice to disable it and just didn't see the value of having it enabled. I get good coverage on the 5Ghz since installing the RT-AX86U so switched most everything over to 5Ghz. I left some old heritage stuff and smart home devices on 2.4Ghz.

Here are my current settings. I have no idea if they're the best. I took my best guess and it's been working for me. If anyone sees anything questionable, I'd like to hear feedback.

I did notice in the professional settings that there is a setting to disconnect if RSSI gets below a defined dBm threshold. But that would just effect wireless not wired Ethernet.

 

[BreakingDad]

Wow, wasn't expecting this, this morning. I'm going to bail on this now, as I don't think I have anything useful to add, it seems Colin is looking at this thread now who has far greater knowledge.

One last 2 cents, Colin mentions this is ethernet as well. Just a thought, have you tried changing your cabling and looking at the main cable to your modem? There was a fault recently on my network, that the isp picked up when doing fault testing. Turned out the main box into my house needed replacing.

Also another "thought" are you using the 2.5gb port? If so I had issues with this and found the 1gb far more reliable.

Really hope you get the cause of all this, must be driving you crazy.

 

[pb9]

I would still advise, latest Merlin firmware, reboot manually, full factory reset, 1 ssid, leaving all settings alone and testing that for a while. Then make additonal tweaks if all good.

Quick update - After rebooting the Modem and the router, the disconnects seem to have disappeared. I hope this sticks because last time this happened, the Router worked great for 2 weeks and then the disconnects came back(started with interference on 160MHz). This time I hope after 2 weeks it doesn't go back to disconnects.

Here are the steps I took to get this issue fixed(for now anyways)
1)flashed to 386.5_2.
2)did a factory reset and have the smart connect turned on.
3)QoS is off. WPS is off.
4)In WAN/Internet Settings - changed DHCP query frequency to "Normal" from "Aggressive"(I believe this is needed for Spectrum users)

After above 4 steps, disconnects continued, so,
5)Left Smartconnect ON and changed 2.4GHz to channel 11 and set bandwidth to 20 MHz.
6)Rebooted Modem and Router.

Something changed after 5 and 6(or 5 or 6) and the disconnects magically disappeared.

I may have missed a step from @L&LD's guides but if I had done the Modem AND Router reboot, the disconnects probably wouldn't have happened.

I have been a poster boy for disconnect frustration. If this thing works for me, I will be this router's biggest advocate , because it has all the features I need and more.

 

[BreakingDad]

Quick update - After rebooting the Modem and the router, the disconnects seem to have disappeared. I hope this sticks because last time this happened, the Router worked great for 2 weeks and then the disconnects came back(started with interference on 160MHz). This time I hope after 2 weeks it doesn't go back to disconnects.

Here are the steps I took to get this issue fixed(for now anyways)
1)flashed to 386.5_2.
2)did a factory reset and have the smart connect turned on.
3)QoS is off. WPS is off.
4)In WAN/Internet Settings - changed DHCP query frequency to "Normal" from "Aggressive"(I believe this is needed for Spectrum users)

After above 4 steps, disconnects continued, so,
5)Left Smartconnect ON and changed 2.4GHz to channel 11 and set bandwidth to 20 MHz.
6)Rebooted Modem and Router.

Something changed after 5 and 6(or 5 or 6) and the disconnects magically disappeared.

I may have missed a step from @L&LD's guides but if I had done the Modem AND Router reboot, the disconnects probably wouldn't have happened.

I have been a poster boy for disconnect frustration. If this thing works for me, I will be this router's biggest advocate , because it has all the features I need and more.

Fingers crossed again.

You're not the only one with disconnect issues, I had to invoke a ping vb script on my sons pc yesterday, to stop a powerline going to sleep.

 

[ggeinec]

Quick update - After rebooting the Modem and the router, the disconnects seem to have disappeared. I hope this sticks because last time this happened, the Router worked great for 2 weeks and then the disconnects came back(started with interference on 160MHz). This time I hope after 2 weeks it doesn't go back to disconnects.

... snipped ...

I have been a poster boy for disconnect frustration. If this thing works for me, I will be this router's biggest advocate , because it has all the features I need and more.

Silly question, but have you tried temporarily replacing this router with a substitute one just to see if these same issues occur with the substitute router? If not it might be worth a shot.

But I hope these changes do work for you so you can get on with your life.

 

[pb9]

Silly question, but have you tried temporarily replacing this router with a substitute one just to see if these same issues occur with the substitute router? If not it might be worth a shot.

But I hope these changes do work for you so you can get on with your life.

I haven't tried a different router. Going through @L&LD's notes, I realize I haven't gone through the troubleshooting and resetting steps that he put together, so if this happens next time( I am guessing within 2 weeks if it does) I will follow his notes to try and reset. If that doesn't work I will follow the RMA route and try a different router.

 

[yzT]

just registered to post a similar issue, but with AX82U, and found this thread. In my case, I got 2 x AX82U in AiMesh setup, and the ISP's router just as modem.

For several weeks now, I have experienced disconnections as well. Losing about 30-50 ping probes in a row and then recovering again for some time. Happening any device, using wireless or ethernet.

Initially, I thought this was caused due to a little twist I have in my fiber wire, as people say fiber is very fragile, but today I did a test connecting directly to my ISP's router, and 30000 out of 30000 probes succeeded, while the other computers connected to the AX82U had a loss ratio of 1-2%.

So, it's definitively something related with the Asus devices. But... what? What could I do?