Its possible to migrate from 1.2.3 to 2.0 ?
-
Im having some problems with 1.2.3 traffic shaping and Im considering a migration to 2.0 when release is stable.
Its possible to migrate from a working system 1.2.3 to a 2.0? with update from the web frontend?
does it keep al 1.2.3 config or there are any problems with something?Many thanks
-
It will keep your config when you upgrade. Right now I think there are some minor problems when updating to 2.0…
-
to my experience i simply restored my 1.2.3 config in 2.0 when the betas for nanobsd were functioning long time back and since then i never created a new config, always restored or upgraded and has been working fine so its worth a try at least.
-
Most of the 1.2.3 upgrade issues have been sorted out but there are still some (rare) issues.
For many people and configurations, it should "Just Work
" -
If you use NanoBSD, I'd avoid the upgrade.
I had a pretty simple setup, just firewall and NAT for one WAN/LAN, and tried last week. The thing blew up in strange ways that would be tough to file bug reports for but fairly easy for a dev to reproduce by, well, actually having a 1.2.3 setup and doing the upgrade.
I can only conclude that NanoBSD is still second rate in terms of testing/support, but things worked pretty well after recreating my config from scratch. RRD graphs are the only thing broken on the current NanoBSD images that I have experienced.
The painful upgrade was quickly brushed aside as 2.0 is awesome in terms of features and performance.
-
If you use NanoBSD, I'd avoid the upgrade.
I had a pretty simple setup, just firewall and NAT for one WAN/LAN, and tried last week. The thing blew up in strange ways that would be tough to file bug reports for but fairly easy for a dev to reproduce by, well, actually having a 1.2.3 setup and doing the upgrade.
I can only conclude that NanoBSD is still second rate in terms of testing/support, but things worked pretty well after recreating my config from scratch. RRD graphs are the only thing broken on the current NanoBSD images that I have experienced.
The painful upgrade was quickly brushed aside as 2.0 is awesome in terms of features and performance.
While it's true that this hasn't been well tested, it's not that NanoBSD is second rate in any way, it's the upgrade process that doesn't happen as often as it should. NanoBSD sees plenty of testing and support. :-)
Do you mind sharing the configuration you had which failed to upgrade?
-
I've had the same probs updating from 1.2.3 to 2.0. Simple config but blew up the router. It was not a nanobsd-upgrade, it was a normal instzall. Installing from scratch and configuring by hand was the only solution. I stated this here: http://forum.pfsense.org/index.php/topic,26536.0.html
I think that you may have luck or not.
My config was sent to cmb. -
I've had the same probs updating from 1.2.3 to 2.0. Simple config but blew up the router. It was not a nanobsd-upgrade, it was a normal instzall. Installing from scratch and configuring by hand was the only solution. I stated this here: http://forum.pfsense.org/index.php/topic,26536.0.html
I think that you may have luck or not.
My config was sent to cmb.That is probably a different issue. He forwarded me a copy of that config but I haven't had a chance to test it out.
