OneFirewall vs pfSense: enterprise intelligence for an open-source firewall.
pfSense is a capable, low-cost firewall with no commercial threat intelligence of its own. OneFirewall fills that gap: a scored, Alliance-validated IP feed in pfBlockerNG, and optional log analysis that shows what your rules currently let through.
Firewalls & NGFW · Last reviewed: 20 November 2026
pfSense and OneFirewall are complementary. pfSense provides the packet filter, VPN and routing. On its own, its blocklists are community lists you curate yourself. OneFirewall gives it a maintained, scored feed that pfBlockerNG downloads like any other list.
FreeBSD pf, packages and community lists
pfSense is a FreeBSD-based firewall and router built on the pf packet filter. Rules are stateful and interface-based, and features grow through packages: pfBlockerNG for IP and DNS blocklists, and Snort or Suricata for IDS/IPS.
pfBlockerNG downloads IP lists from URLs on a schedule and turns them into firewall aliases and auto-generated deny rules. Out of the box, those lists are public sources such as country blocks or community DROP lists, and keeping them relevant is the administrator's job.
- Low-cost, flexible, widely deployed in SMEs, branches and labs
- No commercial threat intelligence included
- pfBlockerNG turns any URL-based IP list into deny rules
- Remote syslog can forward firewall events to an external collector
A pfBlockerNG feed, plus syslog for visibility
The integration uses pfBlockerNG's standard IPv4 list feature. No custom code runs on the firewall.
Generate the feed URL
In the OneFirewall dashboard, generate a JWT token, then open Install Agent, activate the pfSense licence and copy the configuration URL it provides (OFA_API_WITH_TOKEN).
Install pfBlockerNG
From System › Package Manager, install pfBlockerNG and complete the wizard.
Add the OneFirewall IPv4 list
Under Firewall › pfBlockerNG › IP › IPv4, add the URL as a source with a Deny action. pfBlockerNG creates the alias and rules and refreshes them automatically.
Forward logs (optional)
In Status › System Logs › Settings, enable remote logging to the WCF Agent on UDP 514 so OneFirewall can score the traffic your rules allowed.
What the configuration looks like
# 1. Enforce: Firewall > pfBlockerNG > IP > IPv4 > Add Source: OFA_API_WITH_TOKEN # URL from OneFirewall > Install Agent > pfSense Format: Auto Action: Deny Both (or Deny Inbound) # 2. Contribute: Status > System Logs > Settings > Remote Logging Remote log server: <wcf-agent-ip>:514 Contents: Firewall Events
Need a dedicated enforcement point? OneDevice runs in Parallel mode alongside pfSense: it receives pfSense logs over 514/UDP and blocks out-of-band, with no inline failure risk.
pfSense and OneFirewall, capability by capability
| Capability | pfSense | OneFirewall |
|---|---|---|
| Primary job | Stateful packet filtering, routing, VPN | Decide which IPs should be blocked, based on live Alliance attack data |
| Threat intelligence | None built in; community lists via pfBlockerNG | Scored feed from 290+ organisations, partners and a honeynet |
| List maintenance | Administrator picks and maintains sources | Maintained by OneFirewall; entries age out by temporal decay |
| False-positive control | Depends on the public list chosen | At least 4 high-trust members must confirm before an IP enters the block band |
| Visibility | Local logs and dashboards | Scores every allowed connection from pfSense syslog in the Defence Center |
| Cost model | Free software; hardware or support optional | Priced per device, not by traffic volume |
What OneFirewall adds to pfSense
Commercial-grade intelligence on a free firewall
The same Alliance feed that protects enterprise Check Point and Fortinet estates, at a price per device that suits pfSense deployments.
No more list curation
Instead of picking and pruning public lists, pfBlockerNG pulls one maintained feed with a threshold you set.
See what your rules allow
Syslog analysis shows which permitted connections came from known attackers, so you know the gap before an incident does.
- Routing, NAT, VPN and interface-level rules
- Snort or Suricata signature inspection
- DNS filtering with pfBlockerNG DNSBL
- Full control of a self-hosted, open-source stack
OPNsense, also pf-based, supports the same syslog forwarding; contact us for its feed set-up.
OneFirewall and pfSense: FAQ
Which pfSense version is supported?
pfSense 2.7.0 or later, with the pfBlockerNG package installed.
Does it need an agent on the pfSense box?
No. pfBlockerNG downloads the OneFirewall list from a URL like any other IP list. The WCF Agent is only needed if you want log analysis or OneDevice.
How does pfSense authenticate to OneFirewall?
The configuration URL generated in Install Agent carries the JWT-based authentication, so pfBlockerNG needs no extra headers.
Can OneFirewall see what pfSense let through?
Yes, if you enable remote syslog to the WCF Agent on UDP 514. OneFirewall then scores every allowed connection.
