aboutsummaryrefslogtreecommitdiffstats
path: root/wpa_supplicant/autoscan.c
Commit message (Collapse)AuthorAgeFilesLines
* Add support for configuring scheduled scan plansAvraham Stern2015-11-301-3/+24
| | | | | | | | | | | | Add the option to configure scheduled scan plans in the config file. Each scan plan specifies the interval between scans and the number of scan iterations. The last plan will run infinitely and thus specifies only the interval between scan iterations. usage: sched_scan_plans=<interval:iterations> <interval2:iterations2> ... <interval> Signed-off-by: Avraham Stern <avraham.stern@intel.com>
* Document wpa_s->scan_reqJouni Malinen2012-11-251-1/+1
| | | | | | | Use an enum with documented values to make it easier to understand how wpa_s->scan_req is used. Signed-hostap: Jouni Malinen <j@w1.fi>
* Start autoscan for first connection attemptJouni Malinen2012-06-261-1/+3
| | | | | | | | | Use wpa_supplicant_set_state() to initialize state to DISCONNECT so that autoscan gets initialized properly. This needs a change in autoscan_init() to avoid extra scan request that would postpone the first scan request when an interface is added. Signed-hostap: Jouni Malinen <j@w1.fi>
* Add a simple periodic autoscan moduleTomasz Bursztyka2012-06-261-0/+7
| | | | | | | This module will sets a fixed scanning interval. Thus, the parameter to this module is following this format: <fixed interval> Signed-hostap: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
* Add autoscan module named exponentialTomasz Bursztyka2012-06-261-0/+7
| | | | | | | This module will compute the interval on a base exponential. Thus, params to this module are following this format: <base>:<limit> Signed-hostap: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
* Add automatic scanning supportTomasz Bursztyka2012-06-261-0/+127
Like bgscan, autoscan is an optional module based feature to automate scanning but while disconnected or inactive. Instead of requesting directly a scan, it only sets the scan_interval and the sched_scan_interval. So, if the driver supports sched_scan, autoscan will be able to tweak its interval. Otherwise, the tweaked scan_interval will be used. If scan parameters needs to be tweaked, an autoscan_params pointer in wpa_s will provide those. So req_scan / req_sched_scan will not set the scan parameters as they usually do, but instead will use this pointer. Modules will not have to request a scan directly, like bgscan does. Instead, it will need to return the interval it wants after each notification. Signed-hostap: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>