From: Johannes Berg <johannes@sipsolutions.net>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: "hostap@lists.shmoo.com" <hostap@lists.shmoo.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: deauthentication and disassociation nl80211 commands
Date: Sat, 10 Oct 2009 18:24:26 +0200 [thread overview]
Message-ID: <1255191866.4095.32.camel@johannes.local> (raw)
In-Reply-To: <1254708707.24430.68.camel@maxim-laptop>
[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]
On Mon, 2009-10-05 at 04:11 +0200, Maxim Levitsky wrote:
> My hacky patch that was rejected on the grounds that it is not right to
> introduce the driver dependent behavior might actually be the correct
> solution. It just makes the wpa_supplicant_disassociate do both
> disassociation and deauthentication, as was always assumed by the
> wpa_supplicant core.
Jouni just wanted to have what he felt was a workaround in
driver_nl80211.c rather than the core code.
> Or kernel should became smarter and do the work for wpa_supplicant.
I still disagree. Why should the kernel deauthenticate when userspace
disassociated.
On the other hand, I think Jouni's argument is that you should be able
to authenticate (force an auth frame exchange) even while authenticated.
I don't really disagree with that all that much, but I'm not sure how to
cleanly fit it in. mac80211 would have to reset the auth state without
sending a deauth.
johannes
(NB: I'm off to Japan on Monday. Sorry I've been slow with email, but
had lots of stuff to do and then planning the next trip, I hope it'll
improve once I return on the 22nd -- well after the weekend then)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-10-10 16:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 2:11 deauthentication and disassociation nl80211 commands Maxim Levitsky
2009-10-10 3:45 ` Maxim Levitsky
2009-10-10 16:04 ` John Klehm
2009-10-12 7:44 ` Holger Schurig
2009-10-10 16:24 ` Johannes Berg [this message]
2009-10-12 6:55 ` Jouni Malinen
2009-10-16 9:36 ` Johannes Berg
2009-10-12 6:52 ` Jouni Malinen
2009-10-15 11:45 ` Maxim Levitsky
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=1255191866.4095.32.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=hostap@lists.shmoo.com \
--cc=linux-wireless@vger.kernel.org \
--cc=maximlevitsky@gmail.com \
/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