From: Michael Wu <flamingice@sourmilk.net>
To: "Mark Powell" <Mark.Powell@csr.com>
Cc: "David Lamparter" <dl@diac24.net>,
"Johannes Berg" <johannes@sipsolutions.net>,
"David Lamparter" <lists@diac24.net>,
"Dan Williams" <dcbw@redhat.com>,
"linux-wireless" <linux-wireless@vger.kernel.org>
Subject: Re: [RFC] {cfg,nl}80211 API
Date: Tue, 12 Jun 2007 09:45:30 -0700 [thread overview]
Message-ID: <200706120945.41154.flamingice@sourmilk.net> (raw)
In-Reply-To: <F3555D2D288C3C4CBA0001C074188F119F88C3@cameurexb01.EUROPE.ROOT.PRI>
[-- Attachment #1: Type: text/plain, Size: 722 bytes --]
On Tuesday 12 June 2007 06:58, Mark Powell wrote:
> Very interesting. It raised a question in my mind...
> When associating to a WPA network, at what point should the driver open
> the controlled port?
> With wext/wpa_supplicant, the driver relies on knowing that the
> supplicant sets the pairwise key first and group key second and can open
> the controlled port after the second key.
>
> Can we tie down the correct behaviour more tightly in cfg80211/nl80211?
>
Shouldn't wpa_supplicant know when the connection is ready? It has support for
dormant mode, so the link can be held down by userspace until it is ready.
The driver shouldn't need to figure out when the link is ready to go up.
-Michael Wu
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-06-12 16:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 23:04 [RFC] {cfg,nl}80211 API David Lamparter
2007-06-12 9:15 ` Johannes Berg
2007-06-12 12:08 ` Dan Williams
2007-06-12 14:55 ` Tomas Winkler
2007-06-12 9:59 ` Holger Schurig
2007-06-12 13:15 ` David Lamparter
2007-06-12 13:58 ` Mark Powell
2007-06-12 16:45 ` Michael Wu [this message]
2007-06-12 17:01 ` Mark Powell
2007-06-13 6:46 ` Michael Wu
2007-06-13 13:25 ` David Lamparter
2007-06-13 16:08 ` Johannes Berg
2007-06-13 10:22 ` Johannes Berg
2007-06-13 13:18 ` [RFC] {cfg,nl}80211 API - 802.11j David Lamparter
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=200706120945.41154.flamingice@sourmilk.net \
--to=flamingice@sourmilk.net \
--cc=Mark.Powell@csr.com \
--cc=dcbw@redhat.com \
--cc=dl@diac24.net \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=lists@diac24.net \
/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