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...

[Jonathan Morris]

UK Sentinel wrote:

Jonathan Morris wrote:

Weird that the latest update isn’t shown when you check via the router interface, but is via the Asus app!

Is your XT8 hardware version 1 ?

It has installed it, so I assume so!

You need to login in order to vote

[Nicky]

Well here goes nothing. Just upgraded to Firmware Version:3.0.0.4.388_21617. I took it’s time to settle down. 68 of the 72 devices shown in the list, but that’s not unusual, it can take a while for all devices to show on the list. Initial memory free was 82MB but after about 30 minutes it increased to 117/118MB.

So fingers crossed and let’s see how it fairs overnight?

The system setup is: 2x ZenWiFi (Firmware Version:3.0.0.4.388_21617) + 2x ZenWiFi Mini’s (Firmware Version 3.0.0.4.386_49599) with hardwire Backhaul to all nodes.

Liked by:

You need to login in order to vote

[dodgydrains]

UK Sentinel wrote:

@dodgydrains – ASUS have asked me if you would like to try another offline beta for the XT8 (not for sharing) ?

Happy to test.  Thanks.  What is different between the offline and the online 21617 available here?

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

 

Liked by:

You need to login in order to vote

[dodgydrains]

Jonathan Morris wrote:

Weird that the latest update isn’t shown when you check via the router interface, but is via the Asus app!

 

Same for me too, weird

You need to login in order to vote

[robgbc]

Jonathan Morris wrote:

Weird that the latest update isn’t shown when you check via the router interface, but is via the Asus app!

Same here (NA version 1)

9.0.0.4.388_21493 is still running smoothly for me, 140MB free, backhaul is at 385hrs connected and my TP-Link switches and plugs are at 384hrs

Going to hold off on updating for a bit to see how 3.0.0.4388_21617 plays out.

Liked by:

You need to login in order to vote

[UK Sentinel]

dodgydrains wrote:

Happy to test.  Thanks.  What is different between the offline and the online 21617 available here?

After I spoke with ASUS, the new Offline seems pointless, (older revision number and less improvements) and ASUS agreed

In a completely sane world, madness is the only freedom (J.G.Ballard).

You need to login in order to vote

[UK Sentinel]

Nicky wrote:

So fingers crossed and let’s see how it fairs overnight?

In a completely sane world, madness is the only freedom (J.G.Ballard).

You need to login in order to vote

[dodgydrains]

robgbc wrote:

Jonathan Morris wrote:

Weird that the latest update isn’t shown when you check via the router interface, but is via the Asus app!

Same here (NA version 1) 9.0.0.4.388_21493 is still running smoothly for me, 140MB free, backhaul is at 385hrs connected and my TP-Link switches and plugs are at 384hrs Going to hold off on updating for a bit to see how 3.0.0.4388_21617 plays out.

Is your setup with 2 or 4 XT8’s?  It seems that there are more issues on 21493 with 4 x XT8’s.

You need to login in order to vote

[Nicky]

Well, it’s been up for 10 hours (overnight) with no issues. All 72 devices are now listed and the RAM appears to have stabilised at 99MB.

Let’s see how the day goes.

 

The system setup is: 2x ZenWiFi (Firmware Version:3.0.0.4.388_21617) + 2x ZenWiFi Mini’s (Firmware Version 3.0.0.4.386_49599) with hardwire Backhaul to all nodes.

Liked by:

You need to login in order to vote

[Nicky]

Well it’s been 24 hours and all seams stable. The system has been under fairly heavy load today, with around 90GB of internet traffic plus around 350GB of internal traffic. The Router’s RAM has dropped to 80MB and no devices have been noticed to have lost connection.

That said, the system log does repeatedly show that 2 devices were disconnected because the sending station was leaving or had left but was then immediately reconnected.

The system setup is: 2x ZenWiFi XT8 (1x main router, 1x node) Firmware Version:3.0.0.4.388_21617 + 2x ZenWiFi Mini AX1800 (2x nodes) Firmware Version 3.0.0.4.386_49599 with hardwire Backhaul to all nodes.

You need to login in order to vote

[robgbc]

dodgydrains wrote:

robgbc wrote:

Jonathan Morris wrote:

Weird that the latest update isn’t shown when you check via the router interface, but is via the Asus app!

Same here (NA version 1) 9.0.0.4.388_21493 is still running smoothly for me, 140MB free, backhaul is at 385hrs connected and my TP-Link switches and plugs are at 384hrs Going to hold off on updating for a bit to see how 3.0.0.4388_21617 plays out.

Is your setup with 2 or 4 XT8’s? It seems that there are more issues on 21493 with 4 x XT8’s.

2 XT8s

3.0.0.4388_21617 is still not available via router gui, although it is via the app. Downloaded from Asus XT8 site and currently updating.

Liked by:

You need to login in order to vote

[UK Sentinel]

Nicky wrote:

The system setup is: 2x ZenWiFi (Firmware Version:3.0.0.4.388_21617) + 2x ZenWiFi Mini’s (Firmware Version 3.0.0.4.386_49599) with hardwire Backhaul to all nodes.

As you are (I believe) wired backhaul to all nodes, if that includes one of the XT8 as an AiMesh node, then you are going to not experience backhaul dropouts as others who are using wireless backhaul.

But still good to hear how wired (Ethernet) backhaul is working for Aimesh and your input is always appreciated as I am sure you know 

In a completely sane world, madness is the only freedom (J.G.Ballard).

You need to login in order to vote

[dodgydrains]

After exactly 1 day and 8 hours the wireless backhaul went down and then recovered.  These are the logs for the time it happened, not sure if it shows anything, should I send feedback?

 

Nov 23 07:58:33 wlceventd: wlceventd_proc_event(530): eth5: Auth AA:45:C4:F8:E3:8A, status: Successful (0), rssi:-63

Nov 23 07:58:33 wlceventd: wlceventd_proc_event(540): eth5: ReAssoc AA:45:C4:F8:E3:8A, status: Successful (0), rssi:-63

Nov 23 07:58:39 roamast: [EXAP]Deauth old sta in 1 0: AA:45:C4:F8:E3:8A

Nov 23 07:58:39 roamast: eth5: disconnect weak signal strength station [aa:45:c4:f8:e3:8a]

Nov 23 07:58:39 roamast: eth5: remove client [aa:45:c4:f8:e3:8a] from monitor list

Nov 23 07:58:43 wlceventd: wlceventd_proc_event(494): eth5: Deauth_ind AA:45:C4:F8:E3:8A, status: 0, reason: Previous authentication no longer valid (2), rssi:-79

Nov 23 07:58:43 wlceventd: wlceventd_proc_event(494): eth5: Deauth_ind AA:45:C4:F8:E3:8A, status: 0, reason: Disassociated due to inactivity (4), rssi:-79

Nov 23 07:58:43 wlceventd: wlceventd_proc_event(494): eth5: Deauth_ind AA:45:C4:F8:E3:8A, status: 0, reason: Previous authentication no longer valid (2), rssi:-79

Nov 23 07:58:44 wlceventd: wlceventd_proc_event(511): eth5: Disassoc AA:45:C4:F8:E3:8A, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0

Nov 23 08:05:14 wlceventd: wlceventd_proc_event(530): eth6: Auth FC:34:97:9A:C8:48, status: Successful (0), rssi:-84

Nov 23 08:05:14 wlceventd: wlceventd_proc_event(559): eth6: Assoc FC:34:97:9A:C8:48, status: Successful (0), rssi:-84

Nov 23 08:05:14 kernel: Register interface [wds2.0.1]  MAC: fc:34:97:9b:0b:08

Nov 23 08:05:28 wlceventd: wlceventd_proc_event(530): eth4: Auth FC:34:97:9A:C8:41, status: Successful (0), rssi:0

Nov 23 08:05:28 wlceventd: wlceventd_proc_event(559): eth4: Assoc FC:34:97:9A:C8:41, status: Successful (0), rssi:-69

Nov 23 08:05:45 wlceventd: wlceventd_proc_event(511): wds2.0.1: Disassoc FC:34:97:9A:C8:48, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0

Nov 23 08:05:45 wlceventd: wlceventd_proc_event(511): eth6: Disassoc FC:34:97:9A:C8:48, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0

Nov 23 08:05:57 wlceventd: wlceventd_proc_event(511): wds0.0.1: Disassoc FC:34:97:9A:C8:41, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0

Nov 23 08:05:57 kernel: Flushing net_device wds0.0.1.

Nov 23 08:05:57 wlceventd: wlceventd_proc_event(511): eth4: Disassoc FC:34:97:9A:C8:41, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0

You need to login in order to vote

[UK Sentinel]

Can you send feedback this morning if possible and in comments box and detail UK Sentinel and time of issue,  then let me know, as then I will let ASUS know?

As you say, with four nodes, this is interesting (I think you are four nodes) ?

 

In a completely sane world, madness is the only freedom (J.G.Ballard).

You need to login in order to vote

[dodgydrains]

UK Sentinel wrote:

Can you send feedback this morning if possible and in comments box and detail UK Sentinel and time of issue, then let me know, as then I will let ASUS know? As you say, with four nodes, this is interesting (I think you are four nodes) ?

Feedback sent, the wireless backhaul went down again and recovered.   I mentioned you in the comments.  The uptime did not reset.

Yes, my setup is 4 XT8’s and wireless backhaul.  With the beta 21101 (I think the one you shared) didn’t get any problems for 6+ days.

 

You need to login in order to vote

[Author]

Posts