Restore pfS config.xml to new h/w
-
@KOM said in Restore pfS config.xml to new h/w:
@chudak I usually just do a find/replace on the config.xml file.
Good idea!
What about device ID? Is it h/w dependent ?
-
@chudak No idea. I've used this method successfully several times in the past. The only Gotcha! I had to worry about was a certificate in the config file just happened to include the characters used to describe my interfaces, so don't just blindly replace. Check every one. There are only a few edits depending on how many interfaces you have,.
-
@chudak said in Restore pfS config.xml to new h/w:
What about device ID? Is it h/w dependent ?
The NDI is hardware dependent, yes, mostly the NICs. If you add NICs to an existing system the NDI will change. And a new system will also have a new NDI.
You would have to contact support to check if you can transfer the license to new hardware.
-
You do not need to edit the XML.
During the import the system/GUI will ask what you want to map to, and it will prompt you with the adapters it can see. -
If the new box also uses igb NICs it will just import and reboot without needing (or asking for) any changes. But the resulting order may not be same so be be aware.
-
@chudak said in Restore pfS config.xml to new h/w:
When restoring my config.xml do I need to do anything to map new interfaces?
Easiest method I have found is:
- Install pfsense with minimal Ethernet connections plugged in
- assign at least the Lan so you can access the GUI
- look at the interface naming internally to ascertain how it relates to the external labelling
- decide how you want to map your old interfaces to your new box
- import your old configuration and reassign the interfaces as you want them.
- save your new configuration
-
@Patch said in Restore pfS config.xml to new h/w:
@chudak said in Restore pfS config.xml to new h/w:
When restoring my config.xml do I need to do anything to map new interfaces?
Easiest method I have found is:
- Install pfsense with minimal Ethernet connections plugged in
- assign at least the Lan so you can access the GUI
- look at the interface naming internally to ascertain how it relates to the external labelling
- decide how you want to map your old interfaces to your new box
- import your old configuration and reassign the interfaces as you want them.
- save your new configuration
Thx!
And what did you do about the netgate device ID?
-
Netgate license is tied to the hardware.
- For Netgate hardware with hardware lifetime software updates included, that makes perfect sense to me.
- For third party hardware with a yearly subscription I’m not convinced it’s optimal.
Either way changing Netgate licensing is beyond me
-
@chudak Do you have a Plus license? If not the NDI doesn’t matter.
-
@SteveITS said in Restore pfS config.xml to new h/w:
@chudak Do you have a Plus license? If not the NDI doesn’t matter.
I do.
I wonder how long will I be able to stay on unregistered plus pfS
-
@chudak said in Restore pfS config.xml to new h/w:
I wonder how long will I be able to stay on unregistered plus pfS
The unregistered device won't get any updates at all but will run otherwise fine.
-
@patient0 said in Restore pfS config.xml to new h/w:
@chudak said in Restore pfS config.xml to new h/w:
I wonder how long will I be able to stay on unregistered plus pfS
The unregistered device won't get any updates at all but will run otherwise fine.
I wanted to install 23.04 and then upgrade
Sounds it won't be possible on unregistered device?
-
No it will need to be registered to see 24.03 available. Or any Plus version.
-
@stephenw10 said in Restore pfS config.xml to new h/w:
No it will need to be registered to see 24.03 available. Or any Plus version.
But I will be install the 25.x, yes?
-
@patient0 Yet another reason to avoid pfSense Plus. No tangible benefit for the average user but with the added hassle of DRM.
