Running last stable software for routeros and wifi-qcom. I just reset configuration and brought the unit up as switch/AP and configured 2G and 5G WiFi exactly the same as they were when the unit was running default configuration. The 2G WiFi is working perfectly however the 5G WiFi is acting strange. The 5G WiFi is not allowing any of the laptops that previously work to connect now. Any laptop regardless of Win11 or Linux gives a "failed to activate" error message when attempting to connect to the 5G but they connect fine to the 2G. The odd thing is that all mobiles/tablets can see and connect to the 5G just fine. I have tried disabling WPA2 then WPA3 on 5G and the laptops but nothing seems to work. Also even if I enable SSID broadcast the laptops never see the 5G WiFi so can't connect this way either. I have also tried turning off AX for 5G but this didn't help either. Any idea what could be the issue?

Found this viewtopic.php?t=203251 and following suggestion of setting channels manually "Frequency currently set to 5500, 5580, 5660 and 5180" and the 5G is now working on the laptops. Seems to be a bug with auto frequency allotment on the Hap AX2. My Hap AX3 does not have this issue.


BTW the laptops having this issue are:

Lenovo Intel Evo Thinkpad 1 year old
Lenovo Intel Evo Slim7 3 years old

Mobiles that worked fine are Samsung Z4 Fold and Z5 Flip.

It's not a bug if your AP uses a frequency which the client devices can not use. That's a client device problem.

E.g. for a client installation I have Symbol warehouse scanners only able to use 5Ghz 5180-5240. Nothing else.
So I needed to set all 15 APs to use those frequencies (in a non-overlapping pattern) only and nothing else.

I NEVER use auto frequency not even at home.
I ALWAYS set frequencies manually for each AP after doing a scan of the environment. It rarely requires a change for the devices under my control.

How do you handle DFS events, @holvoetn? Or don't you use any DFS channels?

How do you handle DFS events, @holvoetn? Or don't you use any DFS channels?

I try to avoid those when possible for obvious reasons.
At home I do use them but I am in such a nice isolated appartement that I don't ever see a DFS problem occurring
(really, it's almost a bunker. Most places in there I can't even use my cell phone unless I really move close to the window or go outside on the porch)

It's not a bug if your AP uses a frequency which the client devices can not use. That's a client device problem.

E.g. for a client installation I have Symbol warehouse scanners only able to use 5Ghz 5180-5240. Nothing else.
So I needed to set all 15 APs to use those frequencies (in a non-overlapping pattern) only and nothing else.

I NEVER use auto frequency not even at home.
I ALWAYS set frequencies manually for each AP after doing a scan of the environment. It rarely requires a change for the devices under my control.

Not buying that as the two laptops are fairly new and none of the devices have the issue on my Hap AX3.

How do you handle DFS events, @holvoetn? Or don't you use any DFS channels?

Original setup is full auto configuration for both 2G and 5G WiFi, Skip DFS Channels set to 10min CAC. All other setting are left to whatever Mikrotik has assigned.

Can you report the output of the following commands?
(possibly by disabling WPA3, first)

What linux distribution do you have?

Not buying that as the two laptops are fairly new and none of the devices have the issue on my Hap AX3.

And you can tell with 100% certainty both AX2 and AX3 were using the same frequency ? I doubt it.
Unless you set the frequency yourself, you don't know what will be used.

I have seen devices not 1 or 2 year old unable to connect to higher wifi bands whereas my 4 year old Samsung S20 has no problems doing so.

Can you report the output of the following commands?

Code: Select all

/interface/wifi/actual-configuration/print
/interface/wifi/print detail

(possibly by disabling WPA3, first)

What linux distribution do you have?

This is happening on Linux Mint 21.3 5.15.0-107-generic x86_64 bits as well as Win 11 with latest updates.

Not buying that as the two laptops are fairly new and none of the devices have the issue on my Hap AX3.

And you can tell with 100% certainty both AX2 and AX3 were using the same frequency ? I doubt it.
Unless you set the frequency yourself, you don't know what will be used.

I have seen devices not 1 or 2 year old unable to connect to higher wifi bands whereas my 4 year old Samsung S20 has no problems doing so.

Maybe you missed the fact that the system was working fine before changing the config to switch/AP mode. Yes the same laptops worked fine before that even though the Wifi for 5GHz was setup in exactly the same way after the reconfig.

You are missing the point.
What frequency was used ??

Can you report the output of the following commands?

Code: Select all

/interface/wifi/actual-configuration/print
/interface/wifi/print detail

(possibly by disabling WPA3, first)

What linux distribution do you have?

This is happening on Linux Mint 21.3 5.15.0-107-generic x86_64 bits as well as Win 11 with latest updates.

You probably missed my first part. Could you please provide that report?
Exact model of the laptop could be useful, too.

Also the output of the command
on one of the laptops is useful. Mint should have it.

Also the output of the command

Code: Select all

iw list

on one of the laptops is useful. Mint should have it.

Information requested is in attachment.

Lenovo Intel Evo Thinkpad 1 year old
Lenovo Intel Evo Slim7 3 years old

That was my post and my problem was with a Lenovo laptop too. Probably both using the Realtek chipset. I think on these chipsets, it's a failure to implement 802.11d correctly. They don't set the country correctly and block connecting to 5745 and above. On a Windows laptop, you can try disabling 802.11d in the device manager, if the option is available.

Lenovo Intel Evo Thinkpad 1 year old
Lenovo Intel Evo Slim7 3 years old

That was my post and my problem was with a Lenovo laptop too. Probably both using the Realtek chipset. I think on these chipsets, it's a failure to implement 802.11d correctly. They don't set the country correctly and block connecting to 5745 and above. On a Windows laptop, you can try disabling 802.11d in the device manager, if the option is available.

Both are running the Intel Wi-Fi 6 AX201 hardware, and worked fine before changing the Hap's function from router to switch/AP mode.

Hmm completely different chipsets then. There should be no logical reason why it's different between being configured as a router and a switch/access point. The main difference being lack of firewall and NAT on the later. But that shouldn't really affect Wi-Fi.

There should be no logical reason why it's different between being configured as a router and a switch/access point. The main difference being lack of firewall and NAT on the later. But that shouldn't really affect Wi-Fi.

Yes, indeed. I don't believe that switching from router to switch/AP is the reason.

I've read the output of the commands and there is a chance that the AX2 chose a frequency >= 5845 (channel >= 169) which is permitted in the US (at least according to ROS) but disabled on the laptop (according to iw list).
This also explains why the issue disappeared when the frequencies were explicitly set.
Choosing those frequencies appears to be reasonable, since they allow high transmission power and no DFS. I don't think we have elements for suspecting a bug (not yet, at least).

My suggestion is to check the status tab as soon as the issue arises.

PS: @mtbdrew You probably forgot to elide the password (#ddcomet24#) from the output. Please change it, if I am not wrong.

I've read the output of the commands and there is a chance that the AX2 chose a frequency >= 5845 (channel >= 169) which is permitted in the US (at least according to ROS) but disabled on the laptop (according to iw list).
This also explains why the issue disappeared when the frequencies were explicitly set.
Choosing those frequencies appears to be reasonable, since they allow high transmission power and no DFS. I don't think we have elements for suspecting a bug (not yet, at least).

Q.E.D.

That was my initial suspect. Just collecting data to support the thesis.

I also understand Mikrotik's dilemma:
- if they allow ROS to use high freq (when available) then the channels are likely free but there is a chance that the client is not able to connect ("ehy, my router/AP has a bug")
- If they restrict high frequencies, then the client connects but wireless speed drops ("ehy, wifi sucks")

Maybe adding a flag in the quickset (on by default) that restricts the 5GHz frequencies if flagged?

I just switched back to auto and can confirm that it is defaulting to 5585 in switch/AP mode. No way of knowing what it was using in previous router configuration but it must have been some other channel because the laptops were working then.

Based on the channels available I have switched to using:

5500
5660
5785
5825

Hap AX2 has landed on using the 5825 with power level 26 instead of the 5660 power level 20 it was using.