ZenWiFi XT8 new firmware 3.0.0.4.386_25509

[Marc G.]

ZenWiFi XT8 new firmware 3.0.0.4.386_25509

I was hoping it would solve the disconnection of node after 10 minutes, but it doesn't.
I did a hard reset (WPS button + ON button), reinstalled from scratch, tried Node WiFi or hard wired, but still disconnect. Did hard reset and switched Node for router and router for Node, but still same situation....

Signed, desperate.

UPDATE
Everything seems to work fine for the past hour, no node disconnection.
The only change I did was unplug from the node my Netgear ethernet hub.

 

[TBONE204]

any idea what theses changes include?

i have been looking forward to some new firmware for some time.

 

[Marc G.]

any idea what theses changes include?

i have been looking forward to some new firmware for some time.

Unfortunately no, it was pushed as an auto update. On Asus web, it is not available yet.

 

[NetworkN00b]

ZenWiFi XT8 new firmware 3.0.0.4.386_25509

I was hoping it would solve the disconnection of node after 10 minutes, but it doesn't.
I did a hard reset (WPS button + ON button), reinstalled from scratch, tried Node WiFi or hard wired, but still disconnect. Did hard reset and switched Node for router and router for Node, but still same situation....

Signed, desperate.

Mark, what do you mean your node disconnects? Are you seeing this through the router web access page or the mobile app?

I ask because my nodes have been running smoothly with no disconnects for weeks.

 

[Marc G.]

Mark, what do you mean your node disconnects? Are you seeing this through the router web access page or the mobile app?

I ask because my nodes have been running smoothly with no disconnects for weeks.

Yes through the web page. and it starts blinking blue. I have also tried ethernet, changed it from auto to ethernet in the web page, and disconnects as well.

 

[SloPoke]

Yes through the web page. and it starts blinking blue. I have also tried ethernet, changed it from auto to ethernet in the web page, and disconnects as well.

My mesh node also disconnects, starts rapidly blinking blue, and won't come back online until it is power cycled. But this happens at random, after several days, or maybe a week of operation. Using ethernet backhaul. I also used to have the 160Mhz 5G-2 frequency when it was first installed, which disappeared after the first firmware update.

 

[NetworkN00b]

Yes through the web page. and it starts blinking blue. I have also tried ethernet, changed it from auto to ethernet in the web page, and disconnects as well.

Hmm,

My mesh node also disconnects, starts rapidly blinking blue, and won't come back online until it is power cycled. But this happens at random, after several days, or maybe a week of operation. Using ethernet backhaul. I also used to have the 160Mhz 5G-2 frequency when it was first installed, which disappeared after the first firmware update.

If you go through the web interface, they actually have note under Network Map. If you look on the upper right, you will see System Status. There you can click on the 5G-2 frequency tab and it explains that they have dedicated it to the wireless backhaul (which I don't use for most of my nodes) if you're using AIMesh. You can change that if you want, but you will see that the band is definitely using the 160MHz band, as part of its options.

My issue is that I can't disable the mesh because one of my nodes can't connect via wired backhaul so freeing that band for other uses is not an option.

 

[KINGER72]

ZenWiFi XT8 new firmware 3.0.0.4.386_25509

I was hoping it would solve the disconnection of node after 10 minutes, but it doesn't.
I did a hard reset (WPS button + ON button), reinstalled from scratch, tried Node WiFi or hard wired, but still disconnect. Did hard reset and switched Node for router and router for Node, but still same situation....

Signed, desperate.

Not sure if it’s related but I was having multiple Wi-fi connection issues with most devices (40+) around the house until I manually entered my ISPs DNS settings in the WAN section.

Using AiMesh on 25224 firmware. Have now upgraded to latest firmware today and all seems ok. Have also set DNS to auto as well.

 

[A1MB1G]

I just recently purchased the ZenWifi XT8 and also experiencing the same annoying disconnection problem with the Node. I have it setup for wired backhaul. I'm forced to power cycle every day sometimes twice a day for it to reconnect. I'm also noticing a bunch of these messages in the log files. Not sure where to go with this. Any ideas/suggestions?:

un 4 15:51:13 wlceventd: wlceventd_proc_event(461): eth4: Deauth_ind D0:735:3D:8B:E5, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jun 4 15:51:14 wlceventd: wlceventd_proc_event(478): eth4: Disassoc C8B:26:0C:C94, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jun 4 15:51:17 wlceventd: wlceventd_proc_event(478): eth4: Disassoc 00:05:CD:C6:46:3A, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jun 4 15:51:19 wlceventd: wlceventd_proc_event(478): eth4: Disassoc D0:735:3D:8B:E5, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jun 4 15:51:38 roamast: determine candidate node [D4:5D:64:8A:C4:20](rssi: -58dbm) for client [38:8B:59:21:AD:A1](rssi: -75dbm) to roam
Jun 4 15:51:38 roamast: eth4: disconnect weak signal strength station [38:8b:59:21:ad:a1]
Jun 4 15:51:38 roamast: eth4: remove client [38:8b:59:21:ad:a1] from monitor list
Jun 4 15:51:38 wlceventd: wlceventd_proc_event(461): eth4: Deauth_ind 38:8B:59:21:AD:A1, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jun 4 15:51:38 wlceventd: wlceventd_proc_event(478): eth4: Disassoc 38:8B:59:21:AD:A1, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jun 4 15:51:48 roamast: determine candidate node [D4:5D:64:8A:C4:20](rssi: -61dbm) for client [80:C5:F2:8F:095](rssi: -72dbm) to roam
Jun 4 15:51:48 roamast: eth4: disconnect weak signal strength station [80:c5:f2:8f:09:d5]
Jun 4 15:51:48 roamast: eth4: remove client [80:c5:f2:8f:09:d5] from monitor list
Jun 4 15:51:48 wlceventd: wlceventd_proc_event(461): eth4: Deauth_ind 80:C5:F2:8F:095, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jun 4 15:51:52 wlceventd: wlceventd_proc_event(478): eth4: Disassoc 80:C5:F2:8F:095, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jun 4 15:51:58 roamast: determine candidate node [D4:5D:64:8A:C4:20](rssi: -64dbm) for client [D0:735:3D:71:74](rssi: -76dbm) to roam
Jun 4 15:51:58 roamast: eth4: disconnect weak signal strength station [d0:73:d5:3d:71:74]
Jun 4 15:51:58 roamast: eth4: remove client [d0:73:d5:3d:71:74] from monitor list
Jun 4 15:51:58 wlceventd: wlceventd_proc_event(461): eth4: Deauth_ind D0:735:3D:71:74, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jun 4 15:52:04 wlceventd: wlceventd_proc_event(478): eth4: Disassoc D0:735:3D:71:74, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jun 4 15:52:52 wlceventd: wlceventd_proc_event(478): eth4: Disassoc 00:56:CD:C5:27:8D, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jun 4 15:52:52 wlceventd: wlceventd_proc_event(478): eth4: Disassoc 00:56:CD:C5:27:8D, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jun 4 15:52:53 roamast: eth4: disconnect weak signal strength station [00:56:cd:c5:27:8d]
Jun 4 15:52:53 roamast: eth4: remove client [00:56:cd:c5:27:8d] from monitor list

 

[A1MB1G]

Reset my router/nodes with latest firmware. Going to try running it with a wireless backhaul. I have a funny suspicion these disconnect issues are happening for those using an ethernet backhaul. Going to see how things go. Still getting a boat load of entries in the log similar to the ones above though.

 

[TBONE204]

here is the release notes:

ASUS ZenWiFi XT8 Firmware version 3.0.0.4.386.25509
- Improved connection stability.
- Fixed node 2.5G port connection issues.
- Adaptive QoS supported more apps
Work-From-Home: WeChat Work®, RescueAssist, Tencent/VooV Meeting® Learn-From-Home: LinkedIn Learning®, Binkist®, Skillshare®, edX®
Media Streaming: SiriusXM®, Bilibili®
Indoor training: The Sufferfest®, Bkool Fitness®, TrainerRoad®, Rouvy®

 

[NetworkN00b]

here is the release notes:

ASUS ZenWiFi XT8 Firmware version 3.0.0.4.386.25509
- Improved connection stability.
- Fixed node 2.5G port connection issues.
- Adaptive QoS supported more apps
Work-From-Home: WeChat Work®, RescueAssist, Tencent/VooV Meeting® Learn-From-Home: LinkedIn Learning®, Binkist®, Skillshare®, edX®
Media Streaming: SiriusXM®, Bilibili®
Indoor training: The Sufferfest®, Bkool Fitness®, TrainerRoad®, Rouvy®

That might be the worst set of firmware release notes I've ever seen. Considering that QoS was a major contributor to poor stability in the prior version, not mentioning that you've worked on it is ridiculous.

My network has been solid since upgrading, but the throughput has been subpar all around. I need to check to see if it is ISP related, but normally I can point the fingers back to the AX system.

 

[Lars]

Why cant there come fimware soon so we can get 160MHz channels on front-haul channels,now front-haul doesn't support 160MHz channels,im getting devices at home support 160Mhz,i still have ROG Rapture GT-AX11000,my devices is sometimes connected to main router,but not me xt8 doesnt support and i have 4 nodes zenWifi XT8

 

[samep]

My mesh node also disconnects, starts rapidly blinking blue, and won't come back online until it is power cycled. But this happens at random, after several days, or maybe a week of operation. Using ethernet backhaul. I also used to have the 160Mhz 5G-2 frequency when it was first installed, which disappeared after the first firmware update.

I'm curious about the nodes with Ethernet backhaul disconnecting. I had this issue day one with Ethernet backhaul.

When I reset, I found I needed to pair the 2 again close together. So I brought them close together but paired only after connecting the Ethernet from LAN of router node to WAN of extension node.

Hmm,

If you go through the web interface, they actually have note under Network Map. If you look on the upper right, you will see System Status. There you can click on the 5G-2 frequency tab and it explains that they have dedicated it to the wireless backhaul (which I don't use for most of my nodes) if you're using AIMesh. You can change that if you want, but you will see that the band is definitely using the 160MHz band, as part of its options.

My issue is that I can't disable the mesh because one of my nodes can't connect via wired backhaul so freeing that band for other uses is not an option.

Your nodes connected to backhaul are using the WAN for input port, right?

Sent from my Pixel 4 XL using Tapatalk

 

[mlai]

Just curious, for those who are experiencing node connection issues via Ethernet backhauls, what switches are you guys using?

 

[Dtangas]

I just recently purchased the ZenWifi XT8 and also experiencing the same annoying disconnection problem with the Node. I have it setup for wired backhaul. I'm forced to power cycle every day sometimes twice a day for it to reconnect. I'm also noticing a bunch of these messages in the log files. Not sure where to go with this. Any ideas/suggestions?:

un 4 15:51:13 wlceventd: wlceventd_proc_event(461): eth4: Deauth_ind D0:735:3D:8B:E5, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jun 4 15:51:14 wlceventd: wlceventd_proc_event(478): eth4: Disassoc C8B:26:0C:C94, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jun 4 15:51:17 wlceventd: wlceventd_proc_event(478): eth4: Disassoc 00:05:CD:C6:46:3A, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jun 4 15:51:19 wlceventd: wlceventd_proc_event(478): eth4: Disassoc D0:735:3D:8B:E5, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jun 4 15:51:38 roamast: determine candidate node [D4:5D:64:8A:C4:20](rssi: -58dbm) for client [38:8B:59:21:AD:A1](rssi: -75dbm) to roam
Jun 4 15:51:38 roamast: eth4: disconnect weak signal strength station [38:8b:59:21:ad:a1]
Jun 4 15:51:38 roamast: eth4: remove client [38:8b:59:21:ad:a1] from monitor list
Jun 4 15:51:38 wlceventd: wlceventd_proc_event(461): eth4: Deauth_ind 38:8B:59:21:AD:A1, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jun 4 15:51:38 wlceventd: wlceventd_proc_event(478): eth4: Disassoc 38:8B:59:21:AD:A1, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jun 4 15:51:48 roamast: determine candidate node [D4:5D:64:8A:C4:20](rssi: -61dbm) for client [80:C5:F2:8F:095](rssi: -72dbm) to roam
Jun 4 15:51:48 roamast: eth4: disconnect weak signal strength station [80:c5:f2:8f:09:d5]
Jun 4 15:51:48 roamast: eth4: remove client [80:c5:f2:8f:09:d5] from monitor list
Jun 4 15:51:48 wlceventd: wlceventd_proc_event(461): eth4: Deauth_ind 80:C5:F2:8F:095, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jun 4 15:51:52 wlceventd: wlceventd_proc_event(478): eth4: Disassoc 80:C5:F2:8F:095, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jun 4 15:51:58 roamast: determine candidate node [D4:5D:64:8A:C4:20](rssi: -64dbm) for client [D0:735:3D:71:74](rssi: -76dbm) to roam
Jun 4 15:51:58 roamast: eth4: disconnect weak signal strength station [d0:73:d5:3d:71:74]
Jun 4 15:51:58 roamast: eth4: remove client [d0:73:d5:3d:71:74] from monitor list
Jun 4 15:51:58 wlceventd: wlceventd_proc_event(461): eth4: Deauth_ind D0:735:3D:71:74, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jun 4 15:52:04 wlceventd: wlceventd_proc_event(478): eth4: Disassoc D0:735:3D:71:74, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jun 4 15:52:52 wlceventd: wlceventd_proc_event(478): eth4: Disassoc 00:56:CD:C5:27:8D, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jun 4 15:52:52 wlceventd: wlceventd_proc_event(478): eth4: Disassoc 00:56:CD:C5:27:8D, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jun 4 15:52:53 roamast: eth4: disconnect weak signal strength station [00:56:cd:c5:27:8d]
Jun 4 15:52:53 roamast: eth4: remove client [00:56:cd:c5:27:8d] from monitor list

I just bought the router about a month ago and had this exact issue. It would happen at midnight every single night and sometimes randomly throughout the day. I was on wired backhaul. This latest firmware update fixed that for me.

 

[A1MB1G]

Just curious, for those who are experiencing node connection issues via Ethernet backhauls, what switches are you guys using?

Not using any switches so that wasn’t the issue for me.

since the firmware update, the node hasn’t disconnected once. Fingers crossed they fixed the issue. Time will tell.

 

[TBONE204]

Not using any switches so that wasn’t the issue for me.

since the firmware update, the node hasn’t disconnected once. Fingers crossed they fixed the issue. Time will tell.

that must be the Node 2.5G WAN issues the release mentions. i had the issue as well. couldn't maintain a connection if I had it plugged in. i was using a switch at the time, I haven't tried since new firmware released but it sounds like many had that issue and for many it appears to be resolved now......so far anyways.

 

[RKG81]

Just curious, for those who are experiencing node connection issues via Ethernet backhauls, what switches are you guys using?

I use 3 tp-link switches on my network and all 4 of my nodes are on Ethernet backhaul. I’ve never had any issue whatsoever. Had this system for about a month now. Still no 160 option though

 

[dansalvato]

I'm not sure if it's caused by this last firmware update, but recently, once every 1-2 days, my router disconnects from the internet for about 30 seconds. There are no connection issues between the router and the nodes. But I get an abrupt connection loss, even to ethernet-connected devices, and the router LED turns red. About 30 seconds later, the connection returns to normal. There's nothing unusual in the log when this happens. Also, the LEDs on my modem don't change at all during this, so I'm pretty certain the router is at fault and not the modem or my ISP.