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: Sun, 28 Oct 2007 01:18:28 -0400 [thread overview]
Message-ID: <1193548708.7779.10.camel@localhost.localdomain> (raw)
In-Reply-To: <1193320661.14136.10.camel@johannes.berg>
On Thu, 2007-10-25 at 15:57 +0200, Johannes Berg wrote:
> On Thu, 2007-10-25 at 09:49 -0400, Dan Williams wrote:
>
> > Ok, I'll try to track it down starting with wpa_supplicant then.
>
> If you have a network, it's probably as simple as putting a printk into
> the ioctl path and a printf into hostapd's conversion function to see
> what it returns.
This turned out to be a wpa_supplicant issue. wpa_supplicant uses
KEY_MGMT_802_1X_NO_WPA (instead of KEY_MGMT_802_1X) to handle Dynamic
WEP where the AP doesn't broadcast WPA IEs (ie, a pure Dynamic WEP
network), and that value wasn't being handled correctly by
wpa_driver_wext_keymgmt2wext().
This has been fixed on the wpa_supplicant 0.6.x branch but not
backported to the 0.5.x branch yet. Tested with EAP-TLS and LEAP with
iwl4965 on kernel-2.6.23.1-35.fc8.
For Fedora, I've built wpa_supplicant-0.5.7-15.fc8 to fix this issue.
Dan
next prev parent reply other threads:[~2007-10-28 5:24 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
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 [this message]
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=1193548708.7779.10.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 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).