Problem with the ROAM wpa_cli command and external scans.
Fri Jul 10 11:00:38 PDT 2015
On 07/10/2015 10:54 AM, Jouni Malinen wrote:
> On Wed, Jul 08, 2015 at 03:59:00PM -0700, Ben Greear wrote:
>> Previously (or so I believe), I could request a scan using 'iw', and then
>> tell wpa_cli to do a roam now than the scan is fresh. I let user specify
>> the channels to scan with iw so that I can minimize scan time..which is a big help
>> when doing lots of virtual stations.
>> But, now it seems wpa_supplicant ignores these external scans.
> Why would you use iw for doing the scan if you end up using
> wpa_supplicant control interface for the ROAM command anyway? I would
> use "SCAN freq=<known freq(s)>" instead for triggering the scan and then
> follow that with ROAM if the BSS table includes the target BSS.
I can look into doing it with wpa_cli. But, why/when would you want to ignore
external scans anyway?
Regardless, I think this particular problem was not caused by scan results,
but was instead that the station was not associated when I requested the
ROAM. To fix this properly, I probably need to make wpa_cli able to return
a numeric error code (to program against), and a string error message to
show to users...having to look through the logs and detect specific errors
that way programatically is probably not a useful way to go about it.
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc http://www.candelatech.com
More information about the Hostap