On Mon, 2006-01-09 at 15:19 -0500, Bill Moss wrote:
> Yesterday, I built 1.710 which did not use the bogus AP_SCAN ctrl
> command and it worked fine. Today, I build 1.721 and the bug log showed
> the following because the invalid AP_SCAN ctrl command had been added to
> the NM code.
>
> Jan 9 12:4
On Mon, 2006-01-09 at 14:38 -0500, Robert Love wrote:
> On Mon, 2006-01-09 at 14:27 -0500, Bill Moss wrote:
>
> > 3. NM is now connecting at home with broadcast essid and at work with
> > hidden essid.
>
> Was it not working before?
It will fail out and refuse to connect if AP_SCAN can't be set
Yesterday, I built 1.710 which did not use the bogus AP_SCAN ctrl
command and it worked fine. Today, I build 1.721 and the bug log showed
the following because the invalid AP_SCAN ctrl command had been added to
the NM code.
Jan 9 12:45:43 localhost NetworkManager: SUP: sending
command 'INTERFACE
On Mon, 2006-01-09 at 14:27 -0500, Bill Moss wrote:
> 3. NM is now connecting at home with broadcast essid and at work with
> hidden essid.
Was it not working before?
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome
1. Since AP_SCAN is not a command defined for the ctrl interface of
wpa_supplicant, I deleted the following lines from
nm-device-802-11-wireless.c
/* Tell wpa_supplicant that we'll do the scanning */
if (!nm_utils_supplicant_request_with_check (ctrl, "OK",
__func__, NULL,
