LinuxQuestions.org - Hi All, I am new in Linux

From https://wireless.wiki.kernel.org/en/...ulatory_domain

Quote:

EEPROM world regulatory domain

Atheros EEPROM can use 12 custom world regulatory domains:

WOR0_WORLD = 0x60
WOR1_WORLD = 0x61
WOR2_WORLD = 0x62
WOR3_WORLD = 0x63
WOR4_WORLD = 0x64
WOR5_ETSIC = 0x65
WOR01_WORLD = 0x66
WOR02_WORLD = 0x67
EU1_WORLD = 0x68
WOR9_WORLD = 0x69
WORA_WORLD = 0x6A
WORC_WORLD = 0x6C 0x60, 0x61, 0x62, 0x66, 0x67, 0x68 are only used today moving forward for 2.4 GHz-only band cards.

5 GHz with world regulatory domain and beacon hints

All Atheros custom world regulatory domains have all 5 GHz channels marked with a passive scan flags. The non-DFS channels can have their passive scan flags lifted through a feature implemented in cfg80211 called beacon hints. For details on that please read the beacon hints documentation.

From https://wireless.wiki.kernel.org/en/...ocessing_rules

Quote:

Beacon hints

cfg80211 has a feature called beacon hinting to assist cfg80211 in allowing a card to lift passive-scan and no-beaconing flags. Passive-scan flags are used on channels to ensure that an interface will not issue a probe request out. The no-ir flag exists to allow regulatory domain definitions to disallow a device from initiating radiation of any kind and that includes using beacons, so for example AP/IBSS/Mesh/GO interfaces would not be able to initiate communication on these channels unless the channel does not have this flag. If either of these flags are present on a channel a device is prohibited from initiating communication on cfg80211.

Old regulatory rule flags like passive-scan and no-beaconing were originally invented to help with World Roaming, these two are now combined into the one and only no-ir, for no-initiating-radiation. If you do not know what country you are in you can still behave as an 802.11 STA interface but can wait to enable active scans until you see a beacon from an AP, if the channel being used is not a DFS channel and not channels 12-14 on the 2.4 GHz band. The same can be said for initiating communication, so both the old passive-scan and no-beaconing, now consolidated in modern kernels as one flag no-ir can be lifted if an AP is found beaconing on a non-DFS channel and if the channel is also not channels 12-14 on the 2.4 GHz band. cfg80211 takes advantage of this bit of logic to lift both of these flags if and only if the wiphy device is world roaming.

It is also important to note that the Linux kernel beacon hint mechanism only trusts beacons from 802.11 APs, not Mesh or IBSS. Specifically, the Linux kernel beacon hint mechanism ensures that the beacon ESS capability is set:

As I read the above, your device should not be using 5GHz channels unless there is an AP beaconing the availability of a 5GHz channel.