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 localhost NetworkManager: <information> SUP: sending > command 'INTERFACE_ADD eth1 wext /var/run/wpa_supplicant ' > Jan 9 12:45:43 localhost NetworkManager: <information> SUP: response > was 'OK' > Jan 9 12:45:43 localhost NetworkManager: <information> SUP: sending > command 'AP_SCAN 2' > Jan 9 12:45:43 localhost NetworkManager: <information> SUP: response > was 'UNKNOWN COMMAND' > > ap_scan=2 is a valid ctrl parameter setting from a wpa_supplicant.conf > file but 'AP_SCAN 2' is not a valid ctrl command for use with the > wpa_supplicant control interface which is laid out in ctrl_iface.c. > > The solution is to delete the use of AP_SCAN and to compile in the > desired default behaviour ap_scan=2. This will work for now.
Yeah, it might take a while for the patch I forwarded upstream to wpa_supplicant folks time to get into the program. Jouni is usually pretty responsive, so I'm not sure how long that will take. Dan _______________________________________________ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list