@shahjaufar glad to hear that I'm not alone...
So.. I also have a brand-new wAP R ac here. It was on default config (never used before, still with RouterOS 6). Upgraded the official way (first to the latest v6, then to 7.12.1, then to 7.13.4).
Result:
As soon as you install the wifi-qcom-ac package, you'll have the
error message in the log.
Then, the **only** change to the default config I made was to set the caps-man-address.
Result, as before, the caps-man server has the new device in its list of remote-cap:
But as before, the Wifi devices stay unconfigured. The same caps-man server configures, however, my hAP ac^2 just fine.
The apporach brought up by @Amm0 sounds interesing.
I compared the two scripts, they seem to only differ in a CR being at a different place:
So.. next step as adviced by @erlinden: reset to default (which is somehow silly, as the wAP is brand new) with caps-mode on. This, however, surprisingly worked. Funny enough, afterwards the script error does not re-appear.
I hope that this rather lengthy post (sorry for that) help others. Would still consider the current wAP ac driver being buggy, as my initial approach without a full reset should be valid, worked with the old CAPsMAN and also still works with the hAP ac^2.
So.. I also have a brand-new wAP R ac here. It was on default config (never used before, still with RouterOS 6). Upgraded the official way (first to the latest v6, then to 7.12.1, then to 7.13.4).
Result:
As soon as you install the wifi-qcom-ac package, you'll have the
Code:
13:29:05 script,error script error: error - contact MikroTik support and send a supout file (2)Then, the **only** change to the default config I made was to set the caps-man-address.
Result, as before, the caps-man server has the new device in its list of remote-cap:
Code:
[admin@main] /interface/wifi/capsman/remote-cap> print Columns: ADDRESS, IDENTITY, STATE, BOARD-NAME, VERSION# ADDRESS IDENTITY STATE BOARD-NAME VERSION0 192.168.188.5 hAP_ac2 Ok RBD52G-5HacD2HnD 7.13.4 1 192.168.188.4 wAP_1OG Ok RBwAPG-5HacD2HnD 7.13.4 2 192.168.188.34 MikroTik Ok RBwAPGR-5HacD2HnD 7.13.4 [admin@main] /interface/wifi/capsman/remote-cap> The apporach brought up by @Amm0 sounds interesing.
I compared the two scripts, they seem to only differ in a CR being at a different place:
Code:
$ diff hap wap135,136c135,136< :local removeDatapath [:parse "/interface $wirelessMenu datapath remove [find comment=\"defconf\< "]"]---> :local removeDatapath [:parse "/interface $wirelessMenu datapath remove [find comment=\> "defconf\"]"]I hope that this rather lengthy post (sorry for that) help others. Would still consider the current wAP ac driver being buggy, as my initial approach without a full reset should be valid, worked with the old CAPsMAN and also still works with the hAP ac^2.
Statistics: Posted by harenber — Wed Feb 14, 2024 4:07 pm