Page 91 of 120 FirstFirst ... 41818990919293101 ... LastLast
Results 901 to 910 of 1196

Thread: Moblock (peerguardian linux alternative)

  1. #901
    Join Date
    Jan 2007
    Beans
    762

    Re: Moblock (peerguardian linux alternative)

    Quote Originally Posted by yahooadam View Post
    Code:
    adam@Server1:~/.scripts$ cat /etc/moblock/moblock.conf | grep "IP_REMOVE"
    #IP_REMOVE="Bogon;General Electric Company;4.2.162.144-4.2.162.151"
    IP_REMOVE="72.55.129.46"
    adam@Server1:~/.scripts$ ping yi.org
    PING yi.org (72.55.129.46) 56(84) bytes of data.
    
    --- yi.org ping statistics ---
    5 packets transmitted, 0 received, 100% packet loss, time 4001ms
    What am i doing wrong?
    The IP_REMOVE works with "grep" ["try "man grep" to learn more], so it has to match exactly (in parts) lines of your blocklist. But the IP you inserted is not noted down in the blocklist explicitly, only as part of a bigger range.

    Alternatively you can directly whitelist IPs, e.g.
    IP_TCP_OUT="72.55.129.46"
    (also check the IN/FORWARD and the UDP entries, depending on your needs).
    If you need help for this I need to know why you want to whitelist the IP
    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.

  2. #902
    Join Date
    Apr 2007
    Beans
    33

    Re: Moblock (peerguardian linux alternative)

    yi.org is a dynDNS provider, i have no idea why they are even blocked

    it uses ez-ipupdate with the gnudip2 protocol to update your list of IP's

    Code:
    # This section works only for IPTABLES_SETTINGS="1"
    # Do a "moblock-control restart" when you have changed these settings.
    
    IP_TCP_IN="72.55.129.46"
    IP_UDP_IN="72.55.129.46"
    IP_TCP_OUT="72.55.129.46"
    IP_UDP_OUT="72.55.129.46"
    IP_TCP_FORWARD="72.55.129.46"
    IP_UDP_FORWARD="72.55.129.46"
    Ive tried that, and i still cant get a ping response (and yes, i did restart moblock)

    I just want that IP to be whitelisted, is that possible?

    Thanks for any help

  3. #903
    Join Date
    Jun 2007
    Beans
    1

    Re: Moblock (peerguardian linux alternative)

    I am getting the problem where I run the command

    Code:
    moblock-control test

    and then I get:

    Code:
    Testing MoBlock: head: cannot open `/etc/moblock/guarding.p2p' for reading: No such file or directory
    trying to ping  from /etc/moblock/guarding.p2p ...
     * Some error occured with ping, no test result.
    I tried uninstalling moblock and reinstalling using this method:

    Code:
    aptitude purge moblock-nfq; aptitude install moblock-nfq

    There were some errors, but it tried again a few times and ended without errors at the finish. I tried starting moblock and updating and reloading it and it seems to work fine. I get the impression that the guarding.p2p file is just a test ip that it blocks to see if its being blocked, so if no solutions seem to work, would someone mind sharing the contents of that file?

  4. #904
    Join Date
    Apr 2007
    Beans
    33

    Re: Moblock (peerguardian linux alternative)

    guarding.p2p is the blocklist, without it, moblock will be quite useless

    try moblock-control update

  5. #905
    Join Date
    Feb 2007
    Beans
    48

    Re: Moblock (peerguardian linux alternative)

    I've been using moblock for a log time now, and I just got a new laptop so I wanted to put moblock on it, but it won't fully install.....it looks like it cant download any of the lists right after the installation during the update....does anyone know if the bluetack site is down or something....this is the logfile output when I try to install


    Code:
    2007-11-28 12:27:23 PM EST Begin: /usr/bin/moblock-control update
    Updating blocklists ...
    Updating ads-trackers-and-bad-pr0n.gzstat: cannot stat `ads-trackers-and-bad-pr0n.gz': No such file or directory
    /usr/bin/moblock-control: line 412: [: -gt: unary operator expected
     * . No update available.
    Updating bogon.gzstat: cannot stat `bogon.gz': No such file or directory
    /usr/bin/moblock-control: line 412: [: -gt: unary operator expected
     * . No update available.
    Updating dshield.gzstat: cannot stat `dshield.gz': No such file or directory
    /usr/bin/moblock-control: line 412: [: -gt: unary operator expected
     * . No update available.
    Updating hijacked.gzstat: cannot stat `hijacked.gz': No such file or directory
    /usr/bin/moblock-control: line 412: [: -gt: unary operator expected
     * . No update available.
    Updating iana-multicast.gzstat: cannot stat `iana-multicast.gz': No such file or directory
    /usr/bin/moblock-control: line 412: [: -gt: unary operator expected
     * . No update available.
    Updating iana-private.gzstat: cannot stat `iana-private.gz': No such file or directory
    /usr/bin/moblock-control: line 412: [: -gt: unary operator expected
     * . No update available.
    Updating iana-reserved.gzstat: cannot stat `iana-reserved.gz': No such file or directory
    /usr/bin/moblock-control: line 412: [: -gt: unary operator expected
     * . No update available.
    Updating level1.gzstat: cannot stat `level1.gz': No such file or directory
    /usr/bin/moblock-control: line 412: [: -gt: unary operator expected
     * . No update available.
    Updating level2.gzstat: cannot stat `level2.gz': No such file or directory
    /usr/bin/moblock-control: line 412: [: -gt: unary operator expected
     * . No update available.
    Updating Microsoft.gzstat: cannot stat `Microsoft.gz': No such file or directory
    /usr/bin/moblock-control: line 412: [: -gt: unary operator expected
     * . No update available.
    Updating rangetest.gzstat: cannot stat `rangetest.gz': No such file or directory
    /usr/bin/moblock-control: line 412: [: -gt: unary operator expected
     * . No update available.
    Updating spider.gzstat: cannot stat `spider.gz': No such file or directory
    /usr/bin/moblock-control: line 412: [: -gt: unary operator expected
     * . No update available.
    Updating spyware.gzstat: cannot stat `spyware.gz': No such file or directory
    /usr/bin/moblock-control: line 412: [: -gt: unary operator expected
     * . No update available.
    Updating templist.gzstat: cannot stat `templist.gz': No such file or directory
    /usr/bin/moblock-control: line 412: [: -gt: unary operator expected
     * . No update available.
    Updating trojan.gzstat: cannot stat `trojan.gz': No such file or directory
    /usr/bin/moblock-control: line 412: [: -gt: unary operator expected
     * . No update available.
     * Blocklists updated.
    Building blocklist * Error 6: www.bluetack.co.uk/config/ads-trackers-and-bad-pr0n.gz not available. Check your /etc/moblock/blocklists.list and try a "moblock-control update" first. Aborting!

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

    Re: Moblock (peerguardian linux alternative)

    It *is* indeed down. I'm afraid it might (i'm not really sure) be bëcause of this (i've posted this before, people);

    Dear members and guests,

    Regretfully we need to let you all know that in one weeks time the site may be closing indefinitely. Our web hosting bill is currently 3 months behind and without this server in operation there will also be no more blocklist updates possible.

    We ask you to make a choice and decide on our future. If you want to help keep us alive then we need your support and donations.

    There are literally millions of people downloading our files, however only a very small proportion of people find the time to invest anything in return to ensure that our free services can continue.

    Everything we do here is offered free of charge, we make absolutely no money whatsoever. We do however spend quite a lot of time to keep everything running as best as we can for your benefit.

    In the event that we cannot afford to continue offering our services for free, then we may need to consider introducing a small subscription/fee based service for downloading the blocklist updates and possibly looking towards using ads throughout the site.

    We also need more server mirrors to cope with the excessive bandwidth/traffic associated with hosting the lists.

    So now you can either choose to do nothing and let BISS die or help support us so that we can continue to support you. If you find any value in our free programs and services here then please consider donating.

    The choice is now yours.

    Our donation page is here :
    http://www.bluetack.co.uk/donate/index.html
    - "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. #907
    Join Date
    Jan 2007
    Beans
    762

    Re: Moblock (peerguardian linux alternative)

    Quote Originally Posted by yahooadam View Post
    yi.org is a dynDNS provider, i have no idea why they are even blocked

    it uses ez-ipupdate with the gnudip2 protocol to update your list of IP's

    Code:
    # This section works only for IPTABLES_SETTINGS="1"
    # Do a "moblock-control restart" when you have changed these settings.
    
    IP_TCP_IN="72.55.129.46"
    IP_UDP_IN="72.55.129.46"
    IP_TCP_OUT="72.55.129.46"
    IP_UDP_OUT="72.55.129.46"
    IP_TCP_FORWARD="72.55.129.46"
    IP_UDP_FORWARD="72.55.129.46"
    Ive tried that, and i still cant get a ping response (and yes, i did restart moblock)

    I just want that IP to be whitelisted, is that possible?
    ok, first I think IP_TCP_OUT="72.55.129.46" should be enough, but it won't hurt you to use more entries.

    Now, I can't imagine that you can't ping this IP. Please post your iptables rules (just do a "moblock-control status"). There should be the entries for this IP.
    If not, please check the last "start" section in /var/log/moblock-control.log for iptables errors.
    Also check /var/log/moblock.log to see if the IP is really blocked by moblock.
    If it's not blocked by moblock you can try "traceroute 72.55.129.46" to see where the ping gets stopped.

    Alternatively, (I just had a look at guarding.p2p) you can use this entry:
    Code:
    IP_REMOVE="Groupe iWeb Technologies inc:72.55.128.0-72.55.191.255"
    greets
    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.

  8. #908
    Join Date
    Nov 2005
    Location
    Scandinavia
    Beans
    937

    Re: Moblock (peerguardian linux alternative)

    Ok, so i double checked at phoenix labs forums, and bluetack is apparently safe for now (last minute donations), and they are working on getting the site up again.
    Still, you really should consider donating some money. Maybe that would also not only save bluetack, but also give more reliable blocklist transfers and updates in the future (they need new servers).
    - "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

  9. #909
    Join Date
    Feb 2007
    Beans
    48

    Re: Moblock (peerguardian linux alternative)

    sorry, I didnt see that you had posted that already......yeah I was actually about to donate a little bit of cash, its the least we can do considering priceless service that they provide us....with out them the feds would have surely been knocking on my door ages ago.

  10. #910
    Join Date
    Nov 2006
    Beans
    38

    Re: Moblock (peerguardian linux alternative)

    Hm, I've got moblock installed (gutsy 64), but it is not passing it's test:

    Code:
    sudo moblock-control test
    Testing MoBlock: trying to ping 4.18.162.102 from /etc/moblock/guarding.p2p ...
     * MoBlock did not block the IP, however 4.18.162.102 did not answer.
     * 
     * Maybe 4.18.162.102 is down/doesn't answer to pings
     * or your firewall filtered the ping.
     * 
     * Have a look at "/usr/bin/moblock-control status" and do some manual testing.
    Here is the output of the status command
    Code:
     sudo moblock-control status
    Current iptables rules (this may take awhile):
    
    Chain INPUT (policy DROP 6 packets, 3194 bytes)
     pkts bytes target     prot opt in     out     source               destination         
        0     0 ACCEPT     0    --  lo     *       0.0.0.0/0            0.0.0.0/0           
        0     0 ACCEPT     0    --  lo     *       0.0.0.0/0            0.0.0.0/0           
        0     0 ACCEPT     tcp  --  *      *       10.0.0.2             0.0.0.0/0           tcp flags:!0x17/0x02 
      497  138K ACCEPT     udp  --  *      *       10.0.0.2             0.0.0.0/0           
        0     0 ACCEPT     0    --  lo     *       0.0.0.0/0            0.0.0.0/0           
      195 20347 ACCEPT     icmp --  *      *       0.0.0.0/0            0.0.0.0/0           limit: avg 10/sec burst 5 
        0     0 DROP       0    --  eth0   *       0.0.0.0/0            255.255.255.255     
       12  2970 DROP       0    --  *      *       0.0.0.0/0            10.0.0.255          
        0     0 DROP       0    --  *      *       224.0.0.0/8          0.0.0.0/0           
        0     0 DROP       0    --  *      *       0.0.0.0/0            224.0.0.0/8         
        0     0 DROP       0    --  *      *       255.255.255.255      0.0.0.0/0           
        0     0 DROP       0    --  *      *       0.0.0.0/0            0.0.0.0             
       25  1052 DROP       0    --  *      *       0.0.0.0/0            0.0.0.0/0           state INVALID 
        0     0 LSI        0    -f  *      *       0.0.0.0/0            0.0.0.0/0           limit: avg 10/min burst 5 
    77608   60M INBOUND    0    --  eth0   *       0.0.0.0/0            0.0.0.0/0           
        0     0 LOG_FILTER  0    --  *      *       0.0.0.0/0            0.0.0.0/0           
        0     0 LOG        0    --  *      *       0.0.0.0/0            0.0.0.0/0           LOG flags 0 level 6 prefix `Unknown Input' 
        0     0 moblock_in  0    --  *      *       0.0.0.0/0            0.0.0.0/0           state NEW 
        0     0 moblock_in  0    --  *      *       0.0.0.0/0            0.0.0.0/0           state NEW 
    
    Chain FORWARD (policy DROP 0 packets, 0 bytes)
     pkts bytes target     prot opt in     out     source               destination         
        0     0 ACCEPT     icmp --  *      *       0.0.0.0/0            0.0.0.0/0           limit: avg 10/sec burst 5 
        0     0 LOG_FILTER  0    --  *      *       0.0.0.0/0            0.0.0.0/0           
        0     0 LOG        0    --  *      *       0.0.0.0/0            0.0.0.0/0           LOG flags 0 level 6 prefix `Unknown Forward' 
        0     0 moblock_fw  0    --  *      *       0.0.0.0/0            0.0.0.0/0           state NEW 
        0     0 moblock_fw  0    --  *      *       0.0.0.0/0            0.0.0.0/0           state NEW 
    
    Chain OUTPUT (policy DROP 3 packets, 3010 bytes)
     pkts bytes target     prot opt in     out     source               destination         
        0     0 ACCEPT     0    --  *      lo      0.0.0.0/0            0.0.0.0/0           
        0     0 ACCEPT     0    --  *      lo      0.0.0.0/0            0.0.0.0/0           
        0     0 ACCEPT     tcp  --  *      *       10.0.0.4             10.0.0.2            tcp dpt:53 
      498 31973 ACCEPT     udp  --  *      *       10.0.0.4             10.0.0.2            udp dpt:53 
        0     0 ACCEPT     0    --  *      lo      0.0.0.0/0            0.0.0.0/0           
        0     0 DROP       0    --  *      *       224.0.0.0/8          0.0.0.0/0           
        9   382 DROP       0    --  *      *       0.0.0.0/0            224.0.0.0/8         
        0     0 DROP       0    --  *      *       255.255.255.255      0.0.0.0/0           
        0     0 DROP       0    --  *      *       0.0.0.0/0            0.0.0.0             
      102 12711 DROP       0    --  *      *       0.0.0.0/0            0.0.0.0/0           state INVALID 
    85359   27M OUTBOUND   0    --  *      eth0    0.0.0.0/0            0.0.0.0/0           
        0     0 LOG_FILTER  0    --  *      *       0.0.0.0/0            0.0.0.0/0           
        0     0 LOG        0    --  *      *       0.0.0.0/0            0.0.0.0/0           LOG flags 0 level 6 prefix `Unknown Output' 
        0     0 moblock_out  0    --  *      *       0.0.0.0/0            0.0.0.0/0           state NEW 
        0     0 moblock_out  0    --  *      *       0.0.0.0/0            0.0.0.0/0           state NEW 
    
    Chain INBOUND (1 references)
     pkts bytes target     prot opt in     out     source               destination         
    76468   60M ACCEPT     tcp  --  *      *       0.0.0.0/0            0.0.0.0/0           state RELATED,ESTABLISHED 
     1097  308K ACCEPT     udp  --  *      *       0.0.0.0/0            0.0.0.0/0           state RELATED,ESTABLISHED 
       43  7470 LSI        0    --  *      *       0.0.0.0/0            0.0.0.0/0           
    
    Chain LOG_FILTER (5 references)
     pkts bytes target     prot opt in     out     source               destination         
    
    Chain LSI (2 references)
     pkts bytes target     prot opt in     out     source               destination         
       43  7470 LOG_FILTER  0    --  *      *       0.0.0.0/0            0.0.0.0/0           
        0     0 LOG        tcp  --  *      *       0.0.0.0/0            0.0.0.0/0           tcp flags:0x17/0x02 limit: avg 1/sec burst 5 LOG flags 0 level 6 prefix `Inbound ' 
        0     0 DROP       tcp  --  *      *       0.0.0.0/0            0.0.0.0/0           tcp flags:0x17/0x02 
        0     0 LOG        tcp  --  *      *       0.0.0.0/0            0.0.0.0/0           tcp flags:0x17/0x04 limit: avg 1/sec burst 5 LOG flags 0 level 6 prefix `Inbound ' 
        0     0 DROP       tcp  --  *      *       0.0.0.0/0            0.0.0.0/0           tcp flags:0x17/0x04 
        0     0 LOG        icmp --  *      *       0.0.0.0/0            0.0.0.0/0           icmp type 8 limit: avg 1/sec burst 5 LOG flags 0 level 6 prefix `Inbound ' 
        0     0 DROP       icmp --  *      *       0.0.0.0/0            0.0.0.0/0           icmp type 8 
       43  7470 LOG        0    --  *      *       0.0.0.0/0            0.0.0.0/0           limit: avg 5/sec burst 5 LOG flags 0 level 6 prefix `Inbound ' 
       43  7470 DROP       0    --  *      *       0.0.0.0/0            0.0.0.0/0           
    
    Chain LSO (0 references)
     pkts bytes target     prot opt in     out     source               destination         
        0     0 LOG_FILTER  0    --  *      *       0.0.0.0/0            0.0.0.0/0           
        0     0 LOG        0    --  *      *       0.0.0.0/0            0.0.0.0/0           limit: avg 5/sec burst 5 LOG flags 0 level 6 prefix `Outbound ' 
        0     0 REJECT     0    --  *      *       0.0.0.0/0            0.0.0.0/0           reject-with icmp-port-unreachable 
    
    Chain OUTBOUND (1 references)
     pkts bytes target     prot opt in     out     source               destination         
       18  2405 ACCEPT     icmp --  *      *       0.0.0.0/0            0.0.0.0/0           
    79081   27M ACCEPT     tcp  --  *      *       0.0.0.0/0            0.0.0.0/0           state RELATED,ESTABLISHED 
       61  7543 ACCEPT     udp  --  *      *       0.0.0.0/0            0.0.0.0/0           state RELATED,ESTABLISHED 
     6199  502K ACCEPT     0    --  *      *       0.0.0.0/0            0.0.0.0/0           
    
    Chain moblock_fw (2 references)
     pkts bytes target     prot opt in     out     source               destination         
        0     0 NFQUEUE    0    --  *      *       0.0.0.0/0            0.0.0.0/0           NFQUEUE num 0
    
    Chain moblock_in (2 references)
     pkts bytes target     prot opt in     out     source               destination         
        0     0 NFQUEUE    0    --  *      *       0.0.0.0/0            0.0.0.0/0           NFQUEUE num 0
    
    Chain moblock_out (2 references)
     pkts bytes target     prot opt in     out     source               destination         
        0     0 NFQUEUE    0    --  *      *       0.0.0.0/0            0.0.0.0/0           NFQUEUE num 0
    
    Please check if the above printed iptables rules are correct!
    
     * moblock is running, pid is 28733.
    I don't really know thing 1 about iptables, so I don't really know what I'm looking at or what I should be manually testing. I'd appreciate some advice. Thanks.

Page 91 of 120 FirstFirst ... 41818990919293101 ... 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
  •