IP-Blocklist

Take a look at lines 32-38 in convert-execute.sh. This is where the ipfw.ipfw file is created.
If those commands don't work then the package cannot use the lists that you are using.

One thing you need to verify is that your lists are in fact working. For example do they get download to lists/ and do the file inside lists/ have data?
Another way you can find out what is broken is to step though convert-execute.sh and see what it's hanging on.

I've done so many hours of testing this package on different platforms that I'm very confident it could be a misconfiguration or a list isn't working at it should be. Another thing is that embedded installs are prone to problems with this package.

Let me know, I would be more than happy to do a full in-depth analysis review of your system to see what the issue is.

root2020

Do you have to manually apply updated filters or does IP-Blocklist automatically refresh the list?

For example if I load a list from a site called www.sitelist.com/block.gz, will IP-Blocklist refresh everyday to get the lasted additions to this list?

tommyboy180

@root2020:

Do you have to manually apply updated filters or does IP-Blocklist automatically refresh the list?

For example if I load a list from a site called www.sitelist.com/block.gz, will IP-Blocklist refresh everyday to get the lasted additions to this list?

The package will re-download the list every time it's applied. Without any modifications this could be every 5 minutes or once a day, this is because Ipblockist is re-applied on filter reload. Now if you need to make sure it's being downloaded every day then install a cron job.

I think it's safe to say that your package is re-applying the list every day or at least every other day.

pathia

Not really sure where I could get the logs to show what's going on. The situation is this.

IP-Blocklist works fine, but after a few hours, the whitelist is forgotten and it ignores it entirely. If I login to the router and hit "Save/Update", it'll start using the whitelist again. Obviously this isn't ideal. Any idea what I could do to figure out why it stops using it? I can't find any messages indicating that the whitelist isn't found, it's stored on the same server the blocklist is coming from…

root2020

I removed the IP-Blocklist and I get this error every time I reload the firewall filter. Is there anyway to manually remove it using the command-line? FYI, I also get this same error when I just disable the IP-Blocklist. :'(

Thanks,

Rhett

System Logs:
php: : The command '/usr/local/pkg/pf/IP-Blocklist.sh start' returned exit code '1', the output was 'not running root: IP-Blocklist was found not running Status: 404 Not Found Content-type: text/html No input file specified. 0 table deleted. 0 table deleted. ls: /usr/local/www/packages/ipblocklist/lists: No such file or directory rm: /usr/local/www/packages/ipblocklist/lists/ipfw.ipfwTEMP: No such file or directory /usr/local/pkg/pf/IP-Blocklist.sh: cannot create /usr/local/www/packages/ipblocklist/lists/ipfw.ipfwTEMP: No such file or directory /usr/bin/sort: open failed: /usr/local/www/packages/ipblocklist/lists/ipfw.ipfw: No such file or directory mv: rename /usr/local/www/packages/ipblocklist/lists/ipfw.ipfwTEMP to /usr/local/www/packages/ipblocklist/lists/ipfw.ipfw: No such file or directory rm: /usr/local/www/packages/ipblocklist/Wlists/whitelistTEMP: No such file or directory /usr/bin/sort: open failed: Wlists/whitelist: No such file or directory rm: /tmp/rules.debug.tmp: No such fi

tommyboy180

@root2020:

I removed the IP-Blocklist and I get this error every time I reload the firewall filter. Is there anyway to manually remove it using the command-line? FYI, I also get this same error when I just disable the IP-Blocklist. :'(

Thanks,

Rhett

System Logs:
php: : The command '/usr/local/pkg/pf/IP-Blocklist.sh start' returned exit code '1', the output was 'not running root: IP-Blocklist was found not running Status: 404 Not Found Content-type: text/html No input file specified. 0 table deleted. 0 table deleted. ls: /usr/local/www/packages/ipblocklist/lists: No such file or directory rm: /usr/local/www/packages/ipblocklist/lists/ipfw.ipfwTEMP: No such file or directory /usr/local/pkg/pf/IP-Blocklist.sh: cannot create /usr/local/www/packages/ipblocklist/lists/ipfw.ipfwTEMP: No such file or directory /usr/bin/sort: open failed: /usr/local/www/packages/ipblocklist/lists/ipfw.ipfw: No such file or directory mv: rename /usr/local/www/packages/ipblocklist/lists/ipfw.ipfwTEMP to /usr/local/www/packages/ipblocklist/lists/ipfw.ipfw: No such file or directory rm: /usr/local/www/packages/ipblocklist/Wlists/whitelistTEMP: No such file or directory /usr/bin/sort: open failed: Wlists/whitelist: No such file or directory rm: /tmp/rules.debug.tmp: No such fi

try rm -R /usr/local/www/packages/ipblocklist
Remove the xml and inc file from /usr/local/pkg
Also see if the start script is in /usr/local/rc.d

root2020

Thank you for the information.

I deleted a file and things are working good again.
Looks like you need to have your uninstaller delete the following file:
/usr/local/pkg/pf/IP-Blocklist.sh

tommyboy180

@root2020:

Thank you for the information.

I deleted a file and things are working good again.
Looks like you need to have your uninstaller delete the following file:
/usr/local/pkg/pf/IP-Blocklist.sh

Thank you. I will update that!

jikjik101

@tommyboy180:

try rm -R /usr/local/www/packages/ipblocklist
Remove the xml and inc file from /usr/local/pkg
Also see if the start script is in /usr/local/rc.d

How to remove the xml and inc files using the webGUI? Also, I'm using windows and experience root2020's problem. TIA

root2020

The uninstaller seems to remove those two files. Do an uninstall via the GUI and then just remove the "/usr/local/pkg/pf/IP-Blocklist.sh"

Goto > Diagnotics > Command Line and type in the following
rm /usr/local/pkg/pf/IP-Blocklist.sh

jikjik101

tnx. no more error on the syslog with ipblock… however, i have tx underrun. need to search the forum about that one.
Thanks again. ;)

mikesamo

Hello,

samething with countryblock.sh

Thanks,

MrEmbedded

@tommyboy180:

@Systex:

@tommyboy180:

@Systex:

I'm running an embedded install of 2.0Beta5 and tried to make the changes listed in this thread in order to get it to work. However, I accidentally forgot a semicolon after the first line I added (require_once('config.inc')) and when I went to refresh the IP-Blocklist page I got the following error in the textbox:

Parse error: syntax error, unexpected T_ECHO in /usr/local/www/packages/ipblocklist/ipblocklist_list.php on line 5

Since then, I've tried everything I can to get back to a cleanly-installed state: I've undone the edits I made to that file, and I've even uninstalled and reinstalled the IP-Blacklist package, but whatever I do, I now always get that error. How can I get back to a clean slate without completely reinstalling pfsense?

My best advice is to uninstall the package, check the file system (/usr/local/www/ipblocklist) and delete it, and then reboot. That should help you start from a clean slate.

Hmm, after uninstalling I looked in /usr/local/www/ and there was no file or directory ipblocklist. I then rebooted, and reinstalled the package. Same exact error as before. The strange thing, is that if I look at the file /usr/local/www/packages/ipblocklist/ipblocklist_list.php, it's the stock, unmodified form (i.e., correct syntax)!? I'm very confused as to what's going on.

Sorry. The directory is /usr/local/www/packages/ipblocklist/
Uninstall and check to make sure that it's deleted.
Try executing the .sh manually in your console if you get the same error again.

I can add to this. I was having the same issue with a mistype such that on the main tab there was a similar error message to Systex. An uninstall-manual flush/reinstall did nothing. I did not reboot however. What I have realized is that everything is fine but the message was stale and showing in the frame and this never refreshed. I right clicked on the frame and manually reloaded the frame where the error message was and this fixed everything for me as far as the display and the error message is concerned.