Now Available: pfSense® Plus 25.07-RELEASE

keyser

Upgraded 2100 Max from 24.11 to 25.07 without any hickups or issues.

Packages installed:

Freeradius 3
pfBlockerNG
Tftpserver
Nut
Notes
Lldpd

It does take quite a while though... 15'ish minutes before it's back up.

slu

@pfGeorge thank you to the Netgate team, I update appliances without issue.

WN1X

Upgraded my 4200 Max this morning from the 25.07-RC. Easy peasy!

markster

Upgraded 5100 without issues. Switched to KEA and so far so good.
One small issue was with older LG TV that would not use KEA DHCP for some reason. But I switch to static IP, disable DHCP and I am good.

provels

@Phizix Wish I had, tried, failed, had to spin up my 20 year old 2.3.5 hardware. Oh, well, at least I'm reitired... :)

LarryFahnoe

Upgraded 2 4200 MAX appliances from 24.11 to 25.07 and all went well. About 3-4 minutes each.

I did not remove packages prior to the upgrade, current list:
acme
aws-wizard
Cron
haproxy-devel
ipsec-profile-wizard
mailreport
Netgate_Firmware_Upgrade
nut
pfBlockerNG
sudo
System_Patches
WireGuard

--Larry

provels

Just me, or can't we edit posts anymore?

F00d

Upgraded 3100 from 24.11 to 25.07. Everything seems normal. The upgrade took about 10 minutes until the web UI reloaded. Installed packages include: Cron, RRD_Summary, Service_Watchdog, WireGuard. I'm following the advice to remain on ISC and not migrate to KEA due to arm32 incompatibility with the 3100.

ITSGS_

Updated from 25.07.r.20250715.1733.1500029 to 25.07 on my SG4200. No issues so far.

Cylosoft

It looks like Kea still has issues with static entries at times pulling an IP out of the pool.

Gertjan

@provels said in Now Available: pfSense Plus 25.07-RELEASE:

Just me, or can't we edit posts anymore?

Not on Netgate's 'Pinned' forum posts.

Dean79

I successfully upgraded my SG-1100.

Before upgrading, I backed up the config, deleted all packages, and updated firmware via the GUI rather than the console.
After upgrading my SG-1100 to firmware version 25.07, most of the resource overload issues that occurred with the previous version 24.11, were resolved, making it much more efficient. I had previously only been using the PFBlockerNG and Snort packages.

When I used version 24.11 on my SG-1100, the load was extremely high, reaching 100% CPU and RAM usage, frequently resulting in performance degradation and crashes down.
However, the current version 25.07 has reduced the load to about 30-70%.

This appears to be a very successful upgrade. I'd like to thank the Netgate developers for their hard work.

sjhawke

Upgraded SG-2100 BASE - updated with a 128Gb SSD (Internal drive wear was too high).

Upgrade process was ok, though it did get confused and give the "another process" error in the updates screen.

After update:

Unbound crashed with out of memory error. Switched to python mode and it seems to work, though pfblocker dns filter service then failed to start on boot and needed starting on the portal.

Hope these things get patched soon.

Simon

Gertjan

@sjhawke said in Now Available: pfSense Plus 25.07-RELEASE:

Switched to python mode

Still using 'Unbound mode' is popping often rather often these days.
A bit strange, as to really make shine pfBlockerng, you had to switch to the back then new Python mode :

should / would enough to convince people to switch over

sjhawke

@Gertjan - good point - I didn't see that. Wish I had. Generally don't mess with stuff that is working, until it isn't.

Phizix

@Gertjan,

Curious what hardware you were updating?

tman222

After cruising along at 180 days+ of uptime on 24.11, I decided to move ahead and upgrade to 25.07 this evening. Upgrade went flawless and probably took around 5 minutes on a Xeon D-1718T based system. Happy to see Unbound 1.23 included (there were some bug fixes in that release related to serve expired that I was looking forward to) as well as reduced CPU usage when viewing the dashboard page.

Thanks to everyone at Netgate for all your hard work on this release!

kymmitsu

Anyone knows why this has come up - SG-2100 - took 20 mins to get past - I thought it was locked up - one Acme *.domain cert only ? This was upgrade and fresh.

[48/72] Extracting ca_root_nss-3.104_1: ....... done
certctl: Skipping untrusted certificate 57bcb2da (/etc/ssl/untrusted/57bcb2da.0)
certctl: Skipping untrusted certificate 08063a00 (/etc/ssl/untrusted/08063a00.0)
certctl: Skipping untrusted certificate 5e98733a (/etc/ssl/untrusted/5e98733a.0)
certctl: Skipping untrusted certificate 18856ac4 (/etc/ssl/untrusted/18856ac4.0)
certctl: Skipping untrusted certificate 5e98733a (/etc/ssl/untrusted/5e98733a.0)
certctl: Skipping untrusted certificate 18856ac4 (/etc/ssl/untrusted/18856ac4.0)
certctl: Skipping untrusted certificate 08063a00 (/etc/ssl/untrusted/08063a00.0)
certctl: Skipping untrusted certificate 57bcb2da (/etc/ssl/untrusted/57bcb2da.0)
[49/72] Upgrading php83-sqlite3 from 8.3.12 to 8.3.19...
[49/72] Extracting php83-sqlite3-8.3.19: ......... done