To upgrade, click Check For Updates under System/Packages menu and select the long-term Channel in RouterOS configuration interface, or head to our download page: http://www.mikrotik.com/download
Everything went smoothly
I encountered an issue after the update (please post about the device, configuration, and unexpected symptoms)
I encountered an issue, but solved it (please post the solution)
0voters
If you experience version related issues, then please send supout file from your router to support@mikrotik.com. The file must be generated while a router is not working as suspected or after some problem has appeared on the device
Please keep this forum topic strictly related to this particular RouterOS release.
I'd really wish Mikrotik did a Change log from the previous long term to the latest Long Term so we didnt have to piece together our own collage of release notes. its not the end of the world and other vendors are guilty of it as well but when they're consecutive dot point releases they are easy to follow, when they jump from 7.21.x to 7.23.x then to 7.24.x it is a little harder to follow as the change log can consist of stable and long term elements in the period between.
I'm guessing too, but I'd like to know for sure. If it were clearly written in the changelog, there wouldn't be any question.
It is also completely unclear when you need to update the bootloader and when it is not necessary. Because two reboots take longer on critical objects. Why not update the bootloader in one reboot after so many years is also not clear to me.
The thing is currently bootloader version number is not in sync with bootloader version and in many RouterOS releases there are no changes to bootloader code...
I prefer previous practice when bootloaders used to carry their own (actual) version numbers so one would know exactly when to upgrade...
There are questions here. If updating the bootloader is important and officially recommended, why isn't it forced and updated in a single reboot? It's a strange decision to leave the old bootloader by default, allowing the device to malfunction. And no one can say exactly how, because the bootloader can differ from the firmware in any number of ways, and everyone's experience is different.
Okay, so let's say I decided to strictly follow the official recommendations despite the default option to not update the bootloader. Can I do this in a single reboot along with the firmware update to minimize downtime? As far as I know, no.
The bootloader doesn't suffer modifications at every release (they are mentioned in the changelog if any), the version of the bootloader was detached from the RouterOS version in the past but someone decided that it's best to keep the versions in sync so every RouterOS since then has a "new" bootloader even if the only thing changed is the .. version.
That's exactly what I'm saying: this doesn't make sense, and it would be better to update the bootloader version only when there are real changes (like firmware for LTE modems), or at least update it automatically along with the firmware during a single reboot, so that the versions are synchronized for all users. This makes sense, but for some reason it's done the other way around.
If you want full changelog you go from 7.24 to 7.24.5 and then append 7.24.6 changes here, making sure to remove any double entries in (7.24..7.24.5) for fixes that were backported to previous long-term train. Or you could just switch to stable, because long-term is just oldstable and seems to last for exactly one version anyway.