@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.

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.

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

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

Regards

Edit: Update done, no issues.

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

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

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

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!

Did not uninstall any packages, including pfBlockerNG

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

Packages running: pfBlockerNG, Syslog-ng, tftp, lldpd, notes, NtopNG, Freeradius, Nut

It's a simple setup, no aggregation.. It's working as a Syslog server for Synology, Unifi and pfSense.
But I'm also exporting netflow from pfSense to Graylog.

Curious. What are you using as a NetFlow collector?

Graylog:

If you're going from 23.05 to 23.05.1 the risk is much, much lower.

23.01 to 23.05.1 is probably still worth taking out packages for (PHP moved to 8.2) but still less risk than going from the old PHP 7.x code in 22.x up to 23.xx.

And in terms of what to uninstall, uninstall them all unless a package is 100% necessary for your upstream connectivity somehow, and then leave only what is absolutely needed.

As usual, uninstalled pfblockerNG, Softflowd and NUT before upgrading.

New to uninstalling before upgrade. So let's say I were to follow your lead. Would I:

• 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

?

Thanks!

Packages used: pfBlockerNG, Wireguard, Softflowd, NUT, Acme and the others installed by default.

Curious. What are you using as a NetFlow collector?

haha - I run into that myself... Could just be a dick and reboot anyway..

I almost did that, but one of the users watching Plex is my mom.. eheh

a few Plex friends just connected

haha - I run into that myself... Could just be a dick and reboot anyway.. But I normally wait til its quiet, early morning is the best.. Nobody on in in the 5-6 am window ;)

Should I pull trigger or just wait til weekend where be less of bother if its down for a bit. Think I will just wait a couple of days.

It took 5 minutes to update, already reinstalled all packages (keep settings enabled really got things easier).

Now I want to reboot again, RAM usage is pretty high after the upgrade but now I'm stuck, a few Plex friends just connected, I'll have to wait to reboot.

I wonder how many people actually do that?

It is best practice - and have done it in the past, but last couple of upgrades I just pulled the trigger.. After having copy of install media from tac (pfsense+) on hand and making sure have a latest and greatest copy of the config.

I don't really see anything in 23.05.1 that I need - and don't wont to have to reboot twice - will just wait til it goes official.

edit:
Oh - it looks official.. Should I pull trigger or just wait til weekend where be less of bother if its down for a bit. Think I will just wait a couple of days.

I guess I am just a rebel now lol!

ahahah, you are braver than me