PfBlocker
-
they are configured as alias only and yet I've had to re-arrange them 3 times now. I did the aliasing bit specifically to make sure that certain 'targets' were exempt from certain rulesets.
I have a Spammer set, a malicious set and an advertising set Spammer and Malicious I put into floating because I want them to impact on all, I then have the web server followed by the advertising set … the server is aliased as is the local subnet, since the server is encountered first i.e. before the ads then robots etc still work - anything else gets advertising blocked.
I'll scan the documentation again but I'm sure I did it right.
-
My lists are aliased - Spammer1, Malicious1 and ads1, which translate to pfblockerMalicious1, pfblockerSpammer1 and pfblockerAds1 in the rules lists, these carry a comment 'do not edit this alias'
-
Well maybe it's fixed - appreciate the input, I hadn't spotted the 'alias only' in the dropdown box of the pfBlocker itself, I had seen the 'rules and alias only' but since everything I do uses aliases figured that was it - wrong.
I rebooted and things stayed put so despite the sarcasm re documentation I do appreciate the input ;)
-
Posted 'pfBlocker disables firewall on nanobsd when no there is no internet access at boot time' at:
https://redmine.pfsense.org/issues/3109
-
I just started having a possible issue with pfblocker. Even though I have it enabled and all the aliases are created and the CIDRs are present on the dashboard widget, the dashboard widget also shows red arrows pointing down in the status column. What does that mean? I could have sworn the column had green arrows pointing up. ???
-
@nipstech:
I just started having a possible issue with pfblocker. Even though I have it enabled and all the aliases are created and the CIDRs are present on the dashboard widget, the dashboard widget also shows red arrows pointing down in the status column. What does that mean? I could have sworn the column had green arrows pointing up. ???
Did you create any rules on WAN?
-
No I didn't. The only rules are the rules that block private and bogon networks.
-
@nipstech:
No I didn't. The only rules are the rules that block private and bogon networks.
Well, that is the problem… Create something safe there (like, access from 127.0.0.1 to some port). Known bug.
-
That fixed it! I created a safe rule on the WAN interface and even disabled it. Perhaps a "dummy" rule could be created as an option for those of us who run a stripped down firewall like I'm using.
Thanks, doktornotor! :)
-
Well it'd be better to fix the bug instead of creating the dummy rules… lol :D
-
You got that right!
-
When you enable the countries, it should automatically put a rule up if you tell it to block inbound/outbound.. No need to manually create a rule. All of mine auto generated..
-
When you enable the countries, it should automatically put a rule up if you tell it to block inbound/outbound.. No need to manually create a rule. All of mine auto generated..
Let me restate the problem: if your WAN contains no rules (beyond the default pseudo-rules - block private/bogon networks) this does NOT work. The rules are not added and the enable pfBlocker checkbox gets unchecked, and the widget looks as shown in this post. BUG.
-
Backing up libraries…
Removing package...
Removing pfBlocker components...
Tabs items... done.
Menu items... done.
Loading package instructions...I just updated to 2.1 release on my box here. Getting stuck at this while trying to reload pfblocker. Help!
Thanks! :)
-
Anyone else running pfblocker that's updated to 2.1 had issues with lists not updating / populating - all my list URL's are valid, reduced update time to 1 hour but the IP's aren't getting read / or the aliases populated.
As a result the alias is not 'created' and raises rule alerts for unreachable alias's.
Tried uninstalling and re-installing it didn't help - deleted the lists and re-added and that didn't help either …
Also getting a notice that Wan gateway is unknown not using it - which is utter tosh because it is both present and connected - this may or may not be related to pfBlocker
UPDATE : Typing the above prompted a grey cell - I went to check my 'routing' tables and when 2.1 was installed (2.0.3 update) the interfaces got renamed but the routing gateways did not - OPT1 did to OPT1_PPPOE but not WAN which in the system was now WAN_PPPOE ... only in the routing table it wasn't it was still 'WAN' ...
Sorting this sorted pfBlocker ...
-
Backing up libraries…
Removing package...
Removing pfBlocker components...
Tabs items... done.
Menu items... done.
Loading package instructions...I just updated to 2.1 release on my box here. Getting stuck at this while trying to reload pfblocker. Help!
Thanks! :)
found it.
https://forum.pfsense.org/index.php/topic,66571.msg363755.html#msg363755
-
I can't get pfblocker to load this list doc.emergingthreats.net/pub/Main/RussianBusinessNetwork/RussianBusinessNetworkIPs.txt
Has anyone used this list before?
Any ideas on this list? Also pfsense says it detected a crash and this is the info it contains:
Crash report begins. Anonymous machine information:
i386
8.3-RELEASE-p8
FreeBSD 8.3-RELEASE-p8 #1: Tue Jun 11 06:34:27 EDT 2013 root@snapshots-8_3-i386.builders.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_SMP.8Crash report details:
PHP Errors:
in /usr/local/pkg/pfblocker.inc on line 262
in /usr/local/pkg/pfblocker.inc on line 262
in /usr/local/pkg/pfblocker.inc on line 262
in /usr/local/pkg/pfblocker.inc on line 262Filename: /var/crash/minfree
2048Still getting the same as the quoted user and I haven't seen anyone respond to his post yet.
I'm running 2.1-RELEASE at the moment on my firewall and tested the same on 2 virtualbox VM's. Only difference from 2.1-BETA/RC being that php errors now get suppressed.
The list has ~9000 lines in it. I have tried to increase "Firewall Maximum Table Entries" to 999999999, but the list still wont load. Is the php process running out of memory or whats going on?
Also, does changing "Firewall Maximum Table Entries" require a reboot?
-
Also, does changing "Firewall Maximum Table Entries" require a reboot?
It does not require a reboot if you do not had exceeded it.
If you are getting max entries error, clean you lists before increasing "Firewall Maximum Table Entries" value.
-
Good afternoon ;D
I have pfblocker installed and running for months, but I never see any blocking going on at all. The tables do contain IP-adresses, I checked. What might be the cause of this if I may politely ask?
Thank you in advance for your help :-)
-
do you have any rules enabled? Its not showing anything most likely due to that.
