What's new
  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Release ASUS RT-BE96U Firmware version 3.0.0.6.102_38984 (2025/08/26)

fruitcornbread

Senior Member
Version 3.0.0.6.102_38984
65.3 MB
2025/08/26

Important: After installing this firmware, we strongly recommend performing a factory-default reset to activate every new security adjustment.

Security Enhancements
- Password Policy Upgrade – Minimum 10 characters with at least 1 letter, 1 digit and 1 special symbol, and no consecutive identical characters; hardens defense against brute-force attacks.
- HTTPS on 8443 – Management interface now served over TLS by default.
- UPnP Disabled – Universal Plug and Play starts in the off state for reduced surface exposure.
- AiCloud Authentication Hardening (CWE-287) – Added layered verification.
- Authentication Logic Refactor – Removed redundant code paths for a lean sign-in flow.
- Memory Safety Guard (CWE-476) – Introduced null-reference protections across critical services.
- Enhanced IPsec Parameter Validation – The existing input checks have been hardened
- Data Exposure Mitigation (CWE-200) – Reinforced controls on sensitive pathways.
- Detailed Audit Trails – Expanded logging within the authentication module.

System Improvements
- Connection Stability – Core algorithms refined for steadier links.
- Scheduling Accuracy – Timed tasks execute reliably under PPPoE, PPTP and L2TP WAN modes.
- Client List Maintenance – Resolved an issue that prevented offline devices from being removed from the client list.

Bug Fixes:
- Fixed abnormal client list.
- Fixed abnormal GUI behavior of Wireguard VPN.
- Fixed USB internet backup conflict with main WAN.
- Fixed abnormal WAN detection while AiDetection is enabled.
- Improved AdGuard DNS GUI issues.
- Fixed IPv6 related issues.
- Improved USB tether compatibility for pixel phones.

ZIP SHA-256 : 5053EDA9F0D32C3E02FEA0EC2747CFF6D5002AFA68DDE9332D1C347AE88E58A0
FW SHA-256 : 399acac2a32213dbf538f4d26bdd672461be2ffa18c46bd241bfe7eaab1b8064

Download: https://dlcdnets.asus.com/pub/ASUS/wireless/RT-BE96U/FW_RT_BE96U_300610238984.zip?model=RT-BE96U

 
Anyone know if it is still okay to use a saved CFG file after hard reset and still benefit from the security improvements?
 
Anyone know if it is still okay to use a saved CFG file after hard reset and still benefit from the security improvements?
I don't think any one can answer that other than ASUS or maybe RMerlin. Anyways, it's not recommended to restore from a CFG after factory reset.
 
Anyone know if it is still okay to use a saved CFG file after hard reset and still benefit from the security improvements?
Reloading that config will completely overwrite the changes done by the factory default reset. So you'd be back to the same point as before.
 
Reloading that config will completely overwrite the changes done by the factory default reset. So you'd be back to the same point as before.
Oh joy. Seems like this would need to be done for every update (regardless of the changes) then if you ever want to get the new stuff.
 
Oh joy. Seems like this would need to be done for every update (regardless of the changes) then if you ever want to get the new stuff.
No. This is only needed if a specific config setting has a new default value (like https now being enabled by default), or if a requirement for a setting has changed (like passwords having higher requirements). These requirements are fairly rare. Otherwise there is no need for a factory default reset.
 
Updated my RT-BE96U and now its asking me to log in with my ASUS account. After factory reset I re-entered my password for admin access. It never asked me for a USERNAME. Now I am locked out. So what username should I use ?
 
Updated the GT-BE96U which was in AiMesh operation with this new code "FW_RT_BE96U_300610238984", after the completion of the reboot the unit was locked/frozen, no flickering on the 2.4/5/6GHz wireless LEDs. Tried WPS Resets, Power off/on's, and the same locked condition.
Tried the unit in Router mode and all good there, flip to AiMesh mode and once again unit locks up at the end of the boot.
Went back to previous code level "FW_RT_BE96U_300610237849" and all operational in AiMesh & Router mode.
| Opened a formal case with ASUS support.
 
Last edited:
See my post about problem. I am revert back too
 
@RMerlin
I know you do this in your free time as a service to those that want more out of their consumer devices but any thoughts on dropping a new beta with the recent release ASUS firmware? Lot of security updates.
 
I know you do this in your free time as a service to those that want more out of their consumer devices but any thoughts on dropping a new beta with the recent release ASUS firmware? Lot of security updates.
No. Already explained many times that a binary firmware is useless to me.
 

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

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

Members online

Back
Top