Netflix VPN detection - actual engineer needed

Nicholas Suan nsuan at nonexiste.net
Wed Jun 8 15:58:23 UTC 2016


On Wednesday, June 8, 2016, Baldur Norddahl <baldur.norddahl at gmail.com>
wrote:

>
>
> On 2016-06-08 07:27, Mark Andrews wrote:
>
>> In message <20160608070525.06fd5995 at echo.ms.redpill-linpro.com>, Tore
>> Anderson writes:
>>
>>> * Davide Davini <diotonante at gmail.com>
>>>
>>> Blocking access to Netflix via the tunnel seems like an obvious
>>> solution to me, for what it's worth.
>>>
>> And which set of prefixes is that?  How often do they change? etc.
>>
>>
> A start would be blocking 2620:108:700f::/64 as discovered by a simple DNS
> lookup on netflix.com. I am not running a HE tunnel (I got native IPv6)
> and I am not blocked from accessing Netflix over IPv6 so can't really try
> it. I am curious however that none of the vocal HE tunnel users here
> appears to have tried even simple counter measures such as a simple
> firewall rule to drop traffic to that one /64 prefix.
>

That's a start but Netflix has a few more prefixes than that:
http://bgp.he.net/AS2906#_prefixes6



More information about the NANOG mailing list