hAp ax S - Hot Spot 2.0 on wi-fi interface

Hi all!

I encountered some strange RoOs behavior when setting up WiFi on hAp ax S.

I tried to replace old office router with this device and realized that the WiFi interface was behaving strangely.

Initially, I configured all the parameters directly on the WiFi interface itself - I set the password, authorization type, Ssid, and other minimal settings.

Clients disconnected every 5 minutes, jumping between different ranges.

I took the router and started setting it up from scratch.

I found out that the WiFi connection behaves strangely if all the parameters are set on the interface.

Ultimately, I created profiles in the "Channel" and "Security" sections, and linked these settings in the "Configuration" profile. On the WiFi interfaces themselves, I specified the profile from the Configuration section.

As a result, the access point worked more stably, but I noticed that the inscription HotSpot 2.0 appeared next to the SSID.

I have not configured or enabled HotSpot 2.0 anywhere.

It seems that this was "pulled" from the default settings.

I tried to configure it from different versions of WinBox: versions 3 and 4 - the inscription HotSpot 2.0 always appeared

I solved the problem: created a profile in the Interworking section, where I set and disabled the HotSpot 2.0 parameter.

This is the first time I've encountered this kind of RoOs behavior.

And I'm not sure that something else is not turned on "by default" unless it is explicitly turned off.

Has anyone encountered this bug?

RouterOS 7.23.2

model = E62iUGS-2axD5axT

/interface bridge
add mtu=1500 name=bridge1
/interface list
add comment=defconf name=WAN
add comment=defconf name=LAN
/interface wifi channel
add band=2ghz-ax comment=2437 disabled=no frequency=2452 name=2452
skip-dfs-channels=all width=20mhz
add band=5ghz-ax disabled=no frequency=5805 name=5805 skip-dfs-channels=all
width=20mhz
/interface wifi security
add authentication-types=wpa2-psk,wpa2-psk-sha2,wpa3-psk disabled=no
group-encryption=ccmp name=sec2_test
/interface wifi configuration
add channel=2452 country=Ukraine disabled=no installation=indoor
interworking=interworking1 manager=local mode=ap name=test_2.4 security=
sec2_test ssid=Home_UF tx-power=17
add channel=5805 channel.skip-dfs-channels=all country=Ukraine disabled=no
installation=indoor interworking=interworking1 manager=local name=Test_5
security=sec2_test ssid=Home_UF tx-power=20
/interface wifi
set [ find default-name=wifi1 ] channel.band=2ghz-ax .frequency=2452
configuration=test_2.4 configuration.mode=ap disabled=no
interworking.realms-raw=""
set [ find default-name=wifi2 ] channel.frequency=5805 configuration=Test_5
configuration.mode=ap disabled=no interworking.realms-raw=""
/interface bridge port
add bridge=bridge1 interface=ether1
add bridge=bridge1 interface=ether3
add bridge=bridge1 interface=ether2
add bridge=bridge1 interface=ether4
add bridge=bridge1 interface=ether5
add bridge=bridge1 interface=wifi1
add bridge=bridge1 interface=wifi2
/ip firewall connection tracking
set udp-timeout=10s

Yes, this Winbox 3 bug is known for months now. At least here in the forum, not officially confirmed or fixed by Mikrotik.
For example just recently: Why are Capsman networks showing Passpoint on my laptop?

I have the same problem with version 4.

I see the interworking.realms-raw in your export. You need to unset that on both interfaces. see iOS 26.4 cannot connect to the hAP AX3 + CAP Wi-Fi; the iPhone only works with the default AX3 router configuration - #12 by rialtresh

How can I do this from WinBox? I don't see this option in either version 3 or 4.

Can only be done from terminal.

Thanks for the tip. I deleted interworking.realms-raw.

In interface 3.43 and version 4 the parameter exists, but its empty value is not displayed.

I removed it in version 4 like this: I specified the value, then deleted it.

I also created a situation: cfg4 was created in WinBox 3.43 (where the parameter was added), and cfg4 was created in WinBox 4. Everything is very strange. The text portion of the configuration is identical. Even the files obtained via export are identical. But some things are "visible" in the windows, while others are not.

Что, куда и как пишет WinBox

Oh, I was able to reproduce the bug with interworking.realms-raw in version 4!

If you create a configuration from the command line, this parameter is not visible in the WinBox interface :)))))

/interface wifi configuration add disabled=no interworking.realms-raw="" name=cfg1

And if you perform the same actions from the WinBox 4 interface, then everything is visible.

There's a video. Looks like you need to send it to tech support.

The problem with the interworking.realms-raw parameter not being displayed in the interface exists in WinBox version 4 and in the settings web interface.

Both on the current Stable branch (7.23.2) and on the RC branch (7.24rc3)

Technical support confirmed the bug, but there is no time frame.