Lloyd Bryant wrote: > And I've got several more sources doing exactly the same thing: > 64.62.210.2 > 64.62.210.3 > 64.62.210.4 > 64.62.210.66 > 64.62.210.67 > 64.62.210.68 > > 78.129.136.194 > 78.129.136.195
Do you have any more information e.g., some sample query hits? Is this a typo? It belongs to a university unrelated to the above addresses. > 78.128.136.196 > Tracerouting them shows the 64.62.210.x addresses route via Hurricane > Electric (no surprise there), while the 78.129.136.x addresses route via > RapidSwitch (which we've already got a couple of "hostiles.txt" entries on). You don't have to traceroute them. That's also *dangerous* because they can see that. whoooooo! Just use whois. Sometimes the hosters/ISPs even run a whois server and you can check which business/individual the range is assigned to which helps to correlate things. -- Christian ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ gtk-gnutella-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
