Sorry if this has already been asked, (I am sure it has) but I can’t find a definitive answer..
I was around in the 2.8 days and upgraded to 2.9 with some pain (not all the rules carried across) - but that was around the time we were starting up as a WisP and we didn’t have too many rules to carry across )
My obvious question is - I have watched the development of V 3 with great interest, and have licences that are valid for upgrades to V 3.
I am currently running 2.9.46 or 2.9.49.
I would obviously like to upgrade BUT I would appreciate an answer:
do rules like NAT, MANGLE, filter etc etc carry across to the new version?
is the new version essentially a ‘superset’ of the old V2.9 ?
(what I mean is, do I keep all the old but get lots of new goodies - better wireless drivers, better packet filtering etc etc..)
Sorry if this has been answered in detail but I think (after people lost rules going from 2.8 to 2.9) it would be good to know.
All upgrades I have done haven’t been problematic so far.
One thing important for routerboards seems to be to have at least RouterBoot v2.8 on the systems before upgrading.
Otherwise we had some sysetm unresponsive after the upgrade (had to do a serial-port upgrade of RouterBoot and a
netinstall to get them running again).
What you should be aware of is that downgrading is not always possible without manual intervention (because the older versions don’t support some features from the new version.). So you could end up with disabled wireless interfaces or the like…
I did write RouterBOOT, which is the bootloader and something COMPLETELY different than RouterOS (which is the operating system that is being loaded/startet by RouterBOOT).
RouterBOOT is the thing you communicate with when on the serial console when the routerboard is booting (“press any key within 2 seconds”, …).
Just do “/system routerboard upgrade” from console and reboot once
I suggest to create a backup just in case of downgrade - then with one command you will be back where you was.
I didn’t say you HAVE to do a RouterBOOT upgrade via the serial port.
But if the system is unresponsive/cannot boot anymore, that’s the only way left to go.