I built w/ the patches provided @alaraun and it now seems to work fine, including the leds, many tx!
However, I can only boot with the backup boot loader (holding the reset key while resetting). The routerboard had the firmware upgraded to 7.1b5 before flashing. This is a showstopper as the router will be installed in the ceiling.
Any ideas? Shall I try to netinstall and then downgrade the firmware? Maybe the newer bootloader will not work w/ the sysupgrade image installed after the netboot?
First of all, thank you very much for this! I've been using alaraun's PR and was able to install it onto my Cap AC unit quickly.
I've noticed the device connection speed (5GHz WPA2 AES) is very different whether you use OpenWRT version in-RAM or the flashed one.
OpenWRT running in memory:
For default (00) country my iPhone connects at 780 Mbit/s.
For US, iPhone and Android phones constantly connect at 886.7Mbit/s.
OpenWRT flashed onto Cap AC device
For US, iPhone connects between 351Mbit/s and 650Mbit/s. Most of the times, it is 350Mbit/s or 520Mbit/s.
Is this common? I've compiled my initfarms and sysupgrade images from the same commit. The different between installations is that when I flashed OpenWRT onto the device, I've also connected it to my router to get the access to Internet.
Another thing I'm having issues with is getting my Cap AC device to act as a regular AP. I want to be able to extend my router to the wireless devices and bridge both ports on my Cap AC so that I can just use 1 network cable for power and management.
Could someone share their working configuration here?
Here are my configuration files for a regular access point.
Management = vlan9
Trusted network = vlan10
Untrusted (guest) network = vlan11
Please, avoid using vlan2 in your configuration.
In my setup I reduced the "Maximum transmit power" value to 6 dBm (2.4GHz) and 13 dBm (5GHz) to improve roaming between four APs.
Current firmware version: OpenWrt 21.02.0-rc3 r16172-2aba3e9784
I did not try OpenWrt 21.02.0-rc4 yet.
Could somebody please share original SPI flash image for CAP AC?
Somehow I manage to brick it while upgrading RouterOS, now I can't boot it via recovery mode but I'm hoping to flash it with SPI programmer to reveal it back to life.
I don't have a Cap ac, but hopefully you won't need an image.
Mikrotik Netinstall can be tricky. The timing is slightly longer than shown (for the bootloader before RouterBOOT), so watch the LED to confirm.
First, reset the RouterBOOT soft_config settings. Do this by holding the reset button during boot time until LED light starts flashing (~5 seconds), then release.
RouterOS should not normally touch the qcom bootloader, routerboot hard_config, or routerboot backup bootloader (which can be used by starting to hold the reset button before power is applied).
If the LED does not respond as expected at boot with reset button held (5 seconds blinking (reset settings), 5 more seconds solid (capsman), 5 more seconds off (netinstall)) then you likely have an issue with bootloader or hard_config bits on your SPI-NOR. If the problem is caused by something done from RouterOS, you are better off asking Mikrotik support, or your distributor, as hard_config contains device-specific settings, and Mikrotik does do silent hardware revisions.
If the LEDs are responding as expected, watch the WAN port with tcpdump or wireshark after 20+ seconds of reset button.
Since the wAP ac is identical to the cAP ac, except for the missing LED's and the possibility to power it also via DC jack, I previously installed successfully @hmpfe's build for the hAP ac2, see above. Now I wanted to try your build. It boots the initramfs image via TFTP without any issue, but I cannot flash the sysupgrade image using "sysupgrade -n". I also tried to start from various ROS 6-versions. [Surely, your image works fine for the cAP ac.] The reason I'm writing, is just to understand why the build does not upload to the wAP ac, although they are identical. Do you know what could go wrong with the wAP ac?
I merged @alaraun's PR on 21.02 release. Seemed like minimal fuss to get it to compile, just a patch with a bad header.
system boot's and seems stable in its default configuration.
but i can't get VLAN's to work. I've spent many nights on it - i'm still not convinced it isn't me...
my last attempt however, I had port 2 (eth0.1) with a static networkable address which i've been using to configure br-lan with port 1 (eth0.2 (yes confusing)) and turning on VLAN filtering in the bridge (br-lan) kills both ports even though port 2 (eth0.1) is not in the bridge (br-lan).
so i'll have to reset it again to continue.
i'm really at a loss here. I have 3 cAP ac, and 4 other mikrotik switches. i'm convinced my wifi issues would be resolved with non mikrotik drivers, but mikrotik's wifiwave2 (not mikrotik drivers) doesn't look like it will come to cAP AC, even at the recently released 7.1 (testing) where i'd have thought debugging stuff would come out (so smaller) there still isn't any push for 128MB devices like cAP ac.
I went for mikrotik so that I would have some continuity in my network configuration.
it hurts a bit when I look at other wifi solutions such as TP-Links OMADA and see how I could have had more integration between switches and access points. all under one hat.
so that leaves me with having OMADA for wifi, and mikrotik for switches. could be worse i suppose.
openwrt at least would have soften the blow as I would not have had to fork out. OMADA is gonna cost £450 (3x 620HD)
openwrt feels so tantalisingly close. WiFi 5 wave2 would have been a sweet upgrade from stock.
Many others have been able to use VLAN, so it is most likely a configuration problem. This platform does not have a DSA switch driver (yet—in development), so you need to configure the (cap ac SoC hardware) switch and ports with switch_vlan stanzas, as well as the software bridges. Very similar problem here: VLAN configuration issues on 21.02 Mikrotik device (non-DSA switch setup) - #6 by johnth. You will need to provide more details of your config or wanted setup if you want specific guidance.
These (swconfig VLAN) numbers come from the switch_vlanoption vlan. You can change them if it helps you.
If the changes were in master when 21.02.2 was released, then does that mean cAP AC's are now supported (to some extent)? If so, the device page might need updating to indicate the progress on supporting this device.
I might try flashing this to one of my cAP AC's tomorrow unless folks recommend against. I'd love something with 802.11k/v/r support.