To 23.05 or not ? that is the question :)
-
23.05+ was published!
Gathering success and failure feedback for a new point pfSense Plus 23.05 release.
Please add your comment!
-
Your late.
23.01 came out several month ago, somewhere in February 2023..
23.05 is on the ramps right now. -
@gertjan said in To 23.01 or not ? that is the question :):
Your late.
23.01 came out several month ago, somewhere in February 2023..
23.05 is on the ramps right now.I always do it, even tho tried hard :)
Corrected, thx -
Upgraded successfully here, SG-4100.
1- Disabled RAM disk
2- Boot environments restore to a point in which I didn't have packages installed (just usual config)
3- Upgraded
4- Reinstalled and reconfigured packages
5- Enabled RAM disk again -
@chudak Two boxes upgraded succesfully.
One of them showed the certificate failure on a repo and failed the first time (before doing anything) - after which it no longer showed 23.05 - said it was up to date on 23.01. Changing back to 23.01 tree and then back to 23.05 tree restored the update tree and the update went fint on the second try.
One little niggle: The Syslog-ng package does not work - it throws a parsing error of the build configuration file. I’ll create a thread for that issue.
Love the no fuss of using the official appliances :-)
-
My two are up-to-date, the first was a breeze, the second had a hiccup, needed re-registered, hiccup continued, upgrade failed, rebooted, upgraded like the first, easy-peasy.
-
Have issues with Wireguard on 23.05, it did not start after boot, need to manually Save and Apply all Wireguard assigned gateways, then Wireguard starts, but until next boot, then need to do same again...
-
APU6B4 with 23.05 latest version, some hiccups, pkg`s were shortly not available (to install) and
I was not able to upgrade but now all is fine
up and running. I was three times installing it!
2.6 > 23.01 > 23.05 but all in all it was worth it. -
Upgraded my 8200 a day ago, still no problems I have noticed, so upgrade seemed to have went fine here.
-
Upgraded my own SG1100 yesterday without issues.
Small PHP-related crash log at first login, but everthing works so far. Visible change: less RAM usage! From ~75% to 50%, nice.
-
To 23.05 or not ? that is the question :)
pfSense 23.05 on a 4100 : it was a click, a coffee, and done.
-
Updated my 4100 wit activated RAM disk.
made a second reboot after the update and everything works smooth.
Had to apply a small config change for my apc ups, which was not recognized. -
-
Non-Netgate hardware updated first from 23.01 to 23.05 RCs up to 23.05.r.20230519.0600.
After seeing some problems with r.20230522.1252 changed branch back to "Current Stable 23.01" and waited for "Current Stable 23.05" to become available.
No problems updating to 23.05 Release, though I'm not running any special packages. -
@mvikman create a backup and download a local copy in case you have to do a full reinstall.
when you kick off, go have coffee. the rebooting in 10s is way understated in my experience. needed 2-3min before the reboot, and then you still have a minute or so for the update to run
-
@gwaitsi I save the config file to my pc everytime I make changes.
I always do a reboot before upgrade and I follow reboots/upgrades from console(display).
I also have a backup pfsense box that I can swap in to use if the main one dies. -
Updated my 6100 Max:
- Backed-up config
- Set a ZFS Boot Environment snapshot
- Pre-booted
- Clicked on the update icon
- Auto rebooted with zero issues
So yes, I left all packages in place and other than setting backups (thankfully not needed) and the pre-booting I did nothing more than allow pfSense to sort it all out. Which it did.
️ -
Upgraded successfully here, XG-1537 in HA. First the backup unit, then the master.
Using pfBlockerNG and zabbix-agent6. -
@chudak One patch so far, for the bleeding-edgers :)
https://forum.netgate.com/topic/180313/firewall-alias-import-bug-after-upgrade-to-23-05-release-amd64 -
Successfully upgraded two systems (one Xeon D based Supermicro unit and one Intel i3 custom build) from 23.01 to 23.05. Overall, the upgrade went smooth and was fairly quick on both systems.
A minor issue was that both systems ran into the certificate error the first time when trying to upgrade (as has been documented in other threads already), but flipping the Branch back to 23.01 and then forward to 23.05 again under System -> Update allowed the upgrade to proceed the second time.
Very excited to see
IPsec Multi-Buffer (IPsec-MB) Cryptographic Accelerationbeing added in this release as well as a formal pfSense package forudpbroadcastrelay.A big Thank You to everyone who contributed to this release for all hard work and effort.
