Netflix VPN detection - actual engineer needed

Tue Jun 7 14:22:39 UTC 2016

On Tuesday, June 7, 2016, Cryptographrix <cryptographrix at gmail.com> wrote:

> As I said to Netflix's tech support - if they advocate for people to turn
> off IPv6 on their end, maybe Netflix should stop supporting it on their
> end.
>
> It's in the air whether it's just an HE tunnel issue or an IPv6 issue at
> the moment, and if their tech support is telling people to turn off IPv6,
> maybe they should just instead remove their AAAA records.
>
> (or fail back to ipv4 when v6 looks like a tunnel)
>
>
I think you need to reset your expectations of a free tunnel service.

he.net tunnels are a toy for geeks looking to play with v6. In terms of
Netflix subcriber base, it is amazing insignificant number of users.

At the end of the day, anonymous tunnels, just like linux, are not
supported by Netflix. And, he.net tunnel users are hurting ipv6 overall
just like 6to4 by injecting FUD and other nonesense complexity.... For a
toy.

Move on to a real issue instead of beating this dead horse.

CB

>
>
> On Tue, Jun 7, 2016 at 9:22 AM Mark Felder <feld at feld.me <javascript:;>>
> wrote:
>
> >
> > > On Jun 6, 2016, at 22:25, Spencer Ryan <sryan at arbor.net <javascript:;>>
> wrote:
> > >
> > > 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.
> > >
> >
> > 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
> >
> > --
> >   Mark Felder
> >   feld at feld.me <javascript:;>
> >
> >
>