Netflix on IPv6

  • Thread starter Thread starter philip
  • Start date Start date
  • Replies Replies 10
  • Views Views 1,463
Messages
717
Location
NA
ISP
BSNL FTTH
@varkey do u face any streaming issues on Netflix when on ipv6.I am on ipv6 and during evening hours I am not able to stream from netflix not even loading the pictures itself.
 
@philip Nope, works without any issues. Streams in what appears to be full HD always. Yesterday I think for a short time, it buffered twice, but otherwise no issues so far.
 
@philip Nope, works without any issues. Streams in what appears to be full HD always. Yesterday I think for a short time, it buffered twice, but otherwise no issues so far.
Can u please posts traceroutes to Netflix.com on ipv6.mine goes via airtel with a latency 406ms guess that's why the streaming issues are there
 
Can u please posts traceroutes to Netflix.com on ipv6.mine goes via airtel with a latency 406ms guess that's why the streaming issues are there

Tests to netflix.com may not be valid, cause that covers only the main website and associated things, the actual video streams come from elsewhere. I remember reading somewhere that the Netflix website and other things are served only from the US or EU.

Maybe try playing a video and check the diagnostic info and see from which endpoint the video gets served from.
 
So I played couple of videos just now and the CDN was mentioned as below for all. Control+alt+shift+D shows the diagnostic info. Looks like this endpoint is served only over IPv4.

Code:
Current CDN (a/v): c001.bom001.bsnl.isp.nflxvideo.net, Id: 60175 / c001.bom001.bsnl.isp.nflxvideo.net, Id: 60175

Code:
Pinging ipv4_1.lagg0.c001.bom001.bsnl.isp.nflxvideo.net [117.219.236.249] with 32 bytes of data:
Reply from 117.219.236.249: bytes=32 time=36ms TTL=61
Reply from 117.219.236.249: bytes=32 time=39ms TTL=61
Reply from 117.219.236.249: bytes=32 time=36ms TTL=61
Reply from 117.219.236.249: bytes=32 time=36ms TTL=61

Tried another video and it changed to

Code:
Current CDN (a/v): c002.del001.bsnl.isp.nflxvideo.net, Id: 58673 / c002.del001.bsnl.isp.nflxvideo.net, Id: 58673

Code:
Pinging ipv4_1.lagg0.c002.del001.bsnl.isp.nflxvideo.net [117.219.234.249] with 32 bytes of data:
Reply from 117.219.234.249: bytes=32 time=55ms TTL=60
Reply from 117.219.234.249: bytes=32 time=55ms TTL=60
Reply from 117.219.234.249: bytes=32 time=55ms TTL=60
Reply from 117.219.234.249: bytes=32 time=55ms TTL=60

@philip
 


@varkey it's over ipv4 right it will not have any issues ,but are u configured in dual stack mode then how come Netflix works for you on ipv4 mine automatically selects ipv6.
 
@philip So I tested a bit more by disabling IPv4, that means Netflix would be able to use only IPv6. It appears the IPv6 endpoint for the BSNL OCA (Open Connect Appliance) is misconfigured, the requests over IPv6 to BSNL OCA always fail. So when trying to play videos, it spins for a long time, and finally Netflix decides to use Netflix's own cache in Mumbai, and the video starts playing.

Code:
Current CDN (a/v): c011.bom001.ix.nflxvideo.net, Id: 49470 / c011.bom001.ix.nflxvideo.net, Id: 49470

The endpoint of the BSNL OCA it used is https://ipv6-c001-bom001-bsnl-isp.1.oca.nflxvideo.net/ , which appears to have a routing misconfig.

Code:
Pinging ipv6-c001-bom001-bsnl-isp.1.oca.nflxvideo.net [2001:4490:3ffc:800f::41] with 32 bytes of data:
Reply from 2001:4490:3ffc:800f::41: TTL expired in transit.
Reply from 2001:4490:3ffc:800f::41: TTL expired in transit.
Reply from 2001:4490:3ffc:800f::41: TTL expired in transit.
Reply from 2001:4490:3ffc:800f::41: TTL expired in transit.

Code:
Tracing route to ipv6-c001-bom001-bsnl-isp.1.oca.nflxvideo.net [2001:4490:3ffc:800f::41]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  2001:4490:4e4d:4e9::1
  2     1 ms     2 ms     1 ms  2001:4490:4e4c::1
  3     3 ms     3 ms     3 ms  2001:4490:3dfc::82
  4    15 ms    15 ms    16 ms  2001:4490:efff::1:5
  5    15 ms    16 ms    16 ms  2001:4490:efff::1:4
  6    16 ms    16 ms    14 ms  2001:4490:efff::1:5
  7    16 ms    16 ms    16 ms  2001:4490:efff::1:4
  8    15 ms    15 ms    15 ms  2001:4490:efff::1:5
  9    16 ms    16 ms    16 ms  2001:4490:efff::1:4
10    15 ms    55 ms    15 ms  2001:4490:efff::1:5

So unless you are using IPv6 only mode, you shouldn't see much of an issue, and even with IPv6 only, it would just take longer to start playing, but once it starts, should work fine.

@varkey it's over ipv4 right it will not have any issues ,but are u configured in dual stack mode then how come Netflix works for you on ipv4 mine automatically selects ipv6.

Netflix's client side code in this case manages all those (the hostnames used seem to imply that), I mean the endpoint used is automatically determined by Netflix. In my case, even in dual stack mode, it probably detected that requests to the IPv6 endpoint aren't really going through, so it switched to the IPv4 endpoint. If the Netflix client/app is working as intended, it should automatically fail over to the working endpoint. I tested these on a browser, it is possible an Android app works differently.
 

Back