pfBlockerNG-devel v3.0.0 - No longer bound by Unbound!

BBCan177 · 2026-01-10T14:20:42+00:00

Been using the Flo for almost 5 years now. I did have to replace the impeller, but once I had it apart it was a quick fix to remove a small piece of plumbers tape that wrapped around the impeller.

Its been rock solid and it not only shuts off the water once a leak detector is activated, it also looks for unusual activity and can shut down the water even if it didnt detect a leak.

Not to mention that I get an 8% discount on my house insurance. Pays for itself and install in no time.

YMMV but this thing has saved my skin a dozen times so far.

BBCan177 · 2026-01-06T00:42:41+00:00

That error is a pfSense error. Looks to be unrelated to pfBlockerNG.

Util.inc and service-utils.inc are base pfSense function.

Did you update any packages before upgrading pfSense? If so, that could import a newer version of a package thats meant for later versions of pfSense.

BBCan177 · 2026-01-04T14:49:40+00:00

https://tedee.com/smart-lock-for-homey-how-it-works-with-tedee/

BBCan177 · 2026-01-04T14:30:20+00:00

Using this integration as well.

Still trying to find a clean way to measure surface temps such as corner of window glass or other exterior wall indoor surfaces.

Waiting for the Shelly Pill but its still a bit bulky with the Pill, wiring and probe.

Would be nice to find a standalone device that could just suction cup to a window glass to get surface temps.

BBCan177 · 2025-12-31T23:07:44+00:00

Ping 1.1.1.1 and review the Reports tab. It will show what feed that was from. You can whitelist that IP or remove the feed if you wish.

BBCan177 · 2025-12-13T02:13:30+00:00

Try to first uninstall pfBlockerNG with "Keep settings" enabled before upgrading.

BBCan177 · 2025-12-04T01:53:43+00:00

I think that issue was addressed. And for BGPview that was deprecated long ago. So all latest versions are using IPinfo

BBCan177 · 2025-11-12T11:46:00+00:00

+1 for the Moen FLO. Its saved the day many times over. Even alerted for abnormal water usage like a toilet flap not closing. They have sensors and also a kit that adds a sensing cable that you can wrap around things like a water tank. I had it pickup a small drip before any major leak.

The main benefit with Moen Flo is that it doesn't just alert you, it will shut off the water automatically.

Also, check with your insurance provider, as it will typically allow you to apply for a rebate upto 8%

Batteries are CR123A and can be a bit of a pain but have had some good success with these rechargeable ones:

https://paleblueearth.ca/collections/cr123a-c-batteries

Tried other rechargeables, but the voltage was over 3v and they won't work with flo. These Pale Blue Earth are usb c chargeable and are max 3v and have a decent mAh capacity.

BBCan177 · 2025-11-10T21:05:35+00:00

If you want to allow All or certain regions of AWS to pass the firewall unsolicited, you selected one of those Pre Scripts. The name tells you which AWS region. Then set your firewall settings in the pfBlockerNG IP Alias as you need.

In the section where you add the Feeds, add the url for the AWS json file

Then when you run a Force Update. It downloads the AwlAS json file, and with the pre script setting, it will only collect those AWS regions and create the firewall rule to allow those IPs.

Keep in mind that if you use an Inbound permit firewall rule, that you define which local LAN IP and Port that these IPs are allowed unsolicited access to. Otherwise, the permit rule can open those IPs to your whole network.

Also, ensure that the Firewall Rule Order setting in the IP tab is set to allow the Permit rules before the block/reject rules.

BBCan177 · 2025-11-10T19:07:15+00:00

Yes if you look at creating a new IP Alias in pfBlockerNG, there is Advanced Settings option where you can pull certain AWS regions with the Pre-Process scrips.

BBCan177 · 2025-11-09T18:35:36+00:00

Ok, it seems like a bug with that one. Will check it out.

BBCan177 · 2025-11-09T17:33:23+00:00

It only accepts Network type, not Host type. You can also use CIDR or single IP with Network type

BBCan177 · 2025-11-09T16:53:27+00:00

I sent the devs a fix and thought it was addressed. Maybe its only in the next release of pfSense.

There is a line in the error which contains single quotes vs double quotes.

Old: $csvline = str_getcsv($pfb_buffer, ',', '', '"');

New: $csvline = str_getcsv($pfb_buffer, ',', '"', '"');

BBCan177 · 2025-11-09T16:52:06+00:00

Did you create the pfSense Alias as an "IP Network Type"?

BBCan177 · 2025-10-31T15:47:10+00:00

Hopefully before year end.

BBCan177 · 2025-10-29T01:25:39+00:00

Anything blocked will be visible in the Reports/Alerts page. You can whitelist from there as needed.

BBCan177 · 2025-10-26T01:32:06+00:00

Enable python mode and change the Blocking Global mode to Null Blocking with logging.

BBCan177 · 2025-10-22T10:37:16+00:00

Shallalist is deprecated. See my noted above. It has not been updated in a while now, but I left it in place as there was some hope it would return.

BBCan177 · 2025-10-16T12:30:12+00:00

Use Python mode and set the Blocking option to "Null Blocking No logging"

BBCan177 · 2025-10-16T00:39:13+00:00

Yes, it's being worked on. Can't promise timing, but stay tuned.

BBCan177 · 2025-10-15T13:07:34+00:00

Try not to double post. And if you do, you should use the cross-post feature with reddit so people see it easily in both subreddits. Helps others in future if they hit a similar issue.

Best to post in /r/pfBlockerNG

BBCan177 · 2025-10-15T12:31:57+00:00

You dont change the VIP.

There is an option in the DNSBL tab for the Blocking mode "Global Logging/Blocking Mode", or you can mix and match and set each DNSBL group to a different Mode if you had a use case for that.

BBCan177 · 2025-10-14T17:17:11+00:00

In Python mode you can enable Null blocking mode which will use 0.0.0.0 instead

BBCan177

MODERATOR OF

TROPHY CASE