Yes, OPNsense runs very well as a virtual machine on Proxmox VE, and the install is almost identical to installing on real hardware. In short: you download the OPNsense DVD ISO image, create a VM with at least 3 GB of RAM and a virtual disk of at least 8 GB, attach two virtual network cards connected to two separate Proxmox bridges (one for WAN, one for LAN), boot the ISO, and run the standard installer. The official OPNsense virtual machines guide covers KVM, which is exactly what Proxmox VE is built on, and it recommends the DVD ISO for VM installs. This guide walks through each step in order, explains the choices that matter, and finishes with the one setting you must change afterwards: turning off hardware offloading.
What you need before you start
Most failed Proxmox firewall installs are really planning failures, so gather everything first. You need a Proxmox VE host that is already installed and reachable, and you need to know how the host connects to your network today, because you are about to insert a firewall between the host and the rest of the world.
- A Proxmox VE host with enough free resources: at least 3 GB of RAM and 8 GB of disk space for this VM, plus CPU headroom for your expected traffic.
- Two network paths: one that will face the internet or your existing router (WAN) and one that will serve your local network (LAN). Ideally these are two physical network ports on the host; a managed switch with VLANs can also work, but two ports keep things simple.
- The OPNsense DVD ISO image, decompressed and ready to upload. If you are not sure why the DVD image is the right one for a VM, read VGA vs DVD vs Serial vs Nano: Which OPNsense Image Do You Need? first.
- Console access to the Proxmox host that does not depend on the firewall VM itself, for example the host's own management address on the LAN bridge, a keyboard and monitor, or a remote management interface.
- About an hour of uninterrupted time, and a maintenance window if the host already serves other VMs that use the network.
That fourth point deserves emphasis. If you manage Proxmox through the same network that OPNsense will soon be firewalling, a mistake can lock you out of the host. Before you begin, confirm you can reach the Proxmox web interface on an address that stays reachable while the VM is stopped. The networking companion to this guide, OPNsense on Proxmox: Bridges, VirtIO and PCI Passthrough Compared, explains this host-management trap in detail.
Step 1: Plan your bridges
Proxmox connects virtual machines to networks through Linux bridges. A bridge behaves like a virtual switch: you attach one physical port to it, and every VM network card plugged into that bridge shares that port. For a firewall VM you normally create or use two bridges:
| Bridge | Physical port | Role |
|---|---|---|
| vmbr0 | The port connected to your modem or existing router | WAN side of OPNsense |
| vmbr1 | The port connected to your LAN switch | LAN side of OPNsense, and usually Proxmox management |
The bridge names and which one is which are your choice; what matters is that WAN and LAN never share a bridge. In the Proxmox web interface you can review and create bridges under your node's Network settings. If your host has only one physical port, you can separate WAN and LAN with VLAN tags on a VLAN-aware bridge and a managed switch, but that adds a layer of configuration you must get right on both ends. For a first install, two physical ports are strongly recommended.
Write down which bridge is WAN and which is LAN before you create the VM. During the OPNsense setup you will assign interfaces by their order and MAC addresses, and having the plan on paper prevents the classic mistake of swapping them.
Step 2: Get the DVD ISO onto the host
Download the DVD image with the chooser in the download section of our homepage (it serves the official file from the project release server) and, ideally, verify it before uploading. The current install image is named like OPNsense-26.7-dvd-amd64.iso.bz2: it is compressed with bzip2, so decompress it first to get the plain .iso file. In the Proxmox web interface, select your ISO storage (usually "local"), open the ISO Images section, and upload the decompressed file. Wait for the upload to finish completely before moving on; a truncated ISO is a common cause of a VM that boots to a blank screen or fails partway through the install.
Step 3: Create the virtual machine
Create a new VM in Proxmox and work through the wizard with these settings:
| Setting | Value | Why |
|---|---|---|
| OS / ISO image | The OPNsense DVD ISO you uploaded | The official VM guide uses the DVD ISO for virtual installs. |
| Machine type | i440FX or Q35 | OPNsense (FreeBSD) supports both chipsets on KVM; either works, so keep the default unless you have a reason to change it. |
| Memory | 3 GB minimum; more if you plan to run extra services | 3 GB is the official VM minimum; sizing guidance is covered in OPNsense Virtual Machine Requirements and Sizing. |
| Virtual disk | At least 8 GB | 8 GB is the minimum recommended virtual disk size in the official VM guide. |
| CPU | 1 to 2 cores to start | Enough for a home or small-office firewall; add cores for higher throughput or heavy services. |
| Network device 1 | Attached to your WAN bridge | This becomes the WAN interface. |
| Network device 2 | Attached to your LAN bridge | This becomes the LAN interface. |
Add the second network device after creating the VM, under its Hardware tab, if the wizard only offered one. Note the MAC addresses of both devices and which bridge each belongs to; you will match them against the interface names OPNsense shows you during setup. Set the VM to start at boot if you want the firewall to come up automatically after a host reboot, and consider a start order that brings OPNsense up before the VMs that depend on it for network access.
Step 4: Boot the ISO and run the installer
Start the VM and open its console in Proxmox. The DVD image boots into the OPNsense live environment. Let it boot to the login prompt, then log in with the user installer and the password opnsense: logging in as this user starts the installer. (The live environment itself can also be used with the user root and password opnsense, but for installing, the installer account is the direct route.)
The installer asks a few questions, in roughly this order:
- Keymap: accept the default unless your keyboard layout differs.
- Install type: choose Install and pick a file system. The official install guide notes that ZFS is in most cases the best option, but it needs a couple of GB at least; on a small virtual disk, UFS is a reasonable alternative.
- Disk selection: select the virtual disk you created. The installer warns that the contents of the disk will be destroyed, which is expected for a fresh VM disk.
- Swap: for install targets smaller than 16 GB, the official guide advises skipping the swap file, so skip it on an 8 GB disk.
- Root password: set a strong password when prompted. This replaces the default, and you will need it for console and web GUI logins afterwards.
- Complete and reboot: choose the option to complete the installation and reboot. When the VM restarts, detach or unmount the ISO (or set the boot order to the disk first) so it boots from the virtual disk instead of the installer.
Step 5: First boot and interface assignment
After the reboot you should see the OPNsense console menu, a numbered list of options from 0) Logout to 13) Restore a configuration. On a fresh install the system asks you to assign interfaces. The rule is simple: the first interface you assign becomes LAN, the second becomes WAN, and any further interfaces become optional (OPT) interfaces. Assign them using the plan you wrote down in Step 1, matching the interface names to the MAC addresses you noted from Proxmox.
You can skip VLAN configuration at this stage; VLANs can be added later in the web GUI. When assignment is done, the console banner shows your LAN address, which by default is 192.168.1.1/24, and the WAN interface defaults to DHCP. If the LAN address range clashes with the network your WAN side uses (a very common situation when an existing router also uses 192.168.1.x), change the LAN address from the console menu with option 2) Set interface(s) IP address before connecting any clients.
From a computer on the LAN bridge, open https://192.168.1.1 (or your new LAN address) and log in with the user root and the password you set during installation. If you did not change it, the default password is opnsense, and changing it is the first thing you should do. The setup wizard will offer to walk you through the basics; you can complete it now or skip it and configure manually.
Step 6: Disable hardware offloading
This step is small, easy to forget, and officially recommended for virtual machines. In the web GUI, go to Interfaces → Settings and disable all hardware offloading options (hardware checksum offloading, TCP segmentation offloading and large receive offloading). Virtual network drivers and offloading features frequently disagree with each other, and the official VM guide advises turning all of them off for optimal performance and compatibility in a VM. Save the settings and reboot the VM so everything starts cleanly with offloading disabled. Do this before you start benchmarking or troubleshooting throughput; many strange VM network problems trace back to this one page.
How to confirm it worked
- The VM console shows the OPNsense menu and a banner listing your LAN address (192.168.1.1/24 by default) and a WAN address obtained by DHCP.
- From a device on the LAN side, you can open the web GUI at the LAN address and log in.
- A client on the LAN receives an IP address from OPNsense by DHCP and can reach the internet through the VM.
- Interfaces → Settings shows all hardware offloading options disabled.
- Rebooting the VM from Proxmox brings OPNsense back up with the same configuration, which proves the install is on the virtual disk and not still running from the ISO.
Common problems and fixes
| Symptom | Likely cause | What to check |
|---|---|---|
| VM boots back into the installer | The ISO is still attached and first in the boot order | Detach the ISO or move the virtual disk first in the VM's boot order. |
| No network on either interface | Both NICs on the same bridge, or the physical port is down | Compare each NIC's bridge in Proxmox with your plan, and check the physical link lights. |
| Clients get internet but the LAN feels swapped with WAN | Interfaces assigned in the wrong order | Use console option 1) Assign interfaces and match MAC addresses to the bridges. |
| Erratic throughput or dropped connections | Hardware offloading still enabled | Disable all offloading under Interfaces → Settings and reboot. |
| You locked yourself out of Proxmox | Host management depended on the VM's network path | Use direct console access to the host, fix the bridge layout, and keep management independent of the firewall VM. |
Step 7: Update and take your first backup
Two closing tasks turn a fresh install into a system you can rely on. First, update: install images are only rebuilt with the January and July major releases, so the system you just installed trails the latest update in its series. In the web GUI, go to System → Firmware → Status and click "Check for updates"; if updates are offered, install them and let the VM reboot. Second, back up the configuration while it is still simple and known-good: go to System → Configuration → Backups and download the configuration file, keeping it somewhere other than the VM itself. If you later break something while experimenting with bridges, NIC models or rules, that small XML file is the difference between a five-minute restore and a full reinstall.
Next steps
Your firewall is installed, but a Proxmox firewall earns its keep in the details. Read the networking comparison to decide whether bridges are really your best option or whether PCI passthrough suits your hardware, add the QEMU Guest Agent so Proxmox can shut the VM down cleanly and report its addresses, and update OPNsense from System → Firmware once the basics work, since the install image always trails the latest update in the series. The official reference for everything in this guide is the OPNsense virtual machines documentation.