yashsingh1/xdaforums huggingface dataset:
[Google Chromecast] DJames1:
I assume that your LAN address range is set to 192.168.0.xxx with a subnet mask of 255.255.255.0 ? Because if it isn't, then you would need to change the suggested non-existent gateway address of 192.168.0.99 to something that is in your LAN address range.

If your model of D-Link router is for reason testing that the gateway exists when you set up the route, you could always try fooling it. Set one of your computers or devices to that static IP address (i.e., 192.168.0.99 or whatever you decide to use), create and save the route, and then set that device or computer back to its normal IP address. All you want here is that when the Chromecast attempts to use that route to Google DNS, the router returns "Destination unreachable".
[Google Chromecast] lordnotan:
Tried change the metric to two, same thing. I noticed I had the ranges 100 to 199, tried several but still same error message...

I stumbled across another setting which would deny any device connected to the network by it's MAC address. Do you think I would be able to cast to the CC from my Nexus 7/PC over my local WLAN or would it just result in me not being able to access the CC at all?
[Google Chromecast] bhiga:
Flat out denial won't work in the case of Chromecast - it won't be able to check the Google whitelist and will say it has no Internet.

Sent from a device with no keyboard. Please forgive typos, they may not be my own.
[Google Chromecast] lordnotan:
Looks like I'm gonna get a new router then, I don't feel like spending any more time on trying to fix this one.

Thanks for all the help anyways!
[Google Chromecast] Matthew Carson:
No longer working

Is anyone else having trouble with this solution with 15250?

I had it setup so that my router just blocked requests to port 51 specifically from my Chromecast IP address (forcing it to unlocator's DNS setup in my router), and this was working great.

However, since CC updated to 15250 whenever I try to go into the Netflix app it will sit there for a couple of minutes and then come back and say "Cannot connect at this time. The Netflix app will close."

So I changed my setup to simply redirect the requests to an invalid gateway instead. Now it will load the Netflix app - but whenever I go to watch something, it gets to about 25% loaded and says "We are unable to access this title at this time."

I can play it fine on my other devices on the network through Unlocator. The strange thing is it was not working, then it worked one time (with the blocked ports) and now I can't get it to work again. Very frustrating.

Has anyone else seen problems with the 15250 build? If it's just me something else must be up, although I'm not sure what it could be...
[Google Chromecast] bhiga:
If you didn't set a DHCP reservation in your router, Chromecast might have received a new IP address after the upgrade.
[Google Chromecast] Matthew Carson:
It does have a reserved address.
[Google Chromecast] DJames1:
I think I've only tried it once with Netflix since my Chromecast got the latest update, using the static-route-to-nowhere method to block Google DNS, and it did not work the first time I tried. As far as I recall, Netflix on my iPod was unable to connect to the Chromecast. I just reset everything and tried again, and it was fine the 2nd time. Maybe the Chromecast was still updating (although it looked ready on the screen), or it needed to reboot, or some other unknown temporary glitch. I haven't tried it again since, but I will.
[Google Chromecast] amst3l:
Is it possible to only have the Chromecast's IP run trough an VPN so the other PC's in the network aren't affected?
[Google Chromecast] DJames1:
In theory yes, but in practice that would be difficult. It would depend on having a very advanced VPN configuration capability in your router, and most routers don't have that. I would think it would be easier to have a 2nd router with a VPN dedicated to the Chromecast and any portable devices controlling it. I've done it that way.

Of course if you use a DNS service instead of a VPN, the problem is easier since you only have to deal with the Google DNS addresses.
[Google Chromecast] bhiga:
Also, if you only have Chromecast on the VPN, how would the controlling devices see it?

For everything to work right, both Chromecast and the controlling/requesting device need to be using the same DNS. Otherwise Chromecast might receive a request for, say a UK server, and not be able to reach it because it's connected to a US server.
[Google Chromecast] eruur:
Hello everyone,

Your help would be really appreciated, because I have some trouble making my chromecast work with Netflix in France.

The hardware I use is a Linksys WRT54G router with DD-WRT firmware on it. This router is connected to an xDSL modem by ethernet.

I have followed all the steps of the guide for dd-wrt firmware, but my chromecast (neither my phone) can connect to netflix.

The routing table given by the router is the following:

Chain PREROUTING (policy ACCEPT)

target prot opt source destination

DNAT icmp -- anywhere 0.0.0.0 to:192.168.1.129 (ndlr: static ip of the router, modem is 192.168.1.1)

DNAT 0 -- anywhere 8.8.8.8 to:185.37.37.37

DNAT 0 -- anywhere 8.8.4.4 to:185.37.37.185

Any idea why it's not working ?

Thanks in advance for your help.

Regards
[Google Chromecast] bhiga:
Do other Chromecast-enabled apps still work?
[Google Chromecast] eruur:
Thank you for your reply. Yes they do. The Chromecast is able to connect to the network without any issue!

But even when I put on my android the DNS 8.8.8.8 and 8.8.4.4 and connect through wifi, the netflix app doesn't work.

So my guess would be that the routing isn't working as it should.
[Google Chromecast] bhiga:
Simple test - change your routing rules to redirect to a non-existent DNS server. If everything Chromecast stops working, then the redirection is working. If Chromecast continues to function normally, your redirection is not working.
[Google Chromecast] DJames1:
Obviously your Android device must use the same DNS addresses that the Chromecast is using, in your case 185.37.37.37 and .185. Are you assuming that by entering the Google DNS addresses in your Android device, the router will redirect lookups the same way that it does for the Chromecast? That should work, but just to be sure, try entering 185.37.37.37 and .185 directly in the DNS fields on your Android device.
[Google Chromecast] eruur:
That is exactly my thought. However, when I enter the 185.37.37.37 and .185 on my android device, the netflix app works just fine. Moreover it doesn't work if I just leave the 8.8.8.8 and 8.8.4.4 configuration (default one). That is why I suspect the redirection of the router is faulty. I just don't understand why :/

---------- Post added at 12:36 AM ---------- Previous post was at 12:27 AM ----------

I have tried the good idea you suggested. The chromecast continued working, so the redirection is obviously not working.

Do you think it has to do with the router to be in access point bridged mode ? I'm lost :/
[Google Chromecast] bhiga:
I could be wrong here, but as I understand it, the iptables filtering happens as part of the LAN-WAN processing, essentially in the NAT stage.

Thus, in order for a device's traffic to be filtered, it needs to be using the DD-WRT router as a gateway, and the packets must pass between the DD-WRT LAN and WAN side.

If you're using DD-WRT in bridged mode I don't think the iptables rules will apply since the packets will just be passed from the wireless interface to the interface it's bridged to. No LAN-WAN process happens.
[Google Chromecast] daleski75:
Got it working in the UK on my TP-Link WDR-3600 by modifying the rules set out a while ago in this thread.

Advanced Routing

8.8.8.8 -> 255.255.255.255 -> 192.168.1.90

8.8.4.4 -> 255.255.255.255 -> 192.168.1.91

When I set it to the below I would lose internet connectivity, no pings, no nslookups, no tracerts even with a valid WAN/LAN ip address

8.8.8.0 -> 255.255.255.0 -> 192.168.1.90

8.8.4.0 -> 255.255.255.0 -> 192.168.1.91
[Google Chromecast] Shrilaraune:
Time out option help

My router does not support the DD-WRT firmware; so, as others on this thread have done, I tried forcing the CC to time out when attempting to contact Google DNS by adding static routes (see screenshot). I've configured my computer and my router to use unlocker beta as well, but my CC continues to give me the loading screen. Help?

I have pinged both 8.8.8.8 and 8.8.4.4 and the "destination host is unavailable" so it seems like the routing is working. I've tried with "Lan/br0" as the interface and with no indicated interface (as in image) as well. I can cast my chrome tabs--and I haven't tried Youtube, but I suspect all non geo-specific sites work (using my PC not my phone/tablet). Netflix is the only issue, as far as I can tell.

Thanks in advance
[Google Chromecast] DJames1:
Did you try clearing the DNS cache on your computer and your router? Often when you have been experimenting there is a cached lookup stuck somewhere, and neither the computer nor the router automatically flushes the cache when you change DNS. If I'm having that problem I just launch a CMD window in Windows and enter "ipconfig /flushdns", and then reset or unplug/replug the router as the easiest way to force it to flush.

I can confirm that U.S. Netflix on the Chromecast is still working fine with the current Unlocator DNS addresses. I use the static-route-to-nowhere method in my Linksys router to disable Google DNS.
[Google Chromecast] Shrilaraune:
Thanks for the quick reply! I tried flushing the DNS and instead something really peculiar happened. First off, Netflix still isn't working so I'm still looking for solutions there. Secondly, the router interface authentication pop up keeps...well...popping up (see screenshot). And it's not clear whether my username/password combo is working though I still have access to the firewall options. It's like it keeps refreshing or keeps timing out. Weirder still, when I disconnected the router and plugged it back in (after the DNS flush), the status lights didn't blink on. I still had internet access, but then I realized a moment later that I still had access even when the AC adapter wasn't plugged in.

O_o
[Google Chromecast] bhiga:
The fact that Internet works without the router plugged in means your router supports PoE (highly unlikely), you're on a device that has a mobile WAN connection, or your wireless devices are not connecting to what you think they are. The latter is likely the case, and would explain why your routing rules aren't working because the traffic isn't going through the filtering router.

Try a traceroute (tracert in Windows) to see what the traffic path is.

Many cable/DSL modems now have built-in wireless APs, so you might be connected to that?
[Google Chromecast] Shrilaraune:
Thanks for getting back to me. So this may have been worth mentioning, but I'm in a multi-flat/dorm like situation, so I don't actually have direct access to the modem. I'm not sure if it has a built in wireless AP, I just know that I'm still connected to the same network (according to the access window) I always have been. My laptop doesn't have a mobile WAN connection (if only) either. So what should I do if my router supports PoE? I ran a tracert, but wasn't sure if I should run my ip address or a random website (I'm sort of new to networking so, forgive my ignorance here). I tried both (see screenshot). Anything suggest I'm connecting to something other than my router? If it helps all the devices in my flat are still connected to the same network they always have been.
[Google Chromecast] bhiga:
The PoE (Power over Ethernet) comment was a bit tongue-in-cheek, though if the router lights stay on even after unplugging the AC adapter, then it actually might... Highly unlikely though...

Looks like 10.0.0.138 is whatever router you're connected to. It's possible there is a building or campus wireless that you're connected to. Is there no passphrase or key required to connect? Usually you'd know whose wireless it is based on who/where you got the key.

Most likely your router does not default to a 10.x.x.x address, so I do not think you're actually connecting to your router's wireless. Or your wireless "fell back" to the campus wireless when you unplugged your router.

So...

Plug in your router.

Plug an ethernet cable from your laptop to your router.

Disable your laptop's wireless connection.

Set up your routing rules, test them, and get them working

Re-enable your laptop's wireless connection

Disconnect the ethernet cable

Make sure your laptop is connected to your router's wireless. Your laptop's IP address should be in the same range as your router - for example, if your router's web interface address is 192.168.1.1, your laptop should have an IP that is 192.168.1.x like 192.168.1.31

If your laptop is getting a different IP address, go into the Wireless Networks setting and change the priority so your router's SSID is at the top of the list.

Check if things work now. If not, factory-reset Chromecast and make sure it's using your router's SSID.
[Google Chromecast] TripleJumper87:
I've got a strange problem.

I used the static-route-to-nowhere-method to redirect the Google-DNS-Servers to a non-existing gateway.

Everything works fine. I can cast Youtube, Netflix etc. but for some reason I'm no longer able to connect to Google Play Music.

Chromecast always shows an error: "Oops, shouldn't be here!"

When I delete the static-routes I'm able to cast Play Music again.

Any ideas?
[Google Chromecast] bhiga:
Check subnet masks to make sure only the Google DNS servers are being rerouted and you aren't catching other Google servers in the rule.

I'm not sure what server Google Play Music uses.
[Google Chromecast] Shrilaraune:
Thank you! Unfortunately I don't have an Ethernet cable in the country (never thought I'd need one) and all the stores are closed until tomorrow. I'll give this a try and let you know how it goes.

As for your questions, the passcode is a private one I received upon calling the provider and is distinct from the campus wireless. I'm not sure if this helps (again forgive my ignorance) but my router is connected to an ADSL split line. My internet access is still stable, although I've been connecting and disconnecting the AC adapter so I agree I must be connecting to something else. I just don't know what or why it has the same name and passcode as my router--a router I had just reconfigured (with provider assistance) after an accidental factory reset a few days ago (d-link routers are a little annoying).
[Google Chromecast] Carnelain:
I'm running OpenWrt on a WRT54GL and I can't get this to work. I can browse the us content and play them on my laptop and phone but I get an error when streaming to chromecast. I guess the dns redirect isn't working.

The iptables rules are added but do not work. And after a reboot they dissappear. I tried installing iptables-utils to use iptables-save to no avail. It might be necessary to alter /etc/config/firewall but I haven't got a clue how to translate the iptables commands.

Any clues?
[Google Chromecast] DJames1:
Clearly not. :)
[Google Chromecast] DJames1:
The Unlocator beta test is coming to an end shortly. They promise a special promotional offer for the first week as a paid service (TBA). Here's the email:

"UNLOCATOR

Important - Update Your DNS Now!

We have recently updated the Unlocator infrastructure in order to provide a faster and more robust service supporting more sites and devices. If you have not already done so, please update to our new and final DNS servers as soon as possible:

185.37.37.37 and 185.37.37.185

Click here to go to the set up guides

The old DNS servers will be shut down over time so now is the time to update. The new DNS IPs will remain unchanged in the future. Read more about the update here.

Tell Your Friends

Please tell your friends that the Unlocator BETA is soon coming to an end (most likely in a couple of weeks). If they want to be part of the BETA, they need to get on board now. Share on Facebook and Share on Twitter

Once we leave the BETA, all users will have their BETA account transformed into a free 7-day trial. From then on, you can upgrade to the paid version, which will be $4.95/month. However, we are going to run a special offer for the first week of the live service. More about that in a later mail.

Please note that you will not be charged anything unless you choose to upgrade – the Unlocator BETA is still free and no credit card info is needed to create a trial account.

More Sites

Besides making Unlocator faster and more reliable, we have also added more sites to our service. Among others are HBO Go, Crunchyroll, ITV, 4oD, Demand 5 and many more - please see our redesigned channels page. We will continue to add additional sites in the coming weeks and after the launch of the service. See all supported channels and devices.

Updated Terms of Use

We have updated our terms of use to include a Danish translation. Among other things we have also added a 14-day money back guaranty for paid subscriptions once we go live. We have also changed the affiliate commission from a fixed commission to a 100% commission of the users first monthly payment. See the updated terms here.

We are Here to Help

If you need help with anything simply send a mail to support@unlocator.com and we will help you out as quick as possible.

https://support.unlocator.com

https://facebook.com/unlocator

https://twitter.com/unlocator

https://unlocator.com/blog

--

Best Regards

The team at Unlocator"

Coincidentally another popular free DNS service Tunlr.net has just shut down permanently after abandoning their plans to go commercial. There are several other options at the $5/month price level that Unlocator plans. There are also a few other cheaper alternatives (a $20/year offer on Reddit for usaccess, and a $2/month price for AdFreeTime).
[Google Chromecast] scandalousk:
Thanks for the heads up!
[Google Chromecast] burnski:
I live in Canada and have the Canadian Netflix (which sucks compared to the US Netflix). My router is a Asus RT-AC68U which firmware is (apparently) based on DD-WRT. Anyone know if I can setup my router's stock firmware to access the US Netflix?
[Google Chromecast] owensheehan:
US Netflix on Chromeast Ireland

Not sure if anyone has already posted something like this. I found this on the Unblock US support site, it worked for me to get Netflix US and Hulu plus to work here in Ireland.

"JESSE FEB 28, 2014 09:09PM EST

Hi

I was able to get the Chromecast to work in Canada, not using/switching to a DD WRT router.

I blocked access to 8.8.8.8 and 8.8.4.4 in my access control.

Simple and effective. I have tried it with different Netflix regions successfully.

Here are the settings:

(see attachment)

Enjoy!"

"Just to be sure, I added the Chromecast MAC address first, then blocked the IPs"
[Google Chromecast] navahoo:
For those - like me - unsure where to find the correct settings in the FB UI, this might help!
[Google Chromecast] muks1224:
IP

Hi zaqh ,

iam a newbi.just bought a Chromecast iam outside (us)trying to cast Netflix stuck in first screen.iam using Linksys router with DDWRT,i have an 8mps connect.Saw your post ,not very tech savy, can you tell me exactly how to create rules inFirewall to block outgoing DNS of Google.Using unlocator with the ne DNS.

Regards
[Google Chromecast] Shrilaraune:
No dice

So I followed all of your directions and still no luck. My router is still defaulting to 10.x.x.x and my computer's ip is falling within that range. I set up my routing rules again and pinged both coming up with "unreachable" each time. I made sure chromecast was using my router's SSID by re-configuring the router, granting it a new name and connecting CC to that network (after confirming I was re-configuring the correct network, of course). Still nothing. I'm not sure if there is some greater framework on this campus I am not accounting for but I know for certain all my recent work thus far has been on my flat's router.

Any ideas?
[Google Chromecast] bhiga:
First thing would be to circle back around and set your laptop to default DNS (no Unlocator/etc) and see if you can cast something from YouTube. That will confirm Internet connectivity for both Chromecast and your laptop, as well as connectivity between Chromecast and your laptop (meaning they're on the same subnet or otherwise routable).

Once that's confirmed, then it might be a matter of how your router is responding to the requests to Google DNS.

http://xdaforums.com/showthread.php?p=49365627

IIRC you want a timeout situation, rather than an immediate rejection (no route to host, etc)
[Google Chromecast] Shrilaraune:
bhiga, I think you might be correct and I think that the problem might stem from this 10.x.x.x nonsense. It really looks like no proper address I've ever seen and I have used the static route to nowhere testing different valid ip addresses within my router's supposed range. Unfortunately, I know that I am both utilizing the proper network and than I have not fallen back to my campus's wireless.So if, as I suspect, my router's true address is something else, where would I find it so that I can route the requests to Google DNS properly? Running ipconfig, my computer is still within the 10.x.x.x. range.

I tested youtube, without unlocator, and it works perfectly.

Thanks
[Google Chromecast] bhiga:
10.x.x.x is a Class A private address, so it's not technically wrong or anything, just unusual to see as most routers use the 192.168.x.x range.

http://en.wikipedia.org/wiki/Private_network

Is the router a D-Link DSL-2760U ?

I'm poking around the manual and the default IP range is usually 192.168.x.x but being that it's an ADSL modem+router, ISPs sometimes have custom firmware or configurations pushed to them.

Seems to be quite the full-featured router/modem combo.

Looks like a lot of possibility to disable NAT in the WAN configuration too.

On the plus side, looks like its IP Filtering lets you specify source address as well as port, so you could try blocking the Google DNS servers to see if it gives you a different result.
[Google Chromecast] wptski:
The 10.x.x.x is what a Comcast setup uses or at least that's what my nephew has.
[Google Chromecast] Shrilaraune:
Ahh, that does make sense. And yes you're right! I'm working with a DSL-2760U (Wireless N--whatever that means). I also get the feeling you're right about my ISP having some custom configurations in the mix.

So while I do have quite a few ip addresses granted by my ISP, I'm still a little leery of disabling NAT without further direction. I feel I'm almost sure to do some harm

At the risk of sounding even more woefully ignorant than I do:

(Academic Question) What exactly is the difference between routing dns requests to nowhere and blocking (the requests to the servers? The servers themselves?)

What would the ping results look like?

How would I go about blocking?

Ah, thanks for the clarification!
[Google Chromecast] DJames1:
Blocking returns no response, so the request times out.

Routing to nowhere returns a response from the router: "Destination unreachable"

You can see this when you ping the IP address in question from your computer.

The Chromecast falls back to using the DHCP DNS addresses in either case if it fails to access the Google DNS.
[Google Chromecast] bhiga:
Oh, you definitely want NAT enabled... Just looked like there were lots of potential places where it could get disabled, which would then give your devices addresses (mostly) outside of your router's control.
[Google Chromecast] scandalousk:
So how does this work? Add the chromecast mac address to be blocked. Then add the google dns ips to be blocked. And afterwards I enter the unlocator dns ips into my router. Is that the way to go or am i missing something?

EDIT: Nvm. This is useless to me since I can't block ip adresses on my router (Netgear r6300). I really wish there was a different way to go about this. I'm not liking the DD-WRT firmware since wifi is much slower on it then when I use the stock router firmware.