Block VPN brute force attacks on your OPNsense firewall with ThreatListPro's automated IP blocklist. Configure a URL alias and firewall rule in under 5 minutes.
Start 14-Day Free Trial (No Card)OPNsense is a powerful open-source firewall, but its VPN endpoints are still visible to the internet. Attackers don't care if you're running open source or commercial -- they scan and attack every exposed port.
Whether you run OpenVPN, WireGuard, or IPsec on OPNsense, your VPN endpoint is discoverable by mass-scanning bots like Shodan and Censys. Once found, attackers launch automated credential-stuffing and brute force campaigns. OPNsense's built-in rate limiting helps but doesn't stop distributed attacks from thousands of source IPs.
OPNsense supports URL Table aliases that fetch external IP lists on a schedule. ThreatListPro's feed plugs directly into this feature. A single firewall rule referencing the alias blocks all known VPN attackers at the packet filter level -- before any VPN handshake or authentication attempt occurs.
Add ThreatListPro as a URL Table alias and create a blocking firewall rule in OPNsense.
Sign up at threatlistpro.com and copy your unique feed URL from your welcome email:https://api.threatlistpro.com/v1/YOUR_API_KEY/blocklist.txt
In OPNsense, navigate to Firewall > Aliases and click Add. Set the name to ThreatListPro, type to URL Table (IPs), and paste your feed URL in the Content field. Set the refresh frequency to 1 hour. Click Save and Apply.
Go to Firewall > Rules > WAN. Add a new rule at the top of the list. Set action to Block, direction to in, source to the ThreatListPro alias, and destination to This Firewall (or your VPN interface address). Save and apply changes.
Set the URL Table alias Refresh frequency to 1 hour. OPNsense accepts separate days and hours in current 26.x releases. To run the alias updater now from the OPNsense shell, use the command below. It re-downloads a URL Table only when its refresh interval has elapsed or the alias was changed; OPNsense also runs this check automatically every minute.
configctl filter refresh_aliases
Check Firewall > Aliases for a recent Last updated value and a plausible Loaded# count. Then open Firewall > Diagnostics > Aliases to inspect the loaded addresses. With logging enabled on the block rule, use Firewall > Log Files > Live View to see matching traffic.
Check each stage in order: fetch, parse, load, rule, then hit. A successful download alone does not prove that the firewall rule is using the table.
| Stage | What to verify in OPNsense 26.x |
|---|---|
| 1. Fetch | Open Firewall > Aliases. The alias should be enabled, Last updated should advance after a scheduled or manual refresh, and Loaded# should show a plausible nonzero count. |
| 2. Parse | Confirm the source contains one IPv4 address or CIDR network per line. Lines beginning with whitespace, a comma, semicolon, pipe, or hash are ignored by the URL Table parser. |
| 3. Load | Open Firewall > Diagnostics > Aliases, select ThreatListPro, and inspect the addresses actually present in the firewall table. |
| 4. Rule | Open the rule on the WAN or VPN-facing interface. Confirm it is enabled, uses ThreatListPro as Source, targets the intended service, and has logging enabled. |
| 5. Hit | Open Firewall > Log Files > Live View and filter for the rule description or a test source address. Live View only records a match when rule logging or an applicable global logging option is enabled. |
Use the observed symptom to isolate scheduling, parsing, capacity, network, and rule problems.
| Symptom | Check | Fix |
|---|---|---|
| Last updated is stale | Open the alias and verify its Refresh frequency. | Set the interval to 1 hour, save and apply, or run the documented update action: |
| Fetched file produces an empty or partial table | Inspect the text format. OPNsense expects one IPv4 or IPv6 address per line and ignores lines starting with whitespace, comma, semicolon, pipe, or hash. | For this IPv4-only feed, keep one IPv4 address or CIDR network per line without leading whitespace or comment characters. |
| Loaded# is zero or table capacity is exhausted | Compare the alias count with the capacity indicator on Firewall > Aliases. | If necessary, raise Firewall > Settings > Advanced > Firewall Maximum Table Entries. That limit covers aliases and other firewall tables combined. |
| Alias cannot be fetched or resolved | Use Interfaces > Diagnostics > DNS Lookup for the feed hostname. After a refresh attempt, inspect Firewall > Log Files > General for fetch, DNS, or TLS details. | Correct DNS, routing, system time, HTTPS certificate trust, or upstream access before refreshing the alias again. |
| Table is loaded but no blocks appear | Inspect Firewall > Diagnostics > Aliases, then verify the enabled interface rule references the alias and has logging enabled. | Correct the rule interface, order, source, destination, or logging option, apply changes, and check Firewall > Log Files > Live View. |
Compare automated VPN-focused blocking against other approaches for protecting your OPNsense firewall.
| Feature | ThreatListPro | Manual Blocking | Enterprise Threat Feeds |
|---|---|---|---|
| VPN brute-force focused | ✓ | ✗ | ✗ |
| Checked for new attackers every 6 hours | ✓ | ✗ | ✓ |
| OPNsense URL alias compatible | ✓ | ✗ | ✓ |
| Setup in under 5 minutes | ✓ | ✗ | ✗ |
| Price | $19.99/mo | Staff time | $500+/mo |
Go to Firewall > Aliases, add an alias, choose URL Table (IPs), paste the feed URL into Content, and set Refresh frequency to one hour. Save and apply. Then create a logged block rule on the WAN or VPN-facing interface with the alias as Source and the protected service as Destination.
Yes. OPNsense documents its intrusion prevention system as Suricata-based, and an IP alias can be used separately in firewall rules. Use both as distinct controls: the alias rule blocks matching source addresses, while IDS/IPS evaluates traffic against enabled rules. Neither control guarantees that every brute-force attempt will be stopped.
No. ThreatListPro's feed is IPv4-only. Create the OPNsense alias as URL Table (IPs) and use it in an IPv4 firewall rule. Do not create a second IPv6 alias for this feed. The list does not cover IPv6 traffic.
First check Firewall > Aliases: Last updated should advance and Loaded# should be nonzero. Then inspect Firewall > Diagnostics > Aliases. If the table is empty, confirm the Refresh frequency, source format, DNS resolution, HTTPS reachability, and Firewall Maximum Table Entries. Run the documented alias-refresh action and review Firewall > Log Files > General for fetch errors.
Verify the chain in order: Firewall > Aliases shows a recent Last updated value and a plausible Loaded#; Firewall > Diagnostics > Aliases contains addresses; the enabled rule references the alias as Source; and Firewall > Log Files > Live View shows matches. Enable logging on the rule before expecting hits there.
Automated VPN brute force protection in a single URL alias. No plugins required.
Start 14-Day Free Trial (No Card)ThreatListPro provides a standard IP blocklist feed compatible with any firewall that supports external lists.
Learn more about IP blocklists, VPN security, and how ThreatListPro compares to alternatives.
Vendor documentation used to verify the OPNsense 26.x paths, settings, commands, and behavior in this guide.
Aliases — URL Table types, refresh frequency, source format, Loaded#, Last updated, diagnostics, and table capacity.
OPNsense source: URL Table parser — which leading characters cause a line to be ignored.
Firewall Diagnostics — inspecting loaded alias contents and finding alias references.
Firewall Rules — using aliases in rules and enabling logging for Live View.
Firewall Log Files — Live View behavior and logging requirements.
System Settings — the configctl filter refresh_aliases action.
Advanced Firewall Settings — Firewall Maximum Table Entries.
Interface Diagnostics — DNS Lookup and related network diagnostics.
Intrusion Prevention System — OPNsense's Suricata-based IDS/IPS.
OPNsense 26.7 release series — current 26.x Community Edition release documentation.
Last updated: October 28, 2026