You could deselect the "Save settings" check box on the first page and then uninstall/reinstall or
rm -rf /var/db/pfblockerng/ then force an update.

All comes down to what key words used ;)

While the search feature here is for sure not going to be giving google a run for its money - hehehe

You can find stuff.. But prob best to do is just manually look for threads in the section that makes sense, especially if you think something has recently broken or happened to cause a problem.

keywords.png

Yup got it. I didn't know it could create aliases I could use in my own rules ! Much better.

yep that is the option I was looking for, many thanks!!!!

Without knowing more about what you're trying to do the following configuration should create a rule similar to the screenshot you posted.

Replace "Alias for your 10.40.2.56 IP" with an alias you created that contains that IP and select the appropriate gateway at the bottom. Protocol can't be "any" for advanced rules but "TCP/UDP" is the best you can do.

This rule will allow all TCP/UDP traffic from 10.40.2.56 to get to the gateway but it cannot force all traffic from 10.40.2.56 to go through the gateway. That would require a routing rule, not a firewall rule (outside the scope of pfBlockerNG).

IPv4Rule.jpg

Alright, I was finally able to make the -devel package work, by reinstalling pfSense from scratch. Glad to see the IPv6 rules are now working properly!

Thank you for your help.

Install pfBlockerNG-devel

@guardian said in IP Blocking - Is this a bug?:

Thanks for the reply @BBcan177. So is this a bug? I can understand a list changing, and that's no problem -- am I correct that the list name is not logged when the event occurs?
Am I correct then that it's just a matter of report not being able to show which list the IP address is in because the list has changed?

When you refresh the Alerts tab in pfBlockerNG, it checks to see if the IP is still listed in the /var/db/pfblockerng/deny/ folder. If it doesn't find the IP, it will report as "No Match".
What gets added/removed in the Feed (URL) is not managed by the package. IPs are being added/removed all the time by the Feed Maintainers.

@genghiskern
Can you try this:
https://www.reddit.com/r/PFSENSE/comments/b5qpm5/unbound_resolver_error_cant_assign_requested/ejgkuyz/?context=3

pfBlockerNG-devel is the version presently deployed.

@NogBadTheBad said in pfBlockerNG ipv4 not blocking ebay but is blocking twitter:

Yup it relies on DNS pointing to your pfSense box and returns a local IP address :(

Thus far I can either break internet for the OpenVPN client, or still let ads through.

I'm pretty sure this can be done, I'm simply not technically proficient enough to do this alone. :(

@BBcan177 thank you very much for looking at this. I will implement the patched file and report back if the error recurs. I'll also respond in 3-4 weeks if there is still no issue.

@cjbujold said in How to replace Gif with a message for users:

Is it possible to replace the 1x1 gif with a message that tells a user why they are getting a blank page.
We are using PfblockerNG version 2.2.5.22

pfBlockerNG-devel already has a blocked web page for DNSBL.
You wouldn't want the users to see any Blocked page for the 1x1 pixel as that would cause the blocked web page to be seen where all of the ADverts were blocked.

You can however, modify the image to something small:
https://www.reddit.com/r/pfBlockerNG/comments/b5gf5y/dnsbl_1px_gif_location/