Page 64 of 65 FirstFirst ... 145462636465 LastLast
Results 631 to 640 of 650

Thread: General MoBlock thread

  1. #631
    Join Date
    Oct 2009
    Beans
    5

    Re: General MoBlock thread

    Thanks. Just for completeness,


    Code:
    IP_REMOVE="\:192\.168\."

    Has removed fwd filtering issues with my home LAN. I'm still receiving FWD block notices in the logs, which indicate that it's filtering on the other IP, which is what I wanted.

  2. #632
    Join Date
    Jan 2007
    Beans
    762

    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.
    Please post your logfiles and output of commands wrapped in code tags:
    Code:
    [code]output[/code]
    Co-author of PeerGuardian Linux (pgl). Maintainer of the pgl package repositories for Debian and Ubuntu.

  3. #633
    Join Date
    Oct 2012
    Beans
    12

    Re: General MoBlock thread

    Hello, I'm having some trouble getting PeerGuardian Linux to start/run on Ubuntu 12.04 Precise.

    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.

    Here's what the terminal says when I try to update, reload and start:


    Code:
    :~$ sudo pglgui
    [sudo] password for: 
    ** Debug: "/usr/lib/i386-linux-gnu/pgl/pglcmd.defaults" 
    ** Warning: "sni-qt/3365" WARN  16:11:52.243 void StatusNotifierItemFactory::connectToSnw() Invalid interface to SNW_SERVICE 
    ** Debug: Connection to DBus was successful. 
    ** Debug: Executing commands: 
     ("/usr/bin/pglcmd update") 
     
    ** Debug: void ProcessT::executeCommand(const QString&, const QProcess::ProcessChannelMode&, bool) "" 
    ** Debug: Executing commands: 
     ("/usr/bin/pglcmd reload") 
     
    ** Debug: void ProcessT::executeCommand(const QString&, const QProcess::ProcessChannelMode&, bool) "/usr/bin/pglcmd update" 
    ** Debug: Executing commands: 
     ("/usr/bin/pglcmd start") 
     
    ** Debug: void ProcessT::executeCommand(const QString&, const QProcess::ProcessChannelMode&, bool) "/usr/bin/pglcmd reload" 
    ** Debug: "INFO: Started." 
    ** Debug: "ERROR: Error loading /var/lib/pgl/master_blocklist.p2p" 
    ** Debug: "INFO: Blocking 0 IP ranges (0 IPs)." 
    ** Debug: "ERROR: Cannot load the blocklist(s)"

    I saw this thread here:
    http://sourceforge.net/projects/peer.../topic/5461334
    but I got kind of lost at the end there and changing "IP_REMOVE=" didn't do anything for me.

    Then I installed this:
    http://sourceforge.net/projects/peer.../topic/5461334
    and that didn't change anything either.

    Any other ideas I could try?

  4. #634
    Join Date
    Dec 2006
    Beans
    161
    Distro
    Kubuntu Development Release

    Re: General MoBlock thread

    Not sure about the errors but you don't need to run pglgui with sudo, just run as a normal user.

  5. #635
    Join Date
    Jan 2007
    Beans
    762

    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.

    See also https://sourceforge.net/tracker/?fun...roup_id=131687
    Last edited by jre; October 11th, 2012 at 09:26 PM.
    Please post your logfiles and output of commands wrapped in code tags:
    Code:
    [code]output[/code]
    Co-author of PeerGuardian Linux (pgl). Maintainer of the pgl package repositories for Debian and Ubuntu.

  6. #636
    Join Date
    Oct 2012
    Beans
    12

    Re: General MoBlock thread

    @Gavin77 #634:
    Thanks, I'll do that.

    @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!

    ...and the same thing happens when "Reload" is pressed too.

    Code:
    :~$ pglgui
    ** Debug: "/usr/lib/i386-linux-gnu/pgl/pglcmd.defaults" 
    ** Debug: Connection to DBus was successful. 
    ** Warning: bool hasPermissions(const QString&) Could not read from file "/etc/test_file" 
    ** Debug: Executing commands: 
     ("/usr/bin/gksudo "/usr/bin/pglcmd start"") 
     
    ** Debug: void ProcessT::executeCommand(const QString&, const QProcess::ProcessChannelMode&, bool) "" 
    ** Debug: "INFO: Started." 
    ** Debug: "ERROR: Error loading /var/lib/pgl/master_blocklist.p2p" 
    ** Debug: "INFO: Blocking 0 IP ranges (0 IPs)." 
    ** Debug: "ERROR: Cannot load the blocklist(s)" 
    ** Warning: bool hasPermissions(const QString&) Could not read from file "/etc/test_file" 
    ** Debug: Executing commands: 
     ("/usr/bin/gksudo "/usr/bin/pglcmd update"") 
     
    ** Debug: void ProcessT::executeCommand(const QString&, const QProcess::ProcessChannelMode&, bool) "/usr/bin/gksudo "/usr/bin/pglcmd start"" 
    ** Warning: bool hasPermissions(const QString&) Could not read from file "/etc/test_file" 
    ** Debug: Executing commands: 
     ("/usr/bin/gksudo "/usr/bin/pglcmd reload"") 
     
    ** Debug: void ProcessT::executeCommand(const QString&, const QProcess::ProcessChannelMode&, bool) "/usr/bin/gksudo "/usr/bin/pglcmd update"" 
    ** Warning: bool hasPermissions(const QString&) Could not read from file "/etc/test_file" 
    ** Debug: Executing commands: 
     ("/usr/bin/gksudo "/usr/bin/pglcmd restart"") 
     
    ** Debug: void ProcessT::executeCommand(const QString&, const QProcess::ProcessChannelMode&, bool) "/usr/bin/gksudo "/usr/bin/pglcmd reload"" 
    ** Debug: "INFO: Started." 
    ** Debug: "ERROR: Error loading /var/lib/pgl/master_blocklist.p2p" 
    ** Debug: "INFO: Blocking 0 IP ranges (0 IPs)." 
    ** Debug: "ERROR: Cannot load the blocklist(s)"

    Here's the pglcmd.log:

    Code:
    2012-10-11 18:42:50 PDT Begin: pglcmd start
    Building blocklist ...
    WARN: Invalid ASCII line: Binary file standard input matches
    ERROR: Error opening (null) as binary.
    INFO: Blocking 0 IP ranges (0 IPs).
    Blocklist built.
    Inserting iptables ...
    ..Setting up iptables for INPUT:
    ....Creating chain and inserting NFQUEUE rule   ...done.
    ....Whitelisting IP ranges   ...done.
    ....Inserting block rule   ...done.
    ..Setting up iptables for OUTPUT:
    ....Creating chain and inserting NFQUEUE rule   ...done.
    ....Whitelisting ports   ...done.
    ....Whitelisting IP ranges   ...done.
    ....Inserting block rule   ...done.
    ..Setting up iptables for FORWARD:
    ....Creating chain and inserting NFQUEUE rule   ...done.
    ....Inserting block rule   ...done.
    ..Allowing loopback traffic: INPUT OUTPUT   ...done.
    ..Allowing OUTPUT traffic to DNS server 127.0.0.1   ...done.
    ..Allowing FORWARD traffic to DNS server 127.0.0.1   ...done.
    ..Allowing LAN traffic ...
    ....INPUT from 10.0.0.0/24   ...done.
    ....OUTPUT to 10.0.0.0/24   ...done.
    ....FORWARD from 10.0.0.0/24 to 10.0.0.0/24   ...done.
    ..LAN traffic allowed.
    ..Activating chains:
    ....INPUT
    ....OUTPUT
    ....FORWARD
    ..Chains activated.
    Iptables inserted.
    Starting pgld   ...done.
    Starting pglcmd.wd   ...done.
    2012-10-11 18:42:51 PDT End: pglcmd start
    2012-10-11 18:43:01 PDT Begin: pglcmd update
    Automatic blocklist management disabled.
    Problematic daemon status: 1
    * pgld is not running
    2012-10-11 18:46:59 PDT Begin: pglcmd reload
    Problematic daemon status: 1
    * pgld is not running
    2012-10-11 18:47:10 PDT Begin: pglcmd restart
    Stopping pglcmd.wd   ...done.
    Deleting iptables ...
    ..Executing iptables remove script /var/lib/pgl/.pglcmd.iptables.remove.sh   ...done.
    ..Removing iptables remove script /var/lib/pgl/.pglcmd.iptables.remove.sh   ...done.
    Iptables deleted.
    Stopping pgld/sbin/start-stop-daemon: warning: failed to kill 3610: No such process
    ...done.
    Building blocklist ...
    WARN: Invalid ASCII line: Binary file standard input matches
    ERROR: Error opening (null) as binary.
    INFO: Blocking 0 IP ranges (0 IPs).
    Blocklist built.
    Inserting iptables ...
    ..Setting up iptables for INPUT:
    ....Creating chain and inserting NFQUEUE rule   ...done.
    ....Whitelisting IP ranges   ...done.
    ....Inserting block rule   ...done.
    ..Setting up iptables for OUTPUT:
    ....Creating chain and inserting NFQUEUE rule   ...done.
    ....Whitelisting ports   ...done.
    ....Whitelisting IP ranges   ...done.
    ....Inserting block rule   ...done.
    ..Setting up iptables for FORWARD:
    ....Creating chain and inserting NFQUEUE rule   ...done.
    ....Inserting block rule   ...done.
    ..Allowing loopback traffic: INPUT OUTPUT   ...done.
    ..Allowing OUTPUT traffic to DNS server 127.0.0.1   ...done.
    ..Allowing FORWARD traffic to DNS server 127.0.0.1   ...done.
    ..Allowing LAN traffic ...
    ....INPUT from 10.0.0.0/24   ...done.
    ....OUTPUT to 10.0.0.0/24   ...done.
    ....FORWARD from 10.0.0.0/24 to 10.0.0.0/24   ...done.
    ..LAN traffic allowed.
    ..Activating chains:
    ....INPUT
    ....OUTPUT
    ....FORWARD
    ..Chains activated.
    Iptables inserted.
    Starting pgld   ...done.
    Starting pglcmd.wd   ...done.
    2012-10-11 18:47:11 PDT End: pglcmd restart
    pglcmd.wd: pgld is not running!
    The watchdog detected that the daemon is not running.
    To disable the watchdog set WATCHDOG="0" in /etc/pgl/pglcmd.conf.
    Now doing a restart:
    * Restarting only PeerGuardian Linux pgld
    
    2012-10-11 18:52:11 PDT Begin: pglcmd restart_not_wd
    Deleting iptables ...
    ..Executing iptables remove script /var/lib/pgl/.pglcmd.iptables.remove.sh   ...done.
    ..Removing iptables remove script /var/lib/pgl/.pglcmd.iptables.remove.sh   ...done.
    Iptables deleted.
    Stopping pgld/sbin/start-stop-daemon: warning: failed to kill 4519: No such process
    ...done.
    Inserting iptables ...
    ..Setting up iptables for INPUT:
    ....Creating chain and inserting NFQUEUE rule   ...done.
    ....Whitelisting IP ranges   ...done.
    ....Inserting block rule   ...done.
    ..Setting up iptables for OUTPUT:
    ....Creating chain and inserting NFQUEUE rule   ...done.
    ....Whitelisting ports   ...done.
    ....Whitelisting IP ranges   ...done.
    ....Inserting block rule   ...done.
    ..Setting up iptables for FORWARD:
    ....Creating chain and inserting NFQUEUE rule   ...done.
    ....Inserting block rule   ...done.
    ..Allowing OUTPUT traffic to DNS server 127.0.0.1   ...done.
    ..Allowing FORWARD traffic to DNS server 127.0.0.1   ...done.
    ..Allowing LAN traffic ...
    ....INPUT from 10.0.0.0/24   ...done.
    ....OUTPUT to 10.0.0.0/24   ...done.
    ....FORWARD from 10.0.0.0/24 to 10.0.0.0/24   ...done.
    ..LAN traffic allowed.
    ..Activating chains:
    ....INPUT
    ....OUTPUT
    ....FORWARD
    ..Chains activated.
    Iptables inserted.
    Starting pgld   ...done.
    Starting pglcmd.wd   ...done.
    2012-10-11 18:52:12 PDT End: pglcmd restart_not_wd
    ...done.
    Warning: sendmail not found.
    Check the SENDMAIL setting.
    * /var/run/pglcmd.wd.pid already exists, not starting pglcmd.wd again

    Here's the pglcmd.log:
    Code:
    Oct 11 18:42:51 INFO: Connected to dbus system bus.
    Oct 11 18:42:51 INFO: Started.
    Oct 11 18:42:51 ERROR: Error loading /var/lib/pgl/master_blocklist.p2p
    Oct 11 18:42:51 INFO: Blocking 0 IP ranges (0 IPs).
    Oct 11 18:42:51 ERROR: Cannot load the blocklist(s)
    Oct 11 18:47:11 INFO: Connected to dbus system bus.
    Oct 11 18:47:11 INFO: Started.
    Oct 11 18:47:11 ERROR: Error loading /var/lib/pgl/master_blocklist.p2p
    Oct 11 18:47:11 INFO: Blocking 0 IP ranges (0 IPs).
    Oct 11 18:47:11 ERROR: Cannot load the blocklist(s)
    Oct 11 18:52:12 INFO: Connected to dbus system bus.
    Oct 11 18:52:12 INFO: Started.
    Oct 11 18:52:12 ERROR: Error loading /var/lib/pgl/master_blocklist.p2p
    Oct 11 18:52:12 INFO: Blocking 0 IP ranges (0 IPs).
    Oct 11 18:52:12 ERROR: Cannot load the blocklist(s)
    And here's the terminal after trying "sudo pglcmd force-reload":
    Code:
    :~$ sudo pglcmd force-reload
    [sudo] password for: 
     * 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.

  7. #637
    Join Date
    Oct 2012
    Beans
    12

    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"

  8. #638
    Join Date
    Jan 2007
    Beans
    762

    Re: General MoBlock thread

    No problem with the duplicate. That was more a notice for me and other readers.

    You have to do the "sudo pglcmd force-reload" in a terminal. This command does more than a "reload" in pglgui.
    Please post your logfiles and output of commands wrapped in code tags:
    Code:
    [code]output[/code]
    Co-author of PeerGuardian Linux (pgl). Maintainer of the pgl package repositories for Debian and Ubuntu.

  9. #639
    Join Date
    Oct 2012
    Beans
    12

    Re: General MoBlock thread

    @jre #638
    Hi, and thanks for your response! I tried a variety of command orders because I wasn't sure exactly how it should be done. I also did "sudo pglcmd force-reload" in the terminal each time.

    Here's the terminal for "sudo pglcmd force-reload" then "pglgui", then "Start" (start button in the GUI):

    Code:
    :~$ sudo pglcmd force-reload
    [sudo] password for: 
     * Reloading PeerGuardian Linux pgld                                     [ OK ] 
    :~$ pglgui
    ** Debug: "/usr/lib/i386-linux-gnu/pgl/pglcmd.defaults" 
    ** Debug: Connection to DBus was successful. 
    ** Warning: bool hasPermissions(const QString&) Could not read from file "/etc/test_file" 
    ** Debug: Executing commands: 
     ("/usr/bin/gksudo "/usr/bin/pglcmd start"") 
     
    ** Debug: void ProcessT::executeCommand(const QString&, const QProcess::ProcessChannelMode&, bool) "" 
    ** Debug: "INFO: Started." 
    ** Debug: "ERROR: Error loading /var/lib/pgl/master_blocklist.p2p" 
    ** Debug: "INFO: Blocking 0 IP ranges (0 IPs)." 
    ** Debug: "ERROR: Cannot load the blocklist(s)"

    pglcmd.log after "sudo pglcmd force-reload":

    Code:
    2012-10-12 11:59:17 PDT Begin: pglcmd force-reload
    pgld is not running, doing nothing.
    2012-10-12 11:59:17 PDT End: pglcmd force-reload
    2012-10-12 11:59:57 PDT Begin: pglcmd start
    Inserting iptables ...
    ..Setting up iptables for INPUT:
    ....Creating chain and inserting NFQUEUE rule   ...done.
    ....Whitelisting IP ranges   ...done.
    ....Inserting block rule   ...done.
    ..Setting up iptables for OUTPUT:
    ....Creating chain and inserting NFQUEUE rule   ...done.
    ....Whitelisting ports   ...done.
    ....Whitelisting IP ranges   ...done.
    ....Inserting block rule   ...done.
    ..Setting up iptables for FORWARD:
    ....Creating chain and inserting NFQUEUE rule   ...done.
    ....Inserting block rule   ...done.
    ..Allowing loopback traffic: INPUT OUTPUT   ...done.
    ..Allowing OUTPUT traffic to DNS server 127.0.0.1   ...done.
    ..Allowing FORWARD traffic to DNS server 127.0.0.1   ...done.
    ..Allowing LAN traffic ...
    ....INPUT from 10.0.0.0/24   ...done.
    ....OUTPUT to 10.0.0.0/24   ...done.
    ....FORWARD from 10.0.0.0/24 to 10.0.0.0/24   ...done.
    ..LAN traffic allowed.
    ..Activating chains:
    ....INPUT
    ....OUTPUT
    ....FORWARD
    ..Chains activated.
    Iptables inserted.
    Starting pgld   ...done.
    Starting pglcmd.wd   ...done.
    2012-10-12 11:59:59 PDT End: pglcmd start


    pglcmad.log for "sudo pglcmd force-reload" alone:

    Code:
    2012-10-12 12:27:36 PDT Begin: pglcmd force-reload
    pgld is not running, doing nothing.
    2012-10-12 12:27:36 PDT End: pglcmd force-reload

    terminal:

    Code:
    :~$ sudo pglcmd force-reload
    [sudo] password for:
     * Reloading PeerGuardian Linux pgld                                    [ OK ]




    "sudo pglcmd force-reload" after pgl was started:


    pglcmad.log for "sudo pgld start", then "sudo pglcmd force-reload":

    Code:
    2012-10-12 12:29:03 PDT Begin: pglcmd force-reload
    Problematic daemon status: 1
    * pgld is not running                                     [ OK ]

    Code:
    terminal:
    :~$ sudo pgld start
    :~$ sudo pglcmd force-reload
     * Reloading PeerGuardian Linux pgld                                     [fail]

    pglcmd.log for "pglgui", "pglcmd start", "sudo pglcmd force-reload":

    Code:
    2012-10-12 12:36:09 PDT End: pglcmd start
    2012-10-12 12:36:32 PDT Begin: pglcmd force-reload
    Problematic daemon status: 1
    * pgld is not running

    I hope this helps and was done correctly. If I needed to do the commands in a different order or try something entirely different, please let me know, I'm still learning too. Thank you!

  10. #640
    Join Date
    Jan 2007
    Beans
    762

    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.

    Good luck!
    Last edited by jre; October 14th, 2012 at 04:05 PM.
    Please post your logfiles and output of commands wrapped in code tags:
    Code:
    [code]output[/code]
    Co-author of PeerGuardian Linux (pgl). Maintainer of the pgl package repositories for Debian and Ubuntu.

Page 64 of 65 FirstFirst ... 145462636465 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •