-
-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request - Wireless Regulatory Domain #25378
Comments
Any news on this issue? |
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly:
|
Still important to me. Though it's closely related to #57053. |
I marked this as stale due to inactivity. → More info |
Database can be enabled with
Choosing regdom needs to typically be done in
For example
|
@FRidh I tried your suggestion but it doesn't seem to apply correctly. Using Using
Is |
Just an idea for a NixOS module setting for setting the wireless regulatory domain. Usually set by doing
iw reg set AU
.Note that this isn't always possible depending on the wireless driver and wireless card, some cards like Intel have some sort of managed mode or hardware lock that auto locks it to somewhere. My intel 7265D actually fixes it to "00-World", seemingly not able to detect where it is or allow it to be manually specified.
I do not know how this interacts with hostapd country_code specification.
The text was updated successfully, but these errors were encountered: