|
Routing issue with one particular host
![[us]](/s/countries/us.gif) Shadow Hawkins on Tuesday, 05 July 2011 18:53:49
Hello,
This may just be a sanity check, as there may be nothing I can do to fix the issue, but any input would be much appreciated:
I have a tunnel on my router running OpenWRT, as well as a subnet on my LAN. The router advertises routing information to the LAN using radvd.
Most of my testing is done from the LAN from an Ubuntu 11.04 host.
I can connect to many IPV6 sites (ipv6.google.com et al.) just fine, but packages.debian.org still devils me. An AAAA lookup gives me 2 addresses:
;; ANSWER SECTION:
packages.debian.org. 300 IN AAAA 2001:648:2ffc:deb:214:22ff:feb2:17e8
packages.debian.org. 300 IN AAAA 2001:8d8:81:1520::1
Trying to trace to the first address works fine:
~# tracepath6 2001:648:2ffc:deb:214:22ff:feb2:17e8
1?: [LOCALHOST] 0.039ms pmtu 1280
1: gw-389.bos-01.us.sixxs.net 25.051ms
1: gw-389.bos-01.us.sixxs.net 24.810ms
2: bbr01-ve402.bstn01.occaid.net 23.755ms
3: bbr01-p1-0.nwrk01.occaid.net 31.770ms
4: bbr01-g1-0.asbn01.occaid.net 39.740ms
5: gc-equinix-v6.gblx.net 39.122ms
6: 2001:450:2002:71::2 144.168ms asymm 11
7: as1.rt1.ath2.gr.geant2.net 194.003ms asymm 12
8: grnet-gw.rt1.ath2.gr.geant2.net 213.280ms asymm 13
9: holter.debian.org 192.568ms reached
Resume: pmtu 1280 hops 9 back 52
No such luck with the second one:
~# tracepath6 2001:8d8:81:1520::1
1?: [LOCALHOST] 0.058ms pmtu 1280
1: gw-389.bos-01.us.sixxs.net 23.785ms
1: gw-389.bos-01.us.sixxs.net 22.917ms
2: bbr01-ve402.bstn01.occaid.net 28.400ms
3: bbr01-p1-0.nwrk01.occaid.net 32.366ms
4: bbr01-p2-0.lndn01.occaid.net 110.249ms
5: no reply
...
29: no reply
30: no reply
31: no reply
Too many hops: pmtu 1280
Resume: pmtu 1280
Consequently, connections to that site (using Firefox 4) often time out.
It looks to me like the issue is the second IPv6 address being announced by their DNS server, but not actually being reachable, so really not something that I could fix in my setup. Please correct me if I am wrong on that one.
If I am correct, is there anything I can do, like for example configure my network to not use IPv6 when trying to reach *@debian.org?
Thank you very much,
--Juergen
Routing issue with one particular host
Shadow Hawkins on Tuesday, 05 July 2011 20:01:13
I can reach both sites from here:
thumper/~ tracepath6 2001:648:2ffc:deb:214:22ff:feb2:17e8
1?: [LOCALHOST] 0.032ms pmtu 1500
1: cl-90.chi-03.us.sixxs.net 0.730ms
1: cl-90.chi-03.us.sixxs.net 2.573ms
2: cl-90.chi-03.us.sixxs.net 0.693ms pmtu 1280
2: gw-90.chi-03.us.sixxs.net 75.466ms
3: 2620:0:6b0:a::1 71.508ms
4: ge-4-35.car2.Chicago2.Level3.net 277.886ms asymm 11
5: no reply
6: vl-4067.car1.Chicago1.Level3.net 73.965ms asymm 9
7: vl-51.car3.Chicago1.Level3.net 111.942ms asymm 8
8: 2001:1900:4:3::1fe 78.623ms
9: bpt-b4-v6.telia.net 207.477ms asymm 8
10: 2001:798:cc:2c01:1b01::1 223.412ms asymm 11
11: 2001:798:cc:2c01:1901::2 232.611ms asymm 12
12: grnet-gw.rt1.ath2.gr.geant2.net 240.721ms asymm 13
13: holter.debian.org 232.832ms reached
Resume: pmtu 1280 hops 13 back 52
thumper/~ tracepath6 2001:8d8:81:1520::1
1?: [LOCALHOST] 0.030ms pmtu 1500
1: cl-90.chi-03.us.sixxs.net 0.767ms
1: cl-90.chi-03.us.sixxs.net 0.703ms
2: cl-90.chi-03.us.sixxs.net 0.699ms pmtu 1280
2: gw-90.chi-03.us.sixxs.net 79.649ms
3: 2620:0:6b0:a::1 73.748ms
4: tge6-3.fr3.ord4.ipv6.llnw.net 78.691ms
5: ve8.fr3.ord.ipv6.llnw.net 77.165ms
6: 10gigabitethernet4-1.core1.chi1.he.net 80.590ms
7: eqx-v6.bb-a.cr.chi.us.oneandone.net 75.707ms asymm 4
8: te-2-4.bb-d.ws.mkc.us.oneandone.net 85.577ms asymm 5
9: te-1-1.bb-c.slr.lxa.us.oneandone.net 118.073ms asymm 11
10: et-1.gw-tunnel6to4-a.slr.lxa.us.oneandone.net 121.240ms asymm 12
11: powell.debian.org 207.347ms reached
Resume: pmtu 1280 hops 11 back 52
You might learn more by using traceroute and fiddling with the options.
Routing issue with one particular host
Shadow Hawkins on Tuesday, 05 July 2011 22:13:32
OK, weird. I tried a traceroute to the final hoip in your successful traceroute to powell.debian.org, and that failed, too:
~# traceroute 2607:f1c0:0:2::51
traceroute to 2607:f1c0:0:2::51 (2607:f1c0:0:2::51), 30 hops max, 80 byte packet
s
1 gw-389.bos-01.us.sixxs.net (2001:4830:1100:184::1) 24.437 ms 25.419 ms 25
.389 ms
2 bbr01-ve402.bstn01.occaid.net (2001:4830:e1:b::1) 29.905 ms 29.961 ms 30.
188 ms
3 bbr01-p1-0.nwrk01.occaid.net (2001:4830:ff:15c4::1) 35.621 ms 36.620 ms 3
6.882 ms
4 bbr01-g1-0.asbn01.occaid.net (2001:4830:ff:f150::2) 43.477 ms 43.723 ms 4
3.761 ms
5 level3-px.occaid.net (2001:4830:11:1::2) 44.379 ms 44.470 ms 44.671 ms
6 vl-4084.car1.Washington1.Level3.net (2001:1900:4:1::24e) 47.120 ms 234.969 ms 235.116 ms
7 * * *
8 * * *
9 2001:1900:4:1::a9 (2001:1900:4:1::a9) 55.143 ms 52.750 ms 53.610 ms
10 * * vl-4061.car2.Dallas1.Level3.net (2001:1900:4:1::95) 82.893 ms
11 vl-4082.car1.Dallas1.Level3.net (2001:1900:4:1::89) 83.042 ms 78.845 ms 72.655 ms
12 vl-4049.car1.KansasCity1.Level3.net (2001:1900:4:1::37a) 81.343 ms 83.175 ms 81.954 ms
13 * * *
...
30 * * *
I guess my problems run a bit deeper than just being unable to reach this one host.
Could there actually be something in my configuration that would cause a traceroute to get stuck after hitting a number of routers successfully?
Thank you,
--Juergen
Routing issue with one particular host
![[cz]](/s/countries/cz.gif) Carmen Sandiego on Wednesday, 06 July 2011 00:37:25
For me the same issue reaching latest address - so it's not only your problem :)
# traceroute 2607:f1c0:0:2::51
traceroute to 2607:f1c0:0:2::51 (2607:f1c0:0:2::51), 30 hops max, 80 byte packets
1 gw-233.prg-01.cz.sixxs.net (2a01:8c00:ff00:e8::1) 10.424 ms 13.803 ms 15.099 ms
2 2001:1ab0:7e1e:d150:8a43:e1ff:fed8:f57f (2001:1ab0:7e1e:d150:8a43:e1ff:fed8:f57f) 18.288 ms 16.009 ms 14.325 ms
3 2001:1ab0:b0f4::1 (2001:1ab0:b0f4::1) 16.466 ms 19.098 ms 19.197 ms
4 2001:1ab0:b0f4:2::1 (2001:1ab0:b0f4:2::1) 18.354 ms 17.820 ms 16.881 ms
5 2001:978:2:4::11 (2001:978:2:4::11) 14.956 ms 15.054 ms 20.222 ms
6 * * *
...
12 * * *
13 vl-60.car1.Washington1.Level3.net (2001:1900:15:5::3) 131.665 ms vl-80.car1.Washington1.Level3.net (2001:1900:15:7::3) 128.912 ms vl-60.car1.Washington1.Level3.net (2001:1900:15:5::3) 134.041 ms
14 * * *
15 2001:1900:4:1::3b6 (2001:1900:4:1::3b6) 141.512 ms 140.683 ms 139.915 ms
16 2001:1900:4:1::a9 (2001:1900:4:1::a9) 145.179 ms 145.225 ms 132.248 ms
17 * * *
18 vl-4082.car1.Dallas1.Level3.net (2001:1900:4:1::89) 156.854 ms 158.822 ms 162.873 ms
19 vl-4049.car1.KansasCity1.Level3.net (2001:1900:4:1::37a) 175.890 ms 166.670 ms 167.371 ms
20 * * *
...
30 * * *
However previous address is reachable
# traceroute 2001:8d8:81:1520::1
traceroute to 2001:8d8:81:1520::1 (2001:8d8:81:1520::1), 30 hops max, 80 byte packets
1 gw-233.prg-01.cz.sixxs.net (2a01:8c00:ff00:e8::1) 10.859 ms 12.227 ms 14.714 ms
2 2001:1ab0:7e1e:d150:8a43:e1ff:fed8:f57f (2001:1ab0:7e1e:d150:8a43:e1ff:fed8:f57f) 16.698 ms 15.528 ms 16.767 ms
3 2001:1ab0:b0f4::1 (2001:1ab0:b0f4::1) 16.539 ms 13.730 ms 13.601 ms
4 2001:1528:1:ae00::1 (2001:1528:1:ae00::1) 14.555 ms 18.516 ms 17.673 ms
5 2001:4de8:b0ba:ca5a:1::1 (2001:4de8:b0ba:ca5a:1::1) 23.978 ms 22.870 ms 26.870 ms
6 20gigabitethernet4-3.core1.fra1.he.net (2001:7f8::1b1b:0:1) 25.723 ms 28.570 ms 27.207 ms
7 10gigabitethernet5-3.core1.lon1.he.net (2001:470:0:1d2::1) 41.194 ms 39.187 ms 39.383 ms
8 10gigabitethernet7-4.core1.nyc4.he.net (2001:470:0:3e::1) 113.453 ms 112.149 ms 111.269 ms
9 10gigabitethernet8-3.core1.chi1.he.net (2001:470:0:1c6::2) 119.988 ms 125.698 ms 128.185 ms
10 eqx-v6.bb-a.cr.chi.us.oneandone.net (2001:504:0:4::8560:1) 143.429 ms 141.383 ms 139.725 ms
11 te-2-4.bb-d.ws.mkc.us.oneandone.net (2607:f1c0:0:2::39) 142.714 ms 141.022 ms 131.790 ms
12 te-1-1.bb-c.slr.lxa.us.oneandone.net (2607:f1c0:0:2::a) 135.656 ms 138.289 ms 136.934 ms
13 et-1.gw-tunnel6to4-a.slr.lxa.us.oneandone.net (2607:f1c0:0:2::51) 142.820 ms 141.742 ms 140.169 ms
14 powell.debian.org (2001:8d8:81:1520::1) 153.219 ms 149.749 ms 154.535 ms
Routing issue with one particular host
Shadow Hawkins on Wednesday, 06 July 2011 02:11:26
I can't trace 2607:f1c0:0:2::51 either. I can ping it, though. It reverses to
et-1.gw-tunnel6to4-a.slr.lxa.us.oneandone.net with IPv4 74.208.6.109.
Routing issue with one particular host
Shadow Hawkins on Wednesday, 06 July 2011 02:39:52
I can't trace it from here but it traces from my PoP using the distributed traceroute under Misc/Tools. Strange.
|
Posting is only allowed when you are