Tutorials 14 min read

pfSense 2026: Installation on a Mini PC, What's the Best Choice?

pfSense CE on a mini-PC in 2026: why the Minisforum MS-A2 fits and the single-port NUC 14 Pro doesn't, which network ports to use, and installing with the Netgate Installer.

S By Selfhostr · no sponsored content
pfSense 2026: Installation on a Mini PC, What's the Best Choice?
This article may contain affiliate links (no extra cost to you, it funds the site). As an Amazon Associate, Selfhostr earns from qualifying purchases. See the disclosure.

👍 What we like

  • pfSense CE is free, with no subscription
  • The installer handles DHCP, static IP, PPPoE and VLANs on the WAN
  • ZFS by default, with rollback through boot environments
  • The MS-A2 offers 10 GbE and enough ports for a DMZ or guest network

👎 What to watch

  • Internet access is required during installation
  • The NUC 14 Pro has only one Ethernet port
  • The MS-A2 mixes Intel and Realtek chips, and its CPU is oversized for a router
  • No automatic updates, and the disk is fully wiped
📑 Contents ▾

For a pfSense router, what matters is how many network ports you get and how good they are, well before CPU power. Of the two mini-PCs covered here, the Minisforum MS-A2 is the only one that works as is: it has four ports, including two 10 GbE SFP+ ports. The ASUS NUC 14 Pro has a single Ethernet port. It only works as a router with a managed switch and VLANs, so it’s best left to people who already own that switch or who mainly want it as a server. Either way, pfSense CE now installs through the Netgate Installer, which downloads the system during installation. That means the WAN needs Internet access from the start, which often catches people used to the old ISOs off guard.

The specifications quoted here come from ASUS’s and Minisforum’s pages and Netgate’s documentation, checked in November 2026. Selfhostr has not installed pfSense on these two machines: the steps below follow Netgate’s official procedure.

What pfSense actually needs

According to Netgate’s documentation, the official minimum is modest: an x86-64 CPU, 1 GB of RAM and an 8 GB disk. Netgate does point out that this minimum won’t suit every use. High-throughput encrypted VPN, large rule sets, and packages like Suricata or pfBlockerNG need more memory and CPU. For home use, almost any recent mini-PC goes far beyond these needs.

What makes the difference lies elsewhere:

  • At least two interfaces, one for the WAN (ISP box or ONT) and one for the LAN. A third one gives you a guest network or DMZ without VLANs.
  • Controllers that FreeBSD handles well. pfSense runs on FreeBSD, not Linux. A port that works perfectly on Windows or Ubuntu may behave differently here. In the pfSense community, Intel chips remain the default choice. Realtek chips have a reputation for being less consistent on FreeBSD, even though recent releases have improved things.
  • No USB-to-Ethernet adapter for the WAN or the main LAN. It can work in a pinch, but it’s not a reliable foundation for a firewall that runs around the clock.
  • A small SSD is enough. A few tens of GB cover the system, logs and packages. A 1 TB SSD does nothing for a machine dedicated to pfSense.

Minisforum MS-A2: four ports, but not all the same

The Minisforum product page lists two 10 GbE SFP+ ports on an Intel X710 controller and two 2.5 GbE RJ45 ports. The two RJ45 ports don’t use the same chip: published listings and reviews show an Intel I226-V for one and a Realtek RTL8125 for the other. In practice:

  • The X710, I226 and RTL8125 use three different FreeBSD drivers (ixl, igc and re). On the console, the interfaces will have different names (for example ixl0, igc0, re0). That’s not a problem, but you need to know which is which before you pick the WAN.
  • For a simple RJ45 setup, put the WAN and LAN on the Intel I226-V port and an SFP+ port (with an RJ45 module or a DAC cable to the switch). The Realtek port can stay in reserve or carry a secondary network.
  • The SFP+ ports only work with a module or a DAC cable. Before buying one, check that it’s compatible with an Intel X710 controller.
  • The CPU is a workstation-class chip (a Ryzen 9 HX-series part, depending on the version). That’s far more than you need to route a home connection. The MS-A2 only really makes sense if you want 10 GbE to your switch or NAS, or if you plan to run pfSense as a virtual machine next to other services (see below).

Chip models can change between production runs. Once pfSense is installed, the pciconf -lv command gives you the exact list (see step 6).

ASUS NUC 14 Pro: one port means a different architecture

According to ASUS’s spec sheet, the NUC 14 Pro has a single 2.5 GbE RJ45 port (Intel I226-V or I226-LM), plus two Thunderbolt 4 ports and several USB ports. The network chip is a very good fit for FreeBSD, but a single port can’t physically separate the WAN from the LAN. You have two options:

  1. Router-on-a-stick. The single cable goes to a managed 802.1Q switch. The ISP box plugs into a switch port set to the “WAN” VLAN, and your devices sit on the “LAN” VLAN. pfSense then sees two VLAN interfaces on the same card. The installer can set a VLAN for both the WAN and the LAN (“VLAN Settings”). All Internet traffic crosses the same link twice, which is still acceptable on a 2.5 GbE port with a home connection. A switch misconfiguration, however, can expose the LAN on the ISP box’s side, so this setup is for people who are comfortable with VLANs. Our guide to configuring VLANs on a managed switch covers that part.
  2. A second interface over Thunderbolt or USB. Before buying an adapter, check that FreeBSD recognizes it. Support for these adapters is much narrower there than on Linux. For 24/7 use, this is the least reliable option.

If you don’t already own a managed switch, a mini-PC built from the start with several network ports will save you these workarounds. Our comparison of router mini-PCs for pfSense and OPNsense reviews those models.

Bare metal or a VM

Installing directly on the mini-PC is the simplest option. pfSense takes over the whole disk, with no dual boot and no other system alongside it. On a machine as powerful as the MS-A2, many people prefer to install Proxmox VE first, then pfSense in a VM with physical ports dedicated to the WAN and LAN. The rest of the machine stays free for other services, such as Home Assistant. For this case, Netgate provides an ISO image of the same installer. The trade-off: when the hypervisor reboots or fails, the whole house loses Internet.

If you’re still weighing the software itself, our pfSense, OPNsense or OpenWrt comparison covers the differences. For OPNsense, which still installs from a full offline image, follow our tutorial on installing OPNsense on a mini-PC instead.

Before you start

  • A dedicated SSD: everything on it will be erased.
  • A USB flash drive: its contents will be erased too.
  • A monitor and keyboard connected to the mini-PC.
  • Internet access on the WAN port during installation. The Netgate Installer image doesn’t contain pfSense: it downloads it.
  • Your ISP’s details if you aren’t behind a DHCP box: PPPoE credentials, or the VLAN number your provider requires.
  • A computer to plug into the LAN for the web wizard.

Step-by-step installation

Step 1: Download the Netgate Installer and verify its checksum

There’s no longer a direct ISO link. You get the Netgate Installer from the Netgate Store: create an account, add the image to your cart and check out a free order, which exists only to deliver the file. Choose AMD64 Memstick USB. It’s the image meant for most third-party hardware, and it supports both VGA and serial consoles. The AMD64 ISO is for virtual machines and IPMI installs.

Netgate doesn’t ship a .sha256 file alongside the image. The hashes are published on a separate page, Netgate’s checksum list. Compute the hash on the compressed file, before you decompress it:

cd ~/Téléchargements
sha256sum netgate-installer-amd64.img.gz   # adaptez au nom exact du fichier

(The cd path and the comment are copied from the French version: use your own downloads folder and the exact file name.)

Check: the hash shown must match the one Netgate publishes for that file. On macOS, Safari may decompress the download automatically, which makes verification impossible. Turn that setting off or use another browser.

Step 2: Write the image to the USB drive

balenaEtcher (Windows, macOS, Linux) reads the .img.gz file directly. Choose “Flash from file”, then the drive, then “Flash!”. On Linux, dd works too.

⚠️ dd overwrites the target device without asking for confirmation. Identify the USB drive with certainty first:

lsblk -o NAME,SIZE,MODEL,TRAN,MOUNTPOINTS
# Repérez la ligne dont TRAN = usb et dont la taille correspond à votre clé (ex. sdb).
# Si la clé est montée, démontez ses partitions :
sudo umount /dev/sdX?* 2>/dev/null

The comments say: find the line where TRAN = usb and the size matches your drive (e.g. sdb), and unmount its partitions if the drive is mounted. Replace sdX with the name you found, never with your system disk:

gunzip -c netgate-installer-amd64.img.gz | sudo dd of=/dev/sdX bs=4M status=progress conv=fsync
sync

Check: lsblk /dev/sdX shows new partitions. If your system offers to “format” the drive, decline: it simply can’t read these FreeBSD partitions.

Step 3: Connect the WAN and boot from the USB drive

  1. Plug the cable from the ISP box or ONT into the port you’re reserving for the WAN. On the MS-A2, preferably use an Intel port. On the NUC 14 Pro, plug in the cable that goes to the switch.
  2. Insert the drive, power on and open the UEFI boot menu.
  3. If the drive doesn’t show up, make sure USB boot is allowed in the UEFI and try disabling Secure Boot.

Check: the License screen appears. Press Enter to Accept.

Step 4: Configure networking in the installer

The official installer walkthrough starts at the Welcome Menu. Choose Install. If needed, Advanced Options lets you set the swap size or enable Low Capacity System for small disks.

  1. Select WAN Interface: the list shows each interface’s MAC address and link state. Only the one with a cable plugged in shows as active, which helps you find the right port. On the MS-A2, this is also where the igc, re and ixl names reveal the chip behind each port.
  2. Interface Mode: DHCP (Client) behind an ISP box, STATIC (IP/CIDR, gateway, DNS) or PPPoE (username, password, service name). VLAN Settings is for when your ISP requires a VLAN, or for the WAN VLAN of a single-port setup.
  3. Select LAN Interface: in static mode, the LAN gets 192.168.1.1/24 by default, with a DHCP server handing out addresses 192.168.1.100 to 192.168.1.150. Many ISP boxes already use 192.168.1.0/24. If yours does, pick another subnet (for example 192.168.10.1/24), or routing won’t work properly.
  4. Confirm Network Configuration → Continue.

Check: the installer contacts Netgate’s servers. The message “Cannot verify the eligibility of this system” means it couldn’t reach them. Go back and check the WAN interface, its mode and any VLAN.

Step 5: Choose CE and the disk, then install

  1. A third-party mini-PC isn’t eligible for pfSense Plus without a subscription. Choose Install CE.
  2. File System: keep ZFS (the default, recommended by Netgate). UFS is still available. Partition Scheme: GPT by default, MBR only for old hardware.
  3. Select the target disk. On FreeBSD, disks aren’t named sdX: an NVMe SSD shows up as nda0 (or nvd0), a SATA SSD as ada0, a USB drive as da0. Don’t overwrite da0: it’s probably your installation drive. Go by the size and model shown.
  4. Confirm the warning: everything on the disk will be destroyed.
  5. Pick the version, usually Current Stable Version, then OK. The installer downloads and writes the files.
  6. Choose reboot and remove the USB drive while the hardware is initializing, before the machine boots from the internal disk. Otherwise it may launch the installer again.

Check: the pfSense console menu appears, with the WAN and LAN addresses and numbered options (1 Assign Interfaces, 2 Set interface(s) IP address, 8 Shell…).

Step 6: Check the interfaces and disk from the console

If the WAN and LAN are swapped, use option 1 to reassign them and option 2 to change the LAN address. Option 8 opens a FreeBSD shell. The following commands run in that shell, on pfSense, not on your PC:

ifconfig -l                       # liste des interfaces (ex. igc0 re0 ixl0 ixl1)
pciconf -lv | grep -B3 -i network # contrôleurs réseau réellement présents
geom disk list | grep -E "Geom name|Mediasize|descr"   # disques (nda0, ada0…)
zpool status                      # état du pool ZFS (si ZFS choisi)
ping -c 3 9.9.9.9                 # le pare-feu sort-il sur Internet ?

In order, these commands list the interfaces, show the network controllers that are actually present, list the disks, show the ZFS pool status (if you chose ZFS), and test whether the firewall can reach the Internet.

Check: zpool status shows state: ONLINE and ping gets replies. Type exit to return to the menu.

Step 7: Run the web wizard

Connect a computer to the LAN port, or to the switch’s LAN VLAN. It should get an address via DHCP. Open https://192.168.1.1 (or the LAN address you chose) and accept the self-signed certificate. Log in with admin / pfsense. The wizard (System > Setup Wizard) asks for the hostname and DNS servers, time server and time zone, WAN and LAN settings, then a new admin password, before finishing with Reload.

From a Linux machine on the LAN:

ip -4 addr show                               # le poste a-t-il une adresse dans le LAN pfSense ?
ping -c 3 192.168.1.1                         # pfSense répond-il ?
curl -skI https://192.168.1.1 | head -n 1     # l'interface web répond-elle ?
curl -sI https://www.pfsense.org | head -n 1  # Internet passe-t-il par pfSense ?

These check, in order, that the machine has an address on the pfSense LAN, that pfSense replies, that the web interface responds, and that Internet traffic goes through pfSense.

Check: every command gets a response. Status > Interfaces shows the WAN and LAN as “up” with their addresses. Status > DHCP Leases lists your machines.

Securing and maintaining the firewall

  • Don’t open the web interface or SSH on the WAN side. By default, pfSense blocks all inbound traffic on the WAN. For remote administration, use a VPN (WireGuard or OpenVPN) running on pfSense.
  • SSH is disabled by default. If you turn it on, use key-based authentication, on the LAN only.
  • If several people manage the firewall, create named accounts in System > User Manager.
  • To replace the self-signed certificate, use System > Certificates, then System > Advanced > Admin Access.
  • Updates aren’t automatic. Run them from System > Update or from the update option in the console menu. Export the configuration first in Diagnostics > Backup & Restore. With ZFS, a boot environment also lets you roll back.

When things go wrong

  1. The installer can’t reach Netgate. The cable is often in the wrong port. Otherwise, the ISP expects PPPoE or a VLAN while you left DHCP selected. Go back to the network screen and check the link state of the chosen port.
  2. https://192.168.1.1 doesn’t respond. The machine isn’t on the right port or VLAN, or the WAN and LAN were swapped. The console shows each interface’s address: fix it with options 1 and 2.
  3. pfSense has a WAN address, but the LAN has no Internet. The LAN uses the same subnet as the ISP box, or DNS isn’t responding. Change the LAN subnet (option 2) and test with Diagnostics > DNS Lookup.
  4. Throughput is erratic on one port. On the MS-A2, check that it isn’t the Realtek port (re0), and move the WAN or LAN to an Intel port.
  5. The machine reboots into the installer. The drive is still plugged in or comes before the SSD in the UEFI. Remove it and put the SSD first in the boot order.

Frequently asked questions

Can you install pfSense CE without Internet access?

No, not with the Netgate Installer, which downloads the packages during installation. If your connection needs special settings, have the details ready beforehand: the installer handles PPPoE, a static address and a VLAN on the WAN.

Do you need a lot of RAM or a big SSD?

Not for a home router. The official minimum is 1 GB of RAM and an 8 GB disk. Plan for more if you add intrusion detection or large blocklists. But a high-capacity SSD does nothing for a machine dedicated to pfSense.

Can the NUC 14 Pro route a fast fiber connection?

The port runs at 2.5 GbE. In a router-on-a-stick setup, Internet traffic enters and leaves through that same port, on two VLANs. On a home connection this generally holds up, but it depends entirely on the switch. For multi-gigabit fiber with heavy local traffic, a machine with separate ports is a better fit.

Key facts

2 minimum (or 802.1Q VLANs)
Network ports needed
x86-64, 1 GB RAM, 8 GB disk
Official minimum
Netgate Installer (online)
Installer
192.168.1.1/24
Default LAN

Our picks

Affiliate links · same price for you
Recommended
Minisforum MS-A2

Minisforum MS-A2

View on Amazon

Amazon · price and availability on the listing

Alternative
📦

ASUS NUC 14 Pro

View on Amazon

Amazon · price and availability on the listing

See all our recommended gear in the shop.

Tags: pfsensemini-pcinstallationguide2026

Related

Tutorials

Home Assistant on Mini-PC in 2026: Zigbee Key and Backups

Install Home Assistant Container with Docker Compose on a Linux mini-PC, add a ConBee III stick through ZHA, and set up encrypted automatic backups, local HTTPS with Caddy and two-factor authentication.

Read
Tutorials

Metal Rack Assembly for Home Lab 2026: Step-by-Step Guide

Discover our comprehensive and detailed tutorial to install a metal rack in 2026. Follow our practical tips, complete configuration files, and exact commands.

Read
Tutorials

Upgrade Your Homelab to 10 GbE in 2026: DAC, Fiber or RJ45, and a Step-by-Step Direct Link

Moving your homelab to 10 GbE in 2026: SFP+ or RJ45 10GBASE-T, DAC cable, AOC or fiber module, Intel X710-DA2 and X520-DA2 cards, then a direct DAC link configured with Netplan and checked with iperf3.

Read