pfSense 2.4.4-RELEASE is now available!

Hugovsky

Thanks a lot one more time! pfSense FTW!!

beremonavabi

Not sure if this should be it's own topic, but the blog entry points to installation images at:

https://www.pfsense.org/download/

If I'm reading that correctly, for my official SG-4860, the correct image is from there and is named like:

pfSense-CE-memstick-ADI-2.4.4-RELEASE-arch.img.gz ("arch" being replace with "amd64" in this case)

It's no longer on my portal page and named something like:

pfSense-netgate-memstick-ADI-2.4.3-RELEASE-amd64.img

Is that correct?

jimp

Factory images should still be available to you when you are logged in. It's possible that they are not in place yet.

When you are logged into the portal the images you see there are the tuned Netgate factory images with extra features. You can use the ADI CE memstick if you want on that hardware, but the factory images offer a more optimal experience if you have access to them.

EDIT: I just checked and the 2.4.4 images are up on the portal so you can still use those if you have access.

beremonavabi

@jimp Thanks. I guess I'm not seeing those because my Gold subscription has lapsed. All the portal page shows me is "Membership Information" (essentially, nothing). I guess it would be nice if our portal pages pointed to those tuned images even though the membership has lapsed.

jimp

@beremonavabi said in pfSense 2.4.4-RELEASE is now available!:

@jimp Thanks. I guess I'm not seeing those because my Gold subscription has lapsed. All the portal page shows me is "Membership Information" (essentially, nothing). I guess it would be nice if our portal pages pointed to those tuned images even though the membership has lapsed.

If you submit a request to the support team they can get you access to the images you need. They are not tied to gold subscriptions.

Rico

So to avoid any (PHP) Errors, is it better to make a Backup, do a clean 2.4.4 Install and pop the Backup in?

-Rico

jimp

@rico said in pfSense 2.4.4-RELEASE is now available!:

So to avoid any (PHP) Errors, is it better to make a Backup, do a clean 2.4.4 Install and pop the Backup in?

The errors mentioned in the post are harmless. If you want to do a clean install, you can, but it is not necessary.

ramup

Hello,
thanks for all your efforts you put in the new release. My pfSense running on a ESXI 6.0 U3 VM (2.4.3-p1) was updated after doing a snapshot to 2.4.4-final.

Update worked (with PHP errors that I cannot recall) but the service C-ICAP was not working anymore and could not be started under "services". (Maybe problem https://redmine.pfsense.org/issues/8832).

That's why I reverted to 2.4.3-p1 via snapshot and hope there will be a fix for this soon and maybe for the PHP errors, too. Maybe they are not relevant but always leave a bad feeling that something is missing / not working as expected.

I saw a lot of PHP fixes on redline for 2.4.4 after RC release. Were they implemented in the RC since the release of RC or are they implemented in 2.4.5-Dev?

jwt

I saw a lot of PHP fixes on redline for 2.4.4 after RC release. Were they implemented in the RC since the release of RC or are they implemented in 2.4.5-Dev?

If they were material to functionality in 2.4.4, then they'r pin 2.4.4, otherwise, they're in 'master' which will yield a number of releases. a 2.4.4-p1 is already being planned.

There have been a lot of PHP fixed going from PHP 5.6 to PHP 7.2. This change has exposed a lot of poorly-written PHP that was written in the past. Example:

https://redmine.pfsense.org/projects/pfsense/repository/revisions/8501d8477c007a768537ebcb5a916f8f8ebb4091/diff/src/etc/inc/filter.inc

https://redmine.pfsense.org/projects/pfsense/repository/revisions/1ed21e0a2512554752de35d5758bcff503fcba9b/diff

PHP 7 is a lot more "picky" than was 5.6, and pfSense is 100,000 lines of PHP spread over 200 files.

When we say that these errors on upgrade are typically harmless, we mean it.

wgstarks

Is there a guide for updating using a factory image? This is the first update I have done on my SG-3100 and I’m not quite sure of the process.

jimp

@wgstarks said in pfSense 2.4.4-RELEASE is now available!:

Is there a guide for updating using a factory image? This is the first update I have done on my SG-3100 and I’m not quite sure of the process.

The same steps as CE. It is already configured internally for the factory repositories.

You might want to login to the portal and download an installer image for the 3100.

wgstarks

@jimp said in pfSense 2.4.4-RELEASE is now available!:

@wgstarks said in pfSense 2.4.4-RELEASE is now available!:

Is there a guide for updating using a factory image? This is the first update I have done on my SG-3100 and I’m not quite sure of the process.

The same steps as CE. It is already configured internally for the factory repositories.

So just process as outlined in the guide in the first post?

You might want to login to the portal and download an installer image for the 3100.

Is this just for a backup? All I see in the portal is the recover images for clean install.

jimp

@wgstarks said in pfSense 2.4.4-RELEASE is now available!:

@jimp said in pfSense 2.4.4-RELEASE is now available!:

@wgstarks said in pfSense 2.4.4-RELEASE is now available!:

Is there a guide for updating using a factory image? This is the first update I have done on my SG-3100 and I’m not quite sure of the process.

The same steps as CE. It is already configured internally for the factory repositories.

So just process as outlined in the guide in the first post?

Yep.

You might want to login to the portal and download an installer image for the 3100.

Is this just for a backup? All I see in the portal is the recover images for clean install.

Yep. Just in case.

wgstarks

@jimp
Thanks. Big help.

Joe Friday

Thank-You very much for the new update, and all the hard work you guys put into the new release!

ramup

Hello jimp,

I saw the C-ICAP Squid package was updated and I can confirm that C-ICAP is now working properly under 2.4.4 after update.

But the reason I (unintentionally) updated to 2.4.4 was not very satisfying. The acme package was updated even for 2.4.3 users. The problem is when a user has 2.4.3 installed (like me) and updates the acme package some php 7.2 packages are installed, too which causes a lot of PHP errors under 2.4.3 because it also tries to update to 2.4.4. I could not stop this upgrade process and so I received a lot of PHP errors. So I said, ok I will update to 2.4.4 but I could not update to 2.4.4 via web interface or console because there were errors. I had to use the shell and "pfSense-upgrade -d"

So please restrict the current ACME package (with dependencies to php7.2) to 2.4.4 users only!

Grimson

@ramup
https://redmine.pfsense.org/issues/8938

tman222

Upgraded to 2.4.4 this evening and things thankfully went smooth. Started the upgrade process and got the dreaded "upgrade failed" after it had downloaded 74 or so of the packages. However, I have had this error occur on at least one or two other release upgrades in the past as well, and after each of those the system came back up just fine. In this case, the system also came up after a couple minutes, though I was greeted with a message that pfSense had crashed. I didn't pay close attention to it at the time, figuring it may have been related to the major PHP version upgrade. Thankfully, since then there have been no further errors.

Everything appears to be working great, and I really appreciate the the feature additions to the GUI to enable fq_codel, and DNS over TLS / QNAME minimization for Unbound.

Thanks again for all you hard work on this release.

ravegen

Updated my version 2.4.3_1 to 2.4.4 and got this error paste on pastebin because its is lengthy.

https://pastebin.com/Rt1LcH42

trees spanning the land

When I updated a lot of our Site to site links with open vpn broke resulting in all our tunnels having to be deleted and re-created with the exact same settings, attempts to restore from a backup were un-successful