You can run non-wave2 CAPsMAN on one of the non-wave2 CAPs and manage the other non-wave2 CAPs from that one. Both the old and new CAPsMANs should work on the same network, just not on the same device.Will I ever be able to run wifiwave2 on my rb5009 and manage non wifiwave2 Caps? Or will I have to upgrade all my Caps to hardware that wifiwave2 supports?
No you can never run wifiwave2 as there will never be a RB5009 with wifi.Will I ever be able to run wifiwave2 on my rb5009
But what radios work with that driver is the issue.The wifiwave2 package exists for the 5009 so that it can run as a capsman.
Is this a hard "no" from your side? Or is it simply a matter of time?You can run non-wave2 CAPsMAN on one of the non-wave2 CAPs and manage the other non-wave2 CAPs from that one. Both the old and new CAPsMANs should work on the same network, just not on the same device.
Ah, nice! I misunderstood that. Would that replace the default capsman? or can I run both on my rb3011?WifiWave2 CAPsMAN can be installed on non AP devices as well, aside from SMIPS and MIPSBE architectures. This is meant purely for WifIWave2 CAPsMAN capability, not for adding wireless NICs to x86 for example. You can download WifiWave2 for other architectures from the current testing branch - 7.7rc4.
My RB3011 has 128MBThough any device with 16MB flash won't have the storage capacity for the ~10MB wifiwave2 package!
To my knowledge:Would that replace the default capsman? or can I run both on my rb3011?
You do not need wifi capability on a device to install and run wifiwave2 package (It's CPU and memory size).No you can never run wifiwave2 as there will never be a RB5009 with wifi.Will I ever be able to run wifiwave2 on my rb5009![]()
With 7.13beta coming out, situation has changed completely.To my knowledge:
As it is now:
You need (at least) one capsman controller using wifiwave2 and (at least) one separate controller using legacy wifi-package for controlling the respective access points through capsman.
As far as I am aware you can not run both wifi-packages on the same capsman controller.
For a mixed AP environment (legacy Wifi and wifiwave2 devices on the same network), this means at least 2 controllers, 4 if you want redundancy.
(and keep in mind some AP devices are perfectly capable to act as capsman as well)
Future:
it may be possible both wifi-packages are going to be integrated into one package (but I could have misunderstood some messages completely wrong there although it would be the only logical evolution, in my view).