how to trigger 'set_key/associate' with ap_scan=0 and CONFIG_NO_SCAN_PROCESSING?

Enrico enricop
Fri Jun 8 04:36:32 PDT 2012

I found out ap_scan=2 just perfectly fits our needs,
the driver sets the bssid manually before mlme assoc request is sent.
With ap_scan=2, even after setting 'bssid=', wpa_driver_associate_params::bssid 
is always NULL....

On 06/07/2012 07:04 PM, Enrico wrote:
> Hi,
> on Illumos, platform driver and system library take care of scanning, AP
> selection, and set ieee802.11 parameters.
> For reducing architectural changes we want to avoid wpa_s from sending scan
> requests once started. I would like to know what is the recommended way for
> externally triggering set_key and associate driver ops.
> We set up wpa_s with CONFIG_NO_SCAN_PROCESSING, and start it with ap_scan=0.
> It triggers _init, _get_ssid, _get_bssid, but _set_key and _associate are never
> started, even if *all* "wpa_scan_res" and "wpa_ie_data" fields have been passed
> via control interface.
> (only caps and freq are missing because already set by the driver)
> (get_bssid, get_ssid return 00:00..... and 0)
> EVENT_SCAN_RESULTS cannot be used, scan is performed before wpa_s even starts...
> Reassociate/reconnect ctrl_if commands request a scan...
> I've seen ways to force it after i set network params via ctrl_if, not sure if
> this supported by wpa_s state machine.
> Any suggestion?
> Thank, Enrico

More information about the Hostap mailing list