PfBlockerNG
-
ye, ******* :)
-
I've updated the install steps to make it easier :)
-
Output of full patch apply test:
/usr/bin/patch –directory=/ -t -p1 -i /var/patches/54c7f4a39c5e8.patch --check --forward --ignore-whitespaceHmm... Looks like a unified diff to me...
The text leading up to this was:-- pkg-utils.orig.inc 2015-01-27 14:27:38.000000000 +0000
+++ pkg-utils.inc 2015-01-27 14:27:50.000000000 +0000 No file to patch. Skipping... Hunk #1 ignored at 624. 1 out of 1 hunks ignored while patching pkg-utils.inc done Close Is the patch info I got when I tried to use your patch. I am running 64 bit release 2.2
-
-p1 is obviously wrong with –directory=/
Kindly use the System Patches package and see the screenshot above. If you cannot handle that, you probably should avoid doing similar changes in the first place.
-
I did use SYSTEM patches and pasted that in the code window and hit Test patch and this is the result I got
-
Go back to the screenshot. Really.
-
I found the problem it was the screenshot I did I typo in my directory area
Thank you and sorry for the posts regarding this
-
Is there a suggested base directory for the patch mentioned earlier?
I'm pretty new and trying my best, but I can't figure this part out. I looked at the screen shots and it shows /etc/inc, yet I cannot progress to the next step of the instructions (install…).
Thank you in advance for your time, I appreciate your comments.
-
It's /etc/inc/ dir just like the screenshot shows.
Save the patch then click on test (see what it returns) then apply it.
-
Thank you for your reply, Marc :) With some help, it is now up and going.
I'm going to go into the corner now and hang my head in shame lol.
-
This is working great great!
Thank you BBcan!
Thanks marcelloc and doktornotor for showing how to get this downloaded and installed.
-
Someone should make a page on how to use this on
https://doc.pfsense.org/index.php/PfblockerNG
I got it running just trying to get the lists I put in to block like the old did. Still more testing on it.
-
I think the first steps is for this package to become an Official pfSense package.. before anything else
Its use at your own risk. I'll help out with support/tips once its official but until then, I can't. I don't want to be responsible if my advice breaks your box. It is pretty easy to use, just read the pages ;-) Everything you need to know if there
-
@marcelloc - Thanks a million for the steps to install pfBlockerNG. I was just a tad disappointed to see that the installed version doesn't have the DNSBL tabs. Is there any way to get the version that's referenced in this post?
Thanks,
MediocreFred. -
It's not merged yet and still in the testing phase
-
I was just a tad disappointed to see that the installed version doesn't have the DNSBL tabs.
DNSBL - I am still developing this at the moment.
pfBlockerNG v1.0 still needs to be reviewed by the Devs for it to be an Official pkg.
So I expect that I will release DNSBL in v2.0. I also expect to have easylist AdBlock plus integrated into the pkg. It won't have all of those features, but it will pull all of the AdBlock domains for blocking.
-
if I restore the config from the old pfblocker package, will NG pick it up? Or do I have to reconfigure it from scratch?
-
You'll have to configure it from scratch. Its a brand new package, separate from pfBlocker
-
I was just a tad disappointed to see that the installed version doesn't have the DNSBL tabs.
So I expect that I will release DNSBL in v2.0. I also expect to have easylist AdBlock plus integrated into the pkg. It won't have all of those features, but it will pull all of the AdBlock domains for blocking.
Ah you liked my idea and think you can bring in those lists? They are not standard like CIDR or IP lists. That would be amazing.
Wonder if there could be history little long in the widget on home page so you can refresh screen and not zero out all the hits blocked? Maybe option for how long you want to keep or clear each time refresh for those that like that.
The Alerts page also maybe could have some range of days you would like to see. Maybe the widget has direct link to that page with the logs link you have -
They are not standard like CIDR or IP lists. That would be amazing.
Yes DNSBL is already designed to handle domain names. Take a look at the Link in the post above. I have the most common formats already working, I have played with AdBlock plus list about a month ago, but put it aside for now, as it's in a non-standard format. I want to get the key parts of the code working first before spending more time on this AdBlock feature.. But it is on to todo list. So this will be released in v2.0 of pfBNG.
Wonder if there could be history little long in the widget on home page so you can refresh screen and not zero out all the hits blocked? Maybe option for how long you want to keep or clear each time refresh for those that like that.
The widget counts are "0" when the filter_reload is executed. So the design pfBNG is to only clear the widget when there are rules changes. So if the rules remain static, the widget counts will continue to increase without being cleared… This is the design of pfctl as that is where the counts are queried from.
The Alerts page also maybe could have some range of days you would like to see. Maybe the widget has direct link to that page with the logs link you have
The Alerts tab is not the place to handle queries of that nature. The best would be to send the logs to a remote syslog server for further analysis and correlation. The Alerts Tab references the pfSense Firewall log, which in itself doesn't hold data for very long.
