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

[UK Sentinel]

Great news, I did read simular on another forum – Version 9.0.0.4.388.21101 Beta release is proving to be more stable

Share the knowledge

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

You need to login in order to vote

[UK Sentinel]

So ASUS have released a BETA XT8 firmware that addresses some of the issues in 9.0.0.4.388_21101

​RT-AX95Q_9.0.0.4_388_21493-g12b5b2a_puresqubi.w.zip

Release note:

• Optimized memory usage and improved system stability.
• Fixed AiMesh web GUI issue.
• Fixed 2.5G port compatibility issues.
• Added a new web GUI login URL http://asusrouter.com
• Fixed AiProtection related issues in 9.0.0.4.388_21101

Note; Usual UKTH ASUS beta firmware Terms and Conditions apply see top of Forum, I have made this firmware release members only and any feedback on fixes would be appreciated.

RT-AX95Q_9.0.0.4_388_21493-g12b5b2a_puresqubi.w.zip (45 downloads )

Share the knowledge

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

Liked by:

You need to login in order to vote

[dodgydrains]

Any ideas what this means?  Uptime did not reset (showing as nearly 8 days) and the free RAM is now 130MB.

Nov 3 20:57:14 out of memory [1867]
Nov 3 20:57:14 out of memory [1867]
Nov 3 21:00:42 out of memory [1867]
Nov 3 21:02:36 out of memory [1867]
Nov 3 21:04:45 out of memory [1867]
Nov 3 21:05:43 out of memory [1867]
Nov 3 21:06:16 check_watchdog: [check_watchdog] restart watchdog for no heartbeat
Nov 3 21:06:16 rc_service: check_watchdog 1834:notify_rc restart_watchdog
Nov 3 21:07:16 check_watchdog: [check_watchdog] restart watchdog for no heartbeat
Nov 3 21:07:16 rc_service: check_watchdog 1834:notify_rc restart_watchdog
Nov 3 21:08:16 check_watchdog: [check_watchdog] restart watchdog for no heartbeat
Nov 3 21:08:16 rc_service: check_watchdog 1834:notify_rc restart_watchdog
Nov 3 21:09:16 check_watchdog: [check_watchdog] restart watchdog for no heartbeat
Nov 3 21:09:16 rc_service: check_watchdog 1834:notify_rc restart_watchdog
Nov 3 21:10:16 check_watchdog: [check_watchdog] restart watchdog for no heartbeat
Nov 3 21:10:16 rc_service: check_watchdog 1834:notify_rc restart_watchdog
Nov 3 21:11:16 check_watchdog: [check_watchdog] restart watchdog for no heartbeat
Nov 3 21:11:16 rc_service: check_watchdog 1834:notify_rc restart_watchdog
Nov 3 21:12:16 check_watchdog: [check_watchdog] restart watchdog for no heartbeat
Nov 3 21:12:16 rc_service: check_watchdog 1834:notify_rc restart_watchdog
Nov 3 21:13:16 check_watchdog: [check_watchdog] restart watchdog for no heartbeat
Nov 3 21:13:16 rc_service: check_watchdog 1834:notify_rc restart_watchdog
Nov 3 21:14:16 check_watchdog: [check_watchdog] restart watchdog for no heartbeat
Nov 3 21:14:16 rc_service: check_watchdog 1834:notify_rc restart_watchdog
Nov 3 21:15:16 check_watchdog: [check_watchdog] restart watchdog for no heartbeat
Nov 3 21:15:16 rc_service: check_watchdog 1834:notify_rc restart_watchdog
Nov 3 21:16:16 check_watchdog: [check_watchdog] restart watchdog for no heartbeat
Nov 3 21:16:16 rc_service: check_watchdog 1834:notify_rc restart_watchdog
Nov 3 21:17:16 check_watchdog: [check_watchdog] restart watchdog for no heartbeat
Nov 3 21:17:16 rc_service: check_watchdog 1834:notify_rc restart_watchdog
Nov 3 21:18:16 check_watchdog: [check_watchdog] restart watchdog for no heartbeat
Nov 3 21:18:16 rc_service: check_watchdog 1834:notify_rc restart_watchdog
Nov 3 21:19:16 check_watchdog: [check_watchdog] restart watchdog for no heartbeat
Nov 3 21:19:16 rc_service: check_watchdog 1834:notify_rc restart_watchdog
Nov 3 21:20:16 check_watchdog: [check_watchdog] restart watchdog for no heartbeat
Nov 3 21:20:16 rc_service: check_watchdog 1834:notify_rc restart_watchdog
Nov 3 21:21:16 check_watchdog: [check_watchdog] restart watchdog for no heartbeat
Nov 3 21:21:16 rc_service: check_watchdog 1834:notify_rc restart_watchdog

Share the knowledge

You need to login in order to vote

[dodgydrains]

UK Sentinel wrote:

So ASUS have released a BETA XT8 firmware that addresses some of the issues in 9.0.0.4.388_21101 ​RT-AX95Q_9.0.0.4_388_21493-g12b5b2a_puresqubi.w.zip Release note:

• Optimized memory usage and improved system stability.
• Fixed AiMesh web GUI issue.
• Fixed 2.5G port compatibility issues.
• Added a new web GUI login URL http://asusrouter.com
• Fixed AiProtection related issues in 9.0.0.4.388_21101

Note; Usual UKTH ASUS beta firmware Terms and Conditions apply see top of Forum, I have made this firmware release members only and any feedback on fixes would be appreciated. RT-AX95Q_9.0.0.4_388_21493-g12b5b2a_puresqubi.w.zip (3 downloads)

Thanks, hope you don’t mind me sharing this in another forum.  People there have also been complaining about 388.21101 stability issues.

Share the knowledge

You need to login in order to vote

[Jonathan Morris]

Installed the latest beta and now sitting with 161MB free. Let’s see how things pan out…

One thing to note is that my USB flash drive was red before, and failed the health scan. Drive appeared fine and it seems the error is RAM related. I’ve just noticed the flash drive is no longer red – and the health scan worked fine.

Share the knowledge

Liked by:

You need to login in order to vote

[dodgydrains]

Updated to the new offline beta 388.21493.  Free RAM is now showing as 200MB.

Share the knowledge

Liked by:

You need to login in order to vote

[UK Sentinel]

dodgydrains wrote:

Thanks, hope you don’t mind me sharing this in another forum.  People there have also been complaining about 388.21101 stability issues.

I have had comments from other forums members about these firmware’s, so please do check before sharing any such firmware’s, this is why it is a members only release.

Note: I just noticed this release on SNB, please do check in future before sharing 

Share the knowledge

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

Liked by:

You need to login in order to vote

[UK Sentinel]

Jonathan Morris wrote:

One thing to note is that my USB flash drive was red before, and failed the health scan. Drive appeared fine and it seems the error is RAM related. I’ve just noticed the flash drive is no longer red – and the health scan worked fine.

Sounds encouraging

Share the knowledge

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:

I have had comments from other forums members about these firmware’s, so please do check before sharing any such firmware’s, this is why it is a members only release. Note: I just noticed this release on SNB, please do check in future before sharing

I take your point and will not share next time, totally understand what you are saying.

Share the knowledge

Liked by:

You need to login in order to vote

[TomThumb]

Cheers UK Sentinel.

Just installed the .21493 beta,

need a couple of days uptime to see how the TrendMicro performs,

but at least it’s working in this release, so defo a step up from the 21101 beta👍

free ram gained, up from 81 > 100, so not a big a jump as dodgydrains,

anything lower than 80%  & router did seem to behave like a moody teenager😃

so fingers crossed there.

 

Tom…

Share the knowledge

Liked by:

You need to login in order to vote

[UK Sentinel]

TomThumb wrote:

so fingers crossed there.

This release does seem to have ironed out a few of the bigger issues when compared to 21101 beta etc.

Share the knowledge

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

You need to login in order to vote

[dodgydrains]

The nodes lost wireless backhaul at around 11am today on 388.21493. 3rd and 4th nodes (furthest away from main xt8 router) reconnected at 2.4GHz, possibly as they were far away from main xt8.  The closest node to the router needed a power cycle, after which 5Ghz-2 backhaul was re-established.

Is there anything I can check in the logs to see what happened?

 

Share the knowledge

You need to login in order to vote

[UK Sentinel]

dodgydrains wrote:

Is there anything I can check in the logs to see what happened?

Alas, you will have to look at the logs around the time the issue happened to see if there are any clues ?

Any indication of Free RAM before disconnect ?

Share the knowledge

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:

Alas, you will have to look at the logs around the time the issue happened to see if there are any clues ? Any indication of Free RAM before disconnect ?

Free RAM was the first thing I checked in the whole available logs.  No errors or messages regarding ‘RAM’.  Also checked anything on ‘RADAR’ in the  logs, couldn’t find anything either.

Share the knowledge

You need to login in order to vote

[UK Sentinel]

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 ?

Share the knowledge

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

You need to login in order to vote

[Author]

Posts