Moblock (peerguardian linux alternative)

[n0ctem]

I'm trying to remove moblock so that I can reinstall, but I keep getting this error:

Removing moblock-nfq ...
 * MoBlock: /etc/moblock/moblock.conf not installed.
invoke-rc.d: initscript moblock-nfq, action "stop" failed.
dpkg: error processing moblock-nfq (--purge):
 subprocess pre-removal script returned error exit status 6
 * MoBlock: /etc/moblock/moblock.conf not installed.
invoke-rc.d: initscript moblock-nfq, action "start" failed.
dpkg: error while cleaning up:
 subprocess post-installation script returned error exit status 6
Errors were encountered while processing:
 moblock-nfq
E: Sub-process /usr/bin/dpkg returned an error code (1)

Trying to stop moblock doesn't work either.

Any help would be much appreciated. Thanks.

[raffytaffy]

I seemed to have solved my problems. As someone before mentioned there was an update which indeed broke my moblock. So I removed it with all config files, and reinstalled. Configured the lists from scratch and it works well now. Here is the moblock.config I use now.

# moblock.conf - configuration file for moblock-control

# This file is sourced by a bash script. Any line which starts with a # (hash) 
# is a comment and is ignored. If you set the same variable several times,
# then only the last line will be used. You have to stop/restart/reload moblock
# if you change entries.

############################ General configuration ############################

# Specify the format of the blocklists that you use. You can´t mix different
# formats.
# d - eMule ipfilter.dat format
# n - peerguardian .p2b v2 binary format
# p - peerguardian .p2p text format
BLOCKLIST_FORMAT="p"

# Specify a NFQUEUE queue number (default 0)
# Works only with -nfq version
NFQUEUE_NUMBER="0"

# Turn on/off automatic start
# 0 - Don´t start MoBlock at system boot
# 1 - Start MoBlock at system boot
MOBLOCK_INIT="1"

# Turn on/off automatic blocklist update
# 0 - Don´t update the blocklists automatically
# 1 - Update the blocklists automatically
MOBLOCK_CRON="1"

# Set the verbosity of moblock-control
# 0 - No normal output to STDOUT, only to logfile
# 1 - Output to STDOUT and to logfile
VERBOSITY="1"

################## Settings for the iptables firewall rules ###################

# MoBlock requires the iptables rule NFQUEUE (nfq version)
# or the deprecated QUEUE (ipq version).

# Do a "moblock-control stop" before you change these iptables settings.

# Define how traffic is sent to MoBlock
# 0 - Don't set any iptables rules.
#     You or another script/firewall has to do this!
# 1 - NFQUEUE is in the chains moblock_in, moblock_out and moblock_fw.
# 2 - Set custom iptables rules (defined in
#     /etc/moblock/iptables-custom-insert.sh and iptables-custom-remove.sh)
IPTABLES_SETTINGS="1"

# Define when traffic is sent to the chain that contains NFQUEUE
# This section works only for IPTABLES_SETTINGS="1"
# 0 - Do nothing. You or another script/firewall has to do this!
# 1 - Insert the rules at the head of the chains.
# 2 - Append the rules to the end of the chains.
IPTABLES_ACTIVATION="2"

############################### Whitelist ports ###############################

# Whitelist ports by port number or with the associated service name
# (using iptables with the target RETURN)
# Seperate several entries with whitespace (" ")
# Port ranges are specified in the format "port:port"

# This section works only for IPTABLES_SETTINGS="1"
# Do a "moblock-control restart" when you have changed these settings.

WHITE_TCP_IN=""
WHITE_UDP_IN=""
WHITE_TCP_OUT=""
# This is an example to whitelist outgoing web traffic (port 80 is the service
# http, 443 is https) and the port range 1000-1024:
WHITE_TCP_OUT="80 443 5050 1863 5222 465 995"
WHITE_UDP_OUT=""
WHITE_TCP_FORWARD=""
WHITE_UDP_FORWARD=""

################################ Whitelist IPs ################################

# Whitelist either a network name, a hostname (please note that specifying any
# name to be resolved with a remote query such as DNS is a really bad idea), a
# network IP address (with /mask), or a plain IP address.
# (using iptables with the target RETURN)
# The mask can be either a network mask or a plain number, specifying the number
# of 1's at the left side of the network mask. Thus, a mask of 24 is equivalent
# to 255.255.255.0.
# Seperate several entries with whitespace (" ")

# This section works only for IPTABLES_SETTINGS="1"
# Do a "moblock-control restart" when you have changed these settings.

IP_TCP_IN=""
IP_UDP_IN=""
IP_TCP_OUT=""
# This is an example to whitelist the range 192.168.178.1-192.168.178.255:
# IP_TCP_OUT="192.168.178.0/24"
IP_UDP_OUT=""
IP_TCP_FORWARD=""
IP_UDP_FORWARD=""

###################### Remove lines from the blocklist ########################

# Remove lines from the blocklist (using "grep -v -i")
# Warning for beginners: If you want to whitelist a special IP then check the
# above section. In most cases you won't succeed if you insert an IP here.
# Seperate values with a semicolon ";".

# Do a "moblock-control reload" when you have changed these settings.

IP_REMOVE=""
# This is an example to remove all lines from the blocklist which contain one
# of the words "google", "yahoo", "altavista", "debian" or "sourceforge":
# IP_REMOVE="google;yahoo;altavista;debian;sourceforge"	

########################### Full LSB compatibility ############################

# The control script uses /lib/lsb/init-functions. In Debian this file also
# provides functions which are not defined by the LSB standard. Change this
# entry if the script complains of not knowing a function.
# 0 - Debian compatible system (default)
# 1 - LSB 3.1 but not Debian compatible system
LSB_MODE=0

[freedom]

you dont need to reinstall everything
this morning I do update and moblock was broken but...
just by adding

VERBOSITY="1"

which was not in my moblock.conf
and after

sudo moblock-control restart

problem is solved

[jre]

E: moblock-nfq: subprocess post-installation script returned error exit status 6

6 is configuration error. In most cases this means that a blocklist (configured in /etc/moblock/blocklists.list) could not be downloaded. Therefore moblock won't start.
Just remove the missing blocklists from the conffile for a while or try updating the lists again.

[wilberfan]

Thanks for these posts...I was very sad last night when my beloved Moblock wouldn't install on my new mythbuntu partition!

(Boy, you don't miss the water, till the well runs dry, do ya!)

All seems well this morning!

[mellowd]

Well, I guess you kept your old moblock.conf.
Just place a

VERBOSITY="1"

somewhere in moblock.conf. Or purge and reinstall moblock.

Thanks pelle for your last post, I totally agree.

Works perfectly, thanks!

btw, I've never done a purge, how is that done?

[pelle.k]

sudo apt-get purge moblock-nfq; sudo apt-get install moblock-nfq

This is recommended, since the VERBOSITY variable may not be the only thing changed in the last update. save your changes from moblock.conf and merge them when you've purged the installation.

[mellowd]

sudo apt-get purge moblock-nfq; sudo apt-get install moblock-nfq

This is recommended, since the VERBOSITY variable may not be the only thing changed in the last update. save your changes from moblock.conf and merge them when you've purged the installation.

Fantastic. I was having trouble trying to remove moblock, it simply wouldn't do it.

Thanks again!

[Maczimus]

6 is configuration error. In most cases this means that a blocklist (configured in /etc/moblock/blocklists.list) could not be downloaded. Therefore moblock won't start.
Just remove the missing blocklists from the conffile for a while or try updating the lists again.

Thanks. I got moblock working but it scared me when it would give me the error whenever i would reinstall it (after removing it) but I have tailed the log and it is blocking sites.

Thanks again.

[SpookyET]

Is there any way to allow HTTP traffic like PeerGuardian?