Page 70 of 120 FirstFirst ... 2060686970717280 ... LastLast
Results 691 to 700 of 1196

Thread: Moblock (peerguardian linux alternative)

  1. #691
    Join Date
    Nov 2005
    Location
    Scandinavia
    Beans
    937

    Re: Moblock (peerguardian linux alternative)

    tank you, daradib!
    - "though It seems that I know that I know, what I would like to see Is the I that sees me, when I know that I know that I know" / Alan Watts

  2. #692
    Join Date
    Apr 2006
    Beans
    48
    Distro
    Ubuntu 9.04 Jaunty Jackalope

    Re: Moblock (peerguardian linux alternative)

    Hmm, in Gutsy it doesn't seem to work. I'm using the deb repo from the moblock-deb site

    Testing MoBlock: trying to ping 3.0.0.0 from /etc/moblock/guarding.p2p ...
    * MoBlock did not block the IP. Test failed.

  3. #693
    Join Date
    Aug 2007
    Beans
    19
    Distro
    Ubuntu 9.04 Jaunty Jackalope

    Re: Moblock (peerguardian linux alternative)

    well, I just gave up and upgraded to Feisty. Now moblock starts and stops with no problems. Everything seems to be working great! So if you have edgy...just upgrade



    Quote Originally Posted by lucis
    * MoBlock did not block the IP. Test failed.
    btw, if you whitelist http/https the test WILL fail. Those must not be whitelisted if you want the test to work.
    Last edited by draggy; October 1st, 2007 at 04:18 PM.

  4. #694
    Join Date
    Jan 2007
    Beans
    770

    Re: Moblock (peerguardian linux alternative)

    Hey, I also have a real live, so I can't spend as much time with answering and fixing bux etc as I'd like to ...

    General: If you are experimenting or have some problems: If you want to reinstall then first purge (not remove) moblock.

    Quote Originally Posted by draggy View Post
    btw, if you whitelist http/https the test WILL fail. Those must not be whitelisted if you want the test to work.
    No, the test is based on ping and does not use these whitelisted ports. The test will work with these ports whitelisted.

    following my comments to the last posts. If you miss something then please remind me.


    draggy/ordou [edgy doesn't work; update to feisty helps]
    I guess that you have problems (a bug) with the lsb init-functions in edgy (in packet "lsb-base"). Those are responsible for starting moblock. Solving the edgy problems doesn't have high priority. But I'm working on an all distribution version, not only Debian and Ubuntu ...


    lucis (gutsy) [moblock-control test does not succeed]:
    but moblock is running? please post the output of "moblock-control status"
    Also, the test function might gice wrong results e.g. if moblock blocks many other things the same time. So do in another terminal an "tail -f /var/log/moblock.log" and see what's happening.


    daradib:
    thanks for the packages. I added the nfq version on the homepage. Also, feel free to do the PPA thing. Just heard of it and it sounds very interesting, but I haven't enough time to start this now (just made a bookmark on it). Also, personally I'm using Debian, not Ubuntu. Fell free to do it.


    jamesford:
    dude, just look at the moblock-deb homepage for instructions to make (amd64) packages
    But daradib already did it.

    feld:
    [initial update took long time and resulted in empty blocklist; manual update works]
    I'll look into this bug later and will add some status message on install. Thx

    LordKelvan:
    Yes, MoBlock_nfq.sh is NOT used in the debian packages. You have to do all configuration in moblock.conf.

    Neovos [firehol problems]:
    Can anybody confirm that moblock (new deb version 0.8-21) and firehol don't work together? I can't imagine why this should stop working.

    quixotic-cynic:
    so many thx for your work.
    Just: "/etc/init.d/moblock COMMAND" is old. Always use "moblock-control COMMAND" instead.

    pelle:
    I think in Debian it's recommended to use aptitude instead of apt-get. But that's really unimportant THX!


    Greets to all
    jre
    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.

  5. #695
    Join Date
    Aug 2007
    Beans
    19
    Distro
    Ubuntu 9.04 Jaunty Jackalope

    Re: Moblock (peerguardian linux alternative)

    Quote Originally Posted by jre
    No, the test is based on ping and does not use these whitelisted ports.
    I tried it again, and it started failing (again). So I messed with it, reloaded it, checked the status, tested it, and it would always fail.

    Then I did a update, and a reloaded (this is what I had done before to get it to work) and ran two tests, and they both succeed. Why would I need to update, and reload it for the test to work?

  6. #696
    Join Date
    Nov 2005
    Location
    Scandinavia
    Beans
    937

    Re: Moblock (peerguardian linux alternative)

    Well, that was a mouthfull!
    Man am i happy you guys are helping out. (not that i've been *that* active lately, but anyway...)

    Neovos [firehol problems]:
    Can anybody confirm that moblock (new deb version 0.8-21) and firehol don't work together? I can't imagine why this should stop working.
    Sure thing.
    It's firehol that is broken, nothing else. There's nothing about it in launchpad so i guess i'll have to file a bug. (god i hate launchpad. maybe it's gotten better than the last time i used it?...)
    - "though It seems that I know that I know, what I would like to see Is the I that sees me, when I know that I know that I know" / Alan Watts

  7. #697

    Re: Moblock (peerguardian linux alternative)

    Quote Originally Posted by draggy View Post
    I tried it again, and it started failing (again). So I messed with it, reloaded it, checked the status, tested it, and it would always fail.
    Not an answer to your main question, but when you reload (and it fails) does it still occur if you replace the reload with a separate start command and stop command?

    I.e. changing
    Code:
    moblock-control restart
    to
    Code:
    sudo moblock-control stop
    sudo moblock-control start
    I had an issue recently that was simmilar and I was wondering if your issue behaves in the same way as my one did... if I autoloaded moblock or started it from my openbox menu it would not work. Reloading didn't fix it but for some reason stopping/starting did... it was weird.
    -- quixotic-cynic

  8. #698
    Join Date
    Aug 2007
    Beans
    19
    Distro
    Ubuntu 9.04 Jaunty Jackalope

    Re: Moblock (peerguardian linux alternative)

    Now I can't seem to get it to test successfully at all anymore

    Code:
    sudo moblock-control test
    Testing MoBlock: trying to ping 3.0.0.0 from /etc/moblock/guarding.p2p ...
     * MoBlock did not block the IP. Test failed.
    sudo moblock-control stop
    Stopping MoBlock   ...done.
    sudo moblock-control start
    Starting MoBlock   ...done.
    sudo moblock-control test
    Testing MoBlock: trying to ping 3.0.0.0 from /etc/moblock/guarding.p2p ...
     * MoBlock did not block the IP. Test failed.
    sudo moblock-control update
    Updating blocklists and reloading MoBlock if any blocklist was updated   ...done.
    sudo moblock-control test
    Testing MoBlock: trying to ping 3.0.0.0 from /etc/moblock/guarding.p2p ...
     * MoBlock did not block the IP. Test failed.
    sudo moblock-control reload
    Reloading MoBlock   ...done.
    sudo moblock-control test
    Testing MoBlock: trying to ping 3.0.0.0 from /etc/moblock/guarding.p2p ...
     * MoBlock did not block the IP. Test failed.
    sudo moblock-control update
    Updating blocklists and reloading MoBlock if any blocklist was updated   ...done.
    sudo moblock-control reload
    Reloading MoBlock   ...done.
    sudo moblock-control test
    Testing MoBlock: trying to ping 3.0.0.0 from /etc/moblock/guarding.p2p ...
     * MoBlock did not block the IP. Test failed.

    This is what the log says most recently:
    But most of the log file consists of skipping useless ranges, whatever that means.
    Code:
    tail /var/log/moblock.log
    Skipping useless range: (050326) Unassigned 33437
    Ranges loaded: 241839
    Reopening logfile.
    Blocked IN: tzulo, inc,hits: 1,SRC: 208.77.17.4
    Blocked OUT: Bogon,hits: 1,DST: 76.10.160.164
    Blocked IN: tzulo, inc,hits: 2,SRC: 208.77.17.4
    Blocked OUT: GAMES-BEZEQINT,hits: 1,DST: 212.179.109.105
    Blocked OUT: General Electric Company,hits: 1,DST: 3.0.0.0
    Blocked OUT: GAMES-BEZEQINT,hits: 2,DST: 212.179.109.105
    Blocked OUT: GAMES-BEZEQINT,hits: 3,DST: 212.179.109.105
    It looks like it's blocking ips, so why doesn't the test work correctly?


    here's my status
    Code:
    Current iptables rules (this may take awhile):
    
    Chain INPUT (policy ACCEPT)
    target     prot opt source               destination
    RETURN     0    --  anywhere             anywhere
    moblock_in  0    --  anywhere             anywhere            state NEW
    
    Chain FORWARD (policy ACCEPT)
    target     prot opt source               destination
    moblock_fw  0    --  anywhere             anywhere            state NEW
    
    Chain OUTPUT (policy ACCEPT)
    target     prot opt source               destination
    RETURN     0    --  anywhere             anywhere
    moblock_out  0    --  anywhere             anywhere            state NEW
    
    Chain moblock_fw (1 references)
    target     prot opt source               destination
    NFQUEUE    0    --  anywhere             anywhere            NFQUEUE num 0
    
    Chain moblock_in (1 references)
    target     prot opt source               destination
    RETURN     tcp  --  anywhere             anywhere            tcp dpt:8888
    RETURN     tcp  --  anywhere             anywhere            tcp dpt:ssh
    NFQUEUE    0    --  anywhere             anywhere            NFQUEUE num 0
    
    Chain moblock_out (1 references)
    target     prot opt source               destination
    RETURN     tcp  --  anywhere             anywhere            tcp dpt:8888
    RETURN     tcp  --  anywhere             anywhere            tcp dpt:ssh
    NFQUEUE    0    --  anywhere             anywhere            NFQUEUE num 0
    
    Please check if the above printed iptables rules are correct!
    
     * moblock is running, pid is 9093.

  9. #699
    Join Date
    Sep 2007
    Beans
    8

    Re: Moblock (peerguardian linux alternative)

    I think I have the same test failure problem as above guy.
    Doing "moblock-control test" outputs FAILURE in 9 out of 10 times.
    And sometimes like 1 out of 10 times I get SUCCESS. And it's the same test ip What's going on man, Is it on or off??

  10. #700
    Join Date
    Nov 2005
    Location
    Scandinavia
    Beans
    937

    Re: Moblock (peerguardian linux alternative)

    Listen people, as jre has told us before, the "test" isn't foolproof in it's design. Let me show you why;
    Blocked OUT: General Electric Company,hits: 1,DST: 3.0.0.0
    Blocked OUT: GAMES-BEZEQINT,hits: 2,DST: 212.179.109.105
    Blocked OUT: GAMES-BEZEQINT,hits: 3,DST: 212.179.109.105
    See, ip "3.0.0.0" *was* blocked, but i guess ip "212.179.109.105" was hammering you so fast that the script (that checks the *last* line in the log file) didn't catch the result of a succesful block...
    - "though It seems that I know that I know, what I would like to see Is the I that sees me, when I know that I know that I know" / Alan Watts

Page 70 of 120 FirstFirst ... 2060686970717280 ... 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
  •