To 2.5.0 or not ? that is the question :)
-
This post is deleted! -
This post is deleted! -
This post is deleted! -
This post is deleted! -
This post is deleted! -
This post is deleted! -
This post is deleted! -
@johnpoz said in To 2.5.0 or not ? that is the question :):
I pulled the trigger last night vs waiting til early morning (wife not up yet time frame)... And while playing with trying to get zfs working - I got that - hey you doing something with the internet yell ;)
LOL. I know exactly what you are talking about. Been there too many times.
-
This post is deleted! -
This post is deleted! -
This post is deleted! -
We have had a very bad experience with the update to version 2.5 or 21.02 as it appears on the dashboard, and this has more to do with support for previous versions, I have more than 100 devices running on version 2.4.5-RELEASE -p1 and none of these allow me to update or install packages from the package manager
-
This post is deleted! -
@juanpadiaz said in To 2.5.0 or not ? that is the question :):
We have had a very bad experience with the update to version 2.5 or 21.02 as it appears on the dashboard, and this has more to do with support for previous versions, I have more than 100 devices running on version 2.4.5-RELEASE -p1 and none of these allow me to update or install packages from the package manager
You should be able to install packages on the 2.4.5 RELEASE if you go to the Update Manager screen and change the drop-down to "Previous Stable Version" (or something akin to that wording). That will reset
pkgon your system to reference and use the older repository.However, if you have already tried to install a 2.5 package onto pfSense-2.4.5, you may have corrupted
pkgas it would get updated with the latest version which is likely to have issues with the shared libraries present in the older 2.4.5 pfSense. Note that packages in the 2.4.5 repository tree will stay at their current versions. Updates to packages will only happen in the "current" pfSense release which is now either 2.5 or 21.02, depending on whether you are using Community Edition on generic hardware, or running the new pfSense+ on Netgate hardware. -
This post is deleted! -
@bmeeks Many thanks, we are using Netgate hardware but we already try to install packages from a 2.4.5-RELEASE-p1, never updated one, and the package manager just gives us, and the premium support doesn't have the right response yet, we can not just upgrade all of our production devices without any tests, but any device with the version 2.4.5-p1 or older are not able to download or install packages via the package manager.
-
This post is deleted! -
None of my static routes are active in my routing table after upgrading. I tried disabling and re-enabling to no avail.
-
This post is deleted! -
@juanpadiaz said in To 2.5.0 or not ? that is the question :):
@bmeeks Many thanks, we are using Netgate hardware but we already try to install packages from a 2.4.5-RELEASE-p1, never updated one, and the package manager just gives us, and the premium support doesn't have the right response yet, we can not just upgrade all of our production devices without any tests, but any device with the version 2.4.5-p1 or older are not able to download or install packages via the package manager.
The translation to English is a bit confusing to me, so please forgive me asking additional questions. So are you saying you have a pfSense-2.4.5_p1 box that you never attempted to update anything on, and you went first to the Update Settings page and changed the drop-down there to "Previous Stable Version (2.4.5 deprecated)" and saved that change? Then you go to SYSTEM > PACKAGES and can't do anything? Or did you first go to SYSTEM > PACKAGES and attempt to install a package BEFORE you changed the Update Settings value in the drop-down? The sequence is critical. If you attempted to install or update a package before you changed the
pkgutility on your firewall to reference the "Previous Stable Version (2.4.5 deprecated)", then that would have immediately installed an updatedpkgbinary on your 2.4.5 firewall, but from the 2.5 (or 21.02) new pfSense repository. That newerpkgutility can't work on 2.4.5_p1. That can cause the issue you are seeing.Go check out this thread: https://forum.netgate.com/topic/160989/upgrade-packages-on-2-4-5-p1/6 and see if the solution there helps you.
