What's new

Error WiFi, AX88U Pro, wlceventd, Disassociated due to inactivity

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

azagramac

Regular Contributor
Hi, I purchased this equipment a few days ago (I come from a Ubiquiti network, without a single failure of this type), and randomly I am disconnected certain equipment, the ones that give me more problems are, Alexa speakers, plugs and work computer.

It happens to me in both 2.4Ghz and 5Ghz networks, I have fixed channels, but also in auto, I don't know what else to touch, it happens to me both in OEM firmware and with Merlin firmware.

I have opened a case to Asus, but I do not have many guarantees, I have seen the problem is already known and without solution.

Model: Asus RT-AX88U Pro
Firmware version: 3.0.0.4.388.23110
Tested also firmware Merlin v388.2_2 and 2_0 with the same problems.

Log

Bash:
2023-05-27T01:12:45+02:00 RT-AX88U_Pro-2105841-C wlceventd: wlceventd_proc_event(530): eth6: Auth XX:XX:XX:XX:XX:XX, status: Successful (0), rssi:-44
2023-05-27T01:12:45+02:00 RT-AX88U_Pro-2105841-C wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind XX:XX:XX:XX:XX:XX, status: 0, reason: Unspecified reason (1), rssi:-69
2023-05-27T01:12:45+02:00 RT-AX88U_Pro-2105841-C wlceventd: wlceventd_proc_event(530): eth6: Auth XX:XX:XX:XX:XX:XX, status: Successful (0), rssi:-45
2023-05-27T01:12:45+02:00 RT-AX88U_Pro-2105841-C wlceventd: wlceventd_proc_event(559): eth6: Assoc XX:XX:XX:XX:XX:XX, status: Successful (0), rssi:-45
2023-05-27T01:13:00+02:00 RT-AX88U_Pro-2105841-C wlceventd: wlceventd_proc_event(511): eth6: Disassoc XX:XX:XX:XX:XX:XX, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
2023-05-27T01:13:00+02:00 RT-AX88U_Pro-2105841-C wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind XX:XX:XX:XX:XX:XX, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
2023-05-27T01:13:04+02:00 RT-AX88U_Pro-2105841-C wlceventd: wlceventd_proc_event(530): eth6: Auth XX:XX:XX:XX:XX:XX, status: Successful (0), rssi:-45
2023-05-27T01:13:04+02:00 RT-AX88U_Pro-2105841-C wlceventd: wlceventd_proc_event(559): eth6: Assoc XX:XX:XX:XX:XX:XX, status: Successful (0), rssi:-44
2023-05-27T01:13:18+02:00 RT-AX88U_Pro-2105841-C wlceventd: wlceventd_proc_event(511): eth6: Disassoc XX:XX:XX:XX:XX:XX, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
2023-05-27T01:13:18+02:00 RT-AX88U_Pro-2105841-C wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind XX:XX:XX:XX:XX:XX, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
2023-05-27T01:13:22+02:00 RT-AX88U_Pro-2105841-C wlceventd: wlceventd_proc_event(530): eth6: Auth XX:XX:XX:XX:XX:XX, status: Successful (0), rssi:-45
2023-05-27T01:13:22+02:00 RT-AX88U_Pro-2105841-C wlceventd: wlceventd_proc_event(559): eth6: Assoc XX:XX:XX:XX:XX:XX, status: Successful (0), rssi:-70
2023-05-27T01:13:37+02:00 RT-AX88U_Pro-2105841-C wlceventd: wlceventd_proc_event(511): eth6: Disassoc XX:XX:XX:XX:XX:XX, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
2023-05-27T01:13:37+02:00 RT-AX88U_Pro-2105841-C wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind XX:XX:XX:XX:XX:XX, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
2023-05-27T01:13:41+02:00 RT-AX88U_Pro-2105841-C wlceventd: wlceventd_proc_event(530): eth6: Auth XX:XX:XX:XX:XX:XX, status: Successful (0), rssi:-45
2023-05-27T01:13:41+02:00 RT-AX88U_Pro-2105841-C wlceventd: wlceventd_proc_event(559): eth6: Assoc XX:XX:XX:XX:XX:XX, status: Successful (0), rssi:-50
2023-05-27T01:13:55+02:00 RT-AX88U_Pro-2105841-C wlceventd: wlceventd_proc_event(511): eth6: Disassoc XX:XX:XX:XX:XX:XX, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
2023-05-27T01:13:55+02:00 RT-AX88U_Pro-2105841-C wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind XX:XX:XX:XX:XX:XX, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
2023-05-27T01:13:59+02:00 RT-AX88U_Pro-2105841-C wlceventd: wlceventd_proc_event(530): eth6: Auth XX:XX:XX:XX:XX:XX, status: Successful (0), rssi:-45
2023-05-27T01:13:59+02:00 RT-AX88U_Pro-2105841-C wlceventd: wlceventd_proc_event(559): eth6: Assoc XX:XX:XX:XX:XX:XX, status: Successful (0), rssi:-50
2023-05-27T01:14:14+02:00 RT-AX88U_Pro-2105841-C wlceventd: wlceventd_proc_event(511): eth6: Disassoc XX:XX:XX:XX:XX:XX, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
2023-05-27T01:14:14+02:00 RT-AX88U_Pro-2105841-C wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind XX:XX:XX:XX:XX:XX, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
2023-05-27T01:14:18+02:00 RT-AX88U_Pro-2105841-C wlceventd: wlceventd_proc_event(530): eth6: Auth XX:XX:XX:XX:XX:XX, status: Successful (0), rssi:-45
2023-05-27T01:14:18+02:00 RT-AX88U_Pro-2105841-C wlceventd: wlceventd_proc_event(559): eth6: Assoc XX:XX:XX:XX:XX:XX, status: Successful (0), rssi:-44
 
Last edited:
Hi, I purchased this equipment a few days ago (I come from a Ubiquiti network, without a single failure of this type), and randomly I am disconnected certain equipment, the ones that give me more problems are, Alexa speakers, plugs and work computer.

Don't worry about it - it's likely a phone goes into power save mode...
 
Yes, that is a common occurance with cell phones.
 
I too have had those log entries in the past but my current setup does not exhibit this behavior but I do have AX wifi capabilities disabled. I only have 3 AX capable devices but with my ISP bandwidth it’s not really a factor for me.
 
Good morning, thank you for your answers.

But precisely the connected mobiles (2 OnePlus mobiles (6 and 8T) do not have these disconnections).

I have checked the log during the night, and the Alexa Studio has disconnected more than 30 times, a SonOff switchboard more than 50 and the Xiaomi vacuum cleaner 12 times. 😥🤦🏻‍♂️

I will delete the NVRAM and install the firmware v9.0.0.6.102.4856

Just to rule it out. I can't have a computer with these problems, the AX network has been unsuccessfully disabled on both network 2.4 and 5.


Update.
Installed firmware 9.0.0.6.102_4856, I confirm that it still happens.

I will look for alternatives, in Asus or another brand, I can not have a computer that does not let me neither work nor control the devices at home, and less with the cost that has the equipment.


Here you can see how the device with the MAC address ending in 63:9F, which is a Xiaomi hoover, is disconnected several times.
This happens in both 2.4Ghz and 5Ghz networks, with or without AX mode activated.
1685174010919.png


2.4Ghz
1685174222909.png


5Ghz
1685174328574.png
 
Last edited:
I forgot to mention that I have Roaming Assistant turned off in the Professional tab. I have found that it does not really work very well even on systems with an AiMesh node(s).

Since I am not running any mesh, it is certainly not needed.

It too will cause devices to disconnect because the router will disconnect them in an attempt to make the device switch to a closer node.

Make sure you turn it off on both wifi bands.

Also in the Proffessional tab, 2.4g band, I have the Modulation Scheme set to MCS 7 802.11n for best compatibility.

Here are my settings on the 2.4 band
 

Attachments

  • IMG_0638.jpeg
    IMG_0638.jpeg
    66.2 KB · Views: 153
Last edited:
Thanks you @Smokey613 for your help, I have made the changes you mentioned, I will test it for a few hours and I will comment on the news.

Thank you very much for your help


1685188998696.png



Update
I have made the changes, both in firmware 9.0.0.6.102_4856 and 3.0.0.4.388_22250 (by deleting the NVRAM before installing and after).

And I have the same problems.
1685195225274.png
 
Last edited:
Doesn't sound like your router is in a good/known state.

I suggest fully resetting the router, do not use a saved backup config file, and minimally and manually configuring it to secure it and connect to your ISP.

After doing the above (with the specific steps indicated for your router in the link below), keep in mind that toggling options on/off are not the same as leaving the options off in the first place. If you do toggle things to see what they do, a full reset will be the quickest way back to a router and network that is in a good/known state.



 
As has been mentioned before, everyone’s environment is unique. We can tell what settings we use as a reference but it is not a guarantee it will work for you.

2.4g wifi IoT devices are notorious for having the lowest cost wifi components which can cause a lot of issues.
 
Doesn't sound like your router is in a good/known state.

I suggest fully resetting the router, do not use a saved backup config file, and minimally and manually configuring it to secure it and connect to your ISP.

After doing the above (with the specific steps indicated for your router in the link below), keep in mind that toggling options on/off are not the same as leaving the options off in the first place. If you do toggle things to see what they do, a full reset will be the quickest way back to a router and network that is in a good/known state.



Restore the router and I have done it several times this week, today 3 times, and always deleting the NVRAM before installing the firmware and then as I said before, I never restore file because I know the problems that brings even more when it is a different version.

The router is new, bought this week, I have already tried the official firmwares, the stable and beta versions available on the asus website, as well as the 2 available today from merlin.

I have opened a ticket to asus for this same problem, I have already provided the syslog, traces, screenshots, etc ... even the link to this thread, but their response is not exactly very interested in solving the problem even though as they told me they have known about it for some time.

If I can't fix it somehow, I'll return it and go back to the AX58U, which didn't have these problems.
 
Last edited:
There was an Airtime Fairness glitch, enabled and some IoT devices had trouble staying connected (or wouldn't connect).

Not sure if that was ever addressed on the AP side -

On the client side, it was older firmware from Espressif that had the issue on their side... and these chips are everywhere as they are basically an all-in-one solution, not just WiFi, but the MCU side, along with UART support for sensors, etc...
 
There was an Airtime Fairness glitch, enabled and some IoT devices had trouble staying connected (or wouldn't connect).

Not sure if that was ever addressed on the AP side -

On the client side, it was older firmware from Espressif that had the issue on their side... and these chips are everywhere as they are basically an all-in-one solution, not just WiFi, but the MCU side, along with UART support for sensors, etc...
It gives me problems in Alexa speakers, 2 FireTV, xioami vacuum cleaner... and the laptop at work, I can't work over wifi because it disconnects me every few minutes, they are the most affected.

And to a lesser extent a couple of SonOff plugs and a zigbee bridge also from SonOff.
 
Good morning, thank you for your answers.

But precisely the connected mobiles (2 OnePlus mobiles (6 and 8T) do not have these disconnections).

I have checked the log during the night, and the Alexa Studio has disconnected more than 30 times, a SonOff switchboard more than 50 and the Xiaomi vacuum cleaner 12 times. 😥🤦🏻‍♂️

I will delete the NVRAM and install the firmware v9.0.0.6.102.4856

Just to rule it out. I can't have a computer with these problems, the AX network has been unsuccessfully disabled on both network 2.4 and 5.


Update.
Installed firmware 9.0.0.6.102_4856, I confirm that it still happens.

I will look for alternatives, in Asus or another brand, I can not have a computer that does not let me neither work nor control the devices at home, and less with the cost that has the equipment.


Here you can see how the device with the MAC address ending in 63:9F, which is a Xiaomi hoover, is disconnected several times.
This happens in both 2.4Ghz and 5Ghz networks, with or without AX mode activated.
View attachment 50409

2.4Ghz
View attachment 50410

5Ghz
View attachment 50411
Unhide the SSID's and things should stay connected
 
I have always had the SSID hidden, in all my routers, more than 1 year with Ubiquiti with the SSID hidden and now this router if I hide it gives problems?

What a piece of crap then.

Could you reason me the reasons why to show the SSID?
 
I have always had the SSID hidden, in all my routers, more than 1 year with Ubiquiti with the SSID hidden and now this router if I hide it gives problems?

What a piece of crap then.

Could you reason me the reasons why to show the SSID?
Devices sometimes have a problem with a hidden SSID. Unhide them and reboot the router and see if your issue persists.
 
Check the traces that I uploaded above, by the way I have made it visible between tests and version changes and it happens anyway.
 
Some people believe hiding the ssid makes the WiFi more secure. The fact is it makes wifi less secure - the connecting devices transmit the ssid in the open.
 
It has me desperate, that gives me problems the vacuum cleaner is the least of the problems, but I have the Alexa speakers crazy with disconnections, since you tell them a voice command and now responds to me that it has connection problems, it touches unplug and plug the speaker back in, but the worst is the work computer.

It's not comfortable to be like this, I'm going to ask for a refund, a shame, because it's a great equipment, but it works very badly.
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top