Archive > 18.1 Legacy Series

[OBSOLETE] How to test the development version

(1/17) > >>

franco:
Hello everyone,

The development package is available now for the upcoming 17.1 and updated alongside each stable release. You can read about its most prominent changes here:

https://forum.opnsense.org/index.php?topic=3478.0

With 16.7.1 and up, it's possible to switch to the development version by invoking this command on a shell:

# opnsense-update -t opnsense-devel

Switching back to the release version is done by typing the following instead:

# opnsense-update -t opnsense

On top of using the opnsense-devel package, it's now (as of 16.7.10) possible to upgrade to the next FreeBSD 11.0 underneath as well by invoking the console menu item 12, typing "17.1.b" at the prompt.

THERE IS NO SAFE WAY TO UNDO THIS, PLEASE MAKE SURE YOU BACK UP YOUR CONFIGS, SNAPSHOT YOUR VMS AND/OR USE APPROPRIATE TEST SETUPS.

FURTHERMORE, THE UPDATE SETS ARE UPDATED INFREQUENTLY UNTIL THE RELEASE CANDIDATE PHASE IS REACHED.

It's possible to move back to the stock 16.7, but newer files can linger in the file system preventing the downgrade or proper operation thereof.

# opnsense-update -ur 16.7
# /usr/local/etc/rc.reboot

Switching the top package is also required for using the upgrade mechanism from the git repository to get even newer changes:

# opnsense-code core
# cd /usr/core
# git pull
# opnsense-update -t opnsense-devel
# make upgrade CORE_ABI=17.1


Cheers,
Franco

tillsense:

--- Quote ---# pkg install git
# cd /usr
# git clone https://github.com/opnsense/core
# cd core
# make package-keywords
# opnsense -t opnsense-devel
# make upgrade

--- End quote ---

small typo


--- Quote ---...
#opnsense-update -t opnsense-devel
...

--- End quote ---

cheers till

franco:
Nice catch, sorry, fixed now. :)

sfn:
If we upgrade our opnsense like that will be opnsense beta version of 17 ? Can we use multiwan with Squid Proxy ?

franco:
Not yet, I'm still working on patches with FreeBSD.

Navigation

[0] Message Index

[#] Next page