Netflix streaming issue 2014-05-24

Forums › Online streaming services › Netflix streaming issue 2014-05-24

1 | ... | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | ... | 53

115 posts

Master Geek
+1 received by user: 11

#1054646 27-May-2014 22:09

I was able to get US netflix working this afternoon but now it seems to have stopped again. Might just wait it out now, see what happens in the next few days.

watsonash

91 posts

Master Geek
+1 received by user: 14

#1054648 27-May-2014 22:18

All we need is for sky NZ to change the nds encryption like what happened to Foxtel and all of us running media centres will be queueing up down the local movie store to rent DVDs/bluerays!
Looks like we'll all need to switch to SSL vpns in the meantime and hope that our upstream VPN providers can dance around geo-ip blocking strategies that are being worked on!

wasabi2k

2101 posts

Uber Geek
+1 received by user: 856

#1054650 27-May-2014 22:31

Telecom VDSL with Getflix - appears to be ok now.

Nope: Broken again

jarj

35 posts

Geek
+1 received by user: 9

#1054656 27-May-2014 22:32

Stopped again with me too

bequbed

18 posts

Geek

#1054660 27-May-2014 22:44

Working fine as of this evening for Netflix US.

Have watched 6 different episodes with no issues/error at all.

I am on Slingshot Unlimited ADSL with Global Mode ON. I dont use any paid DNS services since Slingshot's Global Mode does the job quite perfectly.

ovipop

34 posts

Geek

#1054664 27-May-2014 22:52

Netflix US works on Snap ADSL with unblock-us.

kingjj

1728 posts

Uber Geek
+1 received by user: 445

ID Verified

Trusted

#1054669 27-May-2014 23:23

Netflix US has been working flawlessly for us on Telecom ADSL during the time of these issues. Switched to Snap UFB this afternoon and not an issue with it yet.

Telecom ADSL and Snap UFB

Un-Blockus

PS3/Android Tablet/Windows 7

AliExpress

Shop now on AliExpress (affiliate link).

PaulZA

314 posts

Ultimate Geek
+1 received by user: 10

#1054681 27-May-2014 23:46

Something's not quite right about this, if it is in fact Netflix, trying to block off international users, surely the whole world would be effected.

Why is it just kiwi users complaining?

Something's not quite right...

PaulZA

314 posts

Ultimate Geek
+1 received by user: 10

#1054684 27-May-2014 23:53

If anybody here, is running Telecom VDSL, and they are unable to access Netflix (Not UFB, or ADSL2+, as that's confirmed working already), and has access to two different VDSL modems, even if one is stored somewhere, are they able to test them both out, and see what happens just to rule that out.

I know the Technicolor units, had issues with Windows 8.1, so it wouldn't surprise me, if some of DNS settings on the Huawei units also have issues.

I wish I didn't ship my old Technicolor VDSL modem off in such a hurry, as I could've done that test myself.

UnoTellyNick

52 posts

Master Geek
+1 received by user: 30

Trusted

Unotelly

#1054692 28-May-2014 00:31

Hi all,

We suspect the root cause is transparent proxy and caching requests/responses.

Pre-NZ-Netflix-Issue:
1. NZ ISPs running transparent proxy and cache (Let's call it ISPv1)
2. Netflix Streaming Auth/Checksum (Let's call it NFv1)
3. Streaming works fine

Now:
1. NZ ISPs running transparent proxy and cache (ISPv1) (no specific changes at ISPs)
2. Netflix updated Streaming Auth/Checksum(NFv2)
3. Broken streaming

It seems to be an unintended consequence of some update at Netflix's end.

@Slingshot users, please try this:

1. Go to Slingshot control panel
2. Turn off the caching
3. Try US Netflix
4. Turn back on
5. Try US Netflix
6. Report your result here

http://www.unotelly.com

Unlock Netflix, BBC iPlayer, Hulu, and more in New Zealand!

UnblockUs

14 posts

Geek
+1 received by user: 27

Trusted

Unblock-US

#1054694 28-May-2014 01:07

Hi guys,

Following our testing through the night, we're now looking for a few people that have US/CA Netflix working without any issues, that have a mac.

If you could drop me a PM that would be awesome.

Thanks all of you for your help and info so far - it's very much appreciated.

UnblockUs

14 posts

Geek
+1 received by user: 27

Trusted

Unblock-US

#1054700 28-May-2014 03:49

Another update from us, we've investigated the issue and here is what we've found:

1. Netflix recently changed the format of URLs for US and Canadian CDN used for video streaming

2. The affected NZ providers are using transparent caching proxies for the Netflix CDN range of IP addresses.

They are NOT using these for other IP ranges we tested.

3. The affected NZ providers are using transparent caching proxies that are set up incorrectly:

- They cache content with "no cache" directive in HTTP header (Pragma: no-cache & Cache-Control: no-store)

- They ignore query string part of the URL for caching

The combination of 1, 2 and 3 has resulted in the Netflix streaming issue. Netflix has started using query string part of the URL to request the movie pieces.

Since the content is cached incorrectly, the Netflix player tries to get a fragment of the movie but gets a completely different movie piece from the proxy and shows the error message.

Affected ISPs have to reconfigure their proxies to:

Take query string into account OR
Respect "no cache" directive OR
Turn them off for Netflix CDN IP range as caching Netflix streaming does not work anymore.

We encourage you to send the above to your ISP - as this is how they can fix the issue. If enough of you speak - then your ISP might do something about it.

watsonash

91 posts

Master Geek
+1 received by user: 14

#1054702 28-May-2014 04:00

a theory here....
When I was trying to get my chromecast working several months ago I was attempting to minimise traffic through to the unotelly DNS servers so I used a dnsmasq configuration to only forward the DNS requests that I was interested in.
What I found was that different devices use different CDNs to stream the content.
In the case of BBC iplayer on an android and PC browser, BBC content would stream fine forwarding the requests to a PC via forwarding bbc.co.uk. However, it would fail on the chromecast. When I did a packet trace using tcpdump looking for port 53 on my router (DNS traffic), I realised that the chromecast was also using the "cp143012-i.akamaihd.net" for main content streaming.
I see @skewt had an issue with the fbstatic-a.akamaihd.net URL.
I suspect Akamai have changed their configuration to prevent traffic being proxied by Unotelly (and others) on the *.akamaihd.net URL (maybe others) - as its my understanding that unotelly is essentially intercepting some DNS requests and for ones which need to be seen to be coming from overseas, resolves the request to a different IP corresponding to one of their offshore proxying servers.

So to fix some of the issues, I think Unotelly may need to set up a new proxying service at a different point in the US and then change their infrastructure so requests on *.akamaihd.net are being seen as originating from a different IP block in the US.

If I look at http://www.cidr-report.org/as2.0/ I see that during the last week, there have been quite a lot of Akamai routing changes - I don't know if this is expected or not.

I'm with Bigpipe who are not using a transparent proxy, so I'm not convinced this is entirely ISP proxy related - its more likely to be route optimisation on the Akamai nodes.

does this sound logical?

I can't help feeling that it is relatively trivial for the CDN owners to identify and block traffic to these geo-ip unblocker services like UnoTelly so as they become more prevalent, they are more likely to raise the eyebrows with the contents rights owners and this could easily turn into a game of cat and mouse.

The ultimate solution to all of this is for Netflix/BBC etc to change their models to take into account the NZ market, but this is unlikely to happen while the content owners are holding onto their "sell same content to multiple regions" model.

psychnurse

329 posts

Ultimate Geek
+1 received by user: 37

ID Verified

Trusted

#1054706 28-May-2014 06:18

Looks like the DNS companies have identified the issue, now we wait for our ISP's to take action. Telecom!

robjg63

4110 posts

Uber Geek
+1 received by user: 1370

Subscriber

#1054711 28-May-2014 07:34

Think there is any likelyhood that vodafone will even be remotely interested in the above suggestions given their previous statements?

Might be useful to get a list of isps that 'fix' the issue....

Nothing is impossible for the man who doesn't have to do it himself - A. H. Weiler

1 | ... | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | ... | 53