Just installed the update. Initial experiences are not good.
Within 15 minutes the router had marked my Internet as "offline" (this has been an ongoing problem with the prior firmware).
As well, even when the router "knew" it had an Internet connection, various clients, which were successfully connected to WiFi, claimed to have NO Internet connection. This still happens with this latest firmware update.
VERY disappointed with this router.
I did... not looking for "tier1-helpdesk-support-work-around" but a root cause fix / update from ASUSwow. did you just write and not read previous post? If you read, you may already solved it.
Oct 3 08:33:40 ubuntu systemd-resolved[1604]: Using degraded feature set (UDP) for DNS server 192.168.50.1.
Oct 3 08:34:11 ubuntu systemd-resolved[1604]: Using degraded feature set (TCP) for DNS server 192.168.50.1.
Oct 3 08:34:58 ubuntu systemd-resolved[1604]: Using degraded feature set (UDP) for DNS server 192.168.50.1.
Oct 3 08:00:08 SHARK-5F0DDCB-C check_watchdog: [check_watchdog] restart watchdog for no heartbeat
Oct 3 08:00:08 SHARK-5F0DDCB-C rc_service: check_watchdog 1346:notify_rc restart_watchdog
Oct 3 08:00:40 SHARK-5F0DDCB-C WAN Connection: Fail to connect with some issues.
Oct 3 08:00:48 SHARK-5F0DDCB-C WAN Connection: WAN was restored.
Oct 3 08:00:58 SHARK-5F0DDCB-C WAN Connection: Fail to connect with some issues.
Oct 3 08:01:06 SHARK-5F0DDCB-C WAN Connection: WAN was restored.
Oct 3 08:01:06 SHARK-5F0DDCB-C wanduck: Error locking /var/lock/resolv.lock: 28 No space left on device
Oct 3 08:01:06 SHARK-5F0DDCB-C wanduck: Error unlocking -1: 9 Bad file descriptor
Oct 3 08:01:08 SHARK-5F0DDCB-C check_watchdog: [check_watchdog] restart watchdog for no heartbeat
Oct 3 08:01:08 SHARK-5F0DDCB-C rc_service: check_watchdog 1346:notify_rc restart_watchdog
Oct 3 08:02:08 SHARK-5F0DDCB-C check_watchdog: [check_watchdog] restart watchdog for no heartbeat
Oct 3 08:02:08 SHARK-5F0DDCB-C rc_service: check_watchdog 1346:notify_rc restart_watchdog
Oct 3 08:03:08 SHARK-5F0DDCB-C check_watchdog: [check_watchdog] restart watchdog for no heartbeat
Oct 3 08:03:08 SHARK-5F0DDCB-C rc_service: check_watchdog 1346:notify_rc restart_watchdog
Oct 3 08:04:08 SHARK-5F0DDCB-C check_watchdog: [check_watchdog] restart watchdog for no heartbeat
Oct 3 08:04:08 SHARK-5F0DDCB-C rc_service: check_watchdog 1346:notify_rc restart_watchdog
Oct 3 08:05:08 SHARK-5F0DDCB-C check_watchdog: [check_watchdog] restart watchdog for no heartbeat
Oct 3 08:05:08 SHARK-5F0DDCB-C rc_service: check_watchdog 1346:notify_rc restart_watchdog
Oct 3 08:06:08 SHARK-5F0DDCB-C check_watchdog: [check_watchdog] restart watchdog for no heartbeat
Oct 3 08:06:08 SHARK-5F0DDCB-C rc_service: check_watchdog 1346:notify_rc restart_watchdog
Oct 3 08:07:08 SHARK-5F0DDCB-C check_watchdog: [check_watchdog] restart watchdog for no heartbeat
Oct 3 08:07:08 SHARK-5F0DDCB-C rc_service: check_watchdog 1346:notify_rc restart_watchdog
Oct 3 08:08:08 SHARK-5F0DDCB-C check_watchdog: [check_watchdog] restart watchdog for no heartbeat
Oct 3 08:08:08 SHARK-5F0DDCB-C rc_service: check_watchdog 1346:notify_rc restart_watchdog
Oct 3 08:09:08 SHARK-5F0DDCB-C check_watchdog: [check_watchdog] restart watchdog for no heartbeat
Oct 3 08:09:08 SHARK-5F0DDCB-C rc_service: check_watchdog 1346:notify_rc restart_watchdog
Oct 3 08:10:08 SHARK-5F0DDCB-C check_watchdog: [check_watchdog] restart watchdog for no heartbeat
Oct 3 08:10:08 SHARK-5F0DDCB-C rc_service: check_watchdog 1346:notify_rc restart_watchdog
Oct 3 08:11:08 SHARK-5F0DDCB-C check_watchdog: [check_watchdog] restart watchdog for no heartbeat
Oct 3 08:11:08 SHARK-5F0DDCB-C rc_service: check_watchdog 1346:notify_rc restart_watchdog
Oct 3 08:12:08 SHARK-5F0DDCB-C check_watchdog: [check_watchdog] restart watchdog for no heartbeat
Oct 3 08:12:08 SHARK-5F0DDCB-C rc_service: check_watchdog 1346:notify_rc restart_watchdog
Oct 3 08:13:08 SHARK-5F0DDCB-C check_watchdog: [check_watchdog] restart watchdog for no heartbeat
Oct 3 08:13:08 SHARK-5F0DDCB-C rc_service: check_watchdog 1346:notify_rc restart_watchdog
Oct 3 08:14:08 SHARK-5F0DDCB-C check_watchdog: [check_watchdog] restart watchdog for no heartbeat
Oct 3 08:14:08 SHARK-5F0DDCB-C rc_service: check_watchdog 1346:notify_rc restart_watchdog
Oct 3 08:14:52 ZenWiFi_XT8-5940-5F0DDCB-R kernel: eth0 (Int switch port: 1) (Logical Port: 1) (phyId: 1f) Link DOWN.
Oct 3 08:14:52 ZenWiFi_XT8-5940-5F0DDCB-R kernel: br0: port 10(eth0) entered disabled state
Oct 3 08:14:54 ZenWiFi_XT8-5940-5F0DDCB-R kernel: device dpsta entered promiscuous mode
Oct 3 08:14:54 ZenWiFi_XT8-5940-5F0DDCB-R kernel: br0: port 7(dpsta) entered forwarding state
Oct 3 08:14:54 ZenWiFi_XT8-5940-5F0DDCB-R kernel: br0: port 7(dpsta) entered forwarding state
Oct 3 08:14:54 ZenWiFi_XT8-5940-5F0DDCB-R BHC: Add dpsta to br0 successfully.
Oct 3 08:14:56 ZenWiFi_XT8-5940-5F0DDCB-R BHC: Topology change from 1 to 0.
Oct 3 08:14:56 ZenWiFi_XT8-5940-5F0DDCB-R BHC: Start AMAS Path Reselection!
Oct 3 08:15:01 ZenWiFi_XT8-5940-5F0DDCB-R kernel: eth0 (Int switch port: 1) (Logical Port: 1) (phyId: 1f) Link Up at 1000 mbps full duplex
Oct 3 08:15:01 ZenWiFi_XT8-5940-5F0DDCB-R kernel: br0: port 10(eth0) entered forwarding state
Oct 3 08:15:01 ZenWiFi_XT8-5940-5F0DDCB-R kernel: br0: port 10(eth0) entered forwarding state
Oct 3 08:15:02 ZenWiFi_XT8-5940-5F0DDCB-R kernel: device dpsta left promiscuous mode
Oct 3 08:15:02 ZenWiFi_XT8-5940-5F0DDCB-R kernel: br0: port 7(dpsta) entered disabled state
Oct 3 08:15:02 ZenWiFi_XT8-5940-5F0DDCB-R BHC: Add eth0 to br0 successfully.
Oct 3 08:15:04 ZenWiFi_XT8-5940-5F0DDCB-R BHC: Topology change from 0 to 1.
Oct 3 08:15:04 ZenWiFi_XT8-5940-5F0DDCB-R BHC: Start AMAS Path Reselection!
Oct 3 08:15:18 ZenWiFi_XT8-5940-5F0DDCB-R kernel: eth0 (Int switch port: 1) (Logical Port: 1) (phyId: 1f) Link DOWN.
Oct 3 08:15:18 ZenWiFi_XT8-5940-5F0DDCB-R kernel: br0: port 10(eth0) entered disabled state
Oct 3 08:15:20 ZenWiFi_XT8-5940-5F0DDCB-R kernel: device dpsta entered promiscuous mode
Oct 3 08:15:20 ZenWiFi_XT8-5940-5F0DDCB-R kernel: br0: port 7(dpsta) entered forwarding state
Oct 3 08:15:20 ZenWiFi_XT8-5940-5F0DDCB-R kernel: br0: port 7(dpsta) entered forwarding state
Oct 3 08:15:20 ZenWiFi_XT8-5940-5F0DDCB-R BHC: Add dpsta to br0 successfully.
Oct 3 08:15:22 ZenWiFi_XT8-5940-5F0DDCB-R BHC: Topology change from 1 to 0.
Oct 3 08:15:22 ZenWiFi_XT8-5940-5F0DDCB-R BHC: Start AMAS Path Reselection!
....
I just received my new ASUS ZenWiFi AX XT8 set from NewEgg (shoutout to NewEgg because I received them 24 hours after ordering!). I powered down the old XT8's with the dodgy firmware (3.0.0.4.386_25790) and installed the new XT8's which came factory installed with 3.0.0.4.386_25524. 30 minutes later I was up and running with client devices renamed complete with device icons, family members set up, 802.11ax delivering over 800mbps to my iPhone 11 Pro Max and everything working perfectly.
Needless to say the XT8's are now whining that there is a firmware update available. Let me put it this way, for so long as my heart is beating, I will never ever update to that useless 3.0.0.4.386_25790 code.
The old XT8's are being packed up and will be shipped back to ASUS for repair with a specific note that I want them back with 3.0.0.4.386_25524. As some member here made the excellent suggestion of having standby network equipment, the repaired routers will fulfill that role.
Never again am I going to mess with something that works just to be up-to-date.View attachment 26658
I would agree. For me 25790 has been much better than 25524. The one caveat is that I had lots of issues when I used the GUI to automatically do the upgrade. Only after I manually downloaded the FW upgrade file from the Asus website and used the GUI to manually update the router and node did it work correctly and become stable. Since then it has been rock solid. Only a reboot was required after I manually applied the FW update, no reset required.Very strange, for most on here the 25524 firmware was a complete disaster and the latest 25790 firmware is the best Asus has put out for the XT8. I’ve taken down and reinstalled every single firmware including the RC releases they’ve put out at least 20 times and it’s taken this long to get it working properly.
Has anyone found an open source firmware for the Asus XT8?
Something like : https://www.asuswrt-merlin.net/download - currently though the RT-AX95Q / XT8 is not yet supported.
XT8 CPU : Quadcore 1.5Ghz Broadcom BCM6755
I would contribute but need a tutorial for up a development environment: https://github.com/RMerl/asuswrt-merlin.ng
Since you have the XT8, are you having any problems with stability?There is no open source firmware for the XT8. I believe aimesh is locked down and no one has access to the code, Merlin has referred to it. XT8 is just now running pretty well with the latest Asus firmware.
There is no open source firmware for the XT8. I believe aimesh is locked down and no one has access to the code, Merlin has referred to it. XT8 is just now running pretty well with the latest Asus firmware.
There is no open source firmware for the XT8. I believe aimesh is locked down and no one has access to the code, Merlin has referred to it. XT8 is just now running pretty well with the latest Asus firmware.
Since you have the XT8, are you having any problems with stability?
Does anyone know if ASUS is trying to data mine DNS queries in the name of "security" for the monitoring "features"?
I am having stability issues ...
router becomes unresponsive after every 24 to 48 hours
- I have AiProtection and AiMesh enabled
- wired backhaul
- PPPoE WAN connection
- about 30 to 33 devices connected to the nodes at a given point in time
- AX Wi-fi 6 wireless standard enabled ( I may try disabling )
How many devices are you running ?
How on earth do you manage that? The app will look for the IP address 192.168.1.50, which is not a public IP address. Bizarre.Probably should start a new thread but ... I noticed that even though I have remote access disabled, that I can still access my router from the mobile app from outside my network. Is this by design? Can it be disabled?
What is the proper procedure to downgrade the firmware ?
Do I first apply the downgraded version to the router and then the node?
Or vice-versa?
Because this firmware version is a disaster stability wise.
I get 2 or 3 random reboots a day. And it seems to become worse every day.
NTP update doesn't work anymore since the firmware upgrade, so it constantly things the WAN is down. Despite being setup that it needs to do a ping to check the WAN connection.
Already shut them down and rebooted them, doesn't seem to fix anything.
The previous firmware was a lot more stable on my system.
So I want to put that one back.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!