[193914] in North American Network Operators' Group
Re: google ipv6 routes via cogent
daemon@ATHENA.MIT.EDU (Alarig Le Lay)
Thu Mar 2 10:26:04 2017
X-Original-To: nanog@nanog.org
Date: Thu, 2 Mar 2017 15:52:37 +0100
From: Alarig Le Lay <alarig@swordarmor.fr>
To: nanog@nanog.org
In-Reply-To: <001801d28f7e$d063ac10$712b0430$@gvtc.com>
Errors-To: nanog-bounces@nanog.org
--t2zib6ispdntemwg
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On sam. 25 f=C3=A9vr. 09:49:56 2017, Aaron wrote:
> Hi, I'm new to the nanog list, hope this isn't out of scope for what is
> usually discussed here.
>=20
> =20
>=20
> Cogent is telling me that I can't route through cogent to get to google i=
pv6
> routes (particularly the well known dns addresses 2001:4860:4860::88xx)
> because google decided not to advertise those route to one of their mutual
> peers.
>=20
> =20
>=20
> Anyone know anything about this ? .and why it happened and when it will =
be
> resolved ?
>=20
> =20
>=20
> -Aaron
Hi,
Cogent is not able to receive traffic from Google since February 2016,
the case is the same with HE since 2010.
So, as a quick workaround, you have to connect your network to another
IPv6 transit operator for these destinations.
I you don=E2=80=99t have this possibility, you can set up an IPv6-in-IPv4 t=
unnel
to HE; the IPv4 traffic flows normally.
--=20
alarig
--t2zib6ispdntemwg
Content-Type: application/pgp-signature; name="signature.asc"
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEE+2yGwT0H0n57WkRbrzhKwWsgK4gFAli4MbEACgkQrzhKwWsg
K4gVzAgAhea3iJGHl1WzEwOJ0qd0Ik24AYOB0DAKsubIkpLaG5Nfn8x5S4+1nGMO
dFYH6Z13qSPzucfAZaMmmY+j84zcI0YuV/Pfwy2bKrDgg/1Q6mwMrEXM8YCqTxzH
ifxUlaGDLibma+h+btzRQ6y356Enhwz/4winX18PX8gnlOSkcPaNJ09FRWeMdsMD
5ZkKGRBZdMRbd+1dyLWGidZ9hnstBhfwZvGysmw9/BR5wYaxvkmN8j7asQENXGU2
vPI0bUgqR7oq0UwUMp1Pf91LNOoP7dCOezmdT4/vmCRoZ+O/HihkFyxgJcezbUY2
/udIZczBHD937nqx3wVOgWZ7SuLsmA==
=th4t
-----END PGP SIGNATURE-----
--t2zib6ispdntemwg--
