Are there any Wi-Fi compatibility issues with MikroTik?

RouterOS Wireless Networking
1

The Xiaomi Smart Plug 2 Wi-Fi outlets can’t connect to wifi-qcom-ac. The client connects, then disconnects after a couple of seconds, and this repeats endlessly. The client authenticates, and I can even ping it sometimes, but it disconnects almost immediately. Signal power -55.

For testing, I set up an old access point on a hAP ac², and the Xiaomi Smart Plug 2 connects to it without any problems. These plugs work with all kinds of Wi-Fi access points, even cheap ones, but stubbornly refuse to work when using wifi-qcom-ac.

2

tough to say without your actual Wi-Fi config from the Mikrotik, But you should check what frequency band and encryption you are running and whether your Xiomi device supports it.

3
4

As i noticed before client support . Same settings but without using wifi-qcom-ac works well. IT is nothing special in config. Almost all default :

/interface wifi channel
add band=2ghz-n disabled=no name=2Ghz width=20/40mhz-Ce
add disabled=no name=5Ghz
/interface wifi datapath
add bridge=brCeV1 client-isolation=yes disabled=no name=datapath1
/interface wifi security
add authentication-types=wpa2-psk,wpa3-psk disable-pmkid=yes disabled=no ft=yes group-encryption=ccmp name=Net2
/interface wifi steering
add 2g-probe-delay=yes disabled=no name=steering1 neighbor-group=dynamic-SSS-2f9eea5b rrm=yes wnm=yes
/interface wifi configuration
add channel=2Ghz country=Ukraine datapath=datapath1 disabled=no interworking.realms-raw="" mode=ap name=Net_2Ghz security=Net2 ssid=SSS steering=steering1
add country=Ukraine datapath=datapath1 disabled=no interworking.realms-raw="" mode=ap name=Net_5Ghz security=Net2 ssid=SSS steering=steering1
/interface wifi access-list
add action=accept client-isolation=yes disabled=no interface=any
/interface wifi capsman
set ca-certificate=auto enabled=yes interfaces=brCeV1 package-path="" require-peer-certificate=no upgrade-policy=none
/interface wifi provisioning
add action=create-dynamic-enabled disabled=no master-configuration=Net_2Ghz name-format=cap2-wifi supported-bands=2ghz-n
add action=create-dynamic-enabled disabled=no master-configuration=Net_5Ghz name-format=cap5-wifi supported-bands=5ghz-ac

5

Thanks . it started to work with management protection disabled. But now do not work wpa3.

6

Welcome.

7

That's normal.
Quite a bit of "smart devices" (but actually they're stupid) are not able to use more advanced wifi settings.

Best to create a separate SSID where you only use these devices on with minimal needed wifi settings so they do not pose an added risk for the rest of your network.

8

Make sure to remove this (can be done from cli):

/interface wifi configuration
unset value-name=interworking.realms-raw [find]

Why did you set

disable-pmkid=yes

From the documentation:

For interfaces in AP mode, disables inclusion of a PMKID in EAPOL frames. Disabling PMKID can cause compatibility issues with client devices that make use of it.

  • yes - Do not include PMKID in EAPOL frames.
  • no - include PMKID in EAPOL frames.

Indeed...disabling management protection disables wpa3 as well...sure you need wpa3?

IOS 26 and Mikrotik 7.22.x Wifi - bad relationship?
9

To give context to the above:
After RouterOS version 7.22, CAPsMAN causes only iPhones (iOS) to be unable to connect to Wi-Fi
After RouterOS version 7.22, CAPsMAN causes only iPhones (iOS) to be unable to connect to Wi-Fi - #5 by jaclaz

10

It is astonishing how many people already got affected by that WinBox bug. But MikroTik seems not to care much about it. At least they are silent.

1 Like
11

For wifi-qcom w/ WPA2-PSK/WPA3-PSK and 802.11k/r/v I’m currenty using the following config. So far with no issues.

/interface wifi security
add authentication-types=wpa2-psk,wpa3-psk disable-pmkid=yes disabled=no ft=yes ft-over-ds=no management-protection=allowed name=sec1 wps=disable
/interface wifi steering
add disabled=no name=steering1 rrm=yes wnm=yes

Your mileage might vary with wifi-qcom-ac.

12

They replied to one of my tickets with that fix.

13

Mildly interesting :slight_smile:

There should be a) an official fix for the WinBox 3.x bug causing this and b) an apology by Mikrotik for causing this issue for so many people.

1 Like
14

Should be pointed out that “it fixed nothing”, BTW.

15

The debate is still open if simply apologizing would be enough or delivering the apologies while kneeling on chickpeas should be required ... :wink: