CAP ac wifi and updates shenanigans

Hi everyone, I just need to vent a little.

I've purchased MikroTik products several times in the past, and I've never had a single problem. They've always been excellent. This is the first time I've bought MikroTik Wi-Fi routers specifically, in this case two cAP ac RBcAPGi-5acD2nD units, according to the box.

I've been struggling with these things for the past five hours. They show the Wi-Fi lights as active, but no device can see the wireless network, even after verifying that the SSIDs are enabled. I've also had trouble updating them, and several times they've ended up completely dead, requiring Netinstall to bring them back to life.

Only to find out that the stable updates the router itself finds apparently exceed its storage capacity, causing it to break.

Then there are random Wi-Fi disconnections whenever I actually manage to find the network, which, by the way, seems to work only when I add it manually.

Honestly, I'm pretty disappointed with these routers. It's a shame because I really like MikroTik as a brand, but I'm seriously trying to restrain myself from smashing these things to pieces with a hammer.

If anyone has experienced similar issues and found a stable RouterOS version that doesn't cause so many problems with these routers, I'd really appreciate it. And thanks for letting me vent.

Greetings from Argentina,
Mauricio.

Why, seriously why would anyone ever buy a cAP ac, its two whole generations behind wifi AP.

It has insanely low amounts of both RAM and flash (16MB? seriously? people are having to netinstall them...).

Not to mention 2.4ghz is wifi 4, and only 5ghz has wifi 5, speeds are miserable.

Only valid reason to get them over cAP ax's is the size of cAP ax's form factor.

It is known how bad they work with cap/wap ax lineup and that you have to jump through hoops to get them working together nicely.

You would be better buying two of the current generation cAP ax's (they are only 20$ more expensive than cAP ac...) and wait for a mature wifi 8 alternative, considering how disappointing wifi 7 lineups are, its only a speed bump nothing else.

Even if you absolutely HAD to buy something you would be 100 times better off buying a random router and putting it into a access point mode and saving up for a up-to-date cAP ax's.

Do research before buying.

Stop buying cAP ac's there is NOT A SINGLE GOOD REASON FOR IT.

I take it that you are trying to use wifi-qcom-ac on these, and not wireless as "shipped"? If so, try the 25.1 release tree - it addressed the space issue somewhat. Otherwise, you can drop back to wireless.

I have hAP-ac, which should be the same basic thing other than form factor, and have never had an issue hearing it or a stable connection. I suggest that you check country and frequency/channels, since i have had, at times, Mikrotik stuff come up on the "latest and greatest" wifi frequencies that older clients can't hear . . .

If you are on wifi-qcom-ac in order to use "new" CapsMan, well, you kind of painted yourself into a corner on that one . . . The only option I see there is to user 25.1 - it gives back about 600K of space for the qcom driver.

Well, maybe if Mikrotik create WiFi6 AP that doesn't look like it could provide WiFi for the whole neighborhood maybe people would buy them... I don't have anything against cAP ac, it's older device for sure but it's still a usable device.

The CAP-ax is smaller than the WiFi-6 Netgears I replaced . . . not sure why anyone has an issue. More size == more antenna and less power consumed . . .

This thead might help you: Access points with KERNEL FAILURE - I'm going crazy

What you have to do:

  1. Upgrade to latest stable: 7.25.1: System -> Packages

  2. Download new wifi driver, upload to files and reboot: https://download.mikrotik.com/routeros/7.25.1/wifi-qcom-ac-7.25.1-arm.npk

  3. You should have 2 packages installed in System -> Packages

  4. Reset configuration: System -> Reset configuration

  5. Configure Wifi:

    A network provisioned to all radios

    /interface/wifi/network
    add ssid=MikroTik security.authentication-types=wpa2-psk,wpa3-psk security.passphrase=[:rndstr] datapath.bridge=bridge

    Set the regulatory domain of all radios

    /interface/wifi/network/radio add configuration.country=Latvia

Connect via Ethernet and check your wireless settings. Maybe you have misconfigured the Country and your Argentinian devices don't like that.

Why? What happened? Updating a RouterOS device, especially one with default configuration, cause no trouble usually.

This needs a proof. I don't believe you in this point. cap ac comes with routeros+wireless package. This means there is quite some free flash space. If you did not upload files, import a bulk amount of certificates, etc. to your flash storage within these 5h of initial setup, then there is basically no way to run into a storage-space shortage.

It is an access point, not a router. Sure it can act as one but it is meant to be an access point.

You did not say which version it came with, which versions you have tried. Just to ask this question. Please go into more detail what you did, what did not work and how your configuration looks like. Then someone can give you some kind of advice.

My advice is: netinstall 7.25.2 routeros+wireless npk, reset-configuration ticked. Start again.

It is a fairly well known shortcoming of this device that when the wifi-qcom-ac driver is used, the 16MB flash is woefully inadequate. Of course only this driver is compatible with the new capsman, but again there is a caveat: driver vlan tagging is not supported.

The space constraints are (for now at least) alleviated in the newer 7.25.2 release series, so try these. The most appropriate way to upgrade is using netinstall, exactly as you have found.

If the choice for a return is open to you, I suggest you would be much better off with the ax series devices...

It is also well known that this device comes with wireless package from factory. Not wifi-qcom-ac.

Yep. It also runs totally fine with the wifi package after the space saving repacking upgrade.

Anyway, the main point is that it's out of date. I'd only recommend it for replacing a failed device or extending an existing system.