📑 Contents ▾
- 01 FreeBSD or Linux: the difference that decides the hardware
- 02 The comparison in one table
- 03 Filtering, VPN and intrusion detection
- 04 Day-to-day administration
- 05 A pfSense in production: the publisher’s setup
- 06 Hardware for each
- 07 Who should pick what
- 08 Updates: the discipline a firewall demands
- 09 Moving from pfSense to OPNsense
- Our picks
If you have a mini-PC or an old x86 PC with at least two network ports and you want a real firewall (VLANs, VPN, intrusion detection), install pfSense CE or OPNsense: both are built on FreeBSD and the pf filter. OPNsense has the more modern interface; pfSense has the largest body of documentation and forum answers. If your hardware is a consumer Wi-Fi router or a small ARM board, only OpenWrt, a Linux distribution, will install on it. On the homelab of Selfhostr’s publisher, pfSense is the production firewall, running in a virtual machine: the setup is described further down.
FreeBSD or Linux: the difference that decides the hardware
pfSense and OPNsense, two branches of the same family
pfSense and OPNsense share the same foundation: FreeBSD and its in-kernel firewall, pf (Packet Filter). OPNsense was born in 2015 as a fork of pfSense. Both are managed through a web interface and store their whole configuration in one XML file, config.xml, which is easy to back up.
- pfSense is the historical reference. Its development is conservative: only what is necessary gets changed. It comes in two editions: pfSense CE, free and open source, and pfSense Plus, which Netgate ships on its own appliances among others.
- OPNsense reorganized its code to be more modular, with a stricter object-oriented structure, which makes plugin development and security audits easier.
FreeBSD offers Jails to isolate services, but neither pfSense nor OPNsense uses them for their built-in services (captive portal, DNS server…): those run directly on the firewall system. Neither system is meant to host your applications either: Home Assistant, Jellyfin or a file server belong on other machines, behind the firewall.
OpenWrt, a Linux built for embedded hardware
OpenWrt is a Linux distribution slimmed down for embedded hardware. Its filtering engine is nftables, through fw4, since release 22.03 (iptables before that). Packages are installed with apk since OpenWrt 25.12 (opkg before), built for each architecture: ARM, MIPS, x86.
The gap in resources is huge. OpenWrt needs at the very least 64 MB of RAM and 8 MB of flash, and the project recommends at least 128 MB of RAM and 16 MB of flash. pfSense and OPNsense target x86-64 PCs: plan for 4 GB of RAM to be comfortable and 32 GB of storage, preferably an SSD, which copes better with constant log writes.
The direct consequence: pfSense and OPNsense do not install on a consumer Wi-Fi router. To reflash that kind of device, OpenWrt is the only option of the three.
The comparison in one table
| Criterion | pfSense CE | OPNsense | OpenWrt |
|---|---|---|---|
| Base | FreeBSD | FreeBSD | Linux |
| Target hardware | x86-64 PCs and mini-PCs | x86-64 PCs and mini-PCs | ARM/MIPS routers, Raspberry Pi, x86 |
| Filtering | pf (kernel) | pf (kernel) | nftables via fw4 (kernel) |
| Interface | Web, dense and complete | Web, more modern | LuCI, lightweight; frequent command line |
| VPN | WireGuard, OpenVPN, IPsec | WireGuard, OpenVPN, IPsec | WireGuard, OpenVPN, IPsec |
| IDS/IPS | Snort or Suricata (packages) | Suricata built in | Snort or Suricata (packages, heavy on ARM) |
| Release cadence | Infrequent and irregular (CE) | 2 major a year + frequent minor | Stable branch + snapshots |
| RAM | 4 GB to be comfortable | 4 GB to be comfortable | 64 MB minimum, 128 MB recommended |
Filtering, VPN and intrusion detection
The filtering engine
On pfSense and OPNsense, pf lives in the kernel and rules are managed in the web interface. Netgate, the company behind pfSense, rates its Netgate 4200 appliance (4-core Intel Atom C1110) at 8.75 Gbps for routing, 8.61 Gbps with the firewall enabled and 3.20 Gbps for IPsec VPN (AES-GCM-128 with AES-NI). These are the manufacturer’s figures, not Selfhostr measurements, but they give an idea of what pf can handle on a small, recent x86 processor.
On OpenWrt, the move to nftables modernized filtering, with a more concise syntax and better performance than the old iptables. On a low-end ARM router, however, a complex rule set can become the bottleneck.
VPN
- WireGuard has become the default choice for its simplicity and speed. pfSense and OPNsense both support it, with its settings in the web interface. On OpenWrt it is supported in the kernel and configured in LuCI or with
ucion the command line; managing many mobile clients there is less comfortable than with a dedicated interface. - OpenVPN is still useful for the widest compatibility (Android, iOS, Windows). It is solid on pfSense and OPNsense; on OpenWrt, preparing the clients’
.ovpnfiles and certificates is more of a manual job. - IPsec goes through strongSwan on pfSense and OPNsense, a stable base for site-to-site links with Cisco or Juniper hardware. OpenWrt offers strongSwan or Libreswan, less integrated into its graphical interface.
To choose between these protocols, our WireGuard, OpenVPN and Tailscale comparison covers the trade-offs.
IDS/IPS: Suricata and Snort
- OPNsense integrates Suricata as its IDS/IPS engine (Snort is not offered). Suricata is multi-threaded and inspects application protocols (HTTP, TLS metadata) without decrypting HTTPS traffic.
- pfSense offers Snort, historically, and Suricata, added later, as packages. With many rules on weak hardware, throughput drops.
- OpenWrt has
snortandsuricatapackages, but on an ARM router inspection quickly costs more than the processor can give: keep that use for OpenWrt on x86.
Day-to-day administration
pfSense CE has an aging interface, dense and sometimes confusing, but very complete. Its strength is its documentation: almost every question already has an answer on the forums. The learning curve is steep.
OPNsense has a clearer, responsive interface with a logical layout. Security fixes arrive quickly: two major releases a year and frequent minor updates. On the other hand, there are fewer community tricks than for pfSense, and some advanced features come through plugins.
OpenWrt is managed with LuCI, a lightweight, modular web interface. As soon as the configuration gets complex (elaborate firewall, VPN), you often end up in SSH editing configuration files such as /etc/config/firewall. The documentation is technical and scattered.
On pfSense, SSH gives you a full root shell, but a change made by hand outside the interface can be overwritten by the web interface’s configuration.
A pfSense in production: the publisher’s setup
pfSense runs in production on the homelab of Selfhostr’s publisher: a virtual machine on a rack server running VMware ESXi, which acts as firewall and router between the ISP’s router (the provider’s “box”) and the server network.
So a firewall does not need a box of its own: a virtual machine on a hypervisor that keeps the ISP side and the server side apart does the job. This architecture has a trade-off you should accept knowingly: the firewall depends on the host. When the server reboots or goes down for maintenance, the whole network behind pfSense is cut off. A dedicated box avoids that dependency, at the cost of one more machine. To choose the hypervisor, see our Proxmox VE, ESXi and XCP-ng comparison; to segment the network, our tutorial on configuring VLANs on a managed switch.
A VPS is a different case: the point is limited to testing or virtual routing. Network performance there depends on the hypervisor and the provider’s bandwidth, and the added latency can get in the way of real-time uses (VoIP, online gaming).
Hardware for each
pfSense or OPNsense: an x86 machine with several ports
These systems target the x86-64 architecture and benefit from processors with AES-NI encryption instructions. A reasonable baseline:
- CPU: an Intel Celeron J4125 or N5105 (4 cores, AES-NI) to start with; an AMD Ryzen 3000 or 5000 for high throughput.
- RAM: 4 GB; plan for 8 GB if you enable Suricata.
- Storage: 32 GB on a SATA or NVMe SSD.
- Network: at least two ports (WAN and LAN), 1 Gbps or faster. For 10 Gbps you need a PCIe card such as the Intel X520 or X540.
Three ways to get equipped:
- A multi-port router mini-PC. This is the most common form factor: a small x86 box with four ports or more. The 4-port pfSense mini-PCs sold online vary a lot from one listing to the next: check the network chip and the processor before buying. Among the models whose spec sheet we collected, the Protectli Vault VP2420 is designed to run either pfSense or OPNsense: four Intel I226-V 2.5 GbE ports, a Celeron J6412 (4 cores, AES-NI), up to 32 GB of DDR4 and a fanless case drawing 24 W at most according to Protectli.
- A box that ships with pfSense. The Netgate 4200 is sold by the company behind pfSense, with pfSense Plus: 4-core Atom C1110, 4 GB of DDR5, a 128 GB NVMe SSD, a 240 × 180 × 60 mm case, and the throughput figures quoted above.
- A recycled PC plus a network card. An old desktop PC makes a good firewall once you add ports. Pick an Intel network card: an M.2 card with the Intel I226-V chip (2.5 GbE), listed by a retailer, is advertised as compatible with pfSense, OPNsense and FreeBSD; for a desktop PC, take the PCIe form factor and check the chip on the listing. The Intel X520-DA2 adds two 10 GbE SFP+ ports (Intel 82599 controller).
Model-by-model detail, port by port, is in our pfSense/OPNsense router mini-PC guide, and step-by-step installation in our pfSense and OPNsense tutorials.
OpenWrt: from ARM routers to x86
OpenWrt runs on a very wide range of hardware, from the Raspberry Pi (official images, bcm27xx target) to routers built on MediaTek Filogic chips. A reasonable baseline:
- CPU: Qualcomm IPQ40xx (Wi-Fi 5 routers) or MediaTek MT7622 (2 A53 cores, found in some Wi-Fi 6 routers).
- RAM: 256 to 512 MB.
- Flash: 16 to 128 MB.
- Network: one or two gigabit ports depending on the model.
Before buying an OpenWrt-compatible router, check that the exact model, hardware revision included, appears in the supported hardware list on the project’s website. On an MT7622 router, routed throughput depends on hardware offloading and active rules, and IDS is unrealistic. On a Raspberry Pi 4 with a 2.5 Gbps USB network adapter, routed throughput remains limited by the built-in Ethernet port, which is gigabit, and by the USB bus.
Who should pick what
- You protect self-hosted services with a mini-PC (Home Assistant, Jellyfin, a file server, on other machines): OPNsense or pfSense. OPNsense for its interface and frequent updates, pfSense for its documentation.
- You have a Wi-Fi 6 router (Asus, TP-Link, Netgear) and want to replace its firmware: OpenWrt, the only one of the three that installs on it. You give up advanced centralized management and gain full control over Wi-Fi and traffic.
- You run a small business network (more than 50 devices, several VLANs, RADIUS authentication, 1 Gbps or faster Internet access): OPNsense, or pfSense Plus. OPNsense’s modularity lets you add specific features (advanced captive portal, NetFlow analysis) without weighing the system down, and the frequency of patches matters for compliance.
- You want to script your network and compile your own packages: OpenWrt on x86, which remains a standard Linux system (Docker, Nginx and the usual Linux tools install on it), or pfSense with its root shell, keeping in mind that the web interface can overwrite manual changes.
Updates: the discipline a firewall demands
A firewall that is not updated is an open door to the whole network behind it.
- pfSense: updates are carefully tested, but a major version jump (from 2.5 to 2.6, for example) can break an old configuration or custom scripts. Back up the XML file before every update.
- OPNsense: the interface clearly shows the available updates, for the kernel as well as for packages. Its configuration also lives in
config.xml: back it up before applying a major release. - OpenWrt: two branches. The stable branch is reliable but may lack recent drivers; the snapshot branch brings the latest features and can be unstable. Unless you are an expert, stay on the stable branch.
Whatever the system, protect the admin interface with a strong password and enable two-factor authentication when it is available.
Moving from pfSense to OPNsense
Can you import a pfSense backup into OPNsense? Not officially. OPNsense has no migration tool for pfSense, and importing a pfSense XML backup is not supported: at best the result is partial. Both systems rely on pf, but their configuration files use different formats. There is no direct upgrade from one to the other either: their package repositories are separate.
The method that works:
- Back up the pfSense configuration (Diagnostics > Backup & Restore) to keep as a reference.
- Install OPNsense cleanly, on the same hardware or on a new machine.
- Rebuild the configuration section by section from that reference. The import in System > Configuration > Backups is meant for OPNsense backups, not pfSense ones.
- Check Firewall > Rules: the objects (addresses, groups) and above all the target interfaces. A rule meant for the LAN that ends up on the WAN is the mistake not to let through.
What about pfSense packages? Most basic functions are native in OPNsense, but some very specific pfSense packages (monitoring scripts, proprietary integrations) have no direct equivalent. If you depend on them, check the official list of OPNsense plugins before migrating.
Key facts
Our picks
Affiliate links · same price for you4x 2.5 GbE mini-PC
- The form factor pfSense and OPNsense are built for
- Amazon search: check the network chip and CPU of each listing
Amazon · price and availability on the listing
Protectli Vault VP2420
- 4x Intel I226-V 2.5 GbE
- Celeron J6412, 4 cores, AES-NI
- 24 W maximum (Protectli spec sheet)
Amazon · price and availability on the listing
Netgate 4200
- Intel Atom C1110, 4 cores
- 4 GB DDR5, 128 GB NVMe SSD
- 8.61 Gbps with firewall enabled (Netgate figure)
Amazon · price and availability on the listing
Intel i226 NIC
- Intel I226-V (2.5 GbE) or I350 (1 GbE) chip, depending on the listing
- PCIe form factor for a desktop PC: check the listing
Amazon · price and availability on the listing
Intel X520-DA2
- 2 SFP+ 10 GbE ports
- Intel 82599 controller
Amazon · price and availability on the listing
OpenWrt-compatible router
- Look up the exact model and hardware revision in OpenWrt's hardware list
Amazon · price and availability on the listing
See all our recommended gear in the shop.