On Tue, 2007-01-30 at 20:14 +1300, [EMAIL PROTECTED] wrote: > Dan Williams wrote: > > If you can build your own copy of wpa_supplicant, put some > > debugging prints in driver_wext.c in > > wpa_driver_wext_get_scan_results() in the 'case > > SIOCGIWESSID:' block to print out the code flow there. > > What's 'ssid_len'? Does the 'if (custom + ssid_len > > > end)' trigger? > > No it doesn't, but the problem does seem to be passing > through this code. The ssid_len is set to 8 (same as NM > sees), but custom appears to be an empty string.
Can you show me the debug code you put into wpa_supplicant so I can see the exact flow and values? Thanks! Dan > I guess this points to a possible driver bug, so I'll try > update those just in case, see if that helps... > > Incidentally, NM is currently running fine with the attached > patch applied, filtering out the obviously bad item. Would > you want to apply it as a form of idiot-proofing, or do you > prefer to just rely on drivers (and wpa_supplicant) not > providing bad data? > > Simon. > _______________________________________________ > NetworkManager-list mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/networkmanager-list _______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
