|
Ticket ID: SIXXS #10567466 Ticket Status: Resolved PoP:
Routing gone loop
![[de]](/s/countries/de.gif) Shadow Hawkins on Tuesday, 26 November 2013 12:09:42
Dear Sixxs staff.
From inside of my tunnel to the rest of the world, about 5% of all requests get routed at all. Usually ping6 results with "Destination unreachable: Address unreachable".
Routing from outside to my tunnel shows that uslax02 has some internal routing loop issues.
See traceroute66 attached, that's how at least my german home connection to the tunnel gets routed. But because the routing issue is not in germany but cleraly nearby uslax02 itself, I guess others have similar routing experiences.
:~$ traceroute6 cl-61.lax-02.us.sixxs.net
traceroute to cl-61.lax-02.us.sixxs.net (2607:f878:fe00:3c::2) from 2001:470:1f0b:212:885a:9ad1:1516:4bd3, 30 hops max, 16 byte packets
1 goli-wrt.internal.g4n.de (2001:470:1f0b:212::1) 5.516 ms 0.638 ms 0.551 ms
2 goli-1.tunnel.tserv6.fra1.ipv6.he.net (2001:470:1f0a:212::1) 19.474 ms 23.914 ms 15.827 ms
3 v320.core1.fra1.he.net (2001:470:0:69::1) 17.652 ms 23.583 ms 24.92 ms
4 100gigabitethernet3-1.core1.ams1.he.net (2001:470:0:2d4::1) 33.846 ms 27.638 ms 46.173 ms
5 amsix.ipv6.r3.am.hwng.net (2001:7f8:1::a501:2989:1) 35.093 ms 24.129 ms 24.874 ms
6 1-3.ipv6.r1.lo.hwng.net (2001:4de0:1000:36::2) 49.012 ms 29.42 ms 31.456 ms
7 ve10.ipv6.r2.lo.hwng.net (2001:4de0:1000:24::2) 30.437 ms 29.37 ms 38.959 ms
8 1-3.ipv6.r2.ny.hwng.net (2001:4de0:1000:3::2) 114.585 ms 123.325 ms 125.402 ms
9 6-4.ipv6.r1.ch.hwng.net (2001:4de0:1000:1f::1) 149.694 ms 156.423 ms 145.418 ms
10 2001:4de0:1000:28::2 (2001:4de0:1000:28::2) 151.803 ms 191.473 ms 306.954 ms
11 2001:4de0:3102:1::2 (2001:4de0:3102:1::2) 153.6 ms 139.593 ms 144.653 ms
12 2607:f878::147 (2607:f878::147) 154.53 ms 154.095 ms 151.546 ms
13 2607:f878::159 (2607:f878::159) 222.703 ms 243.347 ms 236.088 ms
14 2607:f878::189 (2607:f878::189) 224.662 ms 233.823 ms 223.314 ms
15 uslax02.sixxs.net (2607:f878:3:400::2) 223.214 ms 225.403 ms 223.935 ms
16 2607:f878:3:a::1 (2607:f878:3:a::1) 227.314 ms 228.768 ms 228.827 ms
17 uslax02.sixxs.net (2607:f878:3:400::2) 247.9 ms 229.162 ms 227.816 ms
18 2607:f878:3:a::1 (2607:f878:3:a::1) 235.783 ms 237.25 ms 231.613 ms
19 uslax02.sixxs.net (2607:f878:3:400::2) 229.201 ms 235.313 ms 223.869 ms
20 2607:f878:3:a::1 (2607:f878:3:a::1) 233.879 ms 225.207 ms 227.412 ms
21 uslax02.sixxs.net (2607:f878:3:400::2) 225.737 ms 246.298 ms 227.519 ms
22 2607:f878:3:a::1 (2607:f878:3:a::1) 247.911 ms 226.01 ms 232.841 ms
23 uslax02.sixxs.net (2607:f878:3:400::2) 228.091 ms 239.784 ms 242.612 ms
24 2607:f878:3:a::1 (2607:f878:3:a::1) 237.558 ms 245.194 ms 238.915 ms
25 uslax02.sixxs.net (2607:f878:3:400::2) 224.837 ms 227.194 ms 227.053 ms
26 2607:f878:3:a::1 (2607:f878:3:a::1) 234.604 ms 226.946 ms 228.085 ms
27 uslax02.sixxs.net (2607:f878:3:400::2) 226.556 ms 236.254 ms 224.412 ms
28 2607:f878:3:a::1 (2607:f878:3:a::1) 227.102 ms 231.11 ms 225.343 ms
29 uslax02.sixxs.net (2607:f878:3:400::2) 226.48 ms 226.904 ms 223.858 ms
30 2607:f878:3:a::1 (2607:f878:3:a::1) 229.549 ms 235.507 ms 227.353 ms
And ping6 from my home networks shows comparable results.
:~$ ping6 2607:f878:fe00:3c::2
PING 2607:f878:fe00:3c::2(2607:f878:fe00:3c::2) 56 data bytes
From 2607:f878:3:a::1 icmp_seq=1 Time exceeded: Hop limit
From 2607:f878:3:a::1 icmp_seq=2 Time exceeded: Hop limit
From 2607:f878:3:a::1 icmp_seq=3 Time exceeded: Hop limit
From 2607:f878:3:a::1 icmp_seq=4 Time exceeded: Hop limit
^C
My local (home) connection is either 2001:470:1f0b:212:885a:9ad1:1516:4bd3 or 2001:470:1f0b:212::1, that's the net part I control.
My sixxs tunnel part is 2607:f878:fe00:3c::2.
I decided that this was not a duplicate of the previous uslax02 loop issue from ~june since
* you mentioned it as resolved
* it just worked the last month
* there are different nodes involved
Kind regards,
Stephan.
|
Posting is only allowed when you are