GT-AX6000 reset itself

I have a main gt-ax6000 and a mesh network using 4 RT-AX82U's.
This morning, the GT-AX6000 disconnected. When I looked to reconnect, both the 2.5 GHZ and 5 GHZ channels had disappeared and the only channel showing was the ASUS 38 default channel. I logged into that default SSID and all my settings were erased. I did a hard reset and manually put all my settings back in.

Has anyone else seen this behavior?

Nope, but I've only had mine for a few months.

It might've been an electrical surge, as it's the only thing I can think of that could cause something like that, unless someone reset the router.

TheLostSwede said:

Nope, but I've only had mine for a few months.

It might've been an electrical surge, as it's the only thing I can think of that could cause something like that, unless someone reset the router.

Click to expand...

I dont think it was a surge. I have it and a bunch of other equipment on a surge protector that didn't trip and non of the other equipment was affected.

In my experiments with Asus routers I had auto reset after reboot cases with RT-AC86U, RT-AX88U and RT-AX86U models. It usually happens after firmware update on the first reboot. I don't know what causes it. We had reports here on SNB Forums of auto reset happening after Asuswrt auto update. I remember folks with ZenWiFi XT8 and ZenWiFi XT12. So yes - it happens, it affects multiple models, but it's rare. Just restore or reconfigure your router and continue using it. Nothing else you can do.

Is it normal that the System Log says its been up for 4 days but its only keep a log for 1 day? I had log items yesterday that have now disappeared. If I recall, it was keeping a log for days or even weeks previously.

I did a factory reset last Weds

The retention is based on size, not duration. It’s usually 512K max (256K max per each syslog.log and syslog.log-1 file).

Ah! Size matters! I'm getting tons of these roamast messages like this:

Feb 5 06:51:34 roamast: sta[B6:50:8C:124:CC] on ap[FC:34:978:49:1C], rcpi is 94 and rssi is -63
Feb 5 06:51:34 roamast: sta[B6:50:8C:124:CC] on ap[58:11:22:28:67:3C], rcpi is 98 and rssi is -61
Feb 5 06:51:34 roamast: sta[B6:50:8C:124:CC] on ap[58:11:22:28:67:3C], rcpi is 98 and rssi is -61
Feb 5 06:51:34 miniupnpd[3450]: upnp_event_process_notify: connect(192.168.50.153:2869): Connection timed out
Feb 5 06:51:34 miniupnpd[3450]: upnpevents_processfds: 0x1d8ac48, remove subscriber uuid:3ddcd1d3-2380-45f5-b069-58112228dea6 after an ERROR cb: http://192.168.50.153:2869/upnp/eventing/jxrermostr
Feb 5 06:51:41 miniupnpd[3450]: upnp_event_process_notify: connect(192.168.50.153:2869): Connection timed out
Feb 5 06:51:41 miniupnpd[3450]: upnpevents_processfds: 0x1d86e10, remove subscriber uuid:3ddcd1d3-2380-45f5-b069-581122284d37 after an ERROR cb: http://192.168.50.153:2869/upnp/eventing/ryzvwcennw
Feb 5 06:51:59 miniupnpd[3450]: upnp_event_process_notify: connect(192.168.50.153:2869): Connection timed out
Feb 5 06:51:59 miniupnpd[3450]: upnp_event_process_notify: connect(192.168.50.153:2869): Connection timed out
Feb 5 06:51:59 miniupnpd[3450]: upnpevents_processfds: 0x1d8ac48, remove subscriber uuid:3ddcd1d3-2380-45f5-b069-58112228b53d after an ERROR cb: http://192.168.50.153:2869/upnp/eventing/xliumtiugq
Feb 5 06:56:39 roamast: sta[B6:50:8C:124:CC] on ap[7C:10:C9:7B:61:4C], rcpi is 78 and rssi is -71
Feb 5 06:56:39 roamast: sta[B6:50:8C:124:CC] on ap[7C:10:C9:7B:61:4C], rcpi is 78 and rssi is -71
Feb 5 06:56:39 roamast: sta[B6:50:8C:124:CC] on ap[FC:34:97:8F:77:4C], rcpi is 70 and rssi is -75
Feb 5 06:56:39 roamast: sta[B6:50:8C:124:CC] on ap[FC:34:97:8F:77:4C], rcpi is 70 and rssi is -75
Feb 5 06:56:39 roamast: sta[B6:50:8C:124:CC] on ap[7C:10:C9:7D:26:EC], rcpi is 50 and rssi is -85
Feb 5 06:56:39 roamast: sta[B6:50:8C:124:CC] on ap[7C:10:C9:7D:26:EC], rcpi is 50 and rssi is -85
Feb 5 06:56:39 roamast: sta[B6:50:8C:124:CC] on ap[58:11:22:28:67:3C], rcpi is 100 and rssi is -6

b 5 12:02:15 wlceventd: wlceventd_proc_event(662): eth7: Disassoc B6:50:8C:124:CC, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Feb 5 12:02:15 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind B6:50:8C:124:CC, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Feb 5 12:28:18 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind 44:6D:7F:06:1A3, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Feb 5 12:28:18 wlceventd: wlceventd_proc_event(662): eth7: Disassoc 44:6D:7F:06:1A3, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Feb 5 12:28:23 wlceventd: wlceventd_proc_event(685): eth7: Auth 44:6D:7F:06:1A3, status: Successful (0), rssi:0
Feb 5 12:28:23 wlceventd: wlceventd_proc_event(722): eth7: Assoc 44:6D:7F:06:1A3, status: Successful (0), rssi:-51
Feb 5 12:51:35 miniupnpd[3450]: upnp_event_process_notify: connect(192.168.50.153:2869): Connection timed out
Feb 5 12:51:35 miniupnpd[3450]: upnpevents_processfds: 0x1d86b38, remove subscriber uuid:3ddcd1d3-2380-45f5-b069-58112228d22c after an ERROR cb: http://192.168.50.153:2869/upnp/eventing/xbzjhyolvq
Feb 5 12:51:42 miniupnpd[3450]: upnp_event_process_notify: connect(192.168.50.153:2869): Connection timed out
Feb 5 12:51:42 miniupnpd[3450]: upnpevents_processfds: 0x1d86e10, remove subscriber uuid:3ddcd1d3-2380-45f5-b069-581122288d4a after an ERROR cb: http://192.168.50.153:2869/upnp/eventing/ctfaywhelb
Feb 5 12:52:56 miniupnpd[3450]: upnp_event_process_notify: connect(192.168.50.153:2869): Connection timed out
Feb 5 12:52:56 miniupnpd[3450]: upnp_event_process_notify: connect(192.168.50.153:2869): Connection timed out
Feb 5 12:52:56 miniupnpd[3450]: upnpevents_processfds: 0x1d86b38, remove subscriber uuid:3ddcd1d3-2380-45f5-b069-581122282d9b after an ERROR cb: http://192.168.50.153:2869/upnp/eventing/vmmevaxbor
Feb 5 14:19:33 kernel: CPU: 1 PID: 13418 Comm: httpd Tainted: P O 4.19.183 #1
Feb 5 14:19:33 kernel: Hardware name: GTAX6000_50991 (DT)
Feb 5 14:19:33 kernel: pstate: 600c0030 (nZCv q T32 LE aif)
Feb 5 14:19:33 kernel: pc : 00000000f70b1e10
Feb 5 14:19:33 kernel: lr : 0000000000081ae0
Feb 5 14:19:33 kernel: sp : 00000000ffeb6a60
Feb 5 14:19:33 kernel: x12: 00000000000d7630
Feb 5 14:19:33 kernel: x11: 0000000000a2e610 x10: 0000000000a1a448
Feb 5 14:19:33 kernel: x9 : 00000000ffeb6b04 x8 : 0000000000000000
Feb 5 14:19:33 kernel: x7 : 00000000ffeb6ad0 x6 : 00000000ffeb6abc
Feb 5 14:19:33 kernel: x5 : 00000000009e1190 x4 : 00000000ffeb6c92
Feb 5 14:19:33 kernel: x3 : 0000000000000000 x2 : 00000000ffeb6a9c
Feb 5 14:19:33 kernel: x1 : 00000000ffeb6c92 x0 : 0000000000000000
Feb 5 14:19:55 watchdog: restart httpd
Feb 5 14:19:55 rc_service: watchdog 3473:notify_rc stop_httpd
Feb 5 14:19:55 rc_service: watchdog 3473:notify_rc start_httpd
Feb 5 14:19:55 GT-AX6000: start httpd:80
Feb 5 14:19:55 httpd: Save SSL certificate...80
Feb 5 14:19:55 httpd: mssl_cert_key_match : PASS
Feb 5 14:19:55 httpd: Succeed to init SSL certificate...80
Feb 5 14:57:58 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind 44:6D:7F:06:1A3, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Feb 5 14:57:58 wlceventd: wlceventd_proc_event(662): eth7: Disassoc 44:6D:7F:06:1A3, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Feb 5 14:58:04 wlceventd: wlceventd_proc_event(685): eth7: Auth 44:6D:7F:06:1A3, status: Successful (0), rssi:0
Feb 5 14:58:04 wlceventd: wlceventd_proc_event(722): eth7: Assoc 44:6D:7F:06:1A3, status: Success

Michael James said:

I'm getting tons of these roamast messages like this:

Click to expand...

How far apart are your 5 APs?

OE

2 of my nodes are around 35 feet from main router. 2 others are around 20 feet. Main router is in the middle of the house. Wood house no metal or concrete walls in the way of the routers. "Connection Quality" = "Great" on all 4 as being reported from the Asus PC interface menu.

OzarkEdge said:

How far apart are your 5 APs?

Click to expand...

We actually discussed this at the end of 2022, but seems like @Michael James still decided to use all 5x routers in AiMesh configuration. This is a lot of Wi-Fi and all on the same channels and blasting at full power. AiMesh has no Tx power control on nodes. Hopefully they work in somewhat acceptable way.

Tech9 said:

We actually discussed this at the end of 2022, but seems like @Michael James still decided to use all 5x routers in AiMesh configuration. This is a lot of Wi-Fi and all on the same channels and blasting at full power. AiMesh has no Tx power control on nodes. Hopefully they work in somewhat acceptable way.

Click to expand...

I appreciate your memory! Yeah, my two APs cover a 3 level brick house, detached garage, and surrounding 2 acres.

OE

Michael James said:

2 of my nodes are around 35 feet from main router. 2 others are around 20 feet. Main router is in the middle of the house. Wood house no metal or concrete walls in the way of the routers. "Connection Quality" = "Great" on all 4 as being reported from the Asus PC interface menu.

Click to expand...

Too much WiFi, imo... your clients are roaming around in the middle of a giant point source of too much radio. Try spreading them out to about 40-60 feet apart and leave the extra nodes OFF.

OE

@Michael James has cameras plugged into the nodes. My suggestion back then was to convert some of the routers to Media Bridges. It is too much Wi-Fi indeed and the Great connection to the main router doesn't necessarily mean clients with great connection and roaming. The 20ft away nodes are way too close.

Yes indeed the issue is that at least 1 POE camera is connected to a mesh node. I did that because the antennas built into some of these cameras were too weak to consistently reach the main router. When you say "convert some of the routers to media bridges", I'm not sure how to do that. I normally just do a factory reset on a RT-AX82U and its sets it up as a mesh node automatically.

What is a POE camera with Wi-Fi connection? The most common PoE meaning is Power over Ethernet.

Tech9 said:

What is a POE camera with Wi-Fi connection? The most common PoE meaning is Power over Ethernet.

Click to expand...

Typical POE setup: RT-AX82U to ethernet cable. Ethernet cable into POE injector. POE injector out to camera.

1) Some of my cameras are not WIFI enabled. Those are large outdoor Dahua PTZ's. So those are POE into one of the 4 RT-AX82U mesh routers. (I dont have access to the main router to run ethernet cables directly to it or I would have done that. The main router is in the middle of the house. I would have to rip out walls to run new cables).
2) Some other of my cameras have WIFI and Ethernet connections both. But their WIFI side (the physical antenna) is weak so I'm using an ethernet into the RT-AX82U mesh. This allows me to use the 4 WIFI antennas in the RT-AX82U which boosts the signal. These are not POE

Also, should I turn off Roaming Assistant? ( in the "Professional" tab in the "Wireless" section )
I keep getting these long messages every day. Or are all these messages pointing to a problems with one of the RT-AX82U mesh AP's?