Release Asus ZenWiFi XT8 - New Firmware: 3.0.0.4.386_45934

[Dodgydrains]

Looks like a new firmware is available via the GUI. Will be updating to it shortly.

Firmware version 3.0.0.4.386_45934
- Release Note -

Bug Fixes and Improvements:
1. Fixed Let's encrypt related bugs.
2. Fixed httpd vulnerability
3. Fixed stack overflow vulnerability
4. Fixed DoS vulnerability

Edit: Found this link under Windows XP 64-bit

https://dlcdnets.asus.com/pub/ASUS/wireless/ZenWiFi_XT8/FW_ZENWIFI_XT8_300438645934.zip

 

[Mikeyboyeee]

Wonder how it differs from the Beta.

 

[RogerSC]

Installed this new version, looked at the log, and was immediately presented with a screen full of "<mac address> not mesh client, can't delete it", same as 45898. Not impressed *smile*. Not sure that I'll bother with it.

 

[toaruScar]

This update did fix the "Let's encrypt bug" for me. No more DDNS update errors.

 

[pantsontoast]

I tried this firmware update and still get significant packet loss within the network only on two MacBookPros as described in this post. Downgraded back to 42095 again. I still have a support ticket open with ASUS, but they have yet to respond with anything helpful.

 

[in2ndo]

Updated mine yesterday. Used the routers web interface. It all went fine and I’m still getting my over 450Mbps down of the 400 I’m paying for. And no issues with the over 20 devices connected.

 

[kobilica]

I upgraded a few days ago on two nodes. I am facing frequent crashes when USB disk is attached and used for Mac Time Machine backup. The behavior was the same with the previous firmware.
The system is more stable without an attached USB disk.
Anyone has similar experience and maybe problem resolution?

 

[rsnhakan]

No problems here updated through interface.

 

[Piel]

Updated mine yesterday. Used the routers web interface. It all went fine and I’m still getting my over 450Mbps down of the 400 I’m paying for. And no issues with the over 20 devices connected.

And what is your upload speed? Mine is still garbage at 120 when it should be at 500...

 

[in2ndo]

And what is your upload speed? Mine is still garbage at 120 when it should be at 500...

I have a basic cable package. So the upload is only 25 to 50. And that’s what I’m getting.

 

[Dodgydrains]

And what is your upload speed? Mine is still garbage at 120 when it should be at 500...

My package is 1Gb upload and download. Wired speed is 945 up and 925 down. Wireless using an Oppo android phone maximum speed was 850 up and 875 down. This is all with speedtest.net.

 

[BrendonSF]

Anyone know if this fixes the IoT device disconnects? I'm finally stable on the beta 9.0.1.4_386_46197 beta firmware, and am feeling pretty risk averse at this point.

 

[ThatGuyinNC]

Anyone know if this fixes the IoT device disconnects? I'm finally stable on the beta 9.0.1.4_386_46197 beta firmware, and am feeling pretty risk averse at this point.

I am reverting as I was losing even more devices and receiving the kernel errors on this update. Having to revert and factory reset is not ideal but would like to use the devices as intended.

 

[slikr]

just upgraded everything working fine so far.

 

[shama_001]

Hi all,

(I posted almost the same in another topic)
I'm new in the XT8 stuff, now upgraded to this FW so barely not experience with older version. So far so good, testing a lot of stuff, but I'm concerned by the WAN speed I'm able to reach: I get my Up&Download fully but after 8 to 12hours the download speed decrease (-15%). I need a bigger picture about this and how it behaves by time but restating the router gives me back the lost speed.
This is true with wired computer & internal router speedtest.

Is this something usual, specific to last FW, or you never notice such?

 

[bradbort]

Well this is a puzzle. Around the same day that this mesh router updated to new firmware, my nest thermostat also updated its firmware. Since that date, the nest app has shown the thermostat to be disconnected about once a day. Rebooting the router does not help. Rebooting the thermostat does. Lots of chit chat on the google/nest forum about the firmware creating issues, some connectivity, but it seems to be limited to older nest learning thermostats 3, leading folks to suspect some chip differences over the years. No other IOT devices are showing issues, just the Nest thermostat. Nest protects and Nest doorbell are all fine.

So, is the problem with the thermostat’s firmware or the router’s firmware. I actually just set up a repeater, and linked the nest to that instead of directly to the router, and it has stayed stable since then.

Anyone who knows more about this stuff then me (practically anyone) have some thoughts about what is going on.

 

[h1berto]

I'm experience a weird problem.
Without any warning my connection status just changes to "disconnected".
I reboot the router and it's all good.
On the log i see a lot of kernel entries...could it be related?
Just before the "disconnect":

Nov 17 09:57:43 rc_service: httpd 1723:notify_rc reboot
Nov 17 09:57:46 iTunes: daemon is stoped
Nov 17 09:57:46 FTP Server: daemon is stopped
Nov 17 09:57:46 Samba Server: smb daemon is stoped
Nov 17 09:57:46 Timemachine: daemon is stoped
Nov 17 09:57:46 WEBDAV Server: daemon is stoped
Nov 17 09:57:48 BWDPI: force to flush flowcache entries
Nov 17 09:57:48 BWDPI: rollback fc
Nov 17 09:57:48 WEBDAV Server: daemon is stoped
Nov 17 09:57:49 Mastiff: Got SIGTERM
Nov 17 09:57:49 hour monitor: dpi engine doesn't exist
Nov 17 09:57:50 iTunes: daemon is stoped
Nov 17 09:57:50 FTP Server: daemon is stopped
Nov 17 09:57:50 Samba Server: smb daemon is stoped
Nov 17 09:57:50 Timemachine: daemon is stoped
Nov 17 09:57:50 disk_monitor: Finish
Nov 17 09:57:52 ahs: ===Terminate ahs daemon===
Nov 17 09:57:53 kernel: CPU: 2 PID: 2288 Comm: cfg_server Tainted: P O 4.1.52 #2
Nov 17 09:57:53 kernel: Hardware name: Generic DT based system
Nov 17 09:57:53 kernel: task: d27be000 ti: d27cc000 task.ti: d27cc000
Nov 17 09:57:53 kernel: PC is at 0x6edac
Nov 17 09:57:53 kernel: LR is at 0x6ed78
Nov 17 09:57:53 kernel: pc : [<0006edac>] lr : [<0006ed78>] psr: 200f0010
Nov 17 09:57:53 kernel: sp : b68b5cb0 ip : ffffffff fp : b6f9b878
Nov 17 09:57:53 kernel: r10: 000b5000 r9 : b671f250 r8 : bedeeb82
Nov 17 09:57:53 kernel: r7 : b68b5d0c r6 : 00000000 r5 : 00000000 r4 : 00000001
Nov 17 09:57:53 kernel: r3 : b6ff0000 r2 : b6ff1000 r1 : 00000031 r0 : 00000005
Nov 17 09:57:53 kernel: Flags: nzCv IRQs on FIQs on Mode USER_32 ISA ARM Segment user
Nov 17 09:57:53 kernel: Control: 10c5387d Table: 1277004a DAC: 00000015
Nov 17 09:57:53 kernel: CPU: 2 PID: 2288 Comm: cfg_server Tainted: P O 4.1.52 #2
Nov 17 09:57:53 kernel: Hardware name: Generic DT based system
Nov 17 09:57:53 kernel: [<c0026e60>] (unwind_backtrace) from [<c0022c38>] (show_stack+0x10/0x14)
Nov 17 09:57:53 kernel: [<c0022c38>] (show_stack) from [<c04bace4>] (dump_stack+0x8c/0xa0)
Nov 17 09:57:53 kernel: [<c04bace4>] (dump_stack) from [<c003aaec>] (get_signal+0x490/0x558)
Nov 17 09:57:53 kernel: [<c003aaec>] (get_signal) from [<c00221d0>] (do_signal+0xc8/0x3ac)
Nov 17 09:57:53 kernel: [<c00221d0>] (do_signal) from [<c0022658>] (do_work_pending+0x94/0xa4)
Nov 17 09:57:53 kernel: [<c0022658>] (do_work_pending) from [<c001f4cc>] (work_pending+0xc/0x20)
Nov 17 09:57:53 kernel: port_generic_stop 561 skip turnning off power on eth1 here
Nov 17 09:57:53 kernel: port_generic_stop 561 skip turnning off power on eth2 here
Nov 17 09:57:53 kernel: port_generic_stop 561 skip turnning off power on eth3 here
Nov 17 09:57:54 kernel: ubi2: attaching mtd10
Nov 17 09:57:54 kernel: ubi2: scanning is finished
Nov 17 09:57:54 kernel: ubi2: attached mtd10 (name "misc1", size 8 MiB)
Nov 17 09:57:54 kernel: ubi2: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
Nov 17 09:57:54 kernel: ubi2: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
Nov 17 09:57:54 kernel: ubi2: VID header offset: 2048 (aligned 2048), data offset: 4096
Nov 17 09:57:54 kernel: ubi2: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
Nov 17 09:57:54 kernel: ubi2: user volume: 1, internal volumes: 1, max. volumes count: 128
Nov 17 09:57:54 kernel: ubi2: max/mean erase counter: 8/3, WL threshold: 4096, image sequence number: 1526576606
Nov 17 09:57:54 kernel: ubi2: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 4
Nov 17 09:57:54 kernel: ubi2: background thread "ubi_bgt2d" started, PID 4219
Nov 17 09:57:55 kernel: UBIFS (ubi2:0): background thread "ubifs_bgt2_0" started, PID 4234
Nov 17 09:57:55 kernel: UBIFS (ubi2:0): UBIFS: mounted UBI device 2, volume 0, name "nvram"
Nov 17 09:57:55 kernel: UBIFS (ubi2:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
Nov 17 09:57:55 kernel: UBIFS (ubi2:0): FS size: 5840896 bytes (5 MiB, 46 LEBs), journal size 1396736 bytes (1 MiB, 11 LEBs)
Nov 17 09:57:55 kernel: UBIFS (ubi2:0): reserved for root: 0 bytes (0 KiB)
Nov 17 09:57:55 kernel: UBIFS (ubi2:0): media format: w4/r0 (latest is w4/r0), UUID 9DC75FF7-E8C0-4018-A1ED-1D54D1E5AC77, small LPT model
Nov 17 09:57:55 kernel: UBIFS (ubi2:0): un-mount UBI device 2
Nov 17 09:57:55 kernel: UBIFS (ubi2:0): background thread "ubifs_bgt2_0" stops
Nov 17 09:57:55 kernel: ubi2: detaching mtd10
Nov 17 09:57:55 kernel: ubi2: mtd10 is detached

 

[RMerlin]

Nov 17 09:57:43 rc_service: httpd 1723:notify_rc reboot

Your router was issued a reboot command through the web interface.

 

[h1berto]

I did a hard reset on all 3...let's see how they "behave"...

 

[sgoldswo]

Looks like a new firmware is available via the GUI. Will be updating to it shortly.

Firmware version 3.0.0.4.386_45934
- Release Note -

Bug Fixes and Improvements:
1. Fixed Let's encrypt related bugs.
2. Fixed httpd vulnerability
3. Fixed stack overflow vulnerability
4. Fixed DoS vulnerability

Edit: Found this link under Windows XP 64-bit

https://dlcdnets.asus.com/pub/ASUS/wireless/ZenWiFi_XT8/FW_ZENWIFI_XT8_300438645934.zip

So my experience with this firmware was originally negative, based on an in place upgrade via the app. I experienced drop outs on the wireless backhaul. I reinstalled the firmware (downloaded from the ASUS support site) via the web GUI, and since then I haven’t had any problems. Didn’t do a reset this time.