[Cerowrt-devel] OT: Netflix vs 6in4 from HE.net

[Cerowrt-devel] OT: Netflix vs 6in4 from HE.net

[Rich Brown]

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

Re: [Cerowrt-devel] OT: Netflix vs 6in4 from HE.net

[Dave Taht]

On Sat, Mar 21, 2020 at 1:20 PM 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.

This happened to me over a year back.

http://www.peachyphotos.com/blog/posts/netflix-and-hurricane-electrics-ipv6-service/

Briefly I swtched to just blackholing netflix's ipv6 range, then I
tunnled my linode connection, then I switched to just universally
using comcast native ipv6 (with source specific routing and static
assignments on the key routers).

I was VERY reluctant to do this as comcast reserves the right to
change your ipv6 addressing at any point, and it changes if you change
routers, but having to manually reconfigure  a dozen routers and
several servers if it ever changes seemed easiest. I dread
renumbering...

The vast majority of my traffic in the evenings is ipv6 now.


> Rich
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel



-- 
Make Music, Not War

Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-435-0729

Re: [Cerowrt-devel] OT: Netflix vs 6in4 from HE.net

[Michael Richardson]

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


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.

I suspect it's part of a geo-fencing system.

    > 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.

If your only IPv6 is via the tunnel, then I'd blacklist the netflix device
from getting IPv6.  (Maybe that fails because it's your general purpose laptop)

Maybe you would be able to determine what IPv6 destinations are netflix, and
blacklist that, but given that it usually uses a stack of EC2, etc. servers,
that might be too big a gun.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

Re: [Cerowrt-devel] [Bloat] OT: Netflix vs 6in4 from HE.net

[Sebastian Moeller]

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

Re: [Cerowrt-devel] [Bloat] OT: Netflix vs 6in4 from HE.net

[Dave Taht]

Per the url I posted earlier you can stick something like this into
/etc/firewall.user

    ip -6 route add blackhole 2406:da00:ff00::/96 # AWS
    ip -6 route add blackhole 2607:FB10::/32
    ip -6 route add blackhole 2620:0:ef0::/48
    ip -6 route add blackhole 2a00:86c0::/32

I actually used "unreach" and put it in /etc/config/networks

config 'route6' 'killnetflix61'
        option 'interface' 'lan'
        option 'target' '2406:da00:ff00::/96'
        option 'type' 'unreachable'
        option 'proto' '50'

... etc...

I then used the proto 50 bit (requires ip-full), to make  babel pick it up with
a redistribute proto 50
line. (I use this also to propigate /22s around for ipv4)

Neither approach is something "joe user" will be able to do.

But it turned out to be essentially just as much work to just
propigate my native /60s
to the entire campus network statically and try to work out what new security
holes I'd introduced. I have 22 APs to renumber if I get renumbered,
and a few dns entries.


On Sat, Mar 21, 2020 at 3: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



-- 
Make Music, Not War

Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-435-0729

Re: [Cerowrt-devel] [Bloat] OT: Netflix vs 6in4 from HE.net

[Rich Brown]

 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
> 

Re: [Cerowrt-devel] [Bloat] OT: Netflix vs 6in4 from HE.net

[David P. Reed]

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
> 

Re: [Cerowrt-devel] [Bloat] OT: Netflix vs 6in4 from HE.net

[Colin Dearborn]

[-- 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 --]

Re: [Cerowrt-devel] [Bloat] OT: Netflix vs 6in4 from HE.net

[Dave Taht]

It is easy to use a nearby linode server as an ipv6 vpn. Back when I was still
doing it (I too went native ipv6), I used wireguard and babel and
source specific routing to bring ipv6 anywhere I felt I needed it.
Linode will give you your own ipv6/64 if asked. If asked especially
nicely you can get a /56....

whether or not they meet netflix's requirements for geolocation i don't know.

Re: [Cerowrt-devel] [Bloat] OT: Netflix vs 6in4 from HE.net

[David P. Reed]

Sadly, my home provider, RCN, which is otherwise hugely better than Comcast and Verizon provisioning wise, still won't provide IPv6 to its customers. It's a corporate level decision. I know the regional network operations guys, which is why I know about the provisioning - they have very high-end DOCSIS 3.1 fabric, with extra capacity, unlike Comcast and Verizon, who are not replacing gear with newer gear until it breaks.

Unfortunately I haven't found a really local place to get IPv6 tunneling from. I've had my he.net /56 forever, but the best tunnel goes down to NYC. And the peering wars are just truly annoying when he.net is blocked as it is from some AS's.

On Tuesday, March 24, 2020 1:47pm, "Dave Taht" <dave.taht@gmail.com> said:

> It is easy to use a nearby linode server as an ipv6 vpn. Back when I was still
> doing it (I too went native ipv6), I used wireguard and babel and
> source specific routing to bring ipv6 anywhere I felt I needed it.
> Linode will give you your own ipv6/64 if asked. If asked especially
> nicely you can get a /56....
> 
> whether or not they meet netflix's requirements for geolocation i don't know.
> 

Re: [Cerowrt-devel] [Bloat] OT: Netflix vs 6in4 from HE.net

[David P. Reed]

Thanks, Colin, for the info. Sadly, I learned all about the licensing of content in the industry back about 20 years ago when I was active in the battles about Xcasting rights internationally (extending "broadcast rights" to the Web, which are rights that exist only in the EU, having to do with protecting broadcasters whose signals are powerful enough to cross borders of countries, so a whole new, non-copyright-based Intellectual Property Right was invented. WIPO wanted to argue that the Web was just like broadcasting across borders, so web pages should be burdened by Xcasting rights, along with all other copyrighted things.)

What I wanted to know was exactly what you just said in passing: that he.net's address space was entirely blocked by Netflix because it wasn't accurately geolocated for "region restriction" enforcement.

Whether I think that is "correct" or "reasonable", I just want to be able to get Netflix in my US house. Not to be any sort of "pirate" intentionally trying to break the license. I really just want that stuff to work as the license between Netflix and content provider requires (I'm sure the license doesn't say "block he.net").


On Tuesday, March 24, 2020 11:11am, "Colin Dearborn" <Colin.Dearborn@sjrb.ca> said:

> 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
> 

Re: [Cerowrt-devel] [Bloat] OT: Netflix vs 6in4 from HE.net

[Toke Høiland-Jørgensen]

"David P. Reed" <dpreed@deepplum.com> writes:

> Thanks, Colin, for the info. Sadly, I learned all about the licensing
> of content in the industry back about 20 years ago when I was active
> in the battles about Xcasting rights internationally (extending
> "broadcast rights" to the Web, which are rights that exist only in the
> EU, having to do with protecting broadcasters whose signals are
> powerful enough to cross borders of countries, so a whole new,
> non-copyright-based Intellectual Property Right was invented. WIPO
> wanted to argue that the Web was just like broadcasting across
> borders, so web pages should be burdened by Xcasting rights, along
> with all other copyrighted things.)
>
> What I wanted to know was exactly what you just said in passing: that
> he.net's address space was entirely blocked by Netflix because it
> wasn't accurately geolocated for "region restriction" enforcement.
>
> Whether I think that is "correct" or "reasonable", I just want to be
> able to get Netflix in my US house. Not to be any sort of "pirate"
> intentionally trying to break the license. I really just want that
> stuff to work as the license between Netflix and content provider
> requires (I'm sure the license doesn't say "block he.net").

This can also be achieved by filtering the DNS responses for Netflix.
Here's a guide for doing this with Bind and dnsmasq:

https://community.ui.com/questions/Blocking-IPv6-traffic-to-Netflix-over-HE-net-tunnel/816b5753-6a86-4781-935e-06f5e972428f#answer/39318121-4ef3-4425-8e20-0c5d39f03937

And here's someone who got annoyed enough to write a Python daemon to do
the same thing:

https://github.com/cdhowie/netflix-no-ipv6-dns-proxy

-Toke

Re: [Cerowrt-devel] [Bloat] OT: Netflix vs 6in4 from HE.net

[Michael Richardson]

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


Mark Andrews <marka@isc.org> wrote:
    > Netflix could just redirect requests from HE.NET address ranges to IPv4
    > only servers and that would solve the issue for all HE.NET customers.
    > This isn’t the case of attempting to circumvent GEOIP rules.  They can
    > detect that the connection is coming from a HE.NET address range, they
    > can easily install a redirect.

Yeah. That's a good idea.

Maybe even just 404 (maybe faster than host unreachable) even when you
connect from an range they don't like, and make sure their client does Happy Eyeballs.

Users and/or he.net could find a way to (optionally!) blackhole route netflix
IPv6, but that may be very hard to maintain that list.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]