| 1 |
I have encountered this problem before, however www.python.org works |
| 2 |
fine on ipv6 for me. Many cases where things fail is because DNS |
| 3 |
resolves the AAAA record, but the ISP/upstream providers don't have IPv6 |
| 4 |
connectivity to the site. |
| 5 |
|
| 6 |
Can you post a traceroute -6 www.python.org ? |
| 7 |
|
| 8 |
Regards, |
| 9 |
|
| 10 |
Tom |
| 11 |
|
| 12 |
|
| 13 |
gummay@gummay ~ $ traceroute -6 www.python.org |
| 14 |
traceroute to www.python.org (2001:888:2000:d::a2), 30 hops max, 80 byte |
| 15 |
packets |
| 16 |
1 2001:44b8:62:120::1 (2001:44b8:62:120::1) 0.545 ms 0.534 ms 0.665 ms |
| 17 |
2 2001:44b8:61::38 (2001:44b8:61::38) 41.691 ms 44.181 ms 45.319 ms |
| 18 |
3 vl67.cor1.adl6.internode.on.net (2001:44b8:8060:8000::1) 46.238 ms |
| 19 |
48.241 ms 49.140 ms |
| 20 |
4 gi0-0.bdr1.adl6.internode.on.net (2001:44b8:8060:14::1) 50.099 ms * * |
| 21 |
5 pos3-1.cor1.per1.internode.on.net (2001:44b8:8060:17::1) 85.518 ms |
| 22 |
86.254 ms 87.498 ms |
| 23 |
6 pos1-0.bdr1.sin1.internode.on.net (2001:44b8:f0c0:1::1) 136.581 ms |
| 24 |
134.181 ms 136.971 ms |
| 25 |
7 pos2-0.bdr1.hkg1.internode.on.net (2001:44b8:f0c0:2::1) 173.361 ms |
| 26 |
146.103 ms 146.240 ms |
| 27 |
8 2001:7fa:0:1::ca28:a116 (2001:7fa:0:1::ca28:a116) 150.657 ms |
| 28 |
152.182 ms 153.212 ms |
| 29 |
9 so-3-0-0-bcr1.tok.cw.net (2001:5000:0:12b::1) 229.245 ms 228.674 |
| 30 |
ms 230.268 ms |
| 31 |
10 so-6-0-0-ecr1.sfo.cw.net (2001:5000:0:c2::1) 295.898 ms 297.402 ms |
| 32 |
299.065 ms |
| 33 |
11 so-4-2-0-dcr1.nyk.cw.net (2001:5000:0:2f::1) 362.469 ms 364.008 ms |
| 34 |
338.077 ms |
| 35 |
12 xe-0-0-0.xcr1.nyk.cw.net (2001:5000:0:112::1) 319.072 ms 318.671 |
| 36 |
ms xe-7-2-0.xcr1.nyk.cw.net (2001:5000:0:14b::2) 350.301 ms |
| 37 |
13 xe-7-0-0.xcr1.lsw.cw.net (2001:5000:0:149::2) 426.384 ms 426.860 |
| 38 |
ms 425.766 ms |
| 39 |
14 xe-11-2-0.xcr1.amd.cw.net (2001:5000:0:130::2) 436.763 ms |
| 40 |
xe-11-1-0.xcr1.amd.cw.net (2001:5000:0:12f::2) 438.084 ms |
| 41 |
xe-11-2-0.xcr1.amd.cw.net (2001:5000:0:130::2) 435.584 ms |
| 42 |
15 xe-0-1-0.xcr1.amd.cw.net (2001:5000:0:11d::1) 427.150 ms |
| 43 |
xe-0-2-0.xcr1.amd.cw.net (2001:5000:0:11e::1) 426.011 ms 403.879 ms |
| 44 |
16 ge-6-0-0.dcr1.fra.cw.net (2001:5000:0:10d::2) 475.073 ms |
| 45 |
ge-2-0-0.dcr1.fra.cw.net (2001:5000:0:10e::2) 468.561 ms 437.742 ms |
| 46 |
17 so-3-0-0-zcr2.muc.cw.net (2001:5000:0:cd::2) 443.292 ms 444.370 ms |
| 47 |
so-5-0-0-zcr2.muc.cw.net (2001:5000:0:63::2) 443.197 ms |
| 48 |
18 ge-1-0-0-200-gar1.muc.cw.net (2001:5000:0:4::5) 444.125 ms 442.912 |
| 49 |
ms ge-0-0-0-100-gar1.muc.cw.net (2001:5000:0:3::5) 444.174 ms |
| 50 |
19 mchn-s2-rou-1030.DE.eurorings.net (2001:5001:100:15::2) 424.237 ms |
| 51 |
424.956 ms 425.794 ms |
| 52 |
20 asd2-rou-1030.eurorings.net (2001:680::134:222:86:48) 448.829 ms |
| 53 |
448.465 ms 448.624 ms |
| 54 |
21 2001:680:0:800f::32 (2001:680:0:800f::32) 454.279 ms 453.855 ms |
| 55 |
449.562 ms |
| 56 |
22 te5-4.swcolo1.3d12.xs4all.net (2001:888:0:114::2) 424.238 ms |
| 57 |
434.206 ms 430.882 ms |
| 58 |
23 vlan5.swcolo2.3d12.xs4all.net (2001:888:0:3101::2) 567.259 ms |
| 59 |
563.464 ms 551.640 ms |
| 60 |
24 dinsdale.python.org (2001:888:2000:d::a2) 461.020 ms 460.998 ms |
| 61 |
501.074 ms |
| 62 |
|
| 63 |
|
| 64 |
Lindsay Haisley wrote: |
| 65 |
> I'm having some problems reaching *.python.org with web browers here, |
| 66 |
> and the problem appears to be related to ipv6 issues. My desktop system |
| 67 |
> is connected to a Linux router which has an assigned /64 v6 block from |
| 68 |
> freenet6. Firefox defaults to using ipv6 if there's an AAAA record for |
| 69 |
> an address. This isn't a problem in most cases. |
| 70 |
> |
| 71 |
> If I access most v6 enabled web servers, e.g. www.kame.net or |
| 72 |
> testmyipv6.com with firefox, no problem. I get back a page indicating |
| 73 |
> that I"ve made a v6 connection to the web server. www.python.org also |
| 74 |
> resolves with an aaaa record (2001:888:2000:d::a2), and I can ping6 the |
| 75 |
> server, so I know that routing is OK. I can't, however, get a response |
| 76 |
> from the server with a firefox, which just blocks trying to retrieve a |
| 77 |
> page. |
| 78 |
> |
| 79 |
> If I disable the v6 address on the net IF on my desktop, firefox uses a |
| 80 |
> v4 connection immediately and the connection is OK, same for lynx. But |
| 81 |
> if the IF has a global v6 address both lynx and firefox block. |
| 82 |
> |
| 83 |
> My immediate guess was that www.python.org is running a v6 enabled box |
| 84 |
> and has v6 routing to it, but that the web server there isn't v6 |
| 85 |
> enabled. This still may be the case, however I _can_ use (v6-enabled) |
| 86 |
> lynx to get to the box from my router, and either something very strange |
| 87 |
> is going on, or the fallback to v4 algorithm for lynx on the router is |
| 88 |
> different from that on my desktop system. If I emerge lynx with |
| 89 |
> USE="-ipv6" on my desktop system I have no trouble getting to |
| 90 |
> www.python.org from that system with lynx. |
| 91 |
> |
Archives