[85545] in North American Network Operators' Group

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

Re: Bad IPv6 connectivity or why not to announce more specifics

daemon@ATHENA.MIT.EDU (Jeroen Massar)
Thu Oct 13 15:48:00 2005

From: Jeroen Massar <jeroen@unfix.org>
To: Valdis.Kletnieks@vt.edu
Cc: nanog@nanog.org
In-Reply-To: <200510131938.j9DJccEv025891@turing-police.cc.vt.edu>
Date: Thu, 13 Oct 2005 21:44:23 +0200
Errors-To: owner-nanog@merit.edu



--=-p7eYuFdcythHmGhbEEmf
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Thu, 2005-10-13 at 15:38 -0400, Valdis.Kletnieks@vt.edu wrote:
> On Thu, 13 Oct 2005 21:06:30 +0200, Jeroen Massar said:
>=20
> > Well Valdis, that bad route also has to do with your side of the
> > equation, you might want to check who you are actually using as transit=
s
> > and if the routes they are providing to you are sane enough.
>=20
> Well, if somebody at stupi.se wants to do a traceroute6 back at us, I'll
> be glad to see what the reverse path looks like...  but last I heard
> traceroute and traceroute6 showed the *forward* path of packets..

That is correct, try tracepath, this shows at least the assymetry.
You can also peek at GRH to see a probable AS path back. ASN's still
tell a lot in IPv6.

Next month I'll finalize the 'symmetry' tool which allows one to do the
AS path checkup between two places automatically.

> > 2001:468::/32 is in the routing table, getting accepted by most ISP's.
> > This one has a reasonable route
>=20
> The real problem (at least for the forward direction from here) is that t=
he
> outbound packets get into the Abilene network, and the best path from the=
re to
> 2001:440:1880 is a 3ffe: tunnel to japan and then another 3ffe: tunnel ba=
ck to New
> York.

Kick Abilene to not be so silly and get some real transits. Then again
Abiline is educational and those networks seem to have very nice (read:
overcomplex) routing policies...

Greets,
 Jeroen


--=-p7eYuFdcythHmGhbEEmf
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iD8DBQBDTrkXKaooUjM+fCMRAvjeAKCEu/9omZm1xKEZEDHqfO61N0MuLQCgtrvn
YeS2ahzgL8ucGyYysTC9QZk=
=ud3E
-----END PGP SIGNATURE-----

--=-p7eYuFdcythHmGhbEEmf--


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