After RouterOS version 7.22, CAPsMAN causes only iPhones (iOS) to be unable to connect to Wi-Fi

RouterOS Wireless Networking
1

After entering the password, there's no response, and it's stuck in an endless wait.

This is unrelated to the iOS version.

It's unrelated to RouterOS Wi-Fi settings.

It's definitely a firmware version issue; any iPhone using CAPsMAN with RouterOS version 7.22 or later will get stuck after entering the password.

All logs that monitor Wi-Fi connection status show no new device connection messages.

Android devices function normally.

I spent three days trying and confirmed that the problem only occurs after version 7.22.

Once you've upgraded to a version after 7.22, even downgrading via LongTerm doesn't work.

In three days, using the normal Winbox method to downgrade the version, only one device downgraded to v7.21.2 and it returned to normal.

I suspect that using the Netinstall method to downgrade is the only effective method.

I tried it on 6 devices with different CPUs: ARM64, ARM, and MMIPS.

The new RouterOS original factory version works as long as it's lower than v7.21.3. The same settings were applied once, and it worked.

2

Check if this applies;

3

@jaclaz When I updated to 7.22 I didn’t notice anything new with Apple Devices not working. My thermostats don’t work thou.

Checking my notes, the thermostats worked on 7.22. Then have disappeared on 7.22.1

4

If the SSID and password are already saved, there's no problem. It will only be detected on a new device or after clearing the password saver.

5

It is not entirely clear, but it seems like the (stupid) interworking.realms-raw is set using Winbox v 3.x on 7.22 or 7.22.1, so not all people got them, it is probably one of multiple reasons why there are new conneciton issues with Apple devices (IOS, not MacOS).

6

I am thinking of already some years: to start a topic it's purpose is to collect Winbox misbehaviour.

7

The issue is consistently attributed to Winbox v 3.x + interworking.realms-raw? But actually, when using Winbox v 4.x /interface/wifi/export, I don't see interworking.realms-raw? Is the unset setting missing?

And in reality, this only occurs when updating to 7.22 or 7.22.1; only iPhones (iOS versions) cannot join Wi-Fi.

The problem seems to stem from firmware versions 7.22 and above. As long as the original device isn't updated to version 7.22 or higher, there shouldn't be any issues.

8

As said earlier the

interworking.realms-raw

only happens to "come out" on 7.22 or 7.22.1, but it is not clear what "triggers" it.

I don't think that it is a "generalized" issue (otherwise by now we would have had tens or hundreds of reports, given the ubiquity of iPhones, particularly in the US but also in many EU countries), it must be happening only in some cases when the update is performed (and the use of Winbox v3 might or might not be the cause, it could be some wifi or non-wifi related setting that is causing it during the "translation" of the configuration from an earlier version).

9

i am getting the same exact issue. The problem did not start immediately when i upgraded to 7.22, rather, Iphones initially were able to join the network via one speciffic AP then roam to the other. After making the iphone “forget” the network as part of the troubleshooting effort, it now fails to join the network completely. The only way i got the iphone to associate is by completely disabling security

10

SUP-214053 opened. i suggest you all do the same.

11

Good luck with that.

12

i’ve sorted stuff with their support in the past, bugfixes mainly. anyway, let’s include the fix for the folks out there who encounter this issue and don’t have the patience to read the whole thread.

so to fix this, issue this command in CLI:

interface wifi configuration set "YOUR CONFIG PROFILE NAME HERE"  !interworking.realms-raw
13

I have already reported several (non wifi) bugs, and many of them have been fixed. Issues with wifi connections - especially when they affect only a few clients - are (in my experience) treated as “special" cases. In such situations, you need to provide a significant amount of evidence yourself (Wireshark sniffs, etc) in order to help with reproduction.

14

I don’t bother reporting bugs with WiFi.

Jut unplug the APs and wait for the next release.

Now when my router freezes up… that get a support file and a ticket right away.

And the CSS610 5 minute lock up still seems to be there if you leave rstp on. Also reported.

But WiFi… why bother? Took em 6 years to get this level, and I trip over bugs every single time I test the new routerOS.

15

The interworking.realms-raw setting, which is not visible in the GUI, is indeed causing the inability of iPhone (iOS) devices to join Wi-Fi networks after entering the password.

After repeated testing, it was confirmed that only specific combinations of Winbox 3.x + 7.22 or 7.22.1 automatically add the interworking.realms-raw setting when configuring Wi-Fi, but this setting is not visible in the GUI.

Whether it's Winbox 3 or 4, the interworking.realms-raw setting is not visible in the GUI; it can only be seen by exporting it from the command line.

Clearly, the bug is not limited to the firmware version but is also present in a specific Winbox version. This combination of bugs means that not many users will encounter it.

Besides this obvious problem of being unable to join Wi-Fi networks, versions after 7.22 seem to have many other issues, though these are not universally encountered, as many features are not used by most users.

16

I can confirm this problem. It took me 2 days to figure out what the problem was. Only iOS devices are affected on my end.

For now i rollback on 7.20.8 long-term and everything is fine.

17

I’ve switched back to the long term (7.20.8) and I still cant get an IOS device to connect…

18

Misconfig (though not your fault), check your topic.

19

Same issue for me, massive problems with iOS devices.

Downgrading to 7.21.3 didn’t help!

Please advise!!!

20