linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Michael Buesch <mb@bu3sch.de>
Cc: dragoran <drago01@gmail.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org
Subject: Re: mac80211 does not support WPA when used with wext
Date: Sat, 31 Mar 2007 13:57:55 -0400	[thread overview]
Message-ID: <1175363875.9349.11.camel@localhost.localdomain> (raw)
In-Reply-To: <200703311837.27990.mb@bu3sch.de>

On Sat, 2007-03-31 at 18:37 +0200, Michael Buesch wrote:
> On Saturday 31 March 2007 13:19, dragoran wrote:
> > Johannes Berg wrote:
> > > On Sat, 2007-03-31 at 11:36 +0200, dragoran wrote:
> > >   
> > >> Hello
> > >> While testing the iwlwifi driver I noticed that the mac80211 does 
> > >> provide a wext interface but does not support wpa with it.
> > >>     
> > >
> > > You must have done something wrong, it works well.
> > >
> > >   
> > same also happens with the rt2x00 drivers....
> > it seems that I am not doing something wrong but that you are using a 
> > ieee80211 based driver....
> 
> I think you can trust Johannes, the author of the mac80211 configuratrion
> interface, in this matter. ;)
> mac80211 _does_ work with WPA. For sure. 100%.
> You are doing something wrong.

No, he's not, see my previous post.  mac80211 doesn't use the right
WE-18 and later IWEVGENIE event to report IEs in scan results.  Like
every other in-kernel driver/stack out there besides mac80211.

Dan



  parent reply	other threads:[~2007-03-31 17:54 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-31  9:36 mac80211 does not support WPA when used with wext dragoran
2007-03-31 10:00 ` Johannes Berg
2007-03-31 10:11   ` dragoran
2007-03-31 11:19   ` dragoran
2007-03-31 16:37     ` Michael Buesch
2007-03-31 16:39       ` Michael Buesch
2007-03-31 17:57       ` Dan Williams [this message]
2007-03-31 17:48   ` Dan Williams
2007-03-31 17:59     ` Jouni Malinen
2007-03-31 18:09     ` Larry Finger
2007-03-31 19:03     ` Michael Wu
     [not found]       ` <f6ca9fed0703311256m1b14ec35p836a62de532dd804@mail.gmail.com>
2007-03-31 21:00         ` Michael Wu
2007-04-01  0:50           ` Dan Williams
2007-04-02  3:50             ` WPA does not connect to bcm43xx-mac80211 when using NetworkManager Larry Finger
2007-04-02  4:12               ` Dan Williams
2007-04-03 14:26                 ` Larry Finger
2007-04-02  5:26               ` Michael Wu
2007-04-01  8:18           ` mac80211 does not support WPA when used with wext Johannes Berg
     [not found]           ` <f6ca9fed0704081445u5536e596m4ca4caeb44f7f87@mail.gmail.com>
2007-04-08 21:54             ` Michael Wu
     [not found]               ` <f6ca9fed0704081527j641a4ecat44151e107cab7342@mail.gmail.com>
2007-04-10  7:13                 ` dragoran
2007-04-10 12:25                   ` Dan Williams
2007-04-10 14:34                     ` dragoran dragoran
2007-04-10 14:39                   ` Larry Finger
2007-04-10 14:44                     ` dragoran dragoran
2007-04-01  0:55       ` Dan Williams
2007-04-01  1:21         ` Michael Wu
2007-04-01  4:51           ` Dan Williams

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=1175363875.9349.11.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=drago01@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mb@bu3sch.de \
    /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;
as well as URLs for NNTP newsgroup(s).