OPNsense Forum

English Forums => Hardware and Performance => Topic started by: chemlud on May 27, 2021, 05:16:12 pm

Title: Move to new appliance - config import
Post by: chemlud on May 27, 2021, 05:16:12 pm
Hi!

Planning to move to a new device (different interface names...), so simply importing the config will not work with DHCP, suricata, FW-rules etc.

What is the latest news on moving the config file? Manually editing interface names? What are the problems?

Many thanks for some input!
Title: Re: Move to new appliance - config import
Post by: opnfwb on May 27, 2021, 05:25:31 pm
I've sort of done this when moving between VMs on different platforms (VMware to HyperV) or when converting a VM to a physical platform.

I'll caveat this with my configs not using IDS/IPS/Sensei. I'm mainly just using a traffic shaper, DHCP, Unbound DNS, NTP server, basic stuff that is supported without add-ons.

For example, if I'm going from a HyperV based install (hnX NICs) to a VMware based installed (VMX NICs), I just edit the config file, find the 'hnX' adapters, and change these to 'vmxX', where X is the adapter number. The only thing you should double check is the order of the adapters in the new appliance that you are moving to. If you get this order correct, everything will come up perfectly after a config restore and reboot. It's been a very simple process for me and I've used this method dozens of times now.
Title: Re: Move to new appliance - config import
Post by: chemlud on May 27, 2021, 05:41:58 pm
Thanks! Any things to avoid with manual editing the config.xml? :-)

I also think about moving the last pfSense to OPNsense, any recent experience in importing (editied?) parts of the old config.xml (DHCP? Firewall rules? Aliases?) to OPNsense? Or start totally from scratch? Havn't done this for quite some time.
Title: Re: Move to new appliance - config import
Post by: opnfwb on May 27, 2021, 05:49:20 pm
I'd just make a backup of the backup so that you always have the original config, just in case an edit goes wrong.

I've never tried to import or edit a pfSense config on to an OPNsense install. It may work but, who knows? At this point the projects are divergent enough I wouldn't trust it and if it was me, I would personally start over from scratch. At the very least, I would try it on a VM first in lab, snapshot the VM and then import the hacked config file to see what happens.

Title: Re: Move to new appliance - config import
Post by: thogru on May 27, 2021, 07:12:20 pm
Hi chemlud,

I moved my OPNsense config from an appliance to VMware (just for testing purposes).

Here are my notes:

Kind Regards
Thomas