-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
wifi: nrf70: Regulatory handling broken #79916
Comments
Hi @kapbh! We appreciate you submitting your first issue for our open-source project. 🌟 Even though I'm a bot, I can assure you that the whole community is genuinely grateful for your time and effort. 🤖💙 |
Thanks @kapbh, I have triaged the issue:
But as |
We also should start enforcing fixes for all drivers when making such changes to avoid breakages. |
Recent WPA supplicant changes have broken nRF regulatory support, implement the new set/get country WPA supplicant ops. WPA supplicant: Regulatory SET through WPA supplicant, GET is direct to the driver Scan only: SET and GET direct calls to the driver Fixes zephyrproject-rtos#79916. Signed-off-by: Chaitanya Tata <[email protected]>
Yes, the previous changes of
If any suggestion or need fix pls ping me. |
If you see the shell help, this basically means that disable any regulatory hints (e.g., beacon) and use the reg_domain from user as a only hint. Problem is, supplicant doesn't have this concept, so, we cannot implement this using |
Describe the bug
The wifi command
wifi reg_domain
is not setting the regulatory domain.To Reproduce
west build -p -b nrf7002dk/nrf5340/cpuapp
wifi reg_domain IN -f
Cannot set Regulatory domain: -1
Expected behavior
It should set the regulatory domain:
Wi-Fi Regulatory domain set to: IN
Logs and console output
wifi reg_domain IN -f
Cannot set Regulatory domain: -1
Environment (please complete the following information):
0fb63c05d1b9ed17cca3d8138a6844d2c125d08b
The text was updated successfully, but these errors were encountered: