Current status of upgrading from pfSense

Started by Kompiler, April 22, 2015, 07:19:59 PM

Previous topic - Next topic
Hello all,

Some of you may know who I am - I apologize if this has been answered prior  but did not see a recent discussion.

What is the status of upgrading to OpnSENSE for someone that is running a pfSense nanobsd image?   I am considering upgrading to OPNsense but I wanted to inquire before bricking my current pfSense box.

TIA!

Hi there Kompiler,

there's a bit of history to unroll here... NanoBSD images with the two-slice approach have been removed -- we may put them back at some point but only after we've successfully merged all different modes into one image/installation (even the live cd/memstick does not run on any more custom code except unionfs/tmpfs to cope with the write failures). Too many code paths and exceptions were the initial motivation. Just recently we removed the /cf read-write merge magic because we believed it can be replaced by simpler approaches (just don't write that much). There's also extensive cleaning of system paths, unwinding soft-coded paths that are unlikely to change or won't change because the ports actually hardcode them, e.g. /var/run.

The current target now is providing embedded installations (noatime, no swap etc.) and a release image for SD cards which can be directly written to disk. I expect this to be finished next week hopefully.

So far I don't think we have bricked any installation (knock on wood) and there's a config importer+reinstall viable with the bsdinstaller these days as well as a google drive backup or the plain config export/import.


Hope that helps,
Franco
"AI has absolutely reduced the cost of creating technical debt." -- ChatGPT

So the nano.sh script is back stripped to a bare minimum. The tweaking is still ongoing, but it's a start: https://forum.opnsense.org/index.php?topic=342.0

FWIW, talking about upgrading... 2.1.5 upgrades are seamless, the config can be imported without a problem. For 2.2.* we have unclear licensing and config.xml divergence so that doesn't work out of the box, but might work when fiddling with the version number.
"AI has absolutely reduced the cost of creating technical debt." -- ChatGPT

OK sounds good.  If I am reading you correctly I should wait until next week?

We'll ship a working version with a NanoBSD image for 15.1.10 if you're looking for a stable entry point. I can't say whether it'S going to be included in the release itself or sneaked in on the side as a still-in-beta image, but basically, yeah, next week when we wrap up 15.1.10. :)


Cheers,
Franco
"AI has absolutely reduced the cost of creating technical debt." -- ChatGPT

The NanoBSD images can be found at https://opnsense.c0urier.net/releases/latest/

Have fun,
Franco
"AI has absolutely reduced the cost of creating technical debt." -- ChatGPT