Still at 2.0.3, wonder if I really need to update. And will it work ;-)

  • My small pfsense machine is not the normal one type

    I installed it at my friend Camping and it is managed from outside of the local network.. let me explain.

    the main internet connection is a 25 mbps cable modem used for both the pfsense and the local family that run the camping. the pf sense machine is behind the main router used on the cable modem connection. So I had to open a port on the wan side of the pfsense machine to connect to the web page to configure it.. (did not used port 80) so to maintain the pfsense machine they enter an adress like that: pfsenseipadress:port, same for the people inside the captive portal they cant log to the administration page.

    Now it took me some time to do that and I am also managing the machine from remote cause they are not very tech savy. If I do upgrade remotely the machine to the latest version will I loose all that configuration? Is there a way for me force the reloading of my configuration in case its wiped out by the update? will I need to update to each version that was released before doing the next?  Lot of question.. I know..

    Thanks for time the you will take to help me.


  • here is the system information from the dashboard.

    Name pfsense
    Version 2.0.3-RELEASE (i386)
    built on Fri Apr 12 10:22:21 EDT 2013
    FreeBSD 8.1-RELEASE-p13

    Update available. Click Here to view update.
    Platform pfSense
    CPU Type VIA Eden Processor 1000MHz
    Hardware crypto VIA Padlock
    Current date/time
    Fri May 30 18:55:06 EDT 2014
    DNS server(s)
    Last config change Mon May 26 18:06:46 EDT 2014
    State table size
    Show states
    MBUF Usage 390/25600
    CPU usage left barred bargray barright bar 
    Memory usage left barred bargray barright bar 
    Disk usage left barred bargray barright bar

  • Netgate Administrator

    You should be able to upgrade directly to 2.1.3 and not loose any config.
    As with any upgrade you should backup your config file first and read this:

    If your upgrade goes badly for whatever reason you will loose remote access to the box so you would then either have to go there yourself or be able to talk through someone on site to restore the config file. It might be better to wait until you're on site to do the upgrade.

    As a side note you should probably configure a better way of accessing the box than using the web gui directly on WAN like setup a VPN connection for example.


    Edit: typo

  • Banned

    The upgrade goes fine here…

    2 things.

    Widescreen back to two columns. If you can live with that, then fine.

    Save GUI settings doesnt work here.

  • I have one of each. Honestly, the 2.0.3 system is still slightly more stable in my application. Both are x64

    In particular, large squid cache seems to be handled much better by it. Hardware is identical, but the 2.1.x system was running into swap where the 2.0.3 system never does - I've had to reduce the cache size on the 2.1. system several times and it still gets there sometimes. Squid is a big factor on my crummy connection with too many users, so that's not an improvement.

    2.1.3 has a nicer look (colors that are not all shades of red you can't tell apart in the RRD graphs, for instance) and provides handy things like CPU temperature on my system, but I haven't seen anything functional to recommend it over 2.0.3 as yet. I'm contemplating a back-grade, actually, but have been giving it time to mature - earlier versions of 2.1 gave me fits with not starting NTP reliably, and that seems to be better at 2.1.3, for instance.

  • Netgate Administrator

    The biggest update for 2.1 was the vast amount of work that went in to get IPv6 functioning. It wasn't the only thing though:
    More has gone in since for 2.1.1, 2.1.2 and 2.1.3.