yashsingh1/xdaforums huggingface dataset:
[Google Chromecast] king conan:
Sale here. unlocator+ddwrt router+iptables for cc. Im in spain and netflix has been rock solid for a long time.

Now is slow , looses connection from phone. And vídeo quality barely tocuhes HD...

I truly hope de can get The previous situation.
[Google Chromecast] Matthew Carson:
Mine still works (see my post above) but I have still been having problems with quality. I also see a couple of other people complaining about it. How fast is your internet speed? It seem to me that Netflix on CC will not use more than about 10% of my bandwidth. I had some problems with my service provider and was only getting 1.5 Mbps, and Netflix would not use over about 150 kbps so it was buffering a lot and quality was horrible. Sometimes the speed was even slower and I could not get it to play. Now bandwidth is fixed and is around 5 Mbps, but the CC is still only using 400-500 kbps. (It uses around 1 Mbps on my S3) I can't say for sure what it was using with the old firmware because I never checked, but the quality is definitely worse now. However, it is only on Netflix - I have seen 1-2 Mbps on WatchESPN with the new firmware. I noticed that when my bandwidth was really slow that I would start a show and it would be taking 600-700 kbps. However, within a few minutes it had reduced down to 140 kbps and stayed stable.
[Google Chromecast] irishpancake:
OK, and thanks.....

So, I finally got to try this out again.....

My set-up here is:

I have ADSL, pretty crap BB in my Village, but OK for Netflix, so I won't comment on quality, because it's never more than 3Mb d/l, but it's unlimited, so I am happy enough.

I have an ancient netopia/motorola modem/router, from my previous provider, still using it, because familiarity, etc.

So, Netflix just works from my PC/Lapto, no problems....also on my LG Smart TV Netflix App. (actually very good, once you put in a static IP on the telly)...

That said, it gets interesting with Android.....so I tried from two devices, a Moto g and a Nexus 7 (2013).

Moto g has new Netflix,,,(3.7.2) and Nexus has the previous version (3.7.1).

I have no static route or DNS settings on either Android device, just DHCP.

My router has been set up with Smartydns DNS settings, as shown below:

Also, I have set up Static routes specificaly for google DNS, shown below:

Static Route Settings for Google DNS re-direct

This should be done for both 8.8.8.8 and 8.8.4.4

My results are:

For my Moto G (latest Netflix).....

as before, Netflix will not stream to the Android local Device(Moto G), unreachable, times out, with error 12001.

Netflix will however stream to my Chromecast enabled TV no problem at all. [CC is at 19084 F/W..S/W ver 1.7.4]

The Movie I chose for the test is 100 Below Zero (OK, not my taste, but only on US Netflix, not on UK/Ireland)....

and I only watched the first 3 minutes!!!! I promise.

For my Nexus 7 (previus Netflix ver).....

The crappy Movie streamed on my Nexus, no problemo.........and also streamed perfectly to my Chromecast-enabled TV.

So, my conclusions are, for me anyway:

Use Netflix Version 3.7.1, set up your Smart DNS on your router, if you can, and use Static Routes to divert 8.8.8.8 and 8.8.4.4 into the ground!!!

iptables would probably solve the problem with "new" Netflix streaming on an Android device, but that requires a router which supports them, like dd-wrt or tomato firmware enabled routers.

There is no problem, for me anyway, with the CC Netflix "App".....

really some clever stuff like a "media player embedded in an HTML5 page" which I am quoting from here, because I know nothing about that stuff.

Hope this helps.
[Google Chromecast] DJames1:
If you must choose something to test U.S. Netflix briefly, I recommend Robot Chicken episodes. Quick cuts and very funny. :)
[Google Chromecast] ahmedsalah83:
that is my setup (but i'm using adfreetime dns), no issues with netflix. hulu plus sometimes doesn't work, tells me that i'm behind an anonymous proxy and that i need to disable it. works again when i restart the hulu chromecast app by switching to another app and back to hulu.
[Google Chromecast] scandalousk:
Sadly enough this doesn't work for me. Got it set up just like that but it won't stream to my chromecast.

It plays fine on my Nexus 5 and 7 though. Once I try to stream it I get the it's not available error.
[Google Chromecast] burnnie:
There's a statement on the unlocator site regarding netflix issues:

Update September 15, 2014: The new Chromecast firmware 19084 is causing issues with Netflix for some users. This is no because of Unlocator but an error with the firmware. If you are unable to use Netflix even when having Google DNS blocked, then please do a factory reset of the Chromecast.

I have no idea if it helps but it's worth a try I guess. On the other hand there were reports that a factory reset on the new firmware broke WiFi or something?
[Google Chromecast] lswai:
I did a factory reset on chromecast on 19084 but it does not help. Still getting title is not available error. It is playing fine on my phone
[Google Chromecast] irishpancake:
Koush, the Allcast guy said factory resetting the CC on that firmware might result in a bricked tiny paperweight. I'll find it, was on Google+

---------- Post added at 11:13 AM ---------- Previous post was at 11:02 AM ----------

Strange, cos it's the streaming to the Android device which is broken in my setup with the latest Netflix.

All is OK when CC is chosen, and if a movie is playing/streaming on the TV, and you then tap the cast icon to change device to your phone/device, the movie does not play on the Android.

You are sure nothing set up on your Android device in WiFi settings/modify network for static routes or DNS??
[Google Chromecast] scandalousk:
I'm guessing this is the post you're talking about: https://plus.google.com/110558071969009568835/posts/cEhdykfYstF

I'm a 100% sure. Although I did play it the other way around. I selected the chromecast first and then attempted to play a video. [EDIT] Doesn't matter.

My setup on my Asus ac68u is like this:

1.Have unlocator dns setup in the router.

2. Have google dns blocked. Can't ping it so I'm sure it's set up properly.

3. Nexus 5 is set to the default dhcp.

Netflix version is 3.7.1.

Chromecast firmware is : 19084
[Google Chromecast] irishpancake:
Thanks, it is certainly weird!!

I'm outta ideas, but happy that I can cast US Netflix to CC with either new or prev versions.

I can't explain why some can and others can't.

Oh, yes, that was Koush's post.

Cheers all, we await developments.
[Google Chromecast] PunchTheLion:
Maybe a clue. Which country do you live in?
[Google Chromecast] scandalousk:
I live in the Netherlands. Funny thing though... I removed the google dns block and guess what... Netflix doesn't play. Made sure I was on the Dutch Netflix and even rebooted the chromecast after removing the settings. Removed the unlocator dns from the router as well.

So I'm guessing Netflix on my end is broken because of the firmware. I'm not going to do a factory reset because of what's in that post. Don't wanna brick it.

Hopefully a fix does come along though.
[Google Chromecast] DJames1:
Did you remember to reboot the router to clear the DNS cache after making changes?
[Google Chromecast] scandalousk:
I did. Didn't work after the route reboot.
[Google Chromecast] clmbtti:
I have the same settings here. I am also testing adfreetime and getting the same message as well when watching Hulu on the cc. I believe it is more a Hulu-related issue, though, as I occasionally get the same error watching Hulu on my appletv. Netflix seems to work fine on both.
[Google Chromecast] fishyrelic:
Chromecast 19084, Netflix 3.7.2 How to setup

Hi All

I have found a solution to this problem.

Netflix on my chromecast in Australia stopped working after the latest update 19084 when casting from Netflix android app 3.7.1 while it would work normally on my laptop and android.

At this point I had unblock-us dns configured on the android device and laptop (issued by the router).

The solution involves fooling the chromecast and android app into thinking they are talking to google DNS while they are actually communicating with unblock-us DNS

Latest chromecast firmware and Netflix app are required for this. (19084 and 3.7.2 respectively)

The way to do this on a cisco router is by using the following configuration

------------------------------------------------------

interface Vlan1 (or any other LAN interface)

ip address 192.168.15.1 255.255.255.0

ip nat inside

ip policy route-map google_dns-redirect

ip access-list extended google_dns

permit udp 192.168.15.0 0.0.0.255 host 8.8.8.8

route-map google_dns-redirect permit 10

match ip address google_dns

set ip next-hop 111.118.175.56

ip nat outside source static 111.118.175.56 8.8.8.8

-------------------------------------------------------

With this config, the router redirects any traffic destined for 8.8.8.8 to instead go to 111.118.175.56 (while the Chromecast thinks it is still going to 8.8.8.8)

It is important that the return traffic to CC does not appear to be coming from Unblock-us so the router needs to be setup to change any traffic coming from 111.118.175.56 to 8.8.8.8 using a static NAT statement.

As you can see, this method is different to the popular method of blackholing traffic to 8.8.8.8 causing the CC to fail over to whatever DNS is configured on the router (unblock-us DNS)

This fix should also be fairly easily to setup on a firewall using a GUI. Not sure if DD-WRT, Open-WRT or Tomato are capable of this as they are firewall features.

Also note that this fix will only work if the Netflix on the Android is latest 3.7.2 as the old version (3.7.1) without hardcoded DNS gives away its location while casting to the lastest chromecast 19084

Hope this helps.
[Google Chromecast] jarayn:
This looks interesting mate.

Do you have any idea if its possible on DDWRT / tomato?

Is it a firewall script like this one (that i have been using but no longer works. Presumably because of the return.

iptables -I PREROUTING -t nat -p udp -d 8.8.4.4 --dport 53 -j DNAT --to-destination
[Google Chromecast] abhinavaca:
Setting on Asus RT-n66U (Solved)

I reside outside USA and use Stock Asus RT-N66U Router, no fancy DD-WRT Firmware etc. I wanted netflix subscription on my Chromecast. I changed the DNS to Unlocator DNS and subscribed to the service. and under LAN>>Route Settings I made the following exceptions as per the image attached. Chromecast now works with Netflix outside USA. I didn't use the Telnet commands etc. as mentioned in the OP.
[Google Chromecast] skivnit:
If I understand correctly, say I'm in France, I can access us Netflix on my phone through VPN, can I just cast it or will cc block it.?
[Google Chromecast] abhinavaca:
Will not cast. The CC uses a DNS of Google hard coded in to it. U need to force it to use other special DNS like unblock us etc.
[Google Chromecast] Vijz:
Chromecast for iPlayer with UnoDNS

Hi,

i use a similar asus router (RT-N12HP). I'm a noob with this. I am in Malaysia and i have a UnoDNS account which i use for netflix etc. through my apple tv. Just got the chrome cast and when i try casting BBC iPlayer from the phone i get an error 94. How do you configure your router to overcome this? Thank you, much appreciated.
[Google Chromecast] abhinavaca:
Refer the pix attachment in my post. U have to block Chromecast request to 8.8.8.8 and 8.8.4.4 DNS. The setting is under lan-route
[Google Chromecast] skivnit:
So unlocator is payable Now any alternative ?
[Google Chromecast] abhinavaca:
None that I know of. If someone else gives a free alternative, it will be great.
[Google Chromecast] scandalousk:
I have a Asus RT-AC68U router and I configured it the exact same way like in your screenshot (had it configured differently before). I thought it worked since I could play select titles like "How I met your mother" and "Arrow" for example. But I've also noticed that I can't play a lot of titles. I tried to cast "Terminator 2", "World War Z" and "Grey's Anatomy" for example and these titles and many others won't play while giving me the "We're having trouble playing this title right now" error. I really wonder why some work and some don't.

I can't check it right now, but I believe that the titles is could play are probably also available in my country. I know for a fact that I'm viewing the USA content since a lot of the content shown on there isn't available in my country. I'm beginning to wonder if it's Netflix (dns) problem or a Chromecast firmware issue.

Unlocator also links to this thread: https://productforums.google.com/forum/#!category-topic/chromecast/4p7GmZIXh6I[251-275-false]

I guess the only way for me to find out where the problem lies is after we get another firmware update.
[Google Chromecast] abhinavaca:
I haven't tried those movie titles yet. Let me check & confirm later. I believe you should be able to view all movies in USA region.

Sent from my XT1053
[Google Chromecast] scandalousk:
Thank you for checking, I appreciate it!

I'm actually hoping it's just me. If that's the case it means something is going wrong on my end and it can probably be fixed.

EDIT: It was as I suspected. I changed the region on my unlocator account to The Netherlands and voila.. I'm able to play ALL of the content provided on the Dutch netflix. This is still with the Google DNS block in effect. After changing it to the UK and the USA. All the content that's available there but NOT in The Netherlands is unavailable to me. (as in I can't cast them)

Titles that are both available in the USA and The Netherlands work. For example, House of cards is available in both countries and thus plays just fine. But Grey's anatomy is only available in the USA and does not play.

So I'm kinda at a loss here since I don't know how to fix this...

In case anyone was wondering, Netflix on my Nexus 5, Nexus 7 and desktop play just fine with the Google DNS block enabled and I'm able to view all the titles exclusive the USA on there. I'm only having issues with the Chromecast.

EDIT 2: IT WORKS! I have no idea how and or what but it suddenly started working...

On a different note. Has anyone tried out the new netflix 3.8.0. to see if it works with the chromecast? I'm still using the 3.7.1.

Don't really wanna mess anything up right now since I just got it working again.
[Google Chromecast] lswai:
Thanks for the info and finally I get my chromecast to work after few weeks. The difference is I need to change response from smart dns server to 8.8.8.8 and 8.8.4.4 as stated. I tested on netflix 3.6 and 3.7.1 and both able to cast to my CC.
[Google Chromecast] abhinavaca:
Great

Sent from my XT1053
[Google Chromecast] abhinavaca:
Hi, I'm outside USA and I use CC (V19084) and Netflix APK (V3.7.1). I didn't have to do the method you posted because I blocked all traffic to 8.8.8.8 & 8.8.4.4. Whats the difference between your method and my method?
[Google Chromecast] jarayn:
why have you done that to 8.8.4.4? DOesnt make sense to me at all. Im no expoert on this stuff though. Havent you redirected it to itself?
[Google Chromecast] abhinavaca:
Same here - I'm no expert either. I used this guide or something similar http://www.buckscoop.com.au/bargain-blog/how-to-configure-google-chromecast-to-access-netflix-or-other-geo-blocked-content/ to block the Google DNS and then I did a Ping, the CMD couldn't reach Google DNS. Have you tried it yet? and is it working?

Update 1: Yeah! I understand what you mean now! I also noticed the error in 8.8.4.4. Nevertheless, it works fine! Someone knowing networking rules may be able to know why it works even though there is an error.
[Google Chromecast] fishyrelic:
What you did seems to be a popular method being used by a lot of people and from what I've read. By blocking traffic to 8.8.8.8 and 8.8.4.4 the CC has no choice to fail over to whatever is configured on the router (VPN provider's DNS)

This method stopped working for a lot of people after the CC 19084 update. I'm not sure how it works for you but blocking traffic doesn't work for me any more.

The latest patch must have removed the fail over process causing the CC to throw an error if it can't talk to 8.8.8.8

My method is simple, The router redirects traffic to Unblock-us DNS instead of 8.8.8.8 and makes the return traffic to CC look like its coming from 8.8.8.8. Chromecast thinks it is talking to google DNS since it is always sending to and receiving from 8.8.8.8

Also, Netflix APK 3.7.2 has hardcoded DNS 8.8.8.8

Even with my method, I had to upgrade my APK to 3.7.2 for some reason
[Google Chromecast] abhinavaca:
Thanks for the explanation. I will continue with my current set up till such time Google or Netflix abandon me with their Hardcoded DNS. As such I dont think I'm losing any major functionality by not upgrading to the latest version of Netflix.
[Google Chromecast] scandalousk:
This is probably the most effective way of solving the problem. The thing is that my Asus RT-AC68U doesn't support the method. At least I don't think it does.

Wish I had paid attention and rooted my chromecast before it updated to the latest firmware. Would have solved all the problems.
[Google Chromecast] skivnit:
Dammit I have a **** modem that doesn't have any static route tab. If I root my chromcast will I encounter same problem?
[Google Chromecast] abhinavaca:
I think u can root CC having any version lower than 19084. Plus, U can change the DNS after root ( assuming u root it). I will doubt u can do it because updates are automatically done on a CC & u may be on latest version already. Using latest Netflix APK also may not help because DNS is hardcoded in it. Nevertheless, a rooted chromecast with Netflix 3.7.1 may be a possibility! All the best!
[Google Chromecast] skivnit:
I actually have a 3c serial with 12xxx firmware so it's rootable, just ordering my board and otg.
[Google Chromecast] abhinavaca:
Good for u!

Sent from my XT1053
[Google Chromecast] jarayn:
I would love to try your way but I dont think I can with DDWRT.

Do you know how to do the same thing with iptables or static route or is it not possible

Thanks
[Google Chromecast] DJames1:
That method still works with my Chromecast after the 19084 update, although not with Android Netflix version 3.7.2, but I just reverted to 3.7.1.

Netflix is making a lot of changes in their apps at the moment, so it's difficult to say what works and what doesn't. Safest to stick to old versions that do work if you can.
[Google Chromecast] clmbtti:
I saw a script on reddit that is currently working just fine in my tomato-based router. You can use it to redirect all traffic going out on TCP/UDP port 53 to a specific IP address:

iptables -t nat -A PREROUTING -i br0 -p udp --dport 53 -j DNAT --to 192.168.1.1

iptables -t nat -A PREROUTING -i br0 -p tcp --dport 53 -j DNAT --to 192.168.1.1

(assumes router IP is 192.168.1.1 - change accordingly or reroute to your smart DNS server of choice directly)

(assumes interface is br0 - change accordingly)
[Google Chromecast] ykphuah:
I factory reset my tablet yesterday, and I can't login to Netflix anymore no matter what I did. It always says that Netflix is not available in your location. It was working before, and I have always updated to the latest version.

Read from unlocator's support page that Netflix version 3.7.2 and above will have this issue. Tried the iptables commands in the first page and it still doesn't work. Finally I need to downgrade it to 3.7.0, glad that I have the apk stored.

It seems to me that the checking for Log In and watching is different, as I was still able to watch before the factory reset, and I always update all my apps to the latest.
[Google Chromecast] smartpr1v4t3:
Thanks the script worked

DD WRT and Using the Script with the SmartDNSProxyServer!

Its nearly easier now to manage the DNS Settings with that :)

Never do an DNS Setting again because every App that try to connect to the DNS Server outside my LAN will redirect to the address rly nice.
[Google Chromecast] ahmedsalah83:
using adfreetime dns:

3.7.2 and 3.8.0 can cast only and can't play on my phone, 3.7.1 works on phone.

using a free us dns that i found , all versions working on phone and casting fine.

its weird ... can anyone explain ?

My setup:

DNS setup on router and advanced routing settings as photo.
[Google Chromecast] irishpancake:
Taking the piss, right??
[Google Chromecast] varun.c.jain:
I have updated the OP with the iptables rules which work for me for Netflix Android app v3.8 and beyond
[Google Chromecast] Mrwazsx:
On what subreddit
[Google Chromecast] clmbtti:
r/sysadmin
[Google Chromecast] Simmster:
Sorry for the n00b question but I mentioned people using a Raspberry Pi as an access point to get around these DNS issues - is that still possible after the latest Netflix update with DNS Hardcoded into the app?

Thanks! If it's still possible then I know what I'll be ordering today.
[Google Chromecast] nicolaspy:
Unlocator + BBC iPlayer + Chromecast stopped working

Hey Guys!

I have been using Unlocator for about the last 4 weeks. It's been like a dream compared to my previously already awesome solution, TunnelBear. Something must have changed this morning or yesterday on some side of things because I can no longer do what I was doing very easily for the last few weeks.

I'm located in the US.

I own a Chromecast w/ Firmware Version 19084 and country code US

I own a Netgear R6300 running DD-WRT setup with iptables as described here: http://goo.gl/JV0tRO

I own a Mac running OSX 10.10, Chromebook running the latest beta build, Android Phone running 4.4, and iPhone 4s running iOS 7.1. I am running Chrome 38.0.2125.111 on the Mac.

Previous to today, I could start watching content on any of my devices at www.bbc.co.uk/iplayer or the BBC iPlayer Apps AND when I clicked the Cast button it would successfully cast the content onto my Chromecast and continue playing. (I went out and bought a DD-WRT compatible router and paid for Unlocator even though I had 6 months left on Tunnelbear because I was tired of hooking up my computers via HDMI to our TV just so that we could watch BBC - when everything else we've been able to Cast. This was so awesome and felt like Magic when it all came together and worked.)

As of today, I can start watching content on all these devices, but when I try casting to the Chromecast, I get errors on the casting device and a Brain Freeze error on the Chromecast.

Chromecast: brain freeze

We're sorry, but something could not load

Activity Aborted

Android: Google Play Services Error. An error has occurred - please try again. (Error Code: 2002)

Chrome: Unable to cast to device.

An unexpected error occurred.

Please try the following:

Try to cast again

Verify your network connectivity

I have 3 Green Check marks at the Unlocator Dashboard. I visited the IP Updater link. I rebooted my router from within the DD-WRT GUI. I factory reset my Chromecast. I rebooted my Mac. I rebooted my Android phone. (I haven't been able to test on IOS but I suspect the same results). I sent a support email to Unlocator. What else do you guys think I could try out? Did Google or BBC take notice and make a change in the way they check geography? Anyone else experiencing this problem?

I really hope I can find a way to fix this!
[Google Chromecast] zoot1:
Were you able to find a solution to this problem.

Also, add this iptables rule with the forwarding rule in your firewall setup:

iptables -t nat -A POSTROUTING -j MASQUERADE

This shows that the incoming traffic from your DNS server is coming from Google DNS. (According to what I have read)

Let us know if this works.
[Google Chromecast] DJames1:
Also please mention what version of the iPlayer apps you are using, as that might make a difference if they have updated.