pfSense® Plus software version 24.03-RELEASE is here! 🥳

the other

@Bob-Dig did just that...even uninstalled, then reboot...as I stated. ULAs then gone from tables.
It is working for me, everything is fine... :) No problems so far with 24.03 (yeah, I checked) ;)

jimp

@SteveITS said in pfSense Plus software version 24.03-RELEASE is here! 🥳:

@the-other I would think the best case is, it will revert and can be reapplied. I suppose though it's possible the new version has slightly different code, and reverting or reapplying would break things. (though I think there's logic in there to refuse to revert or apply if it knows it doesn't match)

If the code was different, it couldn't be reverted.

jimp

@the-other said in pfSense Plus software version 24.03-RELEASE is here! 🥳:

@Bob-Dig did just that...even uninstalled, then reboot...as I stated. ULAs then gone from tables.
It is working for me, everything is fine... :) No problems so far with 24.03 (yeah, I checked) ;)

"uninstall" is a bad choice of words there since that implies other actions.

After upgrading, just delete unneeded custom entries without taking any other action on them. Just like the docs say. No need to overthink it.

Bob.Dig

@the-other Jimp said it, it was news to me. And the info field in system patches does say:

After upgrading, do not revert a patch if the changes from the patch were included in the upgrade. This will remove the changes, which is unlikely to be helpful.

I am not sure if this is overthinking, I think it is not foolproof.

the other

well, it is not foolproof, as I am a fool it seems, so I speak with some experience ;).

Anyways, went back to 23.09, removed the ULA patch, rebooted, installed 24.03 again. No patch is shown under custom patches, ULAs are in Tables.
So I guess now I have that problem fixed with those well done changes in 24.03...
So much for overthinking :)
BUT: both updates went well and without any problem, all is working. So (again) thank you ppl for a great working update so far!!

ericlee

We upgraded without any problems on different platforms: 19 x 2100, 5 x 4100, 1 x 8200, 4 x R720 with TAC, 4 x ESXi VMs with TAC...thank you pfSense and Netgate Team...

tman222

After ~140 days of uptime, I upgraded two machines today from 23.09.1 to 24.03 with no issues. First system was Intel Xeon D-1718T based, the second a Intel i3-10100 custom build. Both machines upgraded quite quickly and were back up and running again in less than 5 minutes.

Couple things I noticed after upgrading:

IGMP traffic now shows up in the firewall logs as blocked on the LAN pass rule which has been mentioned already in other threads. Can easily get around that by adding a separate block rule (and not logging) or enabling IP Options (if IGMP traffic should be allowed to pass).
My RRD graphs appears to be about 2/3 the size they used to be (the height is shortened). I'm still investigating if that's an issue with pfSense or maybe a browser issue while viewing under Linux. Has anyone else run into this?

Finally, thank you to the entire Netgate team for all your hard work and another great release!

coxhaus

@mwatch
I just upgraded to Pfsense 24.03. It seems to be working fine. It was a painless upgrade. It did what it was supposed to do and upgraded without issues. I think they did a fine job.

SteveITS

@mwatch Wow the new ZFS upgrade + restart is fast. That’s going to save us a bunch of time updating clients.

Mission-Ghost

Is there a good track record of successful 1100 updates? I’ve seen one post about a failed update possibly fit to failing nonvolatile storage but not much else.

Cylosoft

@Mission-Ghost We only had 1. No issues.

stephenw10

I've upgraded many without issue. However it is the lowest specced device so I would check the free drive space is at least 1.5GB. If it isn't look for old BE snapshots you might have.

I would also check the RAM usage. If you have a lot of packages installed you might need to disable any RAM hungry services.

Mission-Ghost

@stephenw10 very helpful, thank you.

I've got about 4.9G free. I have only one BE snapshot, which is of the stable baseline configuration now running.

Memory usage is about 57%. I intend to disable and perhaps remove all the installed packages prior to starting the upgrade process.

Phizix

@Mission-Ghost,

I have one 1100 but it only had one package installed - cron.

I did make sure it only had one ZFS configuration saved.

I had to update first to 23.09, before it would let me update to 24.03.

Afterward I decided to delete all but the original ZFS config.

No issues.

SteveITS

@Mission-Ghost said in pfSense Plus software version 24.03-RELEASE is here! 🥳:

Is there a good track record of successful 1100 updates? I’ve seen one post about a failed update possibly fit to failing nonvolatile storage but not much else.

FWIW we have two at the same client. One upgraded just fine, to 23.09.1 then 24.03. The other ran off the rails and only partially-upgraded to 23.09.1. I managed to recover it and save a trip out there. They were very similar/basically the same config, and I did uninstall pfBlocker on both before starting, so I don't know what the issue was on the one.

So, as per every upgrade for any software, have backups and a backup plan.

Phizix

I finally got around to updating my 8200.

I had to go through two versions before I could update to 24.03

I first removed all packages, etc.

Each update was VERY fast and successful.

WooooHoooo

Mission-Ghost

I applied the 24.03 update today to my 1100. Appears to have executed smoothly and rebooted back into production without issue.

Prior to executing the update, I removed all the packages. After the update, I reinstalled all the packages from scratch.

For some reason, some packages did not start automatically after installation including pfBlocker and Status Traffic Totals.

So I ran the pfBlocker download process and when that was complete it started up normally. I started Status Traffic Totals from the dashboard without incident.

My packages are:

Cron
Mailreport
pfBlockerNG
Service Watchdog
Status Traffic Total
System Patches

My plan is to run this in production for a week or so to verify stability and then update my shelf-spare 1100. This will complete my update cycle.