Hi,
I’m having a strange issue with a MikroTik C52iG-5HaxD2HaxD running RouterOS firmware type ipq6000 . The device is brand new and was first tested with the factory firmware 7.6 .
The 2.4 GHz SSID works normally and is visible to all devices. The 5 GHz SSID is the problem: MikroTik can see it in scan, but most client devices do not see it at all.
What I tested:
Different RouterOS versions: 7.21.1 , 7.21.3 LTS , 7.22.3 stable
Factory firmware 7.6
Default configuration
Complete configuration wipe/reset
Different wireless parameter changes
Different frequencies and channel settings
DFS disabled / changed
Security variations
Current behavior:
Out of about 10 computers, only one laptop can see the 5 GHz SSID.
MikroTik can see the SSID in scan.
About half of the phones cannot see it.
Samsung phones with One UI 8.5 do not see it at all.
Samsung phones with One UI 8.0 can see it.
Windows 10 / Windows 11 devices also mostly do not see it.
This does not look like a client connection problem — the network is simply not visible to most devices.
I already tried:
Different firmware versions
Default configuration
Full configuration wipe/reset
Different channel/frequency settings
Disabling DFS
Changing channel width
Various security settings
QuickSet defaults and manual changes
At this point I suspect either:
a compatibility issue in the hAP ax2 WiFi implementation,
a regulatory/channel broadcast issue,
or a bug in RouterOS WiFi on this model.
Has anyone seen similar behavior where the AP sees the SSID itself, but most modern clients do not detect it?
PrintDetail
[admin@MikroTik] > /interface/wifi/print detail
1 M B default-name="wifi2" name="wifi2" l2mtu=1560
Thanks.
99 out of 100 the issue is config but we did not get to see that ?
So please show export of your config, specifically the wifi part.
nicknamer:
.encryption=""
Really?
Config wrong, use /export as mentioned before.
aldek
May 26, 2026, 9:17am
4
The same device model = C52iG-5HaxD2HaxD
RouterOS 7.21.1
No problem at all - iOS, MAC, Ubuntu, Win11 clients, at any 2.4/5 GHz SSIDs
My config:
/interface wifi set [ find default-name=wifi2 ] channel.band=2ghz-ax .reselect-interval=2h..4h .width=20mhz configuration.country=Superchannel .hw-protection-mode=rts-cts .mode=ap .ssid=XXX-X disabled=no name=wifi.2GHz security.authentication-types=wpa2-psk,wpa3-psk .ft=yes .ft-over-ds=yes .passphrase=PASSPHRASE .wps=disable/interface wifi set [ find default-name=wifi1 ] channel.band=5ghz-ax .reselect-interval=2h..4h .width=20/40/80mhz configuration.country=Superchannel .hw-protection-mode=rts-cts .mode=ap .ssid=XXX-X disabled=no name=wifi.5GHz security.authentication-types=wpa2-psk,wpa3-psk .ft=yes .ft-over-ds=yes .passphrase=PASSPHRASE .wps=push-button
[xxxxxxx@hAPax2-ZL] > interface/wifi print detail
Flags: M - master; D - dynamic; B - bound; X - disabled, I - inactive, R - running
0 M BR default-name="wifi2" name="wifi.2GHz" l2mtu=1560 mac-address=FF:FF:FF:FF:XX:XX arp-timeout=auto
radio-mac=FF:FF:FF:FF:FF:FF
configuration.mode=ap .ssid="XXX-X" .country=Superchannel .hw-protection-mode=rts-cts
security.authentication-types=wpa2-psk,wpa3-psk .wps=disable .ft=yes .ft-over-ds=yes
channel.band=2ghz-ax .width=20mhz .reselect-interval=2h..4h
1 M BR default-name="wifi1" name="wifi.5GHz" l2mtu=1560 mac-address=FF:FF:FF:FF:FF:FF arp-timeout=auto
radio-mac=FF:FF:FF:FF:FF:FF
configuration.mode=ap .ssid="XXX-X" .country=Superchannel .hw-protection-mode=rts-cts
security.authentication-types=wpa2-psk,wpa3-psk .wps=push-button .ft=yes .ft-over-ds=yes
channel.band=5ghz-ax .width=20/40/80mhz .reselect-interval=2h..4h
aldek:
channel.band=2ghz-ax
For maximum compatibility, it should not be set. See other topics on the same topic.
aldek
May 26, 2026, 9:47am
6
Yep, I know, but in my case it doesn't matter.
MMM MMM KKK TTTTTTTTTTT KKK
MikroTik RouterOS 7.22.3 (c) 1999-2026 https://www.mikrotik.com/
Press F1 for help
[admin@MikroTik] > /export hide-sensitive
/interface bridge
add comment=defconf interface=ether1 name=ether1
/interface bridge
add comment=defconf interface=ether1 name=ether1
aldek:
/interface wifi set [ find default-name=wifi1 ] channel.band=5ghz-ax .reselect-interval=2h..4h .width=20/40/80mhz configuration.country=Superchannel .hw-protection-mode=rts-cts .mode=ap .ssid=XXX-X disabled=no name=wifi.5GHz security.authentication-types=wpa2-psk,wpa3-psk .ft=yes .ft-over-ds=yes .passphrase=PASSPHRASE .wps=push-button
Thank you. I have two of these devices. Both are configured the same way, but one is having these issues and the other isn't...
2ghz works perfect... problem is in 5ghz...
tested your configuration - not working
Search other topic: Do not use winbox 3 and remove that wrong config.
Paste on Terminal:
/interface wifi
set [ find ] !interworking.realms-raw
Thank you, but not working
/interface wifi
First start from a base where it works for everyone, then customize...
Paste this:
/interface wifi
set [ find default-name=wifi1 ] !channel.band channel.frequency=5180 !channel.reselect-interval \
.skip-dfs-channels=all !channel.width configuration.country=Czech !configuration.hw-protection-mode .installation=indoor \
.mode=ap disabled=no !interworking.realms-raw security.authentication-types=wpa2-psk \
.encryption=ccmp .ft=yes .ft-over-ds=yes .group-encryption=ccmp .management-protection=disabled .wps=disable
/interface wifi
set [ find default-name=wifi1 ] configuration.country=Czech .installation=indoor .mode=ap disabled=no mtu=1500 security.authentication-types=wpa2-psk
set [ find default-name=wifi2 ] configuration.country=Czech .installation=indoor .mode=ap disabled=no security.authentication-types=wpa2-psk .encryption=ccmp
jaclaz
May 26, 2026, 12:25pm
16
You probably need to add this:
aldek:
.passphrase=PASSPHRASE
to each set of commands
Something new comes up every time,
set [ find default-name=wifi1 ] configuration.country=Czech .installation=indoor .mode=ap .ssid=T5G mtu=1500 security.authentication-types=wpa2-psk
It doesn't matter if there's no authentication—I turned off all authentication options and it still doesn't work. Now I've set it to WPA2 with the password 12345678, and that doesn't work either. Most devices just can't see it; it's not listed among the visible networks...
jaclaz
May 26, 2026, 1:49pm
19
Could it be an issue with channel range?, i.e. this:
deprioritize-unii-3-4=yes
is sometimes needed when clients cannot reach the higher frequency channels.
