Re: Errors running current SVN code
- From: Dan Williams <dcbw redhat com>
- To: Simon Geard <delgarde ihug co nz>
- Cc: networkmanager-list gnome org
- Subject: Re: Errors running current SVN code
- Date: Mon, 29 Jan 2007 08:04:10 -0500
On Mon, 2007-01-29 at 17:45 +1300, Simon Geard wrote:
> On Sat, 2007-01-27 at 07:14 -0500, Dan Williams wrote:
> > dbus-send --system --dest=org.freedesktop.NetworkManager \
> > --print-reply /org/freedesktop/NetworkManager/Devices/ath0 \
> > org.freedesktop.NetworkManager.Devices.getProperties
> >
> > See if any of the network object paths look funny.
>
> Indeed, they do - this command includes various normal networks, and
> sometimes (not consistently) includes the invalid one.
>
> Tracing back, it appears that the problem originates either in
> wpa_supplicant, or in the code that talks to it. My debugging shows
> supplicant_iface_scanned_ap_cb() in nm-device-802-11-wireless.c is being
> called where the ssid entry has entry.array_len equal to 8, but where
> the entire entry.bytearray_value is zeroed.
>
> Any ideas? This is running version 0.5.7 of wpa_supplicant, if that
> helps.
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?
Basically, we have to narrow down whether its the driver,
wpa_supplicant, or NM.
Dan
> Simon.
> _______________________________________________
> NetworkManager-list mailing list
> NetworkManager-list gnome org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]