Deco S4 performance drops from ~350Mbps to 22Mbps when experiencing an event recorded in System log.
Hi - having spent hours trying to figure out what was happening with the performance of my S4, I've narrowed it a single event that is repeatedly logged on my S4's system log:
Sun Jan 9 16:37:31 2022 daemon.info hostapd: ath1: STA 50:32:37:c8:db:40 IEEE 802.11: disassociated
Sun Jan 9 16:37:31 2022 daemon.err client_mgmt: wireless client associate or disassociate.
Sun Jan 9 16:37:31 2022 daemon.err client_mgmt: client_mac:50-32-37-C8-DB-40, client_ifname:ath1, client_action:disassociate
Sun Jan 9 16:37:31 2022 daemon.err client_mgmt: client(50-32-37-C8-DB-40) disassocaite by if(ath1).
Sun Jan 9 16:37:36 2022 daemon.info hostapd: ath1: STA 50:32:37:c8:db:40 IEEE 802.11: associated
Sun Jan 9 16:37:36 2022 daemon.info hostapd: ath1: STA 50:32:37:c8:db:40 RADIUS: starting accounting session 69E4FA6E2BA0EE09
Sun Jan 9 16:37:36 2022 daemon.info hostapd: ath1: STA 50:32:37:c8:db:40 WPA: pairwise key handshake completed (RSN)
Sun Jan 9 16:37:36 2022 daemon.notice nrd[5239]: wlanifBSteerEventsHandleNodeAssociatedInd: Node 50:32:37:C8:DB:40 associated on APId 255 ChanId 44 ESSId 0 , Capabilities: RRM , Max bandwidth: 2, Num of spatial streams: 2, PHY mode: 19, Max MCS: 9. Max TX power: 19
Sun Jan 9 16:37:36 2022 daemon.notice nrd[5239]: wlanifLinkEventsCmnGenerateDisassocEvent: Client 50:32:37:C8:DB:40 disassociated on APId 255 ChanId 44 ESSId 0
This event is happening very rapidly and is set at "Error" severity level. The S4 mesh on reboot works for a few hours and then is rendered to its knees by this 'errant' MAC address (50:32:37:c8:db:40) which is an Apple TV 4K connected to my local network via wired Ethernet. By resetting the Apple TV and re-establishing the wired connection, it appears that I've disabled the Apple TV WiFi connection and these error messages have stopped and my performance has remained steady at ~350Mbps but it concerns me that a single misbehaving client could have such an effect on my mesh. Equally concerning is that my only form of diagnosiing the problem is deep down in the bowels of a system log that is only really accessible from the web interface and not the application.
Any ideas on what this exchange is and why it kills my S4 mesh? TP-Link - if you're reading this, fix the 'disassocaite' typo in the err.msg.
p