25.1RC1

Started by JayDee, January 22, 2025, 07:26:05 PM

Previous topic - Next topic
January 22, 2025, 07:26:05 PM Last Edit: January 22, 2025, 07:33:06 PM by JayDee
Hello everyone. Please don't hit me too hard, I don't speak English well (googletranslate).
I want to ask a few questions:
1. I currently have the version: 25.1.r_6, I still don't understand what version this is.
2. When I try to update, it tries to ask me for the version: Fetching packages-25.1.r1-amd64.tar (screenshot), but it constantly hangs at this place.

3. How to painlessly return from RC to the Community version.
I apologize for the stupid questions, I'm new and just learning. If possible, please tell me in more detail for each point.

You did update from Beta to RC1?

If you did a snapshot, you can revert to a previous snapshot.

Regards,
S.
Networking is love. You may hate it, but in the end, you always come back to it.

OPNSense HW
APU2D2 - deceased
N5105 - i226-V | Patriot 2x8G 3200 DDR4 | L 790 512G - VM HA(SOON)
N100   - i226-V | Crucial 16G  4800 DDR5 | S 980 500G - PROD

Quote from: Seimus on January 22, 2025, 07:32:24 PMYou did update from Beta to RC1?

If you did a snapshot, you can revert to a previous snapshot.

Regards,
S.
Yes, I switched from beta.
Unfortunately I didn't take a snapshot.

January 22, 2025, 07:42:50 PM #3 Last Edit: January 22, 2025, 07:44:40 PM by JayDee
It doesn't bother me too much that it freezes through the GUI, I update via SSH. I just can't figure out what version this is? in the changelog it simply says RC1, so I think I did something wrong.
I am attaching a screenshot of an attempt to update to RC1 via SSH and you can see the inscription on it: All repositories are up to date.

The 25.1.r_6 looks like is a middle jump to 25.1.r1.

I have the same on my LAB node. When I try to upgrade the system it will show me  25.1.r1 and fetches it but nothing happens. Most likely the upgrade path is not yet ready. Wait till tomorrow.

Regards,
S.
Networking is love. You may hate it, but in the end, you always come back to it.

OPNSense HW
APU2D2 - deceased
N5105 - i226-V | Patriot 2x8G 3200 DDR4 | L 790 512G - VM HA(SOON)
N100   - i226-V | Crucial 16G  4800 DDR5 | S 980 500G - PROD

Set release type to "community", check for updates and update. Voila: 25.1.r1 (25.1.r1).

The underlying truth is that both 25.1.r_6 and 25.1.r1 are almost entirely the same anyway.

If you used the 25.1-BETA image to install your release default is only "development".

If you used the 25.1-RC1 image to install your release default is already "community".


Cheers,
Franco

aaah I always forget about that option

25.1-BETA set to community and upgrade >
QuoteVersions
OPNsense 25.1.r1-amd64
FreeBSD 14.2-RELEASE
OpenSSL 3.0.15

Regards,
S.
Networking is love. You may hate it, but in the end, you always come back to it.

OPNSense HW
APU2D2 - deceased
N5105 - i226-V | Patriot 2x8G 3200 DDR4 | L 790 512G - VM HA(SOON)
N100   - i226-V | Crucial 16G  4800 DDR5 | S 980 500G - PROD

January 23, 2025, 03:30:43 AM #7 Last Edit: January 23, 2025, 03:32:39 AM by GrantSquirt8415 Reason: adding that I rebooted after each attempt
Quote from: franco on January 22, 2025, 09:12:44 PMSet release type to "community", check for updates and update. Voila: 25.1.r1 (25.1.r1).

The underlying truth is that both 25.1.r_6 and 25.1.r1 are almost entirely the same anyway.

If you used the 25.1-BETA image to install your release default is only "development".

If you used the 25.1-RC1 image to install your release default is already "community".


Cheers,
Franco

Thank you!

I had this same issue.

Attempted to update the system twice with Type = "Development" selected and got the following:
***GOT REQUEST TO UPGRADE***
Currently running OPNsense 25.1.r_6 (amd64) at Thu Jan 23 02:13:22 UTC 2025
Fetching packages-25.1.r1-amd64.tar: ......................................................................... done
Extracting packages-25.1.r1-amd64.tar... done
Please reboot.
>>> Invoking upgrade script 'sanity.sh'
Passed all upgrade tests.
>>> Invoking upgrade script 'unbound-duckdb.py'
Unbound DNS database exported successfully.
>>> Invoking upgrade script 'cleanup.sh'
***DONE***

PS: I rebooted twice. Once after each attempt thinking this could have been like the CrowdSec issue a few point releases back which would hang and prevent a reboot.

Switched Type to "Community" and then re-ran the check for update and got the following:
***GOT REQUEST TO UPDATE***
Currently running OPNsense 25.1.r_6 (amd64) at Thu Jan 23 02:25:14 UTC 2025
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Checking for upgrades (103 candidates): .......... done
Processing candidates (103 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.
Checking integrity... done (0 conflicting)
Nothing to do.
Checking all packages: .......... done
Nothing to do.
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
The following packages will be fetched:

New packages to be FETCHED:
    opnsense: 25.1.r1 (5 MiB: 50.00% of the 9 MiB to download)
    opnsense-devel: 25.1.r_6 (5 MiB: 50.00% of the 9 MiB to download)

Number of packages to be fetched: 2

The process will require 9 MiB more space.
9 MiB to be downloaded.
Fetching opnsense-25.1.r1.pkg: .......... done
Fetching opnsense-devel-25.1.r_6.pkg: .......... done
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Checking integrity... done (1 conflicting)
  - opnsense-25.1.r1 conflicts with opnsense-devel-25.1.r_6 on /boot/lua/brand-opnsense.lua
Checking integrity... done (0 conflicting)
The following 2 package(s) will be affected (of 0 checked):

Installed packages to be REMOVED:
    opnsense-devel: 25.1.r_6

New packages to be INSTALLED:
    opnsense: 25.1.r1

Number of packages to be removed: 1
Number of packages to be installed: 1
[1/2] Deinstalling opnsense-devel-25.1.r_6...
Stopping configd...done
Resetting root shell
Updating /etc/shells
Unhooking from /etc/rc
Unhooking from /etc/rc.shutdown
[1/2] Deleting files for opnsense-devel-25.1.r_6: .......... done
[2/2] Installing opnsense-25.1.r1...
[2/2] Extracting opnsense-25.1.r1: .......... done
Updating /etc/shells
Registering root shell
Hooking into /etc/rc
Hooking into /etc/rc.shutdown
Starting configd.
>>> Invoking update script 'refresh.sh'
Writing firmware settings: FreeBSD OPNsense
Writing trust files...done.
Scanning /usr/share/certs/untrusted for certificates...
Scanning /usr/share/certs/trusted for certificates...
Scanning /usr/local/share/certs for certificates...
certctl: No changes to trust store were made.
Writing trust bundles...done.
Configuring login behaviour...done.
Configuring cron...done.
Configuring system logging...done.
=====
Message from opnsense-25.1.r1:

--
TBA
Nothing to do.
Starting web GUI...done.
***DONE***

I did a fresh install from the 25 RC1 image downloaded from the official repo. Upgrade from the BETA 25 to RC1 ended up on task: extracting.
Installed Zenarmor, crowdsec, IDS IPS ET pro + free and restored from backup file taken on version 24.7.12. Its been up for 3 hours, suddenly no access to GUI, not even via Wireguard network from an allowed device.

After reboot same issue, VPN stopped working as well. No access from LAN, nor other devices - clean reinstall to 24.7.12_2 solved the problem, will stay away from 25 until all issues are solved - for now very unstable.

CPU 1115G4 - 4 port mini pc with Intel 226.