General MoBlock thread

[jre]

@SuperJamie: Feel free to use whatever you wnat. But remember that ufw and MoBlock have different purposes. Which version did you try? Since a few months traffic to the LAN is whitelisted (allowed) automatically. Further there are many options for further whitelisting. The documentation and https://help.ubuntu.com/community/MoBlock show them.

@astarmathsandphysics: Yes, this is the moblock logfile. If you have questions you should ask them.

[hrd]

I'm new to linux, and installed moblock after a lot of stumbles and wrong turns. Moblock now appears to be installed, but it does not block anything. For instance, I was able to ping and visit the riaa and mpaa websites. Help?

[jre]

I'm new to linux, and installed moblock after a lot of stumbles and wrong turns. Moblock now appears to be installed, but it does not block anything. For instance, I was able to ping and visit the riaa and mpaa websites. Help?

Per default port 80 and 443 (http/https) are whitelisted, so surfing will always work. But ping should always be blocked, as long as the IP is really in the blocklist.

Try "sudo moblock-control test" and post the output of "sudo moblock-control status"

[lovinglinux]

I recently noticed an error in the logs when running the latest version.

error during nfq_unbind_pf()

followed by

NFQUEUE: binding to queue '92'

I guess I shouldn't be worried because it is binding properly and seems to work without issues, but I'm reporting it anyway.

[jre]

That's nothing to worry about. This happens since kernel 2.6.23.
In previous versions Moblock would even exit because of this. But this can simply be ignored, see here http://developer.berlios.de/bugs/?fu...&group_id=2509

[lovinglinux]

That's nothing to worry about. This happens since kernel 2.6.23.
In previous versions Moblock would even exit because of this. But this can simply be ignored, see here http://developer.berlios.de/bugs/?fu...&group_id=2509

Thanks

[PresBHaven]

So I followed the MoBlock install from https://help.ubuntu.com/community/MoBlock

After I did that and rebooted I ran the moblock test and this came back.

* moblock is dead, but /var/run/ pid file exists.
* Try "moblock-control stop". Otherwise delete /var/run/moblock.pid
* and all iptables rules related to MoBlock.

Any ideas on how to fit that so I can get moblock running?

[jre]

So I followed the MoBlock install from https://help.ubuntu.com/community/MoBlock

After I did that and rebooted I ran the moblock test and this came back.



Any ideas on how to fit that so I can get moblock running?

So have you tried, what the message told you (there are two advices!!)?
Is it a temporary problem, or does it happen again if you reboot?
Did the installation succeed or were there any error messages?

If the problem persists, please post on which distribution you are and the output of "dpkg -l lsb-base"

[PresBHaven]

Sorry, apparently I forgot how to post on forums about computers...

Here we go

Ubuntu 8.10 on a Toshiba u305 2812 Laptop
Connected to my network through wifi

dpkg -l lsb-base

gives me:

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-==============-==============-============================================
ii lsb-base 3.2-14ubuntu2 Linux Standard Base 3.2 init script function

As for this

Testing MoBlock:
* moblock is dead, but /var/run/ pid file exists.
* Try "moblock-control stop". Otherwise delete /var/run/moblock.pid
* and all iptables rules related to MoBlock.
...fail!

I have tried deleting moblock.pid and then do "sudo moblock-control start" it does not start. It says moblock starting but then instantly drops me right back where I was in the terminal. It also tells me to delete all of the iptable related to moblock and I am not exactly sure how to do that or if deleting moblock.pid does that. Is it deleting all of the blocklists? If so I have tried that, and then when I attempt to reload in the block lists that I copied and pasted out of mobloquer it says that they do not appear to be valid blocklists. Not sure if thats what the iptables are, but that is what I tried...

I just reinstalled the packages and immediately after the install pidgin stopped working but firefox was fine.

An other symptoms I have found before I reinstalled the packages( I have not rebooted since the last reinstall) is that when I boot up and moblock starts on start up firefox pidgin do not work. So I "sudo moblock-control stop" and everything returns to normal. Then when I start it again firefox and pidgin act normal.

Those are all the things I have done thus far

[jre]

Hmm, hard to say what happens.

When moblock is running there must be

1. a pid (/var/run/moblock.pid)
2. the process itself (check "ps aux|grep moblock" which should show a line similar to this (do you get this?):
   

   root      7644  1.9  2.8  64120 58008 ?        S    21:12   0:08 /usr/bin/moblock -t -p /var/lib/moblock/guarding.p2p -q 92 -r 10 -a 20 /var/log/moblock.log

3. the iptables rules (see post #1 in this thread to see how they look like)

No running daemon:
It seems as if MoBlock gets started and the iptables rules inserted, but then the daemon (2) crashes. --> If only the rules exist, but the process is not there to handle the traffic, then all traffic that should be filtered by MoBlock gets completely dropped. (So per default all traffic, except the whitelisted traffic for websurfing, is dropped.)
Please check /var/log/moblock.log if there are any hints (messages about skipping or merging ranges are unimportant).

Running daemon:
Alternatively it might be, that your lsb init-functions are broken/buggy and falsely report that the daemon does not run (but I doubt that, because other intrepid users don't have this problem). In that case you might replace the pidofproc function in your /lib/lsb/init-functions with this code (version 3.2-20, there are small differences in a few lines which might be the culprit).

pidofproc () {
    local pidfile line i pids= status specified pid
    pidfile=
    specified=
    
    OPTIND=1
    while getopts p: opt ; do
        case "$opt" in
            p)  pidfile="$OPTARG"; specified=1;;
        esac
    done
    shift $(($OPTIND - 1))

    base=${1##*/}
    if [ ! "$specified" ]; then
        pidfile="/var/run/$base.pid"
    fi

    if [ -n "${pidfile:-}" -a -e "$pidfile" ]; then
        read pid < "$pidfile"
        if [ -n "${pid:-}" ]; then
            if $(kill -0 "${pid:-}" 2> /dev/null); then
                echo "$pid"
                return 0
            elif ps "${pid:-}" >/dev/null 2>&1; then
                echo "$pid"
                return 0 # program is running, but not owned by this user
            else
                return 1 # program is dead and /var/run pid file exists
            fi
        fi
    fi
    if [ -x /bin/pidof -a ! "$specified" ]; then
        status="0"
        /bin/pidof -o %PPID -x $1 || status="$?"
        if [ "$status" = 1 ]; then
            return 3 # program is not running
        fi
        return 0
    fi
    return 4 # program or service is unknown
}

Final note: You do not have to and should not delete your blocklists!