PfBlockerNG

Rudolf Vesely

Hi all,
I’ve just tried to install pfBlockerNG on pfSense 2.3.1_1 and I got error message:

pkg: https://pkg.pfsense.org/pfSense_v2_3_1_amd64-pfSense_v2_3_1/All/pfSense-pkg-pfBlockerNG-2.0.17.txz: Not Found
Failed

After quick check I found that repository contains 2.0.14 but not 2.0.17.

BBcan177

@Rudolf:

Hi all,
I’ve just tried to install pfBlockerNG on pfSense 2.3.1_1 and I got error message:
pkg: https://pkg.pfsense.org/pfSense_v2_3_1_amd64-pfSense_v2_3_1/All/pfSense-pkg-pfBlockerNG-2.0.17.txz: Not Found
Failed
After quick check I found that repository contains 2.0.14 but not 2.0.17.

Should be fixed now… One of the Devs looked into it...

Brutos

Hope someone can help I have outbound deny selected on the IPV4 list below

Alias Name Alias Description Action Frequency Logging
IBlock pfBlockerNG IBlock Deny_Outbound 04hours enabled

PRI1 pfBlockerNG PRI1 Deny_Outbound 01hour enabled

PRI2 pfBlockerNG PRI2 Deny_Outbound 04hours enabled

PRI3 pfBlockerNG PRI3 Deny_Outbound 04hours enabled

SEC1 pfBlockerNG SEC1 Deny_Outbound 04hours enabled

TOR pfBlockerNG TOR Deny_Outbound 04hours enabled

MAIL pfBlockerNG MAIL Deny_Outbound 08hours enabled

Now I want to keep all the listed enabled but i keep getting some good sites blocked like dropbox.com.

Can someone advice how i can exclude these destination domains please. I have tried the advance rule outbound invert but when i do it locks me out of the firewall interface.

BBcan177

@Brutos:

Can someone advice how i can exclude these destination domains please. I have tried the advance rule outbound invert but when i do it locks me out of the firewall interface.

If an IP is getting blocked, then you can either: 1) Suppress the IP from the Alerts Tab 2) Create a new pfBlockerNG alias (Whitelist), and add the IP to the customlist and set the format to "Permit Outbound". Ensure that the "Rule Order" places the Permit Rules, above the Block/Reject Rules.

If a domain is getting blocked by DNSBL, then you need to suppress it from the Alerts Tab.

Brutos

@BBcan177:

@Brutos:

Can someone advice how i can exclude these destination domains please. I have tried the advance rule outbound invert but when i do it locks me out of the firewall interface.

If an IP is getting blocked, then you can either: 1) Suppress the IP from the Alerts Tab 2) Create a new pfBlockerNG alias (Whitelist), and add the IP to the customlist and set the format to "Permit Outbound". Ensure that the "Rule Order" places the Permit Rules, above the Block/Reject Rules.

If a domain is getting blocked by DNSBL, then you need to suppress it from the Alerts Tab.

Thanks I will try that. :)

Jamerson

after i installed this package on a new installation, a error has pop up
Filter Reload
• There were error(s) loading the rules: /tmp/rules.debug:20: cannot define table bogonsv6: Cannot allocate memory - The line in question reads [20]: table <bogonsv6> persist file "/etc/bogonsv6" @ 2016-06-11 23:56:52
any suggestions what its might be ?

BBcan177

@Jamerson:

after i installed this package on a new installation, a error has pop up
Filter Reload
• There were error(s) loading the rules: /tmp/rules.debug:20: cannot define table bogonsv6: Cannot allocate memory - The line in question reads [20]: table <bogonsv6> persist file "/etc/bogonsv6" @ 2016-06-11 23:56:52
any suggestions what its might be ?

The bogons is handled by the pfSense code not pfBlockerNG. Maybe try to disable and re-enable Bogons to see what that does. The package changes the max table entry in the advanced settings automatically so it shouldn't be that.

Jamerson

@BBcan177:

@Jamerson:

after i installed this package on a new installation, a error has pop up
Filter Reload
• There were error(s) loading the rules: /tmp/rules.debug:20: cannot define table bogonsv6: Cannot allocate memory - The line in question reads [20]: table <bogonsv6> persist file "/etc/bogonsv6" @ 2016-06-11 23:56:52
any suggestions what its might be ?

The bogons is handled by the pfSense code not pfBlockerNG. Maybe try to disable and re-enable Bogons to see what that does. The package changes the max table entry in the advanced settings automatically so it shouldn't be that.

will do it and report back,
can i filter the internet with this package ?
block adult websites ? porn ?
does the package wordt with squad guard and squid 3 ?

blueduckdock

@BBcan177:

@Brutos:

Can someone advice how i can exclude these destination domains please. I have tried the advance rule outbound invert but when i do it locks me out of the firewall interface.

If an IP is getting blocked, then you can either: 1) Suppress the IP from the Alerts Tab 2) Create a new pfBlockerNG alias (Whitelist), and add the IP to the customlist and set the format to "Permit Outbound". Ensure that the "Rule Order" places the Permit Rules, above the Block/Reject Rules.

If a domain is getting blocked by DNSBL, then you need to suppress it from the Alerts Tab.

BBCan- first off, great work. Been using pfblocker for a bit and love it (one of my favorite packages on pfsense.) Second- trying to suppress an internal IP (ie. 192.168.1.xxx). I do not have ANY + sign in the alerts tab to add it to the suppression list. As far as I understand, you can add NATted local IPs to the list right? Even when I modify the alias directly and reload, pfblocker continues to block the packets.

For reference, I am blocking LAN outbound to certain countries and some on WAN too perhaps (not at the box to check.) But regardless, it just seems like my box is not working as it should. I'm running 2.3.1-p5 but I DID upgrade from 2.2.6 with pfblocker still installed (I stupidly didn't uninstall before the big upgrade.)

Any ideas?

BBcan177

@blueduckdock:

Trying to suppress an internal IP (ie. 192.168.1.xxx).

I do not have ANY + sign in the alerts tab to add it to the suppression list. As far as I understand, you can add NATted local IPs to the list right? Even when I modify the alias directly and reload, pfblocker continues to block the packets.

You don't suppress Internal IPs.. Suppression is for External IPs and the Suppression Icon is only visible when "suppression" is enabled, and when the External IP is a /32 or /24. Also it won't suppress for Country Blocking…

To have some internal IPs excluded from the Block Rules… Best to use the "Adv. Inbound/Outbound" Rule settings.

blueduckdock

@BBcan177:

@blueduckdock:

Trying to suppress an internal IP (ie. 192.168.1.xxx).

I do not have ANY + sign in the alerts tab to add it to the suppression list. As far as I understand, you can add NATted local IPs to the list right? Even when I modify the alias directly and reload, pfblocker continues to block the packets.

You don't suppress Internal IPs.. Suppression is for External IPs and the Suppression Icon is only visible when "suppression" is enabled, and when the External IP is a /32 or /24. Also it won't suppress for Country Blocking…

To have some internal IPs excluded from the Block Rules… Best to use the "Adv. Inbound/Outbound" Rule settings.

Sounds good. Part of me thought that I'd have to adjust the rules and couldn't use the suppression but I figured I'd try.
Thanks again mate.

gerry

pfsense 2.2.6
I use the country lists to pretty much block anything outside of US/CA
I then have a whitelist set up for any exceptions
I am pretty sure that in the past this worked fine.
At some point the whitelist stopped having any effect.
The firewall rules order also seems incorrect in that the whitelist follows the pfb block lists
After poking around in the settings I found that setting the Rule Order to :
pfB_Pass/Match|pfB_Block/Reject|pfSense_Pass/Match
seems to get things working correctly - and the rules are now ordered as expected with the pass rule above the block rules.
Did something change that requires using this rule order rather than the default to get whitelists to work ?
I would have thought that this and the default would have been the same thing as far as whitelisting goes.
Although this works I am concerned that this may have unforeseen consequences.

BBcan177

@gerry:

pfsense 2.2.6
I use the country lists to pretty much block anything outside of US/CA

Keep in mind that you could also just "Permit" the Countries that you want instead of blocking the world…

I am pretty sure that in the past this worked fine.
At some point the whitelist stopped having any effect.
The firewall rules order also seems incorrect in that the whitelist follows the pfb block lists
After poking around in the settings I found that setting the Rule Order to :
pfB_Pass/Match|pfB_Block/Reject|pfSense_Pass/Match
seems to get things working correctly - and the rules are now ordered as expected with the pass rule above the block rules.
Did something change that requires using this rule order rather than the default to get whitelists to work ?
I would have thought that this and the default would have been the same thing as far as whitelisting goes.
Although this works I am concerned that this may have unforeseen consequences.

Nothing has changed in that part of the code for awhile…

Pippin

Having a problem getting Bambenek "C2 All Indicator Feed" going.
I have tried to put it in DNSBL but get this in log when update:


[ dnsc2allindicatorbambenek ] Downloading update  .. 200 OK
 No Domains Found

Any ideas?

BBcan177

@Pippin:

Having a problem getting Bambenek "C2 All Indicator Feed" going.
I have tried to put it in DNSBL but get this in log when update:
[ dnsc2allindicatorbambenek ] Downloading update  .. 200 OK
 No Domains Found

DNSBL
https://osint.bambenekconsulting.com/feeds/dga-feed.gz
https://osint.bambenekconsulting.com/feeds/c2-dommasterlist.txt

IP
https://osint.bambenekconsulting.com/feeds/c2-ipmasterlist.txt

Pippin

Thanks, those I use without problem, only for dga-feed.gz I have dga-feed.txt.

The one that gives No Domains Found is:
http://osint.bambenekconsulting.com/feeds/c2-masterlist.txt

Or is it not suitable for pfB?
In text editor I see it`s different format then the rest.

BBcan177

@Pippin:

Thanks, those I use without problem, only for dga-feed.gz I have dga-feed.txt.

The one that gives No Domains Found is:
http://osint.bambenekconsulting.com/feeds/c2-masterlist.txt

Or is it not suitable for pfB?
In text editor I see it`s different format then the rest.

It seems like that Feed is a mix of IPs and Domains…

The DNSBL parser is expecting the CSV line to be in a specific format. As you can see from your text editor, the CSV format is different between the two lists...

I would rather not add another function to the DNSBL parser as its just more overhead to go thru for all the other CSV formatted lists. The feeds that I listed above will work just fine as is...

I also recommend to use the .GZ feed, as that will save both BBC and yourself some bandwidth...

Pippin

Ok thanks, will adjust the feed to gz.

I would rather not add another function to the DNSBL parser as its just more overhead to go thru for all the other CSV formatted lists

Ok but thanks for working on this, very nice.

Another thing, I forgot.
In another feed is 127.0.0.1 listed and does not seem to work well with Squid.
Removing the line manually solves it, I should contact them?

ipv4sqblock.jpg_thumb

BBcan177

@Pippin:

Ok thanks, will adjust the feed to gz.

I would rather not add another function to the DNSBL parser as its just more overhead to go thru for all the other CSV formatted lists

Ok but thanks for working on this, very nice.

Another thing, I forgot.
In another feed is 127.0.0.1 listed and does not seem to work well with Squid.
Removing the line manually solves it, I should contact them?

Yes some feeds add RFC1918, and loopback addresses occassionaly… I've even seen 0.0.0.0 which is disasterous ;)

In the case of Firehol, that site updates those feeds once per day. I ususally update the Feeds more often depending on the frequency of updates for a particular Feed. A lot of Feeds make changes hourly... So getting a feed updated once per day, doesn't really do you justice, and I recommend to add the Original Feed source directly into pfBlockerNG and not go thru a third-party to get a Feed.

Also note, that you can enable "Suppression" in the General Tab, which will remove all RFC1918 and loopback addresses automatically which will avoid this issue for the future…

Pippin

@BBcan177:

I recommend to add the Original Feed source directly into pfBlockerNG and not go thru a third-party to get a Feed.

Was thinking about that too now. Next time I have time enough will try to find the original ones.

Also note, that you can enable "Suppression" in the General Tab, which will remove all RFC1918 and loopback addresses automatically which will avoid this issue for the future…

Yeah I saw that but it`s not removing 127.0.0.0/8, 10.0.0.0/8 and 192.168.0.0/16.
0.0.0.0/8 is also on there (:

Will remove that list later, tomorrow another day.