MyBroadband Web Server and IPv6

[portcullis]

If I access www.mybroadband.co.za via IPv4, traffic flies down NAPAfrica.

However, if I do the same via IPv6:

C:\Users\noc2.SOMERSETWEST>tracert www.mybroadband.co.za

Tracing route to www.mybroadband.co.za [2400:cb00:2048:1::6814:476e]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 2c0f:f470:2:2::1
2 11 ms 9 ms 15 ms 2c0f:f470:0:8::1
3 12 ms 10 ms 10 ms 2c0f:f470:0:4::2
4 15 ms 9 ms 10 ms 2c0f:f470::1
5 12 ms 16 ms 11 ms 2c0f:fa90:200:2:1::2
6 9 ms 5 ms 8 ms 2c0f:fa90:0:2::7
7 169 ms 164 ms 169 ms workonline-ic-314980-ldn-b3.c.telia.net [2001:2000:3080:e91::2]
8 156 ms 163 ms 159 ms ldn-b3-link.telia.net [2001:2000:3080:e91::1]
9 161 ms 160 ms 167 ms ldn-b5-v6.telia.net [2001:2000:3018:b::1]
10 155 ms 162 ms 159 ms cloudflare-ic-306325-ldn-b3.c.telia.net [2001:2000:3080:a4b::2]
11 160 ms 159 ms 159 ms 2400:cb00:2048:1::6814:476e

Trace complete.

That 2400:cb00:2048:1::6814:476e address belongs to CloudFlare.

Obviously, something's not right.

Who do I report this to?

 

[cfilorux]

Experiment without control

Perhaps you should have a look who the IPv4 IP address belongs to ...

 

[halfmoonforever]

MyBB is behind Cloudflare, could be a misconfig on their side sending you to a node overseas

 

[drs]

6 9 ms 5 ms 8 ms 2c0f:fa90:0:2::7
7 169 ms 164 ms 169 ms workonline-ic-314980-ldn-b3.c.telia.net [2001:2000:3080:e91::2]

That's the problem. Workonline is taking an international route to Cloudflare.

Who do I report this to?

Workonline. Ask them to establish IPv6 peering with Cloudflare in Joburg.

 

[portcullis]

That's the problem. Workonline is taking an international route to Cloudflare.

Workonline. Ask them to establish IPv6 peering with Cloudflare in Joburg.

Thanks.

We peer at NAP Jhb. So do Cloudflare.

https://www.napafrica.net/peering-clients/

This should route the same way that traffic to Google routes:

C:\Users\noc2.SOMERSETWEST>tracert www.google.com

Tracing route to www.google.com [2c0f:fb50:4002:802::2004]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 2c0f:f470:2:2::1
2 5 ms 5 ms 3 ms 2c0f:f470:0:8::1
3 6 ms 9 ms 9 ms 2c0f:f470:0:4::2
4 7 ms 6 ms 4 ms 2c0f:f470::1
5 24 ms 21 ms 25 ms 2c0f:f470:0:2::2
6 24 ms 24 ms 24 ms 2001:43f8:6d0::a
7 28 ms 24 ms 25 ms 2001:4860:0:1::18b
8 24 ms 25 ms 26 ms 2c0f:fb50:4002:802::2004

Trace complete.

Why it's going down WOL is a mystery as SEACOM is our primary for IPv6. Maybe this is more contractual that peering. Many companies route their clients' clients down the "paid for" links in preference to peering links. For example, Bitco clients generally can't peer with SEACOM.

I'll ask our BGP guys to contact Cloudflare, and WOL. Maybe Cloudflare aren't advertising all their prefixes via NAP. Maybe they have a contractual arrangement with WOL.

 

[drs]

We peer at NAP Jhb. So do Cloudflare.

It's all very well being present at the same IXP, but one needs to negotiate a BGP peering session with the other network (in this case, Cloudflare) before your traffic can be routed to/from them over the IXP. It's not automatic (except if the IXP has a route-server and both networks are peering with it.)

I'm sure your "BGP guys" will sort it out. Cloudflare advertise that their peering policy is generally open: https://www.peeringdb.com/net/4224

 

[portcullis]

It's all very well being present at the same IXP, but one needs to negotiate a BGP peering session with the other network (in this case, Cloudflare) before your traffic can be routed to/from them over the IXP. It's not automatic (except if the IXP has a route-server and both networks are peering with it.)

NAP CTN and JHB have route servers.

As of just now, we are picking up 5945 IPv4 and 238 IPv6 routes from the NAP CTN route server.
The JHB numbers are 14448 IPv4 and 236 IPv6.

We've only ever entered into four direct peering arrangements over NAP in Cape Town and one in Johannesburg. All the other routes are offered up by the route servers.

It's crazy if you think we can trace to Rwanda in less than 80ms over NAP and Liquid, but need to go to the UK to browse MyBroadband.

Meanwhile, we have received this response from Cloudflare:

Unfortunately we re not able to peering on NAPAfrica, but you should see our prefixes on the route server via our upstream AS37179 in Johannesburg, possibly also Cape Town.

 

[Murmaider]

If I remember right, mybroadband uses a IPv4 to IPv6 tunnel through he.net - Cloudflare is probably routing the IPv6 traffic through the UK to reach the he.net ipv6 range.