Great news for IPv6
otroan at employees.org
Tue Oct 26 12:03:18 CEST 2010
>> After some initial troubles (*), i now try vg.no and hd.no, and my
>> results are a bit unhappy -- none of them works well from a ipv6-only
>> host (i just drop v4 packets in my iptables OUTPUT chain).
>> They load, but very slowly. :)
>> Dual-stack works, and about 50% of the packets come over ipv4 and 50%
>> from ipv6 for the entire site first page load. (I think the only
>> viable migration goal for content providers must be to make content
>> compatible with ipv6-only hosts)
> Yep, but that's definitively step #2. There's content included from ad
> networks and such that are not dual-stack capable and not everything
> loaded from our rig is dual-stack capable at the moment either.
> For now we want to just try out dual-stacking the main hostnames and see
> if we can do so safely. If the verdict after the test day is that the
> broken users problem isn't really a big concern, hopefully we'll put
> dual-stack in production permanently and add the missing pieces so that
> we'll in the end be able to cater to IPv6-only end users. But first
> things first. :-)
> And so far, so good. We've yet to receive any real complains of
> connectivity loss. My contact in VG just called the whole test day an
if I show up in your statistics, then I am only demonstrating to one of my colleagues how badly things go when I turn on the 6to4 interface on my Mac. (41 appears to be blocked in the particular corporate network I'm using).
More information about the ipv6-ops