23.1r1 - version displayed in UI?

[Patrick M. Hausen]

Hello,

this is what I get when I check for updates, even after explictely setting the mirror to OPNsense, NL:



is this the correct version?

Thanks,
Patrick

[franco]

It's the correct version for opnsense-devel, but that's not 23.1-RC1 because that isn't reachable yet.

Mostly the same, minus the new base and kernel... that might be required for some functionality.


Cheers,
Franco

[Patrick M. Hausen]

You wrote in the announcements forum that RC1 was released - how do I install it from a running 2.7.10_2?

[franco]

Other than wait for 22.7.11 for upgrade paths to be included I suppose you could run:

# opnsense-update -ur 23.1.r1

That works from both the development and community version. I strongly recommend updating to 22.7.10 before attempting this.


Cheers,
Franco

[Patrick M. Hausen]

Hmmm ...

Code: [Select]

root@opnsense:~ # opnsense-update -ur 23.1.r1
Fetching packages-23.1.r1-OpenSSL-amd64.tar: .................................................................................... failed, signature invalid

Not that important. I misread the release announcement as "available now". And I would run an RC1 in production, at least at home.

[The_Dave]

I've got the same problem when trying to upgrade from the community repository.

[franco]

Only the development version has the fingerprint for the 23.1 signatures. If you want to insecurely upgrade from the community version use "-i" parameter.

It'll all fit together eventually. For now 23.1-RC1 is image-only, next week will unlock development version (from GUI) and end of January will unlock community version.


Cheers,
Franco

[Patrick M. Hausen]

So I'll start testing next week. Thanks!

[Patrick M. Hausen]

Still confused. What is "23.1.r_20" and how do I get the supposedly released RC2?

Thanks,
Patrick

[danderson]

I did opnsense-update -ur 23.1.r1 last week then just normal update via GUI and I got to RC2. Setting for Type in Firmware Settings is the Community version

Still confused. What is "23.1.r_20" and how do I get the supposedly released RC2?

Thanks,
Patrick

[newsense]

Still confused. What is "23.1.r_20" and how do I get the supposedly released RC2?

Thanks,
Patrick

Hi Patrick,



RC1 showed up in the GUI as 23.1.r_6 and RC2 is showing up as 23.1.r_20 - or at least that's my understanding after performing the upgrades on my FWs.


I am on the development train in Settings-Firmware and will switch back to Community after the official release, then look for any missing updates/changes up from RC2.


After  you are set on the Dev train this is the better avenue to upgrade from RC1 according to a similar question on Twitter answered by the team, and it's what I used to get to RC2 as well:

Code: [Select]

opnsense-update -bkr 23.1.r2
It doesn't look like a reboot is mandatory, I did it nevertheless to see if everything comes up nicely, and I have nothing to report no matter how simple/complex the configuration is.




The one bit of feedback that I have fo the OPNsense team would be to adopt a similar approach as seen in TrueNAS. Development would always be the -devel version and major versions with Betas and RCs once published are selectable in a dropdown menu. I'm not sure if the work required would justify the time - whatever the decision will be (if not already made) will be fine with me.

[Patrick M. Hausen]

I did opnsense-update -ur 23.1.r1 last week then just normal update via GUI and I got to RC2. Setting for Type in Firmware Settings is the Community version

That worked. R2 up and running in development environment. Very nice, no issues so far. Let's try private production next - later this evening 

May I hint at my OPNsense development and testing project (again)?

https://github.com/punktDe/vagrant-opnsense

Completely reworked for up to date versions of VirtualBox and Vagrant. Current Vagrant version mandatory, because they had some nasty bugs in networking and NFS sharing.

[danderson]

ive been running private production at home since RC1 and other than the 1 issue that I posted here and at github that was recently resolved ive had no issues.