Problem setting keys with ndiswrapper after authentication?
Mon Nov 29 03:23:43 PST 2004
Warning: crossposted to hostap and ndiswrapper mailing list.
On Sat, Nov 27, 2004 at 08:55:36PM -0800, Jouni Malinen wrote:
> ndiswrapper-general cc'ed; please, apply the attached patch to
> ndiswrapper CVS.
Thank you for the answer. I had no time to try it (my laptop is at home
now), but I will report back as soon as possible.
Just one question: I downloaded ndiswrapper 0.12 and --- although via a
completely different patch --- the iwndis.c file is quite changed. Should I
use this version? Is the bug fixed in a different way?
> > [root at rukbat wifi]# iwconfig wlan0 mode managed essid upco_wlan key 0 open
> > [root at rukbat wifi]# iwconfig wlan0 && ifconfig wlan0
> > wlan0 IEEE 802.11b ESSID:"upco_wlan"
> > Mode:Managed Frequency:2.427GHz Access Point: 00:11:5C:77:82:40
> OK, so association works when done manually. I tested this with
> wpa_supplicant doing scanning and it actually failed. ndiswrapper ended
> up configuring the driver to reject APs that were using encryption.. I
> fixed wpa_supplicant to set cipher suite to WEP-104 when using IEEE
> 802.1X (available in the current Host AP CVS snapshot) and this seemed
> to have fixed the association part.
Do you mean the CVS snapshot "stable" or "development"?
> The attached patch to the current ndiswrapper CVS version fixes these
> problems. With this patch and the current CVS version of wpa_supplicant,
> I was able to complete IEEE 802.1X (non-WPA) authentication and use the
> encrypted data connection (both unicast and multicast worked).
I will try it later tonight or tomorrow and report. Thanks.
Romano Giannetti - Univ. Pontificia Comillas (Madrid, Spain)
Electronic Engineer - phone +34 915 422 800 ext 2416 fax +34 915 596 569
More information about the Hostap