Release ASUS RT-AX92U Firmware version 3.0.0.4.388.22525

[L&LD]

Bricked your router?

 

[mrmason]

Bricked your router?

Well sort of. It bricked when I added a vpn fusion wireguard tunnel. I noticed this line in the newest firmware:

5.Fixed the reboot issue when assigning specific clients in VPN fusion

I don't know if that is the bug or not. I'm hesitant to update as if this bug is not fixed, I will have to reset my router again and re-image with the older firmware. Not fun.

 

[L&LD]

That's not bricking the router, when you're able to recover it in a straightforward manner (i.e. reset).

To test new firmware properly (particularly when you have issues such as yours), you should flash the firmware you want to use, then do a full reset. Do not import any old saved config files. Do not plug in any USB drives that you used for amtm or other scripts.

 

[Tech9]

22068 bricked my router when connecting to any wireguard vpn fusion clients

This bug was reported and fixed (?) in later Asuswrt. It was present for other models too.

 

[mrmason]

That's not bricking the router, when you're able to recover it in a straightforward manner (i.e. reset).

To test new firmware properly (particularly when you have issues such as yours), you should flash the firmware you want to use, then do a full reset. Do not import any old saved config files. Do not plug in any USB drives that you used for amtm or other scripts.

This is unreasonable. Flashing, then resetting as I have many custom settings and it takes a long time to properly set up the router all over again. And it never goes smoothly and is painful. I should be able to simply update through the UI and expect it to work. Considering Asus uses VPN Fusion as a big selling point of this router and to have the latest firmware break VPN Fusion is unacceptable on every level.

 

[L&LD]

Agreed, it may be unreasonable. But it is still not bricking up the router.

Take screenshots of your customizations, and keep good notes, including the order of installing certain features/options. Setting up a router isn't painful, it just takes a few minutes and some concentration.

If your network configuration is so complicated that it is painful and takes a long time to set up, then it's not the router's fault, is it?

 

[muddymind]

Honestly it is the routers fault. Having to reboot it several times because that's a requirement in many settings it's painful. Not having a simple export for the port forwarding configs, static ips, etc is also super inconvenient.

If you use aiprotection and want to export the whitelist of domains to be allowed then good luck because you'll have to add them again and again.

I have 7 nodes and resetting them, re-adding them and enable in each the support for jumbo frames is even more pain.

Clearly the entire process is so convoluted that I dont fault anyone for being lazy about reseting the router when they have issues.

In my case I created a tamper monkey script to extract and reapply everything automatically but not everyone will have the skills or the patience to do the same I did.

 

[L&LD]

If your network setup is so demanding on the consumer hardware you're attempting to run it on, it is not the hardware's fault. You've picked the wrong hardware for your network.

For the target market, the routers perform above and beyond other manufacturers' examples, overall.

For example, if I were an F1 designer/mechanic/engineer, I wouldn't be trying to replicate that performance on a Prius. No matter what mad skill levels I had.

Time to change platforms, I think.

 

[Tech9]

I have 7 nodes

AiMess. You have created it - now you have to deal with it.

ASUS AiMesh - Have I exceeded max clients for 6 Nodes? Lots of unresponsive clients.

Long story short, we have a lot of smart home and wireless devices (~165) and I’ve been struggling with wireless clients (usually lights or speakers) dropping out and becoming unresponsive for long periods (45min-2hrs), only to reconnect on their own if I haven’t physically intervened by...

www.snbforums.com

 

[muddymind]

If your network setup is so demanding on the consumer hardware you're attempting to run it on, it is not the hardware's fault. You've picked the wrong hardware for your network.

For the target market, the routers perform above and beyond other manufacturers' examples, overall.

For example, if I were an F1 designer/mechanic/engineer, I wouldn't be trying to replicate that performance on a Prius. No matter what mad skill levels I had.

Time to change platforms, I think.

Why change platforms if it works? And like I said I automated the process so it no longer is a problem for me.

1st it removes each node by order (to avoid unreachable nodes)
2nd it stores all static ips list and port forwarding info
3rd it stores ai protection domains list
4th it stores wifi settings for the 3 bands
5th stores all guest networks settings
6th it stores dhcp settings

Then I install the new FW and factory reset.

Then I run the second script in the inverse order.


For my use case it runs perfectly fine so why should I have to switch platforms to something more inconvenient like unify and such? I have physical constraints (I would have to break too many concrete walls and ceilings for ideal AP placement in a HUGE house), 2 nodes must be connected with wifi backhaul (which unify doesn't support IIRC) and I would have to buy POE switches in many places since I need local LAN ports in most of the house.

Btw, the master router is a GT-AX11000 and the nodes are all rt-ax92u.

In the end, asus could perfectly provide the same functionality that I automated with my scripts so yes, I point fingers to asus.

 

[L&LD]

Everything sounds great in your post above, except the last sentence/conclusion.

Not even commercial routers offer that, let alone the prosumer models we're talking about here.

 

[tglesel]

I have noticed after upgrade that the RX92 starts to constantly access my USB attached HDD so it never goes into hibernation. I have tried to disable various usb-drive services, but the disk activity continues. Has anyone noticed this as well? I have downgraded firmware and the constant disk activity disappeared immediately.

 

[AndyB21]

I upgraded to this firmware. It is the first release that has worked for me since June of 2021. I did a hard reset on both nodes, uploaded the firmware from my PC via the web interface, and then reconfigured everything from scratch. So far, the mesh has been running fine for four days, now. Knock on wood. (I did find that one of the problems that had been keeping me from upgrading before this could be resolved by disabling ac/ax on the PC that had been dropping off the network.)

I do see one watchdog timer runout in the logs, but it doesn't appear to have taken down the router.

 

[Techtype]

I have been running this official release for 1 month straight with no glitches whatsoever. Setup is 2 AX-92U in mesh with wired backhaul. Numerous computers, iPads, iPhones and smart home devices (all HomeKit connected). First version in over a year that is completely stable. Note, that most settings are left at default. I did do a complete reset thru the GUI and using the hard reset button although I think the reset business resembles Voodoo more than science. I base this opinion on many years of experience upgrading firmware on numerous types of devices that never required any manual erase procedure before updating. However, these Asus routers do seem to need Voodoo of various kinds, more often than not, after any update. It may be significant that I found that performance was improved by locking down the 2.4 channel.

OK, after 52 days with zero issues, watchdog began resetting this morning and has repeated 3 times in 3 hours. Time to reboot the system.

Apr 26 07:31:30 kernel: wl0: PSM microcode watchdog fired at 4518008 (seconds). Resetting.
Apr 26 07:31:30 kernel: wl0: reason = psm watchdog at 4518008 seconds. corerev 42 ucode revision 1570.181 features 0x0426
Apr 26 07:31:30 kernel: psmdebug 0x00ff8014 phydebug 0x40 macctl 0x84160403 maccmd 0x4
Apr 26 07:31:30 kernel: psm_brc 0x0000 psm_brc_1 0x00a0 M_UCODE_DBGST 0x2
Apr 26 07:31:30 kernel: brwk_0 0x0098 brwk_1 0x0002 brwk_2 0x0030 brwk_3 0x7101 brwk_4 0x0000
Apr 26 07:31:30 kernel: ifsstat 0xaf ifsstat1 0xf0 txectl 0x4000 txestat 0x401
Apr 26 07:31:30 kernel: rxestat1 0x41a0 rxestat2 0x0 rcv_frmcnt 0x0 rxe_rxcnt 0x1ce
Apr 26 07:31:30 kernel: wepctl 0x50
Apr 26 07:31:30 kernel: aqmfifordy 0x0 wepstat 0x0 wep_ivloc 0x1e wep_psdulen 0x3ca
Apr 26 07:31:30 kernel: PC :
Apr 26 07:31:30 kernel: R0: 0xfe98e1 0xff98e9 0xfe9470 0xff8c67
Apr 26 07:31:30 kernel: R0: 0xff8c26 0xc998e1 0xff98e8 0xec9470
Apr 26 07:31:30 kernel: R0: 0xff8014 0xff8014 0xff8014 0xff8014
Apr 26 07:31:30 kernel: R0: 0xff8014 0xff8014 0xff8014 0xff8014
Apr 26 07:31:30 kernel: R0: 0xff8014 0xff8014 0xff8014 0xff8014
Apr 26 07:31:30 kernel: R0: 0xff8014 0xff8014 0xff8014 0xff8014
Apr 26 07:31:30 kernel: R0: 0xff8014 0xff8014 0xff8014 0xff8014
Apr 26 07:31:30 kernel: R0: 0xff8014 0xff8014 0xff8014 0xff8014
Apr 26 07:31:30 kernel: R0: 0xff8014 0xff8014 0xff8014 0xff8014
Apr 26 07:31:30 kernel: R0: 0xff8014 0xff8014 0xff8014 0xff8014
Apr 26 07:31:30 kernel: R0: 0xff8c25 0xff946f 0xfe98e1 0xff98e9
Apr 26 07:31:30 kernel: R0: 0xff8014 0xff8014 0xff8014 0xff8014
Apr 26 07:31:30 kernel: R0: 0xff8014 0xff8014 0xff8014 0xff8014
Apr 26 07:31:30 kernel: R0: 0xff8014 0xff8014 0xff8014 0xff8014
Apr 26 07:31:30 kernel: R0: 0xff8014 0xff8014 0xff8014 0xff8014
Apr 26 07:31:30 kernel: R0: 0xff8014 0xff8014 0xff8014 0xff8014
Apr 26 07:31:30 kernel: phydebug :
Apr 26 07:31:30 kernel: 0x40 0x40 0x40 0x40
Apr 26 07:31:30 kernel: 0x40 0x40 0x40 0x40
Apr 26 07:31:30 kernel: 0x31 0x31 0x31 0x31
Apr 26 07:31:30 kernel: 0x31 0x31 0x31 0x31
Apr 26 07:31:30 kernel: 0x40 0x40 0x40 0x40
Apr 26 07:31:30 kernel: 0x40 0x40 0x40 0x40
Apr 26 07:31:30 kernel: 0x40 0x40 0x40 0x40
Apr 26 07:31:30 kernel: 0x31 0x31 0x31 0x31
Apr 26 07:31:30 kernel: pktproc 0x10e pktproc 0x10e pktproc 0x10e pktproc 0x101
Apr 26 07:31:30 kernel: psm stack_status : 0x10
Apr 26 07:31:30 kernel: psm stack_entries:
Apr 26 07:31:30 kernel: 0x0c27
Apr 26 07:31:30 kernel: 0x1470
Apr 26 07:31:30 kernel: 0x11d3
Apr 26 07:31:30 kernel: 0x1d1d
Apr 26 07:31:30 kernel: 0x128e
Apr 26 07:31:30 kernel: 0x0e7d
Apr 26 07:31:30 kernel: 0x1ec7
Apr 26 07:31:30 kernel: 0x1c69
Apr 26 07:31:30 kernel: wl0: fatal error, reinitializing, total count of reinit's[3]

 

[Mittenz]

Is there any new beta releases for this router ?

 

[Deleted member 84281]

No

 

[Dilbert]

No

Yes. 388_23630 is available.

 

[AndyB21]

Yes. 388_23630 is available.

My router is telling me that 388_23630 is available. Since I have NOT checked the box that says "retrieve beta firmware" I was assuming that the alert meant that new RELEASED firmware was available. I don't see any announcement here, though (or on the ASUS website) and your reply taken in context seems to imply that 23630 is beta. Is the router in fact telling me about beta firmware when I have told it not to do so?

 

[Dilbert]

My router is telling me that 388_23630 is available. Since I have NOT checked the box that says "retrieve beta firmware" I was assuming that the alert meant that new RELEASED firmware was available. I don't see any announcement here, though (or on the ASUS website) and your reply taken in context seems to imply that 23630 is beta. Is the router in fact telling me about beta firmware when I have told it not to do s

I didn’t know Sherlock Holmes had an Asus router. Not beta then.

 

[Techtype]

My router is telling me that 388_23630 is available. Since I have NOT checked the box that says "retrieve beta firmware" I was assuming that the alert meant that new RELEASED firmware was available. I don't see any announcement here, though (or on the ASUS website) and your reply taken in context seems to imply that 23630 is beta. Is the router in fact telling me about beta firmware when I have told it not to do so?

Firmware version 3.0.0.4.388_23630
- Release Note -

Bug fixes and functionality modifications:
- Resolved the issue with login and password changes.
- Resolved the IPSec VPN connection issues.
- Resolved the Instant Guard connection issues.
- Fixed the issue where Traffic Analyzer sometimes couldn't record data.
- Fixed the time display issue for the preferred upgrade time in the Auto Firmware Upgrade function.
- Enabled DynDNS and No-IP DDNS to use IPv6.
- Fixed AiMesh preferred AP identification in site survey results.
- Updated timezone list for Greenland, Mexico, and Iran.
- Allowed WireGuard Server clients to access the Samba server.
- Fixed memory leak issue.
- Resolved the issue where the USB path is not displayed on the Media Server page in the AiMesh node

Security updates:
- Enabled and supported ECDSA certificates for Let's Encrypt.
- Enhanced protection for credentials.
- Enhanced protection for OTA firmware updates.
- Fixed DoS vulnerabilities in firewall configuration pages.
- Fixed DoS vulerabilities in httpd.
- Fixed information disclosure vulnerability.
- Fixed CVE-2023-28702 and CVE-2023-28703.
- Fixed null pointer dereference vulnerabilities.
- Fixed the cfg server vulnerability.
- Fixed the vulnerability in the logmessage function CVE-2023-35086/ CVE-2023-35087.
- Fixed lighttpd vulnerability, CVE-2023-35720.
- Fixed several curl vulnerabilities including CVE-2023-28322, CVE-2023-28321, and CVE-2023-28319.
- Fixed FFmpeg vulnerabilities, specifically CVE-2022-3964, CVE-2022-48434, and CVE-2022-3109.
- Fixed openssl vulnerability, CVE-2023-0464.
- Fixed ReadyMedia vulnerabilitym CVE-2020-28926.
- Fixed UPnP vulnerability CVE-2020-12695.
- Patched a command injection vulnerability to improve overall security.
- Strengthened protection against SSH brute force attacks.