You are not logged in.
Hey guys,
Used to use IPBlock for privacy, however I am unable to compile that in Arch. This is fine however, as I am now using MoBlock (or at least trying to).
I have installed moblock, moblock-control and mobloquer from the AUR, however I am unable to start moblock.
Mobloquer launches fine, and will update the blocklists fine. However, upon clicking "start" I receive the following;
"Inserting iptables
Starting MoBlock/usr/bin/moblock-control: line 702: start-stop-daemon: command not found
failed!"
If I try and do it through the command line;
"[user@machine ~]$
moblock-control start
Error 5: /usr/bin/moblock not installed.
sudo moblock-control start
Starting MoBlock: moblock failed!
"
It may be worth mentioning that after the starting fails, no internet connections work, though LAN connections do.
Any help fixing this would be much appreciated.
Thanks
Offline
ok is this 32bit or 64? if you are 64bit you most likeely will have to compile your own I am not sure how to do it on Arch here is a couple of commands that I knopw work , sometimes the GUI after the first install is a little screwy so try these commands
moblock-control start - inserts iptables rules and starts MoBlock
moblock-control stop - deletes iptables rules and stops MoBlock
moblock-control restart - restarts MoBlock
moblock-control reload - rebuilds the blocklist and reloads MoBlock
moblock-control update - updates the blocklists and reloads MoBlock
moblock-control status - gives the iptables settings and the status of the MoBlock daemon
moblock-control test - simple test to check if MoBlock is working
And here are a couple of links that just might help youhttp://moblock-deb.sourceforge.net/ and here http://mobloquer.foutrelis.com/ but the best place is right at the source which is here http://forums.phoenixlabs.org/forumdisplay.php?f=15
Last edited by Shadowmeph (2008-06-07 01:06:40)
Offline
I downloaded the files from the AUR, and this is what I did to install them;
tar xzf moblock*.tar.gz
cd moblock*
makepkg PKGBUILD
pacman -U moblock*
(note that the *'s indicate these were the same steps followed for all files, I was specific what I installed and untarred.)
That installed them correctly, so not sure why it won't run :S. I rebooted etc too. Thanks for the input though.
Offline
don't take my word for this because I am inexperienced with linux but I thought that it was supposed to be done like this
tar -xvvzf moblock*.tar.gz
cd moblock
makepkg -s
pacman -U what ever packkage is made
Offline
don't take my word for this because I am inexperienced with linux but I thought that it was supposed to be done like this
tar -xvvzf moblock*.tar.gz
cd moblock
makepkg -s
pacman -U what ever packkage is made
Unfortunately this does not fix the issue. Any other ideas?
Offline
I would post this on the phoenixlabs website or check there
Offline
I'm getting the same errors.
$ sudo moblock-control start
Starting MoBlock: moblock failed!
moblock-control.log
2008-08-21 14:54:50 BST Begin: moblock-control start
Inserting iptables.
Starting MoBlock/usr/bin/moblock-control: line 702: start-stop-daemon: command not found
failed!
moblock.log
Error opening /etc/moblock/banned.list, aborting...
was gonna post it at the aur package.
Offline
Does "/etc/rc.d/moblock start" work? If it does then it's a problem with moblock-control, not moblock.
Offline
Does "/etc/rc.d/moblock start" work? If it does then it's a problem with moblock-control, not moblock.
yeah, thanks, it is a moblock-control problem..
ive been using moblock-control to control the cli not the gui, maybe all this is conflicting,
gonna try just installing moblock package and removing control, then using the update,stats,start,stop from /etc/rc.d/moblock
Last edited by gav616 (2008-08-21 15:59:57)
Offline
Try ipblock from AUR again. It has been updated to compile with gcc 4.3
"Your beliefs can be like fences that surround you.
You must first see them or you will not even realize that you are not free, simply because you will not see beyond the fences.
They will represent the boundaries of your experience."
SETH / Jane Roberts
Offline
Try ipblock from AUR again. It has been updated to compile with gcc 4.3
So was moblock
Actually, I'll have to have a look at the moblockcontrol package sometime in the near future and coordinate with its maintainer so that moblock and moblockcontrol work together without problems.
Offline
Just reporting I have the same issue:
Starting MoBlock/usr/bin/moblock-control: line 702: start-stop-daemon: command not found
Everything works fine except starting moblock through moblock-control:
sudo moblock-control start
After moblock has been started manually with:
sudo /etc/rc.d/moblock start
everything works as it should.
Offline
ok, and how do i configure moblock the right way (without guis)? installing, updating and starting moblock went fine but it seems that it blocks my whole network or rather everything which is relating to google^^
Offline
All configuration is done in /etc/moblock/moblock.conf. You'll have to whitelist your local network:
WHITE_IP_OUT="192.168.x.0/24"
replace 192.168.x.0 with your network address (you can find it with ipconfig).
Offline
ok, and how do i configure moblock the right way (without guis)? installing, updating and starting moblock went fine but it seems that it blocks my whole network or rather everything which is relating to google^^
I'm not using moblock control, so this is for moblock by itself... You should edit the /usr/bin/MoBlock-nfq.sh file and edit line 9 to look something like this:
WHITE_TCP_OUT="http https ftp svn"
Offline
there's no /etc/moblock/moblock.conf file avaible. should i create and configure it manually?
Offline
My apologies, that file comes with the package moblockcontrol.
Offline
Instead of using the start-stop-daemon utility (because it wasn't working for me even when it was installed), I edited moblock-control to not use it and just invoke the normal moblock utility.
In /usr/bin/moblock-control
Lines 700 and 708
Change to: DAEMON_OPTS="-$BLOCKLIST_FORMAT $BLOCKLIST -q $NFQUEUE_NUMBER $DAEMON_LOG"
Lines 703 and 710
Change to: sudo /usr/bin/moblock $DAEMON_OPTS
Offline