Nanobsd system upgrade from 2.0.2 to 2.0.3

  • Hi,

    I plan to perform a system upgrade a nanobsd 4g system (i386) from 2.0.2 to 2.0.3.
    Did anyone experienced any problem? I am using ipsec, ADSL connection, and basic
    firewall features, src nat. (no internal services etc.)
    I would like to use auto update.

    This is what I see under Auto Update:
    A new version is now available
    Current version: 2.0.2-RELEASE
      NanoBSD Size : 4g
           Built On: Fri Dec  7 16:30:51 EST 2012
        New version: 2.0.3-RELEASE



  • Netgate Administrator

    You shouldn't have any issues. I didn't on any of the boxes I manage, some of which have far more complex setups than yours. I don't run IPSec anywhere though but there are many who do and I haven't seen many complaints (or didn't a while ago when 2.0.3 was released).


  • Thanks.

  • Rebel Alliance Developer Netgate

    I've upgraded close to a dozen NanoBSD boxes in the last two weeks from various starting versions (1.2.3-RCs, 2.0, 2.0.1, 2.0.2) all up to 2.0.3 and they all came through fine, no problems. Some had IPsec, some had OpenVPN, some even had several packages installed.

    I wouldn't expect any issues in most cases.

  • my 2cents: make sure you take a config backup just before upgrade.
    I have done 2 nano upgrades as up today, this morning mine at home (alix) and just this one asked a bit more attention.
    -> after the auto-upgrade, it reverted to default config ?! (original ip range, pwd & gui setup walk-through) Glad I took a backup just before upgrading…

    Easily fixed, just restore by the xml & everything auto-magically is restored on the new 2.0.3 (including packages & OpenVPN config's)
    Nice touch from the guys@pfsense  8)

  • Rebel Alliance Developer Netgate

    Were there any errors on the console or in the system log on the one that reset itself?

    After dozens of ALIX upgrades to 2.0.3 and countless more done by customers, I have never heard of that happening to anyone.

  • Hi Jimp,
    I was surprised as well, as the previous one went flawless.
    No errors seen. I was not monitoring console, everything went through webgui. Did not bother to go looking in the logs, as it looked to be set to factory defaults?
    I just went through my syslog (pfSense nano seems to be limited to 2000 entries), no errors. Judging by the log, all went fine. If you are really curious, I can send or attach part of my syslog server entries. There is still the part of upgrade until reboot after upgrade. I'm missing part of course where the pfSense's IP range was wrong (default), up to where I have done the restore.
    If you want other info, I'll be happy to provide any log you want, just let me know.

    PS: don't know if it is related, but while checking those logs, I just noticed I have a new issue: lots of NSSWITCH entries in my syslog  ??? I seem to remember that was reported here by other users, need to check…
    [edit: not related & already fixed by your workaround from april 26th 2013]

Log in to reply