Downgrade from pfSense+ to CE
-
yup - da0 is the 8gb virtual SCSI disk. da1 is the 1gb 'virtual usb key' I added. I can mount da1 after initial install and mount using 'mount_msdos' command from CLI - and see /conf/config.xml on the device as well.
I know there's way of moving config.xml manually to /cf/config,xml and rebooting. I've tried this and works well. I still have to go through initial WAN interface config at minimum before I can do this method of restore.
As @ScottishTom mentioned - I have done the web restore, and CLI restore mentioned above. They both work equally well. Was just curious why the 'restore during fresh install' feature was not working for me.
-
You also tried config.xml in root of da1?
-
Had a chance to try another fresh install in another test instance. Seems to work now - after I copied config.xml from /conf/ folder to root of USB key. Now it seemed to act like I expected it too.
- Booted pfSense 2.7.0
- Performed fresh install, chose reboot option
- Old config restored during initial boot of new install!
All my reading of the documents mentions using /conf/ folder - with an optional check of root.
-
Originally the ECL only looked for
/config/config.xmland the config recovery during install looked in/conf/config.xml.But now both also look in the root of the USB so I always just use that.
Steve
-
Good to know - I'll place my restore config files on root of USB key from now on! Haven't needed to do these types of restores too often.
Using the 'restore-on-install' I have migrated my HA pair to CE-2.7.0 without issue. Everything works as expected. I do see that some of the 'Hardware crypto' options are gone. The Polychacha is no longer in the list of 'Hardware crypto'. I do have some WireGuard tunnels but I have plenty of CPU if needed.
-
Just done the revert to 2.7.0 from Plus as well. The funniest thing is that doing a full reinstall from a USB stick takes less time and less downtime than doing an online upgrade… Must remember that next time.
-
@Vollans said in Downgrade from pfSense+ to CE:
Just done the revert to 2.7.0 from Plus as well. The funniest thing is that doing a full reinstall from a USB stick takes less time and less downtime than doing an online upgrade… Must remember that next time.
Glad it went so well. Of course, using CE is just a lily pad for now as Netgate has warned that it will not be as well supported going forward with development, updates and features focused on Plus.
Clearly I acknowledge that nothing much can be trusted to Netgate right now but they will have to work hard to restore that - and fast.
️ -
@RobbieTT Yeah, but at least it avoids rash decisions in the meantime. I’d be loathed to give up on pfBlockerNG, which the obvious product to move to would involve. The menu remembers my upgrade to Plus and offers to complete it if I wish to, so nothing lost so far really for me.
-
@Vollans Understood and the move to CE is probably a good place to be whilst Netgate continues to shoot itself in the haze of untrustworthy statements.
️ -
@RobbieTT And whilst the config file is still the same, the best time to do it.
-
those who took part in testing 23.09, like me, have a problem with returning to CE :)
-
@Viper_Rus Unless you’ve made major config changes recently, roll back to the previous release if you’re using ZFS, copy off config.xml, then do the reinstall.
-
@Viper_Rus No kidding. Send them the bill!
Pure Netgate corporate greed at it's finest....
-
@stephenw10 said in Downgrade from pfSense+ to CE:
2.7 has the same config version as 23.05.1 so it should import without issue.
See: https://docs.netgate.com/pfsense/en/latest/releases/versions.htmlSteve
Will that fall over if there were packages installed on plus that don't exist on CE ? Like OpenVPN client import ?
-
No it won't fall over. It simply won't re-install any packages that are not present in the repo.
Steve
