From: Johannes Berg <johannes@sipsolutions.net>
To: Holger Schurig <hs4233@mail.mn-solutions.de>
Cc: linux-wireless@vger.kernel.org
Subject: Re: cfg80211 question: impedance mismatch of .connect versus .assoc
Date: Wed, 14 Oct 2009 22:41:58 +0900 [thread overview]
Message-ID: <1255527718.4095.292.camel@johannes.local> (raw)
In-Reply-To: <200910141136.03288.hs4233@mail.mn-solutions.de>
[-- Attachment #1: Type: text/plain, Size: 982 bytes --]
On Wed, 2009-10-14 at 11:36 +0200, Holger Schurig wrote:
> While playing with .auth/.deauth/.assoc/.disassoc
> versus .connect/.disconnect in libertas, I notices two things
> that makes things a bit hard for me.
> This makes the "iw connect" command only work if an "iw scan" did
> just take place and I provide an BSS on the command line.
>
> So maybe net/wireless/sme.c should be generalized ?
>
>
>
> BSSID for .deauth/.disassoc vs. .disconnect
> -------------------------------------------
> Both the .deauth and .disassoc get the cfg80211_bss entry to
> deauth / disassociate against.
>
> .disconnect doesn't get this.
This was intentional, as with ->connect() the driver is supposed to
handle roaming/pre-connect scanning etc. Basically it's mostly for the
case of full-mac drivers that do that in the device firmware.
What you perceive as a "mismatch" is fully intentional, due to the
separation of where roaming is handled.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-10-14 13:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 9:36 cfg80211 question: impedance mismatch of .connect versus .assoc Holger Schurig
2009-10-14 13:41 ` Johannes Berg [this message]
2009-10-14 14:26 ` Holger Schurig
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=1255527718.4095.292.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=hs4233@mail.mn-solutions.de \
--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