@stephenw10

I will check.

Interesting though, because pre-upgrade to Pro, the CE edition updated just fine.

@svandive

I foolishly also made this assumption thinking it should have just worked out of the box.

The issue im getting is after various permutations messing with CSM, secure boot, various USB sticks and other variables, i still cannot pass (this is just past the splash page to even install pfsense). The only thing left i havent tried is a BIOS update.

Loading kernel...
/boot/kernel/kernel text=0x1a4c98 text=0xff3048 text=0x17ed568 data=0x180+0xe80 data=0x24c808+0x3b37f8 0x8+0x1d4108+0x8+0x1e9a19-
Loading configured modules...
/boot/kernel/zfs.ko size 0x619a40 at 0x37be000
/boot/entropy size=0x1000
/boot/kernel/opensolaris.ko size 0x1e2a8 at 0x3dd9000
/etc/hostid size=0x25
staging 0x67e00000-0x6c51a000 (not copying) tramp 0x6c51a000 PT4 0x6c51b000
Start @ 0xffffffff803a5000 ...
\

Going forward this should be less of an issue. We reduced the memory requirement for pkg by using a different compression.

You are seeing no branches like that?

I mean it's definitely more secure to stop passing traffic until the admin corrects a config mismatch than to just keep passing traffic on what might be correct. For example this is the same situation you might hit after importing a config into entirely new hardware where no NIC/Interface can be guaranteed.

I agree though it would be better to tie the interfaces to a specific MAC to prevent re-ordering. But doing so is non-trivial.

There have been a few feature requests open for this over the years. Like: https://redmine.pfsense.org/issues/410

Yes, it will definitely have changed your NDI which is why you're seeing the repo check failures.

If you send me your NDI and order number in chat I can check it.

The i210/i219 NIC uses the igb driver and the x550 NIX uses ixgbe. So if you boot the firewall with a config that contains igb0-4 assigned it will drop to the interface assign screen at the console because two of those no longer exist That's expected.

Not really! If I could I'd try to replicate it that way but so far I've been unable to.

@Gertjan Thank you so much for the info.

Mmm, your WAN doesn't show an IP address at all. So if you're expecting it to pull a DHCP lease from somewhere then you probably have a L2 disconnect somewhere.

@P3R
Thanks for posting!

I noticed the firewall setting too. I think I've tried disabling it, not sure though.
Will test it again and report back.
Thank you!

Successfully upgraded from 24.03 to 24.11 via command line (SSH).

I'd been dreading the unpleasant task of dealing with the previous GUI update failures, but SSH -> Option 13 -> Reboot and back up in ~3min with little trouble.

Thank you @patient0, @stephenw10, @SteveITS for replying. The 2.7.2 update became available and the available packages are now listed after running "certctl rehash".

Yes you can still import an older config. If it's using some deprecated feature the config upgrade code will handle that.

No problem, glad I could clarify. 👍

If if gets fixed it will be in 25.07.