Weird ASUS log errors that happen when the connection drops and temp date change

torigrace — Wed, 08 Dec 2021 19:02:55 GMT

Hello,

Recently I bought an ASUS DSL-AX82U to replace my SH2 after repeated connection issues and drops for a couple years.

Connection has been much smoother since my switch but I noticed a few times there was a major connection drop and my router struggled to connect back to the internet for a little while. I checked the logs and there were some weird errors. Curious if anyone would know what they mean? Also I noticed on the logs that the date changes to May 5th every now and then on the log. Anyone else have that issue?

Here is an excerpt from the log when the connection dropped.

Dec 8 17:24:31 wlceventd: wlceventd_proc_event(508): eth6: Disassoc B0:70:2D:BA:79:91, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Dec 8 17:24:31 wlceventd: wlceventd_proc_event(508): eth6: Disassoc B0:70:2D:BA:79:91, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Dec 8 17:27:15 wlceventd: wlceventd_proc_event(527): eth6: Auth 1C:BF:CE:A0:E6:14, status: Successful (0), rssi:0
Dec 8 17:27:15 wlceventd: wlceventd_proc_event(556): eth6: Assoc 1C:BF:CE:A0:E6:14, status: Successful (0), rssi:-91
Dec 8 17:27:19 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 1C:BF:CE:A0:E6:14, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Dec 8 17:27:19 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 1C:BF:CE:A0:E6:14, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Dec 8 17:32:20 acsd: eth5: selected_chspec is 1006 (6)
Dec 8 17:32:20 acsd: eth5: Adjusted channel spec: 0x1006 (6)
Dec 8 17:32:20 acsd: eth5: selected channel spec: 0x1006 (6)
Dec 8 17:32:20 acsd: eth5: txop channel select: Performing CSA on chspec 0x1006
Dec 8 17:33:33 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 54:AE:27:45:64:43, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-64
Dec 8 17:33:33 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 54:AE:27:45:64:43, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-64
Dec 8 17:33:34 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 54:AE:27:45:64:43, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Dec 8 17:35:34 wlceventd: wlceventd_proc_event(527): eth6: Auth 54:AE:27:45:64:43, status: Successful (0), rssi:-57
Dec 8 17:35:34 wlceventd: wlceventd_proc_event(556): eth6: Assoc 54:AE:27:45:64:43, status: Successful (0), rssi:-58
Dec 8 17:42:46 wlceventd: wlceventd_proc_event(527): eth6: Auth 6C:E8:5C:45:FD:46, status: Successful (0), rssi:-83
Dec 8 17:42:46 wlceventd: wlceventd_proc_event(537): eth6: ReAssoc 6C:E8:5C:45:FD:46, status: Successful (0), rssi:-83
Dec 8 17:42:49 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 6C:E8:5C:45:FD:46, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Dec 8 17:42:49 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 6C:E8:5C:45:FD:46, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Dec 8 17:42:54 wlceventd: wlceventd_proc_event(527): eth6: Auth 6C:E8:5C:45:FD:46, status: Successful (0), rssi:0
Dec 8 17:42:54 wlceventd: wlceventd_proc_event(537): eth6: ReAssoc 6C:E8:5C:45:FD:46, status: Successful (0), rssi:-51
Dec 8 17:45:25 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 6C:E8:5C:45:FD:46, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Dec 8 17:45:25 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 6C:E8:5C:45:FD:46, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0

The change of date comes very early in the morning and an example of the code at the end is:

May 5 06:06:32 modprobe: module ip6t_REJECT not found in modules.dep
May 5 06:06:32 modprobe: module ip6t_ROUTE not found in modules.dep
May 5 06:06:32 modprobe: module ip6t_LOG not found in modules.dep
May 5 06:06:33 miniupnpd[1724]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
May 5 06:06:33 wan: finish adding multi routes
May 5 06:06:33 miniupnpd[1724]: shutting down MiniUPnPd
May 5 06:06:33 miniupnpd: it is advised to use network interface name instead of **IP address*

Re: Weird ASUS log errors that happen when the connection drops and temp date change

Stu_H — Thu, 09 Dec 2021 10:17:36 GMT

With Asus logs your best bet is to pop over to a forum called Smallnetbuilder where Merlin can be found who codes for Asus all be it on what he is able to use.

He may be able to tell you what the logs are about.

This topic

Weird ASUS log errors that happen when the connection drops and temp date change

Re: Weird ASUS log errors that happen when the connection drops and temp date change