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 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
 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
 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
 
 <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
 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.
 
 <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/01.rss b/blog/archive/2017/01/01.rss
index ab326e3780b910553c84acf4da8d69b087e134f4..8b91c823ca2d139987ac4b5df7b23c8a03b5bc5b 100644 (file)
--- 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
 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
 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
 
 <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
 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.
 
 <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 ae28b0960e2e62a660c0fb456be7eef4c5a8f8ba..5d586a599c1acb36f72656b8f89baaf927f62cc6 100644 (file)
--- 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"/></a></p>
 
 <p>In the process, I came across the
 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
 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.</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
 
 <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
 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.
 
 <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/index.html b/blog/index.html
index 08496a4432bf735bd39a338da0ac9dc714192824..df4d1af2278de034700727ba51a85852b2be1d0c 100644 (file)
--- 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"/></a></p>
 
 <p>In the process, I came across the
 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
 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
 
 <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
 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.
 
 <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/index.rss b/blog/index.rss
index 208f5d81ee30b8bc75456e08fbc8f43cfb2b7acd..ad121de003b23b32fe3fd1ad261a8a7bed8d08bb 100644 (file)
--- 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
 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
 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
 
 <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
 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.
 
 <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 8bb73cbd0096b09d2549989e6b74fa549ce4b8f0..04d3c62497f3e147d97f5ffb73a266e48f219a0f 100644 (file)
--- 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
 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
 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
 
 <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
 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.
 
 <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 921a9ac487d595912dc054b3be7fb69d84b13da4..a87405e0271d278cd96276b88b6b25731fb8b084 100644 (file)
--- 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"/></a></p>
 
 <p>In the process, I came across the
 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
 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.</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
 
 <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
 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.
 
 <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/kart/index.html b/blog/tags/kart/index.html
index f5498e1e193dab974041b223da8a40c46c071576..7ca1019d268cbe189c80f5ed71960284ba975941 100644 (file)
--- 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"/></a></p>
 
 <p>In the process, I came across the
 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
 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.</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
 
 <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
 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.
 
 <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/kart/kart.rss b/blog/tags/kart/kart.rss
index fbc294f9ac43570761b14ac58a9a17b35f19d896..654e1ab2ba12e32488be71ad1c01f71d18d4b1fe 100644 (file)
--- 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
 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
 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
 
 <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
 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.
 
 <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 498c0ee912254f5407aba16092174caf8b38aec3..e8ed1e4e50b488beb2ce3464e37c7a9e53e33fba 100644 (file)
--- 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"/></a></p>
 
 <p>In the process, I came across the
 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
 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.</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
 
 <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
 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.
 
 <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/nuug.rss b/blog/tags/nuug/nuug.rss
index e836b9746e09f51698dcea2ca2ed8b1a41fcb22b..5da5caa56f798d870a59ea1b43904d9b25818b21 100644 (file)
--- 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
 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
 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
 
 <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
 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.
 
 <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 7dbbd6eadafcc7c4c8a6823dc09e736e57c93be8..3896be218ada858283500b9df8fbd707f4161e5f 100644 (file)
--- 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"/></a></p>
 
 <p>In the process, I came across the
 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
 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.</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
 
 <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
 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.
 
 <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/personvern.rss b/blog/tags/personvern/personvern.rss
index a97181413551e3704023eed2911df61910188076..d508966675122b8d7006ab7f0dff8040b5fcb470 100644 (file)
--- 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
 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
 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
 
 <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
 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.
 
 <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 ba9795797d0f43c2ae86227b5fd5a1caed45b9bd..4a46bdef1c7d4ce22b44cb0843c60dae98e9d047 100644 (file)
--- 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"/></a></p>
 
 <p>In the process, I came across the
 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
 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.</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
 
 <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
 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.
 
 <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/stortinget.rss b/blog/tags/stortinget/stortinget.rss
index b57824734d8c0eb05c4b64857b5947dfea04f7e0..5d43dc28b4994203b5ee46c83e970f0e6493c350 100644 (file)
--- 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
 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
 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
 
 <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
 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.
 
 <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 8ce06d000e3e067dd52f96fe299cf02480ce998c..6492c9e88ab9fdf7f2a57ae06db84185633c7bc7 100644 (file)
--- 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"/></a></p>
 
 <p>In the process, I came across the
 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
 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.</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
 
 <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
 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.
 
 <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/surveillance.rss b/blog/tags/surveillance/surveillance.rss
index f102b65d8eedb16b3a3a9a1082f6d9ba93ecc466..dd31c0f72e31fb8594f2ccf5648478c939c24563 100644 (file)
--- 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
 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
 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
 
 <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
 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.
 
 <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 093b6156c2618e9ed32086db458fc275f20b8e78..8e89f035bb0629478440912eff915e7c4775d543 100644 (file)
--- 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"/></a></p>
 
 <p>In the process, I came across the
 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
 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.</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
 
 <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
 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.
 
 <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/web.rss b/blog/tags/web/web.rss
index 71ab3e95aec4e2cd8bfe1416a0ce01cc93681400..2f862786fe65685b382037e0ef1c13d5b20f5c28 100644 (file)
--- 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
 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
 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
 
 <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
 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.
 
 <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.