Re: General MoBlock thread

Good.

I know (tm) that its working correctly. Generally, when working with FORWARD you should always check if traffic with source from the web (to your LAN) and destination to the web (from your LAN) is checked.

Re: General MoBlock thread

I just jumped from Ubuntu 10.10 to 12.04 and I'm still trying to get the hang of it (for your information).

I've installed Moblock several times successfully on older Ubuntu distros but I'm stuck on PeerGuardian Linux this time. If I understand correctly, my problem is this error:
ERROR: Error loading /var/lib/pgl/master_blocklist.p2p.

Re: General MoBlock thread

(Sorry I'm quite busy currently, answers may take a few days)

Try a "sudo pglcmd force-reload" to get new versions of all blocklists. (This rules out a corrupted blocklist.)

If you still have problems afterwards post your logfiles /var/log/pglcmd.log and /var/log/pgld.log (I don't need the parts before the force-reload). Maybe also the output of "pglcmd show_config" is necessary.

Re: General MoBlock thread

@jre #635:
First of all, thank you for helping make this great program! And also thank you for taking the time to help out so many people with it too.

Yeah, sorry about the duplicate entries. I wanted to post here only but for some reason I couldn't find this thread for a few days.

In pglgui I pressed "Start", then "Update" and I get this error pop-up:

One or more commands(s) failed to ececute.
You can check below the commands that failed and their output.
You can also check pgld's and/or pglcmd's log through the view menu.
Command:
/usr/bin/gksudo "/usr/bin/pglcmd update"
Output: *Updating blocklists and reloading PeerGuardian Linux pgld ...fail!

Some additional info:
After I press "Start" and "Update" in the pglgui, I cannot connect to any websites using my browser anymore, however, I can still run Ubuntu updates for some reason (Yet I can't load Ubuntu.com in Firefox...) and I have ports 80 and 443 allowed for outbound only. Running "pglcmd stop" makes the traffic go through again. I haven't tried whitelisting LAN addresses or anything like that yet, I'll work on that next. I'm not asking how to fix this, just want to tell you it's behavior.

I'm also using the same exact blocklists [files] I used with Moblock just a few weeks ago and I keep them in my home folder. They are also .gz format. I don't know if any of this may make a difference or not, just trying to give you as much info as possible.

Thanks for the ideas; if there's anything else I can try or information I could provide, I would be happy to.

Re: General MoBlock thread

Edit: Just adding the pglcmd.conf file I forgot to earlier [using the edit buttons in my own post did not work...]:

Code:

# pglcmd.conf - configuration file for pglcmd
# This file is sourced by a shell script. Any line which starts with a # (hash)
# is a comment and is ignored. If you set the same variable several times,
# then only the last line will be used.
# Refer to pglcmd.defaults (/usr/lib/pgl/pglcmd.defaults)
# for the complete set of possible configuration variables with comments.
# Do a "pglcmd restart" (sometimes even "reload" is enough) when you have
# edited this file.
WHITE_TCP_OUT="80 443"
INIT="0"
CRON="0"

Re: General MoBlock thread

Ah, sorry, force-reload doesn't work if pgl isn't running ...

Let's do it manually:

Code:

sudo pglcmd stop
sudo rm -rf /var/spool/pgl/
sudo pglcmd start

This way we remove all previously downloaded blocklists (I guess one of them is somehow corrupted, and causes these problems). They get redownloaded on "start" (which will therefore take a few minutes, depending on your internet connection).

I guess the problems will be solved than. If not, post again the current log and your /etc/pgl/blocklists.list.