If aggressive TCP timeouts cause the issue why it isn't constant? And I tried to reset all connections from Tracking/Connections tab and it doesn't solve. At least for a short time it should resolve if it's a timeout issue, I guess.

Does anyone have any ideas?

Config attached.

I'll upload the config soon.
Meanwhile I captured the traffic with wireshark and I see TCP connection issues.

I have an issue with an AC3 v17.3 to v17.5 (latest). It happens randomly. The Teams works but its impossible to start a call or receive calls. I use a bit sophisticated firewall rules, but I've tried to disable the whole firewall (put allow rules on all chain, raw scope too). I've tried to drop the ...

Signal strength of 50 is quiet impossible as far as I know. In theory it's possible, but in practice not so much. It would mean that Rx antenna is pumping 100W worth of signal into receiver. Not many WiFi devices can transmit at that kind of EIRP and as soon as there's some air gap between Tx and R...

+1. I think it's a bug, but it's not funny. Because my wifi clients are flapping with "too strong signal". error message. :\

Thanks everyone. I've got several clients with cAP ac's so I'm just looking at one in the lab. I think the only hurdle I need to overcome is some problem with CAPsMAN and guest VLANs. The solution about doing the tagging in a different way is covered a forum post somewhere :-) The VLANs work like c...

Signal strength of 50 is quiet impossible as far as I know. Can you share your (/wifi) config on the CAPsMAN? /interface/wifi export file=anynameyoulike Yes. It's impossible. :) Maybe it's a bug between MikroTik APs and specific clients. Because most of the clients have no issues. It's a Macbook.

Wave2 drivers so stability is also a lot better.
Also pure performance, quite some difference.

I can debate with it. I have many issues since I updated to wifi-qcom-ac on cAP ACs up to 7.13.5.

Some wifi clients disconnect and connect back continiously. They are frustrated. APs: cAP AC with wifi-qcom-ac 7.13.5 Managed from new CAPsMAN In the attached screenshot this is one client. "Too weak signal" is fine, it comes from access list.. BUT What the hell is "too strong signal&...

What is the successor of :
/interface wireless info country-info country=<country name>
command for checking the available channels and regulations?

You missed configuring the local wifi on RB5009 as a CAP.
/interface wifi cap set ....

I am running DUAL capsman at the moment to support dozens of legacy devices || AC || and new AX devices. So far no issues on 7.13.4 as a controller. There are some things to navigate/additions on the new wifi side of capsman world, but have now got over that hurdle. I have 1 controller a CRS317, I ...

I'm not seeing anything really out of the ordinary on the wave2 capsman part. Only difference I see it that I don't use any certificates at all (don't know why I should on a completely internal LAN). Maybe you can try that as well, if it works, you know where the problem is. Do you use a bridge int...

I checked Interfaces in old CAPsMAN and I think order doesn't matter here because no # column. I learned on MTCNA, order only matters if # is there.

/interface wifi provisioning add action=create-dynamic-enabled disabled=no master-configuration=\ Hedgehog_5GHz name-format=%I-5G radio-mac=XX:XX:XX:XX:XX:XX \ supported-bands=5ghz-ax add action=create-dynamic-enabled disabled=no master-configuration=\ Hedgehog_2GHz name-format=%I-2G radio-mac=XX:X...

I understand correctly that you have configured 2 old Capsman one on CHR the other on mAP lite. PS. After resetting to CAP mode, the second capsman was deleted In this case on CAP ax manager search is enabled on the interface and not by IP address? (When interface search is enabled, IP search does ...

UPDATE: If I put CAP2 (mAP lite legacy 2,4GHz) into CAP mode from reset configuration, it starts working with the provisioned config from CHR's legacy capsman.
The other issue still there.

Update the AC to 7.13 and you can manege from the new CAPsMAN like AX. But if you use VLANs the config will be tricky and complicated because on AC devices the wifi-qcom-ac driver doesn't support vlan tagging. You have to create bridge vlan filtering config in this case: https://help.mikrotik.com/do...

I have a dual test setup at home (using Hex, AX2 and mAP).
Will check this evening if I can see potential issues.

Thanks!

Yes. I built this test environment from resetted, 'no defaults' state. I also tried to remove all certs (old and new capsmane related too) and generate new ones again and again in different order but no effect... I have been testing. If I reboot the CHR with a working CAPsMANv2 with enabled legacy C...

I'm testing Dual-CAPsMAN scenarios on the new 7.13.4 version. Based on the MikroTik official YT video, they mentioned the new and the legacy CAPsMAN can work together on a device for supporting the devices with wiif-qcom/wifi-qcom-ac and the older devices with wireless packages, in one box. I'm face...