General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Colin Dearborn <Colin.Dearborn@sjrb.ca>
To: "David P. Reed" <dpreed@deepplum.com>,
	Rich Brown <richb.hanover@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	"bloat@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [Cerowrt-devel]  OT: Netflix vs 6in4 from HE.net
Date: Tue, 24 Mar 2020 15:11:24 +0000	[thread overview]
Message-ID: <MWHPR04MB06718C00021A4561606ACD8895F10@MWHPR04MB0671.namprd04.prod.outlook.com> (raw)
In-Reply-To: <1584912664.72374374@apps.rackspace.com>

[-- Attachment #1: Type: text/plain, Size: 4849 bytes --]

HE IPv6 space has been tagged as a vpn type service by Netflix, since it has users all over the world, but it's space is all geolocated in the US. If HE had geolocated the blocks of each POP to the country the POP resided in, and put some rules around geolocation of using each POP (IE Canadian residents can only use Canadian POPs) this could have been avoided, but it also would have been a large amount of work on HE's side just to make geolocation accurate-ish.

Fortunately, my ISP got IPv6 working natively shortly after Netflix started blocking HE's space, so I didn't have to suffer for too long (but lost my US netflix.)

Content licensing is a very complex thing. While you might believe that your subscription equals the license, in reality the license is the agreement between Netflix and the content providers. Content providers put strict geolocation rules of where content can be played on Netflix, and Netflix can be sued by them if it appears that they're not doing enough to protect these rules. This is to protect the value of the content providers content, when they sell it to someone other than Netflix, or start their own streaming service.  For example, in Canada, we have a streaming service called Crave. There's a lot of content on there that would be available to Netflix in the States, so if Netflix didn't properly adhere to geolocation rules, Crave could legitimately either sue Netflix directly, or get the content provider to do it for them (again, depending on the licensing agreement).
This is why when you travel, you get the local Netflix content, not the content of the country where you pay the subscription.

Your option of using a cloud server may work. :)


This might turn out to be a problem for me - I have a "smart TV" that I watch Netflix on, and it appears to use IPv4. What specifically triggers Netflix to reject specific IPv6 clients? Is it the player's IPv6 address? Is all of he.net's address space blocked?

I've been planning to move more of my home networks to routed IPv6.

In principle, Netflix as a business shouldn't care - it's just doing its best efforts to protect its content's licensing requirements. So if I'm actually in the US, and my net claims correctly to be in US (by whatever trickery I use), neither Netflix nor I am violating any license from a legal point of view.

So all I need to do would be to get a legit US IPv6 address (I have one /64 on a public cloud server), and tunnel it to my house and give it to my TV. Not ideal, but until Netflix does its geofencing *correctly* according to the license, rather than according to IP address, I'd say it's a proper thing.



On Saturday, March 21, 2020 8:47pm, "Rich Brown" <richb.hanover@gmail.com> said:

>  I love knowing smart people.
>
> Yes, it does appear to be Netflix geo-fencing their services. Given that I only
> watch Netflix on one computer, I am taking Sebastian's advice and turning off IPv6
> DNS queries in Firefox.
>
> Thanks again for these responses.
>
> Rich
>
>> On Mar 21, 2020, at 6:14 PM, Sebastian Moeller <moeller0@gmx.de> wrote:
>>
>> Hi Rich,
>>
>> since it seems to be IPv6 related, why not use firefox for netflix and disable
>> IPv6 in firefox (see
>> https://support.mozilla.org/en-US/kb/firefox-cant-load-websites-other-browsers-can#w_ipv6)
>> maybe that works well enough?
>>
>> Best Regards
>>      Sebastian
>>
>>
>>
>>
>>> On Mar 21, 2020, at 21:20, Rich Brown <richb.hanover@gmail.com> wrote:
>>>
>>> to Bloat & CeroWrt folks: This is a little OT for either of these lists, but I
>>> figured there are plenty of experts here, and I would be delighted to get your
>>> thoughts.
>>>
>>> I just tried to view a Netflix movie and got a F7111-5059 error message. This
>>> prevented the video from playing. (As recently as a month or two ago, it worked
>>> fine.)
>>>
>>> Googling the error message gets to this page
>>> https://help.netflix.com/en/node/54085 that singles out use of an IPv6 Proxy
>>> Tunnel.
>>>
>>> Sure enough, I'm have a 6in4 tunnel through Hurricane Electric on WAN6. Stopping
>>> that WAN6 interface caused Netflix to work.
>>>
>>> What advice could you offer? (I could, of course, turn off WAN6 to watch movies.
>>> But that's a drag, and other family members couldn't do this.) Many thanks.
>>>
>>> Rich
>>> _______________________________________________
>>> Bloat mailing list
>>> Bloat@lists.bufferbloat.net
>>> https://lists.bufferbloat.net/listinfo/bloat
>>
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>


_______________________________________________
Bloat mailing list
Bloat@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/bloat

[-- Attachment #2: Type: text/html, Size: 7476 bytes --]

  reply	other threads:[~2020-03-24 15:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-21 20:20 [Bloat] " Rich Brown
2020-03-21 20:27 ` [Bloat] [Cerowrt-devel] " Dave Taht
2020-03-21 22:06 ` Michael Richardson
2020-03-21 22:14 ` [Bloat] " Sebastian Moeller
2020-03-21 22:41   ` [Bloat] [Cerowrt-devel] " Dave Taht
2020-03-22  0:47   ` [Bloat] " Rich Brown
2020-03-22 21:31     ` [Bloat] [Cerowrt-devel] " David P. Reed
2020-03-24 15:11       ` Colin Dearborn [this message]
2020-03-24 17:47         ` Dave Taht
2020-03-24 22:19           ` David P. Reed
     [not found]       ` <MWHPR04MB06718C00021A4561606ACD8895F10@MWHPR04MB0671.namprd04.prod.outloo k.com>
     [not found]         ` <MWHPR04MB06718C00021A4561606ACD8895F10@MWHPR04MB0671.namprd04.prod.outlook.c om>
2020-03-24 22:28           ` David P. Reed
2020-03-24 22:47             ` Mark Andrews
2020-03-26 20:29               ` Michael Richardson
2020-03-25  8:56             ` Toke Høiland-Jørgensen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=MWHPR04MB06718C00021A4561606ACD8895F10@MWHPR04MB0671.namprd04.prod.outlook.com \
    --to=colin.dearborn@sjrb.ca \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dpreed@deepplum.com \
    --cc=richb.hanover@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox