> > You are right . It may be wpa_supplicant issue . (I'm moving to hostap list > > as soon as I get subscribed ) > > Kernel is amd64 and wpa_supplicant is i386 binary. > > Isn't this the known issue with ioctl compat code when using 64-bit > kernel with 32-bit user space? Yes. > wireless-tools has some workaround code > for figuring out what kernel is trying to say in WEXT data, but > wpa_supplicant does not have such workaround since I do not believe it > belongs to every user space program that is using WEXT. I think only Jean disagrees. > If I've understood correctly, Dave Miller is working on cleaning up the > compat WEXT code (see "Proper compat WEXT support" thread from June 3rd > for the patch series). I would hope that that fixes issues with > 64/32-bit systems without require all user space programs to be modified > to be aware of the bogus data from the kernel. As a temporary > workaround, it might help to build 64-bit wpa_supplicant for that > kernel. Yeah, it should be in there. Building a 64-bit wpa supplicant is quite hard unless you have all 64-bit libs already, so maybe it's easier to apply Dave's patches. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
