It’s possible to downgrade as low as factory version. This depends on manufacturing date of a particular device.
Apparently I’m doing something wrong. Tried with downgrade option but no success.
Did you follow the steps from https://help.mikrotik.com/docs/display/RKB/Downgrading+RouterOS ?
You have to upload npk files to device and then hit the downgrade button. When ROS sees npk file, it tries to install it at reboot … if it’s system package and the version is higher than currently running one (or if it’s additional package with version same as running one). But won’t install it if version is lower than current one … unless you hit the downgrade button. But hitting downgrade button will not download older version for you.
I’ve uploaded routeros-arm-6.49.11.npk, hit downgrade button, LHG reboots with 7.13 version
If you have another packet except the main uninstall him first. Then make downgrade procedure!
Well, probably nothing wrong from the manual perspective. I’m looking for step-by-step guide for both modes of particular device, which has a bit tricky default config even with old drivers. I’m eager to try new driver but I don’t have too much resources for tinkering and guessing the best configuration. There probably should be optimal configs the team used for testing purposes. I see no harm to share them publicly. How do you feel, does it make sense?
Thanks m8, that did the trick !
By the way, is there likely benefit for PtP link between 2 LHG XL 52ac, to go from 6.49.11 to 7.13, considering wifiwave 2 is available now ?
It can be that they don’t support chunking on the moment. However the script can be changed now the file can be downloaded in one go and the then read from disk in chunks of 32KB. Two chunks is 64KB or just double the loops to import the complete file.
Now empty “WiFi” tab in WinBox. And working WiFi tab copied to “Wireless”.
Upgraded D53G-5HacD2HnD successfully. Then I uninstalled wireless package und installed wifi-qcom-ac. LOL, I was astonished as there was not even a default configuration in place for the wifi. Just two disabled interfaces. ROFL, and I had the naive hope that MT transforms my legacy wireless config to the new wifi config. But wasnt that hard to setup manually. I even tried Quick setup out of curiosity to setup some defaults - but that failed hard as a rock. QS created two new interfaces for guest wifi (wlan3/wlan4) but failed to configure wlan1/wlan2. They remained inactive without any configuration. Well played, MT. I was lucky and QS did not destroy anything else according to a export-diff.
One suggestion though: wifi log messages still use the “wireless” prefix. MT should maybe align that so it says wifi there too.
Upgraded a green field RB4011iGS+5HacQ2HnD from 7.12.1. I simply do not have any wireless or for that matter wifi topic logs even with debug enabled.. Which I really need as the 5GHz interface and or config is not working.
Tnx!
I am asking the representatives of Mikrotik to define for me what they mean by the term “stable”.
I have a Mikrotik remotely halfway around the world. Once I had to go to a site and install via NetInstall when there was a transition from version 6.x to version 7.x. Now it hasn’t even gotten to the 20% newer major next version (8.x) and again the device won’t boot after upgrading from 7.12 to 7.13 and I’ll have to fly halfway around the world again to do the Netinstall in person and who knows if it will reinstall.
Paradoxically, this is an Enterprise environment with a professional range of routers, and I cannot afford downtime for entire companies. Older configurations for LTS versions no longer work, where I am told that it is necessary to upgrade to version 7.x, where the settings and scripts work, but security is not ensured even to the extent that the device does not boot at all after the version update.
I don’t know what the problem is anymore. Maybe I’m misunderstanding how the company Mikrtoik interprets the term “stable” version, so I would like it if the engineers from Mikrotik would explain to me how they understand this term. Thank you
And then I want to ask what are the 5 levels of RouterOS test versions for, if this happens in the production version? What is the goal of the test versions?
I have updated my RB5009 and my CRS326-24G and my scripts for Telegram are not working as expected. I am not getting any message more than the download message with the Chat ID.
I will be rolling back to version 7.12 if this not going to be fixed quickly by Mikrotik
Another issue: I tried to downgrade to version 7.12.1 and also doesn’t work!! I just uploaded the RouterOS 7.12.1 ARM64 into the /files of my RB5009 and went to System → Packages → Downgrade and the router refuses to downgrade. Reboots and nothing happens!.
I am so annoyed! and first time I have this kind of behavior. I am getting now messages every min in Telegram with non–sensical messages.
Hi!
I have upgraded from 7.12.1 to 7.13:
CRS326-24G-2S+ X2
CRS317-1G-16S+
CRS305-1G-4S+
CHR (esxi 6.5.0U3)
No issues
I have an issue with 7.13 that 7.12.1 didn’t have (nor before) - I have a bunch of 1gb SFP’s in a CRS328-4C-20S-4S+ switch. None of them will link up auto negotiation at full duplex (they are all fiber). I can hard code both sides of a link and it works full duplex, but with auto negotiation duplex is never picked up and you end up with hundreds of “sfpxx excessive or late collision, link duplex match?” errors and most paths not even passing traffic. Downgrade to 7.12 and it auto negotiates correctly. My 10GB SFP+'s are auto negotiating, only 1GB SFP modules are failing to.
Who maintains physical hardware halfway around the world - as a sole person / without closer person to perform actions needing aphysical access?
Like, you blame MikroTik, but you’ve chosen a low-cost platform and at the same time you’re going low-cost on people, that you don’t even have people nearby the devices you maintain.
MikroTik doesn’t do your business, you do. Even in 10person company no sane person installs version less than 24h old into production. Person who decided that upgrading distant system without test env or local support is a risk for the business.