What's new

ASUS ZenWiFi Pro ET12 Firmware version 3.0.0.4.388.23013

  • 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!

drady

New Around Here

New Features:
-Built-in Surfshark in VPN Fusion allows you to surf the internet anonymously and securely from anywhere by encrypting connections. Please refer to https://asus.click/SurfsharkVPN
-DDNS transfer allows you to transfer your ASUS DDNS hostname from your original router to the new one. Please refer to https://asus.click/ASUSDDNS

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.
-Fine-tuned the description for port status.
-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.
-Fixed memory leak issue.

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. Thanks to Jinghe Gao's contribution.
-Fixed DoS vulerabilities in httpd. Thanks to Howard McGreehan.
-Fixed information disclosure vulnerability. Thanks to Junxu (Hillstone Network Security Research Institute) contribution.
-Fixed CVE-2023-28702 and CVE-2023-28703. Thanks to Xingyu Xu(@tmotfl) contribution.
-Fixed null pointer dereference vulnerabilities. Thanks to Chengfeng Ye, Prism Research Group - cse hkust contribution.
 
Did not fix any of the broken behavior that I'm seeing.
Didn't really expect it to do so.
Next step is downgrading to 3.0.0.4.388.21739 f/w.
 
Did not fix any of the broken behavior that I'm seeing.
Didn't really expect it to do so.
Next step is downgrading to 3.0.0.4.388.21739 f/w.
What broken behavior?
Broken behavior for a normal home router user or broken behavior you for a hardcore network guru pushing the limits of this thing? :)
 
The one with AiMesh maybe? They are broken, last usable firmware is 388.21xxx afaik, regarding XT8 XT9 ET12
 
The one with AiMesh maybe? They are broken, last usable firmware is 388.21xxx afaik, regarding XT8 XT9 ET12
My question was put to drady.

Neither he, nor you, are specifying exactly what issues you see with the router - in general, or with AiMesh.
Essentially, the both of you are just name calling.

FWIW, AiMesh is the one thing that has worked flawlessly (for me) on these routers for months.
I have run firmwares 3.0.0.4.388.21739, 3.0.0.4.388.22127, & 3.0.0.4.388.23013.
x.22127 had stability issues, so I quickly reverted back to x.21739.
x.23013 appears rock solid, and seems to have resolved my issue with Bandwidth Monitor.
 
Last edited:
My question was put to drady.

Neither he, nor you, are specifying are specifying exactly what issues you see with the router - in general, or with AiMesh.
Essentially, the both of you are just name calling.

FWIW, AiMesh is the one thing that has worked flawlessly (for me) on these routers for months.
I have run firmwares 3.0.0.4.388.21739, 3.0.0.4.388.22127, & 3.0.0.4.388.23013.
x.22127 had stability issues, so I quickly reverted back to x.21739.
x.23013 appears rock solid, and seems to have resolved my issue with Bandwidth Monitor.
Name calling ... cute.
 
Did not fix any of the broken behavior that I'm seeing.
Didn't really expect it to do so.
Next step is downgrading to 3.0.0.4.388.21739 f/w.
Things have improved. Am staying at 3.0.0.4.388.21739 f/w.
Got the 2nd node reset/updated/reset AND after it finally sync'd up and online as a mesh node.
Been mostly stable for 8 days now.
Tweaked settings:
- 2.5G ethernet backhaul
- separate SSIDs
- WPA2/Personal only on 2.4 & 5
- 2.4GHz: short preamble, b/g protection, disable 11b.
Have been able to get some Ring devices to reconnect that were previously had issues.
The dhcp still seems fickle, but at least it is handing out addresses now.
 
Last edited:
- 2.5G ethernet backhaul
Please give details on your backhaul.
Length, Cat specification of wire - and if you know it, the manufacture of the cable.

- separate SSIDs
My assumption here is that you are using unique SSIDs for 2.4, 5.0, & 6.0?

- 2.4GHz: short preamble, b/g protection, disable 11b.
Have been able to get some Ring devices to reconnect that were previously had issues.
The dhcp still seems fickle, but at least it is handing out addresses now.
Have you used a WiFi analyzer in your environment?
A congested signal area, coupled with short preamble, could be the cause for a lot of these issues.
While the short preamble is markedly faster, it is less robust for error correction.
Congested channel spaces, with the short preamble could definitely be a contributing factor.
An additional consideration is that short preamble is a modification to the original WiFi specification.
Meaning, older (legacy) devices... or even modern ones built with older (cheaper) radios, can have issues with short preamble.
 
My ET12's received an update to version 3.0.0.4.388_24542-g719e902 via OTA function today. I could not yet find any informations about that version on Asus' support site though.
 
It is listed on the US site.
Version 3.0.0.4.388_24542

Feature:
- Fixed 6GHz WiFi compatibility issues.
- Fixed unstable issue while using VPN fusion.
- Fixed Ethernet AiMesh setup issue while using IPTV.
- Fixed few GUI bugs.
- Allow "2.5G/1G LAN" port to be configured as WAN port.

Security:
- Fixed CVE-2021-36369.
- Updated dropbear patches.
- Fixed five command injection vulnerabilities.
 

Sign Up For SNBForums Daily Digest

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