[afripv6-discuss] What have you done for IPv6 lately, since the 1st of January, 2013?

Nishal Goburdhan ndg at ieee.org
Wed Feb 20 13:22:32 SAST 2013

On 20 Feb 2013, at 12:02 PM, SM <sm at resistor.net> wrote:

> Hi Mark,
> At 08:00 19-02-2013, Mark Elkins wrote:
>> Careful, www.co.za is indeed IPv4 only - but has nothing to do with the
>> registry business in South Africa.
> Ok.
> The consumer end of the IPv6 problem in South Africa seems to be with the "IP connect" used for the ADSL access.

more correctly:
"the barrier to delivering native IPv6 services to..."

ISPs that offer DSL services in ZA are still able to offer IPv6, albeit tunnelled.  
my, to-date tunnelled, service to home has not shown me network related problems, in the "network part" of the service i receive.
there is, of course, incongruency in the manner that content is available over IPv4 and IPv6.

one example is below:
katala:~ nishal$ ping -c2 www.cisco.com
PING e144.dscb.akamaiedge.net ( 56 data bytes
64 bytes from icmp_seq=0 ttl=60 time=31.248 ms
64 bytes from icmp_seq=1 ttl=60 time=43.125 ms
--- e144.dscb.akamaiedge.net ping statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 31.248/37.187/43.125/5.938 ms

katala:~ nishal$ ping6 -c2 www.cisco.com
PING6(56=40+8+8 bytes) 2c0f:fc00:a000:1010:9953:b7f2:be57:56b0 --> 2a02:26f0:32:2:8100::90
16 bytes from 2a02:26f0:32:2:8100::90, icmp_seq=0 hlim=244 time=190.837 ms
16 bytes from 2a02:26f0:32:2:8100::90, icmp_seq=1 hlim=244 time=193.521 ms
--- e144.dscb.akamaiedge.net ping6 statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 190.837/192.179/193.521/1.342 ms



More information about the afripv6-discuss mailing list