we have not managed to reproduce the problem. Still with all of your reports to support.
Still too scared to try any remote devices for now, I'll think about it while waiting for some more more forum comments/feedback 😂įor starters - this fix has nothing to do with the problem that some rare routers lose configuration after an upgrade. Results are looking very promising thus far. Update: successfully upgraded my home RB5009 plus a few other local devices without any data loss thus far (Yipee!). Maybe you can just help us weigh out our options and point us in a preferred direction depending what scenarios we are already in, given the potential significance this single issue (or its fix) can have. The only hint we have right now is the use of the word "improved" rather than "fixed" in the changelog and even that is quite vague as it doesn't really convey the extensiveness of the changes. Is it worth upgrading potentially dozens/hundreds of routers already on 7.2 to this new release or is it only recommended for new upgrades? Is this patch intended to fix the corruption on upgrade/reboot issue, or is it a broader & more general change which may or may not have this effect and we will just have to test? Any hints or pointers to address these types of questions will be greatly appreciated. I just want to know if it would be possible to maybe share some more information about what was fixed/changed with this update? We obviously don't have the same insider information as RouterOS developers so we don't know how impactful this change could really be.
Thanks Normis, strods & whole Mikrotik team working on this issue, some of whom probably had a busy weekend hunting down bugs (more like finding a needle in a scrap yard with this one I'm sure) for the rest of us.
0 kommentar(er)
