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
Related
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).
Hi,
So, since Chromecast updated to 16664 i have been unable to use it in conjunction with Unblock-Us VPN service. This is only the case when attempting to play through chromecast, all other devices work as expected. I have tried routing my primary AP router to Unblock-Us DNS servers and i have also set up a dd-wrt router as a repeater and applied all necessary measures to preroute chromecast dns requests or simply block its dns requests. None od this has worked unfortunately.
The build update for 16664 stated 'dns robustness' which i figure is why this has happened. Does anyone know what this mean? Perhaps, if we knew this info we could figure out a work around.
Usually robustness would mean some sort of protection for it... Like perhaps routing the DNS requests over some sort of secure tunnel/connection so they're invisible to any local DNS caching or rewriting... Someone with Wireshark should be able to see exactly what is (or isn't) happening quite easily though.
I know this won't be very helpful at all, but I got my Chromecast today and it works just fine with my unblock-us account. I have the unblock-us dns servers set in my router (using Tomato rather than dd-wrt) and I was able to switch regions seamlessly.
Sent from my HTC One_M8 using XDA Premium HD app
I checked this latest build to see if it is still necessary to block or redirect Google DNS lookups to use another DNS, and it is. No change there, at least from Canada (UK/Europe firmware may be different).
netflix was not working with build 16664, hulu plus is fine. i had to redirect google DNS to a non existent IP address to get netflix to work. now both are running fine. i'm using adfreetime DNS on my Linksys router.
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
Hi everybody,
Let's say I have 20 RPis each located in different cities. I want to be able to monitor them, transfer files to/from them, control them, etc. remotely and securely from my office.
I searched for possible solutions in the past few days, and found the following solutions:
1. Port Forwarding
2. VPN
3. Using some 3rd party websites like RealVNC, Remote3.it, TeamViewer, etc.
As I've understood, the port forwarding is the least secure solution in this list. Also, 3rd party websites have limits on the number of Pis you can access in free versions. Besides, they are not open source, so you cannot design your desired monitoring system/interface based on them. Hence, the VPN seems a better solution all in all.
As for the VPN, I searched the net a lot, but in most of the relevant tutorials, the RPi is the server, and the PC is the client. There's no problem in being so, until you have only 1 RPi to remotely access to.
Now here are my questions:
1. If I want to remotely access to 20 RPis in different locations and monitor them from 1 PC, what configuration shall I use !? 20 VPN servers + 1 client !? How is this possible !? Or shall I change the configuration to 1 server + 20 clients !? If so, how shall I do that !?
2. Are there any other methods for remote access to RPis securely from the office!? (else than those 3 ones listed above)?
Thanks.
RealVNC works pretty good, im using it on a couple of my Pi's running Raspbian Jessie to monitor cameras.
I'd prefer port forwarding with password-login disabled and only use key-based login. Then config all the Pi's in your ssh config file to login via ssh [email protected], ssh [email protected] and so on.
If port forwarding is a problem I fancy the solution of using autossh to connect all your Pi's to a central server. You can then use this central server as a reverse SSH proxy to connect to each Pi using ports local to the central server. This works even if you have no access to port forwarding and even if the IPs to the Pi's are changed.
Well look here! There's an existing thread covering this
https://forum.xda-developers.com/showthread.php?t=2195040
What about Teamviewer on RPI?
pages.teamviewer.com/published/raspberrypi