[dodgydrains]

TomThumb wrote:

UK Sentinel wrote:

Interesting regarding ‘HTTPD: waiting ‘ are any USB drives in use ?

No usb connected, never had the need, With the general release fw, web history seems populate correctly, then no new data entries after 1 or 2 day’s of uptime, but trying to access web history on the beta’s lock the gui up inside a similar timeframe. TM systems don’t seem to be 100% in the recent beta’s for me, but don’t know if that’s by design or omission. Tom…

Might be worth testing the offline 21099 beta that UK Sentinel shared with me?

You need to login in order to vote

[dodgydrains]

UK Sentinel wrote:

dodgydrains wrote:

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.

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?

I do not recall having this problem with beta 21101.  I can confirm that I did not have the problem with the offline beta 21099 you shared.

You need to login in order to vote

[dodgydrains]

UK Sentinel wrote:

I 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

[dodgydrains]

UK Sentinel wrote:

Edit: 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

[dodgydrains]

I was just about to send, will mention you in the comments as suggested.

Liked by:

You need to login in order to vote

[dodgydrains]

Just 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

[dodgydrains]

UK Sentinel wrote:

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

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

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?

 

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.

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.

Liked by:

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.

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

You need to login in order to vote

[dodgydrains]

For my use case, the online beta has been as stable as the offline beta that @UKSentinel shared with me.  Nearly 6 days uptime and free RAM is at 92MB.

Liked by:

You need to login in order to vote

[dodgydrains]

UK Sentinel wrote:

Did that include ‘Web & Apps Filters’ usage or just Time Scheduling’ ?

I only use ‘Time Scheduling’

Liked by:

You need to login in order to vote

[Author]

Posts