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: information SUP: sending
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.
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:45:43
