RT-AX5400 going crazy (dropping devices, assigning invalid IPs)

[Bubber]

I bought the RT-AX5400 router a few months ago, and it has been running fine until now (with latest firmware). Starting yesterday, I see some devices being (somehow) kicked from the WiFi. It looks like they connect-disconnect-connect-disconnect "forever" very fast. Also, I see the system log being flooded with hundreds (if not thousands) of lines like this:

Apr 10 23:04:09 wlceventd: wlceventd_proc_event(685): wl0.1: Auth 00:1D:63:78:8C:F4, status: Successful (0), rssi:0
Apr 10 23:04:09 wlceventd: wlceventd_proc_event(722): wl0.1: Assoc 00:1D:63:78:8C:F4, status: Successful (0), rssi:-41
Apr 10 23:04:15 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind C4:5B:BE:87:86:6C, status: 0, reason: Unspecified reason (1), rssi:-57
Apr 10 23:04:15 wlceventd: wlceventd_proc_event(685): wl0.1: Auth C4:5B:BE:87:86:6C, status: Successful (0), rssi:-57
Apr 10 23:04:15 wlceventd: wlceventd_proc_event(722): wl0.1: Assoc C4:5B:BE:87:86:6C, status: Successful (0), rssi:-57

In addition, the DHCP server starts to assign "invalid" IP to some client devices (outside the subnet). The correct subnet is 192.168.31.0/24, but some devices gets 192.168.100.x.

The router has been reset and power-cycled, and the problem pops up within a few hours.

Has anyone seen anything like this before?

BR
Jesper
Denmark

 

[bbunge]

I bought the RT-AX5400 router a few months ago, and it has been running fine until now (with latest firmware). Starting yesterday, I see some devices being (somehow) kicked from the WiFi. It looks like they connect-disconnect-connect-disconnect "forever" very fast. Also, I see the system log being flooded with hundreds (if not thousands) of lines like this:

Apr 10 23:04:09 wlceventd: wlceventd_proc_event(685): wl0.1: Auth 00:1D:63:78:8C:F4, status: Successful (0), rssi:0
Apr 10 23:04:09 wlceventd: wlceventd_proc_event(722): wl0.1: Assoc 00:1D:63:78:8C:F4, status: Successful (0), rssi:-41
Apr 10 23:04:15 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind C4:5B:BE:87:86:6C, status: 0, reason: Unspecified reason (1), rssi:-57
Apr 10 23:04:15 wlceventd: wlceventd_proc_event(685): wl0.1: Auth C4:5B:BE:87:86:6C, status: Successful (0), rssi:-57
Apr 10 23:04:15 wlceventd: wlceventd_proc_event(722): wl0.1: Assoc C4:5B:BE:87:86:6C, status: Successful (0), rssi:-57

In addition, the DHCP server starts to assign "invalid" IP to some client devices (outside the subnet). The correct subnet is 192.168.31.0/24, but some devices gets 192.168.100.x.

The router has been reset and power-cycled, and the problem pops up within a few hours.

Has anyone seen anything like this before?

BR
Jesper
Denmark

Sure. The subnet 192.168.100.0 is the 2.4 Gig Guest WIFI #1

The Auth - Deauth is likely a smart device that is not set up right or not set up at all. Vacuum cleaner maybe?

 

[ColinTaylor]

In addition, the DHCP server starts to assign "invalid" IP to some client devices (outside the subnet). The correct subnet is 192.168.31.0/24, but some devices gets 192.168.100.x.

Correction to the previous post: the 2.4 GHz Guest Wi-Fi #1 (wl0.1) is 192.168.101.x. Are you sure you're seeing 192.168.100.x and not the expected 192.168.101.x?

Even though the log is flooded with these messages how many different MAC addresses are generating them? Is it the same few devices creating the problem messages? Are they all from "wl0.1"?

 

[bennor]

Starting yesterday, I see some devices being (somehow) kicked from the WiFi. It looks like they connect-disconnect-connect-disconnect "forever" very fast. Also, I see the system log being flooded with hundreds (if not thousands) of lines like this:

Apr 10 23:04:09 wlceventd: wlceventd_proc_event(685): wl0.1: Auth 00:1D:63:78:8C:F4, status: Successful (0), rssi:0
Apr 10 23:04:09 wlceventd: wlceventd_proc_event(722): wl0.1: Assoc 00:1D:63:78:8C:F4, status: Successful (0), rssi:-41
Apr 10 23:04:15 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind C4:5B:BE:87:86:6C, status: 0, reason: Unspecified reason (1), rssi:-57
Apr 10 23:04:15 wlceventd: wlceventd_proc_event(685): wl0.1: Auth C4:5B:BE:87:86:6C, status: Successful (0), rssi:-57
Apr 10 23:04:15 wlceventd: wlceventd_proc_event(722): wl0.1: Assoc C4:5B:BE:87:86:6C, status: Successful (0), rssi:-57

In addition, the DHCP server starts to assign "invalid" IP to some client devices (outside the subnet). The correct subnet is 192.168.31.0/24, but some devices gets 192.168.100.x.

It may help if you explain your Asus router setup.
What are your WiFi settings? (post readable screen shots with sensitive information redacted)
Do you have Guest WiFi enabled?
What specific WiFi clients are exhibiting the disconnect/reconnect issue?
Do you have manual IP reservations for the LAN clients configured within the router GUI?
Are you using AiMesh or have a downstream AP router? If yes what are those AiMesh nodes or AP routers?
Are you seeing some devices get 192.168.100.x OR are they receiving 192.168.101.x? As the prior poster indicated IP address ranges 192.168.101.x and 192.168.102.x tend to be used by the Asus router (likely for AiMesh, Guest WiFi, etc.) in addition to what ever IP address the end user sets in the router's GUI LAN page.

 

[Bubber]

Thanks all for your replies!

I only have the AX5400 router (no mesh). However, I did have the guest WiFi on, and yes... I incorrectly remembered it as 192.168.100.x, but it was in fact 192.168.101.x. I do not understand how this setup had been running for months, where all IPs given by the DHCP server were in the 192.168.31.x subnet - also to devices connecting to the guest WiFi. Suddenly, several devices started "behaving".

The first time it happened, the log had 3400-ish auth/deauth log lines over 80-ish minutes. It affected three devices: two (a Zaptec EV charger and a Miele washing machine) on wl0.1 and one on eth5 (An IOT "thingy" reading our electricity meter - by the way, it is a WiFI device, so why does it say "eth5" in the log?).

Other devices just simply lost the connecting to the router. One would reconnect after power-cycling them (Google Nest Mini). Others refused to connect again until I gave the devices the WiFI credentials again (Tapo camera, Bambu Lab 3D-printer).

Right now, I have the Guest WiFi disabled, and all devices now connect to the main WiFi. It has been running for about 6-7 hours now without any problems.

 

[ColinTaylor]

(An IOT "thingy" reading our electricity meter - by the way, it is a WiFI device, so why does it say "eth5" in the log?).

Because eth5 and eth6 are the regular (i.e. non-guest) Wi-Fi interfaces for 2.4GHz and 5GHz respectively.