On 2016-06-08 18:57, Javier J wrote:
Tony, I agree 100% with you. Unfortunately I need ipv6 on my media subnet because it's part of my lab. And now that my teenage daughter is complaining about Netflix not working g on her Chromebook I'm starting to think consumers should just start complaining to Netflix. Why should I have to change my damn network to fix Netflix? In her eyes it's "daddy fix Netflix" but the heck with that. The man hours of the consumers who are affected to work around this issue is less than the man hours it would take for Netflix to redirect you with a 301 to an ipv4 only endpont. If Netflix needs help with this point me in the right direction. I'll be happy to fix it for them and send them a bill.
They're doing the same thing with IPv4 (banning people based on the apparent IP address). Your IPv4 numbers may not be on their blacklist at the moment, and disabling IPv6 might work for you, but the underlying problem is the practice of GeoIP/VPN blocking, and the HE.net tunnels are just one example of the collateral damage.
I don't know why Netflix and other GeoIP users can't just ask customers where they are located, instead of telling them. It is possible that some user might lie, but what about "assume good faith"? It shows how much they value you as a customer if they would rather dump you than trust you to tell them where you are located.
-Laszlo
