MTN Business in support of World IPv6 Day

[jes]

MTN Business in support of World IPv6 Day

MTN business supports IPv6 day’s aims to create awareness regarding the diminishing number of IPv4.

 

[Gimli_]

So they support the day, whoopy doo. What did they do about it? Do they offer their website or services on ipv6 network? Bet you they don't!

 

[Deckert]

So they support the day, whoopy doo. What did they do about it? Do they offer their website or services on ipv6 network? Bet you they don't!

Well, actually they do. Sort-of.

Their website is IPv6 enabled, but they're having a few issues with duplicated packets it seems. I can connect to them using pure IPv6 though.

tva@izar:~$ host -t aaaa www.mtnbusiness.co.za
www.mtnbusiness.co.za has IPv6 address 2001:4218:0:1::1

and:

tva@izar:~$ ping6 -n -c 3 www.mtnbusiness.co.za
PING www.mtnbusiness.co.za(2001:4218:0:1::1) 56 data bytes
64 bytes from 2001:4218:0:1::1: icmp_seq=1 ttl=50 time=342 ms
64 bytes from 2001:4218:0:1::1: icmp_seq=1 ttl=50 time=342 ms (DUP!)
64 bytes from 2001:4218:0:1::1: icmp_seq=2 ttl=50 time=342 ms
64 bytes from 2001:4218:0:1::1: icmp_seq=2 ttl=50 time=342 ms (DUP!)

Looking at the high latency, they don't peer locally on an IPv6 level, or at least not with Posix, which is where we currently get our IPv6 connection from.

Lastly, they seem to be keeping the IPv6 koolaid for themsleves - When asking for IPv6 connectivity, our account manager stated that "we don't issue IPv6 blocks at this stage and we have no immediate plans for this". What's up with that MTN Business?

--deckert

 

[ambo]

Looking at the high latency, they don't peer locally on an IPv6 level, or at least not with Posix, which is where we currently get our IPv6 connection from.

This is a known problem with MTN's peering policy.

PING www.mtnbusiness.co.za(2001:4218:0:1::1) 56 data bytes
64 bytes from 2001:4218:0:1::1: icmp_seq=1 ttl=55 time=420 ms
64 bytes from 2001:4218:0:1::1: icmp_seq=1 ttl=55 time=421 ms (DUP!)
64 bytes from 2001:4218:0:1::1: icmp_seq=2 ttl=55 time=420 ms
64 bytes from 2001:4218:0:1::1: icmp_seq=2 ttl=55 time=420 ms (DUP!)
64 bytes from 2001:4218:0:1::1: icmp_seq=3 ttl=55 time=459 ms
64 bytes from 2001:4218:0:1::1: icmp_seq=3 ttl=55 time=459 ms (DUP!)
64 bytes from 2001:4218:0:1::1: icmp_seq=4 ttl=55 time=420 ms
64 bytes from 2001:4218:0:1::1: icmp_seq=4 ttl=55 time=420 ms (DUP!)

EDIT: I'm not sure what they broke to create the DUP!licate packets. :wtf:

 

[InTheCube]

^^ These are exactly the kind of things that World IPv6 Day is meant to uncover. Also, to create more awareness around IPv6 and kickstart the long arduous migration ahead...