feat: support wireless regulatory regions#5
Draft
tomasff wants to merge 3 commits into
Draft
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Currently it's not possible to connect to APs on channel 13 (or other channels that are not widely available) due to the regulatory constraints imposed by cfg80211, unless the region is configured.
Unfortunately my ISP's router does not let me change which channels are used 😢
Given cfg80211 is loaded before the root fs is ready, it's not able to read the regulatory.db + signature (required before we can configure the regulatory region) if we included it as
ExtraFilePaths:Note the
Direct firmware load for regulatory.db failed with error -2(not found).To support regulatory regions, I've added
ReloadRegulatoryDatabaseandSetRegulatoryRegionupstream in mdlayher/wifi#162.The final piece is this PR which,
gokrazy/wifi00, a world-wide safe default)Opted for this approach as it maintains backwards compatibility without broader kernel changes, while supporting the use case.
The regulatory database does not to seem to change often and bundling it with this package seems in-line with the gokrazy philosophy. The license seems compatible, but please let me know if you have any concerns.
ExtraFiles
Testing
Tested successfully on a Pi Zero 2W with an AP on channel 13 (2.4 Ghz).
with
{ "ssid": "myAP", "psk": "...", "region": "GB" }