Horrible upgrade



  • Oh boy that was emotional! I upgraded from 1.2.3 to 2.0-RC1 and it did not go well.

    The web interface didn't load on boot (I had to start it manually) and outbound NAT broke completely. The default route wasn't added until I re-saved the WAN config. The NAT rules wouldn't reload properly because it was checking for hooks in the TFTP package.

    Having read http://forum.pfsense.org/index.php/topic,22158.0.html I deleted all my packages and everything seems to be working again now.

    It could be an idea, in future releases, to disable all packages on upgrade and make the user re-enable them all manually.

    Aside from that, it looks good. Nice work guys.



  • I can second the upgrade struggle…however I have done this with two different devices and one was super smooth -the other did almost exactly what you described Phil.

    I have since removed any packages prior to upgrades and so far it seems to work pretty solidly.

    Dayblade



  • I added a note to the upgrade guide that users may want to uninstall packages first when going from 1.2.x to 2.0. There are some packages that cause problems and there's no way to go back and change existing installs to fix that, by the time the new version is running it's too late in some instances (though we've worked around that as much as possible).


Locked