From: Petter Reinholdtsen Date: Mon, 9 Jan 2017 11:24:17 +0000 (+0100) Subject: Correct capitalization. X-Git-Url: http://pere.pagekite.me/gitweb/homepage.git/commitdiff_plain/72b9a87f027aa91d08083a4ea751450fac9e4468?ds=sidebyside Correct capitalization. --- diff --git a/blog/data/2017-01-09-geotraceroute.txt b/blog/data/2017-01-09-geotraceroute.txt index 65bc771ced..3b806a22f8 100644 --- a/blog/data/2017-01-09-geotraceroute.txt +++ b/blog/data/2017-01-09-geotraceroute.txt @@ -106,7 +106,7 @@ UNINETT, Catchcom, Stortinget, Nordunet, Google, Amazon, Telia, Level src="http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-geotraceroute-small.png" alt="example geotraceroute view for www.stortinget.no"/>

In the process, I came across the -web service GeoTraceRoute by +web service GeoTraceroute by Salim Gasmi. Its methology of combining guesses based on DNS names, various location databases and finally use latecy times to rule out candidate locations seemed to do a very good job of guessing correct @@ -131,11 +131,11 @@ without your best interest as their top priority.

Combining KML files is trivial using a text editor, so I could loop over all the hosts behind the urls imported by www.stortinget.no and -ask for the KML file from geotraceroute, and create a combined KML +ask for the KML file from GeoTraceroute, and create a combined KML file with all the traces (unfortunately only one of the IP addresses behind the DNS name is traced this time. To get them all, one would have to request traces using IP number instead of DNS names from -geotraceroute). That might be the next step in this project.

+GeoTraceroute). That might be the next step in this project.

Armed with these tools, I find it a lot easier to figure out where the IP traffic moves and who control the boxes involved in moving it.