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

[jzchen]

Hi jzchen,
yes, I'm in Italy. I don't tink the problem is related to weak signal: router al very close to other device (when I was saying yesterday that I had problems with my laptop I was practically in front of him...). Moreover, why whit old firmware everithing works fine?

In the end I decided to stop, I don't want to waste any more time doing tests and various tricks: I'll send back the router and I will buy the GL.iNet GL-MT6000(Flint 2). I'm sorry to abandon Asus but I have no other options and I don't want to risk having the same problem again with other models...

The thing that bothers me the most is the lack of response from their customer service: they only responded to the first report but then never got back to me... We are talking about a high-end router costing several hundred euros, I believe it's essential that those high-level products are perfect and that customer service is attentive to the various complaints that come in...

If you're interested, I'll tell you how my devices will behave with the new router...

Have a nice day to you all!

Sorry to read they were not able to resolve your issues in a timely manner, and resulted in you moving on to a different brand. You've been really patient as you started this thread way back in March.

I have seen the GL.iNet around the net. I should probably do some more research into their products...

 

[neo2_hason]

I do have also the same issue like you guys. I did contact Asus but they want to send a feedback directly from router. I did send them logs but this was not enough.
I have latest merlin firmware 3006.102.5.

I did try a lot already by myself. Including deactivation of all advanced features etc. But de-auth is still comming back after few hrs.

Sep 21 22:01:57 wlceventd: wlceventd_proc_event(685): wl0.1: Auth 50:D4:F7:7F:EC:C8, status: Successful (0), rssi:0
Sep 21 22:01:57 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind D8:0D:17:3E:73:E7, status: 0, reason: Unspecified reason (1), rssi:0
Sep 21 22:01:57 wlceventd: wlceventd_proc_event(685): wl0.1: Auth D8:0D:17:3E:73:E7, status: Successful (0), rssi:0
Sep 21 22:01:57 kernel: SBF: dhd0: INIT [50:d4:f7:7f:ec:c8] ID 65535 BFW 65535 THRSH 2048
Sep 21 22:01:57 wlceventd: wlceventd_proc_event(722): wl0.1: Assoc 50:D4:F7:7F:EC:C8, status: Successful (0), rssi:-45
Sep 21 22:01:57 kernel: SBF: dhd0: INIT [d8:0d:17:3e:73:e7] ID 65535 BFW 65535 THRSH 2048
Sep 21 22:01:57 wlceventd: wlceventd_proc_event(722): wl0.1: Assoc D8:0D:17:3E:73:E7, status: Successful (0), rssi:-37
Sep 21 22:15:47 wlceventd: wlceventd_proc_event(645): wl1.1: Deauth_ind BA:64:83:50:CC:21, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Sep 21 22:15:47 wlceventd: wlceventd_proc_event(662): wl1.1: Disassoc BA:64:83:50:CC:21, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Sep 22 01:05:23 wlceventd: wlceventd_proc_event(685): wl0.1: Auth 00:24:E4:ED:01:6C, status: Successful (0), rssi:-81
Sep 22 01:05:23 kernel: SBF: dhd0: INIT [00:24:e4:ed:01:6c] ID 65535 BFW 65535 THRSH 2048
Sep 22 01:05:23 wlceventd: wlceventd_proc_event(722): wl0.1: Assoc 00:24:E4:ED:01:6C, status: Successful (0), rssi:-81
Sep 22 01:05:31 wlceventd: wlceventd_proc_event(662): wl0.1: Disassoc 00:24:E4:ED:01:6C, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Sep 22 01:05:31 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind 00:24:E4:ED:01:6C, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Sep 22 02:00:04 SIG_UPDATE: current sig : 2472
Sep 22 02:00:04 SIG_UPDATE: latest sig : 2472

Sep 22 05:32:17 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind 20:F8:3B:09:A9:0C, status: 0, reason: Unspecified reason (1), rssi:-55
Sep 22 05:32:17 wlceventd: wlceventd_proc_event(685): wl0.1: Auth 20:F8:3B:09:A9:0C, status: Successful (0), rssi:-55
Sep 22 05:32:17 kernel: SBF: dhd0: INIT [20:f8:3b:09:a9:0c] ID 65535 BFW 65535 THRSH 2048
Sep 22 05:32:17 wlceventd: wlceventd_proc_event(722): wl0.1: Assoc 20:F8:3B:09:A9:0C, status: Successful (0), rssi:-55
Sep 22 05:32:17 wlceventd: wlceventd_proc_event(685): wl0.1: Auth B8:16:5F:05:E0:8E, status: Successful (0), rssi:-43
Sep 22 05:32:17 kernel: SBF: dhd0: INIT [b8:16:5f:05:e0:8e] ID 65535 BFW 65535 THRSH 2048
Sep 22 05:32:17 wlceventd: wlceventd_proc_event(722): wl0.1: Assoc B8:16:5F:05:E0:8E, status: Successful (0), rssi:-43
Sep 22 05:32:18 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind 50:D4:F7:7F:EC:C8, status: 0, reason: Unspecified reason (1), rssi:-48
Sep 22 05:32:18 wlceventd: wlceventd_proc_event(685): wl0.1: Auth 50:D4:F7:7F:EC:C8, status: Successful (0), rssi:-48
Sep 22 05:32:18 kernel: SBF: dhd0: INIT [50:d4:f7:7f:ec:c8] ID 65535 BFW 65535 THRSH 2048
Sep 22 05:32:18 wlceventd: wlceventd_proc_event(722): wl0.1: Assoc 50:D4:F7:7F:EC:C8, status: Successful (0), rssi:-48
Sep 22 05:32:18 wlceventd: wlceventd_proc_event(685): wl0.2: Auth 24:2F:D0:63:52:43, status: Successful (0), rssi:-66
Sep 22 05:32:18 kernel: SBF: dhd0: INIT [24:2f:d0:63:52:43] ID 65535 BFW 65535 THRSH 2048
Sep 22 05:32:18 wlceventd: wlceventd_proc_event(722): wl0.2: Assoc 24:2F:D0:63:52:43, status: Successful (0), rssi:-66
Sep 22 05:32:18 wlceventd: wlceventd_proc_event(645): wl0.2: Deauth_ind 74:4D:BD:CE:65:DC, status: 0, reason: 4-way handshake timeout (f), rssi:0
Sep 22 05:32:18 wlceventd: wlceventd_proc_event(685): wl0.2: Auth 74:4D:BD:CE:65:DC, status: Successful (0), rssi:-30
Sep 22 05:32:18 kernel: SBF: dhd0: INIT [74:4d:bd:ce:65:dc] ID 65535 BFW 65535 THRSH 2048
Sep 22 05:32:18 wlceventd: wlceventd_proc_event(722): wl0.2: Assoc 74:4D:BD:CE:65:DC, status: Successful (0), rssi:-30
Sep 22 05:32:21 wlceventd: wlceventd_proc_event(645): wl0.2: Deauth_ind 3C:84:27:CC:40:D8, status: 0, reason: Unspecified reason (1), rssi:0
Sep 22 05:32:22 wlceventd: wlceventd_proc_event(685): wl0.2: Auth 3C:84:27:CC:40:D8, status: Successful (0), rssi:-40
Sep 22 05:32:22 kernel: SBF: dhd0: INIT [3c:84:27:cc:40:d8] ID 65535 BFW 65535 THRSH 2048
Sep 22 05:32:22 wlceventd: wlceventd_proc_event(722): wl0.2: Assoc 3C:84:27:CC:40:D8, status: Successful (0), rssi:-40
Sep 22 05:32:23 wlceventd: wlceventd_proc_event(645): wl0.2: Deauth_ind DC:DA:0C:39:F8:68, status: 0, reason: Unspecified reason (1), rssi:0
Sep 22 05:32:23 wlceventd: wlceventd_proc_event(685): wl0.2: Auth DC:DA:0C:39:F8:68, status: Successful (0), rssi:-58
Sep 22 05:32:23 kernel: SBF: dhd0: INIT [dc:da:0c:39:f8:68] ID 65535 BFW 65535 THRSH 2048
Sep 22 05:32:23 wlceventd: wlceventd_proc_event(722): wl0.2: Assoc DC:DA:0C:39:F8:68, status: Successful (0), rssi:-58
Sep 22 05:32:30 wlceventd: wlceventd_proc_event(645): wl0.2: Deauth_ind 3C:84:27:CC:40:D8, status: 0, reason: Unspecified reason (1), rssi:-39
Sep 22 05:32:30 wlceventd: wlceventd_proc_event(685): wl0.2: Auth 3C:84:27:CC:40:D8, status: Successful (0), rssi:-39
Sep 22 05:32:30 kernel: SBF: dhd0: INIT [3c:84:27:cc:40:d8] ID 65535 BFW 65535 THRSH 2048
Sep 22 05:32:30 wlceventd: wlceventd_proc_event(722): wl0.2: Assoc 3C:84:27:CC:40:D8, status: Successful (0), rssi:-39
Sep 22 05:44:29 WATCHDOG: [FAUPGRADE][auto_firmware_check_merlin:(12094)]do webs_update
Sep 22 05:44:59 WATCHDOG: [FAUPGRADE][auto_firmware_check_merlin:(12094)]do webs_update

 

[zaky]

I just stumbled on this thread and it seems like I wasn't the only one suffering with these deauth issues. In my case I found that it was due to one problematic / compromised IoT device. Still not quite sure how...

If you happen to be having this issue and stumble on this thread, check out my similar thread here: https://www.snbforums.com/threads/n...ly-deauthing-disconnecting.92924/#post-944226.

I still feel that tech support should be able to troubleshoot this issue better - clearly many are struggling.

 

[jammy8911]

I also just found this thread, I am seeing similar issues. Did anyone ever get to the bottom of it or anyone else also seeing this?

@zaky I read through your thread and it doesnt seem to be exactly the same as me since you mentioned even your 5ghz devices arent safe. However all my 5ghz are perfect, its just 2.4ghz.

 

[zaky]

Hi Jammy, FYI my original issue was 95%+ of the time with 2.4, so I'd still take the same approach. After going through all the normal troubleshooting steps/settings that they recommend, start taking devices off your network to see if the behavior improves after a certain point. In my case, finding that one problematic device (AND possibly setting all the other settings they recommended?) pretty much solved my day to day issue.

All that said, my router definitely hasn't been 100% flawless after that. Like.. recently my I started getting occasional internet connectivity issues on my devices that required a factory reset and a DNS server setting update. Not related to our above issue, just wanted to mention that this router hasn't necessarily been as stable as I would have expected when purchasing.

 

[TSS]

If you're interested, I'll tell you how my devices will behave with the new router...

Yes, we are interested!
I own RT-AX86U Pro and also have a lot of these Auth Deauth Assoc Disassoc events in log. I believe we stuck with this and Asus can't / don't want to fix it.

But I'm very interesting about your adventure with GL.iNet GL-MT6000(Flint 2) (if you get one).

 

[jammy8911]

Hi Jammy, FYI my original issue was 95%+ of the time with 2.4, so I'd still take the same approach. After going through all the normal troubleshooting steps/settings that they recommend, start taking devices off your network to see if the behavior improves after a certain point. In my case, finding that one problematic device (AND possibly setting all the other settings they recommended?) pretty much solved my day to day issue.

All that said, my router definitely hasn't been 100% flawless after that. Like.. recently my I started getting occasional internet connectivity issues on my devices that required a factory reset and a DNS server setting update. Not related to our above issue, just wanted to mention that this router hasn't necessarily been as stable as I would have expected when purchasing.

This is the exact same behavior I have observed. Since Christmas, I have removed many 2.4ghz devices such as smart plugs, bulbs, controllers as my Christmas lights have come down. Since then the issue has reduced in frequency, now only occurring once a week or two. I am confused as to why the number of devices has an impact on this issue. Its not like I am using hundreds, I am talking about a difference of around 10-15 devices.