Multiple Kernel log messages

[MatynK]

I am running an RT-AX88U as a main router with a RT-AX3000 as an AiMesh Node using a wired backhaul.

I am continually seeing the following in my log files:

Aug 2 09:06:19 roamast: [EXAP]Deauth old sta in 1 0: AE:B8:0D:CC:4B:0E
Aug 2 09:06:19 roamast: eth7: disconnect weak signal strength station [ae:b8:0d:cc:4b:0e]
Aug 2 09:06:19 kernel: CPU: 3 PID: 15445 Comm: roamast Tainted: P O 4.1.51 #4
Aug 2 09:06:19 kernel: Hardware name: Broadcom-v8A (DT)
Aug 2 09:06:19 kernel: task: ffffffc03ebbea80 ti: ffffffc02ec08000 task.ti: ffffffc02ec08000
Aug 2 09:06:19 kernel: PC is at 0xf676372e
Aug 2 09:06:19 kernel: LR is at 0xf672f858
Aug 2 09:06:19 kernel: pc : [<00000000f676372e>] lr : [<00000000f672f858>] pstate: 20000030
Aug 2 09:06:19 kernel: sp : 00000000f66ebcb0
Aug 2 09:06:19 kernel: x12: 00000000ffffffff
Aug 2 09:06:19 kernel: x11: 00000000f66ec1ac x10: 0000000000000000
Aug 2 09:06:19 kernel: x9 : 00000000f68297a8 x8 : 00000000f682b000
Aug 2 09:06:19 kernel: x7 : 00000000f66ed920 x6 : 0000000000000021
Aug 2 09:06:19 kernel: x5 : 00000000001c68ee x4 : 0000000000000006
Aug 2 09:06:19 kernel: x3 : 0000000000000000 x2 : 0000000000000001
Aug 2 09:06:19 kernel: x1 : 00000000000000a8 x0 : 00000000000000ae
Aug 2 09:06:41 roamast: ROAMING Start...

These are normally surrounded by heaps of the following type of messages:

Aug 2 12:24:05 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind C8:69:CD:6B:BB:96, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-49
Aug 2 12:24:05 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind C8:69:CD:6B:BB:96, status: 0, reason: Previous authentication no longer valid (2), rssi:-49
Aug 2 12:24:06 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind C8:69:CD:6B:BB:96, status: 0, reason: Station requesting (re)association is not authenticated with responding station (9), rssi:0
Aug 2 12:24:06 wlceventd: wlceventd_proc_event(511): eth7: Disassoc C8:69:CD:6B:BB:96, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Aug 2 12:24:13 wlceventd: wlceventd_proc_event(530): eth7: Auth C8:69:CD:6B:BB:96, status: Successful (0), rssi:0
Aug 2 12:24:13 wlceventd: wlceventd_proc_event(559): eth7: Assoc C8:69:CD:6B:BB:96, status: Successful (0), rssi:-49
Aug 2 12:24:17 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind C8:69:CD:6B:BB:96, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-49
Aug 2 12:24:18 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind C8:69:CD:6B:BB:96, status: 0, reason: Previous authentication no longer valid (2), rssi:-49
Aug 2 12:24:18 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind C8:69:CD:6B:BB:96, status: 0, reason: Station requesting (re)association is not authenticated with responding station (9), rssi:0

When this happens a number of devices will drop off the network and have to reconnect.

Anyone with any ideas ?

 

[Olndo Pindaro]

Same erroro in RT-AX86S

 

[bbunge]

I am running an RT-AX88U as a main router with a RT-AX3000 as an AiMesh Node using a wired backhaul.

I am continually seeing the following in my log files:

Aug 2 09:06:19 roamast: [EXAP]Deauth old sta in 1 0: AE:B8:0D:CC:4B:0E
Aug 2 09:06:19 roamast: eth7: disconnect weak signal strength station [ae:b8:0d:cc:4b:0e]
Aug 2 09:06:19 kernel: CPU: 3 PID: 15445 Comm: roamast Tainted: P O 4.1.51 #4
Aug 2 09:06:19 kernel: Hardware name: Broadcom-v8A (DT)
Aug 2 09:06:19 kernel: task: ffffffc03ebbea80 ti: ffffffc02ec08000 task.ti: ffffffc02ec08000
Aug 2 09:06:19 kernel: PC is at 0xf676372e
Aug 2 09:06:19 kernel: LR is at 0xf672f858
Aug 2 09:06:19 kernel: pc : [<00000000f676372e>] lr : [<00000000f672f858>] pstate: 20000030
Aug 2 09:06:19 kernel: sp : 00000000f66ebcb0
Aug 2 09:06:19 kernel: x12: 00000000ffffffff
Aug 2 09:06:19 kernel: x11: 00000000f66ec1ac x10: 0000000000000000
Aug 2 09:06:19 kernel: x9 : 00000000f68297a8 x8 : 00000000f682b000
Aug 2 09:06:19 kernel: x7 : 00000000f66ed920 x6 : 0000000000000021
Aug 2 09:06:19 kernel: x5 : 00000000001c68ee x4 : 0000000000000006
Aug 2 09:06:19 kernel: x3 : 0000000000000000 x2 : 0000000000000001
Aug 2 09:06:19 kernel: x1 : 00000000000000a8 x0 : 00000000000000ae
Aug 2 09:06:41 roamast: ROAMING Start...

These are normally surrounded by heaps of the following type of messages:

Aug 2 12:24:05 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind C8:69:CD:6B:BB:96, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-49
Aug 2 12:24:05 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind C8:69:CD:6B:BB:96, status: 0, reason: Previous authentication no longer valid (2), rssi:-49
Aug 2 12:24:06 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind C8:69:CD:6B:BB:96, status: 0, reason: Station requesting (re)association is not authenticated with responding station (9), rssi:0
Aug 2 12:24:06 wlceventd: wlceventd_proc_event(511): eth7: Disassoc C8:69:CD:6B:BB:96, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Aug 2 12:24:13 wlceventd: wlceventd_proc_event(530): eth7: Auth C8:69:CD:6B:BB:96, status: Successful (0), rssi:0
Aug 2 12:24:13 wlceventd: wlceventd_proc_event(559): eth7: Assoc C8:69:CD:6B:BB:96, status: Successful (0), rssi:-49
Aug 2 12:24:17 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind C8:69:CD:6B:BB:96, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-49
Aug 2 12:24:18 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind C8:69:CD:6B:BB:96, status: 0, reason: Previous authentication no longer valid (2), rssi:-49
Aug 2 12:24:18 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind C8:69:CD:6B:BB:96, status: 0, reason: Station requesting (re)association is not authenticated with responding station (9), rssi:0

When this happens a number of devices will drop off the network and have to reconnect.

Anyone with any ideas ?

Yes.
If the system is working well stop looking around the log!

Are the clients really loosing connection or is it a wacky network map? The network map is seldom 100 % correct in my system.