Country Block

tommyboy180 · Sep 30, 2010, 10:07 AM

Just an idea…..

Why not sort the countries in their respective part of the world instead?

Like Europe, North America, South America, Asia asf....The 7 continents. Thereby making it a lot easier to search and block.

Thank you for the suggestion! Alphabetically is the most efficient way to sort a huge list, it's sort of a defacto standardization that I think everyone has become accustomed to. It's also easier to maintain a large list like this in this order. I will note this for a future release.
Keep the suggestions coming!

jward · Sep 30, 2010, 11:37 AM

Hi Tommy,

I've got some ideas for the UI and process flow that might help - let me know if you're interested and I'll put some mock-up screens together.

Jon.

tommyboy180 · Sep 30, 2010, 12:55 PM

@jward:

Hi Tommy,

I've got some ideas for the UI and process flow that might help - let me know if you're interested and I'll put some mock-up screens together.

Jon.

I am very interested, let's see what you have in mind.

NoahVail · Sep 30, 2010, 1:10 PM

mgc6288

uninstall countryblock completely and re-install

That fixed it for me.
Thanks.
NV

mgc6288 · Sep 30, 2010, 3:01 PM

@tommyboy180:

Version 1.6 is now available!

Changes:

All interfaces are selected/applied by default (no action required by users)

Modified Usage description to be more verbose

To upgrade uninstall countryblock and re-install.

thanks for the patience. Duh, I should have realized maybe uninstalling should have been done first. Works like a charm now.

darklogic · Oct 1, 2010, 12:27 PM

Just an FYI. Since version 1.5 I have been having trouble with keeping Country Block running. I am running cron and have not made any changes to firewall rules. I uninstall the package numerous times and restarted the system. I can get CountryBlock to start ok, but it will only run for a few hours and then shut down. I have also uninstalled and reinstalled cron.

Is anybody else getting this? I noticed started happeing when I install 1.5 and now 1.6.

Thanks,

Supermule · Oct 1, 2010, 12:43 PM

Not reporting anything of that kind :)

tommyboy180 · Oct 1, 2010, 1:08 PM

@darklogic:

Just an FYI. Since version 1.5 I have been having trouble with keeping Country Block running. I am running cron and have not made any changes to firewall rules. I uninstall the package numerous times and restarted the system. I can get CountryBlock to start ok, but it will only run for a few hours and then shut down. I have also uninstalled and reinstalled cron.

Is anybody else getting this? I noticed started happeing when I install 1.5 and now 1.6.

Thanks,

The only real difference between 1.5 and 1.6 is a new file is included. The file is interfaces.txt and it contains "any" by default.
The difference between 1.4 and 1.5 is the interfaces can be specified.
Nothing has changed with how the package is run or how it starts.

Are you getting any errors?

darklogic · Oct 1, 2010, 2:18 PM

no errors, that is why it is odd. It will start just fine and then shut down for no reason. I will try to uninstall and reboot and reinstall again and see if that helps. I have tried this a few times now. I will try again,

Thanks,

mgc6288 · Oct 1, 2010, 2:44 PM

@darklogic:

Just an FYI. Since version 1.5 I have been having trouble with keeping Country Block running. I am running cron and have not made any changes to firewall rules. I uninstall the package numerous times and restarted the system. I can get CountryBlock to start ok, but it will only run for a few hours and then shut down. I have also uninstalled and reinstalled cron.

Is anybody else getting this? I noticed started happeing when I install 1.5 and now 1.6.

Thanks,

I've been having the same issue. I removed countryblock from cron and now it runs…I just check every once in a while. What I did is after I installed the Cron package, I created an auto start like this:

minute: 0
hour: *
mday: *
month: *
wday: *
who: root
command: /usr/local/etc/rc.d/countryblock.sh

Now 1.6 (can't confirm 1.5 as the update was too quick) will say "NOT running" after a while...

chpalmer · Oct 1, 2010, 5:05 PM

@mgc6288:

I've been having the same issue. I removed countryblock from cron and now it runs…I just check every once in a while. What I did is after I installed the Cron package, I created an auto start like this:

minute: 0
hour: *
mday: *
month: *
wday: *
who: root
command: /usr/local/etc/rc.d/countryblock.sh

Now 1.6 (can't confirm 1.5 as the update was too quick) will say "NOT running" after a while...

Ditto and 1.5 did this to me also… ;)

tommyboy180 · Oct 1, 2010, 9:31 PM

I'm glad you figured it out.
I don't run a cron job but my countryblock (v1.6) has been running for me two days in a row now without issues.

robfantini · Oct 2, 2010, 1:46 AM

We are using Pfsense 1.2.3-RELEASE and CountryBlock 1.6

I can not keep CountryBlock running.

I have cron set to run the script every 5 min.

We also use squid and squidGuard. Are those packages ok to run with CountryBlock?

PS: Thanks for this package . I can see that it will

tommyboy180 · Oct 2, 2010, 2:06 AM

@robfantini:

We are using Pfsense 1.2.3-RELEASE and CountryBlock 1.6

I can not keep CountryBlock running.

I have cron set to run the script every 5 min.

We also use squid and squidGuard. Are those packages ok to run with CountryBlock?

PS: Thanks for this package . I can see that it will

Can you PM me your config. I will be home early tonight and will be able to take a look at it.

kilthro · Oct 2, 2010, 3:09 AM

I just updated to your latest version and I am having the same issue. It will stop running after a bit and then I have to manually start it. I added the cron job like a couple a posts above ( was running that cron setting before with no issue) and it still will not stay running.

I dont know if Snort is updating the FW rules/states and then cron isnt properly re-enabling country block after the change. Over the past week it has been working just fine. Just all this after the update version 1.6. I was running 1.4 prior.

I am on the latest 2.0 beta build that has been posted.

Is there anything you need from me that may assist with isolating the issue?

tommyboy180 · Oct 2, 2010, 4:16 AM

@kilthro:

I just updated to your latest version and I am having the same issue. It will stop running after a bit and then I have to manually start it. I added the cron job like a couple a posts above ( was running that cron setting before with no issue) and it still will not stay running.

I dont know if Snort is updating the FW rules/states and then cron isnt properly re-enabling country block after the change. Over the past week it has been working just fine. Just all this after the update version 1.6. I was running 1.4 prior.

I am on the latest 2.0 beta build that has been posted.

Is there anything you need from me that may assist with isolating the issue?

List of packages installed please. Also do you have traffic shaping running?
I need to figure this out. I'm home now so I can work on this for the next couple of hours.

chpalmer · Oct 2, 2010, 5:09 AM

Just came home and Country Block is not running…

Have this in my logs.

Last 50 system log entries
Oct 1 10:14:12 syslogd: kernel boot file is /boot/kernel/kernel
Oct 1 17:28:47 root: rc.update_bogons.sh is beginning the update cycle.
Oct 1 17:28:49 root: Bogons file downloaded: no changes.
Oct 1 18:10:00 check_reload_status: check_reload_status is starting

1.2.3R with only Country Block and Cron installed as packages.

I use dynamic dns.

I have a vip for a static IP I have.

Im on cable.

If I think of anything else Ill add it later...

:)

tommyboy180 · Oct 2, 2010, 5:43 AM

@chpalmer:

Just came home and Country Block is not running…

Have this in my logs.

Last 50 system log entries
Oct 1 10:14:12 syslogd: kernel boot file is /boot/kernel/kernel
Oct 1 17:28:47 root: rc.update_bogons.sh is beginning the update cycle.
Oct 1 17:28:49 root: Bogons file downloaded: no changes.
Oct 1 18:10:00 check_reload_status: check_reload_status is starting

1.2.3R with only Country Block and Cron installed as packages.

I use dynamic dns.

I have a vip for a static IP I have.

Im on cable.

If I think of anything else Ill add it later...

:)

Edit:
When the Bogons update cron job is run the firewall settings get re-applied and that is why countryblock was stopped. To counter this you can have countryblock run after this.
This may be why everyone is having difficulty with keeping the package running, a cron job is running that affects the firewall thus killing countryblock.