TP-Link C7 v2 2,4GHz intermittent performance, unrealiable


#1

Hi guys,

I'm running 18.06.1 on a TP-Link Archer C7 v2. Its a very basic configuration where I use an identical SSID on 5 and 2,4GHz and it's basically just an AP. Everything else is handled by a potent Sophos Firewall.

My problem is, that every few days the 2,4GHz radio locks up. I only notice it when devices which only talk 2,4GHz all of a sudden aren't connected via WiFi anymore. All other devices just switch to 5GHz. A reboot fixes this until the 2,4 band locks up again.

Any ideas what could be done to remedy that?

Thanks in advance :slight_smile:


#2

Posting logs of "before, during, and after" would be helpful.

For many, including my five Archer C7 v2 units, they are very reliable and good wireless performers if not pushed hard for CPU or memory.


#3

Good hint, I just saved a system log "before". I'll try to catch logs "during" and "after".


#4

Ok, caught it. The 2,4 band (wlan1) stopped working today at 17:22:21h, here is the excerpt from the log:

Wed Jan  9 17:13:03 2019 daemon.notice hostapd: wlan1: AP-STA-POLL-OK 78:XX:39:XX:XX:ef
Wed Jan  9 17:15:50 2019 daemon.notice hostapd: wlan1: AP-STA-POLL-OK 00:XX:3a:XX:XX:06
Wed Jan  9 17:18:05 2019 daemon.notice hostapd: wlan1: AP-STA-POLL-OK 78:XX:39:XX:XX:ef
Wed Jan  9 17:21:09 2019 daemon.notice hostapd: wlan1: AP-STA-POLL-OK 00:XX:3a:XX:XX:06
Wed Jan  9 17:22:17 2019 daemon.info hostapd: wlan0: STA 08:XX:98:XX:XX:19 WPA: group key handshake completed (RSN)
Wed Jan  9 17:22:17 2019 daemon.info hostapd: wlan0: STA a4:XX:60:XX:XX:01 WPA: group key handshake completed (RSN)
Wed Jan  9 17:22:21 2019 daemon.info hostapd: wlan1: STA 78:XX:39:XX:XX:ef WPA: group key handshake failed (RSN) after 4 tries
Wed Jan  9 17:22:21 2019 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED 78:XX:39:XX:XX:ef
Wed Jan  9 17:22:21 2019 daemon.info hostapd: wlan1: STA 00:XX:3a:XX:XX:06 WPA: group key handshake failed (RSN) after 4 tries
Wed Jan  9 17:22:21 2019 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED 00:XX:3a:XX:XX:06
Wed Jan  9 17:22:26 2019 daemon.info hostapd: wlan1: STA 78:XX:39:XX:XX:ef IEEE 802.11: deauthenticated due to local deauth request
Wed Jan  9 17:22:26 2019 daemon.info hostapd: wlan1: STA 00:XX:3a:XX:XX:06 IEEE 802.11: deauthenticated due to local deauth request
Wed Jan  9 17:43:03 2019 daemon.notice hostapd: wlan0: STA 78:XX:39:XX:XX:ef IEEE 802.11: did not acknowledge authentication response
Wed Jan  9 17:48:06 2019 daemon.info hostapd: wlan0: STA 78:XX:39:XX:XX:ef IEEE 802.11: disassociated due to inactivity
Wed Jan  9 17:48:07 2019 daemon.info hostapd: wlan0: STA 78:XX:39:XX:XX:ef IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Wed Jan  9 17:50:11 2019 daemon.notice hostapd: wlan0: STA 78:XX:39:XX:XX:ef IEEE 802.11: did not acknowledge authentication response
Wed Jan  9 17:55:14 2019 daemon.info hostapd: wlan0: STA 78:XX:39:XX:XX:ef IEEE 802.11: disassociated due to inactivity
Wed Jan  9 17:55:15 2019 daemon.info hostapd: wlan0: STA 78:XX:39:XX:XX:ef IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Wed Jan  9 18:07:58 2019 daemon.info hostapd: wlan0: STA 3c:XX:ff:XX:XX:1a IEEE 802.11: authenticated
Wed Jan  9 18:07:58 2019 daemon.info hostapd: wlan0: STA 3c:XX:ff:XX:XX:1a IEEE 802.11: associated (aid 3)
Wed Jan  9 18:07:58 2019 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 3c:XX:ff:XX:XX:1a

After that part, no "wlan1" activity is recorded and the band had 0 associations. A reboot fixed it.


#5

Changing to a less congested channel (likely with less hidden stations) worked for me.


#6

I live in a pretty rural area so that's not an issue at all.