From: Petter Reinholdtsen Date: Mon, 9 Jan 2017 11:25:32 +0000 (+0100) Subject: Generated. X-Git-Url: http://pere.pagekite.me/gitweb/homepage.git/commitdiff_plain/37b6bfd6c275b3df8f2345807ce410ab3e05bdfc?ds=inline Generated. --- 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 490ebe0e3b..9b51601e75 100644 --- 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"/>

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 @@ -151,11 +151,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. diff --git a/blog/archive/2017/01/01.rss b/blog/archive/2017/01/01.rss index ab326e3780..8b91c823ca 100644 --- a/blog/archive/2017/01/01.rss +++ b/blog/archive/2017/01/01.rss @@ -115,7 +115,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 @@ -140,11 +140,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. diff --git a/blog/archive/2017/01/index.html b/blog/archive/2017/01/index.html index ae28b0960e..5d586a599c 100644 --- a/blog/archive/2017/01/index.html +++ b/blog/archive/2017/01/index.html @@ -133,7 +133,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 @@ -158,11 +158,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. diff --git a/blog/index.html b/blog/index.html index 08496a4432..df4d1af227 100644 --- a/blog/index.html +++ b/blog/index.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"/>

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 @@ -151,11 +151,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. diff --git a/blog/index.rss b/blog/index.rss index 208f5d81ee..ad121de003 100644 --- a/blog/index.rss +++ b/blog/index.rss @@ -115,7 +115,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 @@ -140,11 +140,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. diff --git a/blog/tags/debian/debian.rss b/blog/tags/debian/debian.rss index 8bb73cbd00..04d3c62497 100644 --- a/blog/tags/debian/debian.rss +++ b/blog/tags/debian/debian.rss @@ -115,7 +115,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 @@ -140,11 +140,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. diff --git a/blog/tags/debian/index.html b/blog/tags/debian/index.html index 921a9ac487..a87405e027 100644 --- a/blog/tags/debian/index.html +++ b/blog/tags/debian/index.html @@ -132,7 +132,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 @@ -157,11 +157,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. diff --git a/blog/tags/kart/index.html b/blog/tags/kart/index.html index f5498e1e19..7ca1019d26 100644 --- a/blog/tags/kart/index.html +++ b/blog/tags/kart/index.html @@ -132,7 +132,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 @@ -157,11 +157,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. diff --git a/blog/tags/kart/kart.rss b/blog/tags/kart/kart.rss index fbc294f9ac..654e1ab2ba 100644 --- a/blog/tags/kart/kart.rss +++ b/blog/tags/kart/kart.rss @@ -115,7 +115,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 @@ -140,11 +140,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. diff --git a/blog/tags/nuug/index.html b/blog/tags/nuug/index.html index 498c0ee912..e8ed1e4e50 100644 --- a/blog/tags/nuug/index.html +++ b/blog/tags/nuug/index.html @@ -132,7 +132,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 @@ -157,11 +157,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. diff --git a/blog/tags/nuug/nuug.rss b/blog/tags/nuug/nuug.rss index e836b9746e..5da5caa56f 100644 --- a/blog/tags/nuug/nuug.rss +++ b/blog/tags/nuug/nuug.rss @@ -115,7 +115,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 @@ -140,11 +140,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. diff --git a/blog/tags/personvern/index.html b/blog/tags/personvern/index.html index 7dbbd6eada..3896be218a 100644 --- a/blog/tags/personvern/index.html +++ b/blog/tags/personvern/index.html @@ -132,7 +132,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 @@ -157,11 +157,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. diff --git a/blog/tags/personvern/personvern.rss b/blog/tags/personvern/personvern.rss index a971814135..d508966675 100644 --- a/blog/tags/personvern/personvern.rss +++ b/blog/tags/personvern/personvern.rss @@ -115,7 +115,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 @@ -140,11 +140,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. diff --git a/blog/tags/stortinget/index.html b/blog/tags/stortinget/index.html index ba9795797d..4a46bdef1c 100644 --- a/blog/tags/stortinget/index.html +++ b/blog/tags/stortinget/index.html @@ -132,7 +132,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 @@ -157,11 +157,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. diff --git a/blog/tags/stortinget/stortinget.rss b/blog/tags/stortinget/stortinget.rss index b57824734d..5d43dc28b4 100644 --- a/blog/tags/stortinget/stortinget.rss +++ b/blog/tags/stortinget/stortinget.rss @@ -115,7 +115,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 @@ -140,11 +140,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. diff --git a/blog/tags/surveillance/index.html b/blog/tags/surveillance/index.html index 8ce06d000e..6492c9e88a 100644 --- a/blog/tags/surveillance/index.html +++ b/blog/tags/surveillance/index.html @@ -132,7 +132,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 @@ -157,11 +157,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. diff --git a/blog/tags/surveillance/surveillance.rss b/blog/tags/surveillance/surveillance.rss index f102b65d8e..dd31c0f72e 100644 --- a/blog/tags/surveillance/surveillance.rss +++ b/blog/tags/surveillance/surveillance.rss @@ -115,7 +115,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 @@ -140,11 +140,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. diff --git a/blog/tags/web/index.html b/blog/tags/web/index.html index 093b6156c2..8e89f035bb 100644 --- a/blog/tags/web/index.html +++ b/blog/tags/web/index.html @@ -132,7 +132,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 @@ -157,11 +157,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. diff --git a/blog/tags/web/web.rss b/blog/tags/web/web.rss index 71ab3e95ae..2f862786fe 100644 --- a/blog/tags/web/web.rss +++ b/blog/tags/web/web.rss @@ -115,7 +115,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 @@ -140,11 +140,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.