Upgrade path from CE 2.7.2 to pfSense+?
-
I am in a pinch. The brand new hardware (Netgate 1100) at a client’s business has failed. I need to get him up and running tomorrow. I don’t have a spare, currently.
I do have a mini PC, on which I was able to install CE 2.7.2. I would like to make the next step an upgrade to pfSense+. Where can I find the best instructions for doing that?
By the way, updating the NIC drivers (the NICs are Realtek) will be next. Would those driver updates survive an update to future versions of pfSense, or would they have to be reinstalled every time?
-
@DominikHoffmann
https://docs.netgate.com/pfsense/en/latest/install/migrate-to-plus.htmlYou’ll need to buy a license.
Otherwise https://docs.netgate.com/pfsense/en/latest/backup/restore-different-version.html
Don’t know about the drivers. CE is on an earlier FreeBSD version.
-
@SteveITS: I remember that there was a free upgrade path. Has that expired?
-
@DominikHoffmann yes.
https://www.netgate.com/blog/addressing-changes-to-pfsense-plus-homelab -
@SteveITS said in Upgrade path from CE 2.7.2 to pfSense+?:
@DominikHoffmann yes.
https://www.netgate.com/blog/addressing-changes-to-pfsense-plus-homelabNo wonder!
So, I am stuck with CE 2.7.2 for now. I found that Interfaces → Switch → VLANs does not exist. Is this a pfSense+ feature, exclusively, or is there a way to turn that menu on?
-
@DominikHoffmann Only a few Netgate models include a hardware switch.
-
@SteveITS: Does that mean that I won’t have to bother with duplicating this configuration from the Netgate 1100
on the NUC PC running CE 2.7.2?
-
@DominikHoffmann The switch doesn’t exist in the replacement PC.
The 1100 uses VLANs to isolate switch ports. Like https://docs.netgate.com/pfsense/en/latest/solutions/netgate-2100/configuring-the-switch-ports.html but it’s already done on the 1100.
You’d need to configure your own VLANs. Though they should exist from the restore.
-
Yes you'll still need to configure VLANs 5 and 6 since they're passed tagged to something external. But WAN, LAN and OPT can just be assigned to NICs directly in the other device.