From: Johannes Berg <johannes@sipsolutions.net>
To: Dhiraj Gaurh <dhiraj.gaurh@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: cfg80211 support for pre-auth
Date: Sat, 14 Aug 2010 14:18:31 +0200 [thread overview]
Message-ID: <1281788311.3984.1.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <AANLkTin1=7JDXSJgTQ-L-9-r18VJY1fUVLPY+cPup8Pn@mail.gmail.com>
Hi,
On Fri, 2010-08-13 at 20:10 +0530, Dhiraj Gaurh wrote:
> Hello folks,
> PMK caching and pre-auth are not currently supported by
> cfg80211/nl80211/supplicant. Actually the former is only not supported
> by wpa_supplicant. I have fixed that and will be moving the code
> upstream shortly.
Sounds good.
> BUT the latter is not even supported by cfg/nl. Anybody working on
> that ? Actually support is not even there for using wext in this
> scenario. So you just fail certification if you use cfg/nl. I need to
> change this scenario.
> Currently thinking if it is better to add support in cfg/nl/supplicant
> or just use wext stuff and a patch.
> I need an API in cfg80211 to let the driver tell cfg that it has got
> beacon from another AP it can preauth with. Then the supplicant will
> start the pre-auth process when it receives the message.
I don't get it. You have the information, it's part of the scan results,
quite obviously. Roaming, and consequently pre-authentication, isn't
triggered by the driver. Or are you thinking about full-mac scenarios?
johannes
prev parent reply other threads:[~2010-08-14 12:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-13 14:40 cfg80211 support for pre-auth Dhiraj Gaurh
2010-08-14 12:18 ` Johannes Berg [this message]
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=1281788311.3984.1.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=dhiraj.gaurh@gmail.com \
--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