Disconnected due to excessive missing ACKs on Ath10k (OpenWRT Chaos Chalmer RC2)

[Fernando S]

Same suggestion was posted on Openwrt forum (disable
disassoc_low_ack), I'll try it, do some stress test and come back with
results.

Here are two links to Openwrt forum threads related to this problem:

https://forum.openwrt.org/viewtopic.php?id=43188
https://forum.openwrt.org/viewtopic.php?pid=228738

And two tickets with some more information:

https://dev.openwrt.org/ticket/12372
https://dev.openwrt.org/ticket/15464


2015-07-15 4:09 GMT-03:00 Michal Kazior <michal.kazior at tieto.com>:
> On 14 July 2015 at 19:29, Fernando S <fsclavo at gmail.com> wrote:
>> I'm having dropouts on my TP-Link Archer C7, 2.4Ghz Wlan runs perfect,
>> but 5Ghz is unstable (my laptop and my Ipad 4 loss connection after a
>> couple of minutes, specially on heavy traffic).
>> Looking on router's log, I found:
>>
>> Thu Jul 9 20:51:32 2015 daemon.info hostapd: wlan0: STA
>> 01:02:03:04:05:06 IEEE 802.11: disconnected due to excessive missing
>> ACKs Thu Jul 9 20:52:02 2015 daemon.info hostapd: wlan0: STA
>> 01:02:03:04:05:06 IEEE 802.11: deauthenticated due to inactivity
>> (timer DEAUTH/REMOVE)
>
> Hmm.. This means there had to be a peer kickout event generated in
> firmware and your hostapd is configured to handle low-ack events as
> disassoc triggers.
>
> Ben recently raised a problem concerning ACK problems [1]. Perhaps
> that's one of the manifestations.
>
> You could just try disabling the `disassoc_low_ack` option in hostapd.
> Stations will still be disassociated when they go out of range and
> don't respond to NullFunc frames pings after a few minutes of idling
> (from AP point of view).
>
> [1]: http://lists.infradead.org/pipermail/ath10k/2015-July/005618.html
>
>
>> And on client side:
>>
>> Jul 9 20:51:05 laptop wpa_supplicant[1011]: wlan0:
>> CTRL-EVENT-DISCONNECTED bssid=30:30:30:30:30:30 reason=7 Jul 9
>> 20:51:05 laptop NetworkManager[861]: <warn> Connection disconnected
>> (reason 7)
>> A little search on Google show me some old bugs, apparently resolved
>> and only on ath9k (2.4Ghz): maybe the same issue is present on ath10k
>> (5Ghz)?
>>
>> Please let me know if I can help to debug this issue.
>
> Can you point to the ath9k thread/patches, please?
>
>
> Michał