Release ASUS ZenWiFi Pro ET12 Firmware version 3.0.0.6.102_36597 (2025/04/17)

[rudoyeugene]

Firmware version for ASUS ZenWiFi Pro ET12 3.0.0.6.102_36597
Version 3.0.0.6.102_36597
50.96 MB
2025/04/17
SHA-256 ：9E20908C366F192FD651BAC1AACF567428F1B07E34AF71E5A5654E255F1F0ABC
1. Fixed the UI issue in Chrome.
2. Fixed client binding issues in Mesh scenarios.
3. Enhanced input parameter handling techniques to improve data processing stability and system security.
4. Enhance system access control mechanisms.
5. Improved system stability and security by fixing a kernel integrity validation issue.

*Do NOT downgrade the firmware on any mesh device (router or node).
Due to enhanced security mechanisms, both the router and node must be upgraded together. Downgrading may result in a mismatch of security protocols between devices, causing the mesh connection to fail.

Download link

 

[rudoyeugene]

Hello fellows!
Just did a dirty flash on top of previous "beta".
Booted, checked the logs, see no unusuals, all clients reconnected just fine.
Well, finally!

 

[rsnhakan]

Thank you! I installed it. The Automatic Update knob is not working so I had to install the firmware first on the router and after on the node.

Also had to agree with new terms in the router.asus.com environment.

1) Btw, you can't turn off automatic updates anymore?

2) I have the exact same problem again that some clients stay connected to the main router and will not connect to the node…

 

[rudoyeugene]

Thank you! I installed it. The Automatic Update knob is not working so I had to install the firmware first on the router and after on the node.

Also had to agree with new terms in the router.asus.com environment.

1) Btw, you can't turn off automatic updates anymore?

2) I have the exact same problem again that some clients stay connected to the main router and will not connect to the node…

The same, neither web ui nor mobile app see the update.
Automatic updates, I was thinking why they made like that, my guess to ensure no botnets can load onto customers routers anymore, people usually never update their firmware, the only thing they always say: it works, why should I do that? Can this strategy crash your hone network one day? Yes. And the last one: am I worry about that? No

 

[rsnhakan]

The same, neither web ui nor mobile app see the update.
Automatic updates, I was thinking why they made like that, my guess to ensure no botnets can load onto customers routers anymore, people usually never update their firmware, the only thing they always say: it works, why should I do that? Can this strategy crash your hone network one day? Yes. And the last one: am I worry about that? No

;-)

I fixed the issue btw with devices connecting to the main router. A reboot did the trick!

I did see a huge speed bump with the 6GHz band.

 

[junior120872]

Upgraded my 3 aImesh ET12's from the previous beta flawlessly. Things seem to running stable. I'm seeing devices connecting to different AP's than before, will diagnose a little more. Super happy Asus finally released this. Wish we had the promised VLAN support from the start, but you deal with what you get.

 

[Spaatz]

I had a different experience, likely because over a year ago I downgraded from the Beta to the Stable version.

I run 9 nodes and 1 router, all ET12's around the house. When the firmware update rolled out, it crippled the house for about 3 hours including the one node in our adjacent AirBnB where we have a particularly needy elderly guest that kept pinging me incessantly while trying to fix the issues resultant from the update.

First, the update erased my guest network entirely, instead replacing it with 3 network names I used over a year ago when I was testing the beta. Overwriting one of those wifi networks that was installed with the correct SSID name and password didn't work at all, until I had to fully delete all of the guest wifi profiles and start anew with a fresh profile.

Second, it reverted names for routers to previously configured names under the beta. I had relocated one router to a different room and switched it out with another some time ago. The update renamed them incorrectly, and insisted the routers on the opposite ends of the property were switched. This led to my troubleshooting the wrong device for quite some time until I realized the error.

It also erased the backhaul settings for the routers, defaulting to auto instead of in my case, a mix of ethernet backhaul and Wifi 6. I had to manually reset each router.

Further, the preferred wifi AP uplink settings were all mangled and required resetting again to their correct (previously configured) settings.

Lastly, I noted that minor changes to the network configuration now require full network reset where they did not before. Changing a static IP on one device for example, caused each node to reset. Various minor other settings did the same.

I have also temporarily stopped periodic system reboots now given the time it take to fully reboot the mesh network as well.

As best as I can tell, the firmware read data from the same tables as the previously installed beta or used the same tables and didn't overwrite them properly when it setup, resulting in this behavior.

So, lesson learned here: if you've previously used the Beta and downgraded, this update will likely reset your system to settings previously used in the beta.

Hope this helps someone!

 

[Spaatz]

Finding that the previously configured Guest Wifi networks are still broadcasting despite having been deleted and not present in the Guest Network tab too. It's like a ghost network. Also, devices seem to be connecting to a different main network than the one I have possible to configure in ASUS GUI, they don't register in the device lists for example and are again, ghost devices.

 

[junior120872]

Since your moving from 3.0.0.4 to 3.0.0.6 or vice versa it is recommended to do a factory restore and reconfigure from scratch. In your situation from doing a dirty downgrade, then back to a dirty upgrade I can see how you'd have some stale configurations stored somewhere. There have been a lot of changes with wireless and additions of SDN ,etc between the software. Your best bet is to reset all and start anew.

 

[Spaatz]

Since your moving from 3.0.0.4 to 3.0.0.6 or vice versa it is recommended to do a factory restore and reconfigure from scratch. In your situation from doing a dirty downgrade, then back to a dirty upgrade I can see how you'd have some stale configurations stored somewhere. There have been a lot of changes with wireless and additions of SDN ,etc between the software. Your best bet is to reset all and start anew.

Yeah, I realized this as well. Can't really do much at the moment about it but I assumed this to be the case as well. Factory resetting 10 routers and reconfiguring them all not going to be fun.

 

[junior120872]

Yeah, I realized this as well. Can't really do much at the moment about it but I assumed this to be the case as well. Factory resetting 10 routers and reconfiguring them all not going to be fun.

Yah. It's painful with just 4(My configuration), so I can understand. Since you're aiMesh though, it's the main configuration only, but adding the nodes can be a pain especially with how many you have though. I have 130 devices on my network so adding names to devices can be a choreas well. Haven't found a way to easily update on stock firmware, but I'm sure there is instead of manually setting each one. Good Luck!

 

[Devious]

With this update did anyone lose client devices? I’ve done a reboot but my ring floodlight can’t suddenly see my ssid anymore.

 

[rsnhakan]

With this update did anyone lose client devices? I’ve done a reboot but my ring floodlight can’t suddenly see my ssid anymore.

No, check your Wi-Fi settings to be sure. Smart connect is off I guess?

 

[Devious]

No, check your Wi-Fi settings to be sure. Smart connect is off I guess?

I disabled smart connect and now my Ring devices can see the wifi again. I guess I gotta go read up the impacts or if some other setting would be best but at least they connect now. Thanks!!

 

[Devious]

I disabled smart connect and now my Ring devices can see the wifi again. I guess I gotta go read up the impacts or if some other setting would be best but at least they connect now. Thanks!!

Weird. Now one at the front works and the one at the back has dropped off.

 

[Spaatz]

Back to update. I factory reset all 10 nodes including the router last night using the newest firmware and started from scratch. I'm getting nodes dropping offline repeatedly and regularly, like every couple minutes or so. The guest network being particularly unstable with the separate VLAN assigned to it only working occasionally and for a short period of time. A relatively new model of Chromecast for example not being able to sustain a connection. All the smart bulbs and many 2.4Ghz devices are refusing to connect and requiring manual synching again with the network. I'm questioning whether this is up to my configuration or down to the firmware update. Open to anyone helping, this is absolutely ruining my Easter weekend. Thanks for anyone that breaks away from the festivities to help.

 

[junior120872]

Back to update. I factory reset all 10 nodes including the router last night using the newest firmware and started from scratch. I'm getting nodes dropping offline repeatedly and regularly, like every couple minutes or so. The guest network being particularly unstable with the separate VLAN assigned to it only working occasionally and for a short period of time. A relatively new model of Chromecast for example not being able to sustain a connection. All the smart bulbs and many 2.4Ghz devices are refusing to connect and requiring manual synching again with the network. I'm questioning whether this is up to my configuration or down to the firmware update. Open to anyone helping, this is absolutely ruining my Easter weekend. Thanks for anyone that breaks away from the festivities to help.

Here are my 2.4Ghz wifi settings. They seemed to fix all my woes on 2.4Ghz. Granted my 2.4 is primarily IoT devices. YMMV. Also are you binding devices to particular AP's? I've seen issues on updates at times for devices that are bound to AP's. I usually have to unbind them for them to reattach.

 

[Spaatz]

Also are you binding devices to particular AP's? I've seen issues on updates at times for devices that are bound to AP's. I usually have to unbind them for them to reattach.

This helped. I unbound tons of devices and unset the preferred Wireless Uplink Node settings for the different nodes. I've experienced more stability in last half hour than last 48. I'll be examining this in detail a bit further but wanted to say thanks for the tip.

 

[Devious]

Back to update. I factory reset all 10 nodes including the router last night using the newest firmware and started from scratch. I'm getting nodes dropping offline repeatedly and regularly, like every couple minutes or so. The guest network being particularly unstable with the separate VLAN assigned to it only working occasionally and for a short period of time. A relatively new model of Chromecast for example not being able to sustain a connection. All the smart bulbs and many 2.4Ghz devices are refusing to connect and requiring manual synching again with the network. I'm questioning whether this is up to my configuration or down to the firmware update. Open to anyone helping, this is absolutely ruining my Easter weekend. Thanks for anyone that breaks away from the festivities to help.

There is definitely something wacky with 2.4.
I have like 6 ring devices and half of them right now are connected to guest network vs my primary internet. Fortunately no real harm for doing that right now. Most times the devices don’t even see the sssd for whatever reason.

 

[mmjlmjl]

I Upgraded from the 9006 beta to this, what a deception as all VLAN support was dropped, I tried to revert back to 9006, however, that does not work, most of the me is are not working, factory reset, downgrade to 3004 and back to 9006 same issues. Will Asus bring back support for Vlans on this router, if not I’ll have to switch to different system unfortunately.. ?