Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    PfSense version numbers

    Scheduled Pinned Locked Moved
    2.3.3 Development Snapshots
    8
    27
    9.2k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • N
      NOYB
      last edited by

      This may not be 100% complete or accurate.

      
RELENG_2_3 ---|--- (aka 2.3.x development; currently x=4)
              |
               --- RELENG_2_3_2
              |
              |
               --- RELENG_2_3_3
              |
              |
               --- Future/Unknown (RELENG_2_3_4)
      1 Reply Last reply Reply Quote 0
      • P
        pablot
        last edited by

        Changed to STABLE and now I have a message that says "The system is on a later version than the official release."

        Sorry guys, but I still cannot understand how the versioning scheme works…
        how did I end on a version (2.3.4) that does not even exist?, or in other words where does 2.3.4 fits in this scenario?

        1 Reply Last reply Reply Quote 0
        • N
          NOYB
          last edited by

          @pablot:

          Changed to STABLE and now I have a message that says "The system is on a later version than the official release."

          Sorry guys, but I still cannot understand how the versioning scheme works…
          how did I end on a version (2.3.4) that does not even exist?, or in other words where does 2.3.4 fits in this scenario?

          2.3.4 is on the first line of the little diagram I drew.
          RELENG_2_3 branch = 2.3.x development = currently 2.3.4

          1 Reply Last reply Reply Quote 0
          • RonpfSR
            RonpfS
            last edited by

            @pablot:

            Changed to STABLE and now I have a message that says "The system is on a later version than the official release."

            Sorry guys, but I still cannot understand how the versioning scheme works…
            how did I end on a version (2.3.4) that does not even exist?, or in other words where does 2.3.4 fits in this scenario?

            Try Option 13 from the console. https://forum.pfsense.org/index.php?topic=125470.msg692930#msg692930

            2.4.5-RELEASE-p1 (amd64)
            Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
            Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

            1 Reply Last reply Reply Quote 0
            • K
              kpa
              last edited by

              Those funny looking identifiers RELENG___* are actually Git branches that you can view at Github. They are obviously borrowed from FreeBSD development that used the same kind of identifiers when they still used CVS as the revision control system. RELENG stands for "release engineering".

              The "master" branch at github is the work towards version 2.4:

              https://github.com/pfsense/pfsense/tree/master

              The "mysterious" 2.3.4 version is from the RELENG_2_3 branch which is the work towards the next 2.3.* release 2.3.4:

              https://github.com/pfsense/pfsense/tree/RELENG_2_3

              The upcoming version 2.3.3 and its release candidates are from the RELENG_2_3_3 branch:

              https://github.com/pfsense/pfsense/tree/RELENG_2_3_3

              Note that all of the RELENG_2_3_N branches have been branched from RELENG_2_3 at some point and they form the "maintenance" branches for the matching release versions.

              This development model is essentially the same that FreeBSD uses.

              1 Reply Last reply Reply Quote 0
              • P
                pablot
                last edited by

                ok guys, thanks for all the explanations.

                I've switched to STABLE and tried both option 13 from console and tried to update from the GUI but it seems to be stucked on 2.3.4 and aborts upgrading from console and seems to work from the GUI, but it did not upgrade/downgrade any pkg and after rebooting it still happily shows 2.3.4-DEVELOPMENT.

                Do I have a broken installation and have to reinstall from scratch?

                1 Reply Last reply Reply Quote 0
                • RonpfSR
                  RonpfS
                  last edited by

                  Post the update log from console or the one from WebGUI.

                  2.4.5-RELEASE-p1 (amd64)
                  Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
                  Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

                  1 Reply Last reply Reply Quote 0
                  • P
                    pablot
                    last edited by

                    From GUI:

                    Current Base System 2.3.4.a.20170215.0422
                    Latest Base System 2.3.3.r.20170215.0027

                    This is the output…

                    >>> Updating repositories metadata… 
Updating pfSense-core repository catalogue...
pfSense-core repository is up-to-date.
Updating pfSense repository catalogue...
pfSense repository is up-to-date.
All repositories are up-to-date.
>>> Unlocking package pfSense-kernel-pfSense... done.
>>> Downloading upgrade packages... 
Updating pfSense-core repository catalogue...
pfSense-core repository is up-to-date.
Updating pfSense repository catalogue...
pfSense repository is up-to-date.
All repositories are up-to-date.
Checking for upgrades (5 candidates): ..... done
Processing candidates (5 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.
Upgrade is complete.  Rebooting in 10 seconds.
>>> Locking package pfSense-kernel-pfSense... done.
Success

                    Seems to work but no pkg upgraded… and after rebooting, still shows 2.3.4-DEVELOPMENT

                    And from the console:

                    *** Welcome to pfSense 2.3.4-DEVELOPMENT (amd64 full-install) on pfSense ***

 FIBERTEL (wan)  -> vtnet1     -> v4/DHCP4: 190.192.36.210/24
 LAN (lan)       -> vtnet0     -> v4: 192.168.2.13/24
                                  v6: fd83:6d20:2ec5:732c::/64
 ARNET (opt1)    -> pppoe0     -> v4/PPPoE: 190.225.66.90/32

 0) Logout (SSH only)                  9) pfTop
 1) Assign Interfaces                 10) Filter Logs
 2) Set interface(s) IP address       11) Restart webConfigurator
 3) Reset webConfigurator password    12) PHP shell + pfSense tools
 4) Reset to factory defaults         13) Update from console
 5) Reboot system                     14) Disable Secure Shell (sshd)
 6) Halt system                       15) Restore recent configuration
 7) Ping host                         16) Restart PHP-FPM
 8) Shell

Enter an option: 13

>>> Upgrading necessary packages…
Updating pfSense-core repository catalogue...
pfSense-core repository is up-to-date.
Updating pfSense repository catalogue...
pfSense repository is up-to-date.
All repositories are up-to-date.
Checking for upgrades (5 candidates): ..

pfSense-kernel-pfSense-2.3.4.a.20170215.0422 is locked and may not be modified
Checking for upgrades (5 candidates)..... done
Processing candidates (5 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.
>>> Removing unnecessary packages... done.
>>> Cleanup pkg cache... done.
*** Welcome to pfSense 2.3.4-DEVELOPMENT (amd64 full-install) on pfSense ***

 FIBERTEL (wan)  -> vtnet1     -> v4/DHCP4: 190.192.36.210/24
 LAN (lan)       -> vtnet0     -> v4: 192.168.2.13/24
                                  v6: fd83:6d20:2ec5:732c::/64
 ARNET (opt1)    -> pppoe0     -> v4/PPPoE: 190.225.66.90/32

 0) Logout (SSH only)                  9) pfTop
 1) Assign Interfaces                 10) Filter Logs
 2) Set interface(s) IP address       11) Restart webConfigurator
 3) Reset webConfigurator password    12) PHP shell + pfSense tools
 4) Reset to factory defaults         13) Update from console
 5) Reboot system                     14) Disable Secure Shell (sshd)
 6) Halt system                       15) Restore recent configuration
 7) Ping host                         16) Restart PHP-FPM
 8) Shell

Enter an option:
                    1 Reply Last reply Reply Quote 0
                    • RonpfSR
                      RonpfS
                      last edited by

                      Seems you have updated already. Do you have the log for the first update to 2.3.4 ?
                      Maybe that will be fixed at some point, or reinstall.

                      To reinstall, better to disable packages, save the config & RRD data, save any other files (eg : Suricata SID Management Configuration Files), install 2.3.3RC, restore config, restore files, re-enable packages.

                      2.4.5-RELEASE-p1 (amd64)
                      Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
                      Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

                      1 Reply Last reply Reply Quote 0
                      • P
                        pablot
                        last edited by

                        ok, unfortunately I do not have other logs…

                        You mean that I've already updated to 2.3.3 but the wrong version is showing?

                        1 Reply Last reply Reply Quote 0
                        • RonpfSR
                          RonpfS
                          last edited by

                          Looks more that you updated to 2.3.4 for now. That's probably almost identical to 2.3.3RC.

                          2.4.5-RELEASE-p1 (amd64)
                          Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
                          Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

                          1 Reply Last reply Reply Quote 0
                          • P
                            pablot
                            last edited by

                            So, that brings me back to how I ended on 2.3.4…..  :o
                            ok, if I just "wait" for 2.3.4 this should be fixed by then or you recommed to backup, reinstall and restore ?

                            1 Reply Last reply Reply Quote 0
                            • N
                              NOYB
                              last edited by

                              I'm not recommending this.  But if the system is not critical and you want to experiment.  You might gitsync it to RELENG_2_3_3.

                              
playback gitsync --minimal --diff --show-files --dry-run git://github.com/pfsense/pfsense.git RELENG_2_3_3

                              Remove the dry-run option when you want to actually apply the changes.

                              Oh that's option 12 on the console.  Also reboot after applying a gitsync.

                              Also note RELENG_2_3_3 went from RC to RELEASE this morning.

                              1 Reply Last reply Reply Quote 0
                              • P
                                pablot
                                last edited by

                                :-\ will try that when I feel brave enough!!!

                                Seriously, it's a VM (kvm) so, I can happily try that and restore from a backup if it fails!!!  8)

                                Thanks for your help and advice!

                                1 Reply Last reply Reply Quote 0
                                • N
                                  NOYB
                                  last edited by

                                  @pablot:

                                  So, that brings me back to how I ended on 2.3.4…..  :o
                                  ok, if I just "wait" for 2.3.4 this should be fixed by then or you recommed to backup, reinstall and restore ?

                                  Because your updates were tracking RELENG_2_3.  Which previously was 2.3.3 Development.

                                  When 2.3.3 went to RC.  A new branch for it, RELENG_2_3_3 was made from RELENG_2_3, and the RELENG_2_3 branch went to 2.3.4 development.

                                  Since you where tracking RELENG_2_3 branch you went to 2.3.4 development along with it.

                                  I don't think there is any reason to reinstall if your update setting is set to now track stable I don't think you'll get anymore updates from RELENG_2_3 (2.3.4 development).  Your just a few commits ahead of RELENG_2_3_3 (2.3.3 release).

                                  If you want to get back from being ahead.  I think a gitsync would do it.  But I don't know for sure and thus am not making this a recommendation.

                                  1 Reply Last reply Reply Quote 0
                                  • N
                                    NOYB
                                    last edited by

                                    If you have VM snapshot form 2/10 (or before) it will probably be of 2.3.3.  You could go back to there and change the update setting to track stable.

                                    1 Reply Last reply Reply Quote 0
                                    • P
                                      pablot
                                      last edited by

                                      @NOYB:

                                      If you have VM snapshot form 2/10 (or before) it will probably be of 2.3.3.  You could go back to there and change the update setting to track stable.

                                      The oldest snapshot I have is from 2/10 so I will try that al see what happens.

                                      Thanks again!

                                      1 Reply Last reply Reply Quote 0
                                      • P
                                        pablot
                                        last edited by

                                        Went back to 2/10 VM snapshop, switched to STABLE, upgraded from console and now I'm on 2.3.3-RC

                                        Thanks!!!

                                        1 Reply Last reply Reply Quote 0
                                        • S
                                          survive
                                          last edited by

                                          Hi guys,

                                          I had the same problem where I was running 2.3.4. I ran the gitsync command a from an earlier post & now the system reports 2.3.3 in the version box I still show:

                                          Current Base System 2.3.4.a.20170227.0254

                                          When I check for updates.

                                          Is there a file I can edit to correct this?

                                          -Will

                                          1 Reply Last reply Reply Quote 0
                                          • M
                                            MoonKnight
                                            last edited by

                                            Hi,

                                            I got this one today :)

                                            pfsense_update.png_thumb
                                            pfsense_update.png

                                            --- 24.03 ---
                                            Intel(R) Xeon(R) CPU D-1518 @ 2.20GHz
                                            Kingston DDR4 2666MHz 16GB ECC
                                            2 x HyperX Fury SSD 120GB (ZFS-mirror)
                                            2 x Intel i210 (ports)
                                            4 x Intel i350 (ports)

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post