pfSense Plus Software Version 23.05 Release Candidate Now Available
-
We are excited to announce that the release candidate (RC) build for pfSense Plus software version 23.05 is now available for testing! See our blog for the complete details and upgrade instructions: https://www.netgate.com/blog/pfsense-plus-software-version-23.05-rc-now-available
-
@mwatch No issues on Protectli FW4B since upgrading ~12 hours ago
-
@mwatch said in pfSense Plus Software Version 23.05 Release Candidate Now Available:
in some automatic dynamic gateway names appearing in mixed case rather than all upper case, potentially causing connectivity issues until the default gateway or gateway group membership was updated.
So this only applies to automatic dynamic gateway names like OpenVPN Clients?
If I create them manually they can be mixed or all lower case? The latter I see in my setup.
-
It's this: https://redmine.pfsense.org/issues/14057
Manually created gateways shouldn't be a problem because they will always use the same format. The problem was that existing dynamic gateways in the config no longer matched the generated names. It applied to OpenVPN but also DHCP and PPPoE gateways.
Steve
-
@mwatch I get that an issue might be uncovered with the RC, but if not, how long before release of nothing serious shows up?
-
how long before release of nothing serious shows up?
About the time it's ready -- we do a final run a smoke tests that takes a day or two typically.
-
@mwatch said in pfSense Plus Software Version 23.05 Release Candidate Now Available:
https://www.netgate.com/blog/pfsense-plus-software-version-23.05-rc-now-available
Server 2022, I can't move from CE to 23.01 because of "Early boot hangs on Hyper-V with Gen2 VMs #1389". What is the work around to get to 23.05 that fixed this issue?
-
I'll be upgrading my 6100 MAX tonight.
-
@free99 said in pfSense Plus Software Version 23.05 Release Candidate Now Available:
What is the work around to get to 23.05 that fixed this issue?
After 23.05 is released we will update the CE > Plus upgrade repo to use it. Then you can upgrade directly.
-
APU6B4 - pfSense+ (Plus) 23.05 RC since a half hour all
is fine here, only three packages must be updated too,
but this went automatically after the first reboot.
(ACME, Snort and Squid)APU4D4 - pfSense 2.7 Devel runs like a charm since today.
-
Upgraded went smoothly on my SG-1100. So far no issues. Enabled IPsec-MB also, seems to be working, though my firewall doesn't have the scale to see if this helped me at all.
Thanks.
-
Upgraded my box Minisforum TH-50 from 23.01, no problems.
-
Upgraded my 6100 MAX successfully. I did notice a bunch of errors in the install log watching the console, but I have not encountered any problems. The upgrade waa extremely fast coming from 23.01.
-
Guess I'll be upgrading again tonight!
-
@defenderllc Yep. The upgrade to 23.05.r.20230511.0600 was small, quick, and painless so far.
-
@juanzelli I'll knock it out between meetings. Yes, I like to roll the dice. :)
-
Upgraded my 6100 MAX from the first RC build to the new one. Upgrade time was less than 5 minutes.
-
Upgrade completed without errors. However, after reboot GUI reported Mem usage increased form 16% to 51%.
This on my Netgate 5100 4Mb RAM. After I did system Halt; and restarted mem usage is back to 17%. -
@markster said in pfSense Plus Software Version 23.05 Release Candidate Now Available:
Upgrade completed without errors. However, after reboot GUI reported Mem usage increased form 16% to 51%.
This on my Netgate 5100 4Mb RAM. After I did system Halt; and restarted mem usage is back to 17%.Same. Mine usually hovers around 18% and now it's nearly double that.
-
@markster said in pfSense Plus Software Version 23.05 Release Candidate Now Available:
Upgrade completed without errors. However, after reboot GUI reported Mem usage increased form 16% to 51%.
This on my Netgate 5100 4Mb RAM. After I did system Halt; and restarted mem usage is back to 17%.That is quite normal. It happens because of the ZFS filesystem ARC cache. The upgrade does a LOT of filesystem work (completely unusual), and the ARC cache therefore grows alot as long as there is free memory to use. A restart clears the cache, and it will not happen again unless a new upgrade or some other anomaly causes massive filesystem work.
