ASUS RT-BE92U

[Hypothosis]

with the above config workign ok so far

4 days 1 hour(s) 8 minute(s) 55 seconds

​

 

[Hypothosis]

so no crashes, that's good. but it'll just stop communicating once in a while. it's very annoying. fix is to manually disconnect and reconnect.

May 9 21:53:44 wlceventd: wlceventd_proc_event(696): wl1.1: Auth 4C:49:6C:96:29:95, status: Successful (0), rssi:0
May 9 21:53:44 wlceventd: wlceventd_proc_event(706): wl1.1: ReAssoc 4C:49:6C:96:29:95, status: Successful (0), rssi:-71
May 9 21:53:44 wlceventd: wlceventd_proc_event(656): wl2.1: Deauth_ind 4C:49:6C:96:29:95, status: 0, reason: Previous authentication no longer valid (2), rssi:-78
May 9 21:53:45 wlceventd: wlceventd_proc_event(656): wl2.1: Deauth_ind 4C:49:6C:96:29:95, status: 0, reason: Disassociated due to inactivity (4), rssi:-78
May 9 21:55:55 wlceventd: wlceventd_proc_event(656): wl1.1: Deauth_ind 4C:49:6C:96:29:95, status: 0, reason: Unspecified reason (1), rssi:0
May 9 21:55:55 wlceventd: wlceventd_proc_event(673): wl1.1: Disassoc 4C:49:6C:96:29:95, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 9 21:55:59 wlceventd: wlceventd_proc_event(733): wl2.1: Assoc 4C:49:6C:96:29:95, status: Successful (0), rssi:-78

 

[degrub]

Energy saving settings come to mind - either the client device or the AP.
Those RSSI values are pretty weak too.

 

[Rajjco]

so no crashes, that's good. but it'll just stop communicating once in a while. it's very annoying. fix is to manually disconnect and reconnect.

May 9 21:53:44 wlceventd: wlceventd_proc_event(696): wl1.1: Auth 4C:49:6C:96:29:95, status: Successful (0), rssi:0
May 9 21:53:44 wlceventd: wlceventd_proc_event(706): wl1.1: ReAssoc 4C:49:6C:96:29:95, status: Successful (0), rssi:-71
May 9 21:53:44 wlceventd: wlceventd_proc_event(656): wl2.1: Deauth_ind 4C:49:6C:96:29:95, status: 0, reason: Previous authentication no longer valid (2), rssi:-78
May 9 21:53:45 wlceventd: wlceventd_proc_event(656): wl2.1: Deauth_ind 4C:49:6C:96:29:95, status: 0, reason: Disassociated due to inactivity (4), rssi:-78
May 9 21:55:55 wlceventd: wlceventd_proc_event(656): wl1.1: Deauth_ind 4C:49:6C:96:29:95, status: 0, reason: Unspecified reason (1), rssi:0
May 9 21:55:55 wlceventd: wlceventd_proc_event(673): wl1.1: Disassoc 4C:49:6C:96:29:95, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 9 21:55:59 wlceventd: wlceventd_proc_event(733): wl2.1: Assoc 4C:49:6C:96:29:95, status: Successful (0), rssi:-78

Your client is too far from the router.
You can adjust rssi value to prevent disconnections its under wifi > professional tab.

 

[iFrogMac]

Thought I would post about an unusual issue I had with my RT-BE92U, and it's none of the typical ones being circulated. Never had random reboots, or high CPU, or even random connection drops. This issue is connection related though with a smart light.

My last wiz bulb that I brought with me through the move is about 3 years old now, and it started turning the wrong colors, especially with purple, or pink. It would turn an off white color. So, I did the typical troubleshooting steps of powering off the light and taking it out of the socket to completely cut power, that initially didn't resolve it. So, I rebooted modem, and router, initially that didn't fix it either. So thinking the bulb had started failing with from age, I got a new one, and that one wouldn't stay connected. So, I swapped in my RT-AX86U since it's a dual band vs tri-band, and both issues went away, so it turns out the bulb wasn't bad after all, neither bulb. The new one is now connected, and the old one turns the right colors again. I remember when I first got the BE92U, certain 2.4ghz only smart devices had issues when the 6ghz band was enabled, even with the three networks separated and none of the smart functions such as smart connect, or MLO enabled. The lights are on their own iOT network with WPA2 only, and no other advanced options enabled.

I had done a factory reset a while back, on the BE92U and set it up fresh after the initial few firmware updates. But I haven't done a factory reset since, as things have just been working. Would doing another factory reset and setting it up fresh again be beneficial here, or is this a known issue with this router, to not play nice with older devices, or at least iOT devices.

I have seen reports of 6ghz related issues with this router on Reddit and other forums, and I've seen the other issues mentioned, and Amazon has a banner now for a frequently returned item due to connection issues (i think it says.)

 

[dinko05]

I recently got this router and installed the latest Merlin firmware (3006.102.4). I got everything set up and things seemed to be working great (no high CPU utilization, no random disconnects, etc) until ... the clock randomly resets itself to 1917 (or at least that is what the router reports, chrony reports sometime in 2053). I first suspected a NTP problem so tried all three options (inbuilt ntpd, ntpMerlin with chrony and ntpMerlin with ntpd) and none fixed the issue. I logged things and with chrony (which gives detailed logging), I can see that it is still pinging the NTP servers and gets results back and goes from having an offset in the 10^-3 to 10^+8 or so (so clearly it detects the change). I have no idea what is causing this sudden clock change and I have not seen it reported elsewhere so thought I'd ask.

I even went as far as writing a cron script to check the time every minute and if the offset was too large to reset it (using date -s "@<epoch>") and that also didn't work because supposedly "the date is in the wrong format" (which it wasn't). The weirdest thing is that for a while the `date -s` trick worked and now stopped working.

This was a brand new factory reset router with a clean install of the Merlin firmware.

Does anyone have any idea of how I could debug this further. For now, I am back on my older router because this one is totally unusable (when the clock stops working, a bunch of other things break too).

Any help would be appreciated.

Thanks!

 

[iFrogMac]

I recently got this router and installed the latest Merlin firmware (3006.102.4). I got everything set up and things seemed to be working great (no high CPU utilization, no random disconnects, etc) until ... the clock randomly resets itself to 1917 (or at least that is what the router reports, chrony reports sometime in 2053). I first suspected a NTP problem so tried all three options (inbuilt ntpd, ntpMerlin with chrony and ntpMerlin with ntpd) and none fixed the issue. I logged things and with chrony (which gives detailed logging), I can see that it is still pinging the NTP servers and gets results back and goes from having an offset in the 10^-3 to 10^+8 or so (so clearly it detects the change). I have no idea what is causing this sudden clock change and I have not seen it reported elsewhere so thought I'd ask.

I even went as far as writing a cron script to check the time every minute and if the offset was too large to reset it (using date -s "@<epoch>") and that also didn't work because supposedly "the date is in the wrong format" (which it wasn't). The weirdest thing is that for a while the `date -s` trick worked and now stopped working.

This was a brand new factory reset router with a clean install of the Merlin firmware.

Does anyone have any idea of how I could debug this further. For now, I am back on my older router because this one is totally unusable (when the clock stops working, a bunch of other things break too).

Any help would be appreciated.

Thanks!

Never had those particular issues. This router has usually been stable for me, and why I never returned it when I had the chance. It's only been in the past week I've had any strange issues come up again that seem router specific. I did the WPS reset, and then just turned the router off. Haven't reconfigured it yet.

 

[Spartan]

I recently got this router and installed the latest Merlin firmware (3006.102.4). I got everything set up and things seemed to be working great (no high CPU utilization, no random disconnects, etc) until ... the clock randomly resets itself to 1917 (or at least that is what the router reports, chrony reports sometime in 2053). I first suspected a NTP problem so tried all three options (inbuilt ntpd, ntpMerlin with chrony and ntpMerlin with ntpd) and none fixed the issue. I logged things and with chrony (which gives detailed logging), I can see that it is still pinging the NTP servers and gets results back and goes from having an offset in the 10^-3 to 10^+8 or so (so clearly it detects the change). I have no idea what is causing this sudden clock change and I have not seen it reported elsewhere so thought I'd ask.

I even went as far as writing a cron script to check the time every minute and if the offset was too large to reset it (using date -s "@<epoch>") and that also didn't work because supposedly "the date is in the wrong format" (which it wasn't). The weirdest thing is that for a while the `date -s` trick worked and now stopped working.

This was a brand new factory reset router with a clean install of the Merlin firmware.

Does anyone have any idea of how I could debug this further. For now, I am back on my older router because this one is totally unusable (when the clock stops working, a bunch of other things break too).

Any help would be appreciated.

Thanks!

I've not had a single issue or overheating or disconnenction on both of my BE92Us which are connected in an AiMesh system, running the latest firmware 3.0.0.6.102_37548, not Merlin

 

[virus_59]

It looks like that beamforming isn't working.

 

[virus_59]

First day of owning a "hot trash can" from Asus to replace the AX88U.

Setup, changing regio to US for more power and channels, disassembly, copper installation, disappointment...

Beamforming doesn't seem to work, we're waiting for them to finish it, maybe the speed will increase...

On the graphs from HA on the left is AX88U, then BE92U in stock, then the same + copper.

CPU Load Average in System info is complete nonsense that doesn't reflect reality.

 

[virus_59]

more photos

 

[virus_59]

more photos

 

[virus_59]

more photos

 

[virus_59]

last photo

 

[iFrogMac]

So what's the current verdict for this router? As I've mentioned in the past, it's been mainly stable for me until recently, and just wondering if it's worth hanging onto, or if it's just going to keep getting worse?
To recap, the main issues I've had with mine, are:
1. On initial setup, my amazon smart plugs won't connect easily while the 6Ghz band is enabled, but that can be fixed and have the 6Ghz band continue to function as normal.
2. Lately after I factory reset the router on the current firmware, I had two new issues come up. First, the setup wizard didn't want to function correctly, and DHCP didn't function as it should.
3. There was an issue with one of my smart lights turning the wrong color(s) when connected to this router (recent issue, not long term) Was able to associate the issue with the BE92U as switching to the RT-86U resolved the bub color issue, and also connection issues with the new bulb I got to replace it thinking the bulb was bad. I also thought the 2.4Ghz radio had died too as none of my devices would connect on a fresh setup, but that turned out to be a case of me forgetting to turn off the RT-AX86U after disconnecting it, and the devices connecting to that one instead. So minor issues. I would like to be able to use the router again if for no other reason to have multiple 2.5 G ports available vs just the one on the RT-AX86U. 6Ghz and WiFi 7 are in demand right now. Maybe in a year or so as i upgrade devices and more can take advantage of both.

 

[intmanofawesome]

So what's the current verdict for this router?

0 out of 10. Very disappointing. Getting a refund.

I've given up. I've had it for 3 weeks, and the longest it was up without rebooting was 2 days. I tried it again today, from factory defaults, latest firmware, fresh config, nothing special in config. It wouldn't stay up for more than 5 minutes before rebooting.

I've gone back to my rock solid RT-AC68U while I look for another replacement router.

 

[RMerlin]

0 out of 10. Very disappointing. Getting a refund.

I've given up. I've had it for 3 weeks, and the longest it was up without rebooting was 2 days. I tried it again today, from factory defaults, latest firmware, fresh config, nothing special in config. It wouldn't stay up for more than 5 minutes before rebooting.

I've gone back to my rock solid RT-AC68U while I look for another replacement router.

With such unstability, my first guess would be that you have a defective unit, and would have had it replaced. It's highly unlikely to be THAT unstable for everyone, or there would be much more widespread complains.

 

[Spartan]

0 out of 10. Very disappointing. Getting a refund.

I've given up. I've had it for 3 weeks, and the longest it was up without rebooting was 2 days. I tried it again today, from factory defaults, latest firmware, fresh config, nothing special in config. It wouldn't stay up for more than 5 minutes before rebooting.

I've gone back to my rock solid RT-AC68U while I look for another replacement router.

Must be a lemon man. I have 2 of these routers since 1 month, not 1 disconnection or issue. This is one of the best and most stable routers that I've owned

 

[intmanofawesome]

With such unstability, my first guess would be that you have a defective unit, and would have had it replaced. It's highly unlikely to be THAT unstable for everyone, or there would be much more widespread complains.

I agree. However with the posts here and elsewhere with other experiencing reboots, wi-fi issues, and other stability problems, I can't see any other way. I value stability but I feel there is a reasonable possibility I'll just get another dud if the unit is replaced. Once trust is broken it's hard to regain.

@Spartan The router ticked most of my boxes on it's spec sheet and would have been a good upgrade for my RT-AC68U. I'd have like to have seen either another 10G port and vlan support but recognise it's built to a budget.

 

[iFrogMac]

I was asking the verdict because most of the time I've owned this router it's worked as it should. However, lately it's had the odd issue with my smart devices that has no rational exclamation, especially since the RT-AX86U works as it should on it's latest firmware.
The only two rational possibilities are:
1, the latest firmware has a unique bug
2, the hardware is failing.

Since I've had it too long to return it, was asking if I should just wait for the next firmware update, or does this router now have too many issues, and I should just get rid of it at this point. I was going to wait on firmware, but there seems to be more and more people speaking out and saying, it seems to just be a bad piece of hardware overall.

Edit: I wanted to add something I didn't initially when posting about the latest unexpected, and unexplainable issue I've had with the RT-BE92U. It also seems to affect Amazon Alexa as well. When I use voice control with the bulb(s) that have started acting up when connected to the 2.4Ghz band of the RT-BE92U, the Alexa voice has a more agitated / aggressive tone to it than usual. The only way I've found to resolve both problems, is to use my RT-AX86U over the BE92U. The other observation is, the latest release of the firmware for the AX86U Series is that it includes compatibility with certain iOT devices, while the latest version of firmware for the BE92U does not, so I'm wondering if things have changed, and the BE92U is currently not fully compatible with my devices right now because of this change. Either way, this is a situation I can't explain online, it's something you'd have to see in person. So, I'll leave it at that.