What's new

Release Asus ZenWiFi XT8 - New Firmware: 3.0.0.4.386_45898

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

So those of you having issues with this firmware (especially it reverting to 2.4Ghz), if you have Apple devices turn off the Private Address option for your Apple devices (phone, iPad, watch, not sure if Apple TV uses private address but if it does, turn that off as well). I have see some issues with private addresses that causes the firmware to complain about sudden drop in signal strength and then it reverts to 2.4Ghz. Switching off private address seems to fix this.
 
On the other hand, if all you change are a few things, similar for me, then a factory reset and manual reconfig is easy. Just a few minutes, and I've found it worth doing for the ZenWiFi AX when upgrading firmware. Just mentioning what works best for you...if not resetting works well for you, enjoy your extra time *smile*.
So I tried resetting both the nodes and set them up from scratch. With basic config (just SSID and passcode) it worked fine for 7 days. However, as soon as I turned on AIprotection, the router started rebooting randomly. This is what I see in the system log. Should I just get a replacement? or continue fiddling with the configuration. I am lost here, didn't have any issues with my AC68U for all these years.


Code:
Nov  2 22:28:15 kernel: page dumped because: bad pte
Nov  2 22:28:15 kernel: addr:b6d30000 vm_flags:00000075 anon_vma:  (null) mapping:df0378cc index:15a
Nov  2 22:28:15 kernel: file:libcrypto.so.1.1 fault:filemap_fault mmap:generic_file_readonly_mmap readpage:squashfs_readpage
Nov  2 22:28:15 kernel: CPU: 2 PID: 7390 Comm: PS_pod Tainted: P    B      O    4.1.52 #2
Nov  2 22:28:15 kernel: Hardware name: Generic DT based system
Nov  2 22:28:15 kernel: [<c0026e60>] (unwind_backtrace) from [<c0022c38>] (show_stack+0x10/0x14)
Nov  2 22:28:15 kernel: [<c0022c38>] (show_stack) from [<c04bace4>] (dump_stack+0x8c/0xa0)
Nov  2 22:28:15 kernel: [<c04bace4>] (dump_stack) from [<c00ab288>] (print_bad_pte+0x138/0x1a0)
Nov  2 22:28:15 kernel: [<c00ab288>] (print_bad_pte) from [<c00ac928>] (unmap_single_vma+0x474/0x520)
Nov  2 22:28:15 kernel: [<c00ac928>] (unmap_single_vma) from [<c00ad78c>] (unmap_vmas+0x54/0x68)
Nov  2 22:28:15 kernel: [<c00ad78c>] (unmap_vmas) from [<c00b34f4>] (exit_mmap+0xdc/0x1dc)
Nov  2 22:28:15 kernel: [<c00b34f4>] (exit_mmap) from [<c002c694>] (mmput+0x38/0xe4)
Nov  2 22:28:15 kernel: [<c002c694>] (mmput) from [<c002faf4>] (do_exit+0x238/0x934)
Nov  2 22:28:15 kernel: [<c002faf4>] (do_exit) from [<c0030fbc>] (do_group_exit+0x38/0xbc)
Nov  2 22:28:15 kernel: [<c0030fbc>] (do_group_exit) from [<c0031050>] (__wake_up_parent+0x0/0x18)
Nov  2 22:28:15 kernel: BUG: Bad rss-counter state mm:ceb6be40 idx:0 val:-1
May  4 22:05:18 kernel: klogd started: BusyBox v1.24.1 (2021-10-04 23:14:39 CST)
May  4 22:05:18 crashlog: LOG
May  4 22:05:18 crashlog: Modules linked in: tdts_udbfw(O) init_addr(  (null) -   (null)), core_addr(bf0aa000 - bf0aedd8)
May  4 22:05:18 crashlog:  tdts_udb(PO) init_addr(  (null) -   (null)), core_addr(bf22b000 - bf249a34)
May  4 22:05:18 crashlog:  tdts(PO) init_addr(  (null) -   (null)), core_addr(bfc0d000 - bfc47790)
May  4 22:05:18 crashlog:  nf_nat_sip init_addr(  (null) -   (null)), core_addr(bfc08000 - bfc096d0)
May  4 22:05:18 crashlog:  nf_conntrack_sip init_addr(  (null) -   (null)), core_addr(bfbff000 - bfc01dbc)
May  4 22:05:18 crashlog:  nf_nat_h323 init_addr(  (null) -   (null)), core_addr(bfbfa000 - bfbfaf50)
May  4 22:05:18 crashlog:  nf_conntrack_h323 init_addr(  (null) -   (null)), core_addr(bfbeb000 - bfbee8d4)
May  4 22:05:18 crashlog:  nf_nat_rtsp init_addr(  (null) -   (null)), core_addr(bfbe7000 - bfbe7830)
May  4 22:05:18 crashlog:  nf_conntrack_rtsp init_addr(  (null) -   (null)), core_addr(bfbe1000 - bfbe2208)
May  4 22:05:18 crashlog:  nf_nat_ftp init_addr(  (null) -   (null)), core_addr(bfbdd000 - bfbdd228)
May  4 22:05:18 crashlog:  nf_conntrack_ftp init_addr(  (null) -   (null)), core_addr(bfbd8000 - bfbd8b88)
May  4 22:05:18 kernel: Linux version 4.1.52 (gitserv_asus@tpbuildsvrvu01) (gcc version 5.5.0 (Buildroot 2017.11.1) ) #2 SMP PREEMPT Tue Oct 5 00:40:17 CST 2021
May  4 22:05:18 crashlog:  ath3k init_addr(  (null) -   (null)), core_addr(bfbd2000 - bfbd2888)
May  4 22:05:18 crashlog:  btusb init_addr(  (null) -   (null)), core_addr(bfbc6000 - bfbc9ff4)
May  4 22:05:18 crashlog:  btintel init_addr(  (null) -   (null)), core_addr(bfbc2000 - bfbc2198)
May  4 22:05:18 crashlog:  thfsplus(O) init_addr(  (null) -   (null)), core_addr(bfba6000 - bfbb1c10)
May  4 22:05:18 crashlog:  tntfs(PO) init_addr(  (null) -   (null)), core_addr(bfb1f000 - bfb6d8fc)
May  4 22:05:18 kernel: Kernel command line: isolcpus=3 root=/dev/ubiblock0_0 ubi.mtd=0 ubi.block=0,0 rootfstype=squashfs console=ttyAMA0 earlyprintk debug irqaffinity=0 pci=pcie_bus_safe
 
That is great to news. This was sent to me by ASUS as a fix to some problems I have with Microsoft Teams.

I have found it very stable as well, only reverted to 45898 as I need Parental Control.
Unfortunately I have run into a new kernel error problem. Any idea?

Nov 4 15:39:12 kernel: ^[[0;33;41m[ERROR archer] archer_mcast_activate,577: ADD_PORT: WLAN SSID has already been added: egress_port 6, current 0x0001, new 0x0001^[[0m
Nov 4 15:48:16 kernel: ^[[0;33;41m[ERROR archer] archer_mcast_activate,577: ADD_PORT: WLAN SSID has already been added: egress_port 6, current 0x0001, new 0x0001^[[0m
Nov 4 16:08:28 kernel: ^[[0;33;41m[ERROR archer] archer_mcast_activate,577: ADD_PORT: WLAN SSID has already been added: egress_port 6, current 0x0001, new 0x0001^[[0m
 
So I tried resetting both the nodes and set them up from scratch. With basic config (just SSID and passcode) it worked fine for 7 days. However, as soon as I turned on AIprotection, the router started rebooting randomly. This is what I see in the system log. Should I just get a replacement? or continue fiddling with the configuration. I am lost here, didn't have any issues with my AC68U for all these years.


Code:
Nov  2 22:28:15 kernel: page dumped because: bad pte
Nov  2 22:28:15 kernel: addr:b6d30000 vm_flags:00000075 anon_vma:  (null) mapping:df0378cc index:15a
Nov  2 22:28:15 kernel: file:libcrypto.so.1.1 fault:filemap_fault mmap:generic_file_readonly_mmap readpage:squashfs_readpage
Nov  2 22:28:15 kernel: CPU: 2 PID: 7390 Comm: PS_pod Tainted: P    B      O    4.1.52 #2
Nov  2 22:28:15 kernel: Hardware name: Generic DT based system
Nov  2 22:28:15 kernel: [<c0026e60>] (unwind_backtrace) from [<c0022c38>] (show_stack+0x10/0x14)
Nov  2 22:28:15 kernel: [<c0022c38>] (show_stack) from [<c04bace4>] (dump_stack+0x8c/0xa0)
Nov  2 22:28:15 kernel: [<c04bace4>] (dump_stack) from [<c00ab288>] (print_bad_pte+0x138/0x1a0)
Nov  2 22:28:15 kernel: [<c00ab288>] (print_bad_pte) from [<c00ac928>] (unmap_single_vma+0x474/0x520)
Nov  2 22:28:15 kernel: [<c00ac928>] (unmap_single_vma) from [<c00ad78c>] (unmap_vmas+0x54/0x68)
Nov  2 22:28:15 kernel: [<c00ad78c>] (unmap_vmas) from [<c00b34f4>] (exit_mmap+0xdc/0x1dc)
Nov  2 22:28:15 kernel: [<c00b34f4>] (exit_mmap) from [<c002c694>] (mmput+0x38/0xe4)
Nov  2 22:28:15 kernel: [<c002c694>] (mmput) from [<c002faf4>] (do_exit+0x238/0x934)
Nov  2 22:28:15 kernel: [<c002faf4>] (do_exit) from [<c0030fbc>] (do_group_exit+0x38/0xbc)
Nov  2 22:28:15 kernel: [<c0030fbc>] (do_group_exit) from [<c0031050>] (__wake_up_parent+0x0/0x18)
Nov  2 22:28:15 kernel: BUG: Bad rss-counter state mm:ceb6be40 idx:0 val:-1
May  4 22:05:18 kernel: klogd started: BusyBox v1.24.1 (2021-10-04 23:14:39 CST)
May  4 22:05:18 crashlog: LOG
May  4 22:05:18 crashlog: Modules linked in: tdts_udbfw(O) init_addr(  (null) -   (null)), core_addr(bf0aa000 - bf0aedd8)
May  4 22:05:18 crashlog:  tdts_udb(PO) init_addr(  (null) -   (null)), core_addr(bf22b000 - bf249a34)
May  4 22:05:18 crashlog:  tdts(PO) init_addr(  (null) -   (null)), core_addr(bfc0d000 - bfc47790)
May  4 22:05:18 crashlog:  nf_nat_sip init_addr(  (null) -   (null)), core_addr(bfc08000 - bfc096d0)
May  4 22:05:18 crashlog:  nf_conntrack_sip init_addr(  (null) -   (null)), core_addr(bfbff000 - bfc01dbc)
May  4 22:05:18 crashlog:  nf_nat_h323 init_addr(  (null) -   (null)), core_addr(bfbfa000 - bfbfaf50)
May  4 22:05:18 crashlog:  nf_conntrack_h323 init_addr(  (null) -   (null)), core_addr(bfbeb000 - bfbee8d4)
May  4 22:05:18 crashlog:  nf_nat_rtsp init_addr(  (null) -   (null)), core_addr(bfbe7000 - bfbe7830)
May  4 22:05:18 crashlog:  nf_conntrack_rtsp init_addr(  (null) -   (null)), core_addr(bfbe1000 - bfbe2208)
May  4 22:05:18 crashlog:  nf_nat_ftp init_addr(  (null) -   (null)), core_addr(bfbdd000 - bfbdd228)
May  4 22:05:18 crashlog:  nf_conntrack_ftp init_addr(  (null) -   (null)), core_addr(bfbd8000 - bfbd8b88)
May  4 22:05:18 kernel: Linux version 4.1.52 (gitserv_asus@tpbuildsvrvu01) (gcc version 5.5.0 (Buildroot 2017.11.1) ) #2 SMP PREEMPT Tue Oct 5 00:40:17 CST 2021
May  4 22:05:18 crashlog:  ath3k init_addr(  (null) -   (null)), core_addr(bfbd2000 - bfbd2888)
May  4 22:05:18 crashlog:  btusb init_addr(  (null) -   (null)), core_addr(bfbc6000 - bfbc9ff4)
May  4 22:05:18 crashlog:  btintel init_addr(  (null) -   (null)), core_addr(bfbc2000 - bfbc2198)
May  4 22:05:18 crashlog:  thfsplus(O) init_addr(  (null) -   (null)), core_addr(bfba6000 - bfbb1c10)
May  4 22:05:18 crashlog:  tntfs(PO) init_addr(  (null) -   (null)), core_addr(bfb1f000 - bfb6d8fc)
May  4 22:05:18 kernel: Kernel command line: isolcpus=3 root=/dev/ubiblock0_0 ubi.mtd=0 ubi.block=0,0 rootfstype=squashfs console=ttyAMA0 earlyprintk debug irqaffinity=0 pci=pcie_bus_safe
I would not initiate AIProtection or QOS for stability reasons. There are many things that can be adjusted but some features are liable to instability
 
Unfortunately I have run into a new kernel error problem. Any idea?

Nov 4 15:39:12 kernel: ^[[0;33;41m[ERROR archer] archer_mcast_activate,577: ADD_PORT: WLAN SSID has already been added: egress_port 6, current 0x0001, new 0x0001^[[0m
Nov 4 15:48:16 kernel: ^[[0;33;41m[ERROR archer] archer_mcast_activate,577: ADD_PORT: WLAN SSID has already been added: egress_port 6, current 0x0001, new 0x0001^[[0m
Nov 4 16:08:28 kernel: ^[[0;33;41m[ERROR archer] archer_mcast_activate,577: ADD_PORT: WLAN SSID has already been added: egress_port 6, current 0x0001, new 0x0001^[[0m
FYI, this was solved with the 3.0.0.4.386_45934.
 
Hi guys,

for me all firmware after ZENWIFI_XT8_3.0.0.4_386_25790 totally breaks SONOS for me. Just upgrades to latest version and it broke down again. Uploaded ZENWIFI_XT8_3.0.0.4_386_25790 and we got back in business. Does anyone know why?
Altough it works when connected to ethernet. The problem is WiFi
 
Hi guys,

for me all firmware after ZENWIFI_XT8_3.0.0.4_386_25790 totally breaks SONOS for me. Just upgrades to latest version and it broke down again. Uploaded ZENWIFI_XT8_3.0.0.4_386_25790 and we got back in business. Does anyone know why?
Altough it works when connected to ethernet. The problem is WiFi
Check out: https://www.asus.com/support/FAQ/1042475 and see if it helps
 
Did the upgrade yesterday. 26 hours later all XD4 nodes in the mesh went Red as if they were disconnected from the internet. First time that had happened in the 6 months I've owned this mesh setup. Cable modem registered as online entire time, ISP said zero disruptions had occurred, and the router had no errors in the log (not even a reboot). Restarting cable modem didn't help. But, the issue naturally resolved itself after about 10 minutes.

I Attempted to use "manual firmware update" feature in the firmware upgrade tab to revert back to 43129, but the router still says its on 45934. Maybe you can't use "manual firmware update" to revert firmware? At this point I'm just waiting another 26 hours to see if it disconnects again.

I did not do factory resets after upgrades. Not sure if that is root cause of the problem.
 

Attachments

  • Firmware update.png
    Firmware update.png
    508.6 KB · Views: 115
Last edited:
Did the upgrade yesterday. 26 hours later all XD4 nodes in the mesh went Red as if they were disconnected from the internet. First time that had happened in the 6 months I've owned this mesh setup. Cable modem registered as online entire time, ISP said zero disruptions had occurred, and the router had no errors in the log (not even a reboot). Restarting cable modem didn't help. But, the issue naturally resolved itself after about 10 minutes.

I Attempted to use "manual firmware update" feature in the firmware upgrade tab to revert back to 43129, but the router still says its on 45934. Maybe you can't use "manual firmware update" to revert firmware? At this point I'm just waiting another 26 hours to see if it disconnects again.

I did not do factory resets after upgrades. Not sure if that is root cause of the problem.

Yes, using the "manual firmware update" is how you revert firmware. I haven't had a problem doing that, have visited a lot of firmware versions...maybe you need to do a reset before reverting and/or disconnect USB disks. But yes, you will be able to revert to an earlier firmware version using "manual firmware update".
 
Yes, using the "manual firmware update" is how you revert firmware. I haven't had a problem doing that, have visited a lot of firmware versions...maybe you need to do a reset before reverting and/or disconnect USB disks. But yes, you will be able to revert to an earlier firmware version using "manual firmware update".
Went ahead and did factory reset on all three nodes. Crossing fingers that I get no more red lights. If I do, will prob need to try the ‘manual firmware update’ again. Or call support.

Settings I am using:
-Specify my own lan ip
-assign static reservations for 9-10 dhcp clients
-1 port being forwarded for Plex
-provide my own dns in dhcp settings (pi-hole)
-specify wifi channels
-turned on dynamic dns

Pretty vanilla stuff
 
Last edited:
Hi guys,

for me all firmware after ZENWIFI_XT8_3.0.0.4_386_25790 totally breaks SONOS for me. Just upgrades to latest version and it broke down again. Uploaded ZENWIFI_XT8_3.0.0.4_386_25790 and we got back in business. Does anyone know why?
Altough it works when connected to ethernet. The problem is WiFi
I had the same issue and found a post somewhere that mentioned multicast routing. After enabling that, my Sonos speakers have been working perfectly.

I also have 'Smart Connect' and 'Wi-Fi Agile Multiband' disabled, but '802.11ax / WiFi 6 mode' and 'Target Wake Time' are still enabled, and 'Protected Management Frames' is set to "Capable".

With those settings, I simply connected the Sonos speakers to the SSID for my 2.4 GHz network

(Advanced Settings > LAN > IPTV)
1636656531677.png


1636656627038.png
 
I have a quick question my isp speed is 500Mbps. When I test my speed using asus internet speed test I get 530Mbps. My problem is when test using 5ghz and I literally beside my asus xt8 I only get 380Mbps tops. What is the problem?
 
Right beside the router? Too close. Test at least 3 to 4 metres away.

What client device are you using? If not testing with a laptop, plugged into AC power, with the power plan set to Performance, you're not testing properly.

It also depends on what Wi-Fi adaptor the client device is using, how many antennae/streams it supports, the driver version of the said adaptor and not to mention the Control channel and Channel Width the router is set to, too.
 
Right beside the router? Too close. Test at least 3 to 4 metres away.

What client device are you using? If not testing with a laptop, plugged into AC power, with the power plan set to Performance, you're not testing properly.

It also depends on what Wi-Fi adaptor the client device is using, how many antennae/streams it supports, the driver version of the said adaptor and not to mention the Control channel and Channel Width the router is set to, too.
Yup right beside and aroung the main router. Im using my windows laptop and my iphone 13 getting the same speed on both only 380-400Mbps tops and change my setting to 80mhz on 5ghz same results. Im thinking of changing to Orbi.
 
You're still too close (even with the laptop). The other questions weren't answered either. :)

For example, I easily get 850Mbps speeds from my laptop with a Wi-Fi 6E AX210 adaptor, from a room, and a floor away from my RT-AX86U AiMesh (wired backhaul) node. That straight line distance is about four metres.
 
Hi guys,

for me all firmware after ZENWIFI_XT8_3.0.0.4_386_25790 totally breaks SONOS for me. Just upgrades to latest version and it broke down again. Uploaded ZENWIFI_XT8_3.0.0.4_386_25790 and we got back in business. Does anyone know why?
Altough it works when connected to ethernet. The problem is WiFi

Unfortunately, I’ve always had issues with ASUS and sonos. Eventually, I bought a sonos boost, which basically solved the problem by running sonos on its own mesh network instead of wifi. That has other advantages, but for me it was worth it to not constantly deal with sonos wifi connection issues with several versions of ASUS routers.
 
Upgrade a couple of days ago.

There are a few of things I noticed:
1. Lower WAN speeds
2. The WAN Speedtest is missing
3. Loosing Internet connection daily once in the mornings.
Hi ,

May you elaborate please? I recently bought a couple of XT8 so I'm new to the stuff. I upgraded them almost immediately ans noticed my WAN speed decrease after let's say 8 to 12h00 and remains stable but I loose 10-15% of my WAN download speed. I tried to reset them following procedure I found on this forum, but no change.
It may be some settings I use, as said I'm starting the look for the root cause.
The Speedtest is there for me, no Wan disconnection but download only slow down.
 
Anybody know of a similar beta firmware for ET8? (AXE6600 x 2). It looks like they do not share common firmware, despite being nearly identical aside from the 6ghz upgrade on the third wifi.
ET8 Current Version : 3.0.0.4.386_43981-g8cc0fd3

They drop connections often when we have seneral active streams and/or games going. Sorry for "crossposting" ET8 but I'm hoping whoever found that knows more :)

---
Sorry, read a bit more and discovered 9.0.x is beta. And found the original link to the GDrive, which has this beta for multiple versions. All good, I'm hoping it makes a noticeable difference today!

 
Last edited:

Latest threads

Sign Up For SNBForums Daily Digest

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