If you’re asking this, then perhaps you should be asking yourself: “why am I using Mikrotik products?”
You always have to ask yourself if you trust producer of certain item that that item is fit in all aspects to be used by you. And if you answer with kind of a “yes”, then you should probably trust producer about future products as well. If you loose the trust, then probably the reason for loosing trust existed long before you lost it.
For example: if you think that MT introduced something evil in 7.2.1, then I guess you have no reason to believe 7.2 is any better … or 6.48.5 for that matter.
Or, you can do what many people do: wait for some brave souls to install and test it and report the experience. And then decide if you want to install it (if you believe that reporters are true with their reports).
I do not mind testing it, just the description is too vague to understand what was broken exactly. Could you describe a scenario that would break the router with 7.2?
@mkx
That is unfair and wrong. You take my argument and inverse it.
Anyone can update on “stable” channel without actually knowing the exact information to all the fixes. all you need to know: “i do my stable updates when they are available and known to be “safe” from reading this forum. Update to be up2date”
But testing release? "Hey folks, we have a testing release. We improved something. Some stability. Can you please give feedback about? on what? feedback on “improved stability of filesystem”? Is there not any further information than “improved xyz”? Is it that crazy to ask this question in a TESTING release thread?
If you experience version related issues, then please send supout file from your router to > support@mikrotik.com
How can ANYONE give serious feedback to this question?
When there is ONLY A SINGLE CHANGE, then I install this testing-release. I can have a SPECIFIC look on the change and can tell: “yes, it indeed improved the stability for this before instable behaviour” or I can report “no, this change did not improve stability”.
But it here is like: “I installed 7.1.2 and I do not see any difference/improvement/change to 7.2. It W0rKs!!11!11!!”
ontopic: Probably related to the config-corrupted-after-update that’s been around the forums lately?
offtopic: Unfortunately MikroTik doesn’t reveal the full changelog vs 7.2, again.
Comparing files you’ll see differences in files like capsman.ko, wireless, ipsec, profiler, libcrypto.so, a lot of webfig(?) .info files that were still showing 7.2rc5, a lot of kernel modules but I’m sure there’s just a version change there, maybe except sch_agr.ko and sch_sfq.ko which seem to have a little more diffs (probably still related to versioning).
So… which is it, MikroTik? only version change in those files or maybe something else was fixed/changed too?
Thank you!
For starters - this fix has nothing to do with the problem that some rare routers lose configuration after an upgrade. Still with all of your reports to support. we have not managed to reproduce the problem. As we thought before, most likely this problem is already fixed and affected are only routers which had some bad version installed on the in the past. Every by importing backup made before failed upgrade on another upgrade configuration is not lost.
Regarding this particular release - it fixes a very rare situation when a router could brick itself during the upgrade process by removing/corruption filesystem so the device could not read system files anymore. The router had to be get netinstalled. Now, this particular case is fixed. We decided to better release this fix as soon as possible rather than keeping it up to our sleeve. Since the fix is safe and could help some people to avoid unnecessary travels to their server rooms we released it in the testing channel. If no unexpected issues will be found, we will release it in the stable channel as an improvement, not an update for 7.2.1. This release has nothing to do with the 7.2 release. Simply we found this issue and fixed it just now.
Thanks Strods, this gives clarity about the update and gives me hope to leave RC for, maybe testing. To me, it is still a fix to 7.2 and previous versions.
Doesn’t help. I’m guessing this affects only v7 but it would be nice to know for sure, and whether this will be backported. I’ve lost at least one 6.x device after a failed upgrade.
Is this filesystem configuration change as opposed to completely changing filesystem from ext4 to btrfs for example? What filesystem is RouterOS using?
I for one am very happy with all the changes and continued improvements of Router OS 7. Just did the upgrade on one of my CCR2004 and from upgrade back to forwarding and management was less than 22 seconds. Try doing that with a Cisco
I second that, I am a newcomer to Mikrotik, just a few months. Coming from 2 Ubiquiti edgerouters my Rb5009 and a HAPac3 a working perfectly and I am glad I am receiving updates instead of waiting months and months for a small update from Ubiquiti.
Both devices are upgrading in mere seconds (<30S)
[quote=CAMARO1437 post_id=925806 time=1649683567 user_id=165943]
I want to change my RB2011 router for CCR2004-16G-2S+ could someone tell me if this works with RouterOs Version 6?
[/quote]
As it says on that product's [url=https://mikrotik.com/product/ccr2004_16g_2splus]specs page[/url], it's v7 only.
