[189778] in North American Network Operators' Group
Re: Netflix VPN detection - actual engineer needed
daemon@ATHENA.MIT.EDU (Ricky Beam)
Mon Jun 6 18:24:05 2016
X-Original-To: nanog@nanog.org
To: "John Peach" <john-nanog@peachfamily.net>
Date: Mon, 06 Jun 2016 18:23:58 -0400
From: "Ricky Beam" <jfbeam@gmail.com>
In-Reply-To: <20160606110813.255c66da@jpeach-desktop.anbg.mssm.edu>
Cc: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org
On Mon, 06 Jun 2016 11:08:13 -0400, John Peach
<john-nanog@peachfamily.net> wrote:
> The whois information on the HE IPv6 address, does give the location.
> At least, it does on mine.
It lists the location of the user's registration -- which could very well
be a lie as they do nothing at all to verify it. AND that has zero
correlation with where the tunnel actually goes. There in is the
problem... your tunnel isn't nailed to a physical line ["T1"], or a
physical device ["cablemodem"]; it's loosely pinned to an IPv4 address. An
address that can change in an instance. An address that can literally be
any where.
