PfBlocker

LinuxTracker

I've been really busy (figuring out Postfix).
I don't have time to update my previously posted spam lists.

(Note: http://forum.pfsense.org/index.php/topic,42543.msg258273.html#msg258273)

For now I have a routine that extracts all new Spam IPs into one list - updated 2x/hour.
http://dl.dropbox.com/u/71477228/freshspam1.txt

I'm also now harvesting spam IPs from a 2nd email server I manage.
http://dl.dropbox.com/u/71477228/freshspam2.txt

As I update these routines, the next rewrites will:

filter out any IPs of major WebMail providers (GMail, AOL, Yahoo, Hotmail, etc)

For now, I whitelist US Yahoo email servers and Hotmail/Live/Microsoft Hosting.
http://dl.dropbox.com/u/71477228/YahooIPsUS.txt
http://dl.dropbox.com/u/71477228/hotmail.comIPs.txt

Sort spam IPs into my existing US and non-US spam lists
Include relevant comment for each IP
Drop off addresses that haven't had a spam hit in x#of days.

Edit: Here's a list of AOL outbound Email Servers
http://dl.dropbox.com/u/71477228/AOL_MailIPs.txt

It's compiled from the information on this page.
http://postmaster.info.aol.com/info/servers.html

LinuxTracker

These spam lists have been effective w/o giving me false positives.

This is a list of fresh US Spam IPs from a major source, updated hourly.
http://dl.dropbox.com/u/71477228/usspamips.txt

This list contains fresh Spam IPs from US and other countries, updated hourly.
I'll eventually get it sorted into US/non-US.
http://dl.dropbox.com/u/71477228/worldspamips.txt

PM me if you want more detail about them.

LinuxTracker

Just an FYI.

I looked around a lot for a versatile, online IP converter.
The only one I ever found is by Bluetack and it never showed up in any of my Google search queries.

http://www.bluetack.co.uk/converter/

S_D

Hi there,

Sorry if I'm being a bit thick here and/or this question has already been asked, but can i use this package download blocklists, create Aliases against them, and then use standard pfsense firewall rules to block those ranges talking to/from just ONE port on a particular IP address (ie, allow it for all other ports)?

Thanks!

marcelloc

S_D,

Sure you can, just configure pfblocker and set action to alias only.

This way pfblocker download,create the lists and you can assgin these aliases to your own rules.

att,
Marcello Coutinho

S_D

Perfect! Thanks for the reply. I'll set it up tonight.

nesense

Hi :)

issue with system being stuck at "configuring firewall…" after reboot/startup with WAN interface down(or having wrong IP config)
using ctrl-c at console doesn't help.

i think the issue is pf tries to grab the lists but keeps waiting?

I tried uninstalling pfblocker and it worked fine with WAN down.
removed aliases + used deny inbound did not help

I'm using pfblocker 1.0.2 and pfs nanobsd 2.0.1

Thank u!

marcelloc

I've pushed an update to avoid downloads during boot process, reinstall the package and test again.

att,
Marcello Coutinho

nesense

@marcelloc:

I've pushed an update to avoid downloads during boot process, reinstall the package and test again.

att,
Marcello Coutinho

I tried reinstalling but package version is still 1.0.2 and I faced the same issue.

Thank u

marcelloc

Try to get some info on system logs.

nesense

php: : The command '/usr/bin/grep -v '^#' '/var/db/aliastables/pfBlockerspyware.txt.tmp' > '/var/db/aliastables/pfBlockerspyware.txt'' returned exit code '2', the output was ''
php: : The command '/usr/bin/fetch -T 5 -q -o '/var/db/aliastables/pfBlockerspyware.txt.tmp' 'https://127.0.0.1:443/pfblocker.php?pfb=pfBlockerspyware'' returned exit code '1', the output was 'fetch: transfer timed out'
php: : The command '/sbin/pfctl -nf /tmp/rules.test.packages' returned exit code '1', the output was 'no IP address found for grep: /tmp/rules.test.packages:17: file "/var/db/aliastables/pfBlockerTopSpammers.txt" contains bad data no IP address found for grep: /tmp/rules.test.packages:19: file "/var/db/aliastables/pfBlockerads.txt" contains bad data no IP address found for grep: /tmp/rules.test.packages:21: file "/var/db/aliastables/pfBlockerspyware.txt" contains bad data no IP address found for grep: /tmp/rules.test.packages:23: file "/var/db/aliastables/pfBlockerhijacked.txt" contains bad data no IP address found for grep: /tmp/rules.test.packages:25: file "/var/db/aliastables/pfBlockerdshield.txt" contains bad data'

marcelloc

Pfsense is trying to update urltables applied by pfblocker during boot.

I'll try to find a way to prevent this if there is no link/ip/webserver up.

TrickyWidget

I got the dreaded error trying to load the Level 1 list:

There were error(s) loading the rules: /tmp/rules.debug:16: cannot define table pfBlockerLevel1:
 Cannot allocate memory pfctl: Syntax error in config file: pf rules not loaded - The line in question reads
 [16]: table <pfblockerlevel1> persist file "/var/db/aliastables/pfBlockerLevel1.txt"</pfblockerlevel1>

My Firewall Maximum Table Entries is set to 4294967295 and still no love. Freshly installed pfSense and pfBlocker, most everything at defaults. Just the one block list. 512MB of RAM, only 32% in use. 1GHZ CPU.

Does anyone have any suggestions?

Thanks.

TrickyWidget

I got this suggestion from marcelloc:

@marcelloc:

Unselect the list, apply pfblocker config.

change again table max entries and apply config.

when you are sure that the new config is applied, try to enable again the list.

That seemed to work for a while, but the error eventually returned (or at once on reboot).

I've got a RAM upgrade on the way to see if going to 1GB helps any.

fragged

Hi,

On my physical 2.0.1 box pfblocker is making duplicate WAN rules. I only though to check after reading this thread: http://forum.pfsense.org/index.php/topic,50408.0.html . I tried to remove + reinstall the package, but it saved the config files and still keeps making duplicates.

pfblocker works fine on my VM, which also has floating rules though I've only used the latest version on it.

Is there a file / config I should also remove addition to the pfblocker package to make sure nothing is carried on.

Regards,
Joona

marcelloc

I've reduces duplicate cases and also applied some forum users patches but there are still duplicates on some cases.

This does not affect pfsense performance or load, is just a minor bug I could not fix 100% yet.

To workaround, you can change pfblocker action to alias only and create your own rules on wan just like the way you did on floating rules.

att,
Marcello Coutinho

TrickyWidget

Upgrading to 1GB RAM and further increasing the firewall table entries seems to have resolved my memory issues with the level 1 list.

marcelloc

Great! thanks for the feedback.

OldGrayandCranky

I believe that a bug exists in pfBlocker 1.0.2 or maybe it is by design but I can't see why it would be.

In a fresh install of pfSense 2.01, after completing the setup wizard and installing the pfBlocker package, WAN rules are not created automatically by pfBlocker unless a manually added rule already exists in the WAN rules. The Action selected was "Deny Both".

The LAN rules are created without any problem. I did a complete fresh install again to verify this. Can someone confirm if this is a bug?

A workaround is to manually create a rule in the WAN rules and then configure pfBlocker. Everything works fine then.

Thanks for your help. :)

phil.davis

Each interface has an implicit "block all" rule on the end (not listed on the GUI). So if there are no WAN rules, or just other blocking rules (like Block bogon networks), then all connection attempts from WAN are being blocked already. So there is nothing to be gained by adding a pfBlocker rule (I guess it would just add extra processing for nothing). The behaviour is by design, not a bug.
Once you open up something on WAN, then you need to go to pfBlocker and "Save" again. It will reprocess everything, find stuff opened up on WAN and add its blocking rules.
Note: if I then delete the rules that opened things up on WAN, go to pfBlocker and "Save", then pfBlocker does not remove its rules from WAN. So you can end up with an unusual-looking state (but no security issue). If you disable pfBlocker and save, then enable and save, it cleans up any rules then puts back the essential rules, restoring the state of things to "normal".