[129572] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: List of Teredo servers and teredo relays

daemon@ATHENA.MIT.EDU (Jeroen Massar)
Sat Sep 11 16:54:50 2010

Date: Sat, 11 Sep 2010 22:54:29 +0200
From: Jeroen Massar <jeroen@unfix.org>
To: Jeff Kell <jeff-kell@utc.edu>
In-Reply-To: <4C8BE509.1090904@utc.edu>
Cc: NANOG <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

On 2010-09-11 22:22, Jeff Kell wrote:
[..]
> What is currently "breaking" things is the preference of IPv6 over
> IPv4.  If you're running a default Win2K8 active directory, it's
> publishing all of it's goodies for login in IPv6 form complete with AAAA
> address records.  If your network isn't end-to-end IPv6 compliant, but
> some Win7 client across the hall (on another subnet) has found *any*
> IPv6 connectivity (6to4, Teredo, doesn't matter how good/bad/ugly/slow),
> it is going to try to communicate with the domain controller over that
> IPv6 connection.  I have seen this in action, and stacks of trouble
> tickets of slow / intermittent / no connectivity with the domain.

It would be nice that if you make these kind of statements that you
would have actually read up on things which are active already for a
long long time.

Please try google and read up on RFC 3484.

Indeed, Teredo is prioritized AFTER native IPv4.

Greets,
 Jeroen


home help back first fref pref prev next nref lref last post