Vumatel Fibre + ISP for IPv6

I have come to the realisation that the best way, as [MENTION=394133]PBCool[/MENTION] puts it, is to run with a tunnel. I am in progress of (attempting) to get my Vuma line over to CISP and then will run my HE tunnel (www.tunnelbroker.net) service over that. A small setup on a pfSense box to get the whole thing running. Was OK until the current ISP had network issues...
 
joburg_guy said:
I have come to the realisation that the best way, as [MENTION=394133]PBCool[/MENTION] puts it, is to run with a tunnel. I am in progress of (attempting) to get my Vuma line over to CISP and then will run my HE tunnel (www.tunnelbroker.net) service over that. A small setup on a pfSense box to get the whole thing running. Was OK until the current ISP had network issues...
Click to expand...

I do this currently; the config on tunnelbroker is comprehensive enough and works very well... although I don't use IPv6 for anything at the moment.
 
I did this earlier this year, and found that some breakouts only happened in London.

HE: JHB POP
Work link: Seacom V6

Traceroute goes all the way over London to SA.

Sadly I didn't have another local network to test. Should be easy enough, as just my RADVD on pfSense is disabled. Lemme see...
(Vuma on CellC, 50/50, using HE on pfSense)

traceroute6 to REMOVED (Seacom) from REMOVED (HE), 64 hops max, 12 byte packets
1 <REMOVED> 1.636 ms 1.418 ms 1.385 ms
2 10ge11-15.core1.jnb1.he.net 1.335 ms 1.412 ms 1.282 ms
3 10ge3-11.core1.lon2.he.net 163.879 ms 162.882 ms 174.672 ms
4 2001:7f8:4::90ec:2 162.882 ms 162.792 ms 162.875 ms
5 ae-5-0.er6-05-lhr.uk.seacomnet.com 162.812 ms 162.870 ms 162.849 ms
6 *
xe-0-0-0-2.cr6-02-lhr.uk.seacomnet.com 165.113 ms 163.914 ms
7 xe-0-1-0-3.cr6-02-cpt.za.seacomnet.com 303.944 ms
xe-0-0-0-1.cr6-01-cpt.za.seacomnet.com 304.172 ms
xe-0-0-0-0.cr6-02-jnb.za.seacomnet.com 303.130 ms
8 xe-0-0-0-8.cr6-02-jnb.za.seacomnet.com 320.227 ms
xe-0-0-0-2.cr6-01-jnb.za.seacomnet.com 320.039 ms
xe-0-0-0-8.cr6-02-jnb.za.seacomnet.com 319.864 ms
9 ae-6.er6-02-jnb.za.seacomnet.com 318.642 ms 318.392 ms 318.557 ms
10 xe-0-1.es6-14-jnb.za.seacomnet.com 318.923 ms 318.812 ms 318.854 ms
11 xe-0-2.es6-12-jnb.za.seacomnet.com 319.043 ms 318.950 ms 319.112 ms
12 xe-0-1.es6-08-jnb.za.seacomnet.com 323.854 ms 319.429 ms 319.672 ms
13 xe-0-0-24.es6-32-jnb.za.seacomnet.com 319.871 ms 320.497 ms 319.707 ms
14 xe-0-0-25.es6-47-jnb.za.seacomnet.com 320.307 ms 320.115 ms 319.852 ms
15 xe-0-0-24.es6-29-jnb.za.seacomnet.com 319.836 ms 320.256 ms 319.875 ms
16 * * *
Click to expand...

There seems to be a routing issue at the end - will have to investigate.

To Google it looks a LOT better, but still not usable, IMO:

traceroute6 to www.google.com (2a00:1450:4009:809::2004) from REMOVED, 64 hops max, 16 byte packets
1 <REMOVED> 1.464 ms 1.437 ms 1.471 ms
2 10ge11-15.core1.jnb1.he.net 1.506 ms 1.328 ms 1.348 ms
3 google.jinx.net.za 1.468 ms 1.464 ms 1.396 ms
4 *
2001:4860::9:4000:ce66 180.414 ms 180.263 ms
5 2001:4860:0:1101::1 180.170 ms 181.234 ms 180.821 ms
6 2001:4860:0:1::8f 181.468 ms 180.332 ms 180.291 ms
7 lhr25s10-in-x04.1e100.net 178.767 ms 179.988 ms 180.001 ms
Click to expand...

Ping results to Google:
PING6(56=40+8+8 bytes) REMOVED --> 2a00:1450:4009:809::2004

--- 2a00:1450:4009:809::2004 ping6 statistics ---
10 packets transmitted, 9 packets received, 10.0% packet loss
round-trip min/avg/max/std-dev = 180.403/180.967/182.053/0.615 ms
Click to expand...

From Seacom to Google:

traceroute to www.google.com (2c0f:fb50:4002:802::2004), 30 hops max, 80 byte packets
1 REMOVED 1.786 ms 1.739 ms 1.682 ms
2 xe-0-0-25.es6-32-jnb.za.seacomnet.com (2c0f:feb0:1:2::335) 44.143 ms 44.466 ms 44.453 ms
3 xe-0-0-25.es6-32-jnb.za.seacomnet.com (2c0f:feb0:1:2::446) 1.527 ms 1.895 ms 1.878 ms
4 xe-0-2.es6-08-jnb.za.seacomnet.com (2c0f:feb0:1:2::262) 0.975 ms 0.976 ms 0.951 ms
5 xe-0-1.es6-12-jnb.za.seacomnet.com (2c0f:feb0:1:2::23e) 4.951 ms 4.939 ms 4.915 ms
6 xe-0-2.es6-14-jnb.za.seacomnet.com (2c0f:feb0:1:2::23a) 1.290 ms 1.176 ms 1.523 ms
7 xe-1-3-0-0.er6-02-jnb.za.seacomnet.com (2c0f:feb0:1:2::255) 14.740 ms 1.421 ms 1.399 ms
8 ae-4-0.pp6-01-jnb.za.seacomnet.com (2c0f:feb0:b::1:8) 2.199 ms ae-3-0.pp6-01-jnb.za.seacomnet.com (2c0f:feb0:b::8) 1.628 ms 1.643 ms
9 2001:4860:1:1:0:90ec:0:1 (2001:4860:1:1:0:90ec:0:1) 1.560 ms 1.566 ms 1.524 ms
10 2001:4860:0:1::18b (2001:4860:0:1::18b) 1.482 ms 1.463 ms 1.441 ms
11 2c0f:fb50:4002:802::2004 (2c0f:fb50:4002:802::2004) 1.333 ms 1.340 ms 1.321 ms
Click to expand...


So it will depend where your landing point is. Some connections will work a LOT better than others.

Question from my end: In the HE / Seacom issue above, would it be better to address this to Seacom (who I have a contract with) or to HE support? It seems to be that the announce between the networks are only done in London, not here, where both have POPs.

Also, HE seems to perform badly to local destinations. I don't think my ISP has much to do with this?

EDIT: Re the Seacom/HE Google difference ... I just noticed the IPs are different. Here's the trace to the same IP as Seacom used:

traceroute6 to 2c0f:fb50:4002:802::2004 (2c0f:fb50:4002:802::2004) from REMOVED, 64 hops max, 12 byte packets
1 REMOVED 1.637 ms 1.485 ms 1.489 ms
2 10ge11-15.core1.jnb1.he.net 5.987 ms 1.337 ms 1.293 ms
3 google.jinx.net.za 1.431 ms 1.530 ms 1.362 ms
4 2001:4860:0:1::18b 1.505 ms 1.454 ms 1.756 ms
5 2c0f:fb50:4002:802::2004 1.379 ms 1.354 ms 1.385 ms
Click to expand...

PING6(56=40+8+8 bytes) REMOVED --> 2c0f:fb50:4002:802::2004

--- 2c0f:fb50:4002:802::2004 ping6 statistics ---
20 packets transmitted, 20 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 1.286/1.331/1.414/0.032 ms
Click to expand...

Much better. I use 8.8.8.8 as DNS server at work, and 1.1.1.1 at home. Might be where my issue lies ...
 
Last edited:
Apparently Vumatel are working on support for v6. For now you would have to tunnel.
 
Native IPv6 is available on Openserve, push your ISP to get it implemented!
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X