|
Unable to connect to AICCU from Windows (teredo)
![[us]](/s/countries/us.gif) Shadow Hawkins on Tuesday, 03 May 2011 01:46:19
I am having connection problems to my IPv6 subnetwork from Windows 7. My tunnel's POP is usphx01.sixxs.net. The Windows 7 system uses the default teredo setup.
Some connections work. I can request a blank webpage from a webserver on my IPv6 subnet from the Win 7 system. Requesting a larger webpage times out.
I can ping the IPv6 webserver from the Win 7 system. Pinging with a larger packet size (>1212) times out. I get the same ping results to my POP (usphx01.sixxs.net). I can ping other POPs with packet sizes >1212. (usanc01.sixxs.net works.)
I've tried two different Windows 7 systems, both on the same network.
Unable to connect to AICCU from Windows (teredo)
I am having connection problems to my IPv6 subnetwork from Windows 7. My tunnel's POP is usphx01.sixxs.net. The Windows 7 system uses the default teredo setup.
Thus if I understand this correctly, you have a computer ONE which is a Windows 7 machine and uses Teredo. You have a computer TWO in an IPv6 subnet which is behind usphx01.sixxs.net?
Some connections work. I can request a blank webpage from a webserver on my IPv6 subnet from the Win 7 system. Requesting a larger webpage times out.
That clearly indicates an MTU issue. Do verify that you local network is using an MTU of 1500 on the Ethernet part and that the tunnel is properly configure to 1280 (unless you changed it to something else, and hopefully correct in the webinterface)
What you need to do have is output of tracepath, otherwise you end up doing a traceroute and pinging every hop along the way manually with different packet sizes.
As you are on Windows, try out MTURoute which should give you some insight.
As you are involving Teredo though, the anycast nature of that system will make it interesting to debug this.
Unable to connect to AICCU from Windows (teredo)
Shadow Hawkins on Tuesday, 03 May 2011 19:49:24
Your description of my setup is correct.
Here is the routing table from my IPv6 router. The sixxs tunnel MTU is 1280, and the Ethernet MTUs are 1500.
$ ip -6 route
2001:1938:81:11d::/64 dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 0
2001:1938:269::/64 dev eth1 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 0
2001:1938:269:1::/64 dev wlan0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 0
fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 0
fe80::/64 dev eth1 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 0
fe80::/64 dev wlan0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 0
fe80::/64 dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 0
default via 2001:1938:81:11d::1 dev sixxs metric 1024 mtu 1280 advmss 1220 hoplimit 0
I ran mturoute on the Windows system against my POP.
mturoute usphx01.sixxs.net
* ICMP Fragmentation is not permitted. *
* Speed optimization is enabled. *
* Maximum payload is 10000 bytes. *
+ ICMP payload of 1472 bytes succeeded.
- ICMP payload of 1473 bytes is too big.
Path MTU: 1500 bytes.
I didn't see any way to use mturoute over IPv6.
I'll run the traceroute/ping tests next. Should I be testing IPv6 or IPv4 when I do this?
Unable to connect to AICCU from Windows (teredo)
Here is the routing table from my IPv6 router. The sixxs tunnel MTU is 1280, and the Ethernet MTUs are 1500.
Even with AYIYA you could increase the MTU of the tunnel quite a bit. Is there a specific reason for using AYIYA, proto-41 tunnels give better performance, and if you had a proto-41 tunnel your MTU would be 1480 which is effectively the best one can get except for native IPv6.
I'll run the traceroute/ping tests next. Should I be testing IPv6 or IPv4 when I do this?
IPv6, as your tunnel is working, the question becomes where the packets are being dropped, I can only assume at some remote site, and in that case you would have to contact that remote location for it to be resolved.
Of course you should also make sure that your network allows ICMP, especially Packet Too Big. pMTU issues are what are causing your issues.
If you want to solve this issue easier, I would suggest changing the Teredo host to a proper tunnel, makes it much easier to debug.
Unable to connect to AICCU from Windows (teredo)
Shadow Hawkins on Tuesday, 03 May 2011 23:00:16Even with AYIYA you could increase the MTU of the tunnel quite a bit. Is there a specific reason for using AYIYA, proto-41 tunnels give better performance, and if you had a proto-41 tunnel your MTU would be 1480 which is effectively the best one can get except for native IPv6.
I will give proto-41 heartbeat a try on my tunnel.
If you want to solve this issue easier, I would suggest changing the Teredo host to a proper tunnel, makes it much easier to debug.
I setup AICCU on the Windows system, and connections no longer time out.
|
![[ch]](/s/countries/ch.gif)
on Tuesday, 03 May 2011 11:00:39
Posting is only allowed when you are