You can install OPNsense on Proxmox in two ways: pass a physical network card’s ports straight through to the virtual machine, or give the VM virtual network cards on Linux bridges, which works without a spare NIC.
Everything here was checked in November 2026 against Proxmox VE 9.2.2 and OPNsense 26.7, which updates to 26.7.8 once it’s installed. If you’ve installed pfSense on Proxmox, OPNsense will look familiar, because the Proxmox side is the same.
Disclosure: Some links below are Amazon affiliate links, which means that I earn a percentage of each sale at no cost to you. Thank you for your support.
What You Need Before You Start
You need a working Proxmox host (here’s how to install Proxmox VE 9) with room for a VM that meets OPNsense’s minimums. Per the OPNsense virtual machine docs, that’s 3 GB of RAM and an 8 GB disk, and its hardware docs add a dual-core CPU.
The bigger decision is how the VM reaches your network:
- Pass through a physical NIC if OPNsense is going to be the router for your whole house. The VM gets two of the card’s ports, one for WAN and one for LAN, while Proxmox keeps its own port, and the host needs IOMMU support (VT-d on Intel, AMD-Vi on AMD). A dual-port card like the H!Fiber dual-port gigabit NIC built on Intel’s I350 chip covers both ports in one slot.
- Use virtual bridges if you don’t have a spare NIC, or you’d like to test OPNsense first. The VM gets virtual network cards on Linux bridges, so OPNsense can route your house if the host has a second port, or a test network of VMs if it has only one, and you can move to passthrough later.
When I first wrote this tutorial in 2022, I installed OPNsense on a Proxmox development server and passed a NIC’s ports through to the VM, one for WAN and one for LAN. I did the same for my pfSense tutorials. If OPNsense is going to be your main router, passthrough is the one to pick, since the firewall owns its ports outright.
Download the OPNsense ISO Straight Into Proxmox
You don’t have to download and extract the ISO on your computer anymore. Since Proxmox VE 8.3, Download from URL can fetch the compressed .iso.bz2 file, check its SHA-256 and decompress it in one task. Use the DVD image, which OPNsense’s docs name for a virtual machine.
1. In Proxmox, select your node, then the local storage, and finally, ISO Images.
2. Select Download from URL, paste the URL of the DVD image below into URL, then select Query URL. Proxmox fills in the File name (OPNsense-26.7-dvd-amd64.iso) and shows a file size of 471.40 MiB.
https://pkg.opnsense.org/releases/26.7/OPNsense-26.7-dvd-amd64.iso.bz2
3. Tick Advanced (Decompression algorithm already reads BZIP2), set Hash algorithm to SHA-256, and paste the hash of the .iso.bz2 file into Checksum. It’s in OPNsense-26.7-checksums-amd64.sha256 in the same release folder.

4. Select Download. The task log shows “calculating checksum…OK, checksum verified”, then the decompression, then TASK OK, and the ISO (about 2 GB once it’s unpacked) appears under ISO Images.

The official server ran at about 250 KB/s when this was checked in November 2026. If it crawls, swap the start of the URL for an OPNsense mirror like https://mirror.wdc1.us.leaseweb.net/opnsense/releases/26.7/, which delivered the same verified file much faster.
Create the OPNsense VM in Proxmox
Create the VM with OS type Other, 2 cores, 4096 MiB and a 32 GiB disk, and the wizard is the same for both paths until the Network tab. Leave Start after created unticked at the end, because there’s still hardware to add.
1. Select Create VM in the top right corner. On General, give the VM a Name (opnsense, for example) and note the VM ID Proxmox picked, which is the next free number.

2. On OS, keep Use CD/DVD disc image file (iso), choose the local storage and OPNsense-26.7-dvd-amd64.iso as the ISO image, then set the Guest OS Type to Other. There is no FreeBSD entry (OPNsense 26.7 is built on FreeBSD 15.1), so Other is the right choice.

3. On System, the defaults are fine: i440fx, SeaBIOS and the VirtIO SCSI single controller.

4. On Disks, pick the Storage for the VM. With OS type Other, Proxmox defaults to IDE 0 and 32 GiB, which is plenty against OPNsense’s 8 GB minimum (its hardware docs call 40 GB the reasonable size if you’d like more room).

5. On CPU, set Cores to 2. The default is one, and OPNsense’s minimum is a dual-core CPU.

6. On Memory, set Memory (MiB) to 4096. The default of 2048 is under OPNsense’s 3 GB minimum, and its docs say an install that stops with “File copy failed” is most likely short on RAM.

7. On Network, what you pick depends on the path. For passthrough, tick No network device. For virtual bridges, keep Bridge on vmbr0, change Model from the default Intel E1000 to VirtIO (paravirtualized) (more on that in Option 2), and tick Advanced and Disconnect so OPNsense’s LAN DHCP server stays off your network for now.

8. On Confirm, check the summary and select Finish.

Option 1: Pass Through a Physical NIC
With passthrough, OPNsense talks to the card directly and the host stops using it, so never pass through the port vmbr0 uses, or you’ll lose the Proxmox web UI. Install the card, but leave its ports unplugged until WAN and LAN are assigned.
Turn On IOMMU and Load the VFIO Modules
Enable IOMMU in the host’s BIOS or UEFI first (the setting is usually called IOMMU or VT-d). AMD CPUs have IOMMU on by default, and Intel CPUs do too on kernel 6.8 and newer. Proxmox VE 9.2 ships kernel 7.0, so the old intel_iommu=on GRUB edit is not needed.
1. Open the node’s Shell and add the three VFIO modules to a file under /etc/modules-load.d/.
cat <<'EOF' > /etc/modules-load.d/vfio.conf
vfio
vfio_iommu_type1
vfio_pci
EOF
2. Update the initramfs, then reboot the host.
update-initramfs -u -k all
3. After the reboot, lsmod should list the three vfio modules, and dmesg should say IOMMU, Directed I/O or Interrupt Remapping is enabled.
lsmod | grep vfio
dmesg | grep -e DMAR -e IOMMU -e AMD-Vi
4. Check the card’s IOMMU group, replacing <node> with your node’s name. Each port should be in its own group or share one only with the card’s other functions, its root port or a PCIe bridge, and moving the card to a different slot can help if it shares a group with something else.
pvesh get /nodes/<node>/hardware/pci --pci-class-blacklist ""
Add the NIC Ports to the VM
1. Select the OPNsense VM, then Hardware, then Add, and finally, PCI Device.
2. In Add: PCI Device, choose Raw Device and pick one port from the Device list. A multi-port card usually lists each port as its own function (0000:03:00.0 and 0000:03:00.1, for example), so add one port with Add and repeat for the second, or tick All Functions if you’d like to pass the whole card as one entry.

Added separately, each port shows on the Hardware tab as its own PCI device (hostpci0, hostpci1), and that works on the default i440fx machine type. Once the ports are added, skip ahead to the installer.
Option 2: Use Virtual Bridges Without a Spare NIC
Proxmox’s installer already created one bridge, vmbr0, on the network port you picked during the install, and the VM’s first network device sits on it. A router needs a second network for its other side, so you’ll make a second bridge and give the VM a second network device on it.
If the host has a second physical port, make it the bridge’s port, so vmbr1 becomes WAN and vmbr0 your LAN, and OPNsense replaces your current router. If it only has one, leave Bridge ports empty. vmbr0, your home network, has to be WAN, and vmbr1 is a test LAN that only VMs on this host can join, so you’ll need a VM with a browser to reach the web GUI.
Create a Second Linux Bridge
1. Select your node, then System, then Network, and finally, Create and Linux Bridge.
2. In Create: Linux Bridge, keep the Name it fills in (vmbr1) and leave IPv4/CIDR and Gateway (IPv4) empty. Set Bridge ports to the second physical port (a wired port not listed under vmbr0’s Ports/Slaves, named like nic0 or enp2s0) or leave it empty for a VM-only network, tick VLAN aware if you plan to configure VLANs in Proxmox for OPNsense later, then select Create.

3. Select Apply Configuration, which applies the change without a reboot.
Add the Second Network Device
Use the same model for both network devices. Proxmox’s VM docs recommend VirtIO for performance, with up to three times the throughput of an emulated E1000 card in iperf. Inside OPNsense, VirtIO shows up as vtnet0 and vtnet1, E1000 as em0 and em1.
1. Select the OPNsense VM, then Hardware, then Add, and finally, Network Device.
2. Set Bridge to vmbr1 and Model to the same model as net0, tick Advanced and Disconnect as before, then select Add.
The OPNsense Installer Password and Default Login
The OPNsense installer password is opnsense, and the user is installer. Once OPNsense is installed, the default login is root / opnsense until you set your own. The DVD boots into a live system, and nothing is written to the virtual disk until you confirm Last Chance!.
If you imported a configuration, both logins use that configuration’s root password instead.
Install OPNsense to the Virtual Disk
1. Start the VM, then select Console. Let the boot menu autoboot after 3 seconds, or press Enter on Boot Multi user.

2. At the login prompt, log in as installer with the password opnsense.

3. Continue with the default keymap, then choose Install (ZFS) and keep the default stripe on Select Virtual Device type for a single virtual disk.

4. Tick ada0, the QEMU HARDDISK, with Space and select OK. Last Chance! has NO preselected, so select YES to erase the disk.

5. Wait for Installation Progress to finish. It can sit at 90 % for a couple of minutes.
6. On Final Configuration, select Root Password, set a new password and confirm it, then select Complete Install.

7. On Installation Complete, select Halt now, as the screen itself warns that the system may boot back into the installation media.

The password you set at Root Password is root’s password in the console and the web GUI. If you skip that step, change root’s password in the GUI right away. And if the installer login doesn’t work at all, log in as root, choose 8) Shell and run opnsense-installer.
Eject the ISO and Boot From the Disk
1. Select the VM, then Hardware, select the CD/DVD Drive, and finally, Edit. Choose Do not use any media and select OK.
2. Start the VM again. It boots from the virtual disk and stops at a login prompt, so log in as root with the password you set to reach the console menu.
Assign Interfaces and Open the Web GUI
With two network devices, OPNsense assigns the first as LAN at 192.168.1.1/24 and the second as WAN on DHCP.

1. If WAN and LAN are the wrong way round, choose 1) Assign interfaces, answer n to LAGGs and VLANs, type the WAN device, then the LAN one, press Enter at the optional interface prompt, and answer y to proceed. On the passthrough path the order follows the card. On the bridge path, net0 on vmbr0 comes up as LAN, so swap them on a one-port host.
2. If OPNsense replaces your router, or 192.168.1.1 clashes with a network you already have, choose 2) Set interface IP address, pick LAN, answer N to “Configure IPv4 address LAN interface via DHCP?”, enter the new address and subnet (your old router’s, if it’s replaced), and press Enter at the gateway prompt. Later, answer y to “Do you want to enable the DHCP server on LAN?” and give it a range in the new subnet, because the old one is deleted. The defaults are fine for the other prompts.
3. If OPNsense replaces your router, unplug that router and move the modem to WAN. Then untick Disconnect on both network devices (select each under Hardware, then Edit and Advanced), or on passthrough, plug your switch into LAN. From a computer on the LAN side (a VM on vmbr1 on a one-port host), open https://192.168.1.1 (or your new address), accept the self-signed certificate warning, and log in as root with the password you set in the installer.
4. The first login opens the setup wizard. Run it, or click the logo in the upper left corner to bypass it.
Turn Off Hardware Offloading
OPNsense’s docs say to disable all hardware offloading on a virtual machine, under Interfaces > Settings. On 26.7.8_2, the three General boxes, Disable hardware checksum offload, Disable hardware TCP segmentation offload and Disable hardware large receive offload, are ticked by default, and VLAN Hardware Filtering is on Leave default. Open the page, confirm all three are ticked, and select Apply if you changed anything.

Then update it from System > Firmware > Updates, where the 26.7 image goes to 26.7.8. For the QEMU guest agent, install os-qemu-guest-agent from System > Firmware > Plugins (select Click to view the community plugins. first), then turn on QEMU Guest Agent in the VM’s Options and shut the VM down and start it again.
From there, the rest of the OPNsense Proxmox setup is regular OPNsense work, like how to set up a VLAN in OPNsense or port forwarding in OPNsense. If you decide the firewall belongs on its own box after all, the best OPNsense hardware guide covers that route. Firewall software and its security defaults change from release to release, so treat this as how OPNsense 26.7 behaved on Proxmox VE 9.2 in November 2026, and nothing here is a guarantee that your network is secure.
