Re: General MoBlock thread
Although I can't imagine what is going wrong, perhaps a "sudo blockcontrol force-update" helps. This will delete all currently downloaded blocklists and start from scratch again.
Another possibility might be that you had too many downloads from iblocklist.com, and were therefore banned temporarily (although this never happened to me, even when I made many downloads while working on the blocklist download code).
Re: General MoBlock thread
it appears to be downloading the files as i've been to /var/spool/blockcontrol/Bluetack_level1/ had a look in the download folder and there is a file in there that just cannot be extracted - which would go with the CRC error that moblocker is giving me.
The owner of the folder above is OWNER and changing the folder permissions to my user name have no effect.
Ill give it another go on one of the machines at work tomorrow and see if i can get it to work there
Re: General MoBlock thread
I've just tested it at work and for some reason it works just fine - I'm going to reload my pc at home tonight and see what's what.... still odd though.
Re: General MoBlock thread
Re-installed Ubuntu and installed MoBlock then as if by magic it works - cheers jre
Re: General MoBlock thread
Glad to hear. Although I think that was a bit overkill ;-)
I guess you were just unlucky and somehow got a coorupted list. The maintainer of iblocklist.com thinks it might be, that you just downlaoded the list from the server, while a new one was uploaded. So probably the "blockcontrol force-update" would have worked.
Have fun!
Re: General MoBlock thread
My install of moblock 0.9rc2 (compiled OK from source, and installed OK; I can run 'moblock' from the terminal and get its usage options) and blockcontrol 1.6.12 is refusing to start on Ubuntu 10.04.1 (PPC).
Looking at blockcontrol.log, I just see:
Code:
2010-09-11 21:49:05 IST End: blockcontrol force-update
2010-09-11 21:50:01 IST Begin: blockcontrol start
Building blocklist... ...done.
* Warning: Could not load kernel module xt_iprange, continuing anyway.
* Whitelisting IP ranges with the allow list will not work.
* The allow list is in /etc/blockcontrol/allow.p2p.
Inserting iptables ...
iptables: Chain already exists.
...fail!
...fail!
And nothing else. Is there a way for me to see what's causing the "...fail!" messages? Syslog isn't showing anything.
Re: General MoBlock thread
The log says that blockcontrol can't insert the necessary iptables rules/chains because they were already inserted previously. You can remove them by issuing a "blockcontrol stop". Verify that they are removed with a "blockcontrol status" - in that output you should see no reference to "blockcontrol" at all. Then try a "blockcontrol start" again.
After solving that problem I guess you will still experience another problem, which is the original reason for the error message you just got.
Do you use a custom built kernel? (I guess so because of the warning message about xt_iprange. Please note that this is eally just a warning, but does not prevent moblock from working. But it still indicates something special about your system). Make sure that you enable (as modules) the necessary netfilter support. See the README for details.
Why did you compile your own version? I recommend to just install from moblock-deb.sourceforge.net. See also the guide at https://help.ubuntu.com/community/MoBlock
Where did you get your sources from? The original moblock source from berlios.de needs patching in order to work. Even if you want to compile on your own, I recommend to use the source from moblock-deb.sf.net
Re: General MoBlock thread
I built the package using the instructions from moblock-deb (I'm running on PPC, and there doesn't seem to be a package available in apt), ran blockcontrol stop, then start, then status, and now it's fine. I didn't even get the warning about the missing kernel module. Odd, but it's running, and I'm seeing hits in the log.
Re: General MoBlock thread
Indeed I don't offer PPC packages, but you just made everything right. So great to hear that it works on PPC. Just strange that you had those problems in the beginning.