Regulatory domain settings versus. iw reg get

Installing and Using OpenWrt Network and Wireless Configuration
1

Hello Forum Members,

i changed the regulatory domain to DE via the Wireless Network Device Configurations "Advanced Settings" tab. This propagates into the radio0 and radio1 section of /etc/config/wireless as expected. But when i do a "iw reg get" on the command line i see, that only in the "global" part of the output the country has changed. phy#0 and phy#1 are still in the default US. However, i am able to configure working channels successfully that are allowed in DE and are not allowed in US.

Is this just a cosmetic issue, a problem of my hardware or plain pebcac? I am running LEDE Reboot 17.01.2 r3435-65eec8bd5f / LuCI lede-17.01 branch (git-17.163.57307-c79bb96) on a TP-Link TL-WDR4300 v1.

Thanks for your time.

2

Hello @Gebuesch

I have the same Problem with an ath10k device (WLE900VX 7AA). I set the regulatory domain to DE, but the output from

iw reg get

is

global
country DE: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 27), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 14), (N/A)
(57000 - 66000 @ 2160), (N/A, 40), (N/A)

phy#0
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)

And i still can select the not allowed channels in germany.
Did you made any progress on this issue?
I do not know what this two section mean. I only knowe the global section

Kind regards
Flo

3

Just curious:

  • Why are you using iw instead of the OpenWrt UCI (command line or LuCI)?
  • Also, what happens when you set the REG domain on the phy, in addition to global?
4

I want to check if LuCI do everything correct. OpenWrt will use in the end

iw reg set

as well

I can only set the reg domain of the global section.

I should change my question.
Why is the reg domain difference for phy domain and global domain?
Is this OK or is there a problem?
What is the sense of this?

5

Have you tried 18.06-SNAPSHOT?

Not sure, I'm unable to reproduce the issue you're experiencing on my routers.

root@OpenWrt:~# iw reg get
global
country US: DFS-FCC
	(2402 - 2472 @ 40), (N/A, 30), (N/A)
	(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
	(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
	(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
	(5735 - 5835 @ 80), (N/A, 30), (N/A)
	(57240 - 63720 @ 2160), (N/A, 40), (N/A)

root@OpenWrt:~# iw phy phy0 reg get
global
country US: DFS-FCC
	(2402 - 2472 @ 40), (N/A, 30), (N/A)
	(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
	(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
	(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
	(5735 - 5835 @ 80), (N/A, 30), (N/A)
	(57240 - 63720 @ 2160), (N/A, 40), (N/A)
6

@lleachii
On your output there is not phy#0 identifier so i think you have no dedicated phy#0 config.
I think this is hardware specific.
And so you will see no difference.
I am using a ath10k device and i will have a global and a dedicated phy#0 domain section.

If you have more phy´s frontends (wlan hardware device) in the system you will get for every phy a new regdomain phy#X section on the output with iw reg get

7

On another device:

root@OpenWrt:~# iw reg get
global
country US: DFS-FCC
	(2402 - 2472 @ 40), (N/A, 30), (N/A)
	(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
	(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
	(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
	(5735 - 5835 @ 80), (N/A, 30), (N/A)
	(57240 - 63720 @ 2160), (N/A, 40), (N/A)

phy#1
country US: DFS-FCC
	(2402 - 2472 @ 40), (N/A, 30), (N/A)
	(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
	(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
	(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
	(5735 - 5835 @ 80), (N/A, 30), (N/A)
	(57240 - 63720 @ 2160), (N/A, 40), (N/A)

phy#0
country US: DFS-FCC
	(2402 - 2472 @ 40), (N/A, 30), (N/A)
	(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
	(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
	(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
	(5735 - 5835 @ 80), (N/A, 30), (N/A)
	(57240 - 63720 @ 2160), (N/A, 40), (N/A)

I'll do more testing to see if I can reproduce your issue.

8

Problem exists in a device with an Atheros AR9344 and Atheros AR9380 (Western Digital My Net N750).

root@OpenWrt:~# iw reg get
global
country DE: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 13), (N/A)
(57000 - 66000 @ 2160), (N/A, 40), (N/A)

phy#1
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)

phy#0
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)

I reproduced this by setting my 2.4 band to DE (Germany).

9

I am not sure if this is a failure?
The WLAN is working as expected but it is strange.

10

The released builds are compiled with CONFIG_ATH_USER_REGD=n

11

You saw this decision -->