pfSense Support Subscription

Author Topic: pfSense version numbers  (Read 3621 times)

0 Members and 1 Guest are viewing this topic.

Offline pablot

  • Jr. Member
  • **
  • Posts: 59
  • Karma: +3/-0
    • View Profile
pfSense version numbers
« on: February 15, 2017, 01:20:24 pm »
Hi, sorry if this is somewhere else on the forum or on any documentation, but I have not been able to find it.

How do I understand versioning numbering in pfSense?

I have just read that 2.3.3 is around the corner, but I'm already using 2.3.4-DEVELOPMENT... but 2.3.4 is not on the redmine of pfSense, only 2.3.3 and 2.4.0 are there... so... I'm kind of lost...  :o

Offline JorgeOliveira

  • Full Member
  • ***
  • Posts: 153
  • Karma: +24/-1
  • May the Triforce be with you...
    • View Profile
Re: pfSense version numbers
« Reply #1 on: February 15, 2017, 02:46:29 pm »
You are running 2.3.4 (RELENG_2_3 branch), while the RC version is 2.3.3 (RELENG_2_3_3)

You need to change repository to stable (System > Update > Update Settings) and re-run upgrade procedure (console option 13). It should "downgrade" to 2.3.3 and business as usual. ;)
« Last Edit: February 15, 2017, 02:50:22 pm by JorgeOliveira »
My views have absolutely no warranty express or implied. Always do your own research.

Offline jimp

  • Administrator
  • Hero Member
  • *****
  • Posts: 21404
  • Karma: +1437/-26
    • View Profile
Re: pfSense version numbers
« Reply #2 on: February 15, 2017, 03:56:08 pm »
If you are running 2.3.4, then you are on "2.3.x snapshots" (RELENG_2_3), which is "whatever the latest development builds of 2.3.x are".

We branched 2.3.3 (RELENG_2_3_3) off from RELENG_2_3 and it's got its own separate images (of which the release images are being tested now).

If you want to end up on 2.3.3, you need to do as JorgeOliveira suggests.

Or, worst case scenario, back up the config and reinstall with a 2.3.3 release image when it comes out.
Need help fast? Commercial Support!

Co-Author of pfSense: The Definitive Guide. - Check the Doc Wiki for FAQs.

Do not PM for help!

Offline pablot

  • Jr. Member
  • **
  • Posts: 59
  • Karma: +3/-0
    • View Profile
Re: pfSense version numbers
« Reply #3 on: February 15, 2017, 04:45:35 pm »
Ok, but is 2.3.4 a real version ir just a dummy one and  only 2.3.3 is they real one?
 
Also, what happens if I just leave my upgrade settings as I have now?. Will I stop getting daily builds when 2.3.3 is finally released?

Offline kpa

  • Hero Member
  • *****
  • Posts: 1188
  • Karma: +132/-6
    • View Profile
Re: pfSense version numbers
« Reply #4 on: February 15, 2017, 04:57:15 pm »
Ok, but is 2.3.4 a real version ir just a dummy one and  only 2.3.3 is they real one?
 
Also, what happens if I just leave my upgrade settings as I have now?. Will I stop getting daily builds when 2.3.3 is finally released?

If you leave your system as it is you'll be tracking 2.3.4 development builds which is probably not what you want. The release of 2.3.3 will not make any difference because it is a separate version branch from the branch where the development of 2.3.4 is happening (the RELENG_2_3 branch as mentioned).

Offline NOYB

  • Hero Member
  • *****
  • Posts: 1703
  • Karma: +158/-273
    • View Profile
Re: pfSense version numbers
« Reply #5 on: February 15, 2017, 05:31:34 pm »
This may not be 100% complete or accurate.

Code: [Select]
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)
« Last Edit: February 15, 2017, 06:27:44 pm by NOYB »

Offline pablot

  • Jr. Member
  • **
  • Posts: 59
  • Karma: +3/-0
    • View Profile
Re: pfSense version numbers
« Reply #6 on: February 15, 2017, 06:11:18 pm »
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?
« Last Edit: February 15, 2017, 06:17:40 pm by pablot »

Offline NOYB

  • Hero Member
  • *****
  • Posts: 1703
  • Karma: +158/-273
    • View Profile
Re: pfSense version numbers
« Reply #7 on: February 15, 2017, 06:24:29 pm »
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

Offline RonpfS

  • Hero Member
  • *****
  • Posts: 684
  • Karma: +96/-2
    • View Profile
Re: pfSense version numbers
« Reply #8 on: February 15, 2017, 06:51:27 pm »
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.3.5-RELEASE (amd64)
Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
pfBlockerNG 2.1.2_1/Dev, suricata 4.0.1

Offline kpa

  • Hero Member
  • *****
  • Posts: 1188
  • Karma: +132/-6
    • View Profile
Re: pfSense version numbers
« Reply #9 on: February 15, 2017, 06:56:49 pm »
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.
« Last Edit: February 15, 2017, 07:07:40 pm by kpa »

Offline pablot

  • Jr. Member
  • **
  • Posts: 59
  • Karma: +3/-0
    • View Profile
Re: pfSense version numbers
« Reply #10 on: February 15, 2017, 07:14:30 pm »
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?

Offline RonpfS

  • Hero Member
  • *****
  • Posts: 684
  • Karma: +96/-2
    • View Profile
Re: pfSense version numbers
« Reply #11 on: February 15, 2017, 07:19:31 pm »
Post the update log from console or the one from WebGUI.
2.3.5-RELEASE (amd64)
Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
pfBlockerNG 2.1.2_1/Dev, suricata 4.0.1

Offline pablot

  • Jr. Member
  • **
  • Posts: 59
  • Karma: +3/-0
    • View Profile
Re: pfSense version numbers
« Reply #12 on: February 15, 2017, 07:30:36 pm »
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:




Offline RonpfS

  • Hero Member
  • *****
  • Posts: 684
  • Karma: +96/-2
    • View Profile
Re: pfSense version numbers
« Reply #13 on: February 15, 2017, 07:41:13 pm »
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.3.5-RELEASE (amd64)
Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
pfBlockerNG 2.1.2_1/Dev, suricata 4.0.1

Offline pablot

  • Jr. Member
  • **
  • Posts: 59
  • Karma: +3/-0
    • View Profile
Re: pfSense version numbers
« Reply #14 on: February 15, 2017, 07:45:45 pm »
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?