nanog mailing list archives
Re: google ipv6 routes via cogent
From: Alarig Le Lay <alarig () swordarmor fr>
Date: Thu, 2 Mar 2017 15:52:37 +0100
On sam. 25 févr. 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. Cogent is telling me that I can't route through cogent to get to google ipv6 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. Anyone know anything about this ? .and why it happened and when it will be resolved ? -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’t have this possibility, you can set up an IPv6-in-IPv4 tunnel to HE; the IPv4 traffic flows normally. -- alarig
Attachment:
signature.asc
Description:
Current thread:
- Re: google ipv6 routes via cogent, (continued)
- Re: google ipv6 routes via cogent Jared Mauch (Mar 02)
- Re: google ipv6 routes via cogent joel jaeggli (Mar 07)
- Re: google ipv6 routes via cogent Chuck Anderson (Mar 02)
- Re: google ipv6 routes via cogent Hunter Fuller (Mar 02)
- Message not available
- Message not available
- Re: google ipv6 routes via cogent Baldur Norddahl (Mar 04)
- Re: google ipv6 routes via cogent Dennis Bohn (Mar 02)
- Re: google ipv6 routes via cogent Theodore Baschak (Mar 02)
- Re: google ipv6 routes via cogent Christopher Morrow (Mar 02)
- Re: google ipv6 routes via cogent Marty Strong via NANOG (Mar 08)
- Re: google ipv6 routes via cogent Alarig Le Lay (Mar 08)