Restore pfS config.xml to new h/w

stephenw10

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.

Patch

@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

chudak

@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?

Patch

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

SteveITS

@chudak Do you have a Plus license? If not the NDI doesn’t matter.

chudak

@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

patient0

@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.

chudak

@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?

stephenw10

No it will need to be registered to see 24.03 available. Or any Plus version.

chudak

@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?

KOM

@patient0 Yet another reason to avoid pfSense Plus. No tangible benefit for the average user but with the added hassle of DRM.

Patch

@chudak no. Not with out buying a new plus subscription for that new non Netgate device.

Edit, from your other thread
@chudak said in Why do we need to pay for pfS + ????:

I paid for 2 years pfs + subscription.

In order to install on a new h/w I need to install CE and then transfer my subscription or buy a new one.

pfsense plus subscription Netgate sell is tied to the hardware and not transferable.
When buying a new subscription ( which was always a requirement) you can readily buy it for a new device.
As described above
said in Restore pfS config.xml to new h/w:

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

@Patch said in Restore pfS config.xml to new h/w:

@chudak no. Not with out buying a new plus subscription for that new non Netgate device.

I might be overreacting, but this is BS and adds only more troubles to users :(

stephenw10

If it's a paid subscription and you had to replace the hardware you should open a TAC ticket. We are not completely inflexible. Yes, it's tied to the hardware but if you are forced to change that we have options.