ASUS RT-BE88U - WiFi 2.4GHz drop with "Deauth_ind Unspecified reason (1), rssi:0"

[dandy585]

Hi all,
I'm going to tell you about a problem I've had for a while and it's driving me crazy...

My router worked very well until firmware 3.0.0.6.102_37094. When I have installed it (without any problem during the process), my IoT devices on 2.4GHz wifi networlk started to disconnect. It seems to occur in "random" way: they can stay connect for 1, 2, 3 hours (or more) and then stop working util I manually reboot the router (reboot the devieces doesn't resolve the situation).

The problem only occur for 2.4GHz band, I need it for some devices that operate only on this modality. I've try several configuration but nothing resolve: disabled smart connect (to force all devices on 2.4GHz, even if someone can operate at 5GHz), set AP isolated on IoT network, disable Beamforming, MIMO, WMM APSD, set WiFi 5 scheme to MCS 7 (802.11n), use fixed channel/band... I also try to hard reset the router (with WPS button and power on procedure)... Nothing works !

When the error occured, the system logs have always the same behaviour: these lines repeated hundred of times

Mar 27 11:30:50 wlceventd: wlceventd_proc_event(656): wl0.2: Deauth_ind E8:C7:CF:64:44:FA, status: 0, reason: Unspecified reason (1), rssi:0
Mar 27 11:30:50 wlceventd: wlceventd_proc_event(696): wl0.2: Auth E8:C7:CF:64:44:FA, status: Successful (0), rssi:0

I searched a lot for similar issue, I found similar problem with IoT/2.4GHz network but nothing with those specific error infinitely repeated (system logs in this case report information regarding "sending station is leaving (or has left) BSS
"). Anyway, as told, all the tentative I've done was unsusseffully.

Do you have any suggestion for me? I also contacted Asus support, in case my router has a hardware problem or if there was really a bug in the firmware. If they tell me someting I'll share the information with you in case it might be useful to someone else.

For the moment... Thanks a lot for your time and attention!

Have a nice day!

 

[degrub]

What happened when you reverted to the older firmware and factory reset the router and hand configured the router ?

 

[dandy585]

I'll need to try... Sincerely, I dont want to proceed with downgrade but if I cant find any other solution ...

 

[Ripshod]

Stab in the dark. By any chance are you routing traffic through a wireguard VPN?

 

[dandy585]

No, VPN isn't used. At the moment Asus support as suggest to force channel bandwidth at 20MHz and send it the log if the issue persist (surelly, because I've already made this test ).

I'm seriuosly intended to try downgrade the firmware to check and have the certainty that the issue is related to a buggy firmware... Do you have any contraindications regarding this ?

Thanks guys!

 

[HPDeskjet]

I am having the same problem on 2.4 GHz with the RT-BE88U. That's with the Asuswrt-Merlin latest firmware 3006.102.3. Clients using 2.4GHz keep disconnecting and reconnecting.

Mar 28 20:24:47 wlceventd: wlceventd_proc_event(685): wl0: Auth FC:3C: 7:E7:F9:35, status: Successful (0), rssi:0
Mar 28 20:24:51 wlceventd: wlceventd_proc_event(645): wl0: Deauth_ind FC:3C: 7:E7:F9:35, status: 0, reason: Unspecified reason (1), rssi:0

 

[jzchen]

Do you have a mobile device that you can use to download a network analyzer type of app and scan? 0 dBm means there is no signal.

 

[Ripshod]

@dandy585 @HPDeskjet Can you identify this device from it's MAC? I've seen this happen when a device outside of my home has been trying to connect to my network (tuya anyone). Was giving the same 0dB (which means it's not actually connecting, just trying). If it's not your device block it in the MAC filters.

 

[sfx2000]

HInt - perhaps turn off roaming assistant

 

[dandy585]

@jzchen in my case the devices with the issue are two thermostats (of different brand) that operate only in 2.4GHz. Anyway, when the problem occurs all the device in 2.4GHz are disconnected. With smart connect enabled the device on IoT network that could operate in 5GHz continue to works but because they switch to this band. Otherwise, if I disable smart connect and set the network on 2.4GHz, when the error start to appear in system log all the device going offline. This behaviour suggest me the problem is not device related, but affect the router when operate at 2.4GHz

@Ripshod there are no MAC filters.

@sfx2000 roaming assistant is off.

Today I've replied to ASUS support because (as I feared) force channel bandwidth at 20MHz don't solve the situation.
If it coul be usefull, I'll post the system logs when the error begin

Mar 30 05:02:00 kernel: WLC_SCB_DEAUTHORIZE error (-30)
Mar 30 05:02:00 kernel: WLC_SCB_DEAUTHENTICATE_FOR_REASON err -30
Mar 30 05:02:00 wlceventd: wlceventd_proc_event(656): wl1.2: Deauth_ind 00:9E:C8:B3:12:63, status: 0, reason: Group key update timeout (10), rssi:-71
Mar 30 05:02:00 kernel: WLC_SCB_DEAUTHORIZE error (-30)
Mar 30 05:02:01 wlceventd: wlceventd_proc_event(656): wl1.2: Deauth_ind 00:9E:C8:B3:12:63, status: 0, reason: Group key update timeout (10), rssi:-71
Mar 30 05:09:07 wlceventd: wlceventd_proc_event(696): wl1.2: Auth 00:9E:C8:B3:12:63, status: Successful (0), rssi:-76
Mar 30 05:09:07 kernel: SBF: dhd1: INIT [00:9e:c8:b3:12:63] ID 65535 BFW 65535 THRSH 2048
Mar 30 05:09:07 wlceventd: wlceventd_proc_event(733): wl1.2: Assoc 00:9E:C8:B3:12:63, status: Successful (0), rssi:-76
Mar 30 05:25:03 wlceventd: wlceventd_proc_event(656): wl0.2: Deauth_ind A2:D5:AF:52:B8:85, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Mar 30 05:25:03 wlceventd: wlceventd_proc_event(673): wl0.2: Disassoc A2:D5:AF:52:B8:85, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar 30 05:26:44 wlceventd: wlceventd_proc_event(673): wl0.2: Disassoc 0C:B8:15:54:C8:24, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar 30 05:26:44 wlceventd: wlceventd_proc_event(656): wl0.2: Deauth_ind 0C:B8:15:54:C8:24, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Mar 30 05:26:53 wlceventd: wlceventd_proc_event(696): wl1.2: Auth A2:D5:AF:52:B8:85, status: Successful (0), rssi:0
Mar 30 05:26:53 kernel: SBF: dhd1: INIT [a2:d5:af:52:b8:85] ID 65535 BFW 65535 THRSH 2048
Mar 30 05:26:53 wlceventd: wlceventd_proc_event(733): wl1.2: Assoc A2:D5:AF:52:B8:85, status: Successful (0), rssi:-49
Mar 30 05:26:56 wlceventd: wlceventd_proc_event(696): wl0.2: Auth 0C:B8:15:54:C8:24, status: Successful (0), rssi:0
Mar 30 05:27:00 wlceventd: wlceventd_proc_event(656): wl0.2: Deauth_ind 0C:B8:15:54:C8:24, status: 0, reason: Unspecified reason (1), rssi:0
Mar 30 05:27:00 wlceventd: wlceventd_proc_event(696): wl0.2: Auth 0C:B8:15:54:C8:24, status: Successful (0), rssi:0
Mar 30 05:27:13 wlceventd: wlceventd_proc_event(656): wl0.2: Deauth_ind 0C:B8:15:54:C8:24, status: 0, reason: Unspecified reason (1), rssi:0
Mar 30 05:27:13 wlceventd: wlceventd_proc_event(696): wl0.2: Auth 0C:B8:15:54:C8:24, status: Successful (0), rssi:0
Mar 30 05:27:17 wlceventd: wlceventd_proc_event(656): wl0.2: Deauth_ind 0C:B8:15:54:C8:24, status: 0, reason: Unspecified reason (1), rssi:0
Mar 30 05:27:17 wlceventd: wlceventd_proc_event(696): wl0.2: Auth 0C:B8:15:54:C8:24, status: Successful (0), rssi:0
Mar 30 05:27:31 wlceventd: wlceventd_proc_event(656): wl0.2: Deauth_ind 0C:B8:15:54:C8:24, status: 0, reason: Unspecified reason (1), rssi:0
Mar 30 05:27:31 wlceventd: wlceventd_proc_event(696): wl0.2: Auth 0C:B8:15:54:C8:24, status: Successful (0), rssi:0
Mar 30 05:27:35 wlceventd: wlceventd_proc_event(656): wl0.2: Deauth_ind 0C:B8:15:54:C8:24, status: 0, reason: Unspecified reason (1), rssi:0
Mar 30 05:27:35 wlceventd: wlceventd_proc_event(696): wl0.2: Auth 0C:B8:15:54:C8:24, status: Successful (0), rssi:0
Mar 30 05:27:50 wlceventd: wlceventd_proc_event(656): wl0.2: Deauth_ind 0C:B8:15:54:C8:24, status: 0, reason: Unspecified reason (1), rssi:0
Mar 30 05:27:50 wlceventd: wlceventd_proc_event(696): wl0.2: Auth 0C:B8:15:54:C8:24, status: Successful (0), rssi:0
Mar 30 05:27:54 wlceventd: wlceventd_proc_event(656): wl0.2: Deauth_ind 0C:B8:15:54:C8:24, status: 0, reason: Unspecified reason (1), rssi:0
Mar 30 05:27:54 wlceventd: wlceventd_proc_event(696): wl0.2: Auth 0C:B8:15:54:C8:24, status: Successful (0), rssi:0
Mar 30 05:28:08 wlceventd: wlceventd_proc_event(656): wl0.2: Deauth_ind 0C:B8:15:54:C8:24, status: 0, reason: Unspecified reason (1), rssi:0
Mar 30 05:28:08 wlceventd: wlceventd_proc_event(696): wl0.2: Auth 0C:B8:15:54:C8:24, status: Successful (0), rssi:0
Mar 30 05:28:12 wlceventd: wlceventd_proc_event(656): wl0.2: Deauth_ind 0C:B8:15:54:C8:24, status: 0, reason: Unspecified reason (1), rssi:0
Mar 30 05:28:12 wlceventd: wlceventd_proc_event(696): wl0.2: Auth 0C:B8:15:54:C8:24, status: Successful (0), rssi:0
Mar 30 05:28:26 wlceventd: wlceventd_proc_event(656): wl0.2: Deauth_ind 0C:B8:15:54:C8:24, status: 0, reason: Unspecified reason (1), rssi:0
Mar 30 05:28:26 wlceventd: wlceventd_proc_event(696): wl0.2: Auth 0C:B8:15:54:C8:24, status: Successful (0), rssi:0

Very sad ! Anyway, do you think there are any drawbacks to downgrading while waiting for a firmware that doesn't have the problem?