From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: "David P. Reed" <dpreed@deepplum.com>,
Colin Dearborn <Colin.Dearborn@sjrb.ca>
Cc: Rich Brown <richb.hanover@gmail.com>,
"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: Wed, 25 Mar 2020 09:56:26 +0100 [thread overview]
Message-ID: <878sjorex1.fsf@toke.dk> (raw)
In-Reply-To: <1585088915.30981517@apps.rackspace.com>
"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
prev parent reply other threads:[~2020-03-25 8:56 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
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 [this message]
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=878sjorex1.fsf@toke.dk \
--to=toke@toke.dk \
--cc=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