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.
On Fri, Jun 3, 2016 at 7:54 PM, Mark T. Ganzer <gan...@spawar.navy.mil> wrote: > 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. > > 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. > > -Mark Ganzer > > > On 6/3/2016 4:49 PM, Cryptographrix wrote: > >> Depends - how many US users have native IPv6 through their ISPs? >> >> 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. >> >> 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. >> >> >> >> >> On Fri, Jun 3, 2016 at 7:45 PM Baldur Norddahl <baldur.nordd...@gmail.com >> > >> wrote: >> >> Den 4. jun. 2016 01.26 skrev "Cryptographrix" <cryptograph...@gmail.com>: >>> >>>> The information I'm getting from Netflix support now is explicitly >>>> >>> telling >>> >>>> me to turn off IPv6 - someone might want to stop them before they >>>> completely kill US IPv6 adoption. >>>> >>> Not allowing he.net tunnels is not killing ipv6. You just need need >>> native >>> ipv6. >>> >>> On the other hand it would be nice if Netflix would try the other >>> protocol >>> before blocking. >>> >>> >