PfBlocker
-
Quick update, i exported my nanobsd config and imported it in a microdrive + classic embedded installation (so no nanobsd)
I can confirm that I have zero issue now and boot time takes 2 minutes.
So the problems I noticed are only while using nanobsd.
-
hubsd,
Second test, first problem:
I've changed /etc/platform to nanobsd.
after a reboot mount -a returns:/dev/ad0s1a on / (ufs, local, noatime, read-only, synchronous) devfs on /dev (devfs, local) /dev/md0 on /tmp (ufs, local) /dev/md1 on /var (ufs, local)So, read-only file system.
installed and configured pfblocker with no issues.
after a reboot,
I got the same error:php: : The command '/sbin/pfctl -o basic -f /tmp/rules.debug' returned exit code '1', the output was 'no IP address found for grep: /tmp/rules.debug:15: file "/var/db/aliastables/pfBlockerTopSpammers.txt" contains bad data pfctl: Syntax error in config file: pf rules not loaded' php: : New alert found: There were error(s) loading the rules: no IP address found for grep: /tmp/rules.debug:15: file "/var/db/aliastables/pfBlockerTopSpammers.txt" contains bad data pfctl: Syntax error in config file: pf rules not loaded The line in question reads [ /tmp/rules.debug]: php: : There were error(s) loading the rules: no IP address found for grep: /tmp/rules.debug:15: file "/var/db/aliastables/pfBlockerTopSpammers.txt" contains bad data pfctl: Syntax error in config file: pf rules not loaded - The line in question reads [ /tmp/rules.debug]:But, without saving any new config, I've looked at diagnostics-> table and pfBlockerTopSpammers was filled up normally, alias was there and firewall rules too.
So, Isn't it just a 'until boot finishes issue'?
Can you check if it happens the same way on your installation?
I know system alerts are annoying and have to be fixed but if package is still working, isn't it a minor issue?
Second problem:
boot takes 3 to 4 minutes.
it's a problem in fetch call that has no time out(or 01:15 timeout), I'll include a timeout patch to pfsense-tools.inc file on next release.Just saw your answer, well the problem is only until boot finishes issue yes ! It slow down boot time + spam warning messages. pfBlocker works fine so yes it's not a major issue and is because of nanobsd …
-
Version 0.1.4.2 includes fixes to 3-9 minutes boot on embedded systems.
-
thanks !
-
just installed pfsense and this tonight…. getting emails of this:
There were error(s) loading the rules: /tmp/rules.debug:17: cannot define table pfBlockerAfrica: Cannot allocate memory
/tmp/rules.debug:19: cannot define table pfBlockerAsia: Cannot allocate memory
/tmp/rules.debug:21: cannot define table pfBlockerEurope: Cannot allocate memory
/tmp/rules.debug:23: cannot define table pfBlockerNorthAmerica: Cannot allocate memory
/tmp/rules.debug:25: cannot define table pfBlockerOceania: Cannot allocate memory
/tmp/rules.debug:27: cannot define table pfBlockerSouthAmerica: Cannot allocate memory
/tmp/rules.debug:29: cannot define table pfBlockerTopSpammers: Cannot allocate memory
/tmp/rules.debug:31: cannot define table pfBlockerBlockedLists: Cannot allocate memory
pfctl: Syntax error in config file: pf rules not loaded The line in question reads [17]: table <pfblockerafrica>persist file "/var/db/aliastables/pfBlockerAfrica.txt":( how do I fix?
edit just figured out how to up my tables size. Upped it to 100mil.
I'm testing the ad blocking lists and they aren't blocking anything. All I've done was add the lists and tell it to deny_inbound. Is there anything else I should be doing to make this work? Thanks.
Also if anyone knows of any great ad lists to help me block all the advertisements I possibly can please do let me know! :)</pfblockerafrica>
-
While blocking adwares, proxies, spywares the default way is outbound
Take a look in ipblocklist, the are many lists there.
Also pay attention on direction.
If you want to do not access somewhere, the action is deny outbound.
If you want that someone in somewhere do not access your network, the action is deny inbound.If 100mil means you Speaker portuguese, there is also a pfBlocker topic in portuguese forum.
-
While blocking adwares, proxies, spywares the default way is outbound
Take a look in ipblocklist, the are many lists there.
Also pay attention on direction.
If you want to do not access somewhere, the action is deny outbound.
If you want that someone in somewhere do not access your network, the action is deny inbound.If 100mil means you Speaker portuguese, there is also a pfBlocker topic in portuguese forum.
I'm American. Thanks for the clarification. I was up till 3am last night playing with this, tweaking and fixing several small issues. Still got a few left, but so far I am amazed at pfsense. This is way better than Mikrotik for my needs and its FREE. :)
-
Yea the quality of this package is outstanding, if i had money, i would donate to it. :D honest.
One feature request would be send all blocks to a new tab in the system logs status page called pfblocker and then have the ability to quickly add blocked ips to whitelist. Also a blocked log widget similar to the firewall logs one also.
-
Yea the quality of this package is outstanding.
Thanks for that, our main goal is write package that improves pfSense quality and help daily admins tasks.
One feature request would be send all blocks to a new tab in the system logs status page called pfblocker and then have the ability to quickly add blocked ips to whitelist. Also a blocked log widget similar to the firewall logs one also.
I can't be done until pfsense has a way to choose log direction or prefix.
pfblocker just help alias and rule creation.When you check enable log, it include rules with log enabled.
-
OK that makes sense. I guess adding a easyrule rule: pass from firewall will do the same thing.
I do not have xmlrpc sync enabled but i am getting this in syslog after update list jobs.
php: /pkg_edit.php: [pfblocker] pfblocker_xmlrpc_sync.php is starting.
Nov 8 12:30:00 php: : /etc/rc.update_urltables: Starting up.
Nov 8 12:30:00 php: : /etc/rc.update_urltables: Sleeping for 45 seconds.
Nov 8 12:30:45 php: : /etc/rc.update_urltables: Starting URL table alias updates
Nov 8 12:30:45 php: : /etc/rc.update_urltables: pfBlockerAsia does not need updated.
Nov 8 12:30:45 php: : /etc/rc.update_urltables: pfBlockerSouthAmerica does not need updated.
Nov 8 12:30:45 php: : /etc/rc.update_urltables: pfBlockerTopSpammers does not need updated.
Nov 8 12:30:45 php: : /etc/rc.update_urltables: pfBlockerMicrosoft does not need updated.
Nov 8 13:45:17 check_reload_status: Syncing firewall
Nov 8 17:51:00 check_reload_status: Syncing firewall
Nov 8 17:51:00 check_reload_status: Syncing firewall
Nov 8 17:51:00 php: /pkg_edit.php: [pfblocker] pfblocker_xmlrpc_sync.php is starting. -
it's just a print before if
not a big deal.
never mind If you do not have checked sync option.
-
My alias keeps getting knocked up to the top of the rule sets I have for my networks (I have a LAN and WLAN network). It's been happening erratically. I'm not sure what is causing it or what to do about it.
* * * LAN Address 22 80 443 * * Anti-Lockout Rule [move] [edit rule] [add a new rule based on this one] [click to toggle enabled/disabled status] TCP LAN net * * 6697 * none Allow all IRC (secure) [edit rule] [delete rule] [add a new rule based on this one] [click to toggle enabled/disabled status] TCP LAN net * * 6667 * none Allow all IRC [edit rule] [delete rule] [add a new rule based on this one] [click to toggle enabled/disabled status] TCP LAN net * * 80 (HTTP) * none Allow all HTTP [edit rule] [delete rule] [add a new rule based on this one] [click to toggle enabled/disabled status] TCP LAN net * * 21 (FTP) * none Allow all FTP [edit rule] [delete rule] [add a new rule based on this one] [click to toggle enabled/disabled status] TCP LAN net * * 443 (HTTPS) * none Allow all HTTPS [edit rule] [delete rule] [add a new rule based on this one] [click to toggle enabled/disabled status] * * * pfBlockerantitorrentout * * none pfBlocker Outbound rule [edit rule] [delete rule] [add a new rule based on this one] [click to toggle enabled/disabled status] * LAN net * WLAN net * * none [edit rule] [delete rule] [add a new rule based on this one] [click to toggle enabled/disabled status] * LAN net * * * * none Default allow LAN to any rule My pfBlocker rule won't stay in the order that I have here. It moves to the top and ends up blocking a lot of traffic my rules allow.[/move] -
If you need custom rules before pfBocker, you must change pfBlocker action to alias only and then create your own block rules.
A shortcut to this is changing pfBlocker applied rules description before changing action.
-
Makes sense. :)
-
Hey guys I'm new here and to pfsense. I noticed that when I enable pfblocker my wireless clients can longer connect to the internet but my wired. Any ideas. I'm using a linksys wireless router with dd-wrt loaded on it. It has worked forever until I enable pfblocker without any rules created. I'm a complete noob to linux/unix. Thanks in advance!!!
-
PfBlocker does not remove or include any rule different from its own rules.
Try disabling it and see what happens.Also try to include some lists and see how it include aliases and rules.
-
You might add something about the rule being under pfBlocker control in the rules description.
-
Don't you think pfBlocker Inbound/outbound rule description is less robotic? :)
-
I created an outbound rule using the ads, spyware, and level 3 list. Once I enabled pfblocker all wireless client stopped accessing the internet. My wired desktop worked perfectly fine. I disabled pfblocker and the wireless clients started working again. Any ideas?
-
i know …. but the warning about the alias is very robotic :D DO NOT EDIT THIS ALIAS
but I did modify one of them and got surprised when the modification was lost :o after a pfBlocker restart.
I'm not sure now, but maybe copy or the rule disappeared too !?
In the end it is easier to just use aliases, that way you can choose the order of the rules.
