Country Block
-
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.shNow 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… ;)
-
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. -
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
-
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.
-
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?
-
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. -
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 starting1.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...
:)
-
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 starting1.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. -
Version 1.7 is available.
Changes:
-
Complete UI overhaul
-
Changed execution process
Hopefully these changes will help those people that are having trouble keeping the package running.
To upgrade Uninstall Countryblock, reboot, and then install the newest version.
-
-
thank you for the update. we are lucky to have you working on this package.
0.1.6 would not stay running.
0.1.7 has been up approx an hour without a problem…
one question - i enabled logging. do I need to setup log rotation ?
-
I have never seen updates come this fast…....;)
-
thank you for the update. we are lucky to have you working on this package.
0.1.6 would not stay running.
0.1.7 has been up approx an hour without a problem…
one question - i enabled logging. do I need to setup log rotation ?
Thank you. I hope it keeps running.
As far as log rotation goes: unless you are blocking a huge amount of networks and need to keep track of a couple days worth then no. Blocking a couple countries may increase your log size significantly depending on your networks, however. It's really Dependant on how many entries are being produced and how much you need to keep track of.Thank you Supermule :) I got off work early today and I wanted to fix this problem that some people were having with the last update.
-
I dont have traffic shaping running
Packages are
Country Block
Cron
DarkStat
nmap
snortI will give the updated version a try and see if that resolves it.
Thanks so much for your support and quick updates on this package. :-)
-
After a few hours CB is still running.
Here is one thing to check:
when I click 'Country Block' under 'Firewall' section in Pfsense the 'Enable Country Block' is 'on'
when I add countries, the 'Enable Country Block' is unchecked or 'off' at the top of the screen.
so for now if you add/change countries , reclick the 'Enable Country Block'CB for us is working a lot better.
-
Version 1.7 is available.
Changes:
-
Complete UI overhaul
-
Changed execution process
Hopefully these changes will help those people that are having trouble keeping the package running.
To upgrade Uninstall Countryblock, reboot, and then install the newest version.
Outstanding. Like the new UI and cron is still tickin'. Thanks!
-
-
Well so far so good. It has been running for 3 hours now and its still up and not stopped. :-) So your changes seem to have corrected the issue. Thanks!
The only thing that doesnt seem to be automatic is if I change the firewall states with another package or clear it ect in settings which resets the current table which kills country block (as its mentioned in the package that it will), it doesn't seem like country block will start on its own with the cron job entry. When I make the changes mentioned, I will let it sit there for 10 minutes and it will not start back up. Once I start it manually it seems to stay running. So I am unclear why it will not start back up. I guess as long as I know I make changes and check to start it back up it should stay up and running without issue i suppose.
I do have this cron entry
minute: 0
hour: *
mday: *
month: *
wday: *
who: root
command: /usr/local/etc/rc.d/countryblock.sh -
Well so far so good. It has been running for 3 hours now and its still up and not stopped. :-) So your changes seem to have corrected the issue. Thanks!
The only thing that doesnt seem to be automatic is if I change the firewall states with another package or clear it ect in settings which resets the current table which kills country block (as its mentioned in the package that it will), it doesn't seem like country block will start on its own with the cron job entry. When I make the changes mentioned, I will let it sit there for 10 minutes and it will not start back up. Once I start it manually it seems to stay running. So I am unclear why it will not start back up. I guess as long as I know I make changes and check to start it back up it should stay up and running without issue i suppose.
I do have this cron entry
minute: 0
hour: *
mday: *
month: *
wday: *
who: root
command: /usr/local/etc/rc.d/countryblock.shfor every 5 min use
Minute: */5*/2 # every 2 min etc.
-
Well so far so good. It has been running for 3 hours now and its still up and not stopped. :-) So your changes seem to have corrected the issue. Thanks!
The only thing that doesnt seem to be automatic is if I change the firewall states with another package or clear it ect in settings which resets the current table which kills country block (as its mentioned in the package that it will), it doesn't seem like country block will start on its own with the cron job entry. When I make the changes mentioned, I will let it sit there for 10 minutes and it will not start back up. Once I start it manually it seems to stay running. So I am unclear why it will not start back up. I guess as long as I know I make changes and check to start it back up it should stay up and running without issue i suppose.
I do have this cron entry
minute: 0
hour: *
mday: *
month: *
wday: *
who: root
command: /usr/local/etc/rc.d/countryblock.shfor every 5 min use
Minute: */5*/2 # every 2 min etc.
I changed the 0 to */1 and then reset the states and it killed country block and waited a minute and it started back up. That seemed to do the trick. Thanks alot.
I -
Glad to know I was not crazy, well to some degree. Tommy, thanks for looking into this. I love this package, I really feel you have developed something that should be a standard option in most firewalls but is not.
Thanks for the quick replies and fast updates. Hands down to you…
Thanks again,
Matt
-
Nice new interface tommy appreciate it.
Gotta question for you though, i see that there are a few packages related to dns (country block,dns blacklist), is it possible to get something like OpenDNS but locally? mostly the custom shortcuts andstats (top domains etc)? if so how hard would it be?
