Testing the latest versions

[nivek1612]

Quick question is OPNsense 18.1.r_11 now the latest version for testing

Want to ensure I have upgraded correctly

Also is will this lock me on the latest 18.1 and install FreedBSD 11.1 on top ?

# opnsense-update -bkgr 18.1.b -n "snapshots\/beta"
# opnsense-update -L
# /usr/local/etc/rc.reboot

[phoenix]

Yes, is the answer to all your questions.

[nivek1612]

Thanks

[mais_um]

Can't have the OPNsense 18.1.r! still in OPNsense 18.1.b.

[phoenix]

Can't have the OPNsense 18.1.r! still in OPNsense 18.1.b.

He didn't say he was on 18.1.r1 he asked if those commands would update to the latest beta with the 11.1 kernel and it does.

[franco]

By the end of the week there will be the official 18.1.r1 with images and all....


Cheers,
Franco

[nivek1612]

LIKE :-)

[mais_um]

Can't have the OPNsense 18.1.r! still in OPNsense 18.1.b.

He didn't say he was on 18.1.r1 he asked if those commands would update to the latest beta with the 11.1 kernel and it does.

I did't say he said. I see packages on the repository with 18.1r and and I thought i was doing something wrong.

But thanks for let me know everything is right.

[franco]

Hi guys,

It's not final, but if you have opnsense-devel installed you can upgrade...

# opnsense-update -sn "18.1\/test"
# opnsense-update -ur 18.1.r1 -N OpenSSL
# /usr/local/etc/rc.reboot

The repo looks fine, OpenSSL-only at this point, but latest FreeBSD 11.1 for both i386 and amd64. Images are still being tested and release notes half-written.

If you feel like wanting to go back to the actual 18.1.r1 release (not opnsense-devel) the GUI will automatically take you there now during check + update as there is a new release type setting.


Enjoy,
Franco

[Julien]

Hi guys,

It's not final, but if you have opnsense-devel installed you can upgrade...

# opnsense-update -sn "18.1\/test"
# opnsense-update -ur 18.1.r1 -N OpenSSL
# /usr/local/etc/rc.reboot

The repo looks fine, OpenSSL-only at this point, but latest FreeBSD 11.1 for both i386 and amd64. Images are still being tested and release notes half-written.

If you feel like wanting to go back to the actual 18.1.r1 release (not opnsense-devel) the GUI will automatically take you there now during check + update as there is a new release type setting.


Enjoy,
Franco

Hi Franco,
tried the update to r1 however its said the kernel is locked on the b.

Code: [Select]

Kernel locked at 18.1.b-amd64, skipping.
Base locked at 18.1.b-amd64, skipping.

[phoenix]

Hi Franco,
tried the update to r1 however its said the kernel is locked on the b.

Then just unlock it with:

Code: [Select]

opnsense-update -U

[Julien]

Hi Franco,
tried the update to r1 however its said the kernel is locked on the b.

Then just unlock it with:

Code: [Select]

opnsense-update -U

Thank you Bill,
its unlocked using U and now its error out

Code: [Select]

Fetching packages-18.1.r1-OpenSSL-amd64.tar: .............No trusted fingerprint found matching file's                                   certificate
 failed

[franco]

Hi Julien,

You're not allowed to upgrade from 17.7.x yet, only 18.1.x works (opnsense-devel).

And I thought I specifically remember adding update overrides for the locks to avoid bricking the system a while back...

https://github.com/opnsense/update/commit/bd9640b6

Tested this twice today. From the latest version on opnsense-devel everything works as expected. Phew!

In any case, when the update fingerprint for 18.1 hits 17.7.x it'll all work out fine.


Cheers,
Franco

[Julien]

Hi Julien,

You're not allowed to upgrade from 17.7.x yet, only 18.1.x works (opnsense-devel).

And I thought I specifically remember adding update overrides for the locks to avoid bricking the system a while back...

https://github.com/opnsense/update/commit/bd9640b6

Tested this twice today. From the latest version on opnsense-devel everything works as expected. Phew!

In any case, when the update fingerprint for 18.1 hits 17.7.x it'll all work out fine.


Cheers,
Franco

Thank you Franco,
i'll update first to 18.1 and try it again.
i'll post the result while I tried it.

[DanMc85]

I updated to this build as well using the command line. Now I cannot access the management interface from an external web browser outside my network. Not sure if a SSL configuration changed for the Cipher with the new build or if it is a bug.

Google Chrome: ERR_SSL_PROTOCOL_ERROR

IE: This might be because the site uses outdated or unsafe TLS security settings. If this keeps happening, try contacting the website’s owner.