Netflix VPN detection - actual engineer needed

Tue Jun 7 13:58:58 UTC 2016

(not specifically to Cryptographrix) Anyone that expects any consumer-focused support to be able to address any legal or high level technical situation is a fool for having thought appropriate. These sorts of issues are things you start with Tempkin and others that frequent NOGs and other telecom events. You don't go to the web site support chat to get them to make a change to how they handle IPv6 on their end. 

----- 
Mike Hammett 
Intelligent Computing Solutions 
http://www.ics-il.com 

Midwest Internet Exchange 
http://www.midwest-ix.com 

----- Original Message -----

From: "Cryptographrix" <cryptographrix at gmail.com> 
To: "Mark Felder" <feld at feld.me>, nanog at nanog.org 
Sent: Tuesday, June 7, 2016 8:55:10 AM 
Subject: Re: Netflix VPN detection - actual engineer needed 

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) 

On Tue, Jun 7, 2016 at 9:22 AM Mark Felder <feld at feld.me> wrote: 

> 
> > On Jun 6, 2016, at 22:25, Spencer Ryan <sryan at arbor.net> 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 
> 
> 