Release ASUS ZenWiFi XT8 Firmware version 3.0.0.4.388_24709 (2025/03/18)

[fruitcornbread]

Version 3.0.0.4.388_24709
V1 - 49.68 MB
V2 - 50.27 MB
2025/03/18

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.

XT8 V1 ZIP SHA-256 : 8DF2CF653DCF359BF7CE4D8AFF52CB0BEEFA1747240C95E7AEA0C054838BE7DB
XT8 V1 FW SHA-256 : de685082f55a561e96567d2ed076c38aeef251188f66e7052e8674d5df6b7f0f
Download XT8 V1: https://dlcdnets.asus.com/pub/ASUS/..._300438824709.zip?model=ASUS ZenWiFi AX (XT8)

XT8 V2 ZIP SHA-256 : 77AAECE0FAD3126E4EAA043491AAE87BD0878F4C4693D2F7752B73DE3B00C3F1
XT8 V2 FW SHA-256 : 574dc1a6a7c9582e5bc853166f765daa766ecba50ba5c70f12913f2eed6e87cc
Download XT8 V2: https://dlcdnets.asus.com/pub/ASUS/..._300438824709.zip?model=ASUS ZenWiFi AX (XT8)

 

[Jim_OS]

Has anyone been "brave enough" to install the version and if so, have you noticed any problems?

I have version 3.0.0.4.388_24668 installed (XT8 V1), and the release note I get is:

Firmware version 3.0.0.4.388_24709
- Release Note -

New Add:
- WPA Encryption Settings Update. Added new configuration options for WPA encryption, including the option to select AES for improved client compatibility.
This setting can be found under "Network > Main Network".

Bug Fixes and Enhancements:
- Addressed potential irregularities in AiProtection.
- Corrected the issue where the wireless network settings page disappears in AP mode on the WebGUI.
- Enhanced AiCloud password protection mechanisms, safeguarding against unauthorized access attempts.
- Enhanced input parameter handling techniques to improve data processing stability and system security.
- Enhance system access control mechanisms.
- Enhanced security of system command processing to guard against potential malicious operations.
- Fixed compatibility issues with older models, preventing WiFi malfunctions after SDN settings.
- Fixed connectivity issue with Apple wireless devices.
- Fixed an issue that could lead to system failures following a reboot.
- Fixed the malfunction of the "Prefer AP" feature.
- Fixed the issue where devices do not appear in the client list after connecting to the ASUS router.
- Fixed UI issues during VPN file export.
- Improved AiMesh backhaul stability.
- Improved web rendering engine, enhancing browsing experience and security.
- Optimized memory management mechanisms, improving system efficiency and stability.
- Optimized stability and efficiency of the AiMesh system.
- Perfected JavaScript-related security mechanisms, offering a more secure web interaction environment.
- Resolved LAN device disconnections after SDN configuration.
- Strengthened input validation and data processing workflows, further protecting your information security.

 

[naitkris]

Just updated now one XT8 V1 node to 3.0.0.4.388_24709 in a small AiMesh network consisting of the below and so far so good!

Router: ASUS XT8 HW V1 running AsusWrt Merlin GNUton build 3004.388.8_4-gnuton1
Node: ASUS XT8 HW V1 now running this new official firmware 3.0.0.4.388_24709

 

[Waltski]

I have 2 XT8s V1 in AP mode - one of them has updated to 3.0.0.4.388_24709. Spouse usually connects to the updated AP during the day. So far, no complaints (she still uses Nexus 7 2013 tablets which can be finicky with slowdowns/lockups). If we go a few days without any weird issues I'll update the second AP...

 

[jmpr]

Mine updated auomatically last night. But if I try to check updates (I know I have the last one)...

Has this update broken the updating system?

 

[naitkris]

Upgraded now more XT8 V1's (all running as AiMesh nodes) in another network to 3.0.0.4.388_24709 and all is running well and appears stable so far.

 

[Jim_OS]

Since the firmware version does contain some relevant points and fixes, I've just installed it on my three XT8s (AP Mode).

I haven't noticed any issues right now after the installation, but that doesn't mean anything. If I notice any issues in the near future, I'll post them here.

@jmpr For me, searching for a new firmware version works normally even after installing version 3.0.0.4.388_24709.

Have you tried the search again? Perhaps you were simply having a connection problem with the Asus server at that time.

 

[Waltski]

Mine updated auomatically last night. But if I try to check updates (I know I have the last one)...

View attachment 64493

Has this update broken the updating system?

One of my XT8 V1 in access point mode had the same issue after the firmware update - it could not connect to the ASUS server. Checking the system time, it was incorrect by over 2 years (something like December 31, 2023). Any timezone selected would throw up a message that the timezone was inconsistent with the system time. Also, ping would not work in System Tools.

I tried hard hardware reset and set up everything from scratch with my old static IP, DNS and NTP servers, but system time and the other problems returned. I tried rolling back to the previous firmware, but this didn't help.

The only way I could get the XT8 to work properly was by taking the unit off of static IP, using DHCP for IP. I changed my static DNS to different servers and changed the NTP server address from pool.ntp.org to time.nist.gov. Everything then worked fine; pings worked, correct time zone worked, system time was now correct and checking the ASUS firmware update worked again.

I then tried resetting static IP to my previous address, DNS and NTP to previous servers and rebooted, but the same system time error, timezone error and inability to reach the ASUS firmware server returned.
So, I changed back again to using DHCP for IP and resetting different DNS /NTP servers - everything works again just fine.

Go figure...

 

[Jim_OS]

The only way I could get the XT8 to work properly was by taking the unit off of static IP, using DHCP for IP.

Only FYI: I use the DHCP server function of my router (Fritzbox) for IP assignment, i.e. my three XT8s do not have a static IP but are always assigned the same IP via the DHCP server function of the Fritzbox. It's possible, of course, that this is preventing me from having the correct time(zone) and/or accessing the Asus server.

 

[Waltski]

Okay - figured out my problem on the XT8 with static IP issue. My router had reserved an IP for the unit different from the static IP I was trying to set, probably not allowing DNS to start on the XT8. Once I removed the XT8 reserved address from the router the XT8's static IP/DNS allowed the NTP server to connect, setting correct system time which enabled access to the ASUS firmware server.
Both are now on Version 3.0.0.4.388_24709.

 

[dauhee]

I took the chance. Couldn't use any firmware released in the last 3 years as some devices would be in a cycle of constant auth/deauth. After this update I got the usual constant auth/deauth from a couple of edge of coverage devices. I changed 2.4ghz to 20hz and now all good. this quite possibly would have solved my problem years ago with older firmware. I have 3 XT8 nodes in AP mode - AP mode due to getting a plague of issues when first comissioning

 

[crawfish]

I took the chance. Couldn't use any firmware released in the last 3 years as some devices would be in a cycle of constant auth/deauth. After this update I got the usual constant auth/deauth from a couple of edge of coverage devices. I changed 2.4ghz to 20hz and now all good. this quite possibly would have solved my problem years ago with older firmware. I have 3 XT8 nodes in AP mode - AP mode due to getting a plague of issues when first comissioning

OK, that's interesting to me, and it's the first mention I've seen in a few years. To keep my log from being spammed by deauth/auth events from a couple of Lenovo smart clocks, and to keep my Amazon smart thermostat from losing connection a few times per day, which really bugged me, I turned off the 2.4 GHz radio and hooked up a Netgear R6700v3 in access point mode for all my 2.4 GHz devices. I never tried limiting to 20 MHz; I always had it on 20/40. Will have to give that a try sometime...

NB: My auth/deauth were never really in a cycle or constant. Maybe 10 times per day? Anyway, thanks for bringing this up. I love the XT8 except for this.

 

[dauhee]

OK, that's interesting to me, and it's the first mention I've seen in a few years. To keep my log from being spammed by deauth/auth events from a couple of Lenovo smart clocks, and to keep my Amazon smart thermostat from losing connection a few times per day, which really bugged me, I turned off the 2.4 GHz radio and hooked up a Netgear R6700v3 in access point mode for all my 2.4 GHz devices. I never tried limiting to 20 MHz; I always had it on 20/40. Will have to give that a try sometime...

NB: My auth/deauth were never really in a cycle or constant. Maybe 10 times per day? Anyway, thanks for bringing this up. I love the XT8 except for this.

yeah I read somewhere that setting 20mhz can sacrifice higher potential speed for connection reliability which is what I was after as they are just IoT devices on 2.4ghz for me. If only i stumbled on this setting years ago as on my old fwI had a few funnies including apple device connection issues, loss of internet when my public IP changed (resulting in a full wipe and config upload to fix) which I believe this latest fw fixes - 24 hours in and this fw looking positive

 

[crawfish]

yeah I read somewhere that setting 20mhz can sacrifice higher potential speed for connection reliability which is what I was after as they are just IoT devices on 2.4ghz for me. If only i stumbled on this setting years ago as on my old fwI had a few funnies including apple device connection issues, loss of internet when my public IP changed (resulting in a full wipe and config upload to fix) which I believe this latest fw fixes - 24 hours in and this fw looking positive

After 12 hours back to the XT8 on the 20 MHz setting, I saw the red light on my thermostat for the first time in months, and checking the logs, it did the auth/deauth twice in 15 minutes. Unfortunately, the experiment seems to be a bust for me. Back to my R6700v3. ISTR reading earlier Asus routers have the same problem. Did they ever fix it? Or does Asus just suck in general for IoT devices?

 

[Fred777]

TLDR v. sensitive to channel.
I had issue with roaming between a mesh node and a router. It would only connect to the node. To reconnect to the router I had to toggle Wifi on the device. Tech Support had me 2.4G: 40 Mhz Channel {1, 7, 11} already auto on 1 so went to 7 and roaming worked perfectly.

Wifiman good app that continuously shows signal strength to the AP and channel quality... reminder to check both ends as different channel interference.

I didn't conceive that XT8 BW/channel settings would be 0% to 100% but was also case for rejoining mesh after power cycle. Advised 5Ghz 80Mhz {64 or 128}... Since I have separate SSIDs they advised 5GH-1 {36 or 44} again auto was on 44 so switched to 36.

 

[dauhee]

TLDR v. sensitive to channel.
I had issue with roaming between a mesh node and a router. It would only connect to the node. To reconnect to the router I had to toggle Wifi on the device. Tech Support had me 2.4G: 40 Mhz Channel {1, 7, 11} already auto on 1 so went to 7 and roaming worked perfectly.

Wifiman good app that continuously shows signal strength to the AP and channel quality... reminder to check both ends as different channel interference.

I didn't conceive that XT8 BW/channel settings would be 0% to 100% but was also case for rejoining mesh after power cycle. Advised 5Ghz 80Mhz {64 or 128}... Since I have separate SSIDs they advised 5GH-1 {36 or 44} again auto was on 44 so switched to 36.

There can be problematic physical areas between nodes where a client can stick to a node and not get so good performance. There is a setting to change what RSSI it goes below to trigger moving onto another node. I tried that to no avail but it turns out it was a bug with how XT8 handled apple devices.