IP blocking
Build IPv4 and IPv6 aliases from feeds, GeoIP data, and custom entries. Use generated rules or reference the aliases from your own pfSense rules.
pfSense package · IP + DNS policy
Block at the firewall. Block at the resolver.
pfBlockerNG turns trusted IP and domain feeds into live pfSense policy, with reports, safe exceptions, and one place to operate both enforcement paths.
§ 01 · Two components
One policy surface.
IP blocking and DNSBL solve different problems. Use either component independently, or combine them for network- and name-level enforcement.
DNSBL
Evaluate domain lists in Unbound, including Adblock Plus and EasyList rules, with selectable response modes and per-query reporting.
Reports and control
Trace blocked traffic and names, add precise exceptions, inspect update logs, and keep the last good data when a feed download fails.
§ 02 · Operating model
Feeds become native policy.
pfBlockerNG downloads, validates, normalizes, and publishes data into the pfSense services already responsible for enforcement.
SourcesIP feeds, domain feeds, GeoIP, custom entries
pfBlockerNGDownload, parse, deduplicate, aggregate, prioritize
pfSensepf aliases and rules, Unbound DNSBL, reports and logs
§ 03 · Start here
Install, configure, explore.
Install pfBlockerNG from the project repository, configure a small verified policy, then explore the wider project.
1. Install pfBlockerNG
Choose a channel and use the copy-ready commands from the official package repository.
2. Configure pfBlockerNG
Establish safe defaults, apply one small list, and verify enforcement before expanding policy.
GitHub organization
Repositories, issues, releases, architecture work, and the people building pfBlockerNG.