Stefan Sperling [s...@stsp.name] wrote:
>
> Sending BA req frames with the firmware node which represents the AP seems to
> fix the problem. I have not yet managed to trigger it again with this patch.
> My best explanation is that this allows the firmware to retry block ack
> requests properly,
On 3/16/21 2:38 PM, Stefan Sperling wrote:
> However, the second frame was sent at 24 Mbit/s, which
> indicates that the firmware could be retrying the BA request (frames sent
> at a different Tx rate than specified by the driver are generally retries).
My guess would be that a CRC fails causing
While testing my RA patches, I've seen iwn "hang" even though the AP and
iwn client were still exchanging packets at the wifi layer, but the upper
layers IP/UDP/TCP etc. were stuck. I could easily trigger this by running
tcpbench and moving towards the edge of the range of my AP.
Traffic would
