From: Jean-Pierre TOSONI <jp.tosoni@acksys.fr>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: mac80211+ath9k AP fails to honour power save mode from client
Date: Thu, 18 Jul 2019 14:52:05 +0000 [thread overview]
Message-ID: <AM4PR0101MB23055B57EF8BEBA8D478554CE4C80@AM4PR0101MB2305.eurprd01.prod.exchangelabs.com> (raw)
Hello list,
Context:
I am using one device in AP mode, the other in client mode.
The client uses wpa_supplicant to do *background scan to other channels that the data channel*.
I am running iperf (UDP) *from the AP* to the client.
My device is Cavium development board-based (Octeon III CPU), equipped with Compex WLE350NX.
It used to work correctly with kernel 3.18 and an old 2015 wireless backport.
Now I updated to kernel 4.9 and the wireless backport 4.19.32-1, the last one from the OpenWRT trunk. (previously I used backport-2017-11-01 with the same failure).
I am running wireshark with Airpcap to spy the wireless link.
Problem:
When the client scans offchannel, it correctly sends nullfunc frames around the offchannel period, with the PM bit set then unset.
However, during this time, the AP continues to send data to the client.
This results in a lot of lost frames, though I set the powersave buffers to high values on the AP side.
After some research I saw that the same kind of problem was fixed [1] and even re-fixed, but since there where so many changes in the queue management, I cannot really compare his work and the current state of the driver.
Any idea / patch / directions of research ?
J.P. Tosoni - ACKSYS
[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5519541d5a5f19893546883547e2f0f2e5934df7
next reply other threads:[~2019-07-18 14:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 14:52 Jean-Pierre TOSONI [this message]
2019-09-20 13:16 ` mac80211+ath9k AP fails to honour power save mode from client Kalle Valo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AM4PR0101MB23055B57EF8BEBA8D478554CE4C80@AM4PR0101MB2305.eurprd01.prod.exchangelabs.com \
--to=jp.tosoni@acksys.fr \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).