[135722] in North American Network Operators' Group
Re: test-ipv6.com
daemon@ATHENA.MIT.EDU (Kevin Stange)
Fri Jan 28 03:40:52 2011
Date: Fri, 28 Jan 2011 02:39:54 -0600
From: Kevin Stange <kevin@steadfast.net>
To: nanog@nanog.org
In-Reply-To: <20110128001632.CF4E1938AFA@drugs.dv.isc.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig2F67AC4F02C807351725FBC5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
On 01/27/2011 06:16 PM, Mark Andrews wrote:
> In message <alpine.BSF.2.00.1101271448000.15852@goat.gigo.com>, Jason F=
esler wr
> ites:
>> Several people have suggested I (re)post information about test-ipv6.c=
om=20
>> here.
>>
>> http://test-ipv6.com ..
>> tests ipv4 and ipv6 by dns name
>> tests dual stack (will the client break on World IPv6 Day?)
>> tests ipv6 by IP literal (teredo can pass this)
>> gives advice to end user about current status and (depending on
>> circumstances) more information
>> "broken" users (can't connect to dual stack) are solicited for info=
>> Caution: does depend on javascript.
>>
>> http://test-ipv6.com/simple_test.html
>> Eyeball test only for user, with instructions; no javascript requir=
ed.
>>
>> Please direct any comments, flames, etc directly to me instead of the =
>> list. I've added enough noise already :-)
>=20
> Note you can have totally broken IPv6 connectivity and still be
> fine on World IPv6 day. You just need applications with good
> multi-homing support. No web site can check this for you.
However, by coincidence, this week I happened to be playing with the
site and it revealed to me a particular use case of my DNS resolvers
that was broken and gave me a chance to fix it.
I don't think there's any harm in some baseline sanity checking.
--=20
Kevin Stange
Chief Technology Officer
Steadfast Networks
http://steadfast.net
Phone: 312-602-2689 x203
Fax: 312-602-2688
Cell: 312-320-5867
--------------enig2F67AC4F02C807351725FBC5
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk1CgOQACgkQkd/BoeKjg0h/YwCgigKCnoAWNcj6QpSiwLVLuqSG
0zIAoIOOqrjjixgEfZaSTXhQsz9uq1NA
=tTTa
-----END PGP SIGNATURE-----
--------------enig2F67AC4F02C807351725FBC5--
