[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Did IPv6 between HE and Google ever get resolved?

On Sat, Mar 30, 2019 at 4:37 AM Matthew Petach <mpetach at netflight.com> wrote:
>
>
>
> On Sat, Mar 30, 2019 at 4:33 AM Matthew Petach <mpetach at netflight.com> wrote:
>>
>>
>>
>> On Thu, Mar 28, 2019 at 12:40 PM David Hubbard <dhubbard at dino.hostasaurus.com> wrote:
>>>
>>> Hey all, Iâ??ve been having bad luck searching around, but did IPv6 transit between HE and google ever get resolved?  Ironically, I can now get to them cheaply from a location we currently have equipment that has been Cogent-only, so if it fixes the IPv6 issue Iâ??d like to make the move.  Anyone peer with HE in general and want to share their experience offlist?  With the price, if theyâ??re a good option, Iâ??d consider rolling them in to other locations where we have redundancy already, so the v6 isnâ??t as big a deal there.
>>>
>>>
>>>
>>> Thanks
>>>
>>>
>>
>>
>> I wasn't aware of any issues between HE.net and Google;
>> are you sure you don't mean HE.net and Cogent?

thread subject still says 'google and he', I don't think there's ever
been problems between google/he for v6.
I think there are some issues from cogent - > he over v6 :(

Looking at a sample AS6939 customer link I see no:
  ".* 174$"
  ".* 174 .*$"

routes in the bgp stream :(

Looking at a AS174 customer link session I see no:
  ".* 6939$"
  ".* 6939 .*"

routes in the bgp stream :(

-chris

>>
>> Matt
>>
>
> Ah.  Sorry, the changed subject line didn't thread in with this,
> so this showed up as an unreplied singleton in my inbox.
>
> Apologies for the duplicated response; at least this won't
> be a lonely singleton in anyone else's inbox now.  ^_^;
>
> Matt
>