Unable to upgrade 2.7.0 Community to pfsense plus Dev
-
You have an actual AT&T connection? You are using pfatt?
-
I dont use AT&T, I use Frontier fiber.
-
I found an old 3com switch this morning at work. I'm gonna see if I can use that to strip the vlan tagging.
-
Ah, well in 23.01 that should just work then. No script required.
Only the known e1000 issue may trip you up, if you have e1000 NICs. But you should be able to get past that by disabling vlanhwfilter. If you add that as a shellcmd it would survive the update.
Steve
-
+1 this upgrade path would be great.
Don't new installs of 2.7.x/23.01 do ZFS a little differently compared to upgraded installs?
I like the idea of a clean install on the latest branch so 2.7 > 23.01 would be great considering there is no option to fresh install 23.01 on generic hardware.
-
It would certainly be nice to have and we will be looking into it but upgrades from 2.6 will take priority.
-
I would need this as on current 2.7 not sure if started from scratch 2.6-23.01 if i could then apply config from 2.7 ??
pfsense plus 25.03 super micro A1SRM-2558F
C2558 32gig ECC 60gig SSD -
This is what I was hoping to do to. I worked on editing by backup config file so I can restore it on a fresh 23.01 switching my wan interface from using the netgraph script
-
Luckily I found an old dlink switch that I can use to get around using the script but I may wait to upgrade until I can install 2.7 - 23.0 fresh. Working on the backup config files I found lots of crap gets left behind from removed packages and old settings that are no longer needed.
-
@grandrivers said in Unable to upgrade 2.7.0 Community to pfsense plus Dev:
not sure if started from scratch 2.6-23.01 if i could then apply config from 2.7 ??
You can import a 2.7 config into 23.01 as long as the config remains the same version:
https://docs.netgate.com/pfsense/en/latest/releases/versions.htmlAt some point after 23.01 release 2.7 may move to a new config version at which point the config will warn you when you try to import it. You may get unexpected results if you are using anything where the config format has changed.
Srteve
