PfBlocker
-
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.
-
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 !?
When you copy a rule, you must change pfblocker description to something without pfblocker and rule
In the end it is easier to just use aliases, that way you can choose the order of the rules.
yes, it's realy usefull.
-
@WarMachine357:
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?
Do your wireless clients are on the same subnet as LAN users?
Check rules with pfBlocker enabled and disabled
-
Yeah, they are are the same subnet. The pfsense box hands out dhcp to them. The outbound rule I created comes before the default LAN rule LAN NET. Also, the ntp server in pfsense provides service to the wireless ap.
-
@WarMachine357:
Yeah, they are are the same subnet. The pfsense box hands out dhcp to them. The outbound rule I created comes before the default LAN rule LAN NET. Also, the ntp server in pfsense provides service to the wireless ap.
If wired and wireless machines are on the same subnet and using the same dhcp, I have no idea how pfsense or pfblocker could block one and do not block other. It's weird to me.
-
I have found by moving the rule after the allow rules the wireless clients work. But, that doesn't seem right does it?
-
I agree that it doesn't make sense. What happens to one should happen to the other. But, did you see what I said about moving the rule to the bottom?
-
@WarMachine357:
I have found by moving the rule after the allow rules the wireless clients work. But, that doesn't seem right does it?
No it's not.
An outbound rule blocks access from any to pfblockerAlias.
If you have one rule that permits traffic, the deny rule will have no effect.
