Hello,

Does anyone here know how to make mikrotik wireless devices broadcast country code? I have tried "/interface wireless wlan2 country=netherlands" but my macbook still does not receive a country code from my cap ac, tried wap ac and hap ac as well.
I did a wireless scan with wifi explorer and every device in my street is broadcasting country code, about 50% NL and other 50% EU. One of them that is broadcasting "EU" has a very powerful signal so my macbook chooses EU for country code and disables all 5GHz chanels except 36, 40, 44 and 48 which are of course the chanels all used by that other router. When I set my my accesspoint to use any of these chanels the transfer speed is bad. When I set e.g. chanel 60 I get very good transfer speeds but I must first power on and connect to my old airport express to trick my laptop into country code NL and then reconnect to the Mikrotik

Wait. It should not matter what the other AP devices are doing. Just set a specific frequency in your MikroTik device and use a unique SSID.

I noticed this behavior too ...
MT devices (like my RB962's) do not transmit a country code.

But, not all do
Some DO, like FritzBox from AVM, Some Samsung device, Some Arcadyan device, Some Ziggo devices (transmit EU)
Some DON'T, Like MT, ZTE devices, Belkin devices, TP-Link devices, Sitecom devices

AND Yes, IF my MacBook gets connected to an AP that is transmitting a countrycode, it seems to adjust some config, not sure exactly what ..
(using Wifi Explorer in OSX to scan)

I know it does that, but even if it does, why wouldn't it connect to a MikroTik device that has a statically set frequency?

Since many AccessPoints have it and some devices are dependent on it, it maybe worth a feature request.

Mikrotik please add 802.11d support in ROS. It would be great to have country-code and allowed-rf-power in the beacon. Of course there should be an option to disable one or both. Also it would be great to manually override default values. Good example is for europe. Choice of "EU" or national country code like "NL", "DE".

I understand the request, but can you clarify the reason? Like I said already, code doesn't matter

One case: I was running my WiFi 2.4GHz (802.11n) set to channel 13 which is completely legal in my whereabouts. When my better half received a brand new phone LG G4, it wouldn't pick up the signal ... as if it wasn't scanning for it on channel 13. After I inserted SIM card, the mobile configured self and it started to see the AP.

I know it is ridiculous for a WiFi client device to impose any kind of restrictions, however growing number of devices are capable of becoming APs themselves (think WiFi tethering) and in that case they have to follow regulations. If exact location (whatever method of obtaining it) is not known, it is understandable that device runs in a "fail safe" mode, not using any functionality (wireless channel, Tx power) that might be restricted in any part of the World. Device can find out its whereabouts using different methods, including (but not limited to): GPS positioning, MNO decoding and WiFi SSID locating ... for devices without GPS (or without GPS fix) and with no mobile connection (either device doesn't support it or it's not available), WiFi country code broadcast might be a "life saver".

So it's not only about what Mikrotik developers / product managers think is sensible (we, WiFi operators, might completely agree with MT's view), it's also about how client devices behave.

Yes, but your example has nothing to do with the transmitted country code. The phone has a built-in scan list, it wouldn't use channel 13 in certain regions, regardless of what the AP is transmitting as the country code in it's beacons.

Yes, but your example has nothing to do with the transmitted country code. The phone has a built-in scan list, it wouldn't use channel 13 in certain regions, regardless of what the AP is transmitting as the country code in it's beacons.

Again: phone needs something to figure out the region of current existence. If nothing else is available, CC emitted in beacons by AP would help.

My problem is with my Laptop, at work our wifi is broadcasting Country Code 'NL'
Systemprofiler shows: Supported channels: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 36, 40, 44, 48, 52, 56, 60, 64, 100, 104, 108, 112, 116, 120, 124, 128, 132, 136, 140
So I can connect to company wifi wich is at channel 100 without problem

Then I return home, I can see my own Wifi in the airport menu, I know it is configured at channel 60, but connect fails and the I look again in System profiler, i see Country Code 'EU' and Supported channels: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 36, 40, 44, 48 Rest is gone. So I assume that this is caused by lack of this code.
Mikrotik allows me to change every setting and more. But country code is just not there, while it is on most other routers.

Normis, so what about 802.11d? I have to drive idle next to tp-link to shake the correct country code.

The issue apparently is that some client devices look at what other APs are transmitting to then lock their settings to the country code they receive there, instead of first looking for the correct SSID and then connecting there without country code (and thus no locked settings).
This may be related to some other behavior I see from some devices: to connect to EVERY AP that they see to try if they get admitted there and to freeride on the internet if they do.
But, also causing loggings of breakin attempt including their MAC address in case the attempt fails. The users probably don't know that!

You could see if this method of working is somehow configurable in your device. When you turn it off, the bad behavior of using other people's country code could be gone as well.

The issue apparently is that some client devices look at what other APs are transmitting to then lock their settings to the country code they receive there, instead of first looking for the correct SSID and then connecting there without country code (and thus no locked settings).
This may be related to some other behavior I see from some devices: to connect to EVERY AP that they see to try if they get admitted there and to freeride on the internet if they do.
But, also causing loggings of breakin attempt including their MAC address in case the attempt fails. The users probably don't know that!

You could see if this method of working is somehow configurable in your device. When you turn it off, the bad behavior of using other people's country code could be gone as well.

Hello, no, it’s completely wrong. MacOs wants to see the code country from the AP, over 802.11d. if it does not receive it, it takes the first one who broadcasts from neighboring ones.

As an example, AirPort Extreme translates the country code over 802.11d.

Time to transmit the country code of a country that does not allow WiFi! Fun...

Time to transmit the country code of a country that does not allow WiFi! Fun...

?

Well I think it is pretty broken to listen to what other people's devices (you have no control over) transmit and take it as authoritative.
But it is probably required by law in the USA.

But main issue here is that without 802.11d you get problems with some devices to connect.
And it can't be fixed in any other way, you can't just tell your clients to buy different notebook or phone.
Good luck explaining to your boss why he can't connect to your WIFI with his macbook...
11d is standardized, adds just a few bytes to beacon and solves the problem... so why it's not supported already?

But main issue here is that without 802.11d you get problems with some devices to connect.
And it can't be fixed in any other way, you can't just tell your clients to buy different notebook or phone.
Good luck explaining to your boss why he can't connect to your WIFI with his macbook...
11d is standardized, adds just a few bytes to beacon and solves the problem... so why it's not supported already?

Normis, Reinis
what about 802.11d?

I now have a workaround that seems to work most of the time: plug in an old apple airport basestation, set up with a not-used SSID and on different channels to prevent performance decrease of your regular network. Most important: set the desired country code. unplug the basestation from your network if necessary and place it not too far away from your devices.

Now when you start or wake a device it will see the apple station with correct country code. and your device will have none problem connecting to your own wireless network even if it is MT that lacks 802.11d itself, maybe they read this too and feel ashamed ?

Turns out these Apple aiport devices weren't that bad after all. Especialy the latest extreme 'towers' delivered pretty high speed as well.

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.

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.

I now have a workaround that seems to work most of the time: plug in an old apple airport basestation, set up with a not-used SSID and on different channels to prevent performance decrease of your regular network. Most important: set the desired country code. unplug the basestation from your network if necessary and place it not too far away from your devices.

Now when you start or wake a device it will see the apple station with correct country code. and your device will have none problem connecting to your own wireless network even if it is MT that lacks 802.11d itself, maybe they read this too and feel ashamed ?

Turns out these Apple aiport devices weren't that bad after all. Especialy the latest extreme 'towers' delivered pretty high speed as well.

That's right, I started using tp-link for this.

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 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.

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 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)

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?

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)

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.

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 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.

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.

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 "

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?!

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 "

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.

802.11d is a deprecated protocol.

I cannot find a reference for this. Where to find?

And since 2015 it is forbidden for devices to set locale based solely on 802.11d.

This is for FCC only, as far as I know. And there is an exception (https://apps.fcc.gov/kdb/GetAttachment. ... mber=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.

I cannot find a reference for this. Where to find?

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.)

This is for FCC only, as far as I know. And there is an exception (https://apps.fcc.gov/kdb/GetAttachment. ... mber=39498):

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.

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.

And you're deliberately missing my point, I never said that the regulations are "TRANSMITTING" related

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?!

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

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 "

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.

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

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?!

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

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:
1) Set another region on AP - and possibly violate some country regulations.
2) 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.

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.

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.

So I have two ways to overcome the issue:
1) Set another region on AP - and possibly violate some country regulations.
2) Disable 802.11d in macbook.

1. 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 ?!)

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.

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.

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.

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.

1. 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 ?!)

1. Won't help me.
2. Apple can help me, but don't want to. So the only way is to do it myself.

1. Here - that's what I’m talking about. Mikrotik does not broadcast the region.

I've already provided the current situation ON the matter: "Currently MikroTik has no plans of implementing 802.11d"

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.

You are blaming router manufacturers for not implementing a protocol that is rarely used on any device newer than nearly 10 years, which also is an "optional" protocol? Where the issues arise only if the HOST manufacturer forces to use the mentioned protocol and does not give an option to disable it, am I understanding your statement correctly?
Note, that issue can only arise if the nearby AP's have wrong country settings and the whole process is fully done on the HOST device side

And one more thing: they seem to have problems with wave2, there is no region, and other devices stupidly do not see the network.

There are no problems with wave2 as calling "feature that has not been yet added" a problem is also deliberately false statement. And regarding the country/region, it's controlled on HOST device side, not AP

I've already provided the current situation ON the matter: "Currently MikroTik has no plans of implementing 802.11d"

This was clear from your first answer. But still we would like to see support. There are many situations where miracles begin because of this. And in the end, the customer does not choose your equipment - and we have nothing to argue.

You are blaming router manufacturers for not implementing a protocol that is rarely used on any device newer than nearly 10 years, which also is an "optional" protocol? Where the issues arise only if the HOST manufacturer forces to use the mentioned protocol and does not give an option to disable it, am I understanding your statement correctly?
Note, that issue can only arise if the nearby AP's have wrong country settings and the whole process is fully done on the HOST device side

No, we do not blame you, you misinterpreted. The whole debate lies in the need for support - you said that you will not. Ok.
We can’t go in and breaks into a building where the wrong region is being broadcast and demand correction. The police will be called: D

There are no problems with wave2 as calling "feature that has not been yet added" a problem is also deliberately false statement. And regarding the country/region, it's controlled on HOST device side, not AP

I understood you.

This was clear from your first answer. But still we would like to see support. There are many situations where miracles begin because of this. And in the end, the customer does not choose your equipment - and we have nothing to argue.

We understand the request and of course, if possible, we would support every possible customer desire, but the world isn't perfect and resources are not infinite.
The protocol has been added to the "TODO" list, but I cannot comment on the ETA of it.

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.

My personal headache was using Mikrotik at home. All other manufacturers have no problem with this situation. Regarding 802.11d.
They do not realize, was Reinis's answer. And if implemented, it will help. Checked.

For you the problem is that apple devices rely only on 802.11d to set the region ignoring the absence of any other info.

If there is no other information. You have to broadcast the region for Mikrotik with another device.

Since many AccessPoints have it and some devices are dependent on it, it maybe worth a feature request.

Mikrotik please add 802.11d support in ROS. It would be great to have country-code and allowed-rf-power in the beacon. Of course there should be an option to disable one or both. Also it would be great to manually override default values. Good example is for europe. Choice of "EU" or national country code like "NL", "DE".

In addition, it would be great (for debugging purposes of course) to choose country-code independent from set regulatory-domain country (e.g. for superchannel).

This was clear from your first answer. But still we would like to see support. There are many situations where miracles begin because of this. And in the end, the customer does not choose your equipment - and we have nothing to argue.

We understand the request and of course, if possible, we would support every possible customer desire, but the world isn't perfect and resources are not infinite.
The protocol has been added to the "TODO" list, but I cannot comment on the ETA of it.

Thank you so much Reinis !!!!

If there is no other information. You have to broadcast the region for Mikrotik with another device.

Smartphones and other mobile devices have GPS, they don't need 802.11d at all.

Out of curiosity looked what regions do APs around broadcast at the moment, only half of them are set to the correct region, the rest do not broadcast region at all or broadcast wrong region.
The whole concept to rely on 3rd party APs to set your own region, if your own AP doesn't specify one, without an option to manually override it is ridiculous!
If some router nearby is violating local regulations you may find yourself doing the same involuntarily.

Smartphones and other mobile devices have GPS, they don't need 802.11d at all.

That's right, but all the rest of the equipment is needed.

Out of curiosity looked what regions do APs around broadcast at the moment, only half of them are set to the correct region, the rest do not broadcast region at all or broadcast wrong region.
The whole concept to rely on 3rd party APs to set your own region, if your own AP doesn't specify one, without an option to manually override it is ridiculous!
If some router nearby is violating local regulations you may find yourself doing the same involuntarily.

There are different situations. As an example, a foreign representative office, where there are many visitors and workers from other countries. And they configure their access points for their region. Corporate requirement.

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.

And you're deliberately missing my point, I never said that the regulations are "TRANSMITTING" related

It seems you are not getting that what people request here is implementation of 802.11d for TRANSMIT (some fields in the beacon), NOT implementing the 802.11d protocol to make the router (when used as a WiFi client) respect the 802.11d protocol as sent by other routers.
This is only to tell some (broken? old?) equipment what is your country code, because when you do not do that they act upon country codes sent by other routers (broken! but it won't be fixed).

In general when working on software that interworks with other software, like a WiFi router and clients, it is always easy to point to the others and say "it is your side that is broken" but in many situations it is easy to work around that in the own software and not so easy to get others to fix their things.

Smartphones and other mobile devices have GPS, they don't need 802.11d at all.

That's right, but all the rest of the equipment is needed.

The rest of the equipment should use something like "no-country-set" or ask the user, if it can't locate it's position with 100% accuracy.

Out of curiosity looked what regions do APs around broadcast at the moment, only half of them are set to the correct region, the rest do not broadcast region at all or broadcast wrong region.
The whole concept to rely on 3rd party APs to set your own region, if your own AP doesn't specify one, without an option to manually override it is ridiculous!
If some router nearby is violating local regulations you may find yourself doing the same involuntarily.

There are different situations. As an example, a foreign representative office, where there are many visitors and workers from other countries. And they configure their access points for their region. Corporate requirement.

You understand that technically it can be illegal, right?
Using settings for your region in other country just because it better suits you?
And with 802.11d you can find yourself using illegal settings in your own country just because you are near some foreign congress with a lot of people who don't care about local laws.

Please stop posting about what can happen when you interpret 802.11d country codes sent by others and focus on the request to send the 802.11d country code in a MikroTik AP so that others (broken, old, whatever) can pick it up and do whatever they were programmed to do with it!

Please stop posting about what can happen when you interpret 802.11d country codes sent by others and focus on the request to send the 802.11d country code in a MikroTik AP so that others (broken, old, whatever) can pick it up and do whatever they were programmed to do with it!

I am totally with you on this matter: 802.11d is at least useless and at most harmful protocol (maybe not by itself, but in the way other manufacturers treat it), and it should not be implemented, especially having in mind that the same time can be spent to implement some new/useful/long awaited things instead.

The rest of the equipment should use something like "no-country-set" or ask the user, if it can't locate it's position with 100% accuracy.

You understand that technically it can be illegal, right?
Using settings for your region in other country just because it better suits you?
And with 802.11d you can find yourself using illegal settings in your own country just because you are near some foreign congress with a lot of people who don't care about local laws.

Laws apply to access points by radiation exposure. Everything below a certain power, each country has its own standards, is individual. I already wrote above, try to prove that the established region is bothering you, the police will be poisoned you as a hindrance to privacy.

Thank you all for participating in this discussion. As I understand 802.11d support is now on the todo list for mikrotik and for the time being we can work around the issue by using some other equipment just to send out the desired country code.

And when the country code setting is made available, im am sure it can be disabled if it is not needed or wanted. Maybe because you only have devices that are not doing anything with that information at all, or you don't have neigbors' routers that are transmitting unexpected or incorrect country codes and you can't do anything to prevent them from doing so. In which case you are just lucky i guess.

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.

I made my account just to ask this. I do not even use Mikrotik device but this is the only solution I have seen mentioned all over the internet, but I cannot find anywhere how to actually do it, so I'm taking a shot hoping you are able to help me.

I am using a mid 2012 MacBook Pro that also has 802.11d related issues. Its extremely slow wifi and reporting a country code of X3 where as all my other Macs, and other devices for that matter, are working perfectly and are reporting a country code of EU (which is where I am located so that makes sense). My research has told me that the issue lies somewhere in the 802.11d country code problem. However, I can not find anywhere how to disable this 802.11d stuff on my device. I have used kexts before, running a hackintosh in fact, so im sure I can figure that out, but I just can't find anywhere how to disable the 802.11d stuff. Is there any chance you would be willing to help me?

ISSUE on MacOS :
WIFI 5 ghz disappearing / Country Codes Conflicts

ISSUE FIXED !!!

the problem come from the implementation of 802.11d : wifi location and country ID conflicts.
if there are different wifi Access points broadcasting mixed countries ID, Mac OS may shut down certain frequencies.

Solution at the end of the post :)))

Just after a restart my MacBook Pro 16 is set to locale ETSi and country code X3
All channels and frequencies are opened.

If i stop and restart the wifi, or the Mac goes in power save mode and turn off the radios.
When it wakes up i got this: Country code ID, and most of the supported channels are gone.

There's a lot of posts about this on the internet, about either adding another AP and setting county code.
Some APs (like mikrotik don't broadcast country codes)
Some posts are about modifying the wifi drivers.

Don't do any of that, the solution is quite simple !!!

I'm now on MacOS 11.0.1 Big Sur.
But i assume the solution is the same on previous MacOS Versions

Go to:
--> Apple Menu
--> system preferences
--> Security & Privacy
--> Location Services
--> Scroll down till you find System devices
--> Click on Details...
--> UNCHECK WiFi Networking

This will bypass 802.11d implementation and 5ghz will show up right away

ISSUE FIXED !!!

I'm now on MacOS 11.0.1 Big Sur.
But i assume the solution is the same on previous MacOS Versions

Nope.
Broadcom 4331 still needs kext modification on High Sierra.

So perhaps this is true only for some of wireless chips, or only for 11.0.1.

I want to ask a question related to the issues posted on this thread
I have a deployment of Mikrotik AP's on 5GHz that need to support the operation of some WiFi VoIP phones.
The phones are Spectralink 8440, and they have a restriction on operating on 5GHz DFS channels. According to the deployment guide if you want to use the DFS channels then the AP must support 802.11h - Channel Announcement feature. If this is not broadcast in the beacon, then the phone will refuse to join with the AP. And this is exactly what is happening with my deployment. The phones see the AP's, but will not connect.
If I change channels to the non DFS portion, then they work with no problem.
Using these channels however is not a option because the spectrum is very crowded in that region (at least 6-7 overlapping wlans.... - i guess everyone wants to avoid the DFS potential problems), and the deployment is covering some exterior areas as well. I tried all possibilities to no avail. I used regulatory-domain with the proper country code, frequency auto and 20MHz channels, and scan list adjusted to use only the DFS part of the band.
All other devices connect perfectly, everything works, except for the phones....
If there is one setting I missed, maybe someone has an idea and rescues me If not, maybe Mikrotik can add this feature in a future update, apparently it is needed on some deployments.

Thank you everyone

I know it does that, but even if it does, why wouldn't it connect to a MikroTik device that has a statically set frequency?

I have fallen into this hole with more than one site. When MacBook laptops were opened and first saw beacons from access points with misconfigured country code (default US in multiple cases) in a neighbouring office, they limited their scan frequencies to the US, so didn't see the APs on channels on the actual country, breaking the network. Mikrotik APs were nearer, but don't broadcast any country code.

Ultimately, had to workaround it by using more congested US-only channels. I vote for adding the 802.11d country code Information Element; it's a low-complexity improvement which improves robustness, especially as the 5GHz spectrum is getting more congested.

I know it does that, but even if it does, why wouldn't it connect to a MikroTik device that has a statically set frequency?

I have fallen into this hole with more than one site. When MacBook laptops were opened and first saw beacons from access points with misconfigured country code (default US in multiple cases) in a neighbouring office, they limited their scan frequencies to the US, so didn't see the APs on channels on the actual country, breaking the network.

While it would be nice if Mikrotik supported more of 802.11 standards (including d) IMO those clients are brain dead. Why should clients care which country they are operating in? If APs are configured the way they are, clients should just follow (if they're techincally able to). The only time usual PCs, smart phones and tablets need to know country they-re in is when acting as (ad-hoc) APs and they're welcome to operate in wahtever fail-safe (or fool-proof) mode they choose.

That behavior is probably directed by either misunderstanding the legal requirements, or having had an incorrect comment from a legislator who did not understand it.
Of course the frequency of a client should be determined by that of the access point. The client is not supposed to transmit until it hears the access point.
But likely someone has said "you are supposed to use only these channels" (e.g. NOT use channel 13 in the US) and the manufacturer chose to abide by it rather than entering an endless discussion and risk problems.