Yup, they are there but they should be at that linked page too. Digging...

@doxthefox Glad it's working now, sometimes just doing a reinstall and restore from config is the easiest solution lol.

It might work after a while. That particular error is probably because you have the dashboard set to check for updates, so once you login it's kicking off a session of pfSense-upgrade to check for updates. Since you're offline, that will take a while to time out, and going back to the dashboard would start it checking again.

That said, using the CLI in that specific case is probably more reliable. GUI packages are named pfSense-pkg-<name> when operating with pkg or pkg-static directly, you'll want to install/uninstall them using that name. To see what packages like that are installed, use something like pkg-static info -x pfSense-pkg.

@N8LBV said in Update 2.7.0 Dev to Stable process?:

I did not see this in the upgrading docs.

I'm not surprised it's not mentioned there. As I mentioned, the typical pathway would be DEVEL --> RC --> RELEASE, and that pathway is supported. Upgrading from RC to RELEASE is supported because when the RC is available, development there ceases. The only exception would be if a huge showstopper problem was found. In that case RC might get an update, or might even be pulled and the branch fall back into DEVEL.

The problem is that the versions of critical pieces of the OS and supporting shared libraries change as the next DEVEL version progresses. Each DEVEL update can move the DEVEL and RELEASE branches farther apart at the kernel and shared library levels. There rapidly approaches a point where you can't go backwards.

I don't know what your level of expertise is with FreeBSD software development and software development in general, but OS and shared library versions are very critical to other software running on a platform. pfSense is FreeBSD at its heart, but it is a slightly modified FreeBSD kernel. The GUI you see is handled by PHP. Changes to only PHP source code would normally be fairly easy to "downgrade". But if something in the kernel or shared libraries changes, that is not easy to "downgrade". By "downgrade" I'm talking about moving backwards from a DEVEL version to RELEASE.

A really big change between 2.6 and 2.7 (and now 2.8 DEVEL) was the move to PHP 8.x from PHP 7.4.

@jonathanp123
what page are you showing in your screenshot?

@bmeeks Thanks for your ideas.
I have been planning on re-installs.
But really wanted to find a solid answer on if this was supported or is supposed to be supported first before drawing any conclusions that re-installation is the only route.

I am also wondering if I should files a bug report that it does not work.
It can't hurt - and then maybe I will get a hard "no" from the dev. team on this and have the answer.

Pretty much the entire reason I am posting about this.

@Sadsa said in Cannot update through package or get upgrade:

which meant i had to install gcc, which is what im trying to do now

gcc is part of a rather big build tools chain.
It's probably easier to install a FreeBSD 'as close as possible' to the pfSense FreeBSD kernel, and then add the build tools and stuf you need, compile, link (static link, I guess, as it will make a mostly independent program/library) and copy the result over to your pfSense.
pfSense is not a development device, it's a firewall ;)

@cobray I have of course found that link.
It's not official it's not from here (Netgate forum) and there is not wone single comment to support it.
It links off to some site with a domain name in Romania.

I am looking to discuss this within the forum and support.
And if it is supported or not and not a single response yet it.

Thanks
Steve

Also plugging 12v might help. :)

@rcoleman-netgate THANKS!

Easy peasy. Installed.

Now to make it all work ;)

I have a post over in upgrading/troubleshooting.
This is cool pretty excited about the release.
I have a number of system running 2.7dev.
But am unable to upgrade them.
Update page just shows "Unable to check for updates"
It's been 18 days since release and I'm surprised not to see any chatter about this.
I am not finding any official stuff on if this upgrade path is supported or not supported but I sure would like to be able to do this.
Verus a clean install and restore from backup.
But I am not finding where this is or is not the only way to get this upgrade done.

@fireodo Yep, we're aware and we're paying attention.

@SteveITS Thank you for your answer

@Stewart said in Upgrade from 2.4.5 to 2.6:

@SteveITS So, is it OK to go straight from 2.4.5 to 2.6.0?

I went from 2.4.5 to 2.6.0, but I did a clean install of 2.6.0 and restored the 2.4.5 config.xml file and it worked great. I don't know if the direct upgrade process works that smoothly. Ideally you'd test the process on-site and if it fails, be able to to a clean install of 2.6.0 and restore a fresh backup config, and if that works, ideally it'll work at your other sites.

@Rico said in SG-1100 upgrade horror, now brick:

No valid device tree blob found!
WARNING! Trying to fire up the kernel, but no device tree blob found!

That error implies it has failed to load the dtb file at boot. That means the file it tried to load wasn't present. So either it failed to access the file because it couldn't see the media or the file wasn't on the media. Or that the file it was trying to load was incorrect. The latter was the case here, the uboot env that contains the file name was wrong.

Steve

@rcoleman-netgate said in Minor display bug:

When did you download this installer file?

Ryan:
You sent me the link to the file on 03July at 1250 PDT.

And it worked very well, thank you.

Probably since you used sdb1 and not sdb. That is a full disk image so must be written to the disk directly.

@xgiovio Sure but as I noted we will move Professional and Enterprise subscriptions one time during the subscription period. But the terms on those subscriptions do dictate no transfers.

If you are not a TAC Professional or TAC Enterprise subscriber... the TAC Lite license is still free (at the time of commenting) so there's no reason to get a new one. It's the least painful path.