I am the owner of the hap ac2 router. Firmware 7 is installed, the mode is only available in the Internet mode in, dual ap is not available. I installed firmware 6, and dual ap is available. What’s wrong? I think I can try to reinstall it through netistal, but I have no such experience. What is the problem???
Try netinstall … that is the way of experience
Follow it by the letter:
https://help.mikrotik.com/docs/display/ROS/Netinstall
reinstalled from netinstall, the result did not change, for some reason he thinks that he does not have wifi
You must have netinstalled the base OS package only. Add the relevant WiFi packages. Docs may be lagging; all of this changed in v7.13. See that version’s huge release thread for details.
This one might be easier to read, especially the grid.
https://help.mikrotik.com/docs/display/ROS/Wireless
Basically, for 7.13-chain and above:
- if you want legacy wireless like it was: add wireless package
- if you want wave2 wifi (ac2 can do it): add wifi-qcom-ac package
For both cases: be aware storage space might become a problem later on.
It might be (depending on how you use that device) best to keep it on 7.12.x for now.
(7.14, currently rc1, does bring some storage gains but not much)
Hi all was this problem solved? As I am sitting with the same issue, no wlan in routeros7.15.
Have you read both provided links ?
Probably the same solution.
Hi all was this problem solved? As I am sitting with the same issue, no wlan in routeros7.16.
installed packages: routeros 7.16 + wireless 7.16
[admin@MikroTik] > /interface/wireless/print
Flags: X - disabled; R - running
[admin@MikroTik] >
Link provides the following info (https://help.mikrotik.com/docs/display/ROS/Wireless)
New 802.11ax devices
Old Capsman — routeros + wireless — Actually old = dual. Loses built-in cards
… but it does not say when “Loosing built-in cards” will be fixed?
I wouldn’t count on getting that fixed (probably it’s a can of worms which MT disposed off already a while ago).
If you need to run legacy capsman, then get an older device and run it there (you can do it on one of your legacy CAP devices or start a small CHR if that fits better). If you don’t use CAPsMAN forwarding (which is a burden for CAPsMAN device and severely limits wireless throughputs even on fastest devices), then capacity of device, running CAPsMAN, doesn’t matter much.
You’re mixing up two things…
I see references to AX devices yet wireless package.
So what are you exactly trying to do ?
Thank you for quick answer!
Well, then better wording in manuals and advertisements would be good in case it is planned “feature” (and not temporary bug).
My experience so far is that each new Mikrotik device is better (but backward compatible).
It seems it is not the case with hap ax2.
Now I understand why I saw so many refurbished hap ax2 on the sale. Likely other buyers expected the same but after they found out it is not backward compatible with ac2 they returned them.
I do understand that I can install “wifi-qcom” instead of “wireless” but it does not seem to be complatible with old capsman?! Correct?
But I have 5 capsman slaves … upgrading capsman and replacing 4 additional slaves is unexpected change of scope.
No, backwards compatibility is not always guaranteed. One example: curently we’re using capsman v2 (nowdays called legacy capsman) and capsman v3 (the new, wifi, capsman). And capsman v1 was not compatible with v2 … it only co-existed for a short while.
The thing that happened with v7 (and we, users, did put lots of pressure on MT to happen quite a long time before) is that MT stopped using their proprietary wireless driver (which was simply not up to ac and newer chipsets and modern features like WPA3, FT, etc.) and switched over to wireless chipset vendor’s driver (so far Qualcomm). The feature set of both drivers is pretty distinct (e.g. no more nstreme / Nv2, no more detailed wireless measurements, no more non-standard channel widths, etc.), so it’s impossible to expect any kind of backwards compatibility when it comes to configuration. And thus need for new capsman … which also lost quite a few functionalities (such as CAPsMAN forwarding), but added some new (fast roaming).
Many ac devices (hAP ac2, hAP ac3, Audience, …) were transitional … so you can choose which wireless drivers you want to run (legacy wireless or new wifi), newer devices are not supported by wireless any more.
As I already hinted in my previous post here: you can run capsman (unless you heavily rely on CAPsMAN forwarding) on almost any legacy device. So you can continue to run your 5 “capsman slaves” by using one of those slaves as capsman, And use the upgraded/new device as new capsman for new devices (which I hope will come into your network). The benefit of running single capsman is configuration in one place. But (apart from capsman forwarding) legacy capsman doesn’t affect CAPs operations any further. The new capsman does offer advanced mobility, but that advanced mobility is only available for CAPs running new wifi drivers, mobility towards the rest of APs is just like it’s now between CAPs.
Firther development of the proposal in previous paragraph is to upgrade the “new legacy capsman device” to v7 … it will continue to run legacy wireless drivers (when running v7.13+, it’ll actually have “optional” package installed) and will continue to act as legacy capsman (even for CAPs running ROS v6). But by running ROS 7.13+ it’ll be able to act as capsman for new (wifi) devices … as capsman functionality is part of core ROS now. So you’ll be able to configure both parts of your WiFi network on single device … but still in two different configuration subtrees (legacy capsman: /capsman … new capsman: /interface/wifi). This won’t make both parts of WiFi network any more integrated than by running two different capsman devices though.