Are the DFS Regulations for India up to date?

Sorry but I don't have much understanding of the RF Regulations. I wish to use certain bands for my WiFi at home, but don't want to break any rules. The OpenWrt Wiki says that as long as I select the appropriate country code, I should be fine.

Certain bands in the 5Ghz spectrum are specified to have a mandatory DFS/TPC Rule, according to these links (Wikipedia and a circular of gov of India)

https://en.wikipedia.org/wiki/List_of_WLAN_channels#cite_note-N100990-50 (Wiki)
https://blog.gauravkansal.in/2021/12/availability-and-info-of-wlan-channels.html (Blog)
https://dot.gov.in/sites/default/files/License%20Exemption%20in%205%20GHz%20G_S_R_1048(E)%20dated%2022nd%20October%2C%202018_0.pdf (Gov. Of India)

but when run "iw reg get"
I get the following output:

global
country IN: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 30), (N/A)
(5250 - 5350 @ 80), (N/A, 24), (N/A)
(5470 - 5725 @ 160), (N/A, 24), (N/A)
(5725 - 5875 @ 80), (N/A, 30), (N/A)

but according to the reference I stated before 5,250-5,350 MHz and 5,470-5,725 MHz bands have mandatory DFS/TPC.
Here is the precise statement:

The use of appropriate interference mitigation technique dynamic frequency selection and or transmit power control shall be mandatory.
Transmit power control mechanism may not be required for systems with an e.i.r.p. of less than 500 mW.

What should one interpret from the above data?
"and or" means at least one of DFS, TPC must be implemented.
But the second statement states if e.i.r.p. is less than 500mW then TPC is not required.
Does this imply that when you have e.i.r.p less than 500mW you need to implement DFS or you are free from any restrictions? OpenWrt seems to think so, I just want to make sure I am not breaking any rules.

Thank you for your time! :slight_smile:

1 Like

OpenWrt is not the maintainer of that information.
https://wireless.wiki.kernel.org/en/developers/regulatory/wireless-regdb#sending_updates_to_the_regulatory_database
But yes it seems wrong for IN.

2 Likes

I think this has been fixed in wireless-regdb git https://git.kernel.org/pub/scm/linux/kernel/git/wens/wireless-regdb.git/commit/?id=e78c450c08b73b6b291f0770313c97a85d4c865a that is part of
wireless-regdb-master-2023-05-03.tar.gz
stable release.