[189684] in North American Network Operators' Group
Re: Netflix VPN detection - actual engineer needed
daemon@ATHENA.MIT.EDU (Owen DeLong)
Sat Jun 4 14:33:41 2016
X-Original-To: nanog@nanog.org
From: Owen DeLong <owen@delong.com>
In-Reply-To: <CAPPYGuzyq5ut1FrquR6BNnpuOHjkbTzxc6mxPwn60cWyecB68g@mail.gmail.com>
Date: Sat, 4 Jun 2016 11:33:33 -0700
To: Cryptographrix <cryptographrix@gmail.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org
> On Jun 3, 2016, at 18:31 , Cryptographrix <cryptographrix@gmail.com> =
wrote:
>=20
> Honestly I was trying to make that sound like a "missed connections" =
ad
> there for a moment, but seriously I'd buy a /40 right now if possible =
to
> have non-tunneled IPv6 if I could.
You can easily get a /48 from ARIN. Not sure why you think you=E2=80=99d =
need a /40 for home.
I=E2=80=99m a pretty big fan of sparse allocation and tend to be =
considered an outlier for extreme
home networking and my /48 still has many subnets available.
> It's so weird being on US internet - your content distributor makes =
you
> feel like a criminal because their content provider has standing =
orders to
> deny you from viewing the content they provide and the only other =
thing you
> can do about it is turn off the thing that gives you access to the way =
you
> make the money to pay for their stuff.
Yep=E2=80=A6 RIAA and MPAA proving once again that they just don=E2=80=99t=
get it.
Owen
>=20
>=20
>=20
> On Fri, Jun 3, 2016 at 9:25 PM Raymond Beaudoin <
> raymond.beaudoin@icarustech.com> wrote:
>=20
>> As an alternative, there are multiple cloud service offerings that =
will
>> advertise your IPv6 allocations on your behalf direct to a server in =
their
>> data centers. It seems pretty tongue-in-cheek, and satisfying, to =
turn up a *<insert
>> favorite virtual router instance> *and then route through it. The
>> Internet is such an amazing place.
>>=20
>> On Fri, Jun 3, 2016 at 8:15 PM, Cryptographrix =
<cryptographrix@gmail.com>
>> wrote:
>>=20
>>> Yeah I RAWRed to them pretty hard whilst being as understanding to =
the CS
>>> rep that it wasn't their fault.
>>>=20
>>> They thought I was weird as anything.
>>>=20
>>> If there are any Verizon FiOS network engineers on the thread, a =
fellow
>>> Verizon employee would thank you kindly for an off-thread email =
regarding
>>> BGP advertisement (I'll buy the IPv6 block and the drink-of-choice, =
you
>>> configure my account to listen for route advertisement).
>>>=20
>>> Strange that it has to come to this to get "legit" IPv6 service.
>>>=20
>>>=20
>>>=20
>>>=20
>>> On Fri, Jun 3, 2016 at 9:08 PM Raymond Beaudoin <
>>> raymond.beaudoin@icarustech.com> wrote:
>>>=20
>>>> I wasn't originally affected on my he.net tunnel, but this evening =
it
>>>> started blocking. The recommended ACLs are a functional temporary
>>>> workaround, but I've also opened a request with Netflix.
>>>>=20
>>>> On Fri, Jun 3, 2016 at 7:54 PM, Mark T. Ganzer =
<ganzer@spawar.navy.mil>
>>>> wrote:
>>>>=20
>>>>> So far I am not seeing a Netflix block on my he.net tunnel yet. I
>>>> connect
>>>>> to the Los Angeles node, so maybe not all of HE's address space is
>>>> being
>>>>> blocked.
>>>>>=20
>>>>> Not going to be disabling IPv6 here either. + HAD native IPv6 from =
Time
>>>>> Warner, but they decided to in their wisdom to disable IPv6 =
service for
>>>>> anyone that has an Arris SB6183 due to an Arris firmware bug. And
>>>> they are
>>>>> taking their sweet time pushing out the fixed firmware update that
>>>> Comcast
>>>>> and Cox seemed to be able to push to their customers last fall.
>>>>>=20
>>>>> -Mark Ganzer
>>>>>=20
>>>>>=20
>>>>> On 6/3/2016 4:49 PM, Cryptographrix wrote:
>>>>>=20
>>>>>> Depends - how many US users have native IPv6 through their ISPs?
>>>>>>=20
>>>>>> If I remember correctly (I can't find the source at the moment),
>>>> HE.net
>>>>>> represents something like 70% of IPv6 traffic in the US.
>>>>>>=20
>>>>>> And yeah, not doing that - actually in the middle of an IPv6 =
project
>>>> at
>>>>>> work at the moment that's a bit important to me.
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> On Fri, Jun 3, 2016 at 7:45 PM Baldur Norddahl <
>>>> baldur.norddahl@gmail.com
>>>>>>>=20
>>>>>> wrote:
>>>>>>=20
>>>>>> Den 4. jun. 2016 01.26 skrev "Cryptographrix" <
>>>> cryptographrix@gmail.com>:
>>>>>>>=20
>>>>>>>> The information I'm getting from Netflix support now is =
explicitly
>>>>>>>>=20
>>>>>>> telling
>>>>>>>=20
>>>>>>>> me to turn off IPv6 - someone might want to stop them before =
they
>>>>>>>> completely kill US IPv6 adoption.
>>>>>>>>=20
>>>>>>> Not allowing he.net tunnels is not killing ipv6. You just need =
need
>>>>>>> native
>>>>>>> ipv6.
>>>>>>>=20
>>>>>>> On the other hand it would be nice if Netflix would try the =
other
>>>>>>> protocol
>>>>>>> before blocking.
>>>>>>>=20
>>>>>>>=20
>>>>>=20
>>>>=20
>>>=20
>>=20
