Moblock (peerguardian linux alternative)

[Mechanical]

I have a question about updating. First of all, I was using the list pelle.k had made and included up until now in the manual. Now we have discovered another way to update the lists, yet in 'sudo nano /etc/cron.daily/moblock-nfq' there doesn't seem to be a mention for a p2p file. There is the ad blocking and bad porn stuff, but I am usually used to seeing a p2p file which I figured was the most important part of blocking out the baddies. Just wondering, and hope to see more of the gui soon, thanks.

[clessing]

There is the ad blocking and bad porn stuff, but I am usually used to seeing a p2p file which I figured was the most important part of blocking out the baddies. Just wondering, and hope to see more of the gui soon, thanks.

Please see http://www.bluetack.co.uk/forums/ind...CODE=02&qid=18 and
http://www.bluetack.co.uk/config/
and especially http://www.bluetack.co.uk/modules.ph...Blacklists+FAQ

Especially level1 and level2 are anti p2p.

If you think that there is a list that should be included per default in the moblock package or if any of you has improvements for scripts in this package, feel free to contact me.

I know that I have to spend time and work on them but at the moment time is a problem...

[clessing]

I'm having a similar issue. Nothing is being blocked.
I am running Dapper Drake

ottoaim@jesse:~$ tail -f /var/log/moblock.log
NFQUEUE: binding to queue '0'
error during nfq_create_queue()

ottoaim@jesse:~$ lsmod | grep NFQUEUE
ipt_NFQUEUE             1920  0
ip_tables              23744  3 iptable_filter,ipt_NFQUEUE,ipt_state

if anyone has any idea I'd love to get this working

The script in /etc/init.d is not perfect. In some cases you may end up with two instances of moblock, the second one will be unable to bind to the queue.

You may try to killall moblock-nfq and to /etc/init.d/moblock-nfq start.

Maybe this solves your problem.

[clessing]

pommattski; You're absolutely correct. I did not add this because i want people to decide if rebootinbg the computer would be a better choice, as i dont know if restarting moblock leaves one unprotected for a second or two... But i'll add it (commented) to the update script so people can uncoment it on their own...

"/etc/init.d/moblock-nfq reload" does this without leaving you unprotected.
This is the same as killall -HUP moblock-nfq. It reloads the blocklist without quitting moblock.
The command mentioned above is also used by the daily update script.

[haani]

Hi, I'm the gui who is maintaining http://moblock-deb.sourceforge.net/.

Please have a look at the scripts in /etc/firestarter. There are two interesting files "user-pre" and "user-post" to customize firestarter.

You should be able to get moblock and firestarter working together if you disable the iptables stuff in /etc/moblock/MoBlock-....sh and add those rules to the firestarter scripts.

Make sure that the moblock rules grab the traffic before firestarter does

someone please tell me how to configure firestarter so that it can work with moblock in detail thanks

[neev]

Hello!! Sorry if it is a very basic question, but how do i get moblock installed?? Im newbie with linux so most of the things i do is basically read and try to follow steps but i cannot get it with moblock. Ive followed the steps in the 1st page of the topic but i get an error. When i do sudo apt-get update it says it cannot find http://moblock-deb.sourceforge.net/d...stable/Release Unable to find expected entry main/binary-amd64/Packages in Meta-index file (malformed Release file?).

What am i doing wrong?? Any help is much appreciated,

sorry about my english!! and thanks a lot!!

[clessing]

someone please tell me how to configure firestarter so that it can work with moblock in detail thanks

I don't use it and I don't intend to use it.... but looking at the scripts in /etc/firestarter I can say, that firestarter deletes all existing firewall rules when setting up its own rules.
So you have to open /etc/moblock/MoBlock-nfq.sh with your favourite text editor:

Find the line
/usr/bin/moblock $@

Everything before this line goes into /etc/firestarter/user-pre

Leave /etc/moblock/Moblock-nfq.sh unmodified.

Doing so should cause firestarter to insert the iptables rules that moblock uses under normal circumstances before its own rules.

[clessing]

http://moblock-deb.sourceforge.net/d...stable/Release Unable to find expected entry main/binary-amd64/Packages in Meta-index file (malformed Release file?).
!

I haven't compiled a version for amd64. Please google a bit to find out whether you can install debian packages for 32bit processors - I really don't know.

[pelle.k]

Thanks clessing!
Now try this out people, so i can add it to the howto...

[haani]

I don't use it and I don't intend to use it.... but looking at the scripts in /etc/firestarter I can say, that firestarter deletes all existing firewall rules when setting up its own rules.
So you have to open /etc/moblock/MoBlock-nfq.sh with your favourite text editor:

Find the line
/usr/bin/moblock $@

Everything before this line goes into /etc/firestarter/user-pre

Leave /etc/moblock/Moblock-nfq.sh unmodified.

Doing so should cause firestarter to insert the iptables rules that moblock uses under normal circumstances before its own rules.

doesnt work firestarter says that it can't connect/start!! when i remove the text from /etc/firestarter/user-per than it works!! so i am thinkin that there is no way of workin moblock and firestarter together??