Apple’s implementation of 802.11d is a real pain in the ass, indeed.
And setting the correct country code on the AP in use won’t solve the problem in some cases.
For example (at least for some older macbooks’s), if there are changes in country regulations, they are not updated in the drivers.
So if some channels were restricted to use in your country in the past, there is a big chance that you won’t be able to use them even if they are not restricted anymore.
The best workaround is to completely disable 802.11d on a device, but that needs kext modifications, and typically does’t survive apple’s security updates.
not a true statement, on all models since 2012, everything is fine with 802.11d. The AP must broadcast 802.11d. a piece of shit - tp-link even does it.
That’s right, I started using tp-link for this.
That is a known problem for pre-2012 devices.
Your “everything is fine with 802.11d” most likely means that apple no longer uses 802.11d at all, or at least uses something else in addition 
802.11d is a deprecated protocol.
And since 2015 it is forbidden for devices to set locale based solely on 802.11d.
It’s not a matter of language standard, but of channel distribution for each region. For this, Apple uses 802.11d. What is difficult to broadcast the region? Budget devices do it - tp-link, d-link
macbook pro 2019 15" core i9 - if it doesn’t see 802.11d, it’s a region. Takes from a neighboring network - who broadcasts it.
Thank you for informing us about your concerns regarding the issue.
Currently MikroTik has no plans of implementing 802.11d as it’s already not allowed to rely solely on 802.11d for setting country-specific radio parameters in USA since 2015, thus most of the phone, laptop etc. manufacturers most likely have made the changes in their drivers and/or software to obey the law (I highly doubt that they would split such change between models)
it is clear. In what standard then the region is now hung up? 802.11h? Why then is this happening with Apple? Are they so stubborn?
That is a misunderstanding! It is not allowed for USA certified equipment to interpret received countrycodes to extend capabilities beyond the USA allowed ones, as you already know you have to sell USA-specific hardware.
However, that is totally different from TRANSMITTING the countrycode in the beacons, which is of course still allowed, and apparently some clients have issues around that.
As I already said, now it’s forbidden to set region based only on 802.11d.
So apple MUST do it differently, than it did pre-2012. That is why it works fine in new devices, and still does’t work in the older ones.
Bottom line: devices CAN use 802.11d to help them set the region, but they CAN NOT use ONLY 802.11d, they need something else - gps, whatever.
Thus support of 802.11d is nearly useless - all modern devices will set the region without it.
no and no again. I have a mikrotik network. Regoin Apple can not determine, and sees a network nearby on tp-link and takes strange from it.
This is a very simple experiment! What gps? We are talking about a real example - MacBook Pro 2019 15 "
Then why have you disagreed with my original statement, that apple’s implementation of 802.11d is screwed?! 
I don’t need another evidence than my own: I have mikrotik network at home and if I do nothing my 2010 macbook takes region from nearby networks and since in the drivers it’s said that I can use 5Ghz only in 802.11a not in 802.11n in my region, I am not able to use 5Ghz networks on normal speed.
So I need to disable 802.11d at all.
My devices are indeed 2011 macbookpro’s, i have 13", 15" and 17". They work great, and is see many people that still prefer them over the new models with the bad keyboards. I dont expect Apple to change the way they work anymore as they are all vintage by now.
At the places I install wifi installations, eg schools, musea, resturants, i just limit the 5GHz channels to 36-48 now. So visitors don’t notice this issue.
The problem has just come up since a year or so when a large ISP in our country (Ziggo) is sending wifi routers with country-code eu to their customers. So it bothers me that Mikrotik don’t add this option as well. They could leave it off by default.
Thanks for the TP-link tip, they are realy cheap.
I cannot find a reference for this. Where to find?
This is for FCC only, as far as I know. And there is an exception (https://apps.fcc.gov/kdb/GetAttachment.html?id=5NjjaXsjV97%2BhlMWvZ1QRw%3D%3D&desc=594280%20D01%20Configuration%20Control%20v02r01&tracking_number=39498):
Country information derived from multiple adjacent access points (for example using IEEE Std 802.11d provisions) may be permitted on case-by-case basis.
Modern (by modern I mean few years old phones/devices) mostly do not really on the protocol but use other means to know it’s geo-location. We can always cherry pick “special” manufacturers/devices that simply use restrictions by their programmers/company opinion (like enforcing 802.11d always with no way to disable it, or enforcing WMM-Power save while the devices software shows that it should be disabled etc.)
Yes, I already stated that it’s only for USA market and meant for host devices that connect to the AP, but there is no use for an AP if there are no clients, so client restrictions have to be taken into consideration.
And you’re deliberately missing my point, I never said that the regulations are “TRANSMITTING” related
Will your arm break off to check? Set yourself the USA, or Latvia region, and next look at what you say from RU networks. No fool to turn on
Your answer says it all, you don’t need to. We need. People need it.
There is a saying - like it? then use for personal purposes for yourself.
macbook 2010 kek 
To check what?
Once again.
I have an old 2010 macbook pro, which is capable to use 802.11n @ 5Ghz
If region is FR or US or maybe something else, it works OK.
If region is set to RU - it works @5GHz only in 802.11a mode. Not OK.
Country regulations for RU changed, but that changes never made their way into the driver.
So I have two ways to overcome the issue:
- Set another region on AP - and possibly violate some country regulations.
- Disable 802.11d in macbook.
Tried multiple times. As a matter of fact - after every security update, because all modifications to the driver are removed and I need to redo them.
The problem is in the macbook, because it uses 802.11d in improper way, and no one cares to make the correct drivers for old devices.
I talked about this from the very beginning - re-read it. Only you have a special case in 2010. The new 802.11ac - restriction on visible channels. That is the problem.
- Here - that’s what I’m talking about. Mikrotik does not broadcast the region.
2.A crutch is not the right way. (Will you be able to fix the problem with your electric car at home? or give it to an authorized service ?!)
This is not an Apple issue. This is a problem for router manufacturers. Asus everything works, Tp-Link everything works. Cobminium everything works, Cisco everything works.
But Mikrotik does not want to do this.
PS
And one more thing: they seem to have problems with wave2, there is no region, and other devices stupidly do not see the network.
It’s not a special case, It’s a long known issue with a known workaround.
Although it’s not exactly the same problem, it is connected, and my original thesis was, that apple’s approach to 802.11d is a headache both for you and me.
For me the problem is, that Apple doesn’t upgrade region settings in old drivers and at the same time forces me to use 802.11d
So even if mikrotik implement 802.11d it won’t help me in any way.
For you the problem is that apple devices rely only on 802.11d to set the region ignoring the absence of any other info.
- Won’t help me.
- Apple can help me, but don’t want to. So the only way is to do it myself.