Homebrewserver infrastructour: Difference between revisions

From XPUB & Lens-Based wiki
(Created page with "mapping of dependencies, a visualization task 1. who is the internet provider? 2. who pays for the internet? 3. who has access to the router? 4. who is sharing the network...")
 
 
(15 intermediate revisions by 2 users not shown)
Line 1: Line 1:
mapping of dependencies, a visualization task
1. who is the internet provider?
2. who pays for the internet?
3. who has access to the router?
4. who is sharing the network?
5. whom did you have to ask permission?


-------
[[File:INFRASTRUCTOUR_01.jpg|400px|Infrastructour]]


artemis (ag), rita (rg), bo (bw)
==Mapping of dependencies==
1. telfort (KPN network)
2. ag, flatmate1
3. ag, flatmate1
4. ag, flatmate1, rg, bw
5. no-one


simon (sb)
1. who is the internet provider? <br/>
1. t-mobile
2. who pays for the internet? <br/>
2. the landlord (utilities are included in rent)
3. who has access to the router? <br/>
3. sb, flatmate1, flatmate2
4. who is sharing the network? <br/>
4, sb, flatmate1, flatmate2
5. whom did you have to ask permission?<br/>
5. no-one


paloma (pg), biyi (bw)
1. Youfone (KPN network)
2. pg, flatmate1, flatmate2
3. pg, flatmate1, flatmate2
4. pg, flatmate1, flatmate2, bw
5. no-one


tancredi (tdg), pedro (psc)
'''ANSWERS'''
1. t-mobile
2. tdg, flatmate1, flatmate2
3. tdg, flatmate1, flatmate2
4. tdg, flatmate1, flatmate2, psc
5. no-one


Visualisation
https://imgur.com/a/sRugd1O


--------
'''artemis (ag), rita (rg), bo (bw)<br/>'''
1. telfort (KPN network)<br/>
2. ag, flatmate1<br/>
3. ag, flatmate1<br/>
4. ag, flatmate1, rg, bw<br/>
5. no-one<br/>


sb, wm and wr depend on their internet connection
'''simon (sb)<br/>'''
sb, wm and wr depend on a paid service to t-mobile
1. t-mobile<br/>
connection to this service depends on a router owned by t-mobile
2. the landlord (utilities are included in rent)<br/>
the router depends on an underground cable to t-mobile’s network
3. sb, flatmate1, flatmate2<br/>
t-mobile’s network depends on interconnected underground cables throughout the netherlands
4, sb, flatmate1, flatmate2<br/>
5. no-one<br/>


rg and bw depend on ag and hv/dg’s internet connection
'''paloma (pg), biyi (bw)<br/>'''
ag and hv/dg depend on a paid service to telfort
1. Youfone (KPN network)<br/>
connection to this service depends on a router owned by telfort
2. pg, flatmate1, flatmate2<br/>
the router depends on an underground cable to telfort’s network
3. pg, flatmate1, flatmate2<br/>
telfort’s network depends on a connection to kpn’s network
4. pg, flatmate1, flatmate2, bw<br/>
kpn’s network depends on interconnected underground cables throughout the netherlands
5. no-one<br/>


-------
'''tancredi (tdg), pedro (psc)<br/>'''
1. t-mobile<br/>
2. tdg, flatmate1, flatmate2<br/>
3. tdg, flatmate1, flatmate2<br/>
4. tdg, flatmate1, flatmate2, psc<br/>
5. no-one<br/>


stories/anecdotes
 
== Visualisation ==
[[File:19 01 20 dependencies.jpg|500px|visualisation]]
 
sb, wm and wr depend on their internet connection<br/>
sb, wm and wr depend on a paid service to t-mobile<br/>
connection to this service depends on a router owned by t-mobile<br/>
the router depends on an underground cable to t-mobile’s network<br/>
t-mobile’s network depends on interconnected underground cables throughout the netherlands<br/>
 
rg and bw depend on ag and hv/dg’s internet connection<br/>
ag and hv/dg depend on a paid service to telfort <br/>
connection to this service depends on a router owned by telfort<br/>
the router depends on an underground cable to telfort’s network<br/>
telfort’s network depends on a connection to kpn’s network<br/>
kpn’s network depends on interconnected underground cables throughout the netherlands<br/>
 
 
==Stories/anecdotes==
We understood from the start that would be impossible to do everything by ourselves and therefore this process wouldn’t be individual. We had some preconditions, e.g having access to our home routers, but these needs really went beyond the software. In some cases, we had to rely on other person’s router (and goodwill) to host our own server, so slowly we started to build our interdependencies.
We understood from the start that would be impossible to do everything by ourselves and therefore this process wouldn’t be individual. We had some preconditions, e.g having access to our home routers, but these needs really went beyond the software. In some cases, we had to rely on other person’s router (and goodwill) to host our own server, so slowly we started to build our interdependencies.


*pedro, rita, bo, biyi depend on others - can't use their home router/internet connection for servers
'''Artemis''' — in order to have access to the router, we all had to know the routers’ passwords. In some cases, the passwords were left unchanged/default.
We traced the route with traceroute (“traceroute is a network tool used to show the route taken by packets across an IP network.”)  As the result, we can have very different paths because there is not a unique path.<br/>
We can check where is the IP with geoiplookup (“an online tool anyone can use to get accurate IP address information”).<br/>
We changed the firewall settings to make it public and also to enable exterior connection to the pi (through shh). We had to open 3 ports.<br/>
We also established a static IP address. (LAN — DHCP)
 
'''Paloma''' — the router was in an interesting place, behind a door, it had a room for itself. She has all the infrastructures in one place (internet, water, gas....)<br/>
The network company (ZTE) brought up some stories about American access to networks, the relationship between the US and China, America banning Chinese equipment, etc.<br/>
Biyi sent an article about this:<br/>
https://mbd.baidu.com/newspage/data/landingsuper?context=%7B%22nid%22:%22news_10206595552637159544%22%7D&n_type=0&p_from=1
It was also discussed port forwarding (having two people with the same host). Biyi opened her ports here for her raspberry pi.
We talked about OpenWrt Project (“Instead of trying to create a single, static firmware, OpenWrt provides a fully writable filesystem with package management”)
 
'''Bo''' — here we encountered a problem, the building had some kind of security and it was impossible to manage the ports.
We discussed the possibility of tunneling.
 
'''Simon''' — it was discussed the better option for the ones without access to their own routers (bo, rita, biyi, pedro): to share a server or to share a machine/raspberry pi. The downside of sharing a server would be having to write the domain name and adding the port name. (eg. website.com:2009) For now, we decided to go for this option. When opening the port for web servers, Simon had to exit the local network to test the connection (couldn't do it over the local network). On both Simon's and Tancredi's routers, only two of the four ethernet ports were for Internet (labelled INT).
 
'''Tancredi''' — In the last house that we visited we had a problem, there weren’t enough ports to host the 4 pi’s left. This router had some ports specifically for tv and others. We understood that these ports don’t work for our purposes. Tancredi has the router at the 2nd floor but the plug for the ethernet cable is at the ground floor


biyis anecdote for paloma's router?
*paloma has all the infrastructures in one place (internet, water, gas....)
*tancredi has the router at the 2nd floor but the plug for the ethernet cable is at the ground floor


other stories:
other stories:
    * The story of the Chinese provider VS past US hegemony in the sector
     * Some of the ethernet ports are only for TV and others only for internet, so not all of them can be used
     * Some of the ethernet ports are only for TV and others only for internet, so not all of them can be used
     * On the Tmobile router if you are connected in the same connection with the pi you can't access with the external IP (both from browser and SSH), you need to connect in LAN
     * On the Tmobile router if you are connected in the same connection with the pi you can't access with the external IP (both from browser and SSH), you need to connect in LAN
Line 72: Line 91:
     * On the Tmobile router there is a usb port where is possible to attach
     * On the Tmobile router there is a usb port where is possible to attach


Artemis — in order to have access to the router, we all had to know the routers’ passwords. In some cases, the passwords were left unchanged/default.
==New terms==
We traced the route with traceroute (“traceroute is a network tool used to show the route taken by packets across an IP network.”)  As the result, we can have very different paths because there is not a unique path.
 
We can check where is the IP with geoiplookup (“an online tool anyone can use to get accurate IP address information”).
Jargon File<br/>
We changed the firewall settings to make it public and also to enable exterior connection to the pi (through shh). We had to open 3 ports.
https://pad.xpub.nl/p/jargon-file<br/>
We also established a static IP address. (LAN — DHCP)
 
 
==Traceroute==
 
=== Some tests ===
 
 
[[File:trace_route.jpg|800px|traceroute map]]
 
 
The *asterisk* means “no reply”;<br />
The route the packets take is not always the same;<br />
The places associated with IP addresses can be misleading. See [https://www.theguardian.com/technology/2016/aug/09/maxmind-mapping-lawsuit-kansas-farm-ip-address “Kansas family sues mapping company for years of ‘digital hell’”;]<br />
Ziggo, KPN, Tele2, etc. are ISPs (Internet Service Providers).
 
 
'''ARTEMIS (+BO +RITA)'''
 
traceroute 77.172.158.66
traceroute to 77.172.158.66 (77.172.158.66), 64 hops max, 52 byte packets
 
1  * 192.168.88.1 (192.168.88.1)  2.028 ms *
PRIVATE
 
2  10.0.0.1 (10.0.0.1)  3.027 ms  6.871 ms  1.863 ms
PRIVATE
 
3  ip-213-126-238-89.ip.prioritytelecom.net (213.126.238.89)  2.292 ms  5.068 ms  2.569 ms
NL, VodafoneZiggo
 
4  asd-tr0021-cr101-bundle-ether113-47.aorta.net (84.116.244.241)  9.796 ms  4.957 ms  4.742 ms
CH, Liberty Global Infrastructure
 
5  nl-ams02a-rc2-lag-2-0.aorta.net (84.116.135.146)  4.822 ms  4.433 ms  4.340 ms
CH, Liberty Global Infrastructure
 
6  nl-srk03a-ri1-ae2-0.aorta.net (84.116.135.145)  18.311 ms  5.240 ms  4.585 ms
CH, Liberty Global Infrastructure
 
7  kpn-as1136.kpn-rt-dc2.nl-ix.net (193.239.117.67)  7.336 ms  10.217 ms *
PRIVATE
 
8  * * *
9  * * *
10  * * *
 
 
 
 
'''PALOMA (+BI)'''
 
 
traceroute 82.169.88.92
traceroute to 82.169.88.92 (82.169.88.92), 64 hops max, 52 byte packets
 
1  192.168.88.1 (192.168.88.1)  320.909 ms  2.766 ms  1.306 ms
PRIVATE
 
2  10.0.0.1 (10.0.0.1)  19.202 ms  1.619 ms  1.176 ms
PRIVATE
 
3  ip-213-126-238-89.ip.prioritytelecom.net (213.126.238.89)  7.552 ms  8.029 ms  1.909 ms
NL, VodafoneZiggo
 
4  asd-tr0021-cr101-bundle-ether113-47.aorta.net (84.116.244.241)  4.613 ms  16.598 ms  4.314 ms
CH, Liberty Global Infrastructure
 
5  nl-ams02a-rc2-lag-2-0.aorta.net (84.116.135.146)  4.897 ms  4.220 ms  4.740 ms
CH, Liberty Global Infrastructure
 
6  nl-srk03a-ri1-ae2-0.aorta.net (84.116.135.145)  4.944 ms  16.480 ms  4.288 ms
CH, Liberty Global Infrastructure
 
7  * * *
8  * * *
9  * * *
10  * * *
 
 
 
'''SIMON'''
 
 
traceroute 85.146.123.46
traceroute to 85.146.123.46 (85.146.123.46), 64 hops max, 52 byte packets
 
1  192.168.88.1 (192.168.88.1)  101.322 ms  1.024 ms  1.014 ms
PRIVATE. MY ROUTER
 
2  10.0.0.1 (10.0.0.1)  1.054 ms  1.152 ms  1.170 ms
PRIVATE
 
3  ip-213-126-238-89.ip.prioritytelecom.net (213.126.238.89)  8.019 ms  9.540 ms  4.064 ms
NL, VodafoneZiggo
 
4  asd-tr0021-cr101-bundle-ether113-47.aorta.net (84.116.244.241)  14.651 ms  14.313 ms  12.698 ms
CH, Liberty Global Infrastructure
 
5  nl-ams02a-rc2-lag-23-0.aorta.net (84.116.130.90)  25.079 ms  16.074 ms  13.425 ms
CH, Liberty Global Infrastructure
 
6  * * *
 
7  uk-lon03a-ri1-ae2-0.aorta.net (84.116.135.46)  18.511 ms  32.846 ms  17.119 ms
CH, Liberty Global Infrastructure
 
8  213.46.174.130 (213.46.174.130)  20.125 ms  26.444 ms  15.658 ms
NL, UPC NL
 
9  ae27.0-xcr1.hex.cw.net (195.2.28.149)  13.416 ms  19.641 ms  15.595 ms
UK, Cable & Wireless Telecommunication Services GmbH
 
10  ae21-xcr1.att.cw.net (195.2.28.166)  18.572 ms  24.301 ms  18.358 ms
UK, Cable & Wireless Telecommunication Services GmbH
 
11  vod-lib-gw2.nl.cw.net (195.89.97.134)  19.091 ms  18.980 ms  22.713 ms
UK, Bradford, AS1273 Customer P2P links
 
 
 
 
'''TANCREDI (+ PEDRO)'''
 
 
traceroute 31.20.8.54
traceroute to 31.20.8.54 (31.20.8.54), 64 hops max, 52 byte packets
 
1  192.168.88.1 (192.168.88.1) 5.743 ms  0.907 ms  0.807 ms
PRIVATE
 
2  10.0.0.1 (10.0.0.1) 1.160 ms  1.294 ms  0.983 ms
PRIVATE
 
3 ip-213-126-238-89.ip.prioritytelecom.net (213.126.238.89)  1.786 ms  2.717 ms  1.774 ms
NL, VodafoneZiggo
 
4  asd-tr0021-cr101-bundle-ether113-47.aorta.net (84.116.244.241)  12.856 ms  12.556 ms  15.895 ms
CH, Liberty Global Infrastructure
 
5  nl-ams02a-rc2-lag-23-0.aorta.net (84.116.130.90) 17.914 ms  12.837 ms  13.554 ms
CH, Liberty Global Infrastructure


Paloma — the router was in an interesting place, behind a door, it had a room for itself.
  6  * * *
The network company (ZTE) brought up some stories about American access to networks, the relationship between the US and China, America banning Chinese equipment, etc.
Biyi sent an article about this:
https://mbd.baidu.com/newspage/data/landingsuper?context=%7B%22nid%22:%22news_10206595552637159544%22%7D&n_type=0&p_from=1
   
It was also discussed port forwarding (having two people with the same host). Biyi opened her ports here for her raspberry pi.
We talked about OpenWrt Project (“Instead of trying to create a single, static firmware, OpenWrt provides a fully writable filesystem with package management”)


Bo — here we encountered a problem, the building had some kind of security and it was impossible to manage the ports.  
7  uk-lon03a-ri1-ae2-0.aorta.net (84.116.135.46)  15.775 ms  24.225 ms  22.717 ms
We discussed the possibility of tunneling.
CH, Liberty Global Infrastructure


Simon — it was discussed the better option for the ones without access to their own routers (bo, rita, biyi, pedro): to share a server or to share a machine/raspberry pi. The downside of sharing a server would be having to write the domain name and adding the port name. (eg. website.com:2009) For now, we decided to go for this option. When opening the port for web servers, Simon had to exit the local network to test the connection (couldn't do it over the local network). On both Simon's and Tancredi's routers, only two of the four ethernet ports were for Internet (labelled INT).
8  213.46.174.130 (213.46.174.130) 15.110 ms  18.130 ms  12.436 ms
NL, UPC NL


Tancredi — In the last house that we visited we had a problem, there weren’t enough ports to host the 4 pi’s left. This router had some ports specifically for tv and others. We understood that these ports don’t work for our purposes.
9  ae27.0-xcr1.hex.cw.net (195.2.28.149)  15.338 ms  21.322 ms  13.705 ms
UK, Cable & Wireless Telecommunication Services GmbH


10  ae21-xcr1.att.cw.net (195.2.28.166)  19.799 ms  26.751 ms  19.035 ms
UK, Cable & Wireless Telecommunication Services GmbH


11  vod-lib-gw2.nl.cw.net (195.89.97.134)  19.695 ms  20.446 ms  19.449 ms
UK, Bradford, AS1273 Customer P2P links


Some new terms: [added to the jargon pad]
[[Category:WttF]]
*LAN
*WAN (wide area network)
*subnet mask
*gateway (router of the router, a network of networks, a machine where all the data travels through)
*mirroring (pirating but also for political reasons, see the case with Turkish Wikipedia)
*pi hole (add blocking)
*dropping (ignoring)

Latest revision as of 00:35, 12 February 2019

Infrastructour

Mapping of dependencies

1. who is the internet provider?
2. who pays for the internet?
3. who has access to the router?
4. who is sharing the network?
5. whom did you have to ask permission?


ANSWERS


artemis (ag), rita (rg), bo (bw)
 1. telfort (KPN network)
2. ag, flatmate1
3. ag, flatmate1
4. ag, flatmate1, rg, bw
5. no-one

simon (sb)
 1. t-mobile
2. the landlord (utilities are included in rent)
3. sb, flatmate1, flatmate2
4, sb, flatmate1, flatmate2
5. no-one

paloma (pg), biyi (bw)
 1. Youfone (KPN network)
2. pg, flatmate1, flatmate2
3. pg, flatmate1, flatmate2
4. pg, flatmate1, flatmate2, bw
5. no-one

tancredi (tdg), pedro (psc)
 1. t-mobile
2. tdg, flatmate1, flatmate2
3. tdg, flatmate1, flatmate2
4. tdg, flatmate1, flatmate2, psc
5. no-one


Visualisation

visualisation

sb, wm and wr depend on their internet connection
sb, wm and wr depend on a paid service to t-mobile
connection to this service depends on a router owned by t-mobile
the router depends on an underground cable to t-mobile’s network
t-mobile’s network depends on interconnected underground cables throughout the netherlands

rg and bw depend on ag and hv/dg’s internet connection
ag and hv/dg depend on a paid service to telfort
connection to this service depends on a router owned by telfort
the router depends on an underground cable to telfort’s network
telfort’s network depends on a connection to kpn’s network
kpn’s network depends on interconnected underground cables throughout the netherlands


Stories/anecdotes

We understood from the start that would be impossible to do everything by ourselves and therefore this process wouldn’t be individual. We had some preconditions, e.g having access to our home routers, but these needs really went beyond the software. In some cases, we had to rely on other person’s router (and goodwill) to host our own server, so slowly we started to build our interdependencies.

Artemis — in order to have access to the router, we all had to know the routers’ passwords. In some cases, the passwords were left unchanged/default. We traced the route with traceroute (“traceroute is a network tool used to show the route taken by packets across an IP network.”) As the result, we can have very different paths because there is not a unique path.
We can check where is the IP with geoiplookup (“an online tool anyone can use to get accurate IP address information”).
We changed the firewall settings to make it public and also to enable exterior connection to the pi (through shh). We had to open 3 ports.
We also established a static IP address. (LAN — DHCP)

Paloma — the router was in an interesting place, behind a door, it had a room for itself. She has all the infrastructures in one place (internet, water, gas....)
The network company (ZTE) brought up some stories about American access to networks, the relationship between the US and China, America banning Chinese equipment, etc.
Biyi sent an article about this:
https://mbd.baidu.com/newspage/data/landingsuper?context=%7B%22nid%22:%22news_10206595552637159544%22%7D&n_type=0&p_from=1

It was also discussed port forwarding (having two people with the same host). Biyi opened her ports here for her raspberry pi. We talked about OpenWrt Project (“Instead of trying to create a single, static firmware, OpenWrt provides a fully writable filesystem with package management”)

Bo — here we encountered a problem, the building had some kind of security and it was impossible to manage the ports. We discussed the possibility of tunneling.

Simon — it was discussed the better option for the ones without access to their own routers (bo, rita, biyi, pedro): to share a server or to share a machine/raspberry pi. The downside of sharing a server would be having to write the domain name and adding the port name. (eg. website.com:2009) For now, we decided to go for this option. When opening the port for web servers, Simon had to exit the local network to test the connection (couldn't do it over the local network). On both Simon's and Tancredi's routers, only two of the four ethernet ports were for Internet (labelled INT).

Tancredi — In the last house that we visited we had a problem, there weren’t enough ports to host the 4 pi’s left. This router had some ports specifically for tv and others. We understood that these ports don’t work for our purposes. Tancredi has the router at the 2nd floor but the plug for the ethernet cable is at the ground floor


other stories: 

   * Some of the ethernet ports are only for TV and others only for internet, so not all of them can be used
   * On the Tmobile router if you are connected in the same connection with the pi you can't access with the external IP (both from browser and SSH), you need to connect in LAN
   * There is the possibility that to set a fixed IP is not possible or it is already done in the default settings
   * On the Tmobile router there is a usb port where is possible to attach

New terms

Jargon File
https://pad.xpub.nl/p/jargon-file


Traceroute

Some tests

traceroute map


The *asterisk* means “no reply”;
The route the packets take is not always the same;
The places associated with IP addresses can be misleading. See “Kansas family sues mapping company for years of ‘digital hell’”;
Ziggo, KPN, Tele2, etc. are ISPs (Internet Service Providers).


ARTEMIS (+BO +RITA)

traceroute 77.172.158.66 traceroute to 77.172.158.66 (77.172.158.66), 64 hops max, 52 byte packets 

1  * 192.168.88.1 (192.168.88.1)  2.028 ms *

PRIVATE 

2  10.0.0.1 (10.0.0.1)  3.027 ms  6.871 ms  1.863 ms

PRIVATE 

3  ip-213-126-238-89.ip.prioritytelecom.net (213.126.238.89)  2.292 ms  5.068 ms  2.569 ms

NL, VodafoneZiggo 

4  asd-tr0021-cr101-bundle-ether113-47.aorta.net (84.116.244.241)  9.796 ms  4.957 ms  4.742 ms

CH, Liberty Global Infrastructure 

5  nl-ams02a-rc2-lag-2-0.aorta.net (84.116.135.146)  4.822 ms  4.433 ms  4.340 ms

CH, Liberty Global Infrastructure 

6  nl-srk03a-ri1-ae2-0.aorta.net (84.116.135.145)  18.311 ms  5.240 ms  4.585 ms

CH, Liberty Global Infrastructure 

7  kpn-as1136.kpn-rt-dc2.nl-ix.net (193.239.117.67)  7.336 ms  10.217 ms *

PRIVATE 

8  * * *
9  * * *
10  * * *



PALOMA (+BI)


traceroute 82.169.88.92 traceroute to 82.169.88.92 (82.169.88.92), 64 hops max, 52 byte packets 

1  192.168.88.1 (192.168.88.1)  320.909 ms  2.766 ms  1.306 ms

PRIVATE 

2  10.0.0.1 (10.0.0.1)  19.202 ms  1.619 ms  1.176 ms

PRIVATE 

3  ip-213-126-238-89.ip.prioritytelecom.net (213.126.238.89)  7.552 ms  8.029 ms  1.909 ms

NL, VodafoneZiggo 

4  asd-tr0021-cr101-bundle-ether113-47.aorta.net (84.116.244.241)  4.613 ms  16.598 ms  4.314 ms

CH, Liberty Global Infrastructure 

5  nl-ams02a-rc2-lag-2-0.aorta.net (84.116.135.146)  4.897 ms  4.220 ms  4.740 ms

CH, Liberty Global Infrastructure 

6  nl-srk03a-ri1-ae2-0.aorta.net (84.116.135.145)  4.944 ms  16.480 ms  4.288 ms

CH, Liberty Global Infrastructure 

7  * * *
8  * * *
9  * * *
10  * * *


SIMON


traceroute 85.146.123.46 traceroute to 85.146.123.46 (85.146.123.46), 64 hops max, 52 byte packets 

1  192.168.88.1 (192.168.88.1)  101.322 ms  1.024 ms  1.014 ms

PRIVATE. MY ROUTER 

2  10.0.0.1 (10.0.0.1)  1.054 ms  1.152 ms  1.170 ms

PRIVATE 

3  ip-213-126-238-89.ip.prioritytelecom.net (213.126.238.89)  8.019 ms  9.540 ms  4.064 ms

NL, VodafoneZiggo 

4  asd-tr0021-cr101-bundle-ether113-47.aorta.net (84.116.244.241)  14.651 ms  14.313 ms  12.698 ms

CH, Liberty Global Infrastructure 

5  nl-ams02a-rc2-lag-23-0.aorta.net (84.116.130.90)  25.079 ms  16.074 ms  13.425 ms

CH, Liberty Global Infrastructure 

6  * * *

7  uk-lon03a-ri1-ae2-0.aorta.net (84.116.135.46)  18.511 ms  32.846 ms  17.119 ms

CH, Liberty Global Infrastructure 

8  213.46.174.130 (213.46.174.130)  20.125 ms  26.444 ms  15.658 ms

NL, UPC NL 

9  ae27.0-xcr1.hex.cw.net (195.2.28.149)  13.416 ms  19.641 ms  15.595 ms

UK, Cable & Wireless Telecommunication Services GmbH 

10  ae21-xcr1.att.cw.net (195.2.28.166)  18.572 ms  24.301 ms  18.358 ms

UK, Cable & Wireless Telecommunication Services GmbH 

11  vod-lib-gw2.nl.cw.net (195.89.97.134)  19.091 ms  18.980 ms  22.713 ms

UK, Bradford, AS1273 Customer P2P links



TANCREDI (+ PEDRO)


traceroute 31.20.8.54 traceroute to 31.20.8.54 (31.20.8.54), 64 hops max, 52 byte packets 

1  192.168.88.1 (192.168.88.1)  5.743 ms  0.907 ms  0.807 ms

PRIVATE 

2  10.0.0.1 (10.0.0.1)  1.160 ms  1.294 ms  0.983 ms

PRIVATE 

3  ip-213-126-238-89.ip.prioritytelecom.net (213.126.238.89)  1.786 ms  2.717 ms  1.774 ms

NL, VodafoneZiggo 

4  asd-tr0021-cr101-bundle-ether113-47.aorta.net (84.116.244.241)  12.856 ms  12.556 ms  15.895 ms

CH, Liberty Global Infrastructure 

5  nl-ams02a-rc2-lag-23-0.aorta.net (84.116.130.90)  17.914 ms  12.837 ms  13.554 ms

CH, Liberty Global Infrastructure 

6  * * *

7  uk-lon03a-ri1-ae2-0.aorta.net (84.116.135.46)  15.775 ms  24.225 ms  22.717 ms

CH, Liberty Global Infrastructure 

8  213.46.174.130 (213.46.174.130)  15.110 ms  18.130 ms  12.436 ms

NL, UPC NL 

9  ae27.0-xcr1.hex.cw.net (195.2.28.149)  15.338 ms  21.322 ms  13.705 ms

UK, Cable & Wireless Telecommunication Services GmbH 

10  ae21-xcr1.att.cw.net (195.2.28.166)  19.799 ms  26.751 ms  19.035 ms

UK, Cable & Wireless Telecommunication Services GmbH 

11  vod-lib-gw2.nl.cw.net (195.89.97.134)  19.695 ms  20.446 ms  19.449 ms

UK, Bradford, AS1273 Customer P2P links

Retrieved from "https://pzwiki.wdka.nl/mw-mediadesign/index.php?title=Homebrewserver_infrastructour&oldid=140958"