I have a production setup with the following hardware:
CAPsMAN: CCR2004
CAPs: 100x cAP ac (RBcAPGi-5acD2nD) and cAP XL ac
Current state: All CAPs are running the legacy wireless package and are managed by CAPsMAN on the CCR2004.
I would like to migrate to the new wifi-qcom-ac package gradually. I have two questions:
Question 1 – Phased migration
Can I migrate my CAPs in stages (e.g., 10 units per week) while keeping the rest on the wireless package?
Specifically:
Can the same CCR2004 run both the legacy CAPsMAN (for wireless) and the new CAPsMAN (for wifi-qcom-ac) at the same time?
Will both groups of CAPs simply provide connectivity during the migration period? (I understand Fast Roaming between groups is not expected — I will enable it after full migration. I just need both groups to work simultaneously.)
Question 2 – Country "unknown" on wifi-qcom-ac
After flashing a cAP AC to the wifi-qcom-ac package, in WiFi → Configuration → Country I only see "unknown" — no countries are listed.
This issue does NOT exist on the wireless package.
yes
Your CAPsMAN device (CCR2004) has to run ROS v7 (as it introduces new WiFi CAPsMAN) and has to have the (optional) wireless package installed. This package brings both legacy wireless drivers (not relevant on CCR devices) and legacy CAPsMAN functionality.
You'll have to configure both CAPsMANs separately, they don't share config. So you'll have to make settings for both parts of your network similar manually.
Since both parts of your network will be controlled by different CAPsMAN entities, there won't be any cooperation between them. But that's the same as it is when using legacy (wireless) CAPsMAN alone. So I suggest you to migrate bunches of APs which have overlapping coverage to enable enhanced mobility (802.11 r/k/v) at least between those APs.
I don't see the same. My AP running wifi-qcom-ac shows quite a lengthy list of countries available (both via CLI and via WinBox 4.0.1 for Linux). My CAPsMAN and CAP devices is running ROS 7.20.8.
I have made some progress and now I have both CAPsMAN versions running simultaneously, but I am stuck with a connection issue on the new wifi-qcom-ac driver.
What I configured on the test CAP (via new WiFi CAPsMAN Wave2):
Same SSID as before
Same passphrase (WPA2-PSK)
Same channel settings (2.4 GHz and 5 GHz)
Datapath: without vlan-id (I do not use VLANs in this setup — it's a simple flat network)
Bridge: I am using the exact same bridge that was working perfectly with the legacy wireless package
When I try to connect a client device (tested with several clients — laptops, smartphones), the client fails to connect. It either times out or shows "authentication failed" even though the passphrase is correct.
The same SSID and passphrase work immediately when I roll back to the legacy wireless package on the same CAP.
What could be wrong?
I only have one Wave2 access point and one wireless (legacy) access point. Both are configured on the same controller and have identical configurations (SSID, datapath, etc.)
I have the wireless package installed on my ccr2004. If I remove it, the interface-capsman option will disappear and the old access points won't work.
I'm still digging. Deleting the option didn't help.
I was able to connect, but there's no received traffic. The device isn't receiving a DHCP address, and it's not working with static data, so there's no response. Under the WiFi option, "Registration," there's no Tx Rate line, but there is an Rx Rate line.
I currently have Legacy Capsman configured. I want to install Wave2 alongside Legacy to seamlessly migrate from Legacy to Wave2. Everything works fine with Legacy, but Wave2 doesn't. I'm using an existing, working datapath. DHCP works in the datapath (it works in Legacy). I tried setting the IP address manually and pinging the datapath, but nothing happened. Wireshark only shows packets being sent, not received. Could this be because both Capsman instances are running simultaneously?
There are 2 major forwarding/traffic-processing modes: local forwarding mode (traffic-processing=on-cap), where CAP is locally forwarding data to and from wireless interface; CAPsMAN forwarding mode (traffic-processing=on-capsman), where CAP sends to CAPsMAN all data received over wireless and only sends out the wireless data received from CAPsMAN. CAPsMAN forwarding is only possible starting with 7.21beta2 version. On older versions, only CAP forwarding is supported. CAPsMAN forwarding is not supported by wifi-qcom-ac devices (wifi-qcom-ac drivers only support local forwarding).
)? 
, but for a moment I thought I was having dislexia 
.