yashsingh1/xdaforums huggingface dataset:
[Google Chromecast] mltan_bdo:
Di i need to root my chromecast in order to worked with netflix in my home country Phils.
[Google Chromecast] Csopi:
No. Just read the first comment.
[Google Chromecast] oo0keba0oo:
it looks very useful,THX~~~~
[Google Chromecast] ahighfield:
Thanks so much, working so far for me!
[Google Chromecast] selfmachine:
any new settings about chromecast?
[Google Chromecast] shnk2010:
I have set up my dd-wrt router with the following commands

iptables -t nat -I PREROUTING -p udp -d 8.8.8.8 --dport 53 -j DNAT --to 185.37.37.37

iptables -t nat -I PREROUTING -p udp -d 8.8.4.4 --dport 53 -j DNAT --to 185.37.37.37

iptables -t nat -I PREROUTING -p tcp -d 8.8.8.8 --dport 53 -j DNAT --to 185.37.37.37

iptables -t nat -I PREROUTING -p tcp -d 8.8.4.4 --dport 53 -j DNAT --to 185.37.37.37

It is working for netflix but, I want to restrict the usage of unlocator to netflix alone. The rest of the traffic should go to Google dns.

Please guide with regards to iptables commands to achieve this configuration.
[Google Chromecast] selfmachine:
edit: problem solved
[Google Chromecast] dragonevo:
Is it possible to setup in my tp-link dd-wrt router so your chromecast gets your normal dns from your provider by dhcp so i get the normal EU content from my chromecast, but also to hockup a Roku device by wifi to my router and block google dns only to that device on my network so only the Roku device gets US netflix.

Possible to config something like this with dd-wrt?
[Google Chromecast] mitti2000:
My question might not be completely on topic but I thought, you guys might be able to help me.

I've been using unblock-us for a few years. I mostly watch netflix on my Samsung Smart-TV. Everything used to work fine until Netflix started to block Smart-DNS providers. After a while I got it to work again but only on my computer with a browser.

I tried the stuff mentioned in this post. When I start the netflix app now on my TV, the US Neflix library is loading. I can see all the content that is available in the US. But when I try to stream a show, it loads until 25% and then tells me that there is a problem with my internet. Content that is available in my homecountry (Switzerland) works.

Did anybody encountered something similar and has a solution for it? Would unlocator work better (I haven't tried it)

Thanks,

mitti2000

P.S. Sorry for any bad english
[Google Chromecast] Danny94:
Does this method still work ?

Unblocker is detected by netflix.

Any other cheap solution?
[Google Chromecast] Seano22:
I'm actually out of the house at moment I will try and paste error when I get back. Before I did what you said I couldn't chromecast Netflix from pc or any devices now I can chromecast from pc, ipad, nexus 7. I'm in Australia so not being in the US was stopping me from using Netflix. I am using Unblock-Us so I changed the DNS settings to theirs
[Google Chromecast] Seano22:
admin@192.168.1.1's password:

> # iptables -t nat -I PREROUTING -d 8.8.4.4 -j DNAT --to-destination 111.118.175.56

sshd:error:636.830:processInput:395:unrecognized command # iptables -t nat -I PREROUTING -d 8.8.4.4 -j DNAT --to-destination 111.118.175.56
[Google Chromecast] varun.c.jain:
Hey the # was supposed to indicate that you are writing the command against a prompt. It is not part of the actual command! My mistake. The prompt in your case is the > symbol.

So as I said, Netflix works for you on all your devices currently, because you have properly configured your router with the Unblock-US DNS IPs. However, Netflix won't work on your Chromecast yet. For that you shall have to use the commands (this time without the misleading #)

iptables -t nat -I PREROUTING -d 8.8.4.4 -j DNAT --to-destination 208.122.23.23
iptables -t nat -I PREROUTING -d 8.8.8.8 -j DNAT --to-destination 208.122.23.22

P.S. I don't see 11.118.175.56 as the DNS IP on Unblock-US. The correct IPs are 208.122.23.22 and 208.122.23.23. Here is the source of my information from the Unblock-US website: Setting up a generic router
[Google Chromecast] Seano22:
My mistake I think the first time I did it I didn't use the # it didn't look like it did anything so I added the #, I am able to chromecast Netflix from my devices
[Google Chromecast] Seano22:
The DNS 11.118.175.56 is what Unblock-US gave me when I first joined I think they have changed to new ones but

The old ones still worl
[Google Chromecast] noamxda:
chromecast withoutVPN

Hello All,

Firstly, Thank u so much Junior member for this awesome tutorial really put some hope into my Cast device.

Please forgive me for the nonexpertee this is my first message in xda.

I read the manual and i have a NETGEAR DGN2200 router which does not support DD-WRT. Anyway i connected to the Unlocator service ,setup the DNS and got an active IP for the router. I had some trouble on the next step.

I didn't find the DNSMasq option in my router manager smart wizard (i attached a printscr for the routers interface).

Mean that, I understood that the main part is to define the iptables and for that I enabled Telnet Client but actually i didn't know how to connect to the host and what are the particular commands that I should write down (what's my host IP/name anyway?)

Is the last part, if working, enough for enabling the neflix without the VPN?

what should I look for in the web? And how should i enable those firewall rules?

Thank U very much for any comment , Im really tired to burn out hours trying to fix that...

**p.s. I Use "Hola" as a free VPN service
[Google Chromecast] varun.c.jain:
To begin with, you're welcome for anything that helped you. I quickly Googled up the possible ways to use the iptables commands for you on your Netgear DGN2200 router:

My source of information is Customizing your Netgear DGN2200v3

Enable the Telnet shell by using the debug backdoor by opening http://192.168.0.1/setup.cgi?todo=debug

View your current iptables rules

iptables -t nat -L PREROUTING

If this works, then go ahead and use the iptables commands which have been mentioned in the first post
[Google Chromecast] noamxda:
Thanks for the quick reply. Actually I was already working with this source but yet didn't manage to connect properly to Telnet.

I enabled debug but this time i tried (and succeded) in the same time to connect to the router's IP with the commands:

telnet
o
192.168.0.1

I also tried to connectd to the IP i've got from Unlocator and got into BusyBox v.1 ,which allows me commands like #free or #df ,but didn't respond to iptabels (returned - iptables:not found).

How do I embed new rules and to which host do I need to connect?

THX again
[Google Chromecast] varun.c.jain:
Yeah so you are able to open a Telnet session to your router at 192.168.0.1, which is exactly what the debug backdoor provides. This is the session in which you are supposed to type the iptables commands. You never mentioned whether you tried those commands or not.

I am not sure what you mean by

Which IP did Unlocator give to you? Are you talking about the Unlocator DNS IPs? You aren't expected to connect to these IPs via Telnet or anything. These IPs are simply the DNS servers, which you should configure in your router's DNS section.
[Google Chromecast] varun.c.jain:
Ok I see, so there this shell doesn't include iptables. Unfortunately I can't help you then. The source from where we got this information talks about Netgear DGN220v3. I don't suppose your HW version is v3, so you are unable to see the same options as he can. The only solution I can give you is to try and install a Custom Firmware for DGN2200, all at your own risk.

If this is too much for you, then just get a cheap Wifi router like the TP-Link TL-WR702N for your Wifi LAN, and configure your existing Netgear DGN220 in bridge mode. There is always a workaround.
[Google Chromecast] noamxda:
Yep, I knew there is something fishy...

I think that im going to preform the firmware update. I guess it's gonna be pretty though but ill survive! Do you think that the update will remove the shell and enable me to write down the iptables?

Thank U so much for saving me a lot of time and money.
[Google Chromecast] Antiq:
Hulu+ app on Android is not working "Bad response from server [34]" :( Is there any solution like for netflix? :confused:
[Google Chromecast] varun.c.jain:
The same solution should work for Hulu+ too. Unlocator's DNS should lift the geoblocking restrictions for Hulu+ just like it does for Netflix. I haven't subscribed to Hulu+ so cannot say for sure if you can Chromecast it from Android, but I can sure watch Hulu on my PC using Unlocator. I believe it should be no different when working with Chromecast.
[Google Chromecast] CliveWRSA:
Working with Ubuntu and PPPOE

I just would like to let people know this method works just fine if your internet gateway is an Ubuntu Server and you are dialing your internet over PPPOE.

My iptables rules are as follows.

-A PREROUTING -p tcp -m tcp -d 8.8.8.8/32 --dport 53 -j DNAT --to-destination 196.41.139.189

-A PREROUTING -p udp -m udp -d 8.8.8.8/32 --dport 53 -j DNAT --to-destination 196.41.139.189

-A PREROUTING -p tcp -m tcp -d 8.8.4.4/32 --dport 53 -j DNAT --to-destination 196.41.139.189

-A PREROUTING -p udp -m udp -d 8.8.4.4/32 --dport 53 -j DNAT --to-destination 196.41.139.189

-A PREROUTING -p udp -m udp -d 192.168.1.1/32 -i p135p1 --dport 53 -j DNAT --to-destination 196.41.139.189

-A PREROUTING -p tcp -m tcp -d 192.168.1.1/32 -i p135p1 --dport 53 -j DNAT --to-destination 196.41.139.189

I use unotelly for my Netflix unblocking. I live in South Africa.

Regards to all

Thanks to OP for the original work around.
[Google Chromecast] ykphuah:
Asus RT-N12

Thanks for the instructions!

Would like to add on that for Asus RT-N12, I just need to enable Telnet, and then I can run the two iptables commands after logging in to telnet. DD-WRT is not needed. It doesn't persist after reboot though.
[Google Chromecast] CliveWRSA:
Nice one :)

I'm quite sure you could add your own init script that will apply the settings when the router boots. Or amend it to some rc script somewhere.
[Google Chromecast] ykphuah:
Well, I am quite well versed with Linux, and tried to look for ways to do this in 2 hours, failed, and gave up.

Basically the whole /etc/ is mounted on /tmp and will get wiped out on every boot.

If you have any clue how to do this please let me know!
[Google Chromecast] CliveWRSA:
I had a poke around for stuff about your router. From what I can find, you are correct in that its not as simple as an rc script on boot. Looks like your only option is a custom modfs implementation, or going with DD-WRT. Which is pretty awesome anyways.

My router is only used as an ATM point for dialing internet from my linux server. So it was much simpler for me than doing stuff on the router.

Your only other option would be to get a little Mikrotik routerboard and set up some routing rules on that.

Good luck mate
[Google Chromecast] croques:
ping

the ping times just recorded for unlocator's dns is

15 packets transmitted, 15 received, 0% packet loss, time 14020ms
rtt min/avg/max/mdev = 158.718/166.061/177.317/5.924 ms

whilst Google's dns is

12 packets transmitted, 12 received, 0% packet loss, time 11017ms
rtt min/avg/max/mdev = 16.914/17.496/18.799/0.581 ms

I know unlocator is only a beta but those times are the pits.
[Google Chromecast] CliveWRSA:
You could try unotelly. I have been using them for a little under a year and never have I had an issue.

Its pretty much the same service anyways just an ip change for you iptables.

Unotelly have a free trial too.
[Google Chromecast] varun.c.jain:
Correct me if I am wrong, but that horrendous ping performance indicates that resolving your DNS queries is going to take some milliseconds more than it would normally have... in no way should that affect your actual content streaming speed... so I don't think you are at much of a loss, or are you?
[Google Chromecast] croques:
Yes, it's some loss to me. I have set up a Raspberry Pi as an ad-blocking wireless access point and added unlocator to that as the DNS service. So all my lookups go through that. Unlocator is simply not viable.
[Google Chromecast] ykphuah:
Sigh, I bought the asus router, without trying to figure out what REVISION it is, and later found out that its D1, and not supported by DD-WRT. :| Tried flashing the C1 DD-WRT but it couldn't work.
[Google Chromecast] CliveWRSA:
Ah man that sucks. Well a Mikrotik might be your best bet then. Their simplest basic little routerboard, the 260GS model is like $30 and will do your routing no problem.

I hope you come right mate.
[Google Chromecast] varun.c.jain:
Ahh interesting. From your given tutorial, I understand that the implementation redirects the querying browser to a locally configured Pixelserv webserver when trying to access a pre-defined ad-service URL. If the webserver has not been configured then the browser receives a 404 - Page not found code after an HTTP timeout. It is this timeout which takes time. The solution to speed this up, by avoiding a timeout, and returning a locally configured webpage running on the Pixelserv webserver has been mentioned in the "Improve Performance" section of the tutorial.

So basically you need to implement this webserver workaround and also define your /etc/resolv.conf as

nameserver 192.168.42.49
nameserver 50.112.186.233
nameserver 50.112.143.40
nameserver 8.8.8.8
nameserver 8.8.4.4

That way all ad-server requests will get resolved by your locally running DNS service on 192.168.42.49 and then display your locally configured webpage. Rest all requests will get resolved by the next DNS service in line, i.e. the Unlocator service.
[Google Chromecast] croques:
Yes, that's right. but read on and you'll see that 404s are wiped away by using Apache2 as a web server. All local redirects are given a 200 OK response by Apache.

Again, that's right and I did make just those changes to my resolv.conf.head file. But that meant all my dns lookups for anything other than blocked ads took forever via unlocator.

If anyone else is reading this and thinking of following the adafruit tutorial; it is heavily flawed, in that resolv.conf is overwritten by the system at various times. Thus the access point stops working, certainly after 24 hours. You will need to install openresolv and then configure a head and tail addition for resolv.conf that gets read in before the system rewrites resolv.conf.

Finally, remember ping times to an ip address are not dns-resolved. They just show the poor response from unlocator's dns server.
[Google Chromecast] CliveWRSA:
If you are using ext3 or higher then you can also run:

#chattr +i /etc/resolv.conf

once your resolv.conf is as you want it.

Stop the file from being overwritten by other processes.

Bit of a hack but so is getting netflix out of country anyways :p
[Google Chromecast] shijuvt:
Netflix not working on chromecast

I had earlier confirmed that the chromecast/netflix works outside USA, in Kuwait, but it seems that there are still some problems.

I can access Netflix on the ipad, and though it does act up some time, I am able to watch titles on the ipad (full season of house of cards!!:D)

However, when i try to cast it on the chromecast it does not work. It starts to buffer up to about 25% and then it says that the title is not availble right now, and to select a different title.

has any one experienced this.

any work arounds or fixes?
[Google Chromecast] varun.c.jain:
Recheck your iptables rules... most probably they got removed after a router reboot... I have to recreate the rules each time I power down/up my router cause I cannot find any apparent way to make them stick.
[Google Chromecast] PelegK:
Works like a charm, this has saved me 4$ a month !

Thanks alot !
[Google Chromecast] Rylo:
Hi guys, i already got unlocator running for a while on my router, fritzbox 7360. Last week i received my CC, but when i want to play a vid through netflix it doesn't play; 'Currently this video isn't available'.

Playing on my phone works fine, but whenever i press on cast, i get the above message. When i remove all the dns, it does play (but i dont have access to usa content :(.

Any idea's ? Is my CC still using google DNS servers even tho i got unlocator's DNS on my router ?

---------- Post added at 10:12 PM ---------- Previous post was at 10:10 PM ----------

Hi guys, i already got unlocator running for a while on my router, fritzbox 7360. Last week i received my CC, but when i want to play a vid through netflix it doesn't play; 'Currently this video isn't available'.

Playing on my phone works fine, but whenever i press on cast, i get the above message. When i remove all the dns, it does play (but i dont have access to usa content :(.

Any idea's ? Is my CC still using google DNS servers even tho i got unlocator's DNS on my router ?
[Google Chromecast] DJames1:
^ Exactly. The Chromecast is hard-coded to bypass the DNS in your router and go straight to Google DNS.
[Google Chromecast] ykphuah:
You need to find a way to run the two iptables command line.
[Google Chromecast] TheMorpheus:
Thanks for this, I've been enjoying the first month of free Netflix

I have just a question: is it necessary set the DNS in the router settings and set the iptables at the same time? In other words, isn't it enough just redirect the Google DNS to the Unlocator ones?
[Google Chromecast] ykphuah:
If you are talking about ONLY doing the iptables command, then your other devices might not use Google's DNS as the DNS server (it depends on the settings in your router), and hence they won't get redirected. :)

If the DNS server is configured to Google's DNS, then yeah, I guess it can work with only the iptables command.
[Google Chromecast] TheMorpheus:
Yes, or you can manually set the Unlocator DNS only on the devices where you need it!!

I'll give a try, thanks!
[Google Chromecast] Shammyh:
Great idea overall!

Only one small note... Referral links are generally frowned upon on XDA. Especially when you include them silently. I even used yours to sign-up, so you get $5, but really, please edit it out.

Thanks otherwise though!
[Google Chromecast] varun.c.jain:
You're welcome... I didn't know about any such rule though... will look it up, and if there is indeed any such thing I'll remove the referral link... btw, the service is in a beta, and there is nothing I am earning out of it... Unlocator isn't charging me anything yet, nor users of my referral link, and neither are they paying me anything... in all probabilities even when they start charging for their service, they won't pay me any referral bonus unless I myself subscribe for their paid service... so to sum it up, my intention to put the link was more of a personal experiment to see how many people use my suggestion from XDA, this being my first (hopefully) useful thread...
[Google Chromecast] maarawoe:
Not necessarily... I made a firewall/nat rule to route all the traffic to Google dns for selected ip to be forwarded to unlockator... The hardcoded dns can lick my b*lls as the router redirects the traffic ;)

Odesláno z mého HTC One pomocí Tapatalk
[Google Chromecast] TheMorpheus:
How did you do it? I have an Asus DSL-N55U, but every time that I reboot the router I need to re-set the iptables... I would like to make a rule just for Chromecast
[Google Chromecast] maarawoe:
Yes - I also wanted to make the rule only for my laptop and the chromecast. It was quite simple for me as I have a Mikrotik rb433 router what is kind of a ISP grade device so such rules are easy to make... No idea if such rule is possible on Asus... Maybe you should try something like dd-wrt firmware or try to do a rc.d command in the router to make the iptables rule after each reboot but I am not familiar with asus routers - I had last one 5 years ago without any need for such advanced config.
[Google Chromecast] Rylo:
I can't configure it on my fritzbox 7360 :(. Have to flash a custom firmware freetz, but then i have so much to read into on how to compile my own firmware >_< aargh!
[Google Chromecast] jasenko:
Just wanted to thank you for this method, no other rules I tried worked for Google Play videos. Netflix and July perfect.
[Google Chromecast] dorgold:
Had someone been able to get this method to work with the new Pandora app?
[Google Chromecast] TheMorpheus:
No, I get this: http://goo.gl/oD6qfL
[Google Chromecast] varun.c.jain:
Same here. For one Unlocator don't have Pandora shown as compatible with Chromecast on their Compatibility page yet. Perhaps it will be on their to-do list. I wonder what the Chromecast Pandora app does differently here as compared to Chromecast Netflix/HuluPlus apps.
[Google Chromecast] TheMorpheus:
It has to be something on the Pandora app on Chromecast because with the Unlocator DNS I can stream Pandora on my tablet/phone/pc without problems!

Sent from my GT_N8000
[Google Chromecast] jasenko:
I am in Australia and Pandora works fine without iptables, mainly because it is locally available service. As soon as I use Unlocator iptables configuration, it "brain freezes".

Because it works just fine on Android, iPhone, PC, I will try to route it to my local DNS that is pre-configured for Unlocator anyway.
[Google Chromecast] jasenko:
Edited:

Didn't work :(
[Google Chromecast] sanpsa:
Maybe wrong place to ask but I got this trick to work with pc and chromecast, but it wont play in HD on either one? When using netflix with my own region it does work, so settings or speed is not the issue?
[Google Chromecast] eztechca:
Awesome post, I'm going to try this on my next trip to Asia.

Thanks for the guide.
[Google Chromecast] sixdaysandy:
If you're in the UK using Sky Broadband and have one of their routers (Sagem F@ST 2504 or 2504n, mine is the latter) I can confirm that this method works if you flash the custom firmware made available here (http://www.ph-mb.com/products/2504n-firmware)

You can skip the dnsmasq stage as that doesn't exist within the router, the commands can be executed via Sky Router Tool Lite -> Tools -> Execute Command.

Make sure you restart everything and it works a treat :D

Edit: maybe not a treat, have had to disconnect the chromecast from Netflix between movies, we'll see how annoying that becomes.
[Google Chromecast] The_Stranger:
Does anobody using this trick have any problems with the chromecast button not showing up in the netflix app on the (android) phone or tablet and/or the app losing connection while playing?

I do have this problem and it almost seems like it started when I updated my modem (netgear 3700) with dd-wrt and applied the work around mentioned in this topic.

casting from my desktop seems to work fine.
[Google Chromecast] ykphuah:
For netflix app, sometimes I need to reboot my chromecast, and when I do that, I loose the chromecast button.

So what I do is to play a video on my tablet, and then the chromecast button will come back out.
[Google Chromecast] billyelliott80:
Vpn

Without Vpn it can't be possible to do this..
[Google Chromecast] ssherlock:
I'm interested ion how you got the Chromecast to work at all with the DSL-N55U as it won't play with mine whatever I try...
[Google Chromecast] TheMorpheus:
Just enable the telnet in the settings of the router and follow the guide in the topic!
[Google Chromecast] zaqh:
I have found a solution that works for me, and I think it would do for everyone who uses private DNS servers as Unblock-Us or Unlocator. The only thing you need is a router capable of filtering outgoing connections, and every router I have seen can do this as part of the built-in firewall without need of flashing an alternate firmware that supports iptables (such as openwrt).

You only need to put two rules on your router firewall to block outgoing packets to Google DNS Servers (8.8.8.8 and 8.8.4.4) for TCP/UDP and port 53 (DNS). This way, Chromecast will get a timeout trying to reach Google DNS Servers and will fallback to your router defined DNS servers and your Netflix or Hulu will work again!