Release ASUS RT-AC88U Firmware version 3.0.0.4.386.43129

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.

Squall Leonhart

Regular Contributor
2021/05/18 40.61 MBytes

ASUS RT-AC88U Firmware version 3.0.0.4.386.43129
1.Fixed the FragAttack vulnerability.
2.Fixed DoS vulnerability. Thanks for Tsinghua University NISL's contribution.
3.Improved system stability.
4.Fixed GUI bugs.
5.Security Fixed: CVE-2020-25681, CVE-2020-25682, CVE-2020-25683, CVE-2020-25687, CVE-2020-25684, CVE-2020-25685, CVE-2020-25686

Please unzip the firmware file first then check the MD5 code.
MD5: 80f8d75eb4b23d60a65e1cdea052d5c8

 

Ken Atkinson

Regular Contributor
Actually folks I upgraded to this FW Version 3.0.0.4.386.43129 last night on an AiMesh rt-ac5300 main node + (using also 3 rt-ac68u nodes) and it broke the connection to my cable modem. Essentially admin page showed X for internet connectivity. I hard rebooted the primary and all the nodes but that did not fix things. I even bounced the modem and then bounced all nodes sequentially starting with rt-ac5300, but still no connection. I flashed back to Version 3.0.0.4.384.82072 and magically things came back to normal.

Note1: I did this upgrade via the admin gui upgrade button in the FW upgrade section/page.I will attempt the same from a downloaded trx and checked with md5sum code.
Moving from the 384 release to 386 requires a factory reset , a dirty flash will cause issues.
 

shoman94

Regular Contributor
Actually folks I upgraded to this FW Version 3.0.0.4.386.43129 last night on an AiMesh rt-ac5300 main node + (using also 3 rt-ac68u nodes) and it broke the connection to my cable modem. Essentially admin page showed X for internet connectivity. I hard rebooted the primary and all the nodes but that did not fix things. I even bounced the modem and then bounced all nodes sequentially starting with rt-ac5300, but still no connection. I flashed back to Version 3.0.0.4.384.82072 and magically things came back to normal.

Note1: I did this upgrade via the admin gui upgrade button in the FW upgrade section/page.I will attempt the same from a downloaded trx and checked with md5sum code.
I'm confused right now, this specific post and update is for the AC88U.
 

GhostDog23

New Around Here
I tried to install the firmwareverison 3.0.0.4.386_43129 via the GUI of the RT-AC68U.
The result is, as before, the old version 3.0.0.4.386_41634 is shown as installed after the update attempt.
Even after all conceivable reboots no change.
 

shoman94

Regular Contributor
I tried to install the firmwareverison 3.0.0.4.386_43129 via the GUI of the RT-AC68U.
The result is, as before, the old version 3.0.0.4.386_41634 is shown as installed after the update attempt.
Even after all conceivable reboots no change.
Wrong thread.... What is going on here?
 

azbruno

Occasional Visitor
I am currently running the beta version Version 9.0.0.4.386.41994 downloaded from the Asus site. My router reports that as the latest version so I cannot update it via the router GUI.

I assume I must run the update manually. Will this be easy or is there any trick I need to know?

Once updated, do I need to do a factory reset?
 

susa-me

New Around Here
I personally wouldn’t run a beta fw. I think it’s untested on every model and think that asus is having its users do the testing for them.
If you can’t go without internet, I suggest you don’t run beta fw on your “production” router. My 2 cents.
 

piok

Occasional Visitor
I tried to install the firmwareverison 3.0.0.4.386_43129 via the GUI of the RT-AC68U.
The result is, as before, the old version 3.0.0.4.386_41634 is shown as installed after the update attempt.
Even after all conceivable reboots no change.
I got the same issue with RT-AC1900U. Just update manually - download new firmware - choose update - point firmware file and start again.
Worked like a charm.
 

st939

New Around Here
I wasn't able to get this (43129) working on my RT-AC88U, factory defaults reset didn't help, when rolled back to 41700 no issues.
 

azbruno

Occasional Visitor
I ran a manual update from the just prior beta (9.0.0.4.386.41994) through the GUI and it worked perfectly. No issues.
 

Ken Atkinson

Regular Contributor
no it doesn't.
Sorry but see below extract from CHANGELOG for first 386 release for AC88U


Version 3.0.0.4.386.41535
2020/12/30 40.67 MBytes
ASUS RT-AC88U Firmware version 3.0.0.4.386.41535
1. AiMesh 2.0
- System optimization: one click in AiMesh to optimize the topology
- System Ethernet backhaul mode, all nodes will only connect by ethernet, all bands will be released for wireless clients.
- System factory default and reboot.
- Client device reconnect, make the device to offline and online again.
- Client device binding to specific AP.
- Guest WiFi on all Mesh nodes (all node need to upgrade to 3.0.0.4.386 firmware)
- Access nodes USB application.
 

Squall Leonhart

Regular Contributor
Sorry but see below extract from CHANGELOG for first 386 release for AC88U


Version 3.0.0.4.386.41535
2020/12/30 40.67 MBytes
ASUS RT-AC88U Firmware version 3.0.0.4.386.41535
1. AiMesh 2.0
- System optimization: one click in AiMesh to optimize the topology
- System Ethernet backhaul mode, all nodes will only connect by ethernet, all bands will be released for wireless clients.
- System factory default and reboot.
- Client device reconnect, make the device to offline and online again.
- Client device binding to specific AP.
- Guest WiFi on all Mesh nodes (all node need to upgrade to 3.0.0.4.386 firmware)
- Access nodes USB application.

You misunderstand this line entirely,

This refers to the addition of AIMesh > System Settings > System Reset to Factory Default as a GUI item for the AIMesh 2.0 system

It does not imply, force or otherwise require a factory reset, and the 386 firmware runs with a persistent 384/385 configuration just fine.

The implementation of the auto update system requires that dirty updates be as smooth and problem-free as possible, if you're one of the few who significantly alter NVRAM CVARS, then all bet are off, but the necessity to start from scratch is not there.
 
Last edited:

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top