General MoBlock thread

**jre** · July 29th, 2009

I don´t know why anything should get slower. Either MoBlock blocks a connection completely, or it allows it, but nothing between.
Anyway, to see the blocked packets of MoBlock have a look at /var/log/moblock.log. You can then allow traffic for either some IPs or ports. Have a look at https://help.ubuntu.com/community/MoBlock

**peacewithall** · July 30th, 2009

For anyone experiencing problems with moblock, and also having firestarter installed, I found a solution which helps me. I searched this thread and found no real solution, apart from starting moblock after firewall applications.

The solution is here,
http://henry.sage-vision.com/blog/

Basically it restarts moblock after each start of firestarter.

Edit firestarter.sh:

Code:

sudo gedit /etc/firestarter/firestarter.sh

Find the section:

Code:

# Start the firewall, enforcing traffic policy
start_firewall () {
lock_firestarter
source /etc/firestarter/firewall 2>&1
retval=$?
if [ $retval -eq 0 ]; then
echo “Firewall started”
else
echo “Firewall not started”
unlock_firestarter
exit $retval
fi
}

Paste this over that section:

Code:

# Start the firewall, enforcing traffic policy
start_firewall () {
lock_firestarter
source /etc/firestarter/firewall 2>&1
retval=$?
if [ $retval -eq 0 ]; then
echo “Firewall started”
if [ -x /etc/init.d/blockcontrol ]; then
/etc/init.d/blockcontrol restart
fi
else
echo “Firewall not started”
unlock_firestarter
exit $retval
fi
}

Click SAVE,

DONE.

So all I did was add this to that section (DO NOT add this, its just an example of what was added above), also this can be removed to reverse the changes applied above.

Code:

if [ -x /etc/init.d/blockcontrol ]; then
/etc/init.d/blockcontrol restart
fi

Hope this tip helps others too.

**jre** · July 31st, 2009

Quite good, just one remark though:

Originally Posted by peacewithall

Code:

if [ -x /etc/init.d/blockcontrol ]; then
/etc/init.d/blockcontrol restart
fi

Use this instead:

Code:

if [ -x /usr/bin/blockcontrol ] && [ "$(blockcontrol status)" = 0 ]; then
  blockcontrol restart
fi

First I take blockcontrol directly - not the init script, which is based on blockcontrol.

More important, I first check if blockcontrol is actually running with "status". So this allows to turn off blockcontrol manually, while with your solution it is always (re-)started by firestarter.

**Jerriy** · August 8th, 2009

Hi there - I have a question. I recently upgraded to Jaunty and (I suspect as a result of that) I get this message scrolling on the screen during boot:

Code:

* Moblock is not running

Doesn't that mean that Blockcontrol is not starting automatically at system boot (which it should per default)?

**jre** · August 9th, 2009

Yes, it should. INIT="1" must be set (check "blockcontrol show_config | grep INIT" for that. Then check /var/log/blockcontrol.log if the start was attempted (perhaps moblock crashed later).
Also check if "sudo blockcontrol start" works.

**Mariane** · August 9th, 2009

Hi,

There are just 2 ip I wish o block
(google syndication and google analytics, which serve the adds and generate all the "addsense" trash, and doubleclick.net which won the big-brother award).

Google syndication is 64.233.161.99
doubleclick.net is 216.73.93.8

So I have a custom file
/etc/blockcontrol/custom-blocklist.p2p

Where I wrote

Code:

64.233.161.99-64.233.161.99
216.73.93.8-216.73.93.8

Mobloquer - Blocklists shows this file and it is set to enabled and local. I removed the others.

Mobloquer - Manage says "Moblock is up and running" but below it says "Number of blocked ip ranges: 0"

And I know it is not working because even on this forum I get the browser message that stuff is transfered between my computer and google-analytics

.

What should I do, please?

Mariane

**Jerriy** · August 9th, 2009

Originally Posted by jre

Yes, it should. INIT="1" must be set (check "blockcontrol show_config | grep INIT" for that. Then check /var/log/blockcontrol.log if the start was attempted (perhaps moblock crashed later).
Also check if "sudo blockcontrol start" works.

To me it all seems strange - it seems to work but at the same time it seems to START by not working... then it starts, as you can see it in the log (the greyed out bit at the end is refering to what happened after I followed your instructions in your previous post):

Code:

2009-08-09 18:47:11 CEST Begin: blockcontrol stop
Stopping blockcontrol.watchdog.
Deleting iptables ...

[74G[ OK ]
Executing /etc/blockcontrol/iptables-custom-remove.sh ...
[74G[ OK ]
Stopping moblock ...
[74G[ OK ]
2009-08-09 18:47:12 CEST End: blockcontrol stop
2009-08-09 18:48:08 CEST Begin: blockcontrol start
Inserting iptables ...
Allowing loopback traffic
[74G[ OK ]

[74G[ OK ]
Executing /etc/blockcontrol/iptables-custom-insert.sh ...
[74G[ OK ]
Starting moblock ...
[74G[ OK ]
Starting blockcontrol.watchdog
[74G[ OK ]
2009-08-09 18:48:09 CEST End: blockcontrol start
Allowing inbound LAN traffic for ###.###.#.## with subnetmask ###.###.###.#   ...done.
Allowing outbound LAN traffic for ###.###.#.## with subnetmask ###.###.###.#   ...done.
Allowing forwarded LAN traffic for ###.###.#.## with subnetmask ###.###.###.#   ...done.
Allowing outbound traffic to DNS server ###.###.#.#   ...done.
Allowing forwarded traffic to DNS server ###.###.#.#   ...done.
2009-08-09 18:57:10 CEST Begin: blockcontrol stop
Stopping blockcontrol.watchdog.
Deleting iptables ...

[74G[ OK ]
Executing /etc/blockcontrol/iptables-custom-remove.sh ...
[74G[ OK ]
Stopping moblock ...
[74G[ OK ]
2009-08-09 18:57:11 CEST End: blockcontrol stop
2009-08-09 18:58:07 CEST Begin: blockcontrol start
Inserting iptables ...
Allowing loopback traffic
[74G[ OK ]

[74G[ OK ]
Executing /etc/blockcontrol/iptables-custom-insert.sh ...
[74G[ OK ]
Starting moblock ...
[74G[ OK ]
Starting blockcontrol.watchdog
[74G[ OK ]
2009-08-09 18:58:07 CEST End: blockcontrol start
Allowing inbound LAN traffic for ###.###.#.## with subnetmask ###.###.###.#   ...done.
Allowing outbound LAN traffic for ###.###.#.## with subnetmask ###.###.###.#   ...done.
Allowing forwarded LAN traffic for ###.###.#.## with subnetmask ###.###.###.#   ...done.
Allowing outbound traffic to DNS server ###.###.#.#   ...done.
Allowing forwarded traffic to DNS server ###.###.#.#   ...done.
2009-08-09 08:23:28 PM CEST Begin: blockcontrol start
 * moblock is already running, doing nothing.
2009-08-09 08:23:28 PM CEST End: blockcontrol start

**cvaty** · August 12th, 2009

Hi,

There are just 2 ip I wish o block
(google syndication and google analytics, which serve the adds and generate all the "addsense" trash, and doubleclick.net which won the big-brother award).

Google syndication is 64.233.161.99
doubleclick.net is 216.73.93.8

since most likely youve whitelisted http traffic adding these to moblock wont prevent your computer from communicating with port 80 (your browser)

you can use the /etc/hosts file however to ignore them

Code:

sudo gedit /etc/hosts

Code:

127.0.0.1 64.233.161.99  # bloccks google-syndication
127.0.1.1 216.73.93.8    # blocks double-click.net

you might find this site of interest
http://someonewhocares.org/hosts/

**jre** · August 12th, 2009

Originally Posted by Mariane

So I have a custom file
/etc/blockcontrol/custom-blocklist.p2p

Where I wrote

Code:

64.233.161.99-64.233.161.99
216.73.93.8-216.73.93.8

You need a description, otherwise it´s incorrect syntax:

Code:

google-syndication:64.233.161.99-64.233.161.99
double-click.net:216.73.93.8-216.73.93.8

But also have a look at cvaty´s post!

@Jerriy: Indeed everything seems to be ok.
I can´t find what´s going wrong. This ought to be the output of the function "status_of_proc". But I just verified that this output should normally not be not shown, because I have "> /dev/null 2>&1".
Still there are some exceptions, but then you should see a message before "Problematic daemon status:".

Anyway, please send me your /lib/lsb/init-functions.
Then try it with the setting LSB="" in /etc/blockcontrol/blockcontrol.conf
I´ll add this to BUGS, for the time being. Please tell me, if this problems gets solved somehow.

**Murimons** · August 21st, 2009

Hello,

I've got a small issue with my moblock.
I'm using Ubuntu 9.04 and i've just started using it a little bit and don't have much linux knowledge.

i edited the moblock.conf file and added some IP adresses to allow OUT.
It worked the whole time but now it blocks a IP that should not be blocked.
I've changed nothing to the moblock.conf.

When i check /etc/init.d/blockcontrol .status, i don't see the allowed IP in there.
So apearently the .conf file allowed IPdoesn't get imported to the iptables or something.
Although some protocols i allowed in the .conf file ARE working and are also listed in the status.

Any idea how i can solve this?

Thanks!

Thread: General MoBlock thread

Thread Tools

Display

Re: General MoBlock thread

Re: General MoBlock thread

Re: General MoBlock thread

Re: General MoBlock thread

Re: General MoBlock thread

Re: General MoBlock thread

Re: General MoBlock thread

Re: General MoBlock thread

Re: General MoBlock thread

Re: General MoBlock thread

Bookmarks

Bookmarks

Posting Permissions