![]() ![]() ![]() My goal is to manage complexity in order to minimize troubleshooting and downtime. Also, sometimes I just need more time to properly research and implement a solution that will serve my needs well. I know I could run Proxmox in high availability mode, but I like the idea of keeping my router/network infrastructure separate and not have any dependencies with other systems. I would store backups on my dedicated Proxmox Backup Server for both my router and my Proxmox server. If I decided to run OPNsense in a VM, I would definitely still run OPNsense on its own hardware separate from my main Proxmox server so that any tinkering or updates I have to do on that server will not take down my network. In fact, it has caused me to re-evaluate running OPNsense in a VM instead of bare metal in order to have an easier restore process and the added benefit of remapping the network interfaces. I am glad I tried migrating to a new firewall before I had any real hardware or software issue(s) on my existing firewall because I discovered there is more to the process than simply importing the configuration. The overall process is a bit more involved than I had originally anticipated. However, the process may not get you 100% migrated over to your new hardware depending on the plugins you have installed as I will discuss in more detail later. ![]() ![]() The import process can save you a lot of time since you do not need to configure your router from scratch. If you have you an existing bare metal OPNsense installation and you wish to migrate to new hardware, you have the option of exporting your current configuration and importing the configuration during the installation of OPNsense on a new system. ![]()
0 Comments
Leave a Reply. |