I will gladly help you
The other good news is that jimtb, the upstream author, might find time again in two months. And I think a project like mobloquer would profit my several authors. There are many tasks to be done.

__________________
Maintainer of http://moblock-deb.sourceforge.net: MoBlock, mobloquer, blockcontrol and NFBlock Debian packages.
Author of blockcontrol, previously moblock-control.

Hey there,

Mobloquer is great. Thanks!

One thing though. How do I get the Whois lookup working?

When I click the 'More Information' button on the Logs page it tries to look up the IP but always comes back with "Failed to get Whois data". Any ideas?

Cheers, and thanks once again for all the great work.

Probably whois is blocked by Moblock. Is there a new entry of a blocked IP in the logfile, whenever you try it?
If yes, then you can either whitelist that IP or the whois port. I'd recommend to whitelist the IP, because there shouldn't be many whois server, so it would be overkill to whitelist the port.

__________________
Maintainer of http://moblock-deb.sourceforge.net: MoBlock, mobloquer, blockcontrol and NFBlock Debian packages.
Author of blockcontrol, previously moblock-control.

Hi jre,

thanks for the response.

There is no new entry in the log file when I try to use the "More Informaiton" (Whois tool). I have also tried with my firewalls disabled but no luck.

Any other suggestions?

Cheers

I've been using Mobloquer in Ubuntu for quite awhile, love it. I've a problem that's started recently though. Multiple instances are starting on account-login. Sometimes it's three, sometimes two. They all function appropriately, I just exit until I'm down to a single instance.

I recently upgraded from Hardy to Jaunty but the problem seemed to begin days, or even weeks, afterwords so I don't believe this is the cause.

Any ideas?

Scratch that.

I "solved the problem" by closing all instances of Mobloquer and choosing system > sessions > "automatically remember running applications when logging out." So I logged out without any instances running, and upon logging back in I found only one instance running. lol

Whatever bug this is (upon re-thinking, I highly doubt it's yours or Mobloquer's), it's amusing if nothing else.

So you had "remember all running applications and start them again" and "automatically start mobloquer" in your graphical user session!?
Perhaps this should be handled more intelligently by your graphical user session. But mobloquer can do this, too. There was code in mobloquer which prevented multiple instances of mobloquer running. Unfortunately it was implemented incorrectly (so that it only worked for root). I removed that, because I saw no reason for it at all, instead of fixing it. Now, that you gave me a reason I might readd it and fix it.

__________________
Maintainer of http://moblock-deb.sourceforge.net: MoBlock, mobloquer, blockcontrol and NFBlock Debian packages.
Author of blockcontrol, previously moblock-control.