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

802.11ac #1420

Closed
Ekiben542 opened this issue Oct 16, 2023 · 7 comments · Fixed by #1443
Closed

802.11ac #1420

Ekiben542 opened this issue Oct 16, 2023 · 7 comments · Fixed by #1443

Comments

@Ekiben542
Copy link

Ekiben542 commented Oct 16, 2023

Is your feature request related to a problem?

802.11ac does not work if country_code is JP.

Describe the solution you'd like

I would like to be able to use 802.11ac even if the country_code is JP.

Describe alternatives you've considered

Additional context

802.11ac is allowed in Japan.
(https://wifiamateur.blogspot.com/2013/04/80211ac-device-deployment-in-japan.html) Also, this uses Google Translate, so there may be some mistakes, sorry. .

@billz
Copy link
Member

billz commented Oct 17, 2023

Follow this FAQ and report your Linux kernel version with uname -a.

@Ekiben542
Copy link
Author

Linux raspberrypi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux 

@Ekiben542
Copy link
Author

The above output is from running uname -a.

@billz
Copy link
Member

billz commented Oct 18, 2023

Ok, check the FAQ. If you are able to start an 802.11ac AP with 'JP' we can look at adding it.

@Ekiben542
Copy link
Author

Where is the configuration directory?

@godfuture
Copy link

godfuture commented Nov 4, 2023

Same for DE....one of the most famous model (https://avm.de/produkte/fritzbox/fritzbox-7590/technische-daten/) has AC included (as many many others..)

@billz
Copy link
Member

billz commented Nov 4, 2023

You are both absolutely correct. RaspAP has relied on its own internal database to set valid frequencies. This was intended as a short-term fix, but it requires updates with each revision of the kernel's wireless-regdb.

A better approach, I think, would be to parse the output of iw list and use this to set allowed frequencies:

sudo iw reg set JP
iw list
Wiphy phy1
...
Band 1:
    Frequencies:
	* 2412 MHz [1] (20.0 dBm)
	* 2417 MHz [2] (20.0 dBm)
	* 2422 MHz [3] (20.0 dBm)
	* 2427 MHz [4] (20.0 dBm)
	* 2432 MHz [5] (20.0 dBm)
	...
Band 2:
    Frequencies:
	* 5180 MHz [36] (18.0 dBm)
	* 5200 MHz [40] (18.0 dBm)
	* 5220 MHz [44] (18.0 dBm)
	* 5240 MHz [48] (18.0 dBm)

This should in theory make RaspAP's db obsolete.

I'll prototype a solution along these lines. Thanks for raising this.

@billz billz linked a pull request Nov 5, 2023 that will close this issue
@billz billz self-assigned this Nov 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants