|
Ticket ID: SIXXS #7680622 Ticket Status: Resolved PoP: deham01 - Easynet (Hamburg)
No/poor routing between hosts in Dublin and ~Hamburg
![[ie]](/s/countries/ie.gif) Shadow Hawkins on Saturday, 25 August 2012 13:53:41
Summary: I have 2 hosts both of which can reach ipv6.google.com, but they can't reach each other. One is in Dublin using the Heanet PoP (iedub01), the other is in Germany, using deham02.
Details:
I'm not reporting the AICCU part, because both host have access to the IPv6 network; the problem seems to be about routing.
Host 1, "quince": 2001:770:18d:0:21e:ecff:fe8b:d0be
Host 2, "quinoa": 2001:6f8:1c00:3ef::2
Problem from quince, I can access e.g. ipv6.google.com, but not quinoa:
maciej@quince:~$ ping6 ipv6.google.com
PING ipv6.google.com(dy-in-x63.1e100.net) 56 data bytes
64 bytes from dy-in-x63.1e100.net: icmp_seq=1 ttl=56 time=28.6 ms
64 bytes from dy-in-x63.1e100.net: icmp_seq=2 ttl=56 time=22.1 ms
64 bytes from dy-in-x63.1e100.net: icmp_seq=3 ttl=56 time=22.0 ms
^C
--- ipv6.google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 22.016/24.278/28.699/3.131 ms
maciej@quince:~$ traceroute6
traceroute6 traceroute6.db traceroute6.iputils
maciej@quince:~$ ping6 2001:6f8:1c00:3ef::2
PING 2001:6f8:1c00:3ef::2(2001:6f8:1c00:3ef::2) 56 data bytes
^C
--- 2001:6f8:1c00:3ef::2 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3024ms
maciej@quince:~$ traceroute6 2001:6f8:1c00:3ef::2
traceroute to 2001:6f8:1c00:3ef::2 (2001:6f8:1c00:3ef::2) from 2001:770:18d:0:64c4:dffb:c340:cc48, 30 hops max, 24 byte packets
1 openwrt.home.blizinski.pl (2001:770:18d::1) 0.577 ms 0.586 ms 0.558 ms
2 gw-270.dub-01.ie.sixxs.net (2001:770:100:10d::1) 20.782 ms 20.807 ms 20.692 ms
3 numbers.heanet.ie (2001:770:18:8::6) 20.614 ms 20.639 ms 21.147 ms
4 blanch-sr1-vlan8.services.hea.net (2001:770:18:8::1) 20.732 ms 20.593 ms 21.134 ms
5 te0-8-0-1-cr2-cwt.hea.net (2001:770:400:60::1) 28.05 ms 35.669 ms 23.696 ms
6 xe-2-1-0.dub20.ip6.tinet.net (2001:668:0:3::c000:71) 45.322 ms 21.51 ms 21.722 ms
7 xe-8-1-0.lon10.ip6.tinet.net (2001:668:0:2::1:1652) 35.314 ms 35.89 ms 35.765 ms
8 te0-3-0-4.gr10.telon.uk.easynet.net (2001:668:0:3::4000:972) 33.846 ms 33.976 ms 58.39 ms
9 2001:6f8:1:0:87:86:77:31 (2001:6f8:1:0:87:86:77:31) 38.617 ms 192.302 ms 130.091 ms
10 2001:6f8:1:0:87:86:77:46 (2001:6f8:1:0:87:86:77:46) 38.825 ms 39.164 ms 80.743 ms
11 * * *
12 * * *
13 * * *
14 * te3-1-4005.br40.kgham.de.easynet.net (::ffff:212.224.5.6) 58.749 ms 58.066 ms
15 2001:6f8:891:1::c2e9:c724 (2001:6f8:891:1::c2e9:c724) 58.69 ms 58.136 ms 58.043 ms
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 *^C
On the other host:
maciej@quinoa:~$ ping6 ipv6.google.com
PING ipv6.google.com(muc03s02-in-x12.1e100.net) 56 data bytes
64 bytes from muc03s02-in-x12.1e100.net: icmp_seq=1 ttl=52 time=35.9 ms
64 bytes from muc03s02-in-x12.1e100.net: icmp_seq=2 ttl=52 time=38.4 ms
64 bytes from muc03s02-in-x12.1e100.net: icmp_seq=3 ttl=52 time=36.4 ms
^C
--- ipv6.google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 35.985/36.958/38.401/1.052 ms
maciej@quinoa:~$ ping6 2001:770:18d:0:21e:ecff:fe8b:d0be
PING 2001:770:18d:0:21e:ecff:fe8b:d0be(2001:770:18d:0:21e:ecff:fe8b:d0be) 56 data bytes
64 bytes from 2001:770:18d:0:21e:ecff:fe8b:d0be: icmp_seq=4 ttl=48 time=79.3 ms
64 bytes from 2001:770:18d:0:21e:ecff:fe8b:d0be: icmp_seq=5 ttl=48 time=78.4 ms
From 2001:6f8:1:0:87:86:77:71 icmp_seq=9 Destination unreachable: No route
From 2001:6f8:1:0:87:86:77:71 icmp_seq=10 Destination unreachable: No route
From 2001:6f8:1:0:87:86:77:71 icmp_seq=16 Destination unreachable: No route
From 2001:6f8:1:0:87:86:77:71 icmp_seq=17 Destination unreachable: No route
^C
--- 2001:770:18d:0:21e:ecff:fe8b:d0be ping statistics ---
17 packets transmitted, 2 received, +4 errors, 88% packet loss, time 16097ms
rtt min/avg/max/mdev = 78.467/78.924/79.382/0.536 ms
maciej@quinoa:~$ traceroute6 2001:770:18d:0:21e:ecff:fe8b:d0be
traceroute to 2001:770:18d:0:21e:ecff:fe8b:d0be (2001:770:18d:0:21e:ecff:fe8b:d0be) from 2001:6f8:1c00:3ef::2, 30 hops max, 24 byte packets
1 gw-1008.ham-02.de.sixxs.net (2001:6f8:1c00:3ef::1) 20.306 ms 20.219 ms 19.763 ms
2 2001:6f8:891:1::c2e9:c721 (2001:6f8:891:1::c2e9:c721) 19.964 ms 19.947 ms 20.36 ms
3 2001:6f8:891:1::c2e9:c725 (2001:6f8:891:1::c2e9:c725) 21.024 ms 20.442 ms 20.018 ms
4 2001:6f8:1:0:87:86:71:248 (2001:6f8:1:0:87:86:71:248) 146.601 ms 21.023 ms 20.637 ms
5 2001:6f8:1:0:86:87:77:81 (2001:6f8:1:0:86:87:77:81) 20.962 ms 20.879 ms 20.531 ms
6 * * *
7 2001:6f8:1:0:87:86:77:62 (2001:6f8:1:0:87:86:77:62) 31.438 ms * *
8 * 2001:6f8:1:0:87:86:77:71 (2001:6f8:1:0:87:86:77:71) 50.629 ms 56.004 ms
9 2001:6f8:1:0:87:86:77:15 (2001:6f8:1:0:87:86:77:15) 38.954 ms 38.817 ms 38.896 ms
10 2001:6f8:1:0:87:86:77:47 (2001:6f8:1:0:87:86:77:47) 39.548 ms 39.895 ms 39.677 ms
11 2001:6f8:1:0:87:86:77:30 (2001:6f8:1:0:87:86:77:30) 48.834 ms 46.589 ms 46.047 ms
12 2001:7f8:4::d1c:1 (2001:7f8:4::d1c:1) 45.556 ms * *
13 * * *
14 * * 2001:6f8:1:0:87:86:77:71 (2001:6f8:1:0:87:86:77:71) 31.287 ms !N
15 * * *
16 * * *
17 * 2001:6f8:1:0:87:86:77:71 (2001:6f8:1:0:87:86:77:71) 36.723 ms !N 34.444 ms !N
Looks like I can't do anything about it myself, so I'm filing a ticket. Please let me know if more diagnostic information is necessary!
Maciej
State change: confirmed
The state of this ticket has been changed to confirmed
No/poor routing between hosts in Dublin and ~Hamburg
Update:
The problem is being caused by two distinct bugs in Cisco GSR and Cisco IOS-XR. A TAC case is open at Cisco who are further investigating and troubleshooting the issue.
No routing to 2001:4830::/32 from 2001:6f8::/32
![[de]](/s/countries/de.gif) Shadow Hawkins on Saturday, 15 September 2012 22:53:19
Hello,
there seem to be a problem routing from 2001:6f8::/32 to 2001:4830::/32:
kristov@peacock ~ $ traceroute v6.testmyipv6.com
traceroute to v6.testmyipv6.com (2001:4830:2502:8002::ac10:a), 30 hops max, 80 byte packets
1 garm.schulz.life24h.net (2001:6f8:13da:1::1) 0.203 ms 0.161 ms 0.158 ms
2 gw-1362.ham-01.de.sixxs.net (2001:6f8:900:551::1) 67.472 ms 75.456 ms 91.503 ms
3 2001:6f8:862:1::c2e9:c729 (2001:6f8:862:1::c2e9:c729) 91.510 ms 99.313 ms 103.278 ms
4 2001:6f8:862:1::c2e9:c72c (2001:6f8:862:1::c2e9:c72c) 115.295 ms 123.406 ms 131.223 ms
5 2001:6f8:1:0:87:86:69:214 (2001:6f8:1:0:87:86:69:214) 139.076 ms * *
6 2001:6f8:1:0:87:86:77:83 (2001:6f8:1:0:87:86:77:83) 163.139 ms * *
7 * * *
8 * * *
9 * * *
10 * * *
11 2001:6f8:1:0:87:86:77:62 (2001:6f8:1:0:87:86:77:62) 79.649 ms !N * *
kristov@peacock ~ $ traceroute -6 ftp.gnu.org
traceroute to ftp.gnu.org (2001:4830:134:3::b), 30 hops max, 80 byte packets
1 garm.schulz.life24h.net (2001:6f8:13da:1::1) 0.223 ms 0.359 ms 0.391 ms
2 gw-1362.ham-01.de.sixxs.net (2001:6f8:900:551::1) 65.766 ms 73.585 ms 81.698 ms
3 2001:6f8:862:1::c2e9:c729 (2001:6f8:862:1::c2e9:c729) 89.508 ms 97.576 ms 105.435 ms
4 2001:6f8:862:1::c2e9:c72c (2001:6f8:862:1::c2e9:c72c) 117.398 ms 121.384 ms 133.327 ms
5 2001:6f8:1:0:87:86:69:214 (2001:6f8:1:0:87:86:69:214) 141.195 ms * *
6 2001:6f8:1:0:87:86:77:83 (2001:6f8:1:0:87:86:77:83) 165.274 ms * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * 2001:6f8:1:0:87:86:77:62 (2001:6f8:1:0:87:86:77:62) 78.800 ms !N *
There are also routing problems to other prefixes (2001:41d0::/32, for example). Please advise if I should provide the corresponding traceroutes in this ticket or if I should open a new ticket for it.
Regards,
Christoph Schulz
No routing to 2001:4830::/32 from 2001:6f8::/32
As this ticket shows we are aware of this issue quite well.
No routing to 2001:4830::/32 from 2001:6f8::/32
Shadow Hawkins on Friday, 28 September 2012 14:37:35
Are you sure this is resolved now? I see no improvement.
Are v6.testmyipv6.com or ftp.gnu.org actually reachable for anyone using this POP from any of the subnets in 2001:6f8::/32 (Routing from the tunnel endpoint itself seems fine)?
No routing to 2001:4830::/32 from 2001:6f8::/32
Instead of posing questions, please provide traceroutes, those are much more valuable than statements.
No routing to 2001:4830::/32 from 2001:6f8::/32
Shadow Hawkins on Friday, 28 September 2012 15:20:45
For the two example hosts:
traceroute to v6.testmyipv6.com (2001:4830:2502:8002::ac10:a), 30 hops max, 40 byte packets using UDP
1 router.mueller (2001:6f8:10a4:cafe::1) 0.144 ms 0.121 ms 0.119 ms
2 gw-2259.ham-01.de.sixxs.net (2001:6f8:900:8d2::1) 27.377 ms 27.717 ms 28.131 ms
3 2001:6f8:862:1::c2e9:c729 (2001:6f8:862:1::c2e9:c729) 28.787 ms 29.216 ms 29.612 ms
4 2001:6f8:862:1::c2e9:c72c (2001:6f8:862:1::c2e9:c72c) 30.520 ms 30.405 ms 31.796 ms
5 2001:6f8:1:0:87:86:69:214 (2001:6f8:1:0:87:86:69:214) 32.205 ms * *
6 * * *
7 * * *
8 * * *
traceroute to ftp.gnu.org (2001:4830:134:3::b), 30 hops max, 40 byte packets using UDP
1 router.mueller (2001:6f8:10a4:cafe::1) 0.154 ms 0.123 ms 0.116 ms
2 gw-2259.ham-01.de.sixxs.net (2001:6f8:900:8d2::1) 27.640 ms 28.019 ms 28.386 ms
3 2001:6f8:862:1::c2e9:c729 (2001:6f8:862:1::c2e9:c729) 29.153 ms 29.718 ms 29.215 ms
4 2001:6f8:862:1::c2e9:c72c (2001:6f8:862:1::c2e9:c72c) 30.551 ms 30.669 ms 31.330 ms
5 2001:6f8:1:0:87:86:69:214 (2001:6f8:1:0:87:86:69:214) 32.477 ms * *
6 * * *
7 * * *
8 * * *
A working example:
traceroute to www.google.com (2a00:1450:4008:c01::69), 30 hops max, 40 byte packets using UDP
1 router.mueller (2001:6f8:10a4:cafe::1) 0.147 ms 0.123 ms 0.117 ms
2 gw-2259.ham-01.de.sixxs.net (2001:6f8:900:8d2::1) 27.847 ms 28.780 ms 29.141 ms
3 2001:6f8:862:1::c2e9:c729 (2001:6f8:862:1::c2e9:c729) 29.534 ms 29.686 ms 29.916 ms
4 2001:6f8:862:1::c2e9:c72c (2001:6f8:862:1::c2e9:c72c) 31.227 ms 31.388 ms 31.585 ms
5 2001:6f8:1:0:87:86:69:214 (2001:6f8:1:0:87:86:69:214) 32.700 ms * *
6 2001:6f8:1:0:87:86:77:83 (2001:6f8:1:0:87:86:77:83) 33.651 ms * *
7 2001:6f8:1:0:87:86:77:62 (2001:6f8:1:0:87:86:77:62) 47.250 ms 47.845 ms 47.007 ms
8 de-cix10.net.google.com (2001:7f8::3b41:0:1) 39.881 ms 40.242 ms 75.239 ms
9 2001:4860::1:0:11 (2001:4860::1:0:11) 39.988 ms 41.375 ms 2001:4860::1:0:10 (2001:4860::1:0:10) 42.563 ms
10 2001:4860::8:0:3015 (2001:4860::8:0:3015) 41.610 ms 41.367 ms 56.343 ms
11 2001:4860::8:0:2e9b (2001:4860::8:0:2e9b) 48.351 ms 47.721 ms 2001:4860::8:0:2e9c (2001:4860::8:0:2e9c) 48.189 ms
12 2001:4860::8:0:3097 (2001:4860::8:0:3097) 93.911 ms 56.377 ms 2001:4860::8:0:3098 (2001:4860::8:0:3098) 57.515 ms
13 2001:4860::2:0:6e0 (2001:4860::2:0:6e0) 58.172 ms 58.083 ms 2001:4860::2:0:612 (2001:4860::2:0:612) 57.205 ms
14 * * *
15 2a00:1450:4008:c01::69 (2a00:1450:4008:c01::69) 58.831 ms 58.750 ms 59.653 ms
No routing to 2001:4830::/32 from 2001:6f8::/32
Fortunately we have a view inside OCCAID, thus
traceroute to 2001:6f8:10a4:cafe::1 (2001:6f8:10a4:cafe::1), 30 hops max, 80 byte packets
1 dcr01-ve402.bstn01.occaid.net (2001:4830:e1:b::1) 0.524 ms 0.516 ms 0.511 ms
2 bbr01-g0-1.bstn01.occaid.net (2001:4830:ff:b100::1) 0.741 ms 0.738 ms 0.731 ms
3 bbr01-g1-0.mnch01.occaid.net (2001:4830:ff:b103::2) 68.426 ms 68.433 ms 68.429 ms
4 bbr01-p2-1.slgh01.occaid.net (2001:4830:fe:2003::1) 76.354 ms 76.666 ms 76.675 ms
5 ibr01-g1-1.slgh01.occaid.net (2001:4830:fe:2004::2) 76.748 ms 77.268 ms 77.265 ms
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
That seems to not get there:
traceroute to 2001:6f8:900:8d2::1 (2001:6f8:900:8d2::1), 30 hops max, 80 byte packets
1 dcr01-ve402.bstn01.occaid.net (2001:4830:e1:b::1) 0.456 ms 0.446 ms 0.439 ms
2 bbr01-g0-1.bstn01.occaid.net (2001:4830:ff:b100::1) 0.625 ms 0.625 ms 0.708 ms
3 bbr01-g1-0.mnch01.occaid.net (2001:4830:ff:b103::2) 68.451 ms 68.457 ms 68.453 ms
4 bbr01-p2-1.slgh01.occaid.net (2001:4830:fe:2003::1) 76.761 ms 76.767 ms 77.045 ms
5 ibr01-g1-1.slgh01.occaid.net (2001:4830:fe:2004::2) 77.244 ms 77.244 ms 77.240 ms
6 pc3.gr10.telon.uk.easynet.net (2001:7f8:4::11ed:1) 81.549 ms 81.656 ms 81.941 ms
7 2001:6f8:1:0:87:86:77:31 (2001:6f8:1:0:87:86:77:31) 87.311 ms 87.211 ms 87.376 ms
8 2001:6f8:1:0:87:86:77:60 (2001:6f8:1:0:87:86:77:60) 88.756 ms 89.376 ms 89.373 ms
9 2001:6f8:1:0:87:86:77:165 (2001:6f8:1:0:87:86:77:165) 99.226 ms 96.415 ms 96.744 ms
10 * * 2001:6f8:1:0:87:86:77:63 (2001:6f8:1:0:87:86:77:63) 94.869 ms
11 2001:6f8:1:0:87:86:69:223 (2001:6f8:1:0:87:86:69:223) 94.944 ms 96.123 ms 95.877 ms
12 * * *
13 * * *
14 2001:6f8:862:1::c2e9:c72c (2001:6f8:862:1::c2e9:c72c) 96.681 ms 95.795 ms 96.394 ms
15 2001:6f8:862:1::c2e9:c729 (2001:6f8:862:1::c2e9:c729) 95.910 ms 96.015 ms 95.703 ms
16 gw-2259.ham-01.de.sixxs.net (2001:6f8:900:8d2::1) 95.062 ms 94.480 ms 95.297 ms
and that seems to work just fine, which is rather to very odd. The only real difference is that the first comes out of a /40 for the PoP,
I can reach the testmyipv6.com site quite fine from deham01 btw:
traceroute6 2001:4830:2502:8002::ac10:a
traceroute to 2001:4830:2502:8002::ac10:a (2001:4830:2502:8002::ac10:a), 30 hops max, 80 byte packets
1 2001:6f8:862:1::c2e9:c72c (2001:6f8:862:1::c2e9:c72c) 0.889 ms 1.356 ms 1.350 ms
2 2001:6f8:1:0:87:86:69:214 (2001:6f8:1:0:87:86:69:214) 1.341 ms * *
3 2001:6f8:1:0:87:86:77:166 (2001:6f8:1:0:87:86:77:166) 13.301 ms 13.305 ms 13.298 ms
4 2001:6f8:1:0:87:86:77:61 (2001:6f8:1:0:87:86:77:61) 15.019 ms 15.021 ms 15.017 ms
5 ams20.ip6.tinet.net (2001:668:0:3::6000:411) 24.911 ms * 10.902 ms
6 xe-4-0-0.lon21.ip6.tinet.net (2001:668:0:2::1:1fc1) 17.344 ms xe-11-0-0.lon21.ip6.tinet.net (2001:668:0:2::1:29a1) 18.373 ms xe-4-0-0.lon21.ip6.tinet.net (2001:668:0:2::1:1fc1) 17.298 ms
7 ibr02-ve26.lndn01.occaid.net (2001:7f8:4:1::7577:2) 19.316 ms 19.334 ms 18.838 ms
8 bbr01-g1-0.slgh01.occaid.net (2001:4830:fe:2001::1) 19.095 ms 19.092 ms 19.975 ms
9 bbr01-p2-4.nwrk01.occaid.net (2001:4830:fe:2002::2) 92.607 ms 92.576 ms 93.279 ms
10 bbr01-g1-0.asbn01.occaid.net (2001:4830:ff:f150::2) 99.132 ms 99.087 ms 98.982 ms
11 bbr01-g1-0.atln01.occaid.net (2001:4830:ff:e250::2) 113.353 ms 112.997 ms 113.091 ms
12 bbr01-p1-0.dlls01.occaid.net (2001:4830:ff:f255::1) 137.108 ms 136.622 ms 136.492 ms
13 2001:4830:e4:17::2 (2001:4830:e4:17::2) 184.151 ms !X 188.389 ms !X 182.880 ms !X
And there tinet shows up in the middle, which is odd. Seems some asymmetric routing is causing random issues, I'll notify involved parties if they can figure it out, but it looks quite random too as at one point it works at another it does not.
State change: resolved
The state of this ticket has been changed to resolved
No/poor routing between hosts in Dublin and ~Hamburg
Shadow Hawkins on Monday, 24 September 2012 13:20:06
I thought my routing problem relies on this ticket, but this has already been marked as solved, but I still recognize routing problems:
Both hosts are connected to the IPv6 internet and can f.i. google.de:
Site 1: (SixXS deham1) 2001:6f8:1317::2
cyn :: ~ ping6 -c2 www.google.de
PING6(56=40+8+8 bytes) 2001:6f8:1317::2 --> 2a00:1450:4008:c01::5e
16 bytes from 2a00:1450:4008:c01::5e, icmp_seq=0 hlim=49 time=80.143 ms
16 bytes from 2a00:1450:4008:c01::5e, icmp_seq=1 hlim=49 time=78.284 ms
--- www.google.de ping6 statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 78.284/79.214/80.143/0.929 ms
Site 2: (Local IPv6 Internet Access Provider) 2a02:238:f002:1:1d63:718f:bdf1:b6f7
imac-ms :: ~ ping6 -c2 www.google.de
PING6(56=40+8+8 bytes) 2a02:238:f002:1:1d63:718f:bdf1:b6f7 --> 2a00:1450:4008:c01::5e
16 bytes from 2a00:1450:4008:c01::5e, icmp_seq=0 hlim=54 time=7.201 ms
16 bytes from 2a00:1450:4008:c01::5e, icmp_seq=1 hlim=54 time=7.175 ms
--- www.google.de ping6 statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 7.175/7.188/7.201/0.013 ms
Because pinging each other won't work, so here's the traceroute from both side, wich losts somewhere on the internet:
Site 1 --> Site 2:
cyn :: ~ traceroute6 2a02:238:f002:1:1d63:718f:bdf1:b6f7
traceroute6 to 2a02:238:f002:1:1d63:718f:bdf1:b6f7 (2a02:238:f002:1:1d63:718f:bdf1:b6f7) from 2001:6f8:1317::2, 64 hops max, 12 byte packets
1 2001:6f8:1317:0:c225:6ff:fe43:7ffd 4.193 ms 1.397 ms 1.348 ms
2 gw-3052.ham-01.de.sixxs.net 63.298 ms 53.727 ms 53.746 ms
3 2001:6f8:862:1::c2e9:c729 54.237 ms 53.730 ms 56.440 ms
4 2001:6f8:862:1::c2e9:c72c 56.716 ms 54.423 ms 53.397 ms
5 2001:6f8:1:0:87:86:69:214 55.253 ms 56.399 ms 58.543 ms
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
Site 2 --> Site 1:
imac-ms :: ~ traceroute6 2001:6f8:1317::2
traceroute6 to 2001:6f8:1317::2 (2001:6f8:1317::2) from 2a02:238:f002:1:1d63:718f:bdf1:b6f7, 64 hops max, 12 byte packets
1 eth0.br1.rz1.connectline.net 0.234 ms 0.256 ms 0.218 ms
2 2a02:238:2:f002::1 1.349 ms 1.697 ms 1.087 ms
3 xe-7-2-2.edge5.frankfurt1.level3.net 14.634 ms 14.726 ms 14.872 ms
4 vl-80.edge3.frankfurt1.level3.net 34.247 ms
vl-70.edge3.frankfurt1.level3.net 14.760 ms
vl-80.edge3.frankfurt1.level3.net 26.587 ms
5 vl-4060.edge4.paris1.level3.net 23.560 ms 23.647 ms 23.932 ms
6 vl-4061.edge4.london1.level3.net 30.619 ms 30.617 ms 30.472 ms
7 vl-4080.edge3.london1.level3.net 30.407 ms
vl-4080.edge4.london1.level3.net 30.380 ms 30.893 ms
8 vl-4084.sar1.london1.level3.net 30.926 ms 30.820 ms 30.766 ms
9 * * *
10 * * *
11 * * *
12 * * *
Traceroutes from both sides get stuck at this point.
No/poor routing between hosts in Dublin and ~Hamburg
Strange that that goes over Level3 (and then also Franfurt -> Paris -> London) as according to GRH Easynet does direct peering with them.
I suggest you contact your provider and show them the traceroutes, seems they have something fishy in their configuration.
|
![[ch]](/s/countries/ch.gif)
on Saturday, 25 August 2012 22:14:19
Posting is only allowed when you are