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

[Enrico]

wpa_s starts wpa_driver_ops::get_bssid() after EVENT_ASSOC.
why it thinks it is has just associated with a *different BSS* if in ap_scan=2?
do i have to return wpa_event_data::assoc_info with EVENT_ASSOC?
any suggestion is welcome
Regards,
Enrico

here is the log:
.
.
rwn0: State: SCANNING -> ASSOCIATING
(begin wpa_driver_ops::associate())
ILLUMOS_set_wpa_ie
ap_scan=2, BSSID IS NULL
(begin wpa_driver_ops::associate())
rwn0: Setting authentication timeout: 60 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - EAP fail=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portControl=Auto
EAPOL: Supplicant port status: Unauthorized
rwn0: RX EAPOL from *00:1b:2f:aa:2a:c0*
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 01 
26 4b 72 fc 8c 0b 6c 4a 82 1c 9b 53 b2 be e6 3f 77 7b 1f f2 00 28 82 3c 2f d8 c9 
24 6d 86 24 52 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
rwn0: Not associated - Delay processing of received EAPOL frame
ILLUMOS_event_handler: got event EVENT_ASSOC
rwn0: *Event ASSOC* (0) received
rwn0: State: ASSOCIATING -> ASSOCIATED
ILLUMOS_get_bssid: 00:1b:2f:aa:2a:c0
rwn0: Associated to a *new BSS*: BSSID=00:1b:2f:aa:2a:c0
.
.
.
now wpa_s disconnects, searching for a new configured network



On 06/08/2012 01:36 PM, Enrico wrote:
> 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
>>