@Gertjan

I understand all of that.

In the end, it was all locking up so frequently, i wiped everything and did a reinstall with 2.7.2.

all has been solid ever since.

I know there isn't anything to go on with this because I'm not providing any logs, but as I said in an earlier post, uninstalling all packages and rebooting as per the documentation, still resulted in errors during the upgrade.

as of now, all is back up and running perfectly.

Yeah unless you actually need that wifi card it's better to remove it. It doesn't work in 2.8 yet anyway and just uses resources.

Indeed the memory can be an issue especially with larger upgrades. The memory usage during ZFS upgrades has been improved in 25.07 (to be released soon) to address the issue. You can check the system log for signs of processes being killed abruptly. If however you're still using UFS it's more likely to have been some other issue.

I decided to check out the repo to see what build looks like for CE. I noticed that 2.8.0-RELEASE is still not an available branch in the repo. The master branch version is currently 2.9.0-DEVELOPMENT. Is netgate going to post the 2.8.0-RELEASE branch for the main package and FreeBSD-src?

Upgrading from the local console is always the safest way. That is using the root user. More importantly you will see all the output from upgrade including after the reboot. So if there's some issue with hardware in the new OS version you will see it and be able debug.

@chpalmer said in Strange behavior with gateway:

???

When the default gateway is set to a failover group the 'Default' column in the gateways list should show the tiers. But in this screenshot it doesn't: https://forum.netgate.com/post/1221365
That's unexpected.

I had same issue for a long time.

Then I tried pkg update -f and got an error for SunnyVally repository
I figured that I had a old version of zenarmor installed that matches the FreeBSD 14 and not 15.
Upgraded the zenarmor to the latest version.

Haven't had any of the error messages for some time now. hopefully that was it.

Maybe this can be helpfull to someone.

@stephenw10 Unfortunately I am going to have to wait till I can bring down the network to test. If I take it down now and it doesn't come back up I will be having some hell to pay from the family...lol. 😃

@Wolfgangthegreat
...and to @comet424

I wasn't able to perform the 2.8.0 update this weekend, but when I got to the school this morning, it worked perfectly!

I appreciate the support from both of you, and from Netgate.

The backup/standby pfSense instance is back in place and ready in case I have a hardware failure, or a failure of the gray matter between my ears!

My best to all of you.

@Wolfgangthegreat For example (this is checked by default):
8544523b-d69b-4088-b221-d2532912455c-image.png

There was a backend issue that's now fixed.

Yup, there was a backend issue. Should be good now.

The repo seems to be back online today Jul 19th, I was able to complete the fresh install.

Hmm, but they are policy based tunnels? And 300 Phase 1 configs not a total of 300 Phase 2 configs for example?

I'm not aware of any issue in 2.8 that might present like that for IPSec.

and then it worked...

@PiAxel said in update from 25.07 beta to 25.07 RC:

The last version doesn't work for me!

??

How do you know that the latest version doesn't work for you, before installing that latest version ?

( 😊 )