I've been following the wifi roaming discussion on
and decided to try it at home.
I've got three TP-Link Archer C7. One is v2 used as router, two are v5 used as APs.
The experience has been less than great at first, so I filed the following bug against ath10k:
More details on my configuration are in the bug report.
However, since I switched to the non-ct version of ath10k+firmware stability is much better.
The problems I observed with the CT version on
SNAPSHOT r13710-7cb721c03f were
- devices have to reconnect when unlocking the screen, i.e. loosing wifi connectivity
- a lot of
daemon.info hostapd: wlan0: STA ea:46:3d:86:c5:e8 IEEE 802.11: disassociated due to inactivitymessages in the log
- single digit MByte/s when close to AP a while after reboot/wifi down/up
- DAWN fails with channel utilizations out of range (negative or way bigger than 255)
First of all: thank you very much, roaming really is an improvement.
There are some observations I'd like to share:
Besides occasional re-authentications (which I would not expect, because a minute earlier there was no re-authentication required when the same AP to AP transition was done) I see some errors in the log:
Tue Jul 21 09:25:50 2020 daemon.err dawn: Received NULL MAC! Client is strange!
Tue Jul 21 10:12:32 2020 daemon.err hostapd: nl80211: kernel reports: key addition failed
Tue Jul 21 12:26:29 2020 daemon.err dawn: not enough memory (3952970380 @ 104)
I didn't see the not enough memory messages with the CT version of ath10k, possibly because I used
kmod-ath10k-ct-smallbuffers. So it might be related to
@adrianschmutzler thanks for making me aware of that.
Is there a way I can assist debug?