2.4.5 Update Caution

bmeeks

I did a little f*ck up. I updated Suricata before upgrading to 2.4.5 and now Suricata does not work. Is there any progress on fixing that?

The fix for that is easy. Update your firewall to 2.4.5. That fixes it for the vast majority of users that have done this to themselves.

If it does not fix it for you, then go follow the steps in this documentation: https://docs.netgate.com/pfsense/en/latest/install/upgrade-troubleshooting.html#forced-pkg-reinstall. That has also fixed it for some folks.

In the future, follow the warnings in the Netgate/pfSense docs and NEVER update packages when a new version of pfSense is available UNTIL you have updated pfSense itself first.

gerjanw

@bmeeks Thanks. I will try the steps in the documentation and yes I have learned my lesson I will never ever again update packages before updating PfSense

Gertjan

Netgate should ask CNN for international coverage before they bring out 2.4.6.
Or high-jack social media to create a mega buz first.
Something smaller just won't do.

@gerjanw : don't worry, we've all been there

chudak

@gerjanw

I did the same and paid high price - had to reimage my router.
It was PFBlockerNG and after un-installing it all went to hell.

Do not uninstall anything.

I'd suggest to upgrade to 2.4.5

stephenw10

We now have a 2.4.4 selection in System > Update > Update Settings that you can use to select 2.4.4 packages if you are not yet ready to upgrade.

Steve

chudak

@stephenw10 said in 2.4.5 Update Caution:

We now have a 2.4.4 selection in System > Update > Update Settings that you can use to select 2.4.4 packages if you are not yet ready to upgrade.

Steve

@stephenw10

Can you pls elaborate?
I am on 2.4.5 so not sure what you are suggesting.
Looking like - specify deprecated 2.4.4 and then how will it help to avoid problems?

stephenw10

It will only help if you were running 2.4.4p3 and accidentally installed a 2.4.5 package. Swicthing the repo and reinstalling should bring you back to the correct package for 2.4.4p3.
But even so if you had done that it would be better to reinstall IMO.

Really it is useful to avoid doing that at all. If you are running 2.4.4p3 and cannot upgrade for whatever reason but need to install a package you can now do so by selecting the 2.4.4 repo.

Steve

chudak

@stephenw10 said in 2.4.5 Update Caution:

It will only help if you were running 2.4.4p3 and accidentally installed a 2.4.5 package. Swicthing the repo and reinstalling should bring you back to the correct package for 2.4.4p3.
But even so if you had done that it would be better to reinstall IMO.

Really it is useful to avoid doing that at all. If you are running 2.4.4p3 and cannot upgrade for whatever reason but need to install a package you can now do so by selecting the 2.4.4 repo.

Steve

I am thinking over how to make it better for next snafu.
Still don't get why if the package is for say 2.4.6, Netgate can't flag it as such in Install Packages pane.

Other option would be even not to show newer packages at all for newer release...

stephenw10

There will almost certainly be improvements for the next significant release. A number of options are being discussed internally.

Steve

chudak

@stephenw10

Thank you !

And I want to repeat - pfSense is awesome and I’m glad I made several years ago to to switch to it !