I use an old PC running pfsense as my router and getting this to work with unblockus is a snap.... less the 5 min (no VPN needed).
( Page I found this on )
For the unbehaving Chromecast, with its hard-coded Google DNS, we are forced to add a NAT rule to reroute all DNS requests.
In Firewall | NAT | Port Forward, add a new rule with these settings:
RDR: Unchecked
Interface: LAN
Protocol: UDP/TCP
Source: IP of your Chromecast
Source port: any
Destination: any
Destination port: DNS (53)
Redirect target IP: the DNS server of unblock-us or similar service
Redirect target port: DNS (53)
I like this as it does not make everything in the house use unblockus... just the chromecast.
pfsense is a free router software that is VERY easy to install and use. It will even run off a live cd or thumb drive. You can pretty much just install it and it will work like any router out of the box... no need to really do anything... but if you want to, you can do almost ANYTHING with it. Used it for many years now (running on a P3 with 256 Meg ram) and will never use a store bought device again.
Cool, think I will check this out later, thanks for the info
Sent from my Windows Phone 8X
using Tapatalk
You don't need to redirect the Dns. It was my initial plan also until I learned another way. All I did on my plain old nergear was I blocked googles Dns. The chromecast is then forced to use whatever the router gives it via Dns.
**edit** sorry didn't read properly, didn't see that you didn't want the other services in the house to use the unblock service via the router
Related
Has anyone found an easy work around for having different ip settings per wireless network? By default you can either have static or dhcp for all connections, you cant set this per ssid.
I found this but looks like it has just been sitting there since 2008
http://code.google.com/p/android/issues/detail?id=1215
I was thinking about starting to look at the system files to see if there was a way to edit the connections via a config file like a typical linux workstation, but not sure if the ssid and other wireless profile info is stored within android or in the system files...
basically I just want to set my own ip and dns server addresses when when I am connected to a particular ssid.
as a side note, xda search is terrible....it makes you wait 30 seconds between searches...
hmm, is it odd to have the below entries in the resolv.conf? or are the 8s used for something within android?
nameserver 8.8.8.8
nameserver 8.8.4.4
Is that Static Wifi app working for you?
I was looking for a similar solution but since I only had 1 problematic location just toggling the static IP setting on and off is taking care of my problem.
The static wifi app looks like you can do multiple locations and just select from a list.
hmm, wifi static looks promising, will try that out, from what i had read people thought it didnt set the settings based off of the access point, but it clearly has those settings...
disgustip8ted said:
hmm, is it odd to have the below entries in the resolv.conf? or are the 8s used for something within android?
nameserver 8.8.8.8
nameserver 8.8.4.4
Click to expand...
Click to collapse
Those are Google's OpenDNS servers. They're main nameservers for the internet.
haha yeah i just realized that like 15 minutes ago lol
I'm from Egypt and I got a chromecast for 30$ on amazon while I was in the US... It's not rootable also.
So I cannot stream Netflix or Hulu on it :crying::crying:
I tried this method and it doesn't work http://forum.xda-developers.com/showthread.php?t=2435579 .. any help please?
LegendJo said:
I'm from Egypt and I got a chromecast for 30$ on amazon while I was in the US... It's not rootable also.
So I cannot stream Netflix or Hulu on it :crying::crying:
I tried this method and it doesn't work http://forum.xda-developers.com/showthread.php?t=2435579 .. any help please?
Click to expand...
Click to collapse
Since your Chromecast is not rootable, if you cannot get one of the below to work
Use iptables to redirect Google DNS requests
Force Chromecast to use DHCP-supplied DNS by blocking its Google DNS requests
Force Chromecast to use DHCP-supplied DNS by rerouting its Google DNS requests
Have router forcibly handle external DNS requests
Have router log into VPN and route client traffic through VPN
Then you will only be able to access the services available in your (ISP's) country.
If your Chromecast isn't rooted, it all depends on your router.
There are 3 main methods:
The most widely-supported method is to get the Chromecast to fall back to DHCP by using the static-route-to-nowhere method, since almost all routers support setting up static routes. You can read about that method in the thread you referenced above.
A few routers let you block the Google DNS addresses specifically to make the Chromecast fall back to DHCP. That works just as well. But unfortunately most routers that follow the Linksys model of access restrictions can't block a specific IP address, even though it looks like it should be possible the way the interface is set up.
If you have a router running DD-WRT or other advanced Linux-based firmware, you can use the iptables command to redirect the Google DNS addresses to the DNS addresses of your choice, as in the link you referenced.
Hello
I have a App which is blocked by my ISP
When I install a VPN the app works PERFECTLY on my PHONE , however CC does not work, (im guessing its because the VPN chnages my IP so cc cant recognise it )
What can I do?
Is there a way to modify the VPN so e.g it makes THAT SPECIFIC APP use e.g US IP BUT EVERYTHING ELSE is normal ??? or am I lost in la la land??
Thank You very much! Would SOO Appreciate it and give a small reward if someone could find a way to solve this puzzle
I don't think that VPN will work with an unrooted CC. And even with a rooted its not really possible I guess.
The people here are using special DNS Services combined with some magic stuff inside their routers (redirecting Google DNS for Chromecast to another DNS which unblocks Netflix for example in Germany).
People do make this work, but it can be a bit tricky, and you might find it beyond your technical ability if you are not very experienced with routers and networking.
The Chromecast and the app casting to it have to be on the same local network so that the app can see the Chromecast. An app using a VPN when the Chromecast is not will put them on two different networks, and the app won't see the Chromecast. If you are going to use the VPN, then it has to apply to both of them. Since the Chromecast has no support for VPNs, you have to set up the VPN in your router. Not every router can do that - typically only routers with optional firmware like DD-WRT. If you have this support in your router, you'll need to look up the instructions in your router's documentation.
If your goal is to get around geoblocking, then other alternative is to use a DNS proxy service instead of a VPN. This can also be a bit tricky with the Chromecast. Since it doesn't allow manual DNS settings in the device, you have to do it using your router. It's even worse with North American models because they are set to use Google DNS by default, so you have to block or redirect Google DNS to force it to use your DNS settings (apparently this does not apply to the just-released European firmware). The details of this method are given in other threads here, so I won't repeat them. You'll need to subscribe to a DNS proxy service (not the same as a VPN, although many VPN companies also offer a DNS proxy service).
Dear community,
I have just setup a raspberry PI as a WIFI Router and connected the chromecast to the cretaed network. Unfortunately i had to realize that it will work
only with an active internet connection. I'm running a Plex server on the raspberry and my intention is to use the PI in combination with the Chromecast while traveling. Especially when there is no intenet available. Given the fact that the chromecast firmware is on the most current level a root is not going to work. I have found a very interesting article explaining the basics of the rCast mod and wondering whether it would be possible to simulate a working internet connection on the raspberry.
– CAST_SHELL AND NET_MGR MAKES HTTP REQUESTS TO GOOGLE SERVERS. I HAVE PATCHED THOSE BINARIES SO THEY MAKE REQUESTS TO THE LOCAL WEB SERVER INSTEAD.
– THE DEVICE MAKE A DNS LOOKUP SENT TO SERVER 8.8.8.8. I HAVE WORKED AROUND THAT BY CREATING AN ALIAS FOR 8.8.8.8 ON THE LOCAL HOST AND RUN A DNS SERVER.
– THE DEVICE WILL NOT FINISH BOOTING UNTIL IT HAS RECEIVED AN UPDATED TIME FROM POOL.NTP.ORG. THIS IS FIXED BY ADDING POOL.NTP.ORG AS 127.0.0.1 IN THE HOSTS FILE, AND LOCALLY RUNNING A SNTP SERVER.
THOSE WORKAROUNDS WILL LET THE DEVICE START UP NORMALLY EVEN WHEN NETWORK IS MISSING.
Does anyone have already experience in this kind of work or could help me to figure if this could work.
Many Thanks
HubbyHub
Is it possible to change the DNS server to such as nord dns to bypass region blocks? I see I can load a vpn to it easily but finding the right server is kinda annoying every time. So it's either this or buy a dedicated vpn up from nord.
does It not take the default from your dhcp server?
Go into network settings, choose static and configure everything there
xqz said:
Go into network settings, choose static and configure everything there
Click to expand...
Click to collapse
In spite of using static ip and setting up DNS numbers provided by my smartdns provider content is not getting unlocked. I think Chromecast is still bypassing the given DNS servers and reaching across to google DNS servers.
Google has been getting pretty overbearing when it comes to DNS lately. They're really pushing for DNS to be served over HTTPS, which makes sense from a "bypass port 53 redirects" perspective, but is terrible from a privacy and control-your-own-destiny perspective, since it basically allows the DNS to be addressed at the application level rather than the system level.
Not that this couldn't be done before, just that its now becoming mainstream, which is nasty.
So basically, what it is going to take to make it *better*, but not perfect, is to implement some fun stuff at the level of your ROUTER;
1) Block port 443 to all known DNS-over-HTTPS public servers; https://en.wikipedia.org/wiki/Public_recursive_name_server
2) Filter and redirect all requests to public servers on port 53 to DNS server of your choice.
Definitely not perfect, because nothing will stop an application from going to an unknown DNS-over-HTTPS server on the public internet.