Removing pfblocker
-
I had the same issue on my box, and I wanted to try this script so I did… It didn't break anything except that of course, I had to delete/modify any rules that had the table alias in reference.
This said, it didn't remove the pfBlocker menu entry under the "Firewall" menu, but it did remove the widget I had on the dashboard.
The output I received from the script was;
Removing pfBlocker from the pfSense Configuration file
Removed pfblocker
Removed pfblockerlists
Removed pfBlocker Menu EntryI inspected the config file… It left the cron entry which looks like this;
<minute>0</minute>
<hour></hour>
<mday></mday>
<month></month>
<wday></wday>
<who>root</who>
<command></command>/usr/local/bin/php -q /usr/local/www/pfblocker.php cronand of course, the menu item;
<menu>
<name>pfBlocker</name>
<tooltiptext>Configure pfblocker</tooltiptext>
Firewall
<url>/pkg_edit.php?xml=pfblocker.xml</url>
</menu>I tried to run the script again but I got the same results.
I should be able to do the cleanup myself quite easily now, thanks! But if you would like to edit/finalize your script, I can wait a couple of days before I do it manually; I'm not in a hurry…
-
Same result as vlurk. Script ran but left menu entry. Cron job was also still left.
Thanks also for the script. It did automate most of the drudgery.
-
Spoke too soon. When I further examined the conf.xml file, the pfblocker stuff was still in there. When I try to manually remove it, pfsense must see the difference and "saves" itself by overwriting with a backup.
-
When I try to manually remove it, pfsense must see the difference and "saves" itself by overwriting with a backup.
No, that's just because you are creating errors in the XML by incorrect edits.
-
BBcan177:
i re-ran your updated script and it did this time remove the menu entry under Firewall for pfblocker. Thank you.
I then inspected the config.xml file and still see the entries under Installed Packages->Services for pfblocker. It looks like this:
<pfblockertopspammers><config><countries>KR,CN,IN,RU,TR,VN,UA,BR,VE,PK</countries> <action>Deny_Inbound</action></config></pfblockertopspammers> <pfblockerafrica><config><countries><action>Deny_Inbound</action></countries></config></pfblockerafrica> <pfblockerasia><config><countries>IL,JP</countries> <action>Permit_Inbound</action></config></pfblockerasia> <pfblockeroceania><config><countries>AU,NZ</countries> <action>Permit_Inbound</action></config></pfblockeroceania> <pfblockersouthamerica><config><countries><action>Deny_Inbound</action></countries></config></pfblockersouthamerica> <pfblockereurope><config><countries>AX,AL,AD,BY,BA,BG,EE,FO,GG,IM,JE,CS,LV,MK,MT,MD,ME,RU,RS,UA</countries> <action>Deny_Inbound</action></config></pfblockereurope> <pfblockernorthamerica><config><countries>CA,PR,US</countries> <action>Permit_Inbound</action></config></pfblockernorthamerica>I manually edited (removed) this file removing these entries and it loaded OK, so maybe I am good now.
Thanks again for your help.
-
Thanks lt1360hp,
I made a fix to remove those xml tags also.
If anyone else runs the script, they can run the following command after running the removal script to ensure it removed all the the old reminents of the previous version of pfblocker.
grep "pfblocker" /conf/config.xml | grep -v "pfblockerng" -
As I have the same issue and like to run your script, I'm not sure where and how to do so.
Via Command Prompt? If yes, php execute? Which port setting do you mean? (I only know ssh port).
I'm a bit lost here.
There is no pfblocker menu and no pfblocker alias but I had it setup so it takes a .txt file from our website where several hourly updated domain names are listed as IP. But now it blocks it for everyone not just the set alias group. But as pfblocker ain't anymore, I can't access it and need this script to (hopefully) remove all the things related to pfblocker.
(we can't access google atm. due to youtube being on that block list which was only for a specific alias group and not for everyone … no the alias does not exist anymore but the block is still active but not visible in the firewall rules)
E: Ah, you meant to type it into the URL bar of the browser from pfsense GUI? Wasn't sure about which port so I tried it now without a port and it seems to have run and deleted all the stuff from the config file. I just hope that solves my issue now. [well had DNS Forwarder also still active instead of DNS Resolver, and that one assigned youtube IP to google IP to clients even though it resolved it correctly itself.]
E2: No, that's not solving the issue now … pfsense still blocks all IPs that were in an earlier alias which were taken from a .txt list for all clients. Really, I'm lost, I don't know how to resolve this problem. I have deleted the .txt file and do not see a cron job grabbing it again, I have rebooted the firewall and restarted PC and flushed DNS and still ... pfsense gives youtube IP to PC instead of google IP. and this specific youtube IP was part of the IP list in the alias that was blocked for specific computers/IPs but not for all.
-
Hi Melphiz,
Before attempting to use packages, ensure that you have basic connectivity working. Take a look at the firewall rules and remove or disable any rules related to the old pfBlocker.
The text file of IPs that you have for youtube might have changed. What was the source of this list?
-
Hi BBcan177,
The list was created via nslookup on a windows server that uploaded the list to our FTP server.
So, yes, the content did ofc change, as google/youtube change their IPs even within a few hours I noticed.The specific IP that gets blocked by pfsense is 145.253.36.96 BUT only on opt1 not on WAN I noticed.
So again: Pfsense has 8.8.8.8 as DNS for WAN (ADSL) and 8.8.4.4 for opt1 (LTE). The alias (which was originally autocreated by pfBlocker) using the mentioned IP list file was set for several PCs that were and are using WAN for internet access. (so the reject rule was visible at LAN tab)
Now the issue is funnily the opposite: users on opt1 (there's a rule on LAN tab that directs an alias group to that gateway instead of using WAN [default] can't access/ping the given IP. Pfsense gives this IP to the clients as google.de next time as google.com sometimes for google.de/com and youtube.de/com. It's weird, because using dns lookup at pfsense itself shows this IP only for google.com.
Anyway if I disable the rule for opt1 users so that they use WAN, they can ping the 145.*
If I set either 8.8.8.8 or 8.8.4.4 on a PC/client as DNS instead of the firewall, the ping also is successful.I tried recreating the alias group that used this IP in the firewall and set it to pass but nothing of it worked. I don't even know why now it's rejecting for opt1 when the alias was originally for WAN. But that IP address was listed in that alias (I still checked the old .txt file yesterday on the FTP), so that's the reason I think this issue is/was caused by pfBlocker.
As I'm usually late updating the firewall (I barely find to for it as it can't be done during a working day, ofc) I run late into those problems. (Well, the pfsense was also still using DNS Forwarder instead of the new(?) DNS Resolver, but that had nothing to do with it, the issue remains on either service).
After your script I can't find anything else related to the previous pfBlocker but that IP that was on the alias list still gets rejected. I know this problem seems to not fit into the thread anymore, but I still hope you may have an idea what I could do about it, thanks.
-
Hi Melphiz,
You could also create a script to run on the pfSense box locally to collect those IPs.
You have to remember that pfBlockerNG doesn't block anything directly. All it does is collect IPs from the Threat Sources and creates Firewall Rules on the selected interfaces. All of the blocking/rejecting/permitting is done via pfSense Firewall Rules.
I believe that Google DNS is trying to re-route the Youtube blocking to other IPs. If you are using Unbound in 2.2, you should use it as a DNS Resolver (Not a forwarder), so it will use the Root DNS Servers for resolving DNS Requests. This will eliminate Google DNS from manipulating the DNS requests. There are other threads where you can get instructions on how to properly configure Unbound.
-
Hi,
I ran this check and the following remains:
<tab><text>General</text>
<url>/pkg_edit.php?xml=pfblocker.xml&id=0</url>
<active></active></tab>Thanks lt1360hp,
I made a fix to remove those xml tags also.
If anyone else runs the script, they can run the following command after running the removal script to ensure it removed all the the old reminents of the previous version of pfblocker.
grep "pfblocker" /conf/config.xml | grep -v "pfblockerng" -
Hi vronp,
That's fine. That is just telling you that the last active menu tab was pfBlocker. If you click another menu item in pfSense and re-run the grep command it should clear that.
-
I tried running the script below on a server running 2.2.2 (without the pfBlocker package as it is not available for 2.2.x) where the config had been restored from a server with 2.1.5 and the pfBlocker package on and it didn't work: the config still had the pfBlocker config in… Output at the bottom of this post:
Here is a script to remove the previous pfBlocker package from the pfSense config.xml
So please make a full backup before proceeding. Please post back if you were successful in removing the old remnants of this package…
Save this script to /usr/local/www/removepfb.php
then from your pfSense GUI
https://x.x.x.x:yyy/removepfb.php
(Change x.x.x.x to your pfsense box IP and yyy to the port setting used.)
It will report to the screen with its activity.
# Script to Remove pfBlocker from Config.xml # # by BBCan177@gmail.com # Copyright (c) 2015 require_once("pfsense-utils.inc"); require_once("config.inc"); require_once("services.inc"); global $config; print "``` "; print "Removing pfBlocker from the pfSense Configuration file\n\n"; $removal = array("pfblocker", "pfblockerlists", "pfblockerafrica", "pfblockerantartica", "pfblockerasia", "pfblockereurope", "pfblockernorthamerica", "pfblockeroceania", "pfblockersouthamerica", "pfblockertopspammers"); foreach ($removal as $remove){ if (is_array($config['installedpackages'][$remove])){ unset ($config['installedpackages'][$remove]); print "Removed {$remove}\n"; } } # Remove pfBlocker Menu Entry $pfb_menus = &$config['installedpackages']['menu']; if (!empty($pfb_menus)) { $key = 0; foreach ($pfb_menus as $menu) { if ($menu['name'] == "pfBlocker") { unset ($pfb_menus[$key]); print "Removed pfBlocker Menu Entry\n"; } $key++; } } # Remove pfBlocker Package Entry $pfb_pkg = &$config['installedpackages']['package']; if (!empty($pfb_pkg)) { $key = 0; foreach ($pfb_pkg as $pkg) { if ($pkg['name'] == "pfBlocker") { unset ($pfb_pkg[$key]); print "Removed pfBlocker Pkg Entry\n"; } $key++; } } # Remove Widget $pfb_widgets = $config['widgets']['sequence']; if (!empty($pfb_widgets)) { $widgetlist = explode(",", $pfb_widgets); foreach ($widgetlist as $key => $widget) { if (strstr($widget, "pfBlocker-container")) { unset($widgetlist[$key]); break; } } $config['widgets']['sequence'] = implode(",", $widgetlist); } #Remove any pfBlocker alias tables if (is_array($config['aliases']['alias'])){ foreach($config['aliases']['alias'] as $alias){ if (!preg_match("/^pfBlocker/", $alias['name'])) { $new_aliases[]= $alias; } } $config['aliases']['alias'] = $new_aliases; } # Remove pfBlocker Files/Folders unlink_if_exists ("/usr/local/pkg/pfblocker.inc"); unlink_if_exists ("/usr/local/pkg/pfblocker.xml"); unlink_if_exists ("/usr/local/pkg/pfblocker_Africa.xml"); unlink_if_exists ("/usr/local/pkg/pfblocker_Asia.xml"); unlink_if_exists ("/usr/local/pkg/pfblocker_Europe.xml"); unlink_if_exists ("/usr/local/pkg/pfblocker_NorthAmerica.xml"); unlink_if_exists ("/usr/local/pkg/pfblocker_Oceania.xml"); unlink_if_exists ("/usr/local/pkg/pfblocker_SouthAmerica.xml"); unlink_if_exists ("/usr/local/pkg/pfblocker_lists.xml"); unlink_if_exists ("/usr/local/pkg/pfblocker_sync.xml"); unlink_if_exists ("/usr/local/pkg/pfblocker_topspammers.xml"); unlink_if_exists ("/usr/local/www/pfblocker.php"); unlink_if_exists ("/usr/local/www/widgets/widgets/pfBlocker.widget.php"); unlink_if_exists ("/usr/local/pkg/Africa_cidr.txt"); unlink_if_exists ("/usr/local/pkg/Asia_cidr.txt"); unlink_if_exists ("/usr/local/pkg/Europe_cidr.txt"); unlink_if_exists ("/usr/local/pkg/Oceania_cidr.txt"); unlink_if_exists ("/usr/local/pkg/South_America_cidr.txt"); rmdir_recursive ("/usr/local/pkg/pfblocker"); rmdir_recursive ("/usr/local/pkg/pfblocker_aliases"); exec ("/bin/rm /var/db/aliastables/pfBlocker*.*"); # Remove Cron Task install_cron_job("pfblocker.php cron", false); # Save Configuration write_config("Removed pfBlocker"); ?>The output for me was:
Removing pfBlocker from the pfSense Configuration file Removed pfblocker Removed pfblockerlists Removed pfblockertopspammers Removed pfBlocker Menu Entry Fatal error: Call to undefined function getUserEntry() in /etc/inc/config.lib.inc on line 501Should I just remove the config manually using the nested grep example BBcan177 gave?
grep "pfblocker" /conf/config.xml | grep -v "pfblockerng" -
P.S. The script removed nothing as far as I could tell: the pfBlocker rules were still present and the menu entry was still present.
-
It won't remove the rules but it should remove the menu entry. Is this a full install version of pfSense. Might need to put the system into RW mode to save the changes if it's a nano/flash type version.
-
greping the config file still shows 'pfblockersync'. Should that be there?
-
greping the config file still shows 'pfblockersync'. Should that be there?
Thanks for pointing that out. I can't edit my original post, but please edit the script to include "pfblockersync" as follows:
Original
$removal = array("pfblocker", "pfblockerlists", "pfblockerafrica", "pfblockerantartica", "pfblockerasia", "pfblockereurope", "pfblockernorthamerica", "pfblockeroceania", "pfblockersouthamerica", "pfblockertopspammers");
New
$removal = array("pfblocker", "pfblockerlists", "pfblockerafrica", "pfblockerantartica", "pfblockerasia", "pfblockereurope", "pfblockernorthamerica", "pfblockeroceania", "pfblockersouthamerica", "pfblockertopspammers", "pfblockersync");
-
script saved me. upgraded from 2.2.4 to 2.3.1 and pfblocker broke. Tried remove and reinstall no go. was able to get to router but not out to internet. ran script, rebooted, and all my problems are gone. Thanks!
-
Just tried running this - after copying the script to my pfsense VM.
I ran the script from Chrome and it just outputs 'Removing pfBlocker from the pfSense Configuration file'
Where exactly am I executing the script from?
Thanks
-
The script is outdated.
