Release RT-BE92U Firmware 3.0.0.6.102_37435-gdd27f25_1059-g807f7_BB0B 12/23/2024

[iFrogMac]

ASUS RT-BE92U Firmware version 3.0.0.6.102_37435
Version 3.0.0.6.102_37435
54.87 MB
2024/12/23
Please unzip the firmware file, and then verify the checksum.
SHA256: 9c94e8890bfc0233dd00ca868e836d9a5a5fedc3bd118f39a33b7147da160e75

Bug Fixes and Enhancements:
- Resolved enabling Instant Guard could cause unexpected restarts.
- Fixed a potential restart issue when using the Feedback system.
- Fixed MAC Filters limit being restricted to 16, increased to 64.
- Improved device connection stability on MLO Network.
- Enhanced MLO backhaul stability.
See: https://www.asus.com/me-en/supportonly/rt-be92u/helpdesk_bios/

 

[iFrogMac]

Just doing a quick followup. After running several days with the new firmware, everything feels stable and responsive (for my setup.)

Devices reconnected quickly after the update, and have stayed connected since.
Router interface is responsive and smooth.
RAM and CPU load look good.
I can't comment on any of the WiFi 7 specifics at this time since I only have up to WiFi 6E capable devices, and most high demand devices are hard-wired.
So far, no complaints here.

 

[spend2much]

I am considering the acquisition of one of these routers, primarily due to their impressive LAN speeds and the "Smart Home Master" feature tailored for IoT devices. My understanding of networking is somewhat limited, yet I actively engage with numerous smart devices as a hobby. Unfortunately, my current GT-AXE16000 has been experiencing frequent disconnections with these devices. To troubleshoot the issue, I connected several devices directly to the AT&T BGW320, and observed no dropouts during this test.
What are your thoughts on this?

 

[iFrogMac]

I am considering the acquisition of one of these routers, primarily due to their impressive LAN speeds and the "Smart Home Master" feature tailored for IoT devices. My understanding of networking is somewhat limited, yet I actively engage with numerous smart devices as a hobby. Unfortunately, my current GT-AXE16000 has been experiencing frequent disconnections with these devices. To troubleshoot the issue, I connected several devices directly to the AT&T BGW320, and observed no dropouts during this test.
What are your thoughts on this?

I personally have had very few issues with this router. After I did some tweaking of the settings such as turning off Mu-Mimo and other related settings, things have been pretty solid. I don't have any WiFi 7 devices yet so I can't currently comment on that. However, the LAN speeds are great for devices that support those speeds. However, my iPhone 15 Pro Max supports 6E and that worked well in my small apartment. Currently I'm using mine as a dual band router until I get more devices that support the 6ghz. Also because of issues with my provider, I had to slow down my internet plan for stability, but when I had the 2Gig plan this router worked great on supported devices,.

As far as iOT devices, in my experience with Asus routers, they've always been a bit glitchy until the firmware for a particular model matures. When I got my AX86U a couple years ago. I had a lot of issues until I found the right settings and Asus fixed bugs. With this router, the glitches were far less. Right now, no issues at all.

 

[digits n bits]

You’re lucky. So you don’t see the CPU core spikes every five seconds to almost 100% and the thermal core errors in the router logs?

 

[Tech9]

thermal core errors

If you see such things in logs - not normal, perhaps the router you have is defective. Get RMA and send it back.

 

[iFrogMac]

You’re lucky. So you don’t see the CPU core spikes every five seconds to almost 100% and the thermal core errors in the router logs?

Haven't had any of those issues. The highest any of the cores go is maybe 15%, but not even that. The router has never been hot to the touch. I haven't looked at logs. Haven't had any reason to. It just sits there and does what it's supposed to. Like I said in my earlier posts. I only have had a few issues with iOT devices and I sorted that by changing settings.

 

[digits n bits]

If you see such things in logs - not normal, perhaps the router you have is defective. Get RMA and send it back.

Maybe you need to read some more comments because this issue is common among posters here for this router. Not an isolated issue but quite common and still occurs with the latest firmware installed. It’s either the bad firmware or the bad hardware or a combination of both.

 

[digits n bits]

Dec 30 12:52:35 kernel: thermal thermal_zone0: failed to read out thermal zone (-1)
Dec 30 12:52:38 kernel: read_bpcm_reg_direct_keyhole: Wait for completion failed, devAddr 0x3, offset 24, idx 2
Dec 30 12:52:38 kernel: thermal thermal_zone0: Failed to get RAIL 0 temperature, ret=256
Dec 30 12:52:38 kernel: thermal thermal_zone0: Failed to get temperature, ret=-1
Dec 30 12:52:38 kernel: thermal thermal_zone0: failed to read out thermal zone (-1)
Dec 30 12:52:41 kernel: read_bpcm_reg_direct_keyhole: Wait for completion failed, devAddr 0x3, offset 24, idx 2
Dec 30 12:52:41 kernel: thermal thermal_zone0: Failed to get RAIL 0 temperature, ret=256
Dec 30 12:52:41 kernel: thermal thermal_zone0: Failed to get temperature, ret=-1
Dec 30 12:52:41 kernel: thermal thermal_zone0: failed to read out thermal zone (-1)
Dec 30 12:52:44 kernel: read_bpcm_reg_direct_keyhole: Wait for completion failed, devAddr 0x3, offset 24, idx 2
Dec 30 12:52:44 kernel: thermal thermal_zone0: Failed to get RAIL 0 temperature, ret=256
Dec 30 12:52:44 kernel: thermal thermal_zone0: Failed to get temperature, ret=-1
Dec 30 12:52:44 kernel: thermal thermal_zone0: failed to read out thermal zone (-1)
Dec 30 12:52:47 kernel: read_bpcm_reg_direct_keyhole: Wait for completion failed, devAddr 0x3, offset 24, idx 2
Dec 30 12:52:47 kernel: thermal thermal_zone0: Failed to get RAIL 0 temperature, ret=256
Dec 30 12:52:47 kernel: thermal thermal_zone0: Failed to get temperature, ret=-1
Dec 30 12:52:47 kernel: thermal thermal_zone0: failed to read out thermal zone (-1)
Dec 30 12:52:48 wlceventd: wlceventd_proc_event(656): wl0.1: Deauth_ind 00:E0:4C:F8:95:84, status: 0, reason: Unspecified reason (1), rssi:0
Dec 30 12:52:48 wlceventd: wlceventd_proc_event(696): wl0.1: Auth 00:E0:4C:F8:95:84, status: Successful (0), rssi:0
Dec 30 12:52:50 kernel: read_bpcm_reg_direct_keyhole: Wait for completion failed, devAddr 0x3, offset 24, idx 2
Dec 30 12:52:50 kernel: thermal thermal_zone0: Failed to get RAIL 0 temperature, ret=256
Dec 30 12:52:50 kernel: thermal thermal_zone0: Failed to get temperature, ret=-1
Dec 30 12:52:50 kernel: thermal thermal_zone0: failed to read out thermal zone (-1)
Dec 30 12:52:52 wlceventd: wlceventd_proc_event(656): wl0.1: Deauth_ind 00:E0:4C:F8:95:84, status: 0, reason: Unspecified reason (1), rssi:0
Dec 30 12:52:52 wlceventd: wlceventd_proc_event(696): wl0.1: Auth 00:E0:4C:F8:95:84, status: Successful (0), rssi:0
Dec 30 12:52:52 kernel: read_bpcm_reg_direct_keyhole: Wait for completion failed, devAddr 0x3, offset 24, idx 2
Dec 30 12:52:52 kernel: thermal thermal_zone0: Failed to get RAIL 0 temperature, ret=256
Dec 30 12:52:52 kernel: thermal thermal_zone0: Failed to get temperature, ret=-1
Dec 30 12:52:54 kernel: read_bpcm_reg_direct_keyhole: Wait for completion failed, devAddr 0x3, offset 24, idx 2
Dec 30 12:52:54 kernel: thermal thermal_zone0: Failed to get RAIL 0 temperature, ret=256
Dec 30 12:52:54 kernel: thermal thermal_zone0: Failed to get temperature, ret=-1
Dec 30 12:52:54 kernel: thermal thermal_zone0: failed to read out thermal zone (-1)
Dec 30 12:52:57 kernel: read_bpcm_reg_direct_keyhole: Wait for completion failed, devAddr 0x3, offset 24, idx 2
Dec 30 12:52:57 kernel: thermal thermal_zone0: Failed to get RAIL 0 temperature, ret=256
Dec 30 12:52:57 kernel: thermal thermal_zone0: Failed to get temperature, ret=-1
Dec 30 12:52:57 kernel: thermal thermal_zone0: failed to read out thermal zone (-1)

I took it out hooked it up and these are the logs from the router.

 

[Tech9]

these are the logs from the router

Always like this even after hard reset?

I haven't looked at logs.

Can you help and look at your logs, please?

 

[digits n bits]

Always like this even after hard reset?



Can you help and look at your logs, please?

Yes after a hard reset. I reinstalled it for a bit, reset it and the log shows the same errors. I’m waiting to hear back from ASUS on an RMA.

 

[iFrogMac]

Yes after a hard reset. I reinstalled it for a bit, reset it and the log shows the same errors. I’m waiting to hear back from ASUS on an RMA.

Also keep in mind the big issues many users went through and some still might be with the malware affecting AX and maybe other Asus routers. Also if you haven't already, along with the RMA file a report with Asus through the feedback service in the router UI. Also remember the BE92U is a brand new release as of a couple months ago. So expect growing pains, especially since WiFi 7 routers as a whole have seemingly had a lot of trouble reported when it comes to stability. Even the more expensive Asus WiFi 7 routers have had a lot of reports of problems. Both in customer reviews and in forums like this one.

 

[iFrogMac]

Thought I would mention that the only glitch I've experienced lately is not specific to this router. The clients list doesn't always automatically update to reflect actively connected clients. This has been a known issue with AsusWRT for several years.
The fix is pretty simple, click on view list under the number of clients on the network map page, give it a few seconds, probably about 5 - 10, and the list will update to the correct number (if you are having the issue.)
Other than that, this router has been stable. It's been going for a couple weeks straight after I finished my comparison between this router, and the RT-AX86U.

 

[Tech9]

Other than that, this router has been stable.

Do you also see the same messages in logs?

 

[iFrogMac]

Do you also see the same messages in logs?

I could look to see. I haven't looked at any logs since I haven't seen any noticeable issues.

 

[digits n bits]

I could look to see. I haven't looked at any logs since I haven't seen any noticeable issues.

Maybe take a look and see what’s there? If you’re logs are showing the same issues as the ones I posted then it’s either defective hardware on a bigger scale or firmware related.

 

[iFrogMac]

Maybe take a look and see what’s there? If you’re logs are showing the same issues as the ones I posted then it’s either defective hardware on a bigger scale or firmware related.

OK, here is what's currently in my system log when I looked:
Dec 30 15:01:13 wlceventd: wlceventd_proc_event(733): wl0.1: Assoc A47:3C:3E:41:FC, status: Successful (0), rssi:-32
Dec 30 17:19:52 wlceventd: wlceventd_proc_event(656): wl0.1: Deauth_ind A47:3C:3E:41:FC, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Dec 30 17:19:52 wlceventd: wlceventd_proc_event(673): wl0.1: Disassoc A47:3C:3E:41:FC, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Dec 31 02:05:11 wlceventd: wlceventd_proc_event(656): wl1.1: Deauth_ind 14:C1:4E:58:A0:CD, status: 0, reason: Unspecified reason (1), rssi:0
Dec 31 02:05:11 wlceventd: wlceventd_proc_event(673): wl1.1: Disassoc 14:C1:4E:58:A0:CD, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Dec 31 02:05:18 wlceventd: wlceventd_proc_event(733): wl1.1: Assoc 14:C1:4E:58:A0:CD, status: Successful (0), rssi:-34
Dec 31 02:15:39 wlceventd: wlceventd_proc_event(656): wl1.1: Deauth_ind 14:C1:4E:58:A0:CD, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Dec 31 02:15:39 wlceventd: wlceventd_proc_event(673): wl1.1: Disassoc 14:C1:4E:58:A0:CD, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Dec 31 02:16:00 wlceventd: wlceventd_proc_event(733): wl1.1: Assoc 14:C1:4E:58:A0:CD, status: Successful (0), rssi:-40
Dec 31 03:28:19 WATCHDOG: [FAUPGRADE][auto_firmware_check8667)]do webs_update
Dec 31 03:28:29 WATCHDOG: [FAUPGRADE][auto_firmware_check8685)]retrieve firmware information
Dec 31 03:28:29 WATCHDOG: [FAUPGRADE][auto_firmware_check8700)]fimrware update check first time
Dec 31 03:28:29 WATCHDOG: [FAUPGRADE][auto_firmware_check8731)]no need to upgrade firmware
Dec 31 03:28:33 ahs: [read_json]Update ahs JSON file.

Dec 31 03:28:59 WATCHDOG: [FAUPGRADE][auto_firmware_check8667)]do webs_update
Dec 31 03:28:59 WATCHDOG: [FAUPGRADE][auto_firmware_check8685)]retrieve firmware information
Dec 31 03:28:59 WATCHDOG: [FAUPGRADE][auto_firmware_check8705)]fimrware update check once
Dec 31 03:29:29 WATCHDOG: [FAUPGRADE][auto_firmware_check8667)]do webs_update
Dec 31 03:29:29 WATCHDOG: [FAUPGRADE][auto_firmware_check8685)]retrieve firmware information
Dec 31 03:29:29 WATCHDOG: [FAUPGRADE][auto_firmware_check8705)]fimrware update check once
Dec 31 03:29:59 WATCHDOG: [FAUPGRADE][auto_firmware_check8667)]do webs_update
Dec 31 03:29:59 WATCHDOG: [FAUPGRADE][auto_firmware_check8685)]retrieve firmware information
Dec 31 03:29:59 WATCHDOG: [FAUPGRADE][auto_firmware_check8700)]fimrware update check first time
Dec 31 03:29:59 WATCHDOG: [FAUPGRADE][auto_firmware_check8731)]no need to upgrade firmware
Dec 31 05:36:03 ahs: [read_json]Update ahs JSON file.

 

[digits n bits]

Thanks, I’m starting to think by the logs on my router that’s it’s defective out of the box.
It’s heading off to ASUS on an RMA.