Generated.

[homepage.git] / blog / Where_did_that_package_go___mdash__geolocated_IP_traceroute.html

diff --git a/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html b/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
index 490ebe0e3b4aa802f0b1575a30fe9b98b4b40b25..9b51601e758f413f830d09610290a8251faf0d5f 100644 (file)
--- a/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
+++ b/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
@@ -126,7 +126,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"/></a></p>
 
 <p>In the process, I came across the
-<a href="https://geotraceroute.com/">web service GeoTraceRoute</a> by
+<a href="https://geotraceroute.com/">web service GeoTraceroute</a> 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
@@ -151,11 +151,11 @@ without your best interest as their top priority.</p>
 
 <p>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.</p>
+GeoTraceroute).  That might be the next step in this project.</p>
 
 <p>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.