Guess the main problem is that setting it JP doesn't make it hit all the channels. It DOES for 2.4ghz but really screws up 5ghz. For example makes it impossible for radio to associated with 5ghz channel numbers 149,151,153,155,157,159,161,165 in the U.S. because 5735->5835 is not allowed in japan. Also kills channel 138 (5650–5730) and channel 142(5690–5730) because in Japan it only goes up to 5710 not 5730.KE7FNS wrote: ↑Fri Dec 06, 2019 2:35 am
I expressed my thoughts on that a while ago, Andy replied that he did it on purpose to scan for every possible network.
viewtopic.php?f=3&t=1915&hilit=country% ... t=10#p8879
I find it very annoying that it constantly forces JP no matter what setting you put in there. I just no longer use the wifi configuration area of the dashboard at all, it seems that whenever you click save, it completely erases all of your prior network settings and sets the country to JP for you.
I also have backups of my wpa_supplicant just incase the dashboard decides to nuke my custom settings for me again.
In Europe it the country=JP settings kills 5ghz Channels 32, 34, 68,96,138,142, and 149 through 173.
Country code 00 (Default when not set) is what is supposed to be used to look for all channels on all bands. As having a 00 crda code makes radio passively listen for access point beacons on all frequencies, then when it associates with something it should take it's country code from the AP it associates with.
Setting correct country code speeds up associations, because it allows radio to actively check for access points and not wait for a beacon. But having the wrong code will keep radio from associating at all on many channels.
Should really be setting correct country code in /etc/default/crda and not in WPA supplicant as it effects modules when they load not just when supplicant starts.