-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mikrotik QRT5 RB911G-5HPnD-QRT #586
Comments
This hardware is not supported by the current version of OpenWRT, so someone would need to donate hardware so we can do the port. |
This device used the old Large firmware. |
Are we talking the N or AC version? The N was previously supported. |
The N version was supported on the old ar71xx target which OpenWRT removed. Everything needs to be ported to the ath79 target and this has not been done for this device. That said, the 911 devices are very similar to the 912 devices, and I did the 912 devices already. So .. if someone wants to donate hardware it can probably be done (see my original comment). |
I don't know which one it is. Can't tell by the specs on Mikrotik's site. |
RB911G-5HPnD-QRT "QRT 5" N version. Supported on 3.22.12.0 If you already have one working, it's the N version. |
Firmware CANNOT be updated
Are we going to have to do like the Basebox (912) and load as new? |
Confirmed same error here. Same strings as above. (This is the N version). |
As noted in the supported device file, you cannot update but must reinstall. This is a limitation on all nand based Mikrotik devices transitioning from the older version of openwrt. |
The QRT only has unknown release. Doesn't say reinstall. |
Reinstalled without issue. So far so good on live mesh. |
Same as AJ6GZ...Reinstalled as a new device without issue and installed iperfspeed as well. Seems to be working correctly. |
Thanks - looks like I messed up where I put the re-install in the SUPPORTED DEVICES file - will fix it. |
Are we going to get firmware for the Mikrotik QRT devices?
The text was updated successfully, but these errors were encountered: