2/2/2024 0 Comments Mikrotik minbox refused on wan![]() ![]() My money is on the problem existing in RouterOS v7 core software itself, in some new function somewhere, and that it still affects even latest versions and could strike anyone at any time regardless of past versions installed if they just meet all of the right conditions to trigger the bug. I suppose one thing we can already know with certainty that the problem doesn't stem from RouterOS v6 or lower, because RB5009 can't run that anyway. But in that case, Mikrotik should focus attention on comparing disk images structure from a device known to be prone to this config loss issue (such as my RB5009), against a similar device which has been freshly wiped with netinstall ![]() If it's a disk partitioning issue, then that is another story of course. Is this somehow analogous to a Microsoft Windows Registry retaining entries from past OS revisions even if they are no longer in use? Surely if "/export" can provide a full, clean and sanitized output of the device configuration, then it should be possible for the router to clear extraneous/problematic configuration using similar functions to sanitize the current device config, negating it of any possible noise/interference? Furthermore, restoring that export on a device which has just been freshly wiped with "/system reset-configuration", should mean that this "registry" starts off with a clean state and that again, no prior installed RouterOS versions should have any effect on device stability going forward (from a config perspective). To what extent does RouterOS store past version configuration and to what extent can that configuration (which should arguably be rendered inert) still be able to influence/affect device operation when running on a new version? Are we talking about actual configuration, or just the underlying disk partitioning/layout? Can a Netinstall fix all of this or not? If MikroTik wants our assistance with this, we need some guidelines on where to look and how this important aspect of device operation and configuration integrity, operates beneath the scenes I'm surprised there's not already more noise about this. We should really not be comfortable with the notion that past versions of software can influence current device operation on latest installed software version. to find out which old version went haywire (if that's indeed the case) and to try to fix it so that when mass of less ssvvy users start to upgradevfrom v6 to v7 they don't fail miserably. I guess this is the very point of this thread. Is there any way to know if a given router is affected by some bad RouterOS version of the past? Thank you very much already ahead of time! We do believe that the issue might be already resolved and affects only routers which have had some "bad" RouterOS version installed on them in the past. Report only if you are 100% sure that this is the case of missing configuration. For example, it was not lost due to a safe mode being enabled, some other administrator making changes on the router, etc. Please keep this topic strictly related to this problem and provide information only if you are 100% sure that the configuration indeed was lost. Try to notice if the configuration indeed was lost or simply was returned back to the configuration which was present on the router in the past. If you do send a backup, then please also let us know how to access the router (username, password, IP address, interface to use). Provide supout file (generated when the configuration is lost) and if it is a possibility backup file (before the configuration was lost). Let us know which part of the configuration was lost. Please write an e-mail to and send a list of RouterOS versions which you have used on this router ever before and are using now. If you have experienced such a problem (after an upgrade or reboot) then please let us know about it. Currently, we have tried everything that we can imagine and have not managed to reproduce this problem in order to resolve it. We are not referring to missing IPsec configuration or missing routing tables. We are aware that there is some kind of an issue in v7 of RouterOS when in some very, very rare cases and under unclear circumstances part of the router configuration is lost. This time here is a topic from MikroTik asking for some assistance. Hello, all of our trusted MikroTik users and fans.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |