PfBlockerNG v2.0 w/DNSBL
-
Did you select the Interface(s) for the Permit Rule?
-
Did you select the Interface(s) for the Permit Rule?
Can you expound on this? Where exactly is this option?
-
Did you select the Interface(s) for the Permit Rule?
Can you expound on this? Where exactly is this option?
DNSBL Tab: DNSBL Firewall Rule: Interface menu options
-
Is there a way to add this to pfBlockerNG or Aliases, this list of domains
Hi Chain, that list can be parsed without issues… If that was from a URL, just add the URL to a DNSBL alias ... You could also paste that into a custom list and the package will parse it...
i did that, but I notices that it don't show up in the list of site to block, that the link below for the site
http://pastebin.com/050GLwG8
Its a good site for block windows 7-10 spying on people
-
Is there a way to add this to pfBlockerNG or Aliases, this list of domains
Hi Chain, that list can be parsed without issues… If that was from a URL, just add the URL to a DNSBL alias ... You could also paste that into a custom list and the package will parse it...
i did that, but I notices that it don't show up in the list of site to block, that the link below for the site
http://pastebin.com/050GLwG8
Its a good site for block windows 7-10 spying on people
Click the "Raw" button, and you should be able to pull that list with DNSBL, as it removes the HTML formatting…
http://pastebin.com/raw/050GLwG8
-
I've attached some pictures to hopefully shed some light on the issue. As I've said, I have configured pfblockerng and DNSBL succesfully many times in the past without issue.
Can you run this command and send me the output:
grep -B10 -A12 "pfB_DNSBL_Allow_access_to_VIP" /conf/config.xml
-
I've attached some pictures to hopefully shed some light on the issue. As I've said, I have configured pfblockerng and DNSBL succesfully many times in the past without issue.
Can you run this command and send me the output:
grep -B10 -A12 "pfB_DNSBL_Allow_access_to_VIP" /conf/config.xml
PM sent
-
Sent you a reply.
-
Hello BBcan177 thanks for a great package, update for 2.2.6 will or only for 2.3.x?
-
Hello BBcan177 thanks for a great package, update for 2.2.6 will or only for 2.3.x?
You can upgrade from 2.2.x to 2.3.x and pfBlockerNG will upgrade without issue…
-
Thank you for this BBcan177.
I am using it for over a year now everything working really fine.
I want to filter the adult website using this package is this even possible or have to install a proxy ? -
Thank you for this BBcan177.
I am using it for over a year now everything working really fine.
I want to filter the adult website using this package is this even possible or have to install a proxy ?Just have to add the domains that you want to block into a DNSBL Alias…
-
pfBlockerNG v2.0.15 - Pull Request #140 was merged:
See the following for details:
https://github.com/pfsense/FreeBSD-ports/pull/140UPDATE:
Please wait for pfBlockerNG v2.0.16 due to the following unescaped variable issue:
https://github.com/pfsense/FreeBSD-ports/pull/143/files -
pfBlockerNG v2.0.15 - Pull Request #140 was merged:
See the following for details:
https://github.com/pfsense/FreeBSD-ports/pull/140UPDATE:
Please wait for pfBlockerNG v2.0.16 due to the following unescaped variable issue:
https://github.com/pfsense/FreeBSD-ports/pull/143/filesGreat job. Just resolved the issue with dnsbl service not starting.
-
Using pfBlockerNG v2.0.16 I have DNSBL EasyPrivacy turned on from before. It was working fine. After updating to v2.0.16 twitter.com is getting blocked. Was not getting blocked before. I tried to add twitter.com to DNSBL->Custom Domain Suppression (Whitelist) but that doesnt unblock it. If I set the EasyPrivacy feed to Off, twitter.com loads successfully.
-
Using pfBlockerNG v2.0.16 I have DNSBL EasyPrivacy turned on from before. It was working fine. After updating to v2.0.16 twitter.com is getting blocked. Was not getting blocked before. I tried to add twitter.com to DNSBL->Custom Domain Suppression (Whitelist) but that doesnt unblock it. If I set the EasyPrivacy feed to Off, twitter.com loads successfully.
You can suppress directly from the Alerts Tab, which will remove the Domain immediately… if you add the domain manually to the Whitelist, you need to select the "update custom list" checkbox, and run a "Force Reload - DNSBL" for it to take effect...
-
You can suppress directly from the Alerts Tab, which will remove the Domain immediately… if you add the domain manually to the Whitelist, you need to select the "update custom list" checkbox, and run a "Force Reload - DNSBL" for it to take effect...
Ahh thanks for clearing that up. All good now.
-
You can suppress directly from the Alerts Tab, which will remove the Domain immediately… if you add the domain manually to the Whitelist, you need to select the "update custom list" checkbox, and run a "Force Reload - DNSBL" for it to take effect...
Ahh thanks for clearing that up. All good now.
Ahh crap… I have to make another change to the code as it shouldn't have picked up that Domain name :) Sorry guys... I will post a PR to get this fixed ASAP...
-
pfBlockerNG v2.0.17 :
https://github.com/pfsense/FreeBSD-ports/pull/144This will fix the issue with the EasyPrivacy Feed (As noted above)
I suspect that EasyList will also change file formats at some point, but I will make those changes at that time.
Until the PR is merged, either disable EasyPrivacy, or fetch the file from my Github repo:
–> File below is only for pfSense v2.3.x <–
fetch -o /usr/local/pkg/pfblockerng/pfblockerng.inc "https://raw.githubusercontent.com/BBcan177/FreeBSD- ports/88fc815594c48f9d99c2f7feb9649a3586a3ca27/net/pfSense-pkg-pfBlockerNG/files/usr/local/pkg/pfblockerng/pfblockerng.inc"
and run a "Force Reload - DNSBL"
-
pfBlockerNG v2.0.17 :
https://github.com/pfsense/FreeBSD-ports/pull/144This will fix the issue with the EasyPrivacy Feed (As noted above)
I suspect that EasyList will also change file formats at some point, but I will make those changes at that time.
Until the PR is merged, either disable EasyPrivacy, or fetch the file from my Github repo:
–> File below is only for pfSense v2.3.x <–
fetch -o /usr/local/pkg/pfblockerng/pfblockerng.inc "https://raw.githubusercontent.com/BBcan177/FreeBSD- ports/88fc815594c48f9d99c2f7feb9649a3586a3ca27/net/pfSense-pkg-pfBlockerNG/files/usr/local/pkg/pfblockerng/pfblockerng.inc"
and run a "Force Reload - DNSBL"
Manually pulled the update and reverted my twitter.com whitelist. Did a force reload and can verify that the fix does work. Thanks.