Is there a best practice when moving to a new hardware?

Started by datenimperator, July 05, 2022, 03:49:22 PM

Previous topic - Next topic
So I had my OpnSense running smoothly on a NUC-like mini PC (like the Protectly Vault FW4B). I wanted to upgrade my home network to 2.5GBit and upgraded the router hardware as well.

On my old appliance, the Intel I210at interfaces were numbered as igb[0,1,2,3]

On the new one, it is Intel I225-V, and they are named igc[0,1,2,3]

I did not expect the network interface names to change. So when I swapped the m.2 drive from the old to the new hardware, a lot of settings were broken, because they referred to non-existing interfaces.

Is there a smarter way to do this, something that would have accounted for the change in interface names? Regards

Christian

When you have retrived the old config, disconnect all ports from the new NIC, go to console (without SSH) and choose Assign interfaces and follow instructions.

This way opnsense should automatically update network card related things.

July 05, 2022, 09:15:42 PM #2 Last Edit: July 05, 2022, 09:24:51 PM by warheat1990
1. Download the config.xml from your old machine (System > Configuration > Backups > Download Configuration)
2. Open the xml file
3. Replace anything that says "igb" with "igc"
4. Fresh install OPNSense in your new machine
5. Restore the modified config file into new machine (System > Configuration > Backups > Restore Configuration)

I always use this method without any issue, just remember to reinstall the plugin after restoring as you have to do it manually, after the plugin is reinstalled, all the previous configuration for each plugins will be restored.

Quote from: warheat1990 on July 05, 2022, 09:15:42 PM
1. Download the config.xml from your old machine 
2. Open the xml file
3. Replace anything that says "igb" with "igc"
4. Restore into new machine

Ah yes, that too works, because backup files aren't encrypted and are just basic .XML files