confirm that it works. Moreover, it works also for the new wAP AC (RBwAPG-5HacD2HnD). [IPQ-4018 CPU] it is in 1:1 correspondence with the cAP AC model (except that you can also power it via DC jack and it has an IP54 protection)
as far as I can see the new wAP AC is also not listened in openwrt.org. Not sure whether a separate entry is needed, since the procedure and builds can be taken from cAP AC
I tried a few of the builds mentioned in this topic and I found the WiFi connectivity unreliable, especially for 5 ghz, where I get disconnects as soon as a bandwidth brust takes place (for instance, when testing download speeds).
The LEDs are not working properly as well - the power and red leds stay solid on (but we can make them blink using custom led configs), the other ones won't work.
Any ideas are welcome and many thanks to the contributors of this effort -- cAP AC will most likely not work with MT's new wave2 drivers and it's users will only have OpenWRT as an option for proper 802.11r (among others) support.
In terms of makefiles producing images, probably no. Are even LEDs the same? Does the board description need editing so right information is shown under System luci tab?
In terms of tables and wiki pages, yes. It needs entries in order to be discoverable as supported and so users know which images to use and so people have a pointer to known working flash instructions. (ie. common tftp instructions).
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?
Half year ago I successfully flashed OpenWrt to one cAP ac /r2. Now I bought an other model and cannot perform netboot of the initramfs image: It starts like
Made a clean install of the ROS LTS 6.47.10 and was able to flash OpenWrt successfully.
Seems, that at the previous upgrade of ROS something went wrong for my device. Now everything is fine.
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?
Thank you for this information. Probably something was wrong with the way I've applied this build then. I just re-tested everything:
flashed Mikrotik's RouterOS back onto the device
compiled the new binary and tested initfarms image first.
Flashed the sysupgrade image onto the device and re-tested the configuration. This time I've got consistent results for connection speed and iperf tests.
Now just need to figure out how to completely remove router functionality and make it as a regular AP...
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.
You are right. I manage to recover it with netinstall. It just turns out that onboard Intel i219-v NIC in Thinkpad T14 g2 laptop doesn't like netinstall and I had to use USB NIC.