Version 2.2 worth it yet?



  • Quite to getting really involved with the forums for pfSense, and though I had v2.1.5 ready to go onto my x750e while it was being sent to me, I've now got 2.2 also.

    I'm seeing a lot of posts about issues with 2.2, as a newbie and a non-Linux cmd line chap, would I be better putting 2.1.5 on for now and waiting? I prefer the latest and greatest, but for now just really want to have something up and running for home labs.



  • it depends on the kind of hardware you are running…. some will run better on 2.2 / others will run better on 2.1.5
    it also depends on what addon packages you intend to use.... squid/squidguard/dansguardian are still being worked on, to get it all smooth and hassle free for 2.2.

    2.1.x will receive no more update / no more new features.
    2.2.x is the way to go and many many people are allready using it, but there are some situations where it is not perfect yet.



  • I believe e2guardian will replace dansguardian going forward. This package is really important to me so I'm waiting for it to upgrade.

    BTW pfSense is based on freebsd.



  • Okay, no problems. I'll persist with v2.2 :)

    Understand the development cycles etc., all good.



  • I did a clean install to my home set up and it's been crashing a lot, glad I didn't upgrade our office box yet.

    Like 2 - 3 times a day pfSense will restart itself and show the error "Pfsense has detected a crash report". May be something specific with my hardware but it never crashed so much on 2.1.

    I'm going to have to roll back for now.



  • What hardware?
    What type of pfSense - 32/64 bit, full instal or nanoBSD?

    It will never get resolved unless more detail is known.



  • Basically if you have hardware that will only boot and run 2.2, then its worth it.

    If you need a feature of 2.2 thats not present in 2.1.5 then its worth it.

    If you like bigger numbers then its worth it.



  • @phil.davis:

    What hardware?
    What type of pfSense - 32/64 bit, full instal or nanoBSD?

    It will never get resolved unless more detail is known.

    It's an Atom 330 on an Nvidia chipset. Nvidia onboard LAN and one Realtek LAN.

    I've uploaded the crash logs when it asks me too, so the issue has been reported.

    64bit release full install.



  • The devs do not analyse every crash dump received, that is just not viable. If nobody comes up with a good idea about your hardware in the near future, you could PM one of the devs (jimp?) with the public IP the crash dump would have come from - then they can have a look.