Migrating config pfsense plus to community edition
-
Hi,
I am running some tests on a community edition of pfsense and importing the configuration file from plus when it restarts I get a big text banner during the boot process about the configuration file being newer than the installed version.
As both plus and community edition are up to date, is it ok to ignore this warning?
-
It might be OK! It depends what you actually have configured.
But one thing you can do is import it into 2.8-Beta which has a newer config version.
-
@stephenw10 Is it possible to return to the stable version when thats updated from the beta?
-
Yes, when 2.8 is released you can upgrade to it from 2.8-beta.
-
@stephenw10 some feedback. It looks like this way creates issues with static routes and unbound, at least it did for me. What I ended up doing was...
Importing config to 2.7.2
- Setting interface IPs prior to restart - to keep internet connectivity after the restart
- Gives warning about newer configuration file, however reading the logs there are no issues reported.
When importing the config to 2.8 beta
- It gave errors in the console when booting at the stage of static routes. Although I did not grab these, it seemed to work.
- I could never get unbound to consistently start on boot, no matter what I did it would be in the stopped state.
My current route is using 2.7.2 importing the config and then updating to 2.8 beta, although for production I may stay with 2.7.2 and ignore the newer configuration warning on boot up.
In this method, there are no issues to report, and the boot log looks warning free. -
@madmaxpr FWIW for reference:
https://docs.netgate.com/pfsense/en/latest/backup/restore-different-version.html
