PfBlockerNG
-
I am having trouble viewing the pfblockerNG alerts.
Why does it only find 29 of the 475 blocked packets?Hi oddworld19,
The Alerts Tab takes its info from the pfSense Firewall Log. So if the Firewall log doesn't contain those Alerts, it won't show in the pfBNG Alerts Tab.
You should disable the "Log Firewall Default Block" option. They are filling your log with unneeded data. You could keep the last two "Bogons" and "Private" as those shouldn't fill your logs as much.
Then clear your firewall logs. Followed by Disable and Re-Enable of pfBlockerNG to clear the widget packet Counts and see how it goes from there.
There is a also known issue that I reported to the Devs, but haven't had a response. But that is only specific if you define Ports in the firewall rules. From your post, it doesn't look like you have this issue.
https://forum.pfsense.org/index.php?topic=99929
update:
The Widget has a customization setting to define the "Max packets for Alerts Tab pivot"… Make sure this is set to meet with your requirements.
-
The "IPv4 Custom list" seem to be inactive in pfBlockerNG. It worked fine before. I have several IPs I want to block manually in that list but it is not working. Force update and force reload has no effect. The custom list does not appear on the dashboard either. Anyone familiar with this?
-
@Ip:
The "IPv4 Custom list" seem to be inactive in pfBlockerNG. It worked fine before. I have several IPs I want to block manually in that list but it is not working. Force update and force reload has no effect. The custom list does not appear on the dashboard either. Anyone familiar with this?
Can you post a screenshot of the Alias? Did you select the "List Action" and define the "Alias" name?
-
@Ip:
The "IPv4 Custom list" seem to be inactive in pfBlockerNG. It worked fine before. I have several IPs I want to block manually in that list but it is not working. Force update and force reload has no effect. The custom list does not appear on the dashboard either. Anyone familiar with this?
Can you post a screenshot of the Alias? Did you select the "List Action" and define the "Alias" name?
Well, the alias name is kind of personal ;). Contains one space but no "pfBlocker" or "pfB_". List action is "Deny Both".
-
@Ip:
@Ip:
The "IPv4 Custom list" seem to be inactive in pfBlockerNG. It worked fine before. I have several IPs I want to block manually in that list but it is not working. Force update and force reload has no effect. The custom list does not appear on the dashboard either. Anyone familiar with this?
Can you post a screenshot of the Alias? Did you select the "List Action" and define the "Alias" name?
Well, the alias name is kind of personal ;). Contains one space but no "pfBlocker" or "pfB_". List action is "Deny Both".
Its probably not going to create the alias if its just a "single space" as the Alias name… Give it a proper name and it should be fine. It can't contain and special or International characters.
-
@Ip:
@Ip:
The "IPv4 Custom list" seem to be inactive in pfBlockerNG. It worked fine before. I have several IPs I want to block manually in that list but it is not working. Force update and force reload has no effect. The custom list does not appear on the dashboard either. Anyone familiar with this?
Can you post a screenshot of the Alias? Did you select the "List Action" and define the "Alias" name?
Well, the alias name is kind of personal ;). Contains one space but no "pfBlocker" or "pfB_". List action is "Deny Both".
Its probably not going to create the alias if its just a "single space" as the Alias name… Give it a proper name and it should be fine. It can't contain and special or International characters.
I renamed it abc123 and now it appears as pfB_abc123 on my dashboard. Thanks!
-
Is spam404, one of the DNSBL feeds, gone?
-
Is spam404, one of the DNSBL feeds, gone?
Would have been best to post this in pfBNG v2.0 thread:
Looks like they moved the Spam404 feed to Github:
https://raw.githubusercontent.com/Dawsey21/Lists/master/main-blacklist.txt -
-
Hello ,
is there a possibility to add the negate rule on ports also ? I don't want to block some ports , aka in the top 20 country list . I modified the xml and the inc file but it seems to ignore the option. Is there an other file that I must change that makes the option work ? Thx.
-
Hello ,
is there a possibility to add the negate rule on ports also ? I don't want to block some ports , aka in the top 20 country list . I modified the xml and the inc file but it seems to ignore the option. Is there an other file that I must change that makes the option work ? Thx.
Sure I can add that to the next release… I will also be adding "Adv. Outbound" settings with other additional options...
Here is a screenshot of what to expect:
http://i.imgur.com/XWqznm2.png -
Hello ,
is there a possibility to add the negate rule on ports also ? I don't want to block some ports , aka in the top 20 country list . I modified the xml and the inc file but it seems to ignore the option. Is there an other file that I must change that makes the option work ? Thx.
Sure I can add that to the next release… I will also be adding "Adv. Outbound" settings with other additional options...
Here is a screenshot of what to expect:
http://i.imgur.com/XWqznm2.pngHi CIURI,
I don't think there is an option to use "!" negate a Ports Alias in pfSense… You can edit an existing pfBNG Rule and see if you see it any different?
-
Hi all,
I find my dropbox syncing is blocked.
In logs I see
IBlock_BT_Hijack list contains 162.125.0.0/24 which is used dropbox.
How should I proceed to get dropbox working again.
Thanks.
-
Hi all,
I find my dropbox syncing is blocked.
In logs I see
IBlock_BT_Hijack list contains 162.125.0.0/24 which is used dropbox.
How should I proceed to get dropbox working again.
Thanks.
You need to create a Permit Outbound pass rule for the IP of you seedbox
or get an IP outside that range from your provider. -
Hi all,
I find my dropbox syncing is blocked.
In logs I see
IBlock_BT_Hijack list contains 162.125.0.0/24 which is used dropbox.
How should I proceed to get dropbox working again.
Thanks.
You need to create a Permit Outbound pass rule for the IP of you seedbox
or get an IP outside that range from your provider.Just to be clear when I say dropbox I mean as in Dropbox the company
Their client desktop app is trying to connect out to 162.125.17.0/24 and 162.125.32.0/24I've enabled suppression and manually added both above networks to pfBlockerNGSuppress Alias. And then "reloaded"
What I do not understand is your reference to a seedbox. I am not sure if I have one of those or not … and yes I feel silly saying this.
How/Where do I create this Permit outbound pass rule. And how does pfBlockerNGSuppress tie in?I went ahead and creating a pass outbound in floating rules and moved it to the very top of the list. I am not sure if this is what you meant or if it is correct.
-
Seedbox … Dropbox, whatever rock you boat :P
Did you read the section in the picture.
It tell you NOT to use pfBlockerNGSuppress Alias in FW rules :o
It tell you that suppression ONLY work for /32 or /24 networks.
IBlock_BT_Hijack specify 162.125.0.0/16, so the "+" icon is not available in the Alerts Tab,
Putting 162.125.17.0/24 and 162.125.32.0/24 in pfBlockerNGSuppress is useless.So move the 2 networks to a new alias pfBlockerWhiteList
Create a FW rule on LAN pass pfBlockerWhiteList
or on the floating tab selecting all LANs interfaces
-
Seedbox … Dropbox, whatever rock you boat :P
Did you read the section in the picture.
It tell you NOT to use pfBlockerNGSuppress Alias in FW rules :o
It tell you that suppression ONLY work for /32 or /24 networks.
IBlock_BT_Hijack specify 162.125.0.0/16, so the "+" icon is not available in the Alerts Tab,
Putting 162.125.17.0/24 and 162.125.32.0/24 in pfBlockerNGSuppress is useless.So move the 2 networks to a new alias pfBlockerWhiteList
Create a FW rule on LAN pass pfBlockerWhiteList
or on the floating tab selecting all LANs interfacesAha! Ok I have done this now. But I am still blocked.
So an extra question.
You said set it up as pass outbound meaning the LAN sending to internet.From pfSense Point of view this is inbound right (packets flying off the network into pfsense)? So I have to re-set to direction=in? I initially had it to direction=out and was still being blocked.
I will monitor and see, but you can correct me if i am worng.
Update
–-------
It seems the above in the case. If I set direction=out, I can't ping dropbox network IPs. When set to direction=in, I can.
Have to wait and see now if it stays connected.Update 2
Ok I think that sloved it thanks very much Ron. I now know how to suppress an IP blocked by pfBNG.
-
Whoa there pfsenseboonie, before you run off I am still confused. :o
Not sure if you are blocking inbound direction with PFBlockerng but that would then make sense. ??? but wrong.
If you are NOT running any open ports to services like a Web Server behind the firewall then you DO NOT need to block Inbound. The firewall is already by Default doing that. That would also probably explain the ping sent to Dropseed errr box whatever not getting back in to you. Really only need to block Outbound and save the firewall much needed processor resources for other tasks.
RonpfS was correct in telling you to allow outbound.
If you set only Outbound blocking and let the firewall default handle the inbound blocking it then makes sense to allow out to Dropbox so your machine will initiate the handshake with dropbox and the firewall will allow the return response back in.
Outbound is LAN to WEB…....Inbound is WEB to LAN ;) Keep it simple. -
@webtyro:
Not sure if you are blocking inbound direction with PFBlockerng but that would then make sense. ??? but wrong.
If you are NOT running any open ports to services like a Web Server behind the firewall then you DO NOT need to block Inbound. The firewall is already by Default doing that. That would also probably explain the ping sent to Dropseed errr box whatever not getting back in to you. Really only need to block Outbound and save the firewall much needed processor resources for other tasks.Hey there,
Yes thats correct I have open ports on the wan interface, so only blocking with pfBNG on those specific ports. -
Good. Was not sure. ::) Late night, sleeping at the keyboard again.
