[96987] in North American Network Operators' Group
Re: Testing IPv6 support on the client's machine (Was: NANOG 40 agenda posted
daemon@ATHENA.MIT.EDU (Nathan Ward)
Wed May 30 06:38:55 2007
In-Reply-To: <20070530094614.GA9807@nic.fr>
From: Nathan Ward <nanog@daork.net>
Date: Wed, 30 May 2007 22:38:05 +1200
To: Nanog <nanog@nanog.org>
Errors-To: owner-nanog@merit.edu
On 30/05/2007, at 9:46 PM, Stephane Bortzmeyer wrote:
> On Wed, May 30, 2007 at 10:55:04AM +1200,
> Nathan Ward <nanog@daork.net> wrote
> a message of 56 lines which said:
>
>> Use Javascript, or flash, or some other fancy thing to do a GET for
>> two files on two different servers as the page loads:
>> a) http://ip6test.<domain>/file
>> b) http://ip4test.<domain>/file
>>
>> And then compare the hit-rate for the two.
>
> Very good idea.
> But you should also log the TCP RTT for the two connections because a
> common failure is the fact that IPv4 goes straight to the server while
> IPv6 goes through a tunnel in Thailand or Brazil.
Yep, I plan to do that.
Also the reason that a connection failed (timeout or reject/
unreachable).
I suppose that a purpose built server could track things like half
opened connections (ie. SYNACK probably dropped), open connections
over which a large-ish request doesn't come (ie. MTU problems), and
so on.
The implementation problem I find now is that XMLHTTPRequest
apparently doesn't let you talk to other domains for security
reasons. I'm going to investigate using nasty iframe hacks, and
Flash. Maybe Java, but that sounds a bit heavy. If anyone has
experience with this sort of stuff and can lend some expertise, I'd
be grateful. Probably offlist would be best for now.
--
Nathan Ward
