Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Mark Powell <Mark.Powell@csr.com>
Cc: Michael Wu <flamingice@sourmilk.net>,
	David Lamparter <dl@diac24.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: Wed, 13 Jun 2007 18:08:57 +0200	[thread overview]
Message-ID: <1181750937.29767.89.camel@johannes.berg> (raw)
In-Reply-To: <F3555D2D288C3C4CBA0001C074188F119F8913@cameurexb01.EUROPE.ROOT.PRI>

[-- Attachment #1: Type: text/plain, Size: 839 bytes --]

On Tue, 2007-06-12 at 18:01 +0100, Mark Powell wrote:

> This is to do with the operation of the "Controlled Port" as specified
> by 802.1x, which is handled by the driver. When the key exchanges are
> complete and the link is secure, then data is allowed to flow. With
> wext, the driver has to guess when this state is reached, based on
> knowledge of how wpa_supplicant uses wext.

Is that really something the driver needs to handle? I see controlled
port operation in mac80211 but I didn't dig yet why it is necessary. As
Michael points out, shouldn't it be possible to handle it entirely from
userland? What userland are you using that needs the driver doing it?

Of course, there's the question of whether to accept packets anyway or
not, I think that's what the 8021x setting in mac80211 does. Not sure.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

  parent reply	other threads:[~2007-06-13 16:09 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
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 [this message]
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=1181750937.29767.89.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=Mark.Powell@csr.com \
    --cc=dcbw@redhat.com \
    --cc=dl@diac24.net \
    --cc=flamingice@sourmilk.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