From: Dan Williams <dcbw@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Zhu Yi <yi.zhu@intel.com>, dragoran <drago01@gmail.com>,
linux-wireless@vger.kernel.org,
ipw3945-devel <ipw3945-devel@lists.sourceforge.net>,
"John W. Linville" <linville@tuxdriver.com>,
Jouni Malinen <j@w1.fi>, Jean Tourrilhes <jt@hpl.hp.com>
Subject: Re: [ipw3945-devel] iwl3945/mac80211 cannot connect to dynamic wep network
Date: Wed, 24 Oct 2007 11:07:03 -0400 [thread overview]
Message-ID: <1193238423.2557.41.camel@localhost.localdomain> (raw)
In-Reply-To: <1193161034.7733.38.camel@johannes.berg>
On Tue, 2007-10-23 at 19:37 +0200, Johannes Berg wrote:
> On Tue, 2007-10-23 at 10:07 -0400, Dan Williams wrote:
>
> > Was there ever a conclusion to this patch? ISTR it went through a
> > couple comments and was more or less rejected as the wrong approach.
> > Can anyone comment as to what the _right_ approach is? Not being able
> > to connect to dynamic WEP networks is not acceptable, what needs to be
> > done to make this work?
>
> My take on it is that it's a wpa_supplicant/wext bug.
>
> See, the log says:
> eth1: privacy configuration mismatch and mixed-cell disabled - disassociate
>
> So that means ieee80211_privacy_mismatch() returned non-zero. However,
> ieee80211_privacy_mismatch() will return 0 instantly when key management
> is enabled, which is obviously true with dynamic WEP.
>
> Hence, IMHO wpa_supplicant should be telling us that it enabled key
> management. But the wext interface is crappy enough to not have a
> definition for dynamic WEP which probably means that in the
> wpa_driver_wext_keymgmt2wext() function in wpa_supplicant's
> driver_wext.c 0 is returned, while we take anything but zero to be "key
> management is enabled".
Could you educate me a bit more about the problem if you've got a bit of
time?
A normal Dynamic WEP configuration should result in wpa_supplicant
sending IW_AUTH_KEY_MGMT with IW_AUTH_KEY_MGMT_802_1X since ieee8021x is
specified in the wpa_supplicant config. Is this not happening here? I
seem to be seeing that wpa_supplicant _should_ be setting key
management, and mac80211 _should_ be returning 0 from
ieee80211_privacy_mismatch() because key management has been set, and
therefore this should succeed...
Dan
> The proper fix would be to
> (a) remove the crap about IW_AUTH_KEY_MGMT values from wext,
> no drivers except mac80211 care and that cares only about
> enabled/disabled
> (b) make the parameter to IW_AUTH_KEY_MGMT a boolean
> (no code changes required, only comment updates, since no driver
> cares one bit except mac80211 which treats it as a bool already)
> (c) update wpa_supplicant's wpa_driver_wext_keymgmt2wext function to
> return 0 for KEY_MGMT_NONE and 1 for everything else
>
> I'm not going to do it though. Dynamic WEP is just too uninteresting to
> me.
>
> johannes
next prev parent reply other threads:[~2007-10-24 15:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 7:54 iwl3945/mac80211 cannot connect to dynamic wep network dragoran
2007-10-23 8:14 ` [ipw3945-devel] " Zhu Yi
2007-10-23 8:56 ` dragoran
2007-10-23 14:07 ` Dan Williams
2007-10-23 17:37 ` Johannes Berg
2007-10-24 15:07 ` Dan Williams [this message]
2007-10-25 13:29 ` Johannes Berg
2007-10-25 13:49 ` Dan Williams
2007-10-25 13:57 ` Johannes Berg
2007-10-28 5:18 ` Dan Williams
2007-10-28 10:28 ` Johannes Berg
2007-10-28 17:36 ` Jouni Malinen
2007-10-28 17:54 ` Johannes Berg
2007-10-28 18:49 ` Jouni Malinen
2007-10-29 14:42 ` Johannes Berg
2007-10-26 10:32 ` [PATCH] " dragoran
2007-10-26 10:43 ` Johannes Berg
2007-10-26 10:53 ` dragoran
2007-10-26 10:43 ` [PATCH] fix dynamic wep dragoran
2007-10-26 10:55 ` Johannes Berg
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=1193238423.2557.41.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=drago01@gmail.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=jt@hpl.hp.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=yi.zhu@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.