On 31 May 2011, at 22:31, Voll, Toivo wrote: > > Netalyzr (http://n3.netalyzr.icsi.berkeley.edu/analysis) finds no issues with > my IPv6 status, but alerts me to the fact (since confirmed by switching to > IE) that Google Chrome defaults to IPv4 rather than IPv6, and consequently a > lot of the testing tools claim that my IPv6 is broken.
I'm a little confused there - the current Chrome prefers IPv6, and also now includes code to allow fast failover to IPv4 in the event IPv6 connectivity is down/slow (300ms headstart). I had some issues with Netalyzer detecting my dual-stack status, which the chaps there are helping with. Tim
