IPv6 Roll Out

AfriNatic said:
Quad 9 peers with us in CPT.

Quad9 | A public and free DNS service for a better security and privacy

A public and free DNS service for a better security and privacy
www.quad9.net www.quad9.net
Click to expand...

quad9's v6 ip's seem to be in jhb
pi@4glass:~$ traceroute6 2620:fe::fe
traceroute to 2620:fe::fe (2620:fe::fe), 30 hops max, 80 byte packets
1 dlinkrouter.Dlink (2c0f:f4c0:2201:fcd8:c6e9:aff:fe31:eb85) 0.697 ms 1.127 ms 1.213 ms
2 2c0f:f4c0:2200::1 (2c0f:f4c0:2200::1) 4.119 ms 4.274 ms 4.813 ms
3 2c0f:f4c0:2000:3::d (2c0f:f4c0:2000:3::d) 3.894 ms 3.822 ms 3.967 ms
4 2c0f:f4c0:2000:3::11 (2c0f:f4c0:2000:3::11) 32.892 ms 32.692 ms 32.617 ms
5 2c0f:f708::d8 (2c0f:f708::d8) 32.906 ms 32.677 ms 32.747 ms
6 2001:43f8:6d0::9:182 (2001:43f8:6d0::9:182) 32.515 ms 33.770 ms 33.929 ms
7 dns.quad9.net (2620:fe::fe) 27.415 ms !X 29.724 ms !X 29.608 ms !X

pi@4glass:~$ traceroute6 iol.co.za
traceroute to iol.co.za (2606:4700:10::ac43:899), 30 hops max, 80 byte packets
1 dlinkrouter.Dlink (2c0f:f4c0:2201:fcd8:c6e9:aff:fe31:eb85) 0.684 ms 1.092 ms 1.150 ms
2 2c0f:f4c0:2200::1 (2c0f:f4c0:2200::1) 4.545 ms 4.631 ms 4.393 ms
3 2c0f:f4c0:2000:3::d (2c0f:f4c0:2000:3::d) 4.313 ms 4.397 ms 7.457 ms
4 2c0f:f4c0:2000:3::11 (2c0f:f4c0:2000:3::11) 7.543 ms 7.466 ms 7.230 ms
5 2c0f:f708::d8 (2c0f:f708::d8) 26.260 ms 26.017 ms 25.944 ms
6 cloudflare.ixp.joburg (2001:43f8:6d0::198) 26.035 ms 23.651 ms 23.544 ms
7 2400:cb00:45:1024::c5ea:f11c (2400:cb00:45:1024::c5ea:f11c) 23.269 ms 24.911 ms 2400:cb00:45:1024::c5ea:f10d (2400:cb00:45:1024::c5ea:f10d) 24.807 ms
pi@4glass:~$
Click to expand...
 
blunt said:
seems to go to jhb for v6

Code: 
traceroute to 2c0f:f4c0::c (2c0f:f4c0::c), 30 hops max, 80 byte packets
1  dlinkrouter.Dlink (2c0f:f4c0:2201:fcd8:c6e9:aff:fe31:eb85)  0.846 ms  1.386 ms  1.432 ms
2  2c0f:f4c0:2200::1 (2c0f:f4c0:2200::1)  5.005 ms  4.921 ms  4.849 ms
3  2c0f:f4c0:2000:3::d (2c0f:f4c0:2000:3::d)  4.619 ms  4.887 ms  4.807 ms
4  2c0f:f4c0:2000:3::11 (2c0f:f4c0:2000:3::11)  8.008 ms  7.935 ms  7.855 ms
5  2c0f:f708::d8 (2c0f:f708::d8)  24.395 ms 2c0f:f708::18 (2c0f:f708::18)  24.315 ms 2c0f:f708::d8 (2c0f:f708::d8)  24.242 ms
6  2c0f:f4c0:1000:3::40 (2c0f:f4c0:1000:3::40)  24.365 ms  27.572 ms  26.053 ms
7  2c0f:f4c0::c (2c0f:f4c0::c)  25.820 ms  21.862 ms  21.573 ms

Code: 
traceroute to 2c0f:f4c0::d (2c0f:f4c0::d), 30 hops max, 80 byte packets
1  dlinkrouter.Dlink (2c0f:f4c0:2201:fcd8:c6e9:aff:fe31:eb85)  0.941 ms  0.979 ms  1.819 ms
2  2c0f:f4c0:2200::1 (2c0f:f4c0:2200::1)  5.623 ms  4.988 ms  5.204 ms
3  2c0f:f4c0:2000:3::d (2c0f:f4c0:2000:3::d)  5.120 ms  4.752 ms  4.970 ms
4  2c0f:f4c0:2000:3::11 (2c0f:f4c0:2000:3::11)  8.503 ms  8.267 ms  8.181 ms
5  2c0f:f708::18 (2c0f:f708::18)  24.599 ms 2c0f:f708::d8 (2c0f:f708::d8)  24.528 ms  24.447 ms
6  2c0f:f4c0:1000:3::40 (2c0f:f4c0:1000:3::40)  24.582 ms  27.850 ms  27.774 ms
7  2c0f:f4c0::d (2c0f:f4c0::d)  25.741 ms *  25.791 ms

v4 via ct to cloudflare dns

Code: 
traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 60 byte packets
1  dlinkrouter.Dlink (192.168.0.2)  0.749 ms  0.650 ms  1.176 ms
2  169-1-254-1.ip.afrihost.co.za (169.1.254.1)  3.086 ms  3.021 ms  2.948 ms
3  169-1-21-147.ip.afrihost.co.za (169.1.21.147)  3.370 ms  3.434 ms  3.368 ms
4  169-1-21-131.ip.afrihost.co.za (169.1.21.131)  4.325 ms  4.254 ms  3.891 ms
5  cloudflare.ixp.capetown (196.60.70.198)  4.280 ms  4.055 ms  4.142 ms
6  one.one.one.one (1.1.1.1)  5.792 ms  3.417 ms  3.340 ms
Click to expand...

Thanks for for this.

Can you do a traceroute to 2606:4700:4700::1111

I want to see how it compares to 1.1.1.1 and I'm trying to find a server hosted in CPT with IPv6 enabled to see if that also goes via JHB first to see if it's an announcement issue or IPv6 compatibility issue.
 
AfriNatic said:
Thanks for for this.

Can you do a traceroute to 2606:4700:4700::1111

I want to see how it compares to 1.1.1.1 and I'm trying to find a server hosted in CPT with IPv6 enabled to see if that also goes via JHB first to see if it's an announcement issue or IPv6 compatibility issue.
Click to expand...

JHB too, I've tried googles v6, cloudflares v6 and a few others, none go to CT

Code: 
traceroute to 2606:4700:4700::1111 (2606:4700:4700::1111), 30 hops max, 80 byte packets
 1  dlinkrouter.Dlink (2c0f:f4c0:2201:fcd8:c6e9:aff:fe31:eb85)  0.660 ms  1.215 ms  1.247 ms
 2  2c0f:f4c0:2200::1 (2c0f:f4c0:2200::1)  3.961 ms  3.721 ms  3.720 ms
 3  2c0f:f4c0:2000:3::d (2c0f:f4c0:2000:3::d)  3.559 ms  3.555 ms  7.561 ms
 4  2c0f:f4c0:2000:3::11 (2c0f:f4c0:2000:3::11)  7.647 ms  7.566 ms  7.325 ms
 5  2c0f:f708::d8 (2c0f:f708::d8)  26.615 ms 2c0f:f708::18 (2c0f:f708::18)  22.492 ms  22.416 ms
 6  cloudflare.ixp.joburg (2001:43f8:6d0::198)  26.382 ms  21.663 ms  21.565 ms
 7  2400:cb00:45:1024::c5ea:f119 (2400:cb00:45:1024::c5ea:f119)  26.311 ms 2400:cb00:45:1024::c5ea:f126 (2400:cb00:45:1024::c5ea:f126)  22.033 ms 2400:cb00:45:1024::c5ea:f10c (2400:cb00:45:1024::c5ea:f10c)  26.295 ms
 
AfriNatic said:
Thanks for for this.

Can you do a traceroute to 2606:4700:4700::1111

I want to see how it compares to 1.1.1.1 and I'm trying to find a server hosted in CPT with IPv6 enabled to see if that also goes via JHB first to see if it's an announcement issue or IPv6 compatibility issue.
Click to expand...

I've taken the Cape Town IP's off http://ipv6.ec2-reachability.amazonaws.com/ and done a traceroute6 to them and both (judging by the ping times) seem to go up to JHB

pi@4glass:~$ traceroute6 2406:da11:e6b:8100::ec2


traceroute to 2406:da11:e6b:8100::ec2 (2406:da11:e6b:8100::ec2), 30 hops max, 80 byte packets


1 dlinkrouter.Dlink (2c0f:f4c0:2201:fcd8:c6e9:aff:fe31:eb85) 0.814 ms 1.208 ms 1.325 ms


2 2c0f:f4c0:2200::1 (2c0f:f4c0:2200::1) 4.758 ms 5.503 ms 5.416 ms


3 2c0f:f4c0:2000:3::d (2c0f:f4c0:2000:3::d) 4.265 ms 4.696 ms 4.618 ms


4 2c0f:f4c0:2000:3::11 (2c0f:f4c0:2000:3::11) 5.119 ms 4.853 ms 7.437 ms


5 2620:107:4008:b66::1 (2620:107:4008:b66::1) 7.359 ms 7.517 ms 7.434 ms


6 * * *


7 2400:6500:0:ff::32 (2400:6500:0:ff::32) 27.976 ms 2400:6500:0:ff::33 (2400:6500:0:ff::33) 25.281 ms 25.023 ms


8 2400:6500:0:9002::7 (2400:6500:0:9002::7) 25.236 ms 2400:6500:0:9002::8 (2400:6500:0:9002::8) 25.013 ms 2400:6500:0:9002::7 (2400:6500:0:9002::7) 25.079 ms


9 2400:6500:0:7::6 (2400:6500:0:7::6) 25.192 ms 25.114 ms 2400:6500:0:7::8 (2400:6500:0:7::8) 25.212 ms


10 2400:6500:0:7::14 (2400:6500:0:7::14) 8.580 ms 2400:6500:0:7::15 (2400:6500:0:7::15) 8.413 ms 2400:6500:0:7::10 (2400:6500:0:7::10) 8.632 ms


11 2400:6500:0:7::19 (2400:6500:0:7::19) 4.247 ms 9.895 ms 2400:6500:0:7::18 (2400:6500:0:7::18) 4.667 ms


12 2400:6500:0:7::e (2400:6500:0:7::e) 8.960 ms 9.010 ms 2400:6500:0:7::f (2400:6500:0:7::f) 8.734 ms


13 2400:6500:0:7::9 (2400:6500:0:7::9) 8.976 ms 8.683 ms 8.764 ms


14 2400:6500:0:7::4 (2400:6500:0:7::4) 9.096 ms 2400:6500:0:7::3 (2400:6500:0:7::3) 8.791 ms 8.679 ms


15 2400:6500:0:4701:8000:0:6441:20 (2400:6500:0:4701:8000:0:6441:20) 8.781 ms 2400:6500:0:4701:8000:0:6441:100 (2400:6500:0:4701:8000:0:6441:100) 78.860 ms 2400:6500:0:4701:8000:0:6441:120 (2400:6500:0:4701:8000:0:6441:120) 78.700 ms


16 2400:6500:0:4701:8000:0:6442:50 (2400:6500:0:4701:8000:0:6442:50) 6.350 ms 2400:6500:0:4701:8000:0:6442:70 (2400:6500:0:4701:8000:0:6442:70) 6.235 ms 2400:6500:0:4701:8000:0:6442:e (2400:6500:0:4701:8000:0:6442:e) 62.397 ms


17 2400:6500:0:4701:8000:0:6442:df (2400:6500:0:4701:8000:0:6442:df) 5.868 ms 2400:6500:0:4701:8000:0:6442:e3 (2400:6500:0:4701:8000:0:6442:e3) 6.121 ms 2400:6500:0:4701:8000:0:6442:f5 (2400:6500:0:4701:8000:0:6442:f5) 5.827 ms


18 * * *


19 2406:da11:e6b:8100::ec2 (2406:da11:e6b:8100::ec2) 5.215 ms 5.283 ms 5.180 ms


pi@4glass:~$ traceroute6 2406:da00:1000::df5:fd


traceroute to 2406:da00:1000::df5:fd (2406:da00:1000::df5:fd), 30 hops max, 80 byte packets


1 dlinkrouter.Dlink (2c0f:f4c0:2201:fcd8:c6e9:aff:fe31:eb85) 0.757 ms 1.187 ms 1.249 ms


2 2c0f:f4c0:2200::1 (2c0f:f4c0:2200::1) 4.360 ms 4.275 ms 4.389 ms


3 2c0f:f4c0:2000:3::d (2c0f:f4c0:2000:3::d) 4.126 ms 3.883 ms 4.362 ms


4 2c0f:f4c0:2000:3::11 (2c0f:f4c0:2000:3::11) 7.668 ms 7.588 ms 7.716 ms


5 2620:107:4008:b66::1 (2620:107:4008:b66::1) 7.642 ms 7.566 ms 7.677 ms


6 * * *


7 2400:6500:0:ff::32 (2400:6500:0:ff::32) 34.476 ms 34.170 ms 34.239 ms


8 2400:6500:0:9002::7 (2400:6500:0:9002::7) 36.949 ms 36.873 ms 2400:6500:0:9002::1 (2400:6500:0:9002::1) 37.578 ms


9 2400:6500:0:7::6 (2400:6500:0:7::6) 33.771 ms 2400:6500:0:7::8 (2400:6500:0:7::8) 32.089 ms 32.158 ms


10 2400:6500:0:7::10 (2400:6500:0:7::10) 32.079 ms 2400:6500:0:7::f (2400:6500:0:7::f) 35.114 ms 2400:6500:0:7::11 (2400:6500:0:7::11) 34.746 ms


11 2400:6500:0:7::16 (2400:6500:0:7::16) 34.964 ms 6.640 ms 10.627 ms


12 2400:6500:0:7::f (2400:6500:0:7::f) 15.313 ms 2400:6500:0:7::12 (2400:6500:0:7::12) 60.251 ms 40.259 ms


13 2400:6500:0:7::9 (2400:6500:0:7::9) 45.001 ms 49.951 ms 2400:6500:0:7::a (2400:6500:0:7::a) 27.735 ms


14 2400:6500:0:7::1e (2400:6500:0:7::1e) 22.573 ms 2400:6500:0:7::2 (2400:6500:0:7::2) 32.514 ms 2400:6500:0:7::1e (2400:6500:0:7::1e) 17.423 ms


15 2400:6500:0:4702:8000:0:6441:0 (2400:6500:0:4702:8000:0:6441:0) 52.059 ms 2400:6500:0:4701:8000:0:6441:80 (2400:6500:0:4701:8000:0:6441:80) 127.063 ms 2400:6500:0:4701:8000:0:6441:60 (2400:6500:0:4701:8000:0:6441:60) 108.742 ms


16 2400:6500:0:4701:8000:0:6442:5c (2400:6500:0:4701:8000:0:6442:5c) 54.566 ms 2400:6500:0:4701:8000:0:6442:40 (2400:6500:0:4701:8000:0:6442:40) 84.956 ms 2400:6500:0:4703:8000:0:6442:34 (2400:6500:0:4703:8000:0:6442:34) 49.711 ms


17 2400:6500:0:4703:8000:0:6442:b1 (2400:6500:0:4703:8000:0:6442:b1) 49.955 ms 2400:6500:0:4701:8000:0:6442:f5 (2400:6500:0:4701:8000:0:6442:f5) 49.795 ms 2400:6500:0:4703:8000:0:6442:bb (2400:6500:0:4703:8000:0:6442:bb) 49.790 ms


18 * * *


19 2406:da00:1000::df5:fd (2406:da00:1000::df5:fd) 49.946 ms 49.894 ms 59.952 ms


pi@4glass:~$
Click to expand...

If I traceroute the v4 CPT ip it goes local (https://ec2-reachability.amazonaws.com/)

traceroute to 13.245.0.253 (13.245.0.253), 30 hops max, 60 byte packets


1 dlinkrouter.Dlink (192.168.0.2) 0.649 ms 0.697 ms 0.775 ms


2 169-1-254-1.ip.afrihost.co.za (169.1.254.1) 3.197 ms 3.122 ms 3.066 ms


3 169-1-21-147.ip.afrihost.co.za (169.1.21.147) 2.993 ms 3.208 ms 3.138 ms


4 169-1-21-131.ip.afrihost.co.za (169.1.21.131) 3.286 ms 3.222 ms 3.374 ms


5 52.95.217.240 (52.95.217.240) 4.173 ms 4.107 ms 4.627 ms


6 52.93.57.8 (52.93.57.8) 9.489 ms 52.93.57.88 (52.93.57.88) 4.412 ms 52.93.57.72 (52.93.57.72) 5.929 ms


7 52.93.57.129 (52.93.57.129) 5.137 ms 52.93.57.113 (52.93.57.113) 3.210 ms 52.93.57.23 (52.93.57.23) 4.312 ms


8 52.93.132.128 (52.93.132.128) 4.920 ms 52.93.134.66 (52.93.134.66) 7.798 ms 7.729 ms


9 * * *


10 150.222.94.192 (150.222.94.192) 4.972 ms 150.222.94.56 (150.222.94.56) 4.446 ms 150.222.94.162 (150.222.94.162) 4.682 ms


11 150.222.94.73 (150.222.94.73) 4.613 ms 150.222.94.243 (150.222.94.243) 4.715 ms 150.222.94.245 (150.222.94.245) 4.493 ms


12 150.222.94.72 (150.222.94.72) 5.296 ms 150.222.94.142 (150.222.94.142) 4.741 ms 150.222.94.68 (150.222.94.68) 5.128 ms


13 150.222.95.11 (150.222.95.11) 5.400 ms 150.222.94.97 (150.222.94.97) 5.327 ms 150.222.95.11 (150.222.95.11) 5.259 ms


14 150.222.93.198 (150.222.93.198) 4.580 ms 150.222.93.196 (150.222.93.196) 4.045 ms 5.513 ms


15 * * *


16 * * *


17 * * *


18 * * *


19 ec2-13-245-0-253.af-south-1.compute.amazonaws.com (13.245.0.253) 4.398 ms 4.113 ms 4.139 ms
Click to expand...
 
blunt said:
JHB too, I've tried googles v6, cloudflares v6 and a few others, none go to CT

Code: 
traceroute to 2606:4700:4700::1111 (2606:4700:4700::1111), 30 hops max, 80 byte packets
1  dlinkrouter.Dlink (2c0f:f4c0:2201:fcd8:c6e9:aff:fe31:eb85)  0.660 ms  1.215 ms  1.247 ms
2  2c0f:f4c0:2200::1 (2c0f:f4c0:2200::1)  3.961 ms  3.721 ms  3.720 ms
3  2c0f:f4c0:2000:3::d (2c0f:f4c0:2000:3::d)  3.559 ms  3.555 ms  7.561 ms
4  2c0f:f4c0:2000:3::11 (2c0f:f4c0:2000:3::11)  7.647 ms  7.566 ms  7.325 ms
5  2c0f:f708::d8 (2c0f:f708::d8)  26.615 ms 2c0f:f708::18 (2c0f:f708::18)  22.492 ms  22.416 ms
6  cloudflare.ixp.joburg (2001:43f8:6d0::198)  26.382 ms  21.663 ms  21.565 ms
7  2400:cb00:45:1024::c5ea:f119 (2400:cb00:45:1024::c5ea:f119)  26.311 ms 2400:cb00:45:1024::c5ea:f126 (2400:cb00:45:1024::c5ea:f126)  22.033 ms 2400:cb00:45:1024::c5ea:f10c (2400:cb00:45:1024::c5ea:f10c)  26.295 ms
Click to expand...

Okay that is why I want a server hosted in CPT with a IPv6 so we can rule the issues with the big CDNs any cast routes.
 
blunt said:
I've taken the Cape Town IP's off http://ipv6.ec2-reachability.amazonaws.com/ and done a traceroute6 to them and both (judging by the ping times) seem to go up to JHB



If I traceroute the v4 CPT ip it goes local (https://ec2-reachability.amazonaws.com/)
Click to expand...

It looks like we did hand over the traffic in CPT though.

4 2c0f:f4c0:2000:3::11 (2c0f:f4c0:2000:3::11) 7.668 ms 7.588 ms 7.716 ms
5 2620:107:4008:b66::1 (2620:107:4008:b66::1) 7.642 ms 7.566 ms 7.677 ms

Not sure why they took it to JHB first and then to CPT. Will investigate it.

Can you try to install IPvFoo browser plugin if you get a chance and see if you can find a speedtest server on speedtest.net in CPT that does IPv6 and do a test to it.

We should peer with with most in CPT so if the IPv6 stays in CPT we need to engage with these CDNs and see why they prefer JHB because we are IPv6 ready in all 3 Teraco's
 
AfriNatic said:
It looks like we did hand over the traffic in CPT though.

4 2c0f:f4c0:2000:3::11 (2c0f:f4c0:2000:3::11) 7.668 ms 7.588 ms 7.716 ms
5 2620:107:4008:b66::1 (2620:107:4008:b66::1) 7.642 ms 7.566 ms 7.677 ms

Not sure why they took it to JHB first and then to CPT. Will investigate it.

Can you try to install IPvFoo browser plugin if you get a chance and see if you can find a speedtest server on speedtest.net in CPT that does IPv6 and do a test to it.

We should peer with with most in CPT so if the IPv6 stays in CPT we need to engage with these CDNs and see why they prefer JHB because we are IPv6 ready in all 3 Teraco's
Click to expand...
This is just via a pi at my parents place, will remote desktop when I can to do this.
 
blunt said:
I traceroute6'd to the IP not the host, but the router is set on default DNS again
Click to expand...

If you get a chance can you do a few like to outlook.com or onderive.com ect like a few hostnames that we know is IPv6 capable.
 
AfriNatic said:
If you get a chance can you do a few like to outlook.com or onderive.com ect like a few hostnames that we know is IPv6 capable.
Click to expand...
sure

traceroute to www.outlook.com (2603:1006:1:b::2), 30 hops max, 80 byte packets


1 dlinkrouter.Dlink (2c0f:f4c0:2201:fcd8:c6e9:aff:fe31:eb85) 0.813 ms 1.286 ms 1.342 ms


2 2c0f:f4c0:2200::1 (2c0f:f4c0:2200::1) 5.500 ms 5.194 ms 5.341 ms


3 2c0f:f4c0:2000:3::d (2c0f:f4c0:2000:3::d) 5.033 ms 4.960 ms 4.357 ms


4 2c0f:f4c0:2000:3::11 (2c0f:f4c0:2000:3::11) 5.038 ms 5.186 ms 5.108 ms


5 2a01:111:2000:1::2ca2 (2a01:111:2000:1::2ca2) 38.924 ms 43.831 ms 48.594 ms


6 ae22-0.icr01.cpt20.ntwk.msn.net (2a01:111:2000:2:8000::22a) 7.628 ms 5.522 ms 5.410 ms


7 2603:1080:101:8101::6 (2603:1080:101:8101::6) 5.216 ms 2603:1080:101:8100::6 (2603:1080:101:8100::6) 7.939 ms 2603:1080:101:8101::6 (2603:1080:101:8101::6) 7.237 ms


8 2603:1080:101:8000::106 (2603:1080:101:8000::106) 7.305 ms 2603:1080:101:8000::86 (2603:1080:101:8000::86) 7.073 ms 2603:1080:101:8000::6 (2603:1080:101:8000::6) 5.425 ms


9 2603:1080:101:8300::106 (2603:1080:101:8300::106) 5.303 ms 2603:1080:101:8200::126 (2603:1080:101:8200::126) 5.719 ms 2603:1080:101:8300::116 (2603:1080:101:8300::116) 5.641 ms


10 2603:1080:103:7::1be (2603:1080:103:7::1be) 5.335 ms 2603:1080:103:7::1d2 (2603:1080:103:7::1d2) 11.482 ms 2603:1080:103:5::1c6 (2603:1080:103:5::1c6) 7.356 ms


11 2603:1080:103:dc:: (2603:1080:103:dc::) 15.546 ms 20.268 ms 21.809 ms


12 * * *


13 * * *


14 * * *


15 * * *
Click to expand...

traceroute to www.facebook.com (2a03:2880:f124:83:face:b00c:0:25de), 30 hops max, 80 byte packets


1 dlinkrouter.Dlink (2c0f:f4c0:2201:fcd8:c6e9:aff:fe31:eb85) 2.096 ms 1.959 ms 1.845 ms


2 2c0f:f4c0:2200::1 (2c0f:f4c0:2200::1) 7.401 ms 6.762 ms 6.932 ms


3 2c0f:f4c0:2000:3::d (2c0f:f4c0:2000:3::d) 6.737 ms 6.351 ms 6.974 ms


4 2c0f:f4c0:2000:3::11 (2c0f:f4c0:2000:3::11) 6.871 ms 6.684 ms 6.777 ms


5 2c0f:f708::18 (2c0f:f708::18) 23.229 ms 2c0f:f708::d8 (2c0f:f708::d8) 23.125 ms 23.166 ms


6 ae2.pr01.jnb1.tfbnw.net (2620:0:1cff:dead:beee::502) 23.061 ms 35.206 ms 34.851 ms


7 po103.psw04.jnb1.tfbnw.net (2620:0:1cff:dead:bef0::8b) 23.716 ms po103.psw03.jnb1.tfbnw.net (2620:0:1cff:dead:bef0::81) 25.560 ms 20.963 ms


8 po4.msw1aj.01.jnb1.tfbnw.net (2a03:2880:f024:ffff::af) 23.148 ms po3.msw1aj.01.jnb1.tfbnw.net (2a03:2880:f024:ffff::7b) 22.949 ms po2.msw1ai.01.jnb1.tfbnw.net (2a03:2880:f024:ffff::45) 23.386 ms


9 edge-star-mini6-shv-01-jnb1.facebook.com (2a03:2880:f124:83:face:b00c:0:25de) 22.886 ms 22.780 ms 22.860 ms
Click to expand...

traceroute to www.hetzner.de (2a01:4f8:0:5176::3), 30 hops max, 80 byte packets


1 dlinkrouter.Dlink (2c0f:f4c0:2201:fcd8:c6e9:aff:fe31:eb85) 2.094 ms 1.990 ms 1.845 ms


2 2c0f:f4c0:2200::1 (2c0f:f4c0:2200::1) 4.944 ms 5.036 ms 4.648 ms


3 2c0f:f4c0:2000:3::d (2c0f:f4c0:2000:3::d) 4.894 ms 4.421 ms 5.182 ms


4 2c0f:f4c0:2000:3::11 (2c0f:f4c0:2000:3::11) 5.073 ms 4.915 ms 4.798 ms


5 2c0e:2008:0:177::1 (2c0e:2008:0:177::1) 9.488 ms 9.374 ms 13.188 ms


6 2001:7f8:4::616c:1 (2001:7f8:4::616c:1) 149.295 ms 153.428 ms 153.086 ms


7 core6.par.hetzner.com (2a01:4f8:0:3::3ad) 163.293 ms 160.536 ms 156.010 ms


8 2a01:4f8:0:3::411 (2a01:4f8:0:3::411) 172.907 ms core11.nbg1.hetzner.com (2a01:4f8:0:3::3b1) 191.012 ms 2a01:4f8:0:3::411 (2a01:4f8:0:3::411) 168.627 ms


9 ex9k2.dc1.nbg1.hetzner.com (2a01:4f8:0:3::156) 173.490 ms 173.273 ms ex9k2.dc1.nbg1.hetzner.com (2a01:4f8:0:3::15a) 169.393 ms


10 * * *


11 * * *


12 * * *
Click to expand...

traceroute to domains.co.za (2606:4700:20::ac43:4945), 30 hops max, 80 byte packets


1 dlinkrouter.Dlink (2c0f:f4c0:2201:fcd8:c6e9:aff:fe31:eb85) 2.272 ms 2.115 ms 1.979 ms


2 2c0f:f4c0:2200::1 (2c0f:f4c0:2200::1) 4.596 ms 5.273 ms 5.327 ms


3 2c0f:f4c0:2000:3::d (2c0f:f4c0:2000:3::d) 4.050 ms 4.094 ms 4.354 ms


4 2c0f:f4c0:2000:3::11 (2c0f:f4c0:2000:3::11) 7.824 ms 7.575 ms 7.608 ms


5 2c0f:f708::d8 (2c0f:f708::d8) 22.945 ms 2c0f:f708::18 (2c0f:f708::18) 22.627 ms 2c0f:f708::d8 (2c0f:f708::d8) 26.598 ms


6 cloudflare.ixp.joburg (2001:43f8:6d0::198) 26.489 ms 26.766 ms 22.636 ms


7 2400:cb00:45:1024::c5ea:f116 (2400:cb00:45:1024::c5ea:f116) 22.524 ms 2400:cb00:45:1024::c5ea:f120 (2400:cb00:45:1024::c5ea:f120) 25.434 ms 2400:cb00:45:1024::c5ea:f113 (2400:cb00:45:1024::c5ea:f113) 24.866 ms
Click to expand...

traceroute to bbc.co.uk (2a04:4e42:600::81), 30 hops max, 80 byte packets


1 dlinkrouter.Dlink (2c0f:f4c0:2201:fcd8:c6e9:aff:fe31:eb85) 0.679 ms 1.123 ms 1.200 ms


2 2c0f:f4c0:2200::1 (2c0f:f4c0:2200::1) 3.718 ms 3.456 ms 3.966 ms


3 2c0f:f4c0:2000:3::d (2c0f:f4c0:2000:3::d) 3.301 ms 7.160 ms 7.086 ms


4 2c0f:f4c0:2000:3::11 (2c0f:f4c0:2000:3::11) 7.149 ms 7.070 ms 7.185 ms


5 * * *


6 * * *


7 * * *


8 * * *


9 * * *
Click to expand...

first time i've seen afrihost.ixp.capetown
traceroute to www.apple.com (2600:1416:a000:18b::1aca), 30 hops max, 80 byte packets


1 dlinkrouter.Dlink (2c0f:f4c0:2201:fcd8:c6e9:aff:fe31:eb85) 2.061 ms 1.929 ms 1.808 ms


2 2c0f:f4c0:2200::1 (2c0f:f4c0:2200::1) 4.671 ms 4.150 ms 4.603 ms


3 2c0f:f4c0:2000:3::d (2c0f:f4c0:2000:3::d) 4.272 ms 3.917 ms 3.643 ms


4 2c0f:f4c0:2000:3::11 (2c0f:f4c0:2000:3::11) 4.534 ms 4.428 ms 4.208 ms


5 afrihost.ixp.capetown (2001:43f8:6d1::113) 6.794 ms 6.688 ms 6.863 ms


6 * * *


7 * * *


8 * * *


9 * * *


10 * * *
Click to expand...
 
AfriNatic said:
Thanks for the tests provided.
Click to expand...

here's a cpt server that goes locally

traceroute to cape-connect.com (2001:43f8:1800:1::131), 30 hops max, 80 byte packets
1 dlinkrouter.Dlink (2c0f:f4c0:2201:fcd8:c6e9:aff:fe31:eb85) 0.678 ms 1.296 ms 1.363 ms
2 2c0f:f4c0:2200::1 (2c0f:f4c0:2200::1) 7.242 ms 7.540 ms 7.465 ms
3 2c0f:f4c0:2000:3::d (2c0f:f4c0:2000:3::d) 7.203 ms 7.138 ms 6.848 ms
4 2c0f:f4c0:2000:3::11 (2c0f:f4c0:2000:3::11) 7.477 ms 7.278 ms 7.202 ms
5 2001:43f8:6d1::71:11 (2001:43f8:6d1::71:11) 7.417 ms 7.169 ms 7.259 ms
6 srv1.tfyre.co.za (2001:43f8:1800:1::131) 7.409 ms 4.992 ms 4.680 ms
Click to expand...
 
ghostim said:
@AfriNatic
Will I get into trouble if I play with ipv6 to ipv4 tunnels on Openserve fibre ?
Click to expand...

No problem with that at all. I used to do it with my Openserve connection.

Ideally when we have IPv6 setup it will be native IPv6 which you do not need to do tunneling for.
 
AfriNatic said:
No problem with that at all. I used to do it with my Openserve connection.

Ideally when we have IPv6 setup it will be native IPv6 which you do not need to do tunneling for.
Click to expand...
Thnx, I understand your problem with Openserve ipv6, just want to play aroung a bit with ipv6.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X