pfSense + for Home User
-
“A few years back” means your installation is out of date, which not a good security practice. At this point you have three options.
-
Pay for a pfSense+ license and upgrade to the latest.
-
Backup your config using the GUI, download and install CE, then restore config backup via GUI.
-
If restoring config fails, install CE and manually set everything up again.
https://atxfiles.netgate.com/mirror/downloads/
-
-
@elvisimprsntr A few years back was just when I upgraded to pfSense +. I've updated to the latest versions along the way. Currently running 24.11. I need to know if the 24.11 backup config is compatible with CE. I have a ton of configs I do not want to reconfigure on CE.
-
@FrankZappa I'm don't know if replacing the SSD will be an issues. I thought only a change in NICs is going to be an issue.
Generally: You can import a plus config without issues as long as the config rev is not newer than the CE versions config rev.
For example 2.7.2 CE has config rev 23.3, Plus version 24.03 got the same config rev, that will work.
But if you are one anything newer than Plus 24.03 then the config rev is newer than any CE version available right now and you may run into issues.
See the list of pfSense version: https://docs.netgate.com/pfsense/en/latest/releases/versions.html#pfsense-plus-software.
Additionally if you use features only available in the Plus version, you'll loose them of course. Like boot environments and Ethernet Filtering.
-
@patient0 Nope, I don't use boot environments or ethernet filtering. I do use a VPN and I enabled KEA DHCP. Not sure if that matters. It really sucks that Netgate took the Plus version away from home users. I understand it's a business decision, but at least give us reliable options for something else i.e. downgrading to CE from Plus.
-
@FrankZappa said in pfSense + for Home User:
I enabled KEA DHCP
On 2.7.2 CE you may have to switch back to ISC DHCP since KEA is (even) less feature complete than on 24.11.
And regarding replacing the HDD/SSD, a post from two years ago from @JeGr : https://forum.netgate.com/post/1082405 . Then at least it seemed not to trigger a NDI change.
-
@patient0 said in pfSense + for Home User:
I'm don't know if replacing the SSD will be an issues.
That^. If your Plus sub is currently valid you should be able to reinstall to a new SSD from the net installer to 24.11 directly. The NDI won't change.
-
@stephenw10 I have a valid Netgate Device ID (Not a purchased Netgate Device. My pfSense rig is on an old laptop) and Netgate sent me the code for the pfSense + upgrade (when they were giving us the home edition for free). Do I just reuse the same code they sent me when re-installing on new SSD? Also, what is NDI? Thanks
-
Nope your NDI is already valid it won't need to be re-registered. Just boot the net installer, it will validate the NDI, and give your option to install 24.11.
-
@stephenw10 Really? It's that simple? Thanks stephenw10. My only concern is I was looking on Netgate's website and they have the following notice: "If you need to reinstall your Home+Lab version, we will be unable to provide a no-cost upgrade path from pfSense CE" https://www.netgate.com/blog/addressing-changes-to-pfsense-plus-homelab
Just to be clear, I never paid for the pfSense + upgrade. Are you saying when I install on a new SSD (same computer) it will give me the option to install 24.11 without any of the subscriptions? If so, you have made me a happy man.
-
As far as I know yes. As long as you are currently able to see the Plus pkg repos you should be able to. Since you are swapping out the SSD you will still have the old install to fall back on.
-
@stephenw10 That's my problem. I have no idea what I did with the old install. I was looking for it all morning. Never knew I would need to keep it. Also, where do I see the "Plus pkg repos"? Are they somewhere on my current install i.e. 24.11?
-
Go to System > Update > Settings to see what repo branch you're using. Then if you can see available packages in System > Packages you have access.
-
@stephenw10 said in pfSense + for Home User:
System > Update > Setting
Thanks. So here's a couple of screenshots just to double check I'm good. (Thanks for your help)
-
Yes, looks good. You would be seeing errors there otherwise.
-
@stephenw10 Many thanks stephenw10
-
@FrankZappa Sorry to be a pain, but those screenshots are from my current install on the failing SSD. The screenshots are NOT from the new SSD, which I have yet to install pfSense on.
-
Yes. But since the NDI will remain the same the net installer should validate it and allow installing 24.11 directly.
-
@stephenw10 Thank You Sir. Really appreciate the help.
-
@FrankZappa This is just a follow-up on this thread. Stephenw10 is spot on. I installed pfSense on a brand new SSD (the same computer). It asked if I wanted 24.11. I said yes, and all is right with the world. My Netgate ID is registered, and I still have pfSense +. I'm pretty happy. The only thing that didn't work on the new SSD is OpenVPN. I'm not sure why the config settings are a problem. Also, many of my previous packages did not install. No problem, I reinstalled them. Regardless, my pfSense + license is still good (until Netgate removes me). Thanks stephenw10. I would have gone down an entirely different, more complicated path if not for you.
-
@FrankZappa said in pfSense + for Home User:
many of my previous packages did not install.
If you've used the config.xml from the old system, all the package info should be in there. If the packages were not present (installed) on the new system, but referenced as installed in the imported config file, the new pfSense will auto install them.
IRC, this will happen in the back ground, and while this is ongoing, a banner will mention this on the dashboard (not sure).If packages still didn't come over, its 'look at the logs and your imported config file' time.
After all, if parts of the info didn't came over it's pretty clear that you don't have the entire list of the "what didn't make it".
Parts of what OpenVPN needs, like certificates and defined OpenVPN users could be one of them.
