v7.11.2 [stable] is released!

Band: 5GHz AC
Channel Width: 20/40/80MHz
Frequency: 5320 (Under Radios, I see that 5320 is removed from the whole "Current channels" table when country "United States" or "Canada" is selected)

Before it was working as a DFS channel that was subject to radar scanning, which I was fine with. Now it can't be used at all, leaving me with basically no noise-free channels to use in current environment.. :confused:

After updating to 7.11.1, some devices like Xiaomi smart vacuum cleaner, underfloor heating sensors, etc. cannot connect to CAPsMAN. I keep seeing the following entry in the logs - rejected, requests wrong RSN group cipher.

What should I do to make everything work? I have Mikrotik 5009 and CAP XL access points

Check debug logs, see what is the error

Can you select channel 5300, @fragtion? That would make sense in case of 80MHz Ceee.
Can you please share your config:

/export file=anynameyoulike

Remove serial and any other private information like public IP.

Why? This is clearly related to the upgrade. 5320 is selectable on 7.11 but not 7.11.1. I downgraded to 7.11 and can now use the channel again until I purchase another wireless AP to replace the wi-fi on my RB4011.
So it's not config related, you could easily reproduce it on a similarly country-locked device. For the record I'm still on 7.11.1 routerboot firmware so this restriction is being applied on a npk level

If this is true:
https://en.wikipedia.org/wiki/List_of_WLAN_channels#5_GHz_(802.11a/h/n/ac/ax)
It is clear that you are not clear how things work.
You can not use 5320 with Ceee, but at least as single 20 channel, or eC at 20/40 or eeeC at 20/40/80, etc.

To check current settings and to give an explanation. You can provide only the wireless part.

I can’t use 5320 regardless of which channel width option is selected. The channel is no longer part of the selectable range for this regulatory domain on this device. And yes, this better conforms with the device description/specifications on MT website, for this locked down variant.

https://mikrotik.com/product/rb4011igs_5hacq2hnd_in:

RB4011iGS+5HacQ2HnD-IN-US (USA) is factory locked for 2412-2462MHz, 5170-5250MHz and 5725-5835MHz frequencies. This lock can not be removed.

I’m just saying, it was possible to use this frequency in prior wifiwave versions but was silently removed in 7.11.1, which is a real bummer. I thought they were maybe revising this since v7, which would have explained why the device was no longer so restricted. Evidently that is not the case..

Since MikroTik do not have TPC, now all frequences that must have TPC are forbidden on US market…
Those are FCC rules, not MikroTik choices.
If the rules of the State change, it is not MikroTik’s job to inform customers, it is assumed that they already know the law, which does not admit ignorance.

Yeah, except that I’m now using the device here in South Africa…

So the other question is why did you buy a device for the American market, and then you didn’t resell it when you moved to South Africa…

Unfortunately they are forced by the FCC that, if they want to sell in America, they must be so strict on the products…

That's an irrelevant and extraneous question (with all due respect). Besides for the fact that Mikrotik as a brand is generally not so popular in the US market, perhaps I did try to sell it and nobody showed interest especially when they read that I have the locked variant and they knew that it's possible to buy the international version even through vendors like Amazon if they really wanted to...

So yeah let's rather remain focused on the fact that the software has changed and that this change was not included in the changelog :wink:

If the rules of the State change, it is not MikroTik’s job to inform customers, it is assumed that they already know the law, which does not admit ignorance.

If you use a peripheral outside of how it was meant to be used, that’s your business.

So it's not MikroTik's business/duty to inform customers of a software change correcting regulatory channel enforcement? I'll wait for your infinite insight in answering this question then

7.11 comparing to 7.10 has some issues with Wi-Fi signal strength on Chateau.

Hi normis,

Could you check my report regarding vpls defragment problem?
http://forum.mikrotik.com/t/vpls-mtu-problem-on-v7-7-9beta4/165519/8
It’s happen in v7

Thx

I don’t see any errors in the debug logs or look at them incorrectly. For many years of operation of your equipment, such problems have not arisen, but now I don’t even know how to find a problem, please help me with a solution.

It seems that there have been some changes with the wireless interface, as a result of which some devices have stopped connecting. Even if you disable the access point from capsman and configure wi-fi on it separately, still not all devices can connect to it.

SUP-114337 is still not fixed even in 7.11.1 “stable”

I still cannot turn Ipv6 HW acceleration on at L3HW - this case has been open since April / ROS 7.8 on my CCR2216.

People… bugs and features that are not mentioned in the release notes are most likely not fixed. No need to refer to that after a new stable release.
When you want to mention it at all (probably useless), do so in the 7.12beta topic.

After rolling back the capsman controller to version 7.11, the problem was solved. Access points themselves on version 7.11.1