A Follow Up To The Issues With Version 3.0.0.4.388.23285 Of The ASUS ZenWiFi XT8 Firmware

So I have been spending the last week working on trying to understand why the latest ASUS firmware for the ZenWifi XT8 is such a dumpster fire of a firmware. When I initially updated to it, it was so bad that I put out a PSA telling people not to upgrade to it. And to frank, even though I have things working now, that PSA will still stand because of a couple of reasons.

The first reason is that this firmware, which is version 3.0.0.4.388.23285, seems not to play nice with the advanced DMZ functionality of the Bell HH4000. Specifically the ASUS ZenWifi XT8 would get an external IP address from the HH4000, but the HH4000 would give the ZenWifi XT8 a self assigned address which looks like 169.xxx.xxx.xxx. If you see an address like this, it means that whatever device has this address will not be able to communicate with other devices on your local network or to the Internet properly, if at all. However on the previous version of the firmware which is 3.0.0.4.388.23012, I could not reproduce this issue. How I ultimately fixed this with the new firmware installed was to completely undo the advanced DMZ setup. Then reboot the HH4000. Followed by removing all the entries from the DHCP table in the HH4000. Rebooting again. Then redoing the advanced DMZ setup. Since no other ASUS firmware has required me to go through these gymnastics to make everything work after the firmware update, logic suggests that this is clearly a bug in the 3.0.0.4.388.23285 version of the ASUS firmware. Though to be fair to ASUS, this is likely a use case that they don’t test.

The second reason is that DNS resolution for reasons that I do not understand seems to be problematic. Before I get into why I say that, let me give you a quick lesson on DNS. When you go to a website, say http://www.itnerd.blog, your computer or smart phone has to ask a server called a Domain Name Server for the address of that website. And that server will respond with the exact address. Now that process should be milliseconds to do. But I was finding that it was taking 5 to 10 seconds for that to happen. Now I never use the DNS servers for any ISP that I do business with as ISPs have been known to track your activities and sell that information to third parties. Instead I normally use the Canadian Shield DNS service. But with this firmware, I could not do that. Instead, I had to use Quad 9 which is one of the list of pre-defined DNS services that are baked into ASUS routers. While I do get the same result which is to keep my browsing history private from my ISP, I question why I am no longer able to use Canadian Shield on my ZenWiFi XT8. I say that because as part of my troubleshooting I went back to the previous firmware which is 3.0.0.4.388.23012 and I was not able to reproduce this issue. That again implies that this firmware has an issue of some sort of issue with entering your own DNS settings.

One other thing that I should mention is that as another troubleshooting step, I factory reset the router and set it up from scratch rather than restoring the configuration from a backup. I did that because I thought that the backup might have been the issue. But as you can see above, that wasn’t the case.

The bottom line is this: While I do have things working at present with version 3.0.0.4.388.23285, I cannot recommend that any ASUS ZenWiFi XT8 user upgrade to this version. And this experience underlines the fact that ASUS really has issues with their firmware and their upgrade process that they really need to get sorted sooner rather than later. On top of issues like the ones above that managed to get out of their QA lab into the public domain, the fact I have to recommend that ASUS users reset their router config and redo it either via a backup file or from scratch when said user does a firmware upgrade makes zero sense. No other consumer or prosumer router works that way. And that reflects poorly on ASUS. This is why I have as of late been recommending Netgear and Linksys routers. With both of those brands, I am able to install them and forget about them so to speak. And ASUS needs to be in that camp or they will lose customers due to the fact that ease of setup and ease of use are thing that really matter to customers.

12 Responses to “A Follow Up To The Issues With Version 3.0.0.4.388.23285 Of The ASUS ZenWiFi XT8 Firmware”

  1. Any thoughts on this article here: https://www.bleepingcomputer.com/news/security/asus-urges-customers-to-patch-critical-router-vulnerabilities/ ? Asus is recommending the latest firmware for lots of routers (XT8 included) to patch some vulnerabilities. Would you recommend upgrading now, or waiting for the next one? Thanks.

  2. […] Take the XT8 that I own for example. The last firmware update was in May which I wrote about my experiences with that. Others like the RT-AX86U PRO has have firmware updates in the last day or two. That […]

  3. nergens last van gt-ax 11000 pro 2 x xt8 zen

  4. Have you tested the newest firmware 3.0.0.4.388_24609 released on 2024/01/26?

  5. Were you able to resolve the DNS delay?

    I’m having a similar issue with my Asus router; aDMZ is working, despite the Bell HH4000 showing the 169.1.1.1 as an IP address under “connected devices”, the WAN IP is shown under aDMZ and as my WAN IP on my router. I cannot get the IP to change from 169.1.1.1 despite your methods above and various other forum suggested fixes.

    I get the 5-10 second, sometimes up to 30 second delay every time a request is made to access a web page or server; at the same time the HH4000 interface locks up.

    When the HH4000 becomes responsive again, the internet kicks back in and works fine until the next request.

    Just manually installed the latest firmware hoping this was resolved – but no luck.

    • Cancel that; IP keeps bumping to 169.1.1.1 even in aDMZ. Can’t get it to stick, going to try Merlin Firmware and hopefully that catches the bug.

    • This isn’t a firmware issue. Dumb question, are you doing the following in this specific order:

      “Power off (pulling the power plug is your best option) both your router and the HH4000. Go find something to do for a couple of minutes. Then power both devices back up. First the router and then the HH4000 once the router is live. If all goes well, you should have a connection to the Internet.”

      This is from this article: https://itnerd.blog/2022/08/16/revisiting-how-to-bypass-bells-hh400-hardware-with-your-own-router/

      • Yes sir. More times than I can count. WAN IP holds for a while then reverts to 169.1.1.1.

        Then, web interface for the HH4000 hangs and internet freezes momentarily. When the interface comes back, internet resumes. Freezes every few minutes. Interface for the router does not hang, but shows “DHCP not configured properly” for network status. When HH4000 interface unfreezes, network status on router changes back to “connected”.

      • What you are describing is the router not dropping into the DMZ properly. Another dumb question, have you got “Automatic IP” turned on in the WAN section of the router?

      • Not dumb at all. I’m fairly amateur in networking, but good with the terminology.

        Yes WAN is set to automatic, DHCP set to “normal” (was on aggressive, which Asus states can cause issues with some equipment; I’ve also tried “continuous”).

        Had the same issue with my older asus router, just picked up a brand new one to take advantage of 2.5GB speeds.

        Side note: I had restored my backed up settings from the old router, but this weekend I’ll be installing Merlin and setting everything up manually to see if the restored settings had an issue. The last thing I can narrow it down to after that is an issue with the HH4000, which I’m only saying because the web interface freezes and hangs up the internet. Many hours troubleshooting with Bell, and they will swap the modem if I can’t get it resolved.

      • I don’t want to speak too soon, but the Merlin firmware and manually reconfiguration of my router (GT-AX6000) seems to have done the trick. DHCP mode set to continuous.

        WAN IP has held steady all morning, no drop outs, freezes, or HH4000 interface hang ups.

Leave a Reply to ASUS Issues Warning To Some Router Owners To Upgrade The Firmware Of Said Routers To The Latest Version | The IT NerdCancel reply

Discover more from The IT Nerd

Subscribe now to keep reading and get access to the full archive.

Continue reading