[189855] in North American Network Operators' Group
Re: Netflix VPN detection - actual engineer needed
daemon@ATHENA.MIT.EDU (Owen DeLong)
Wed Jun 8 11:23:43 2016
X-Original-To: nanog@nanog.org
From: Owen DeLong <owen@delong.com>
In-Reply-To: <32FC6E7F-12E8-4B11-8416-C31FFEE340DA@feld.me>
Date: Wed, 8 Jun 2016 11:23:35 -0400
To: Mark Felder <feld@feld.me>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
Mark,
That would be bad.
At least in my case.
My addresses (192.159.10.0/24, 192.124.40.0/23, 2620:0:930::/48) are not =
from a known residential ISP or mobile ISP.
However, they are within my household and nowhere else. There=E2=80=99s =
no valid reason for Netflix to block them. They are not a server or =
proxy host.
They are not being used to subvert geo-fencing. They=E2=80=99re just my =
home addresses that I have had for many years and use in order to have
stable addressing across provider changes.
Owen
> On Jun 7, 2016, at 9:21 AM, Mark Felder <feld@feld.me> wrote:
>=20
>=20
>> On Jun 6, 2016, at 22:25, Spencer Ryan <sryan@arbor.net> wrote:
>>=20
>> The tunnelbroker service acts exactly like a VPN. It allows you, from =
any
>> arbitrary location in the world with an IPv4 address, to bring =
traffic out
>> via one of HE's 4 POP's, while completely masking your actual =
location.
>>=20
>=20
> Perhaps Netflix should automatically block any connection that's not =
from a known residential ISP or mobile ISP as anything else could be a =
server someone is proxying through. It's very easy to get these subnets =
-- the spam filtering folks have these subnets well documented. /s
>=20
> --
> Mark Felder
> feld@feld.me
>=20
