Anyone here using moblock?

[stevovo]

Good day

I thought I'd give this software a try since I can no longer use peerblock

So has anyone any experience with it?

I installed it on my ubuntu 9.10 but I'm not sure if its working.

I tried to do a traceroute to one of the blacklisted ip's but the problem is that its listed in ranges leaving me unsure how to know which ip to trace.

And how updated is the software? Is it active and are the lists updated regularly?

Any other similar software for linux?

Thanks in advance guys!

 

[milomak]

i've started using it this week. Looks like it works

debian ~ # traceroute www.cnn.com

traceroute to www.cnn.com (157.166.226.26), 30 hops max, 60 byte packets                      
 1  milomak-main (192.168.1.100)  0.047 ms  0.067 ms  0.077 ms

debian ~ # /etc/init.d/blockcontrol stop

Stopping IP block daemon: moblock.

debian ~ # traceroute www.cnn.com

traceroute to www.cnn.com (157.166.226.25), 30 hops max, 60 byte packets
 1  upstairs (192.168.1.1)  1.694 ms  1.982 ms  2.255 ms                
 2  dsl-241-192-01.telkomadsl.co.za (41.241.192.1)  40.025 ms  40.397 ms  40.520 ms
 3  cdsl2-rba-vl2563.ip.isnet.net (196.38.73.213)  40.709 ms  40.835 ms  41.361 ms 
 4  cdsl1-rba-vl11.ip.isnet.net (196.38.73.37)  44.428 ms  61.102 ms  61.434 ms    
 5  196.38.73.86 (196.38.73.86)  61.653 ms  61.790 ms  62.868 ms                   
 6  cdsl1-rba-vl58.ip.isnet.net (196.38.73.81)  63.065 ms  53.619 ms  72.906 ms    
 7  core2b-rba-te2-0-1.ip.isnet.net (168.209.1.182)  73.252 ms  59.746 ms  55.501 ms
 8  mi-za-rba-p6-gi2-0-0-306.ip.isnet.net (168.209.164.177)  438.437 ms  438.700 ms  438.949 ms
 9  mi-us-25b-p2-po1-3-3.ip.isnet.net (168.209.160.215)  439.417 ms  434.969 ms  427.636 ms    
10  core2a-ny-gi1-0-19-306.ip.isnet.net (168.209.164.128)  427.602 ms  573.363 ms  354.559 ms  
11  168.209.245.1 (168.209.245.1)  354.876 ms  365.102 ms  371.714 ms                          
12  gi1-6.ccr01.jfk06.atlas.cogentco.com (38.104.66.89)  385.319 ms  385.632 ms  385.741 ms    
13  te2-1.mpd01.jfk01.atlas.cogentco.com (154.54.24.217)  399.426 ms te2-1.ccr02.jfk01.atlas.cogentco.com (154.54.24.221)  399.869 ms te2-1.mpd01.jfk01.atlas.cogentco.com (154.54.24.217)  400.009 ms                      
14  te2-1.ccr02.jfk02.atlas.cogentco.com (154.54.7.69)  400.191 ms te2-3.ccr01.jfk02.atlas.cogentco.com (154.54.1.209)  400.370 ms  413.498 ms                                                                              
15  te8-3.mpd02.dca01.atlas.cogentco.com (154.54.5.253)  413.829 ms te3-1.ccr01.dca01.atlas.cogentco.com (154.54.25.238)  430.638 ms  430.865 ms                                                                            
16  te8-1.ccr01.iad01.atlas.cogentco.com (154.54.2.50)  671.338 ms te4-3.ccr01.iad01.atlas.cogentco.com (154.54.26.130)  635.800 ms te8-3.mpd02.iad01.atlas.cogentco.com (154.54.26.118)  349.297 ms                        
17  gi0-0-0.core01.iad01.atlas.cogentco.com (154.54.3.225)  349.768 ms  349.899 ms  350.021 ms                
18  pop1-ash-s2-1-0.atdn.net (66.185.134.177)  350.204 ms  350.326 ms  350.621 ms                             
19  bb2-ash-p1-0.atdn.net (66.185.144.34)  351.086 ms  351.381 ms  351.784 ms                                 
20  bb2-atm-p3-0.atdn.net (66.185.152.51)  352.074 ms  352.334 ms  352.560 ms                                 
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

debian ~ # /etc/init.d/blockcontrol start

Starting IP block daemon: moblock.

debian ~ # traceroute www.cnn.com

traceroute to www.cnn.com (157.166.226.26), 30 hops max, 60 byte packets
 1  * * *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * milomak-main (192.168.1.100)  0.062 ms  0.100 ms

 

[stevovo]

Ok I get it now.

I wonder why they block cnn though... even GOOGLE!

 

[milomak]

in the configuration file you can have sites with certain words unblocked. it's probably a function of the blocklists i chose more than anything else.