› UKTH forums › ๐ Wireless Routers & Modems › ASUS & Wireless › ASUS ZenWiFi AX Whole Home Tri-Band Mesh WiFi 6 System Not sure if this is the right place to ask…. I am thinking of upgrading my Google Mesh wifi to the above.ย Has anyone used this and does it...
- This topic has 1,410 replies, 25 voices, and was last updated 2 months, 4 weeks ago by
UK Sentinel.
-
AuthorPosts
-
November 5, 2022 at 3:26 pm #21576
Most odd, only a suggestion, I would reboot AiMesh Primary and all Nodes and see if this happens again ? Hopefully just a blip Edit: I forgot to ask, how long was all the routers online before the issue occured ?
The uptime was around 23 hours when the wireless backhaul went down.
You need to login in order to vote
November 5, 2022 at 4:05 pm #21577The uptime was around 23 hours when the wireless backhaul went down.
23 hours was not long

In a completely sane world, madness is the only freedom (J.G.Ballard).
You need to login in order to vote
November 5, 2022 at 10:35 pm #21578Beta 9.0.0.4_388_21493 not improved things with me,
Since installing the 21493 beta this morning, most of us have been out, so should have been ticking over on a greatly reduced workload,
Not had time to ย put the TrendMicro services to the test, but I can confirm just clicking the web history tab locks the router gui up for me, httpd errors in the log.
โโโโโโโ-
(Nov 5 21:11:54 HTTPD: waitting 10 minitues and restart
Nov 5 21:11:54 rc_service: httpd 7550:notify_rc restart_httpd
Nov 5 21:11:54 ZenWiFi_XT8: start https:57020
Nov 5 21:11:54 ZenWiFi_XT8: start httpd:80
Nov 5 21:11:54 httpd: Save SSL certificate…57020
Nov 5 21:11:54 httpd: mssl_cert_key_match : PASS
Nov 5 21:11:54 httpd: Succeed to init SSL certificate…57020)โโโโโโ
internet access for all connected clients is A ok,
force closing the chrome tab & waiting 10 mins I regain router access again,
Iโm able to navigate the router gui without problem on all but the web history tab,
( web history has always been hit or miss for me, but normally I see errors after 1 or 2 days, when free ram drops below 80%)
Router has uptime of 10 Hrs & free ram down to 90%
With no full fat fibre here & a 70/20 line sync, I do rely on qos to keep everyone (swmbo) happy & web history to keep an eye on the kids now & then, soย everything under the Trend umbrella.
Iโll get to actually testing this beta fw out over the next few days, but not looking good so far.
Tomโฆ
You need to login in order to vote
November 6, 2022 at 7:39 am #21581Not had time to ย put the TrendMicro services to the test, but I can confirm just clicking the web history tab locks the router gui up for me, httpd errors in the log.
Thanks for the update, did you factory reset after applying this latest 9.0.0.4_388_21493 XT8 Beta.
If not then this may help or at least give us a clearer picture of the issues with this beta release ?
ASUS XT8 Hard Factory Reset
1. Turn the power off.
2.ย Press and hold theย “WPSย button”ย and turn the router on.
3. Power light isย onย (keep holding the WPS button).
4.ย Continue to press and hold theย WPS button.
You see the power LED ligh on(white) -> power LED light turn off -> power LED light flashing green color – power LED light turn off and then you can release the WPS button.
5. Reboot your router by manually pressingย the power button.In a completely sane world, madness is the only freedom (J.G.Ballard).
You need to login in order to vote
November 6, 2022 at 11:29 am #21583Just happened again, captured some logs around the time.ย This time the nodes did not fall back to 2.4GHz wireless backhaul and came back to 5GHz within a few minutes.ย Strange one……
Novย 6 11:13:51 wlceventd: wlceventd_proc_event(530): eth6: Auth xx:xx:xx:xx:xx:xx, status: Successful (0), rssi:-84
Novย 6 11:13:51 wlceventd: wlceventd_proc_event(559): eth6: Assoc xx:xx:xx:xx:xx:xx, status: Successful (0), rssi:-84
Novย 6 11:14:00 wlceventd: wlceventd_proc_event(530): eth6: Auth xx:xx:xx:xx:xx:xx, status: Successful (0), rssi:-84
Novย 6 11:14:00 wlceventd: wlceventd_proc_event(559): eth6: Assoc xx:xx:xx:xx:xx:xx, status: Successful (0), rssi:-84
Novย 6 11:14:00 kernel: Register interface [wds2.0.2]ย MAC: xx:xx:xx:xx:xx:xx
Novย 6 11:14:02 wlceventd: wlceventd_proc_event(530): eth6: Auth xx:xx:xx:xx:xx:xx, status: Successful (0), rssi:-82
Novย 6 11:14:02 wlceventd: wlceventd_proc_event(559): eth6: Assoc xx:xx:xx:xx:xx:xx, status: Successful (0), rssi:-82
Novย 6 11:14:02 kernel: Register interface [wds2.0.3]ย MAC: xx:xx:xx:xx:xx:xx
Novย 6 11:14:03 wlceventd: wlceventd_proc_event(530): eth4: Auth xx:xx:xx:xx:xx:xx, status: Successful (0), rssi:0
Novย 6 11:14:03 wlceventd: wlceventd_proc_event(494): eth4: Deauth_ind xx:xx:xx:xx:xx:xx, status: 0, reason: Unspecified reason (1), rssi:-68
Novย 6 11:14:03 wlceventd: wlceventd_proc_event(530): eth4: Auth xx:xx:xx:xx:xx:xx, status: Successful (0), rssi:-68
Novย 6 11:14:03 wlceventd: wlceventd_proc_event(494): eth4: Deauth_ind xx:xx:xx:xx:xx:xx, status: 0, reason: Unspecified reason (1), rssi:-68
Novย 6 11:14:03 wlceventd: wlceventd_proc_event(530): eth4: Auth xx:xx:xx:xx:xx:xx, status: Successful (0), rssi:-68
Novย 6 11:14:03 wlceventd: wlceventd_proc_event(559): eth4: Assoc xx:xx:xx:xx:xx:xx, status: Successful (0), rssi:-68
Novย 6 11:14:08 rc_service: cfg_server 1952:notify_rc update_sta_binding
Novย 6 11:14:08 wlceventd: wlceventd_proc_event(530): eth4: Auth xx:xx:xx:xx:xx:xx, status: Successful (0), rssi:0
Novย 6 11:14:08 wlceventd: wlceventd_proc_event(559): eth4: Assoc xx:xx:xx:xx:xx:xx, status: Successful (0), rssi:-63
Novย 6 11:14:13 rc_service: cfg_server 1952:notify_rc update_sta_binding
Novย 6 11:14:32 roamast: [EXAP]ignore static clients xx:xx:xx:xx:xx:xx
Novย 6 11:14:32 wlceventd: wlceventd_proc_event(494): wds2.0.3: Deauth_ind xx:xx:xx:xx:xx:xx, status: 0, reason: Previous authentication no longer valid (2), rssi:0
Novย 6 11:14:37 wlceventd: wlceventd_proc_event(511): wds0.0.1: Disassoc xx:xx:xx:xx:xx:xx, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Novย 6 11:14:37 kernel: Flushing net_device wds0.0.1.
Novย 6 11:14:37 wlceventd: wlceventd_proc_event(511): eth4: Disassoc xx:xx:xx:xx:xx:xx, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Novย 6 11:14:47 wlceventd: wlceventd_proc_event(511): wds2.0.2: Disassoc xx:xx:xx:xx:xx:xx, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Novย 6 11:14:47 wlceventd: wlceventd_proc_event(511): eth6: Disassoc xx:xx:xx:xx:xx:xx, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Novย 6 11:14:55 wlceventd: wlceventd_proc_event(511): wds0.0.2: Disassoc xx:xx:xx:xx:xx:xx, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Novย 6 11:14:55 kernel: Flushing net_device wds0.0.2.
Novย 6 11:14:55 wlceventd: wlceventd_proc_event(511): eth4: Disassoc xx:xx:xx:xx:xx:xx, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
You need to login in order to vote
November 6, 2022 at 11:31 am #21584Just happened again, captured some logs around the time.ย This time the nodes did not fall back to 2.4GHz wireless backhaul and came back to 5GHz within a few minutes.ย Strange oneโฆโฆ
Can you send feedback form and detail issues and mention ‘UK Sentinel’ in comments box, I can then speak to ASUS about it next week

Edit: just a thought, any iOS devices on your network ?
In a completely sane world, madness is the only freedom (J.G.Ballard).
You need to login in order to vote
November 6, 2022 at 11:33 am #21585I was just about to send, will mention you in the comments as suggested.
You need to login in order to vote
November 6, 2022 at 11:37 am #21587just a thought, any iOS devices on your network ?
In a completely sane world, madness is the only freedom (J.G.Ballard).
You need to login in order to vote
November 6, 2022 at 11:38 am #21588Edit: just a thought, any iOS devices on your network ?
No iOS devices are connected as they are forbidden in our house

You need to login in order to vote
November 6, 2022 at 12:29 pm #21589I thought issue could have been a private IP address issue, I will speak with ASUS and see what they think ๐
In a completely sane world, madness is the only freedom (J.G.Ballard).
You need to login in order to vote
November 6, 2022 at 12:34 pm #21590I thought issue could have been a private IP address issue, I will speak with ASUS and see what they think
Feedback sent.ย Reverted back to the offline beta 388.21099 you shared with me.ย I will be WFH next week and will need a stable connection.
You need to login in order to vote
November 6, 2022 at 12:36 pm #21591Running 9.0.0.4.388.21493 beta
Had some free time time this morning, so did a factory reset (gui followed by a hard rest) & then manually re-applied any custom configuration settings, followed by a system reboot.
System up with 110 free ram, web history is now available & working, but the AI protection / malicious site blocking is not.
The jffs files repopulated the web history from yesterdayโs usage & show web history failed just short of 4pm, roughly about 6Hrs up time, I didnโt save the log files from yesterday, but with a quick glance I didnโt notice anything obvious, but I didnโt have a narrow enough timeline to check in depth.
Currently free ram sitting at 104 MB with an uptime of 1Hr20,
Normally I would expect the free ram to fall over the next few dayโs & my web history to fail in some sort of way before I reach 72Hrs of uptime.
However as not all of the the TM systems appear to be enabled, Iโm not expecting the free ram to drop to low, but will see how that affects overall stability of the system & itโs sub systems over the next few dayโs.
Tomโฆ
You need to login in order to vote
November 6, 2022 at 1:25 pm #21593Noticed this morning that the mesh was back to 2.4GHz backhaul (even though I have turned off DFS channels on the backhaul and limited to 80MHz) and then the Internet stopped working (perhaps because I’d logged in?), and shortly after the connection went. No chance to see what had happened to the available RAM, but after a few minutes it restarted and now back to 131MB free.
I power cycled the mesh to get it to reconnect at 5GHz.
Why can’t Asus implement something in the code to try and reconnect to 5GHz without the need for a reboot? Optimising doesn’t do anything to fix it, and I don’t think it ever has.
The only things connected this morning to the mesh node is my son’s Xbox and some security cameras at the front of the house. That’s really not under any load, so it has to be the main router.
Edit: Having had issues for so long, but not wanting to schedule a reboot on the router (as it messes up connections to the USB drive) I have now put a smart plug on the mesh node and scheduled just the mesh to reboot once per day – around 5am – by turning it off for one minute.
You need to login in order to vote
November 6, 2022 at 2:08 pm #21597Noticed this morning that the mesh was back to 2.4GHz backhaul (even though I have turned off DFS channels on the backhaul and limited to 80MHz) and then the Internet stopped working (perhaps because Iโd logged in?), and shortly after the connection went. No chance to see what had happened to the available RAM, but after a few minutes it restarted and now back to 131MB free.
Anything in the logs around the time to suggest why the backhaul reverted back to 2.4GHz ?
In a completely sane world, madness is the only freedom (J.G.Ballard).
You need to login in order to vote
November 7, 2022 at 8:19 am #21607Feedback sent.ย Reverted back to the offline beta 388.21099 you shared with me.ย I will be WFH next week and will need a stable connection.
So ASUS have comeback after looking at your feedback log and have confirmed that with FW9.0.0.4_FW21493 you did have a wifi connection problem, but they cannot see any indication as to why in the logs etc.
ASUS ask if you had the same issue withย FW9.0.0.4_FW21101 beta firmware?
In a completely sane world, madness is the only freedom (J.G.Ballard).
You need to login in order to vote
-
AuthorPosts
- You must be logged in to reply to this topic.
