I don't believe Sony can spell IPv6. What AS is the destination host in? 



----- 
Mike Hammett 
Intelligent Computing Solutions 

Midwest Internet Exchange 

The Brothers WISP 




----- Original Message -----

From: "Nate Burke" <n...@blastcomm.com> 
To: "AnimalFarm Microwave Users Group" <af@af.afmug.com> 
Sent: Thursday, October 11, 2018 9:06:29 AM 
Subject: Re: [AFMUG] Tracking Down DualStack Problems 

Torching the interface to see the stream source Address, then running a 
traceroute to that address, I have 0 packet loss and 10ms of latency 
from my house to the source IPv6 address. But it's still buffering like 
crazy. I'm not sure how you would troubleshoot this, or offer a 
solution to a customer, other than turning IP6 off... It appears to be 
a problem with the source Stream. I've been using VUE for quite a while 
on IPv6, and these problems just started this week. 

I was doing some troubleshooting, trying other streaming apps on the 
Amazon box, and I came back to Vue, this time it chose the IPv4 stream 
on it's own. 

On 10/10/2018 12:12 PM, Adam Moffett wrote: 
> Could it be that consumer routers see less ipV6 traffic, so undetected 
> bugs are more likely in the V6 stack on those routers? 
> If it's a goofy router that won't stop you from getting the call, but 
> it means you might have an answer. 
> 
> On 10/10/2018 12:43 PM, Nate Burke wrote: 
>> I have my Own DNS servers, without a full time packet sniffer, how 
>> would you ever figure out what actual DNS lookup it did to find the 
>> host? Middle of the day, even a less optimal data center shouldn't 
>> be at capacity. The Wife said she was watching VUE on a different TV 
>> in the house Yesterday afternoon, and it was buffering as well. So It 
>> could be Vue and Their IP6 capacity. Still a pain to track down. 
>> 
>> On 10/10/2018 11:33 AM, Adam Moffett wrote: 
>>> I'm going to be pulling the trigger on dual stack pretty soon. 
>>> You're scaring me a little. 
>>> 
>>> I would think the major CDN's are dual stack by this point. I'm not 
>>> sure if it matters, but whose DNS were you using? It could be that 
>>> the v6 DNS took you to a less optimal data center than the v4 DNS. 
>>> 
>>> 
>>> On 10/10/2018 12:23 PM, Nate Burke wrote: 
>>>> I haven't rolled IPV6 out to customers yet, but I am running 
>>>> Dualstack at my house. Native IP6 with my own ARIN Space. I've 
>>>> noticed that streaming traffic, youtube, netflix, Playstation VUE, 
>>>> Facebook, seem to prefer the IP6 connection. This morning I was 
>>>> having all kinds of Buffering problems watching Playstation VUE, 
>>>> (Via Amazon FireTV box) I turned off IP6, it automatically switched 
>>>> to the IP4 stream, and is now flawless. Those of you running full 
>>>> Dualstack deployments, do you have to do IP4/6 troubleshooting? 
>>>> How do you manage troubleshooting with the customer to determine if 
>>>> the traffic stream is a 4 or 6, and track it down? From the 
>>>> customer perspective, "the internet sucks" because things are 
>>>> buffering. 
>>>> 
>>> 
>>> 
>> 
>> 
> 
> 


-- 
AF mailing list 
AF@af.afmug.com 
http://af.afmug.com/mailman/listinfo/af_af.afmug.com 

-- 
AF mailing list
AF@af.afmug.com
http://af.afmug.com/mailman/listinfo/af_af.afmug.com

Reply via email to