Page 1 of 1

2.9.49 (or 50) to 3.1 stable upgrade..

Posted: Tue Jan 29, 2008 10:20 pm
by billr
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.

Many thanks all.

Re: 2.9.49 (or 50) to 3.1 stable upgrade..

Posted: Thu Jan 31, 2008 10:05 am
by billr
Many views but no comments..

Please people, could someone comment and hopefully confirm I can upgrade (relatively) painlessly..

Many thanks, Bill

Re: 2.9.49 (or 50) to 3.1 stable upgrade..

Posted: Thu Jan 31, 2008 10:37 am
by cmit
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...

Re: 2.9.49 (or 50) to 3.1 stable upgrade..

Posted: Thu Jan 31, 2008 11:33 am
by billr
Hi and THANKS !

I have several systems with 2.9.46 and 2.9.49, and nothing lower.
So from what you say, it looks like I can go ahead.

Much appreciated..

Cheers, Bill.

Re: 2.9.49 (or 50) to 3.1 stable upgrade..

Posted: Thu Jan 31, 2008 2:39 pm
by cmit
Stop! ;-)

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", ...).

Re: 2.9.49 (or 50) to 3.1 stable upgrade..

Posted: Thu Jan 31, 2008 3:15 pm
by macgaiver
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.

Now you can upgrade!

P.S. cmit - just keep it simple ;)

Re: 2.9.49 (or 50) to 3.1 stable upgrade..

Posted: Thu Jan 31, 2008 5:00 pm
by cmit
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.

But probably I got misunderstood ;)

Re: 2.9.49 (or 50) to 3.1 stable upgrade..

Posted: Thu Jan 31, 2008 6:08 pm
by billr
Hmmm..
Thanks again.

However, all I have are X86-PC systems running 2.9.46 or .49 RouterOS.
There - is it safe to simply FTP the .npk file to them for upgrade?

I am *not* talking about routerboards or WRAP or anything similar.

Cheers again.