People looking for ways to make IPv4 hosts talk to IPv6 hosts should know about pros and cons of specific technologies that try to enable that. The end-host would have to have a public IPv4 address or be behind a 6to4-capable device (typically a CPE) for this to work. This results in a poor user experience, which is the reason some large content providers are hesitant to dual-stack their content.Ģ) In a near future with IPv6-only content, 6to4 might be the only connectivity option for IPv4-only end-hosts that were 'left behind' and don't have native IPv6 connectivity yet. When the 6to4-connection fails it has to time-out before hosts try the IPv4 connection. There are 2 reasons why 6to4 is interesting to look at:ġ) A minority of operating systems default to preferring 6to4 (and other auto-tunneled IPv6) over native IPv4 when an end-host connects to a dual-stacked host. A similar failure rate was independently observed by Geoff Huston. More specifically we saw a TCP-SYN, but not the rest of a TCP connection. We pointed out in the article 6to4 - How Bad is it Really? that roughly 15% 6to4 connections we measured fail. In this article we show our attempts to find out why these connections fail. In a previous article we measured that a large percentage of 6to4 connections fail.
0 kommentar(er)
