1 |
My apologies for not reading your post carefully. |
2 |
|
3 |
I see an MTU of 1280 to www.python.org at my end - ipv6 tun device on my |
4 |
router is set to this, so I think it can deal with the 1500 MTU on my |
5 |
local machine's interface. Nice spotting :) |
6 |
|
7 |
|
8 |
Regards, |
9 |
|
10 |
Tom |
11 |
|
12 |
gummay ~ # tracepath6 www.python.org |
13 |
1?: [LOCALHOST] pmtu 1500 |
14 |
1: 2001:44b8:62:120::1 0.695ms |
15 |
1: 2001:44b8:62:120::1 0.630ms |
16 |
2: 2001:44b8:62:120::1 0.691ms pmtu 1280 |
17 |
*snip* |
18 |
24: dinsdale.python.org 460.627ms reached |
19 |
Resume: pmtu 1280 hops 24 back 51 |
20 |
|
21 |
|
22 |
|
23 |
|
24 |
Lindsay Haisley wrote: |
25 |
> On Sat, 2009-05-16 at 13:07 +1000, Tom Fifield wrote: |
26 |
>> I have encountered this problem before, however www.python.org works |
27 |
>> fine on ipv6 for me. Many cases where things fail is because DNS |
28 |
>> resolves the AAAA record, but the ISP/upstream providers don't have IPv6 |
29 |
>> connectivity to the site. |
30 |
> |
31 |
> I'm using a v6->v4 tunnel broker so my ISP is out the loop, what's more, |
32 |
> as I said, |
33 |
> |
34 |
>> www.python.org also |
35 |
>> resolves with an aaaa record (2001:888:2000:d::a2), and I can ping6 |
36 |
>> the server, so I know that routing is OK. |
37 |
> |
38 |
> It looks as if the problem may be related to MTUs. I did a bit of |
39 |
> jiggery-pokery with MTUs, setting the MTU for the IF on my desktop |
40 |
> system slightly lower than the MTU on the LAN IF of my router, and it |
41 |
> appears that the problem is solved for now, at least. |
42 |
> |
43 |
> I've seen network problems before with MTU issues, especially where UDP |
44 |
> packets are involved, as they may be with the tunnel broker. |
45 |
> |