[PATCH 0/5 - v2] Automatic scanning support

Tomasz Bursztyka tomasz.bursztyka
Thu Apr 19 00:12:35 PDT 2012

>> That can be done already, again in a module you want. You can play there
>> with wpa_s->ssid which is used then by
>> wpa_supplicant_req_sched_scan()/wpa_supplicant_req_scan()
> I cannot find ssid field in the wpa_supplicant structure. Currently wpa_supplicant_scan() take ssid list from configuration.
Yes, my mistake, I was talking about wpa_s->config->ssid.
> In a specific autoscan module it's worth to have ability to alter ssid list per scan iteration. Though it could be possible only
> if autoscan module itself builds wpa_driver_scan_params structure. The same regarding scan frequencies list.
Afaik, nothing prevents you from using wpa_s->config->ssid for you own 
purpose (back-upping it, providing you own etc...).
But since it's not that clean, I will add a struct 
wpa_driver_scan_params *autoscan_params in wpa_s that you could set in 
the module.
In req_scan/req_sched_scan function: if that pointer is set it would 
directly use it.

This solution is a bit more intrusive, but way much less than managing 
everything in the module as you proposed,
and solves you issue fully since you can tweak completely the scan 
params then.

I will prepare a new patch set.



More information about the Hostap mailing list