Preconfiguring packages ...
Selecting previously deselected package moblock.
(Reading database ... 169294 files and directories currently installed.)
Unpacking moblock (from .../moblock_0.9~rc2-22+intrepid_i386.deb) ...
Selecting previously deselected package blockcontrol.
Unpacking blockcontrol (from .../blockcontrol_1.3-6_all.deb) ...
Selecting previously deselected package moblock-control.
Unpacking moblock-control (from .../moblock-control_1.3-1_all.deb) ...
Selecting previously deselected package mobloquer.
Unpacking mobloquer (from .../mobloquer_0.6-1+intrepid_i386.deb) ...
Selecting previously deselected package mobloquer-dbg.
Unpacking mobloquer-dbg (from .../mobloquer-dbg_0.6-1+intrepid_i386.deb) ...
Processing triggers for man-db ...
Setting up moblock (0.9~rc2-22+intrepid) ...
Setting up blockcontrol (1.3-6) ...

MoBlock will soon be started ...
If any blocklists are missing, they will be downloaded. This may take several
minutes. Please be patient and don't abort. If you want to follow the update
process, then do in another terminal a
 tail -f /var/log/blockcontrol.log
The lists are saved to /var/spool/blockcontrol/.
The installation of blockcontrol will fail, if starting MoBlock fails. If this
happens, then in most cases downloading the blocklists failed temporarily. To
workaround this, you can turn the automatic starting of MoBlock off by setting
in /etc/blockcontrol/blockcontrol.conf:
 INIT="0"

 * Starting MoBlock moblock
invoke-rc.d: initscript blockcontrol, action "start" failed.
dpkg: error processing blockcontrol (--configure):
 subprocess post-installation script returned error exit status 8
dpkg: dependency problems prevent configuration of moblock-control:
 moblock-control depends on blockcontrol; however:
  Package blockcontrol is not configured yet.
dpkg: error processing moblock-control (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of mobloquer:
 mobloquer depends on blockcontrol; however:
  Package blockcontrol is not configured yet.
dpkg: error processing mobloquer (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of mobloquer-dbg:
 mobloquer-dbg depends on mobloquer (= 0.6-1+intrepid); however:
  Package mobloquer is not configured yet.
dpkg: error processing mobloquer-dbg (--configure):
 dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
                          No apport report written because the error message indicates its a followup error from a previous failure.
                                                    No apport report written because MaxReports is reached already
                                  Errors were encountered while processing:
 blockcontrol
 moblock-control
 mobloquer
 mobloquer-dbg
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
Setting up blockcontrol (1.3-6) ...

MoBlock will soon be started ...
If any blocklists are missing, they will be downloaded. This may take several
minutes. Please be patient and don't abort. If you want to follow the update
process, then do in another terminal a
 tail -f /var/log/blockcontrol.log
The lists are saved to /var/spool/blockcontrol/.
The installation of blockcontrol will fail, if starting MoBlock fails. If this
happens, then in most cases downloading the blocklists failed temporarily. To
workaround this, you can turn the automatic starting of MoBlock off by setting
in /etc/blockcontrol/blockcontrol.conf:
 INIT="0"

 * Starting MoBlock moblock
invoke-rc.d: initscript blockcontrol, action "start" failed.
dpkg: error processing blockcontrol (--configure):
 subprocess post-installation script returned error exit status 8
dpkg: dependency problems prevent configuration of moblock-control:
 moblock-control depends on blockcontrol; however:
  Package blockcontrol is not configured yet.
dpkg: error processing moblock-control (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of mobloquer:
 mobloquer depends on blockcontrol; however:
  Package blockcontrol is not configured yet.
dpkg: error processing mobloquer (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of mobloquer-dbg:
 mobloquer-dbg depends on mobloquer (= 0.6-1+intrepid); however:
  Package mobloquer is not configured yet.
dpkg: error processing mobloquer-dbg (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 blockcontrol
 moblock-control
 mobloquer
 mobloquer-dbg

Please post your logfiles and output of commands wrapped in
[ CODE ] tags. You find them in the advanced editing mode: #

2009-04-05 08:39:39 PM CDT Begin: blockcontrol start
Building blocklist... Updating TBG_Primary_Threats... done.
Extracting TBG_Primary_Threats, detected gz... done.
Updating TBG_General_Corporate_Ranges... done.
Extracting TBG_General_Corporate_Ranges, detected gz... done.
Updating TBG_Business_ISPs... done.
Extracting TBG_Business_ISPs, detected gz... done.
Updating TBG_Hijacked... done.
Extracting TBG_Hijacked, detected gz... done.
Updating TBG_Bogon... done.
Extracting TBG_Bogon, detected gz... done.

[ OK ]
Inserting iptables ...Bad argument `255.255.255.0'
Try `iptables -h' or 'iptables --help' for more information.

[fail]
2009-04-05 08:42:02 PM CDT Begin: blockcontrol start
Inserting iptables ...iptables: Chain already exists

[fail]
2009-04-05 08:42:56 PM CDT Begin: moblock-control start
Inserting iptables ...iptables: Chain already exists

[fail]
2009-04-05 08:43:11 PM CDT Begin: moblock-control start
Inserting iptables ...iptables: Chain already exists

[fail]
2009-04-05 08:45:22 PM CDT Begin: blockcontrol start
Inserting iptables ...iptables: Chain already exists

[fail]
2009-04-05 08:45:24 PM CDT Begin: blockcontrol start
Inserting iptables ...iptables: Chain already exists

[fail]
2009-04-05 08:46:51 PM CDT Begin: blockcontrol start
Inserting iptables ...iptables: Chain already exists

[fail]
2009-04-05 08:47:30 PM CDT Begin: blockcontrol start
Inserting iptables ...iptables: Chain already exists

[fail]
2009-04-05 08:49:12 PM CDT Begin: blockcontrol start
Inserting iptables ...iptables: Chain already exists

[fail]
2009-04-05 08:49:26 PM CDT Begin: moblock-control start
Inserting iptables ...iptables: Chain already exists

[fail]
2009-04-05 08:59:47 PM CDT Begin: blockcontrol start
Inserting iptables ...iptables: Chain already exists
   ...fail!
2009-04-05 08:59:51 PM CDT Begin: blockcontrol start
Inserting iptables ...iptables: Chain already exists
   ...fail!
2009-04-05 09:12:27 PM CDT Begin: blockcontrol start
Inserting iptables ...iptables: Chain already exists
   ...fail!
2009-04-05 09:12:34 PM CDT Begin: blockcontrol start
Inserting iptables ...iptables: Chain already exists
   ...fail!
2009-04-05 09:14:48 PM CDT Begin: moblock-control start
Inserting iptables ...iptables: Chain already exists

[fail]
2009-04-05 09:16:54 PM CDT Begin: blockcontrol start
Inserting iptables ...iptables: Chain already exists
   ...fail!
2009-04-05 09:16:58 PM CDT Begin: blockcontrol start
Inserting iptables ...iptables: Chain already exists
   ...fail!
2009-04-05 09:21:45 PM CDT Begin: blockcontrol update
Updating blocklists ...
Updating Bluetack_ads... . No update available.
Extracting Bluetack_ads, detected gz... done.
Updating Bluetack_bogon... . No update available.
Extracting Bluetack_bogon, detected gz... done.
Updating Bluetack_dshield... . No update available.
Extracting Bluetack_dshield, detected gz... done.
Updating www.bluetack.co.uk/config/fornonlancomputers.gz... 2009-04-05 09:24:04 PM CDT Begin: blockcontrol start
Building blocklist...    ...done.
Inserting iptables ...iptables: Chain already exists
   ...fail!
2009-04-05 09:24:30 PM CDT Begin: blockcontrol stop
Deleting iptables ...iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
   ...fail!
 * There occured some errors during the deletion of the iptables rules.
 * The most common reason for this is that they did not exist, because MoBlock
 * was not running. In this case you don't have to worry.
 * But if MoBlock was running there is some problem. Most probably you have
 * installed another firewall application that did delete the iptables rules.
 * A "blockcontrol restart" will then fix the situation.
Executing /etc/blockcontrol/iptables-custom-remove.sh ...   ...done.
Stopping MoBlock ...   ...done.
2009-04-05 09:24:30 PM CDT End: blockcontrol stop
2009-04-05 09:24:36 PM CDT Begin: blockcontrol stop
Deleting iptables ...iptables v1.4.0: Couldn't load target `blockcontrol_in':/lib/iptables/libipt_blockcontrol_in.so: cannot open shared object file: No such file or directory

Try `iptables -h' or 'iptables --help' for more information.
iptables v1.4.0: Couldn't load target `blockcontrol_out':/lib/iptables/libipt_blockcontrol_out.so: cannot open shared object file: No such file or directory

Try `iptables -h' or 'iptables --help' for more information.
iptables v1.4.0: Couldn't load target `blockcontrol_fw':/lib/iptables/libipt_blockcontrol_fw.so: cannot open shared object file: No such file or directory

Try `iptables -h' or 'iptables --help' for more information.
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
   ...fail!
 * There occured some errors during the deletion of the iptables rules.
 * The most common reason for this is that they did not exist, because MoBlock
 * was not running. In this case you don't have to worry.
 * But if MoBlock was running there is some problem. Most probably you have
 * installed another firewall application that did delete the iptables rules.
 * A "blockcontrol restart" will then fix the situation.
Executing /etc/blockcontrol/iptables-custom-remove.sh ...   ...done.
Stopping MoBlock ...   ...done.
2009-04-05 09:24:36 PM CDT End: blockcontrol stop
2009-04-05 09:24:40 PM CDT Begin: blockcontrol restart
Deleting iptables ...iptables v1.4.0: Couldn't load target `blockcontrol_in':/lib/iptables/libipt_blockcontrol_in.so: cannot open shared object file: No such file or directory

Try `iptables -h' or 'iptables --help' for more information.
iptables v1.4.0: Couldn't load target `blockcontrol_out':/lib/iptables/libipt_blockcontrol_out.so: cannot open shared object file: No such file or directory

Try `iptables -h' or 'iptables --help' for more information.
iptables v1.4.0: Couldn't load target `blockcontrol_fw':/lib/iptables/libipt_blockcontrol_fw.so: cannot open shared object file: No such file or directory

Try `iptables -h' or 'iptables --help' for more information.
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
   ...fail!
 * There occured some errors during the deletion of the iptables rules.
 * The most common reason for this is that they did not exist, because MoBlock
 * was not running. In this case you don't have to worry.
 * But if MoBlock was running there is some problem. Most probably you have
 * installed another firewall application that did delete the iptables rules.
 * A "blockcontrol restart" will then fix the situation.
Executing /etc/blockcontrol/iptables-custom-remove.sh ...   ...done.
Stopping MoBlock ...   ...done.
Inserting iptables ...Bad argument `255.255.255.0'
Try `iptables -h' or 'iptables --help' for more information.
   ...fail!
2009-04-05 09:24:42 PM CDT Begin: blockcontrol stop
Deleting iptables ...iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
   ...fail!
 * There occured some errors during the deletion of the iptables rules.
 * The most common reason for this is that they did not exist, because MoBlock
 * was not running. In this case you don't have to worry.
 * But if MoBlock was running there is some problem. Most probably you have
 * installed another firewall application that did delete the iptables rules.
 * A "blockcontrol restart" will then fix the situation.
Executing /etc/blockcontrol/iptables-custom-remove.sh ...   ...done.
Stopping MoBlock ...   ...done.
2009-04-05 09:24:42 PM CDT End: blockcontrol stop
2009-04-05 09:24:43 PM CDT Begin: blockcontrol start
Inserting iptables ...Bad argument `255.255.255.0'
Try `iptables -h' or 'iptables --help' for more information.
   ...fail!
2009-04-05 09:25:16 PM CDT Begin: blockcontrol stop
Deleting iptables ...iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
   ...fail!
 * There occured some errors during the deletion of the iptables rules.
 * The most common reason for this is that they did not exist, because MoBlock
 * was not running. In this case you don't have to worry.
 * But if MoBlock was running there is some problem. Most probably you have
 * installed another firewall application that did delete the iptables rules.
 * A "blockcontrol restart" will then fix the situation.
Executing /etc/blockcontrol/iptables-custom-remove.sh ...   ...done.
Stopping MoBlock ...   ...done.
2009-04-05 09:25:16 PM CDT End: blockcontrol stop
2009-04-05 09:25:16 PM CDT Begin: blockcontrol reload
 * MoBlock is not running, doing nothing.
2009-04-05 09:25:16 PM CDT End: blockcontrol reload
2009-04-05 09:25:24 PM CDT Begin: blockcontrol start
Inserting iptables ...Bad argument `255.255.255.0'
Try `iptables -h' or 'iptables --help' for more information.
   ...fail!
2009-04-05 09:29:34 PM CDT Begin: blockcontrol stop
Deleting iptables ...iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
   ...fail!
 * There occured some errors during the deletion of the iptables rules.
 * The most common reason for this is that they did not exist, because MoBlock
 * was not running. In this case you don't have to worry.
 * But if MoBlock was running there is some problem. Most probably you have
 * installed another firewall application that did delete the iptables rules.
 * A "blockcontrol restart" will then fix the situation.
Executing /etc/blockcontrol/iptables-custom-remove.sh ...   ...done.
Stopping MoBlock ...   ...done.
2009-04-05 09:29:34 PM CDT End: blockcontrol stop
2009-04-05 10:10:53 PM CDT Begin: blockcontrol start
Building blocklist... Updating TBG_Primary_Threats... done.
Extracting TBG_Primary_Threats, detected gz... done.
Updating TBG_General_Corporate_Ranges... done.
Extracting TBG_General_Corporate_Ranges, detected gz... done.
Updating TBG_Business_ISPs... done.
Extracting TBG_Business_ISPs, detected gz... done.
Updating TBG_Search_Engines... done.
Extracting TBG_Search_Engines, detected gz... done.
Updating TBG_Hijacked... done.
Extracting TBG_Hijacked, detected gz... done.
Updating TBG_Bogon... done.
Extracting TBG_Bogon, detected gz... done.
Updating Bluetack_level1... done.
Extracting Bluetack_level1, detected gz... done.
Updating Bluetack_level2... done.
Extracting Bluetack_level2, detected gz... done.
Updating Bluetack_level3... done.
Extracting Bluetack_level3, detected gz... done.
Updating Bluetack_ads... done.
Extracting Bluetack_ads, detected gz... done.
Updating Bluetack_bogon... done.
Extracting Bluetack_bogon, detected gz... done.
Updating Bluetack_spyware... done.
Extracting Bluetack_spyware, detected gz... done.
Updating Bluetack_spider... done.
Extracting Bluetack_spider, detected gz... done.
Updating Bluetack_Microsoft... done.
Extracting Bluetack_Microsoft, detected gz... done.
Updating Bluetack_proxy... done.
Extracting Bluetack_proxy, detected gz... done.
Updating Bluetack_hijacked... done.
Extracting Bluetack_hijacked, detected gz... done.
Updating Bluetack_badpeers... done.
Extracting Bluetack_badpeers, detected gz... done.
Updating Bluetack_rangetest... done.
Extracting Bluetack_rangetest, detected gz... done.
Updating Bluetack_dshield... done.
Extracting Bluetack_dshield, detected gz... done.
   ...done.
Inserting iptables ...Bad argument `255.255.255.0'
Try `iptables -h' or 'iptables --help' for more information.
   ...fail!
2009-04-05 10:15:11 PM CDT Begin: blockcontrol start
Inserting iptables ...iptables: Chain already exists
   ...fail!
2009-04-05 10:16:25 PM CDT Begin: blockcontrol stop
Deleting iptables ...iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
   ...fail!
 * There occured some errors during the deletion of the iptables rules.
 * The most common reason for this is that they did not exist, because MoBlock
 * was not running. In this case you don't have to worry.
 * But if MoBlock was running there is some problem. Most probably you have
 * installed another firewall application that did delete the iptables rules.
 * A "blockcontrol restart" will then fix the situation.
Executing /etc/blockcontrol/iptables-custom-remove.sh ...   ...done.
Stopping MoBlock ...   ...done.
2009-04-05 10:16:26 PM CDT End: blockcontrol stop
2009-04-05 10:17:10 PM CDT Begin: blockcontrol start
Inserting iptables ...Bad argument `255.255.255.0'
Try `iptables -h' or 'iptables --help' for more information.
   ...fail!
2009-04-05 10:17:14 PM CDT Begin: blockcontrol start
Inserting iptables ...iptables: Chain already exists
   ...fail!
2009-04-05 10:24:46 PM CDT Begin: blockcontrol start
Inserting iptables ...iptables: Chain already exists
   ...fail!
2009-04-05 10:25:00 PM CDT Begin: blockcontrol start
Inserting iptables ...iptables: Chain already exists
   ...fail!
2009-04-05 10:25:44 PM CDT Begin: blockcontrol stop
Deleting iptables ...iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
   ...fail!
 * There occured some errors during the deletion of the iptables rules.
 * The most common reason for this is that they did not exist, because MoBlock
 * was not running. In this case you don't have to worry.
 * But if MoBlock was running there is some problem. Most probably you have
 * installed another firewall application that did delete the iptables rules.
 * A "blockcontrol restart" will then fix the situation.
Executing /etc/blockcontrol/iptables-custom-remove.sh ...   ...done.
Stopping MoBlock ...   ...done.
2009-04-05 10:25:44 PM CDT End: blockcontrol stop
2009-04-05 10:27:21 PM CDT Begin: blockcontrol start
Building blocklist... Updating TBG_Primary_Threats... done.
Extracting TBG_Primary_Threats, detected gz... done.
Updating TBG_General_Corporate_Ranges... done.
Extracting TBG_General_Corporate_Ranges, detected gz... done.
Updating TBG_Business_ISPs... done.
Extracting TBG_Business_ISPs, detected gz... done.
Updating TBG_Search_Engines... done.
Extracting TBG_Search_Engines, detected gz... done.
Updating TBG_Hijacked... done.
Extracting TBG_Hijacked, detected gz... done.
Updating TBG_Bogon... done.
Extracting TBG_Bogon, detected gz... done.
Updating Bluetack_level1... done.
Extracting Bluetack_level1, detected gz... done.
Updating Bluetack_level2... done.
Extracting Bluetack_level2, detected gz... done.
Updating Bluetack_level3... done.
Extracting Bluetack_level3, detected gz... done.
Updating Bluetack_ads... done.
Extracting Bluetack_ads, detected gz... done.
Updating Bluetack_bogon... done.
Extracting Bluetack_bogon, detected gz... done.
Updating Bluetack_spyware... done.
Extracting Bluetack_spyware, detected gz... done.
Updating Bluetack_spider... done.
Extracting Bluetack_spider, detected gz... done.
Updating Bluetack_Microsoft... done.
Extracting Bluetack_Microsoft, detected gz... done.
Updating Bluetack_proxy... done.
Extracting Bluetack_proxy, detected gz... done.
Updating Bluetack_hijacked... done.
Extracting Bluetack_hijacked, detected gz... done.
Updating Bluetack_badpeers... done.
Extracting Bluetack_badpeers, detected gz... done.
Updating Bluetack_rangetest... done.
Extracting Bluetack_rangetest, detected gz... done.
Updating Bluetack_dshield... done.
Extracting Bluetack_dshield, detected gz... done.
   ...done.
Inserting iptables ...Bad argument `255.255.255.0'
Try `iptables -h' or 'iptables --help' for more information.
   ...fail!
2009-04-05 10:31:43 PM CDT Begin: blockcontrol start
Inserting iptables ...iptables: Chain already exists
   ...fail!
2009-04-06 02:15:24 AM CDT Begin: moblock-control start
Inserting iptables ...iptables: Chain already exists

[fail]
2009-04-06 02:15:32 AM CDT Begin: moblock-control start
Inserting iptables ...iptables: Chain already exists

[fail]
2009-04-06 02:15:33 AM CDT Begin: moblock-control start
Inserting iptables ...iptables: Chain already exists

[fail]
2009-04-06 02:15:33 AM CDT Begin: moblock-control start
Inserting iptables ...iptables: Chain already exists

[fail]
2009-04-06 02:15:34 AM CDT Begin: moblock-control start
Inserting iptables ...iptables: Chain already exists

[fail]
2009-04-06 02:15:34 AM CDT Begin: moblock-control start
Inserting iptables ...iptables: Chain already exists

[fail]
2009-04-06 02:15:34 AM CDT Begin: moblock-control start
Inserting iptables ...iptables: Chain already exists

[fail]
2009-04-06 02:15:35 AM CDT Begin: moblock-control start
Inserting iptables ...iptables: Chain already exists

[fail]
2009-04-06 02:15:35 AM CDT Begin: moblock-control start
Inserting iptables ...iptables: Chain already exists

[fail]
2009-04-06 02:15:35 AM CDT Begin: moblock-control start
Inserting iptables ...iptables: Chain already exists

[fail]
2009-04-06 02:15:36 AM CDT Begin: moblock-control start
Inserting iptables ...iptables: Chain already exists

[fail]
2009-04-06 02:15:36 AM CDT Begin: moblock-control start
Inserting iptables ...iptables: Chain already exists

[fail]
2009-04-06 02:15:36 AM CDT Begin: moblock-control start
Inserting iptables ...iptables: Chain already exists

[fail]
2009-04-06 02:15:36 AM CDT Begin: moblock-control start
Inserting iptables ...iptables: Chain already exists

[fail]
2009-04-06 02:15:37 AM CDT Begin: moblock-control start
Inserting iptables ...iptables: Chain already exists

[fail]
2009-04-06 02:15:37 AM CDT Begin: moblock-control start
Inserting iptables ...iptables: Chain already exists

[fail]
2009-04-06 02:18:24 CDT Begin: blockcontrol stop
Deleting iptables ...iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name

[fail]
 * There occured some errors during the deletion of the iptables rules.
 * The most common reason for this is that they did not exist, because MoBlock
 * was not running. In this case you don't have to worry.
 * But if MoBlock was running there is some problem. Most probably you have
 * installed another firewall application that did delete the iptables rules.
 * A "blockcontrol restart" will then fix the situation.
Executing /etc/blockcontrol/iptables-custom-remove.sh ...
[ OK ]
Stopping MoBlock ...
[ OK ]
2009-04-06 02:18:24 CDT End: blockcontrol stop
2009-04-06 13:35:58 CDT Begin: blockcontrol start
Inserting iptables ...
[ OK ]
Executing /etc/blockcontrol/iptables-custom-insert.sh ...
[ OK ]
Starting MoBlock ...
[ OK ]
2009-04-06 13:35:58 CDT End: blockcontrol start
2009-04-06 01:39:21 PM CDT Begin: blockcontrol restart
Deleting iptables ...   ...done.
Executing /etc/blockcontrol/iptables-custom-remove.sh ...   ...done.
Stopping MoBlock ...   ...done.
Inserting iptables ...Bad argument `255.255.255.0'
Try `iptables -h' or 'iptables --help' for more information.
   ...fail!
2009-04-06 01:40:36 PM CDT Begin: blockcontrol start
Inserting iptables ...iptables: Chain already exists
   ...fail!
2009-04-06 01:40:46 PM CDT Begin: blockcontrol start
Inserting iptables ...iptables: Chain already exists
   ...fail!
2009-04-06 01:40:50 PM CDT Begin: blockcontrol start
Inserting iptables ...iptables: Chain already exists
   ...fail!
2009-04-06 01:41:00 PM CDT Begin: blockcontrol stop
Deleting iptables ...iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
   ...fail!
 * There occured some errors during the deletion of the iptables rules.
 * The most common reason for this is that they did not exist, because MoBlock
 * was not running. In this case you don't have to worry.
 * But if MoBlock was running there is some problem. Most probably you have
 * installed another firewall application that did delete the iptables rules.
 * A "blockcontrol restart" will then fix the situation.
Executing /etc/blockcontrol/iptables-custom-remove.sh ...   ...done.
Stopping MoBlock ...   ...done.
2009-04-06 01:41:00 PM CDT End: blockcontrol stop
2009-04-06 01:41:03 PM CDT Begin: blockcontrol stop
Deleting iptables ...iptables v1.4.0: Couldn't load target `blockcontrol_in':/lib/iptables/libipt_blockcontrol_in.so: cannot open shared object file: No such file or directory

Try `iptables -h' or 'iptables --help' for more information.
iptables v1.4.0: Couldn't load target `blockcontrol_out':/lib/iptables/libipt_blockcontrol_out.so: cannot open shared object file: No such file or directory

Try `iptables -h' or 'iptables --help' for more information.
iptables v1.4.0: Couldn't load target `blockcontrol_fw':/lib/iptables/libipt_blockcontrol_fw.so: cannot open shared object file: No such file or directory

Try `iptables -h' or 'iptables --help' for more information.
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
   ...fail!
 * There occured some errors during the deletion of the iptables rules.
 * The most common reason for this is that they did not exist, because MoBlock
 * was not running. In this case you don't have to worry.
 * But if MoBlock was running there is some problem. Most probably you have
 * installed another firewall application that did delete the iptables rules.
 * A "blockcontrol restart" will then fix the situation.
Executing /etc/blockcontrol/iptables-custom-remove.sh ...   ...done.
Stopping MoBlock ...   ...done.
2009-04-06 01:41:03 PM CDT End: blockcontrol stop
2009-04-06 01:41:04 PM CDT Begin: blockcontrol start
Inserting iptables ...Bad argument `255.255.255.0'
Try `iptables -h' or 'iptables --help' for more information.
   ...fail!
2009-04-06 13:45:25 CDT Begin: blockcontrol update
Updating blocklists ...
Updating TBG_Primary_Threats... done.
Extracting TBG_Primary_Threats, detected gz... done.
Updating TBG_General_Corporate_Ranges... done.
Extracting TBG_General_Corporate_Ranges, detected gz... done.
Updating TBG_Business_ISPs... done.
Extracting TBG_Business_ISPs, detected gz... done.
Updating TBG_Search_Engines... . No update available.
Extracting TBG_Search_Engines, detected gz... done.
Updating TBG_Hijacked... . No update available.
Extracting TBG_Hijacked, detected gz... done.
Updating TBG_Bogon... . No update available.
Extracting TBG_Bogon, detected gz... done.
Updating Bluetack_level1... done.
Extracting Bluetack_level1, detected gz... done.
Updating Bluetack_level2... done.
Extracting Bluetack_level2, detected gz... done.
Updating Bluetack_level3...

Current IPv4 iptables rules (this may take a while):

Chain INPUT (policy ACCEPT 12971 packets, 16M bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain OUTPUT (policy ACCEPT 9769 packets, 911K bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain blockcontrol_fw (0 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 NFQUEUE    all  --  *      *       0.0.0.0/0            0.0.0.0/0           NFQUEUE num 92

Chain blockcontrol_in (0 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 RETURN     tcp  --  *      *       0.0.0.0/0            0.0.0.0/0           tcp dpt:443 
    0     0 RETURN     tcp  --  *      *       0.0.0.0/0            0.0.0.0/0           tcp dpt:80 
    0     0 NFQUEUE    all  --  *      *       0.0.0.0/0            0.0.0.0/0           NFQUEUE num 92

Chain blockcontrol_out (0 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 RETURN     tcp  --  *      *       0.0.0.0/0            0.0.0.0/0           tcp dpt:443 
    0     0 RETURN     tcp  --  *      *       0.0.0.0/0            0.0.0.0/0           tcp dpt:80 
    0     0 NFQUEUE    all  --  *      *       0.0.0.0/0            0.0.0.0/0           NFQUEUE num 92

Current IPv6 iptables rules (this may take a while):

Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Please check if the above printed iptables rules are correct!

 * moblock is not running.

Inserting iptables ...Bad argument `255.255.255.0'

Please post your logfiles and output of commands wrapped in
[ CODE ] tags. You find them in the advanced editing mode: #

.blockcontrol current settings:
ACCEPT="1"
ACCEPT_MARK="20"
ALLOW_FW=""
ALLOW_IN="/etc/blockcontrol/allow.p2p"
ALLOW_OUT="/etc/blockcontrol/allow.p2p"
BLOCKLIST_FORMAT="p"
BLOCKLISTS_DIR="/var/spool/blockcontrol"
BLOCKLISTS_LIST="/etc/blockcontrol/blocklists.list"
CONTROL_CONF="/etc/blockcontrol/blockcontrol.conf"
CONTROL_LIB="/usr/lib/blockcontrol/blockcontrol.lib"
CONTROL_LOG="/var/log/blockcontrol.log"
CONTROL_NAME="blockcontrol"
CONTROL_SCRIPT="/usr/bin/blockcontrol"
CRON="1"
CRON_MAILTO="root"
DAEMON="/usr/bin/moblock"
DAEMON_LOG="/var/log/moblock.log"
DESC="MoBlock"
E_BADARGS="2"
E_BLOCKLIST="9"
E_CONFIG="6"
E_IPTABLES="8"
E_NETWORK_DOWN="171"
E_NOTROOT="4"
E_XBIN="5"
E_XCD="66"
E_XEXTERNAL="170"
E_XFILE="7"
INIT="1"
IP_REMOVE=""
IPTABLES_ACTIVATION="1"
IPTABLES_CUSTOM_DELETE="/etc/blockcontrol/iptables-custom-remove.sh"
IPTABLES_CUSTOM_INSERT="/etc/blockcontrol/iptables-custom-insert.sh"
IPTABLES_SETTINGS="1"
IPTABLES_TARGET="NFQUEUE"
IPTABLES_TARGET_WHITELISTING="RETURN"
LOG_IPTABLES=""
LOG_SYSLOG="0"
LOG_TIMESTAMP="1"
LSB="/lib/lsb/init-functions"
LSB_MODE="0"
MASTER_BLOCKLIST_DIR="/var/lib/blockcontrol"
MD5SUM_FILE="/var/spool/blockcontrol/MD5SUM"
NAME="moblock"
NFQUEUE_NUMBER="92"
PATH="/usr/bin:/bin:/sbin:/usr/sbin:/usr/local/bin:/usr/local/sbin"
PIDFILE="/var/run/moblock.pid"
REJECT="1"
REJECT_FW="DROP"
REJECT_IN="DROP"
REJECT_MARK="10"
REJECT_OUT="REJECT"
STATFILE="/var/log/MoBlock.stats"
STDIFS=" "
TESTHOST="iblocklist.com"
VERBOSITY="1"
WGET_OPTS="wget -q -t 5 -T 120 -w 5"
WHITE_IP_FORWARD=""
WHITE_IP_IN=""
WHITE_IP_OUT=""
WHITE_LOCAL="1"
WHITE_TCP_FORWARD=""
WHITE_TCP_IN="http https"
WHITE_TCP_OUT="http https"
WHITE_UDP_FORWARD=""
WHITE_UDP_IN=""
WHITE_UDP_OUT=""

The following blocklists are configured to be used:
http://list.iblocklist.com/?list=ijfqtofzixtwayqovmxn
http://list.iblocklist.com/?list=ecqbsykllnadihkdirsh
http://list.iblocklist.com/?list=jcjfaxgyyshvdbceroxf
http://list.iblocklist.com/?list=pfefqteoxlfzopecdtyw
http://list.iblocklist.com/?list=tbnuqfclfkemqivekikv
http://list.iblocklist.com/?list=ewqglwibdgjttwttrinl
http://list.iblocklist.com/?list=bt_level1
http://list.iblocklist.com/?list=bt_level2
http://list.iblocklist.com/?list=bt_level3
http://list.iblocklist.com/?list=bt_ads
http://list.iblocklist.com/?list=bt_bogon
http://list.iblocklist.com/?list=bt_spyware
http://list.iblocklist.com/?list=bt_spider
http://list.iblocklist.com/?list=bt_microsoft
http://list.iblocklist.com/?list=bt_proxy
http://list.iblocklist.com/?list=bt_hijacked
http://list.iblocklist.com/?list=bt_templist
http://list.iblocklist.com/?list=bt_rangetest
http://list.iblocklist.com/?list=bt_dshield

Please post your logfiles and output of commands wrapped in
[ CODE ] tags. You find them in the advanced editing mode: #

Please post your logfiles and output of commands wrapped in
[ CODE ] tags. You find them in the advanced editing mode: #