System update showing 2.3.4_1 as "up to date"



  • Hi,

    I check for updates at irregular intervals (a few times/year), and the current version 2.3.4_1 has been reported as "up to date" for a looong time.

    Today i checked for updates and it was reported as "up to date".
    However, i had a nagging feeling that something may be wrong so i went to the homepage and found out that the current version is 2.4.4?!

    When checking the instructions for upgrade it is advised to uninstall all packages and update via the GUI.

    I'm a bit puzzled how to do it when the system report itself as "up to date"?
    Does anybody have any information to point me (the dumb ass) in the right direction?



  • A clarification.

    I'm a bit puzzled how to do it when the **system update web GUI ** report itself as "up to date"?



  • @Oidar said in System update showing 2.3.4_1 as "up to date":

    However, i had a nagging feeling that something may be wrong so i went to the homepage and found out that the current version is 2.4.4?!

    You missed https://www.pfsense.org/download/ or forgot to read / consult this forum ? Missed CNN ? ^^

    @Oidar said in System update showing 2.3.4_1 as "up to date":

    When checking the instructions for upgrade it is advised to uninstall all packages and update via the GUI.

    In your case, forget about the GUI. Go straight to the console, and use the Upgrade command line command (probably option 13).
    It will propose the upgrade, or more likely tell you that de firewall itself can't connect to the Internet **. The latter explains right away why it never proposed you an update.

    ** This can happen / has been seen before.

    Btw : 2.3.4 is probably a 32 bits version. 2.4.4-p3 exists only as a 64 bit version - 2.3.5 is the last "non-supported" 32 bit version. Check if your hardware supports 64 bits. If not, 2.3.5 is what's left as an option.

    To upgrade to 2.4.4-p3 you have to re install (see above for the download page).
    Download 2.4.4-p3.
    Export your current config.
    Read all the update and upgrade warnings, alerts, be-awares and other dangers. See here https://www.netgate.com/blog/
    Re install.
    Import settings (if needed - the installer might find them when installing).



  • @Oidar said in System update showing 2.3.4_1 as "up to date":

    A clarification.

    I'm a bit puzzled how to do it when the **system update web GUI ** report itself as "up to date"?

    Easy to explain.

    FreeBSD systems (like Linux based) have one big thing in commun : no news is good news.
    When the PHP scripts fails to contact the pfSense update/upgrade servers, it will not fail or show a failure. It will just re try a couple of hours later on. Like Windows update ^^



  • Thanks for the info Gertjan,
    It seems as a lot have happened under the hood and i have some reading to catch up with.

    I have to admit I'm ashamed not following up of this earlier...



  • @Oidar said in System update showing 2.3.4_1 as "up to date":

    I have to admit I'm ashamed not following up of this earlier...

    Well, if it works for you there is no obligation.
    Not upgrading has a small list of advantages. But keep in mind that you can only decide to not to upgrade when you know all the disadvantages. And that list is big.
    Just to name some of them :
    Packages are always developed against the latest version (pfSEnse doesn't keep packages for old pfSense versions) so thee can't be upgraded neither.
    Security issues !?
    Functionality issues !
    Often forgotten : old pfSense are not available anymore. When your system has a hardware failure, you have to reinstall - on another device probably. This forces you to make a major upgrade, and review the entire setup without really knowing what changed. All the time you gained by not upgrading becomes now a triple pay-back.

    Etc etc ^^


Log in to reply