Fix for missing access points in the list. #39 #36 #41
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In some circumstances not all available access points in range were being listed, or only the connected AP was being found. The problem seems to affect Win10 (maybe adapter specific) and is exacerbated by the passage of time since the connection was established and also by frequent polling of the APs (with APs slowly disappearing over time from the list). To remedy this, its necessary to tell Windows to scan for APs prior to enumerating the APs (opening the Win10 WiFi connection list would actually resolve the problem temporarily). This fix performs a scan during initialisation and optionally rescans automatically when retrieving the list of APs (if more than 60s have elapsed since the last scan). Strictly speaking you should wait for a notification the scan completed before retrieving the APs - but this implementation works well enough in a polling situation.
|
From the MS docs: So I guess there is no way to find out when the scan has finished? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In some circumstances not all available access points in range were being listed, or only the connected AP was being found - #39.
The problem seems to affect Win10 (maybe adapter specific) and is exacerbated by the passage of time since the connection was established and also by frequent polling of the APs (with APs slowly disappearing over time from the list) - #36
To remedy this, its necessary to tell Windows to scan for APs prior to enumerating the APs (opening the Win10 WiFi connection list would actually resolve the problem temporarily).
This fix performs a scan during initialisation and optionally rescans automatically when retrieving the list of APs (if more than 60s have elapsed since the last scan).
Strictly speaking you should wait for a notification the scan completed before retrieving the APs - but this implementation works well enough in a polling situation. #