L009UiGS-2HaxD - WifiWave2 CAPsMAN and wireless package

RouterOS General
1

As in title

I want to use L009 as central router for both CAPsMAN v1 and v2 with wireless package

 
> /system/package/print
Flags: X - DISABLED
Columns: NAME, VERSION
#   NAME          VERSION
0 X wifi-qcom     7.13   
1   wireless      7.13   
2   routeros      7.13   
3 X wifi-qcom-ac  7.13

Which seems to work, except i’ve lost onboard wifi

> /log/print
 13:17:09 script,warning DefConf gen: Unable to find wireless interface(s)
 13:17:09 system,error,critical error while running customized default configuration script: interrupted
 13:17:09 system,error,critical




>  /interface/wifi/print
0 MX wifi1  ap




> /interface/wifi/scan wifi1 
failure: interface not bound

Obviously if wifi-qcom is enabled i am losing wireless and CAPsMAN v1 capabilities


Is there something i can do to have it both ways?

2

What makes you think you loose legacy capsman when enabling wifi-qcom ? (which is v2 BTW)
Only wifi qcom, not qifi-qcom-ac (uninstall, not needed on L009, is only for arm-ac devices).

New capsman is in wifi structure.
Old capsman should be under wireless/capsman.

3

Please don’t be confused by the terms
CAPsMAN v2 is working starting from RouterOS v6.22rc7.
CAPsMAN v1 is discontinued starting from 6.37.
https://wiki.mikrotik.com/wiki/Manual:CAPsMAN

WifiWave2 CAPsMAN
https://help.mikrotik.com/docs/pages/viewpage.action?pageId=46759946#WifiWave2(7.12andolder)-WifiWave2CAPsMAN

4

I might have confuse myself with names, sorry for that.

But that beeing said, I am unable to have wireless package and working local wifi interface at same time.
I can’t fully go for wifiwave2 as i still have mipsbe devcices

5

Wifi interface on L009 is only supported by wifi-qcom driver and has to be configured via wifi configuration subtree (in CLI that’s /interface/wifi). The same configuration tree is shared with wave2/wifi capsman. In your case, only capsman for legacy (remote) radios will be using wireless configuration subtree. So you absolutely need wifi-qcom driver enabled.

Another thing to keep in mind since you’re coming from legacy capsman environment: wave2 capsman can not control local radio, local radios have to be configured “manually”. But since they share same configuration subtree, including all the profiles, performance is still optimal (e.g. 802.11 r/k/v mobility works just like if it was yet another cap). I guess you need to have the “wireless” package enabled for legacy capsman to work. But hopefully it won’t interfere with the ax hardware (it never supported the ax hardware, so I guess that won’t be a problem after all).

6

That’s the problem

When i enable wireless then wifi-qcom is automatically disabled and otherwise,
when i enable wifi-qcom then wireless is automatically disabled

I am unable to have them both active

7

Create supout.rif and contact support.
With 7.13 it should be possible to have both active.

8

Hm, it seems that it can’t


9

Good to know !!

So either you choose to use wireless and corresponding capsman controller can be used ( legacy or wave2 via qcom or qcom-ac).
Or no wireless at all and then both capsman controllers can be used.

10

see this http://forum.mikrotik.com/t/7-13-wireless-package-split-question/172049/1