I’ve got CAPsMAN running in x86_64 hardware. Here, I’ve got 4 cAP ax devices connected.
It’s currently in 7.12.1 environment.
In CAPsMAN, I’ve got 3 packages installed.
routeros
user-manager
wifiwave2
When I click “Download&Install” button, I get below error.
wifi-qcom-ac-7.18.2.npk missing, use ignore-missing or diable package(s).
I understand I only need routeros package for CAPsMAN. (Is this right?) If so, should I go ahead and delete the package then perform the upgrade?
I’m putting in routeros and wifi-qcom-7.18.2-arm64.npk under firmware directory so cAPs will be upgraded automatically.
Am I good to go? or I should be doing something else?
I went ahead and did it (upgrade that is), devices are connecting and network is up but when I login to CAPsMAN (using winbox) then go to WIFI → WIFI (tab) I do not see and Tx and Rx moving.
It’s displaying 0.
I get a RED error message saying “operated by CAP %ether1, traffic processing on CAP”
What do I need to do to see individual Rx Tx stats?
It’s correct to proceed with using “ignore missing packages”.
The thing is: up to and including 7.12.1, the new CAPsMAN (for AX and some AC devices) was a part of wifiwave2 package. On certain platforms (arm), same package (wifiwave2) also contained drivers for actual radio hardware. On x86_64, wifi radios are not supported, so package wifiwave2 only contained CAPsMAN.
From version 7.13 forward, new CAPsMAN became part of base (routeros) package, driver part of wifiwave2 package got split into two new optional packages (wifi-qcom and wifi-qcom-ac) and functionality regarding older wifi (legacy CAPsMAN and wireless drivers) were split off to another separate optional package (wireless).
So the ROS built-in upgrader was made a little smarter in version 7.12(.x) so that it detects combination of packages installed and wireless hardware present and tries to upgrade to appropriate set of new packages:
on devices with none relevant optional packages installed it additionally installs new optional package wireless
on devices with wifiwave2 package installed and with AX radio hardware present it installs new optional package wifi-qcom instead of wifiwave2
on devices with wifiwave2 package isntalled and without AX hardware present it installes new optional package wifi-qcom-ac instead of wifiwave2
And regarding the first and last bullet it’s a bit stupid: it installs wireless package even on devices without any wifi hardware and even if capsman is not enabled; it tries to install wifi-qcom-ac package even on devices without any wifi hardware and barfs if it’s not even available on running platform.
I guess that it was a deliberate decission do it like this just because of chance of breaking some configuration which they didn’t bother to try to detect (like using legacy CAPsMAN on radio-less device … or, like in your case, running new CAPsMAN on a non-arm platform).
Can you tell me where in CAP I can find it? I’ve looked everywhere and can’t see it.
If you are referring to WIFI ->WIFI (tab). No it is only showing 0.
I think you mean this. See attachment.
It also shows 0. However, while I took this screenshot, I noticed that the values of Tx/Rx Bytes were not changing, though they have a non-zero value, which I can’t comprehend as the Tx/Rx rate being 0 all the time.
How is it possible for it to accumulate that size with a rate being 0 all the time?
Am I missing something here?
