2.3.4-RELEASE-p1 same as 2.3.5?

  • I've got a pfsense box running 2.3.4-RELEASE-p1. The web GUI says that I'm running the latest version. I ran an update from the console and if upgraded a bunch of packages. The system is still saying it's running 2.3.4-RELEASE-p1. The console updater is now saying that I am up to date.

    I noticed on the website that 2.3.5 is available for download. Are 2.3.4-RELEASE-p1 and 2.3.5 essentially the same? Or do I need to look into doing a manual upgrade via USB?


  • @lawndartdeath:

    I've got a pfsense box running 2.3.4-RELEASE-p1.  …

    Yeah, you just cut out the most important one : i386 CPU ou AMD64 - or known as "32 bits" or "64 bits".

    2.3.5 is the succesor of 2.3.4-xxxx, so go head, take it, as it is out for several days now, thus : ok.

    If your pfSense proposes you 2.3.5 then you're probably running the 32 bits version, which will be supported a year or so.
    Check out your system to see why you use the 32 bit version, and if 64 bits is accepted, consider a complete re install to jump to "64 bits". Of course, backup your config first and use it when re installing.

    See alos all the doc, blogs, posts, etc for more - if not all - the info.

  • I'm running the i386/32bit version on a Soekris net5501 which has a AMD Geode LX CPU. It's a 32bit chip. So I understand that I can't run 2.4.x and that's fine. I'm just wondering why the update tool is saying that 2.3.4-RELEASE-p1 is the latest version.

  • Here is a screenshot.

    ![pfsense update.png](/public/imported_attachments/1/pfsense update.png)
    ![pfsense update.png_thumb](/public/imported_attachments/1/pfsense update.png_thumb)

  • @yarick123:


    I had also some troubles during upgrading i386 NanoBSD from 2.3.4_1 to 2.3.5 . One of them was missing "Legacy stable version (Security/Errata only 2.3.x)" branch.

    Solution: I switched the Firmware Branch to "Development Snapshot (Experimental 2.3.x)", saved the changes and checked for upgrades. After this procedure I could select "Legacy stable version (Security/Errata only 2.3.x)" branch. After saving the configuration, new updates were recognised.


    P.S. Yes, I got 2.3.5 and 2.3.5_1 on my i386 NanoBSD.

Log in to reply