Release RT-BE92UFirmware version 3.0.0.6_102_37526-g5772bd6_1099-ga930e 04/02/2025

[iFrogMac]

Firmware version 3.0.0.6_102_37526-g5772bd6_1099-ga930e
- Release note -

Improved system stability
Support site:

ASUS RT-BE92U - Support

www.asus.com

 

[iFrogMac]

Update went as expected, and everything seems to be normal. Screenshot below:

 

[Spartan]

Firmware version 3.0.0.6_102_37526-g5772bd6_1099-ga930e
- Release note -

Improved system stability
Support site:

ASUS RT-BE92U - Support

www.asus.com

The site still gives me 3.0.0.6.102_37506, but I checked for updates via the router settings page, and it did the auto upgrade for both my RT-BE92U

 

[iFrogMac]

The site still gives me 3.0.0.6.102_37506, but I checked for updates via the router settings page, and it did the auto upgrade for both my RT-BE92U

Well, I'm glad to hear you had a successful update, either way.

 

[JWoo]

It looks like Asus is updating the bootloader in all of these updates. That is a generally bad practice unless they are actually fixing some faults or adding functionality in the bootloader. Anyone know why Asus is doing that?

 

[alba666]

I updated and have had to pull the plug on my router and modem multiple times and a factory reset on router to get it working.
Seeing my upload speed go from 60 to 10 Meg on my Gigabit Mediacom internet connection. Tested from the router and my iPhone with same result.
Very strange. I’m going to let it go overnight and check again in the morning.

 

[Spartan]

I updated and have had to pull the plug on my router and modem multiple times and a factory reset on router to get it working.
Seeing my upload speed go from 60 to 10 Meg on my Gigabit Mediacom internet connection. Tested from the router and my iPhone with same result.
Very strange. I’m going to let it go overnight and check again in the morning.

weird, I didn't factory restore even, just did an upgrade and everything's working the same, so perfectly. This has been like one of the best and most stable routers that I've owned despite what some of the nagative reviews on Amazon from people complaining about overheating and whatnot

 

[alba666]

weird, I didn't factory restore even, just did an upgrade and everything's working the same, so perfectly. This has been like one of the best and most stable routers that I've owned despite what some of the nagative reviews on Amazon from people complaining about overheating and whatnot

I invoked the Mediacom troubleshooting bot again and it is now suggesting the splitter as a possible issue. Gonna try to bypass it when “She Who Must Be Obeyed” is not watching the TV.

 

[iFrogMac]

I invoked the Mediacom troubleshooting bot again and it is now suggesting the splitter as a possible issue. Gonna try to bypass it when “She Who Must Be Obeyed” is not watching the TV.

I just ran a speedtest with this new firmware and everything is normal here. I used to have gigabit, but dropp3d it to 500 / 50 as Cox has issues with their lines, or was having issues and the higher speed plans weren't dependable. I also found (even for larger downloads) the plan I have stuck with is very comfortable. At first I was a bit disappointed that I couldn't keep the higher speeds reliable in my setup due to provider issues, but now it's OK, because I know the hardware can go up to 2.5Gbps when the time comes I need that much bandwidth, and have a more stable provider. They could have fixed the issue by now, but since things are stable, I've just left it alone.

Here are my speedtest results:

Speedtest by Ookla - The Global Broadband Speed Test

Use Speedtest on all your devices with our free desktop and mobile apps.

www.speedtest.net

 

[alba666]

My issues were from a bad ground on the cable feed. Mediacom fixed it and I am going back to checking this release again.
So far, it has been stable since the cable fix.

 

[iFrogMac]

My issues were from a bad ground on the cable feed. Mediacom fixed it and I am going back to checking this release again.
So far, it has been stable since the cable fix.

Good to hear everything turned out in the end for you, and things are now back to normal.

 

[alba666]

So far, everything except MLO is GTG.
Nothing new with MLO - same old issues.

 

[iFrogMac]

So far, everything except MLO is GTG.
Nothing new with MLO - same old issues.

OK, for now, I have no way of testing MLO here since I don't currently have any WiFi 7 devices, otherwise I would test here to see what happens.

 

[JWoo]

This build 3.0.0.6_102_37526 is pretty bad (37523 also was crap for those who could load it).

We probably all have pages and pages of what appear to be debug logfile entries with a bunch of hex registers. Look at your logfile or via SSH look at dmesg.

Apr 4 18:09:03 kernel: PKT:
Apr 4 18:09:03 kernel: 0000: 78 cb 5c 59 a1 03 00 00 a2 a2 a2 52 94 00 02 02
Apr 4 18:09:03 kernel: 0010: 0e 00 00 00 00 0d 00 00 00 00 20 00 ff ff 00 00

Went back to 3.0.0.6_102_37506

 

[iFrogMac]

This build 3.0.0.6_102_37526 is pretty bad (37523 also was crap for those who could load it).

We probably all have pages and pages of what appear to be debug logfile entries with a bunch of hex registers. Look at your logfile or via SSH look at dmesg.

Apr 4 18:09:03 kernel: PKT:
Apr 4 18:09:03 kernel: 0000: 78 cb 5c 59 a1 03 00 00 a2 a2 a2 52 94 00 02 02
Apr 4 18:09:03 kernel: 0010: 0e 00 00 00 00 0d 00 00 00 00 20 00 ff ff 00 00

Went back to 3.0.0.6_102_37506

This is what was in my system log in the web UI:

Apr 4 05:04:13 WATCHDOG: [FAUPGRADE][auto_firmware_check8715)]fimrware update check once
Apr 4 05:04:43 WATCHDOG: [FAUPGRADE][auto_firmware_check8677)]do webs_update
Apr 4 05:04:43 WATCHDOG: [FAUPGRADE][auto_firmware_check8695)]retrieve firmware information
Apr 4 05:04:43 WATCHDOG: [FAUPGRADE][auto_firmware_check8710)]fimrware update check first time
Apr 4 05:04:43 WATCHDOG: [FAUPGRADE][auto_firmware_check8741)]no need to upgrade firmware
Apr 4 15:59:04 wlceventd: wlceventd_proc_event(656): wl1.1: Deauth_ind 14:C1:4E:58:A0:CD, status: 0, reason: Unspecified reason (1), rssi:0
Apr 4 15:59:04 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
Apr 4 15:59:11 wlceventd: wlceventd_proc_event(733): wl1.1: Assoc 14:C1:4E:58:A0:CD, status: Successful (0), rssi:-43
Apr 5 02:21:54 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
Apr 5 02:21:54 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
Apr 5 02:22:15 wlceventd: wlceventd_proc_event(733): wl1.1: Assoc 14:C1:4E:58:A0:CD, status: Successful (0), rssi:-44
Apr 5 05:03:14 WATCHDOG: [FAUPGRADE][auto_firmware_check8677)]do webs_update
Apr 5 05:03:23 WATCHDOG: [FAUPGRADE][auto_firmware_check8695)]retrieve firmware information
Apr 5 05:03:23 WATCHDOG: [FAUPGRADE][auto_firmware_check8710)]fimrware update check first time
Apr 5 05:03:23 WATCHDOG: [FAUPGRADE][auto_firmware_check8741)]no need to upgrade firmware
Apr 5 05:03:53 WATCHDOG: [FAUPGRADE][auto_firmware_check8677)]do webs_update
Apr 5 05:03:53 WATCHDOG: [FAUPGRADE][auto_firmware_check8695)]retrieve firmware information
Apr 5 05:03:53 WATCHDOG: [FAUPGRADE][auto_firmware_check8715)]fimrware update check once
Apr 5 05:04:23 WATCHDOG: [FAUPGRADE][auto_firmware_check8677)]do webs_update
Apr 5 05:04:23 WATCHDOG: [FAUPGRADE][auto_firmware_check8695)]retrieve firmware information
Apr 5 05:04:23 WATCHDOG: [FAUPGRADE][auto_firmware_check8715)]fimrware update check once
Apr 5 05:04:53 WATCHDOG: [FAUPGRADE][auto_firmware_check8677)]do webs_update
Apr 5 05:04:53 WATCHDOG: [FAUPGRADE][auto_firmware_check8695)]retrieve firmware information
Apr 5 05:04:53 WATCHDOG: [FAUPGRADE][auto_firmware_check8710)]fimrware update check first time
Apr 5 05:04:53 WATCHDOG: [FAUPGRADE][auto_firmware_check8741)]no need to upgrade firmware

 

[JWoo]

I have pages and pages of Kernel PKT (packet) messages on 3.0.0.6_102_37523 and 3.0.0.6_102_37526 that I do not get on 3.0.0.6_102_37506. I have no idea what functions you are using. I am using main and guest networks, IPv6, DNS over TLS and all 3 wireless bands over a 500 Mbps fiber connection. So it very well could be a function that I am using triggers this, and you are not using that function. What function(s) are you exercising on your router?

 

[iFrogMac]

I have pages and pages of Kernel PKT (packet) messages on 3.0.0.6_102_37523 and 3.0.0.6_102_37526 that I do not get on 3.0.0.6_102_37506. I have no idea what functions you are using. I am using main and guest networks, IPv6, DNS over TLS and all 3 wireless bands over a 500 Mbps fiber connection. So it very well could be a function that I am using triggers this, and you are not using that function. What function(s) are you exercising on your router?

I have all three wireless bands enabled, even though nothing is currently connected to 6GHz. I have the main network, and an iOT network (2.4Ghz only). I don't use TLS, and I don't use ipV6 except on the local network only between clients. If I use TLS, etc, or anything related, it's just on the computer, not on the router.

 

[JWoo]

I am using DNS encryption over TLS protocol (Transport Layer Security). It is a WAN setting. This uses opensource software in the background called "stubby" that intercepts the DNS queries on the router and uses the encrypted DNS providers selected so all the lookups are fully encrypted. My point is that all of us have the same router but are using different functions on it. So our experiences may be very different with these firmware releases. I can also see that Asus is routinely updating the UBoot at each firmware upgrade, and that is a bad practice. Merlin, as an example, moved to only updating UBoot if there was a functional reason to do so.

 

[iFrogMac]

I am using DNS encryption over TLS protocol (Transport Layer Security). It is a WAN setting. This uses opensource software in the background called "stubby" that intercepts the DNS queries on the router and uses the encrypted DNS providers selected so all the lookups are fully encrypted. My point is that all of us have the same router but are using different functions on it. So our experiences may be very different with these firmware releases. I can also see that Asus is routinely updating the UBoot at each firmware upgrade, and that is a bad practice. Merlin, as an example, moved to only updating UBoot if there was a functional reason to do so.

I'm not familiar with the router's boot loader, I am familiar with Linux though, and most of the time, that's the grub boot loader. As far as DNS encryption, and TLS, I know what it is, I just use it in Firefox vs on the router. The computer is the only thing it would really matter to me for, and typically I don't utilize those features on a regular practice. Yes, using different settings, and different environments and a mix of different products can all affect performance. Thankfully in my setup, things seem to be rock solid.

 

[iFrogMac]

The first Asus router I got, and officially kept was my Gundam edition RT-AX86U that I kept as a backup in case the RT-BE92U didn't work out as an upgrade. I mainly got this router because I wanted access to more than one multi-gig Ethernet port. It didn't make sense to buy a WiFi 6E router, and then upgrade maybe a year later when in the course of time, I'd most likely start getting more WiFi 7 devices.

I've been happy with this router, and it's been stable. I remember though, that the RT-AX86U had a lot of growing pains with it's firmware too. It just depended on what features were being used as to what problems were experienced.

Going back to the comments about what functions were in use, and not in use, I wanted to add that, I typically do a factory reset after every several firmware updates, or when I have issues to flush the system out, and start over with a clean configuration. This also seems to help avoid cluttered settings build up over time. Since Apple no longer makes Airport products, the only other router I've been able to trust as stable is TP-Link, and the main reason I don't have one of those now, is because of the pending ban in the US, which doesn't seem to be going anywhere, and is just speculation. Nothing formally seems to have come from that, at least not what I can find when looking up the status for that situation.