problem with hostap+ndiswrapper

[Joey Richards]

Al,

That's interesting.  Please let us know if you figure out what the 
difference is.  I'm using Gentoo with a 2.6.15-r1 kernel and having no luck.

Also, if you do have access to another machine that can sniff all the 
wireless traffic, please let us know.  This is actually what I meant by 
my suggestion.  Jouni thought that getting a complete record of the 
packets exchanged between the AP and the client could help determine 
what's going wrong.  The hypothesis was that some sort of event was not 
making its way between the driver and wpa_supplicant.

What are the versions of various things (ndiswrapper, wpa_supplicant, 
kernel) under the working Knoppix configuration?  Are they the same as 
for your Devil-Linux configuration?

Thanks, and glad to hear you made some progress,
joey


> Date: Tue, 21 Mar 2006 23:32:41 +0000
> From: "FireStorm -" <gandalf_the_gray at hotmail.com>
> Subject: Re: problem with hostap+ndiswrapper
> To: hostap at shmoo.com
> Message-ID: <BAY107-F183D344A65F794A9AD0268DCD80 at phx.gbl>
> Content-Type: text/plain; format=flowed
> 
> Hello Joey,
> 
>> >it was suggested to try to use a 3rd
>> >party (i.e., another PC with a wireless card)
> 
> I followed your advice and booted the laptop with Knoppix instead of 
> Devil-Linux. The good news is that now wpa_supplicant works perfectly. The 
> bad news is that now I have to figure out what's wrong with my Devil Linux 
> build.
> 
> Two things I noticed so far:
> 
> 1) there is no more "ioctl[SIOCSIWENCODEEXT]: No such device" repeated 4 
> times when I launch wpa_supplicant, but only "ioctl[SIOCSIWPMKSA]: No such 
> device" repeated once.
> 
> 2) When issuing "wpa_cli status" now I get:
> 
> Selected interface 'wlan0'
> bssid=xx:xx:xx:xx:xx:xx
> ssid=<xxx>
> pairwise_cipher=TKIP
> group_cipher=TKIP
> key_mgmt=WPA-PSK
> wpa_state=COMPLETED
> ip_address=10.0.69.73
> Supplicant PAE state=AUTHENTICATED
> suppPortStatus=Authorized
> EAP state=SUCCESS
> 
> The weird things is that previously (in the non-working scenario) the last 3 
> lines were missing. Something I messed configuring wpa_supplicant ? Some 
> kernel support for EAP that was missing ? Any other possibility ?
> 
> Thanks
> 
> Al
> 
> 
>>> > >