Release ASUS ZenWIFI XT8 Firmware version 3.0.0.4.388_24621

[crawfish]

Been running this version since it was released with no problem except the one I've always had with my XT8. I run it as a single router, and devices like Google Nest Hub and Mini, Lenovo smart clocks, and Amazon Smart Thermostat lose connection and reconnect several times a day. The log messages are all like the following:

Jun 15 21:05:07 wlceventd: wlceventd_proc_event(645): eth4: Deauth_ind xx:xx:xx:xx:xx:xx, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Jun 15 21:05:13 wlceventd: wlceventd_proc_event(685): eth4: Auth xx:xx:xx:xx:xx:xx, status: Successful (0), rssi:0
Jun 15 21:05:13 wlceventd: wlceventd_proc_event(722): eth4: Assoc xx:xx:xx:xx:xx:xx, status: Successful (0), rssi:-37

I've found several threads on this but never a solution, and I've tried many things to fix it over the couple of years I've had these smart devices. I get better performance for these devices using my R6700v3 as bridge for 2.4 GHz and disabling that radio in my XT8, which I've gone back to doing after a spate of noticeable trouble in the last few days.

 

[arnerek]

I have the same experience as you. The XT8 has never given me stable 2.4 GHz experience but I am really happy with the 5 GHz performance and stability.

 

[crawfish]

I have the same experience as you. The XT8 has never given me stable 2.4 GHz experience but I am really happy with the 5 GHz performance and stability.

Yep, the 5 GHz has exceeded expectations. In particular, I use the 5 Ghz-2 in AX-only mode for my file server in another room, and it provides a solid 1 Gbps connection. I typically get 110 MBps file transfers per Windows Explorer, and it's also been great for Kodi, no latency when skipping forward/back or any other anomalies. I just wish I understood how they screwed up 2.4 GHz so badly.

 

[w0lfm0n]

I wanted to update from 42095 to this firmware. I have 2 XT8 in a mesh. When I used the UI I updated the firmware and it updated the node. I then ran it again to update the main router and it just will not update the firmware. It goes through the whole process only to reboot still on 42095. I have tried through the webui via the prompt to update, I have manually updated using the downloaded file. I have also used the mobile app to update. Each time it fails. Nothing in the log shows any errors, just the restart.

Does anyone have any ideas how I can get this device to update it's firmware?

 

[MoreloS]

It appears I am not alone still running 42095. I had so much hassle prior to returning to this version 3 years ago that I have lived in fear, if it ain't broke don't fix it. Now I have an issue with openVPN server. On the client side I upgraded my android app, and found it would not connect. I was finally able to do so by reducing the app security level. I have not upgraded the WIN 11 app, yet! I assume that at some point one of the XT8 firmware upgrades also upgraded the openVPN server element. So my question is do I upgrade the XT8 firmware or leave at 42095.

 

[kaktus]

It appears I am not alone still running 42095. I had so much hassle prior to returning to this version 3 years ago that I have lived in fear, if it ain't broke don't fix it. Now I have an issue with openVPN server. On the client side I upgraded my android app, and found it would not connect. I was finally able to do so by reducing the app security level. I have not upgraded the WIN 11 app, yet! I assume that at some point one of the XT8 firmware upgrades also upgraded the openVPN server element. So my question is do I upgrade the XT8 firmware or leave at 42095.

I'm facing similar issues/challenges with 48706. I have a rock solid uptime and connectivity stability with 48706, which was never the case with any trailing update. So far any update onwards 48706 results in backhaul connectivity issues and poor performance. Merlin is no option for me since I'm using a wireless backhaul and AIMesch is proprietary code from Asus, so I guess the backhaul issue's will also affect the Merlin firmware.

 

[siriuz]

For me this have been the best firmware for quite some time. Runs stable.
I have 4 units all using wireless backhaul. 2 of them are between two different houses, averaging a RSSI at 78-82 dpi.
Using other firmwares, the two units would drop out and/or fall back to 2.4ghz never reverting back to 5ghz without reboot. With this firmware it runs stable 5ghz.
A few time it fell back to 2.4ghz but reverted to 5ghz with in 5 minutes.

I've also used Merlin's firmware but not with the same success as this firmware.

 

[Hozz]

For me this have been the best firmware for quite some time. Runs stable.
I have 4 units all using wireless backhaul. 2 of them are between two different houses, averaging a RSSI at 78-82 dpi.
Using other firmwares, the two units would drop out and/or fall back to 2.4ghz never reverting back to 5ghz without reboot. With this firmware it runs stable 5ghz.
A few time it fell back to 2.4ghz but reverted to 5ghz with in 5 minutes.

I've also used Merlin's firmware but not with the same success as this firmware.

I agree this update has been rock solid for me since I installed it in April.

 

[kaktus]

I agree this update has been rock solid for me since I installed it in April.

Do you have version 1 or 2 XT8 routers?

 

[Hozz]

Do you have version 1 or 2 XT8 routers?

Version 1.

 

[kaktus]

Thanks for the quick response. In that case I will try this latest version, because it adds important security fixes.

 

[siriuz]

Do you have version 1 or 2 XT8 routers?

To add to this. I have this firmware running on both version 1 and 2, in the same mesh network. Both runs amazing, and no problem with the two versions connecting to each other

 

[jksmurf]

To add to this. I have this firmware running on both version 1 and 2, in the same mesh network. Both runs amazing, and no problem with the two versions connecting to each other

Could you advise your backhaul connection method i.e. Wired or Wireless please? Just for the data point really.

 

[Topazali]

Just to add to this as well. I'm also currently using both V1 and V2 XT8s with a wireless backhaul with firmware 24621 with no issues. Very stable.

 

[siriuz]

Just to add to this as well. I'm also currently using both V1 and V2 XT8s with a wireless backhaul with firmware 24621 with no issues. Very stable.

That is all wireless backhaul

 

[kaktus]

I tried this version for 3 days, but unfortunately my setup ran in to wireless backhaul issues. It keeps reverting back to 2,4GHz and 20mhz bandwidth. I downgraded to version 48706 and everything is rock solid again. I decided that I leave it this way and take the vulnerabilities for granted.

 

[mrbill]

I tried this version for 3 days, but unfortunately my setup ran in to wireless backhaul issues. It keeps reverting back to 2,4GHz and 20mhz bandwidth. I downgraded to version 48706 and everything is rock solid again. I decided that I leave it this way and take the vulnerabilities for granted.

I see FW 24668 is available in the app, but not on their USA site. Might want to try that one, but who knows what it fixes with no release notes posted by ASUS.

 

[kaktus]

I see FW 24668 is available in the app, but not on their USA site. Might want to try that one, but who knows what it fixes with no release notes posted by ASUS.

I switched to the latest Merlin firmware and this works better, but still not as stable as the (386) 48706 version.

 

[naitkris]

I switched to the latest Merlin firmware and this works better, but still not as stable as the (386) 48706 version.

Did you try keeping the XT8 Router on 3.0.0.4.388.8_2-gnuton1 and the XT8 Node on latest stock firmware (so 3.0.0.4.388_24668)? As per https://github.com/RMerl/asuswrt-merlin.ng/wiki/AiMesh it is written:

While Merlin-based nodes seem to work fine so far (aside from the above limitation), there is generally little benefit in running it on a node, so it's generally recommended to leave your nodes on the stock Asus firmware.

Also numerous posts on snbforums recommend to keep the AiMesh node(s) on stock firmware.

My experience with AiMesh and having Merlin firmware for the nodes is mixed. I have two environments with AiMesh - one small and one large together with Merlin firmware (GNUton's Asus Merlin for the XT8).

Environment 1 (XT8 Router + XT8 Node both running 3004.388.8_2-gnuton1): Working fine and no issues experienced for many weeks now.
Environment 2 (GT-AX11000 Pro Router running Merlin 3004.388.8_2 + two RP-AX58 Nodes on stock 3.0.0.4.388_24654 + four XT8 Nodes all running 3004.388.7_1-gnuton1): Worked fine after setup for many weeks however after a prolonged downtime of the GT-AX11000 Pro Router due to some maintenance in my home (so more than 1 day the router was powered down while all nodes were still powered on), after the GT-AX11000 Pro Router was later powered back on, none of the XT8's on GNUton's Asus Merlin 3004.388.7_1-gnuton1 came back in to the mesh. However both the RP-AX58's on stock 3.0.0.4.388_24654 came back in to the AiMesh network immediately and no issues seen with them after multiple reboots (so the opposite for all the XT8's on 3004.388.7_1-gnuton1). One of the four XT8's is also wired and still did not come back in to the AiMesh network.

 

[kaktus]

Thanks for sharing this. After 13 days of uptime (with Merlin) I ran in to backhaul issues. When I r

Did you try keeping the XT8 Router on 3.0.0.4.388.8_2-gnuton1 and the XT8 Node on latest stock firmware (so 3.0.0.4.388_24668)? As per https://github.com/RMerl/asuswrt-merlin.ng/wiki/AiMesh it is written:

Also numerous posts on snbforums recommend to keep the AiMesh node(s) on stock firmware.

My experience with AiMesh and having Merlin firmware for the nodes is mixed. I have two environments with AiMesh - one small and one large together with Merlin firmware (GNUton's Asus Merlin for the XT8).

Environment 1 (XT8 Router + XT8 Node both running 3004.388.8_2-gnuton1): Working fine and no issues experienced for many weeks now.
Environment 2 (GT-AX11000 Pro Router running Merlin 3004.388.8_2 + two RP-AX58 Nodes on stock 3.0.0.4.388_24654 + four XT8 Nodes all running 3004.388.7_1-gnuton1): Worked fine after setup for many weeks however after a prolonged downtime of the GT-AX11000 Pro Router due to some maintenance in my home (so more than 1 day the router was powered down while all nodes were still powered on), after the GT-AX11000 Pro Router was later powered back on, none of the XT8's on GNUton's Asus Merlin 3004.388.7_1-gnuton1 came back in to the mesh. However both the RP-AX58's on stock 3.0.0.4.388_24654 came back in to the AiMesh network immediately and no issues seen with them after multiple reboots (so the opposite for all the XT8's on 3004.388.7_1-gnuton1). One of the four XT8's is also wired and still did not come back in to the AiMesh network.

Thanks for the advise, I was not aware of the recommendation to leave the node on stock firmware.