Updating SG 4860 from 2.3.2-RELEASE-p1 (amd64) to the latest stable

[arenel]

Latest version (Currently 2.4.3) is not available for upgrade. Only 2.3.3 is available. Below text is from dashboard

===========================
System Netgate SG-4860
Serial: <Removed>

Version 2.3.2-RELEASE-p1 (amd64)
built on Fri Sep 30 14:36:56 CDT 2016
FreeBSD 10.3-RELEASE-p9
Version 2.3.3_1 is available.

Platform pfSense

CPU Type Intel(R) Atom(TM) CPU C2558 @ 2.40GHz
Current: 1200 MHz, Max: 2400 MHz
4 CPUs: 1 package(s) x 4 core(s)

=================================

Is there any hardware limits preventing upgrade to the latest?

Should do upgrade in multiple steps?

Can I install the latest version(2.4.3) instead of upgrading?
Is it recommended?

[jimp]

If you let the upgrade run it should find the correct version. For older versions we don't always feed their branch the complete set of hints to the current highest version, but it can pick that info up during the upgrade.

You could also set the branch to the 2.3.x legacy stable update branch to get it to 2.3.5-p2 and then form there move up to 2.4.3-p1. That step is not strictly needed.

[teamits]

1. see https://forum.netgate.com/post/681329 (phil.davis post) to switch to dev branch then back to stable. Seems to get something updated. I had to do this a couple of times on various 2.3.something installs as I recall.

2. if you run the update and it updates the update repo and almost immediately fails, just run the update again. That seems to be a common issue I've found across recent releases also. I don't have a link to a post handy but I read a post either here or on the old mailing list that the update is actually running in the background despite the failure message, and it will restart after a couple minutes on its own, however I have not found that to be the case.

[arenel]

@jimp
Thank you for your clear and prompt response

If you let the upgrade run it should find the correct version. For older versions we don't always feed their branch the complete set of hints to the current highest version, but it can pick that info up during the upgrade.

Thank you. I assume my device can be upgradable all the way up to the latest version(2.4.3 p1). Please let me know problem with that

You could also set the branch to the 2.3.x legacy stable update branch to get it to 2.3.5-p2 and then form there move up to 2.4.3-p1. That step is not strictly needed.

I could not see the 2.3.x legacy stable update branch option.

[Summer]

Hi, I'm experiencing a similar issue on a

System	Netgate SG-3100
Version	2.4.3-RELEASE-p1 (arm) 
built on Thu May 10 15:59:52 CDT 2018 
FreeBSD 11.1-RELEASE-p10 

The system is on the latest version.
Version information updated at Fri Aug 3 12:09:19 CEST 2018

===

Should I upgrade to experimental to get the stable 2.4.4 ?
Thanks, BR

[jimp]

2.4.4 is not yet released. It's still in development.