Upgrades into RC1 via 26.1.11 opnsense-devel

[franco]

Hi,

For the brave early testers the upgrade path is now live:

1. Switch to release type "development" and save.
2. Check for updates and install.
3. Check for updates again and it will offer 26.7.rc1 and install.
4. After upgrade switch back to release type "community" and save.
3. Check for updates and install 26.7.r1.

This will make the installed files match the published RC1 images.

A note of caution:

This is a major upgrade in the exact sense of the word: FreeBSD 15.1, PHP 8.5 and OpenSSL 3.5 are the components where we can be sure more problems are hiding somewhere, but we won't find out any other way.  If you have third party repository or plugin installed proceed with caution: we do not vet upgrades of them and they are likely not ready to make the jump.  Removing them beforehand is likely the best course of action at the moment.


Cheers,
Franco

[MoonbeamFrame]

Just upgraded my lab firewall from 26.1.11_6  to 26.7.r1 without issue.

[newsense]

>>> If you have third party repository or plugin installed proceed with caution

As usual Zenarmor users will need to wait for an official announcement.

The mimugmail repository will have to be rebuilt against openssl35.
Until that happens and there's an announcement from Michael packages depending on the openssl3.0 will be silently uninstalled during the upgrade ( i.e. Unifi controller )

[julsssark]

I upgraded my test VM from 26.1.11_6 to 26.7.r1. I have some minor observations:

1) I had to check for updates multiple times at steps 2, 3 and 5. But the update eventually completed and it is running fine.
2) Thanks @newsense for posting about the mimugmail respository. I also ran into the same problem using the single repository with just AdGuard (mimugmail-single.conf). I could not get the upgrade to complete with that repo configured and I ended up needing to delete the repo config.

Just out of curiosity, has anyone built a digital twin (or as near as possible) of their network using Proxmox's SDN to better simulate testing/rules with VLANs? I tried to create one using Proxmox v8 last year but it didn't handle VLANs well and I haven't tried again with v9.

[julsssark]

PS - The new services dashboard widget is great!

[newsense]

>>> single repository with just AdGuard (mimugmail-single.conf)


Actually AGH is the outlier that survives the upgrade to openssl35 - because AGH uses its own ssl from Go.

Still, the mimugmail repo-whichever may be in use - needs to be deleted ( as suggested above) or renamed as .bak for now in order for the OPNsense upgrade to succeed.

[julsssark]

I tried to reinstall AGH single repository under 26.7.r1 and I still get the error:

pkg: Repository mimugmail has a wrong packagesite, need to re-create database

[newsense]

You don't add the current mimugmail repos on a 26.7.x OPNsense

You don't need the mimugmail repos for AGH if already installed. The AGH updates will work just fine


As long as BE and CE are on different versions of OpenSSL there should be a dedicated version of that 3rd party repository built against the respective OpenSSL target

[LHoust]

Actually I used the 26.7 RC1 Image for a "Fresh" Installation on Baremetal...

From the Console I Assigned my WAN/LAN Interfaces, a "New" IPv4 LAN Address and Specified an IPv4 DHCP Range for my LAN Interface...

Unfortunately the Laptop connected to the LAN Interface was NOT being assigned its IP Addresses and therefore I was unable to Connect to the OPNsense Web Interface!!!

After Assigning Static IPv4 IP Addresses to the Laptop, I was able to able to Restore my 26.1 Confirguation...

From there I was able to install the "Missing" Plug-INs, Restored my 26.1 Configuration a Second Time and after that things have proceeded "Normally"...

[franco]

@LHoust Still partially set up for ISC DHCP perhaps?


Cheers,
Franco

[julsssark]

@newsense - thanks for confirming. Yes, AGH continues to run under 26.7 even though the repo does not work.

I opened an issue on the MAXIT GitHub: https://github.com/mimugmail/opn-repo/issues/300

[franco]

I expect the repo is not working because the ABI directory changes from FreeBSD:14:amd64 to FreeBSD:15:amd64 and it's simply not available yet.


Cheers,
Franco