From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>,
Shay Bar <Shay.Bar@celeno.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mac80211: Send deauth to STA's upon AP stop
Date: Thu, 18 Jun 2020 08:26:51 -0700 [thread overview]
Message-ID: <f0b038b4-fbd8-0b9b-2c2e-6337f0d408ea@candelatech.com> (raw)
In-Reply-To: <6da8757ac90a4d34ed1bdc7c84b40aac06c01af9.camel@sipsolutions.net>
On 06/18/2020 07:48 AM, Johannes Berg wrote:
> On Thu, 2020-06-18 at 14:45 +0000, Shay Bar wrote:
>>> So... why would you ever do that? :)
>>> johannes
>>
>> :)
>> Is it illegal to do "ifconfig <if> down" or kill hostapd
>> while STA's are still associated?
>> There are some vendors/users that are doing that.
>
> It's not really *illegal* per se, but it would be weird if both did it
> ... But I do tend to think that if you're using hostapd or such to
> control it, you shouldn't do another out-of-band control.
>
>> Regarding Ben's proposal of using 11k/v, I couldn’t find such
>> "going down" single frame in the standard (although sounds trivial)
>
> Broadcast deauth :)
Or use k/v to tell STA that AP is going down immediately and here is (null, likely)
list of APs to associate with instead?
Another thing I notice: In order to keep things from blocking for long periods (3+ seconds)
with rtnl held, I ended up doing a force flush in ath10k-ct, so at least when using that
driver, sending frames and then immediately doing flush will likely not put much on air.
I have hoped to one day add tx-completion call-backs handling to mac80211 instead of just calling a flush
for these types of station-down communication where flush is to be called shortly.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2020-06-18 15:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 9:36 [PATCH] mac80211: Send deauth to STA's upon AP stop Shay Bar
2020-06-18 13:47 ` Ben Greear
2020-06-18 13:48 ` Johannes Berg
2020-06-18 14:14 ` Shay Bar
2020-06-18 14:18 ` Johannes Berg
2020-06-18 14:36 ` Shay Bar
2020-06-18 14:38 ` Johannes Berg
2020-06-18 14:45 ` Shay Bar
2020-06-18 14:48 ` Johannes Berg
2020-06-18 15:11 ` Shay Bar
2020-06-18 15:26 ` Ben Greear [this message]
2020-06-21 10:12 ` Shay Bar
2020-06-25 9:51 ` Johannes Berg
2020-06-25 10:29 ` Shay Bar
2020-07-30 14:00 ` Johannes Berg
2020-07-30 14:23 ` Shay Bar
2020-07-30 14:28 ` Johannes Berg
2020-07-30 14:45 ` Shay Bar
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=f0b038b4-fbd8-0b9b-2c2e-6337f0d408ea@candelatech.com \
--to=greearb@candelatech.com \
--cc=Shay.Bar@celeno.com \
--cc=johannes@sipsolutions.net \
--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