Skip to content
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

Open
CMCDragonkai opened this issue May 1, 2017 · 6 comments
Open

Feature Request - Wireless Regulatory Domain #25378

CMCDragonkai opened this issue May 1, 2017 · 6 comments

Comments

@CMCDragonkai
Copy link
Member

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.

@mmahut
Copy link
Member

mmahut commented Aug 19, 2019

Any news on this issue?

@stale
Copy link

stale bot commented Jun 2, 2020

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:

  1. Search for maintainers and people that previously touched the related code and @ mention them in a comment.
  2. Ask on the NixOS Discourse.
  3. Ask on the #nixos channel on irc.freenode.net.

@stale stale bot added the 2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md label Jun 2, 2020
@AleXoundOS
Copy link
Contributor

AleXoundOS commented Nov 21, 2020

Still important to me. Though it's closely related to #57053.

@stale stale bot removed the 2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md label Nov 21, 2020
@stale
Copy link

stale bot commented Jun 4, 2021

I marked this as stale due to inactivity. → More info

@stale stale bot added the 2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md label Jun 4, 2021
@FRidh
Copy link
Member

FRidh commented Apr 12, 2022

Database can be enabled with

  hardware.wirelessRegulatoryDatabase = true;

Choosing regdom needs to typically be done in

boot.extraModprobeConfig

For example

  boot.extraModprobeConfig = ''
    options cfg80211 ieee80211_regdom="SE"
  '';

@stale stale bot removed the 2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md label Apr 12, 2022
@thomaseizinger
Copy link

thomaseizinger commented Dec 19, 2023

@FRidh I tried your suggestion but it doesn't seem to apply correctly. Using iw (nix-shell -p iw), it still reads as the wrong regulatory domain afterwards. I can set the domain to something else using iw but that doesn't persist between boots.

Using systool, I can see that the parameter is set correctly:

  Parameters:
    bss_entries_limit   = "1000"
    cfg80211_disable_40mhz_24ghz= "N"
    ieee80211_regdom    = "US"

Is iw mis-reading it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants