[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Yahoo and IPv6
- Subject: Yahoo and IPv6
- From: tjc at ecs.soton.ac.uk (Tim Chown)
- Date: Wed, 1 Jun 2011 12:18:07 +0100
- In-reply-to: <C5346EBB3EF3AA4C984D4F0F6D21542739A36501ED@USFMAIL2.forest.usf.edu>
- References: <AQHMDhXyKg2S7/U2QUaQboRIZhbyWg==> <C9EDE811.A0C8%[email protected]> <[email protected]> <[email protected]> <C5346EBB3EF3AA4C984D4F0F6D21542739A36501ED@USFMAIL2.forest.usf.edu> <[email protected]>
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