Hi, > You know that I don't have any 64 bit box, so I can't really > test it. I did extensive work with people of Gentoo and Debian to make > sure that my fix in Wireless Extension works both with 32 bits > userspace on 64 bits kernel and 64 bits userspace on 64 bits > kernels. The versions that are fully fixed are 29-pre20 and later. Ok. Sounds good. > Then, I modified NetworkManaged to use libiw for scan > parsing. The idea was to simplify NetworkManager and fix the 32-64 bit > bug, plus a few other potential gotchas. The first version of > NetworkManager to include that fix is 0.6.5. But, I've just realised > that I did not convert event parsing, which could be an issue, I'll > try to work on that. > Note that the other big issue is that, if wpa_supplicant is > present, NetworkManager will request the scan from it, and won't use > its internal code, so all those fixes are useless. Maybe there should > be a control to force NetworkManager to use its own scan code when > needed. Does NM always use wpa_supplicant even in 0.6.5? I thought only later versions deferred everything to it. > As far as I know, Debian testing (Lenny) has those > packages. Of course, I would not mind if you could test all this, > verify that the packages are the right version and that iwlist works > properly. If iwlist does not work, the rest will never works. iwlist works fine on my quad G5 box, but NM doesn't. I suppose then it does use wpa_supplicant. > With respect to wpa_supplicant. Well, I sent multiple e-mail > to Jouni to inform him about this. My personaly inclination would be > to rip the custom parsing code of wpa_supplicant and use libiw > instead, but Jouni will never accept that. Maybe you should use > xsupplicant instead. Can't really use xsupplicant, since NM relies on it and we want the kernel to rely more on wpa_supplicant (or another userspace MLME implementation). Is it really hard to fix the parsing code in wpa_supplicant? I'm not familiar with the workaround at all. > Ok, I see what's happening. That would just prevent you to set > authentication information, but that is not the root caause of your > problems. I'll puch a fix ASAP to John. Not sure, this seems to make wpa_supplicant unhappy enough to not even start doing anything. But then I configured it for WPA. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
