Installed Packages Notification

Gertjan

@bmeeks : very true.
Happily enough, the script, which I copied from this forum myself a few month (?) ago also notifies you when pfSense is updated itself. I'm not the author. I just made it less verbose.

And, Microsoft learned us the hard way that, when a new version of something comes out, you never ever install first and think afterwards.

Right after the release date of a new pfSense version, only a test system should be updated, and checked for expected behaviour. Do not update production systems.
For a week or so, while reading all the forum posts and the blog post that comes with the update, one should wait until the dust settles.

During this period : no packages does be updated, as they might use new libs and functionalities only available in the new pfSense version, not present yet.

Exceptions are possible. As long as you keep a saved config, and a spare copy of the soon to be 'old version' of pfSense nearby.

If all goes well, I just spend 200+ words to say something everybody already knows - are totally logic ;)

Raffi_

@bmeeks said in Installed Packages Notification:

That is a very useful script that @Gertjan provided, but ALWAYS remember the cardinal rule with pfSense packages! DO NOT upgrade a package unless you are on the latest release of pfSense for the branch you are using.

Oooh update to packages available, click...
I have been burned by this mistake. Had to fresh install and then restore.
Learned to always make sure my pfsense is up to date before updating packages. I think there should be a big red warning on the Installed packages tab when pfsense itself has an update available. Or better yet grey out the update buttons when pfsense has an update available. This doesn't prevent people from doing it via CLI but I personally always update via the GUI buttons. I'm guessing most users do as well.

bmeeks

@Raffi_ said in Installed Packages Notification:

I think there should be a big red warning on the Installed packages tab when pfsense itself has an update available. Or better yet grey out the update buttons when pfsense has an update available. This doesn't prevent people from doing it via CLI but I personally always update via the GUI buttons. I'm guessing most users do as well.

That would make an excellent Feature Request for the pfSense Redmine Site. Here is the URL: https://redmine.pfsense.org/projects/pfsense.

fireodo

@bmeeks said in Installed Packages Notification:

@Raffi_ said in Installed Packages Notification:

I think there should be a big red warning on the Installed packages tab when pfsense itself has an update available. Or better yet grey out the update buttons when pfsense has an update available. This doesn't prevent people from doing it via CLI but I personally always update via the GUI buttons. I'm guessing most users do as well.

That would make an excellent Feature Request for the pfSense Redmine Site. Here is the URL: https://redmine.pfsense.org/projects/pfsense.

This I subscribe too - I had that bad experience too in my "beginner" time (click before thinking ) and had to rebuild my firewall from scratch ...

fireodo

Raffi_

@bmeeks said in Installed Packages Notification:

@Raffi_ said in Installed Packages Notification:

I think there should be a big red warning on the Installed packages tab when pfsense itself has an update available. Or better yet grey out the update buttons when pfsense has an update available. This doesn't prevent people from doing it via CLI but I personally always update via the GUI buttons. I'm guessing most users do as well.

That would make an excellent Feature Request for the pfSense Redmine Site. Here is the URL: https://redmine.pfsense.org/projects/pfsense.

Someone beat me to it. I went in and +1ed the request. Hopefully others will too.
https://redmine.pfsense.org/issues/10464

newUser2pfSense

Gertjan...thank you for the reply. I don't think the cron image is being displayed from the first snippet of code. Did you mean to show the cron entry for this code in an image? Thanks.

Create a cron entry like :

![eb2c5802-f679-4329-8eec-d565cb94fa30-image.png](/assets/uploads/files/1606810338178-eb2c5802-f679-4329-8eec-d565cb94fa30-image.png)

Gertjan

@newUser2pfSense : Corrected !

newUser2pfSense

Gertjan...Thank you! I appreciate your time.

newUser2pfSense

Gertjan...Just a followup to say it works. Thank you.

Viper_Rus

And how to modify this script so that notifications come to telegram?

And it would be nice if it reported about the appearance of an update for pfSense itself

Raffi_

@Viper_Rus said in Installed Packages Notification:

And how to modify this script so that notifications come to telegram?

And it would be nice if it reported about the appearance of an update for pfSense itself

No idea about telegram, but I can confirm this script does send a notification about updates to pfsense itself.

stephenw10

If it's sent via the included notify functions then it should appear on all configured notification methods.

Gertjan

@Viper_Rus said in Installed Packages Notification:

And how to modify this script so that notifications come to telegram?

Locate the last line in the script :

    notify_via_smtp($msg);

replace it with

    notify_all_remote($msg)

@Raffi_ said in Installed Packages Notification:

And it would be nice if it reported about the appearance of an update for pfSense itself

It does.
An update can be a core FreeBSD package, a pfSense package and also an 'OS' (= pfSense update).

Viper_Rus

@Gertjan

Thanks!!!!!

At the moment I have everything updated. But to check the script, I run: "/usr/local/bin/php -q /root/pkg_check.php" manually. The answer is:
"pfSense version 23.05.1 (installed) is current"

This is fine? Now wait for some kind of update? :)