23.05.1

johnpoz

So I just pulled the trigger.. Took a current config backup, consoled in so could watch the upgrade - all smooth.

Took total of about 6 minutes on my 4860... Logging in now, seems all good.

chudak

Upgraded to 23.05.1 with no issues

Did not uninstall any packages, including pfBlockerNG

Cabledude

@jimp thanks for clarifying. You say with pfSense Plus 23.05 to 23.05.1 the risk is much lower. So there still is a risk and some users here do uninstall.

I could make uninstalling packages a principle or standard workflow. Could you comment on the steps I listed above:

create config backup

uninstall packages like pfBlocker (is there a list of which packages should be uninstalled?)

perform upgrade

load config backup, so that the necessary packages are downloaded and installed automatically + their config is restored

Would you say this is it? Any alterations advised?

Thanks!

jimp

I wouldn't bother with the config restore, just install the packages again. The config restore is a fairly harsh way of saving a handful of clicks.

It will work, but it's like swatting a fly with a cannon.

johnpoz

@jimp said in 23.05.1:

It will work, but it's like swatting a fly with a cannon.

But what if its robotic fly with steel plating? ;)

Cylosoft

For our 2.6 to 2.7 boxes I uninstalled PfBlocker and left all other packages. 23.05.1 I left all packages installed. I'm about 20 boxes in now and zero issues.

FSC830

To be honest: I did never uninstall a package prior updating.
Since 2.4.5 I am running the updates in current status.
I did only see one issue, but I cant remember if really a package was the culprit or something else.
And I remember that one update fails and I need to recover from recovery image.
Thats my fallback, I always request the recovery image from TAC prior updating.

Will update to 23.05.1 during weekend .
Appliance is a SG-3100

Regards

Edit: Update done, no issues.

Cabledude

@jimp said in 23.05.1:

I wouldn't bother with the config restore, just install the packages again. The config restore is a fairly harsh way of saving a handful of clicks.

It will work, but it's like swatting a fly with a cannon.

Ah okay, thank you. I assumed that package configuration (settings sections) would be reset to their defaults if packages are simply uninstalled and reinstalled, but if I understand you correctly the settings will be retained?
So let's say I uninstall Avahi, perform update and reinstall Avahi, will the system have remembered the Avahi settings such as which interfaces, repeat packet across subnets etc.?

Thank you

dennypage

@Cabledude said in 23.05.1:

So let's say I uninstall Avahi, perform update and reinstall Avahi, will the system have remembered the Avahi settings such as which interfaces, repeat packet across subnets etc.?

Yes, Avahi's package settings will be retained.

jimp

@Cabledude said in 23.05.1:

@jimp said in 23.05.1:

I wouldn't bother with the config restore, just install the packages again. The config restore is a fairly harsh way of saving a handful of clicks.

It will work, but it's like swatting a fly with a cannon.

Ah okay, thank you. I assumed that package configuration (settings sections) would be reset to their defaults if packages are simply uninstalled and reinstalled, but if I understand you correctly the settings will be retained?
So let's say I uninstall Avahi, perform update and reinstall Avahi, will the system have remembered the Avahi settings such as which interfaces, repeat packet across subnets etc.?

Upgrading a package effectively uninstalls the old package and reinstalls the new version. Same as if you did it in two steps before/after a reboot.

By default package configurations are retained in the firewall config file and only the metadata about the package is altered (e.g. the info about the package files, menus, tabs, plugins).

There are a small number of packages which have an option to wipe their config on reinstall but that isn't their default behavior, you have to explicitly set them to clear the config.