 |
 |
|
|||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
 |
|
|
Thread Tools | Display Modes |
|
|
03-29-2009, 12:13 PM
|
#1 |
 Member Join Date: Sep 2007 Posts: 21 |
Re: blockcontrol, previously moblock-control
First I tried an upgrade which failed, I went into kpackage to try and reinstall, here's the output
Code:
moblock-control is already the newest version. mobloquer is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 3 not fully installed or removed. After this operation, 0B of additional disk space will be used. Setting up blockcontrol (1.3-3) ... mv: cannot move `/var/spool/moblock/Bluetack_rangetest' to `/var/spool/blockcontrol/Bluetack_rangetest': Directory not empty mv: cannot move `/var/spool/moblock/TBG_Bogon' to `/var/spool/blockcontrol/TBG_Bogon': Directory not empty mv: cannot move `/var/spool/moblock/TBG_Hijacked' to `/var/spool/blockcontrol/TBG_Hijacked': Directory not empty mv: cannot move `/var/spool/moblock/TBG_Primary_Threats' to `/var/spool/blockcontrol/TBG_Primary_Threats': Directory not empty dpkg: error processing blockcontrol (--configure): subprocess post-installation script returned error exit status 1 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 Errors were encountered while processing: blockcontrol moblock-control mobloquer E: Sub-process /usr/bin/dpkg returned an error code (1) RESULT=100 |
|
|
|
03-29-2009, 12:34 PM
|
#2 |
 Senior Member Join Date: Sep 2005 Posts: 588 |
Re: blockcontrol, previously moblock-control
Argh, one more update (1.3-4), please try again.
__________________
Code:
Please post your logfiles and output of commands wrapped in [ CODE ] tags. You find them in the advanced editing mode: # Author of blockcontrol, previously moblock-control. |
|
|
|
|
03-29-2009, 01:20 PM
|
#3 |
|
Member Join Date: Sep 2007 Posts: 21 |
Re: blockcontrol, previously moblock-control
You Da Man!
Upgraded via adept updater without a problem. So I can now build debs from the instructions on http://moblock-deb.sourceforge.net/ I created packages from the old repo but i guess I can get rid of them and create upto date packages? Thank You! Last edited by Digger50 : 03-29-2009 at 01:27 PM. |
|
|
|
|
03-29-2009, 02:30 PM
|
#4 |
|
Member Join Date: Sep 2007 Posts: 21 |
Re: blockcontrol, previously moblock-control
Not a major problem m8 but whitelisting IP's via mobloquer doesn't work.
Not by selecting a blocked IP and clicking "Stop blocking this IP" or even manually adding an IP to the whitelist. Where does mobloquer usually store the whitelisted IP's ? Thanks |
|
|
|
|
03-29-2009, 06:11 PM
|
#5 | |
|
Senior Member Join Date: Sep 2005 Posts: 588 |
Re: blockcontrol, previously moblock-control
Quote:
variables WHITE_IP_IN, WHITE_IP_OUT and WHITE_IP_FORWARD. Or you can add IP ranges to /etc/blockcontrol/allow.p2p You need a "blockcontrol restart" to apply your changes. Perhaps this is not happening in mobloquer because you once told it "Don't ask me agian". Check /var/log/blockcontrol.log to see if the restart is happening or any error occurs. If it doesn't work you could also start mobloquer from the terminal (or even with gdb if you install the mobloquer-dbg package) and check what's happening. If you want to create your own packages (why?), then you have to add a line with "30_hardy.dpatch" to debian/patches/00list for the mobloquer package, so that this patch is applied to the source. You can always browse the svn repository and set it to a revision of your own decision. I.e. you can always get the source of any release that I ever made. No need to make backups now, this will never be removed.
__________________
Code:
Please post your logfiles and output of commands wrapped in [ CODE ] tags. You find them in the advanced editing mode: # Author of blockcontrol, previously moblock-control. |
|
|
|
|
|
|
03-29-2009, 06:51 PM
|
#6 |
|
Member Join Date: Sep 2007 Posts: 21 |
Re: blockcontrol, previously moblock-control
Sorry my bad, I deleted my mobloquer.conf and restarted mobloquer and it works perfectly.
Don't think I'll bother building packages. Thanks |
|
|
|
|
04-08-2009, 08:02 PM
|
#7 |
 Member Join Date: Apr 2009 Country:  Posts: 4 |
Re: blockcontrol, previously moblock-control
with WHITE_LOCAL="0" moblock runs without problems. I had a different lan address than the default but I fix it. Thanl you for you work and time!
Last edited by triath : 04-08-2009 at 08:04 PM. |
|
|
|
|
04-09-2009, 02:38 PM
|
#8 | |
|
Senior Member Join Date: Sep 2005 Posts: 588 |
Re: blockcontrol, previously moblock-control
Quote:
On which system/distribution are you?
__________________
Code:
Please post your logfiles and output of commands wrapped in [ CODE ] tags. You find them in the advanced editing mode: # Author of blockcontrol, previously moblock-control. |
|
|
|
|
|
|
05-07-2009, 01:20 PM
|
#9 |
|
Senior Member Join Date: Sep 2005 Posts: 588 |
Re: blockcontrol, previously moblock-control
I think mobloquer gets that from /var/log/blockcontrol.log. So change in /etc/logrotate.d/blockcontrol the "daily" to "weekly" or "monthly".
And no, don't shut up, that's a valid question. And you nearly figured it out on your own 
__________________
Code:
Please post your logfiles and output of commands wrapped in [ CODE ] tags. You find them in the advanced editing mode: # Author of blockcontrol, previously moblock-control. |
|
|
|
|
06-16-2009, 05:39 PM
|
#10 |
|
Member Join Date: Mar 2009 Country: Posts: 22 |
Re: blockcontrol, previously moblock-control
Hi,
I'm running Slack 12.2 and successfully installed moblock 0.8 and blockcontrol 1.4. Just wondering what I have to do to get them both to start automatically on boot? In the makefile I see you copying the init file to /etc/init.d/blockcontrol. In Slack I believe that should be /etc/rc.d and I would then have to add something to rc.M or rc.local to run /etc/rc.d/blockcontrol. Is that right or is this already all taken care of? Thanks, Phil/TW Last edited by Torquewrench : 06-17-2009 at 02:05 PM. Reason: detail |
|
|
|
|
«
Previous Thread
|
Next Thread
»
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
Hybrid Mode
|
|
All times are GMT -5. The time now is 08:59 PM.
 |
 |
