pfSense version 2.4.4 release candidate is now available for testing!
pfSense version 2.4.4 release candidate is now available for testing. Please help us by testing and reporting bugs.
Users on a stable release or 2.4.4 development snapshots may obtain the RC by selecting the Release Candidate branch from System > Update.
Been looking forward to this. But one question regarding System > Update settings:
So I want to get this 2.4.4 release candidate, and then the final 2.4.4 release. But I don't want it to then kick over into 2.4.5 betas, but stay at 2.4.4.... how do I ensure that?
It looks like your pfSense didn't update the branch list. Refresh that page and it should show the correct branch.
Ah yes, now refreshed..... so I should choose this one?
Yes, select "Next Release Candidate". Once 2.4.4-RELEASE is out, you will need to select "latest stable version" to upgrade to stable from RC.
@ivor Thanks a lot for the quick advice......
I had a crash report after installation.Initially I thought it was just due to needing to update all the packages, but even after doing that and a reboot it persisted. My error was lots of entries like:
PHP Warning: filesize(): stat failed for /usr/local/etc/suricata/suricata_11150_igb1/rules/suricata.rules in /usr/local/pkg/suricata/suricata_generate_yaml.php on line 853 PHP Warning: filesize(): stat failed for /usr/local/etc/suricata/suricata_11150_igb1/rules/flowbit-required.rules in /usr/local/pkg/suricata/suricata_generate_yaml.php on line 855 PHP Warning: filesize(): stat failed for /usr/local/etc/suricata/suricata_11150_igb1/rules/custom.rules in /usr/local/pkg/suricata/suricata_generate_yaml.php on line 857
Reinstalling the suricata package (but keeping settings) fixed my crash problem.
I do still have a problem whereby c-icap will not start, am wondering if it's related to this but haven't had time to investigate more.
Grimson last edited by
Upgrade from 2.4.3p1 to 2.4.4RC went without any noticeable problems. Installed packages:
All upgraded without problems.
The PHP errors during the package updates (after the first reboot) looked a bit alarming, but I guess they are to be expected when upgrading to a new major PHP version. Though it might be a good idea to put a disclaimer about them into the announcements. Good work so far.
Animosity022 last edited by
Upgraded to the RC and noticed no issues. We'll let it run and see.
Why is ivor banned?
Normally, I never install a new, fresh version right away, and even less a Release Candidate.
But this very one time, I could stand it anymore, so I installed the RC on a production machine ...
Just beautiful, the RC update. Didn't saw any error messages, everything looks clean to me : https://pastebin.com/KRCB3XGY
/cf/conf/https://pastebin.com/TpxsnWnh : some PHP errors.
edit : something went wrong, very wrong :
@kom said in pfSense version 2.4.4 release candidate is now available for testing!:
Why is ivor banned?
Dono, wasn't me.
CiscoX last edited by
Why is ivor banned?
Maybe he used some unknown words that is not in the dictionary?
Anyway, I don't really know. Let's hope is nothing bad.
He hasn't been online in 4 days, and his avatar has that alarming BANNED tag.
Fixed .. he should not have been banned.
@delitrium But he is still gone? If so, that's too bad as he was one of the two regular Netgate faces in here along with jimp, and he was quite helpful.
@kom He has moved on to other things and we at Netgate wish him the best in whatever the future brings and appreciate what he has done for us.
I agree with @KOM, this is some heavy news.
Auto Configuration Backup works good !
Video overview of some of the new features (no affiliation): https://www.youtube.com/watch?v=_Dd0Fj46weU
@KOM yeah ivor being gone is SAD news for sure... I would not provide his contact info, but if anyone would like me to hand off your contact info to him. I am in touch with him via personal email. Just PM me your info and will pass it on to him.
I can say I will miss him around here for sure.