[189549] in North American Network Operators' Group
Turning Off IPv6 for Good (was Re: Netflix VPN detection - actual
daemon@ATHENA.MIT.EDU (Matthew Kaufman)
Wed Jun 1 23:42:32 2016
X-Original-To: nanog@nanog.org
From: "Matthew Kaufman" <matthew@matthew.at>
To: NANOG <nanog@nanog.org>
Date: Thu, 02 Jun 2016 03:41:54 +0000
In-Reply-To: <em67bcc237-1f5b-4fcd-a4f6-20cd797206fc@matthew-t5500>
Reply-To: Matthew Kaufman <matthew@matthew.at>
Errors-To: nanog-bounces@nanog.org
Turns out it has nothing to do with my IPv4 connectivity. Neither of my=
=20
ISPs has native IPv6 connectivity, so both require tunnels (one of them=20
to HE.net, one to the ISPs own tunnel broker), and both appear to be=20
detected as a non-permitted VPN. As an early IPv6 adopter, I've had IPv6=
=20
on all my household devices for years now.
So after having to temporarily turn off IPv6 at my desktop to fix=20
issues with pay.gov (FCC license payments), and issues with various=20
other things, and then remember to turn it back on again... I now have=20
the reason I've been waiting for to turn it off globally for the whole=20
house.
Thanks Netflix for helping move us forward here.
Matthew Kaufman
ps. Would still be helpful if the support techs could tell from the=20
error codes that the denied VPN is an IPv6 tunnel
------ Original Message ------
From: "Matthew Kaufman" <matthew@matthew.at>
To: "NANOG" <nanog@nanog.org>
Sent: 6/1/2016 8:27:00 PM
Subject: Netflix VPN detection - actual engineer needed
>Every device in my house is blocked from Netflix this evening due to=20
>their new "VPN blocker". My house is on my own IP space, and the=20
>outside of the NAT that the family devices are on is 198.202.199.254,=20
>announced by AS 11994. A simple ping from Netflix HQ in Los Gatos to my=
=20
>house should show that I'm no farther away than Santa Cruz, CA as=20
>microwaves fly.
>
>Unfortunately, when one calls Netflix support to talk about this, the=20
>only response is to say "call your ISP and have them turn off the VPN=20
>software they've added to your account". And they absolutely refuse to=20
>escalate. Even if you tell them that you are essentially your own ISP.
>
>So... where's the Netflix network engineer on the list who all of us=20
>can send these issues to directly?
>
>Matthew Kaufman
