[129567] in North American Network Operators' Group
Re: List of Teredo servers and teredo relays
daemon@ATHENA.MIT.EDU (Jared Mauch)
Sat Sep 11 12:28:29 2010
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <alpine.OSX.2.00.1009101256570.1117@cust11794.lava.net>
Date: Sat, 11 Sep 2010 12:28:04 -0400
To: Antonio Querubin <tony@lava.net>
Cc: NANOG <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
I would be careful actually using teredo, as some of them (eg: =
Microsoft) have swaths of native IPv6 networks that are unreachable. =20
I'm hoping they will correct some of the problems with it, but it makes =
IPv6 harder to use for some people as the Microsoft one does not appear =
to be well supported/connected. I'm not sure if there is an effort =
under way on Microsofts behalf to correct this, but I hope so.
- Jared
On Sep 10, 2010, at 7:11 PM, Antonio Querubin wrote:
> On Fri, 10 Sep 2010, Fernando Gont wrote:
>=20
>> Does any body maintain a list of Teredo servers and Teredo relays?
>=20
> A list of public Teredo servers might be useful. But a list of public =
relays - not so much.
>=20
> If you google around you'll eventually stumble across the following =
public servers:
>=20
> teredo.ipv6.microsoft.com
> teredo.remlab.net
> teredo2.remlab.net
> debian-miredo.progsoc.org
> teredo.ginzado.ne.jp
> teredo.iks-jena.de
>=20
> The first is the default for Windows. The second is the initial =
default for most Miredo installs. The fourth is supposedly the default =
for the Debian Miredo package.
>=20
> You can get an idea of where some public relays might be at:
>=20
> http://www.bgpmon.net/teredo.php
>=20
> But there may be a bunch of others not listed. The relay used varies =
on a per-connection basis. It'll generally be the closest relay to the =
non-teredo host.
>=20
> Antonio Querubin
> 808-545-5282 x3003
> e-mail/xmpp: tony@lava.net
