PfBlockerNG
-
Add that Blocked IP to a Whitelist Alias. I described how to do that in a post this morning.
That worked thanks!
-
It's strange that there are no aliases. (url tables) listed? Are you sure you checked it properly?
Try to run this command from the shell :
pfctl -sa (and at the end of the output, do you see any pfblocker tables?)
Also try to delete all files in
/var/db/aliastables (then reboot)
Thank BBcan117,
Your post made it clear to me… I kept thinking I was to delete aliases from WebGUI "Firewall" > "Aliases". I now realize I need to delete aliases from /var/db/aliastables/
I've done as you suggested, and I think it is working... So far, no error messages. I'll wait a day to recheck.
Thanks again. -
What am I doing wrong????
Just when I think I'm doing great, I see I'm messing up.
I had China blocked in Country block. I've added 6 lists for and all seemed good. Now I'm getting nailed from China. I see that in County Block China is no longer listed. China by it's self does more than everyone else put together!
Help!
-
Hi Bummer, I need some more details to help.
You added "China", is it "Deny Both" or "Deny Inbound" or "Deny Outbound"?
The 6 Lists are also which Action setting?What do you mean by "I see that in County Block China is no longer listed."?
-
Lazy man's feature request: can you make the widget's aliases clickable? Like, show what's in the alias on hover (like when you hover in Firewall - Rules) and edit the alias when the row is double-clicked. :D
And I can, if you reply back on the testing of the Nano/Ramdisk Aliastables issue/Fix ;D >:(
-
And I can, if you reply back on the testing of the Nano/Ramdisk Aliastables issue/Fix ;D >:(
Hmmm… I tried to apply the pull request and failed, even after editing out those erroneous .bak files and whatnot.
-
Yeah, I need to make things clearer. You know what they say, "A picture is worth a 1,000 words.". Well attached is a screen cap of what I have.
I had China blocked in the Country Block. But something in my lists must have unblocked it as well as other countries I had blocked under Country Block.
I really appreicate you help and in repeating stuff. I read things and then can't find it later when looking for it. It gets frustrating and I hate bothering the community. Everyone is so good.
-
I'm doing this again in hopes that people read it the fifth time ;D .. and for those that are afraid to ask … ;D
-
What is the "White Listed IPs" (Generally speaking). Are these IPs that might be blocked by a Country Block? You normally do not want to allow inbound like that.
-
You can make a Single Alias "Malicious" and put multiple Lists into one… Makes it easier to organize.
-
Spamhaus only needs to be "Deny Outbound" as the Firewall is already Blocking Inbound. Unless you have open ports that you want to protect?
-
Why are the last two aliases set to "Deny Inbound" when you should block the "Outbound"? Unless you have Open Ports on the Wan (Inbound).
-
Country Blocking is set in the Continent Tabs. They will not show in the IPv4 tab. Where do you see it missing in your setup?
-
-
Yes, I'm a dummy. :-\
-
The Ips are to insure they are not blocked. These client are my bread and butter. One is from the UAE and the other is from IT.
-
I'll look in to the Alias. To me this seemed easier to manage.
-
Dumb question - where is the Spamhaus being denied access inbound? Via other lists? Sorry, I'm confused on this one. It shows it is blocking.
-
The ports I have opened are only the ones used. The last 2 are showing that they are blocking inbound.
-
As for the Continent tabs, it was set to block China. It was highlighted or whatever you want to call it. China is still showing up, but not as being blocked.
My concern it to protect the network by blocking all incoming traffic that could do harm.
-
-
No problem… Lets get it working for you...
-
Just be careful with a "Permit Inbound Rule". Make it very specific to a small IP range. You don't want to open up a large CIDR range if you don't need to... If the IPs are not in a Country that you are blocking, then a Country Block will not block it... Do you expect a list to Block any of those Whitelisted IPs... Its up to you. Just giving you information.
-
Spamhaus is "Deny Both" so if you do not have any Open ports, it could be "Deny Outbound".
-
Opened ports are opened if you created a NAT Rule or something similar.
Just remember that pfSense is a "Stateful Firewall" It blocks all Inbound by default. If a device on the Lan (Inside) wants to go out thru the Firewall, it will open an Outbound State which inturn allows that IP Inbound access. So generally, you can set these lists to "Deny Outbound"… Its only needed if you have defined open ports.
Read up on what a "Stateful Firewall means" ...
In the Asia Tab, Select "China", Set the "List Action" as "Deny Outbound" and Run a "Force Update"... If you defined any Open Ports, than use "Deny Both".
-
-
I really appreciate your help.
As for the inbound Ips, there is no range. They are 3 Ips and nothing else.
As for Spamhouse, e do have a mail server. My concern is more with spam coming in than leaving. Although, I don't want a hacked client spamming someone else.
Yes, the NAT rule only open the ports that we use. All other ports are closed.
Okay, I'm curious, for China why do I deny outbound? Isn't inbound that I should be concerned about?
Thanks!
-
I am using List Action: Deny Both. How can I use custom addresses to insert some whitelisted IPs ?
Giacomo
-
Either create a new white list alias (ipv4/ipv6) with Permit_outbound. Permit rules are listed automatically above deny rules.
Permit_both only if you really need certain traffic to always pass without initially being originated from your LAN network. So, extremely rare in most cases. *Or, if you enabled suppression in General settings, just suppress the IP's in question if they are blocked. (In the alert tab* or manually add them to pfBlockerNGSuppress alias).
I use a whitelist alias, since I push my settings to over 40 boxes on occasion. Edit 1 list = 40 boxes having the same whitelist.
*edit *
more detail on permit_outbound vs permit_both at request. -
I'm using the Suppress List feature. However, it has an inconvenience: I wanted to "unlist" some allowed IPs, so I deleted them from the pfBlockerNGSuppress Alias, but the widget always reports them as suppressed :(
-
I'm using the Suppress List feature. However, it has an inconvenience: I wanted to "unlist" some allowed IPs, so I deleted them from the pfBlockerNGSuppress Alias, but the widget always reports them as suppressed :(
Run a "Force Update" and it will update the suppression count but the IPs you un-suppressed will not be restored until the next "Cron" event. You also have the choice of a "Force Reload" which will reload all previously downloaded lists to reflect the current settings.
-
Anyone know what's going on here? If I'm reading this correctly, the "Snaity Check" isn't correct. Is it? If not, what do I need to do to fix it?
#########################
Sanity Check (Not Including IPv6) ** These two Counts should Match! **
–----------
Masterfile Count [ 32614 ]
Deny folder Count [ 41350 ]Duplication Sanity Check (Pass=No IPs reported)
–----------------------
Masterfile/Deny Folder Uniq check
Deny Folder/Masterfile Uniq check
64.104.125.0/24 64.71.172.0/28 64.71.172.128/25 64.71.172.16/31 64.71.172.19/32 64.71.172.20/30 64.71.172.24/29 64.71.172.32/27 64.71.172.64/26 64.78.162.0/24 65.19.135.0/24 65.19.152.0/24 65.19.188.0/24 65.255.36.0/24 65.255.38.0/23 65.63.56.128/27 65.63.89.204/30 66.160.130.0/24 66.160.162.0/24 66.201.188.0/24 66.231.64.0/20 66.54.80.0/22 72.28.117.0/24 74.125.16.64/26 91.234.36.0/24 95.130.197.0/25 98.126.145.0/24 98.126.221.0/24 98.126.222.0/24 98.126.90.0/24Sync Check (Pass=No IPs reported)
-
Run a "Force Reload"…
-
Ha, ha, ha… if I've learned and remembered anything from this forum, it was to perform a "Force Reload"!
I did it again and the cron is ready to run in 8 minutes. We'll see what happens. and I'll let you know.
-
I have submitted Pull Request #820 to fix the following issues:
1. Issue for Nano and Ramdisk Installations -
The /var and /tmp folders get wiped on Reboot. This will delete the /var/db/aliastables folder which on Reboot causes a 60 second timeout per pfBNG Alias (Which for some can timeout for 20mins). The new functionality will now Archive the Aliastables on any Alias updates.
Using the **<earlyshellcmd></earlyshellcmd>**functionality, it will restore the archived Aliastables on reboot to prevent this issue.
However, all of the other /var/db/pfblockerng files are also deleted. To restore those files, a "Force Update" is required or ultimately will get restored by the next CRON run. This however, will not affect the reboot process.
If you manually patched the download_file() function from 60 secs to 5 secs. You can revert that change as its not required with these new changes.
2. Improved the Alerts Tab to handle a Large firewall log file (as 2.2 has functionality to increase the size of the log file). These changes should result in a 50-75% improvement in loading/CPU usage. The Javascript functions were also improved to avoid it being called when the "Auto Resolve" checkbox was not enabled. This was spinning up 2-3 additional php-fpm processes. A timeout was also added to reduce the hostname lookup to 30seconds. If you refresh the Alerts Page shortly after it loads, it can seem to take a little longer, but this is due to the hostname lookups that are still in progress.
3. Made additional improvements to the IPv6 Regex functionality.
4. This will bump the pfBNG version to 1.05.
The following Pull request #820 has been merged… pfBNG v1.05
Additional Fix's in this PR (Including all the above)
1. Aliastables Issue with Nano/Ramdisk Installs (See above)
2. Alerts Tab Improvements. I have also added a "Filter Regex" which will allow you to filter the Alerts better. Please use a "regex-style" search pattern.
3. "Keep Settings" is now a Default Setting. If you haven't already, please enable this checkbox!
4. Fix to the Cron Scheduler (mismatch between 0hr and 24hr) Thanks to Phil.Davis, for spotting it and for providing the patch! Much appreciated!
Please let me know if you have any issues… I hope you guys are happy with the Improvements!
Thanks!
-
Nope - same issue… :-(
