New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Bizzare IPv6 routing from HE.net?
I have just made a traceroute from Vienna to Paris (SyS), but I have been taken from Vienna to Paris (HE.net), then New York (HE.net), then Canada, then US, then Canada, then Paris ?!!!
It takes 165ms to ping from Vienna to Paris via 2 continents (allez-retour):
traceroute to abc.xyz.net (2001:41d0:123:456::789), 30 hops max, 72 byte packets
1 (cut)
2 (cut)
3 2001:7f8:30:0:2:1:0:6939 (2001:7f8:30:0:2:1:0:6939) 0.761 ms 0.341 ms 1.596 ms
4 100ge13-1.core1.par2.he.net (2001:470:0:3f4::1) 16.064 ms 16.103 ms 16.012 ms
5 100ge11-2.core1.nyc4.he.net (2001:470:0:54::1) 86.349 ms 86.266 ms 86.350 ms
6 paix-ny.**bell.ca** (2001:504:f::577:1) 86.674 ms 87.214 ms *
7 tcore4-newyorkaa_lo0.net.bell.ca (::ffff:64.230.15.228) 164.099 ms tcore3-newyorkaa_lo0.net.bell.ca (::ffff:64.230.15.227) 159.156 ms 162.123 ms
8 tcore3-montreal02_lo0.net.bell.ca (::ffff:64.230.193.101) 169.200 ms 169.526 ms ncore4-montreal02_lo0.net.bell.ca (::ffff:64.230.193.102) 165.399 ms
9 tcore4-toronto21_lo0_core.net.bell.ca (::ffff:64.230.193.229) 164.142 ms tcore3-toronto63_lo0.net.bell.ca (::ffff:64.230.193.143) 163.120 ms 161.472 ms
10 tcore3-calgaryqa_lo0.net.bell.ca (::ffff:64.230.15.147) 167.936 ms 168.975 ms 167.692 ms
11 tcore3-calgary68_lo0.net.bell.ca (::ffff:64.230.15.182) 166.450 ms tcore4-calgary68_lo0.net.bell.ca (::ffff:64.230.15.183) 162.939 ms 161.717 ms
12 * * *
13 2001:4958:1::b (2001:4958:1::b) 162.345 ms 162.389 ms 162.457 ms
14 * * *
15 be300.pdx-pdx02-sbb1-nc5.oregon.us (2607:5300::259c) 162.270 ms be300.pdx-prt1-sbb1-nc5.oregon.us (2607:5300::2594) 164.283 ms 164.088 ms
16 2001:41d0:aaaa:100::5 (2001:41d0:aaaa:100::5) 185.397 ms 2001:41d0:aaaa:100::3 (2001:41d0:aaaa:100::3) 178.835 ms 181.668 ms
17 2001:41d0:aaaa:100::2 (2001:41d0:aaaa:100::2) 161.315 ms 162.671 ms 2001:41d0:aaaa:100::4 (2001:41d0:aaaa:100::4) 162.818 ms
18 chi-5-a9.il.us (2607:5300::2556) 167.511 ms 167.475 ms chi-1-a9.il.us (2607:5300::2554) 161.214 ms
19 be103.bhs-g2-nc5.qc.ca (2607:5300::1d0) 166.780 ms 166.377 ms 166.781 ms
20 * * *
21 * * *
22 * * be103.gra-g1-nc5.fr.eu (2001:41d0::430) 162.953 ms
23 vl100.gra-d2-a75.fr.eu (2001:41d0::437) 162.696 ms 164.841 ms 165.595 ms
24 2001:41d0:0:50::5:47 (2001:41d0:0:50::5:47) 163.391 ms 2001:41d0:0:50::5:43 (2001:41d0:0:50::5:43) 166.649 ms 2001:41d0:0:50::5:41 (2001:41d0:0:50::5:41) 161.308 ms
25 2001:41d0:0:50::1:9201 (2001:41d0:0:50::1:9201) 166.223 ms 2001:41d0:0:50::1:9203 (2001:41d0:0:50::1:9203) 160.021 ms 2001:41d0:0:50::1:9201 (2001:41d0:0:50::1:9201) 164.643 ms
26 vl15.gra2-sdtor46a-n3.fr.eu (2001:41d0:0:50::b01f) 161.967 ms 161.171 ms 169.382 ms
27 (cut) 165.501 ms 165.228 ms 165.201 ms
Comments
@yoursunny I would need an IPv6 Advocate
Routing is determined by BGP.
You need to adjust BGP announcement from the destination network.
I would expect this should sort out by itself in a few minutes/hours, if not, write to OVH's traceroute mailing list as described in https://www.lowendtalk.com/discussion/143996/ovh-asia-pacific-network-latest-latency-optimizations/p1
Since the other end in Vienna is likely the Alwyzon network: it appears one of OVH edge routers lost all their IPv6 routes. The Alwyzon routers receive all IPv4 subnets from OVH but 0 IPv6 routes. Traffic is thus re-routed and the initial pick of Hurricane Electric was definitely not a good choice.
Don't bother to try to reach out to OVH, their NOC has already been informed. In the meanwhile, the routes via HE have been dropped and traffic is now routed over Prague & Frankfurt:
— Michael
Yes, it's great. Thank you for your information.