ndiswrapper + wpa_supplicant
dcbw at redhat.com
Wed Dec 5 10:17:14 EST 2007
On Wed, 2007-12-05 at 11:09 -0400, George N. White III wrote:
> On Dec 5, 2007 10:25 AM, Sukku <m.sukumar at gmail.com> wrote:
> > Hi All,
> > From last two weeks, I am working on this problem. I am working on FC8 with
> > kernel version 126.96.36.199-42.
> > I am using Linksys wireless adapter (WUSB54G). I didn't found any linux
> > drivers for this device. so by using ndiswrappers I installed windows native
> > drives in linux box. finally adapter got detected.
> > after words I try to use this wpa_supplicant on this adapter. Hear I am
> > facing problem
> > In debugging mode I am getting so many IOCTL errors. I am not getting,
> > there errors are from ndiswrapper or wpa_supplicant.
> I saw those errors, and failed to connect, also using FC8 with a ndiswrapper
> but a different USB dongle (TEW). However, NetworkManager is more or
> less working (too frequent disconnects from my AP, connects to random
> open AP's). Check that there isn't a 2nd copy of wpa_supplicant running.
NM itself will only ever connect to an AP that you've chosen from the
If you've never chosen that AP from the menu, it's important to remember
that the driver and/or firmware also control roaming, and that
often-times the driver/firmware will decide to associate to an access
point without being told to so (ipw* does this a lot). Some drivers
have module options to disable that functionality, and the only real
arguments I've heard for this behavior are that people alone in the
woods then don't need to issue manual iwconfig commands when they start
their computer up. I'm not sure what the security implications of the
card connecting to a random open AP are, but it can't be much good.
More information about the HostAP