Print

[evaq]

Hi,

I've a working tunnelbrokker IPv6 connection.
I had a working Netflix setup (just browser)

Since a few days (so around April 7, 2015), www.netflix.com in Chrome ends a message ""This webpage has a redirect loop". See http://ipv6-or-no-ipv6.blogspot.nl/2015/04/netflix-and-this-webpage-has-redirect.html

Two workarounds:
- start Chrome with IPv6 disabled
- put an IPv4-only entry for www1.netflix.com into my /etc/hosts

So I'm wondering what other Tunnelbroker IPv6 users experience?

One of my hypotheses is that Netflix with *tunneled* Ipv6 is not working anymore. Possibly by a on-purpose setting by Netflix (to avoid seeing content meant for other countries), or by accident.
Reasons for my hypothesis:
- another person is reporting Netflix problems with a Sixxs IPv6 tunnel
- I can't imagine Netflix is out of order for people with native/dual-stack IPv6 connections, as that would have given much more reports.


So: is Netflix still working for you?

[kriteknetworks]

I can hit www.netflix.com from comcast native just fine *shrug*

[evaq]

I should have said: the loop-problem occurs after logging in.

So I'm interested in experiences of people who have a Netflix account and HE IPv6.

[garman9000]

I just started streaming an episode of Mad Men through Netflix with Safari on Mac OS X 10.10.3 and an HE tunnel through the Ashburn PoP- no problems.

[gigawebs]

I am also having evaq's problem since a couple of days. Also asked a Netflix support engineer if they are blocking connections from tunnelbroker.net ipv6 subnets. But the only thing he could say was that IPv6 is still experimental so I should disable my ipv6 tunnel...

I am using the tserv1.ams1.he.net endpoint server.

[Tornevall]

Now it is not only HE that has problems with Netflix. I run both HE and SiXXS but it was through SiXXS i found out about this. Unfortunately, since it seems that Netflix don't accept me from ipv6 anymore, I have reversed my DNS-servers to only resolve netflix on ipv4-level.

http://tornevalls.se/blog/2016/06/10/netflix-and-the-blocking-of-tunneled-ipv6-routes/

[kriteknetworks]

I cancelled my account because nothing says "I'm unhappy with your service" louder than denying them my dollars.  In the case of netflix, trying to work around their policies just continues to encourage netflix to set them, instead of encouraging netflix to address the problem that geo-wtfever is alleging to fix. Money talks. All else walks. /RANT

[ravenstar]

While I know this is an old thread I wanted to add my own experiences.

Initially when connecting to Netflix I used to get offered the US site when I had the IPv6 tunnel enabled, although at times the service would refuse to stream US video's, then confusingly sometimes it would.
When they added the proxy detection this initially gave me issues as well, with me regularly seeing a message telling me I was using a proxy.
In the last week or two, there seems to have been a change.
Netflix is now picking up my address as in the UK and offering me UK content.  Furthermore I've not been seeing the proxy detection warning.
Also I turned off IPv4 on my Laptop and revealed something interesting.  The Netflix Windows App and Chrome can both stream from Netflix using IPv6 only.

Has anyone else noticed any changes?

Ravenstar68