this message is kinda directed to support as I believe it is a heavy problem, but maybe I am not the only one who can reproduce this problem and I suspect it isn’t actually only a hardware thing.
Instead of many words let me direct you to an a presentation of the problem (with pictures).
I’d like also to draw attention of the MikroTik support to the ticket Ticket#2015042966000707 . If your guy asks me after reading all of this whether I am using two SXT’s and that I can use wireless-fp the same way as I’d wireless package, there is something wrong… huh?
While there was some improvement, I can’t really say that it fixed the problem.
Wireless-fp means to actually run WLAN controller first which I haven’t setup yet… actually working on it now.
(Also hoping to use CM2 in the future, that’s why I don’t want to use FP as a workaround.)
no, with wireless-fp is not mandatory to do capsman
wireless-fp its the main wireless package today in 6.30 wireless no fp package will be retired from default installation, CM2 must be considered beta.
in logs looks like you are doing a lot of things on that AP (dynamic routing etc), try using AP only to do bridge mode and fast path without any aother features to isolate the problem.
remove any un-needed package, in my APs y only use the following packages:
Same issue here. We had 25 deployed and had to removed all the cards because of the exact same issues. They were better on 6.18 but still a unstable. We haven’t tried other cards but it’s either the r11e or the irq issue that the 912’s have, not sure but we wont use them. No issues out of the netmetal ac or sxt ac.