Database Develop

802.1x

Why Google you no like college students?

Hmmm this probably raises a good point, it's a bit hard to implement something like 802.1x though on a streamer device (where authentication is required per login of network prior to you having the ability to control the device).
I don't see this coming for awhile to be honest unless someone manages to hack it in - I just can't see Google releasing the ability to cache 802.1x network credential sets unfortunately due to the security implications.

Friend of mine had to buy his own router to plug in to the colleges ethernet ports in the dorm. Solved a variety of issues they were having.
Sent from my Nexus 5 using Tapatalk

fchowd0696 said:
Why Google you no like college students?
Click to expand...
Click to collapse
Beyond the lack of keyboard/interface, large networks in general fear multicast and UPnP because they have potential to easily clog the network.
Also remember that Chromecast in its current state has little security - it's designed for use within a trusted environment.
You probably don't want to be in the middle of Twilight with your girlfriend and suddenly your Chromecast switches over to SpongeBob SquarePants because someone else in the dorm decided BobsChromecast obviously wants to show SpongeBob...
Having your own router and local network will isolate your Chromecast to just your little piece of the campus network, though double-NAT might be an issue, and you should check with campus policy on use of personal WiFi router/AP hardware.

I've got a similar problem. I use a studentnet, were I can either plug in directly into the wall and log in once every day or setup a router with a PPTP-connection to automatically log into the student-network. I've got the latter set up and it works like a charm.
Thankfully I had a rootable CC so I could set it to use my ISP's DNS but I would love if it if I were able to use a different DNS (aka Unlocator/Unblock) to enjoy the US-version of Netflix, but every time I change the DNS-servers my internetconnection dies.
Is there any way to actually do fix my problem? I know this is more of a network-question than a CC-one, but CC is included in the problem
I use a Netgear WNR3500LV2 as my router.
Sent from my LG-D802 using Tapatalk

ninepoint said:
I've got a similar problem. I use a studentnet, were I can either plug in directly into the wall and log in once every day or setup a router with a PPTP-connection to automatically log into the student-network. I've got the latter set up and it works like a charm.
Thankfully I had a rootable CC so I could set it to use my ISP's DNS but I would love if it if I were able to use a different DNS (aka Unlocator/Unblock) to enjoy the US-version of Netflix, but every time I change the DNS-servers my internetconnection dies.
Is there any way to actually do fix my problem? I know this is more of a network-question than a CC-one, but CC is included in the problem
I use a Netgear WNR3500LV2 as my router.
Click to expand...
Click to collapse
First question is whether you can use a different DNS at all (or whether your ISP is blocking somehow).
Try doing a DNS lookup from another server on your phone/tablet via Ping & DNS or another app that lets you do that.
If that's successful, then it might work - go to the Eureka-ROM web panel at http://Chromecast_IP_addresss/ and turn off DHCP-supplied DNS, Apply, then select another DNS.
You will also need to force your phone/tablet to use the same DNS - otherwise your phone/tablet may be making requests from Mars, while Chromecast tries to retrieve stuff from Venus.

Can't connect Chromecast to Netflix

I took delivery if a Chromecast today and the setup is a breeze. As I'm in Europe I have changed some settings in order to access the American version of Netflix because if the extended selection of films and series. It runs fine on my Galaxy Note 8, iMac, and Xperia Z1. But it can't run on my TV. Every time I try to cast a film on it I get this error: "Whoops, something went wrong...Device Messaging Error. There was an unrecoverable error on your computer. Please reload the page to resume controlling your device."
I have done some searches and found various possible solutions, but none worked. This is what I've tried:
- Signed out of all devices in Netflix.
- Reset the Chromecast.
- Disabled WWM on the router.
I doubt it's an issue with Netflix as it works fine on all devices except on the TV. Sometimes I do see there is an error on my iMac saying that Microsoft Silverlight has crashed but that doesn't seem to affect anything. Is there anything else I could do to troubleshoot?

slonn said:
I took delivery if a Chromecast today and the setup is a breeze. As I'm in Europe I have changed some settings in order to access the American version of Netflix because if the extended selection of films and series. It runs fine on my Galaxy Note 8, iMac, and Xperia Z1. But it can't run on my TV. Every time I try to cast a film on it I get this error: "Whoops, something went wrong...Device Messaging Error. There was an unrecoverable error on your computer. Please reload the page to resume controlling your device."
Click to expand...
Click to collapse
Please tell us...
What make/model router do you have?
Can you describe how you "changed some settings" to access US Netflix?
Do YouTube and other services work?
If you use your normal DNS settings and access your local Netflix, does it work okay?
Chromecast is its own device and does its own DNS lookups and Internet requests after receiving the "go play this video" request, so if you're redirecting DNS on specific IPs/devices (rather than everything on your network), then you need to be sure the Chromecast IP/device is being redirected.
Otherwise your phone/tablet/computer is in Mens and Chromecast is in the Ladies and...
Phone/tablet/computer: "Excuse me, could you get my phone next to the urinal?"
Chromecast: "What's a urinal??"

bhiga said:
Please tell us...
What make/model router do you have?
Can you describe how you "changed some settings" to access US Netflix?
Do YouTube and other services work?
If you use your normal DNS settings and access your local Netflix, does it work okay?
Chromecast is its own device and does its own DNS lookups and Internet requests after receiving the "go play this video" request, so if you're redirecting DNS on specific IPs/devices (rather than everything on your network), then you need to be sure the Chromecast IP/device is being redirected.
Otherwise your phone/tablet/computer is in Mens and Chromecast is in the Ladies and...
Phone/tablet/computer: "Excuse me, could you get my phone next to the urinal?"
Chromecast: "What's a urinal??"
Click to expand...
Click to collapse
Thanks for your reply.
The router is a Cisco EPC3925.
I used the instructions from the Unblock-us website. Changed the DNS settings to 208.122.23.23 and 208.122.23.22 as instructed. But I also changed the DNS settings to that on the Cisco router - otherwise the US material would not show on my tablet and phone (only on the iMac).
YouTube and Plex work just fine when casting material to the TV.
When using the normal DNS settings from the local Netflix it works fine.

slonn said:
Thanks for your reply.
The router is a Cisco EPC3925.
I used the instructions from the Unblock-us website. Changed the DNS settings to 208.122.23.23 and 208.122.23.22 as instructed. But I also changed the DNS settings to that on the Cisco router - otherwise the US material would not show on my tablet and phone (only on the iMac).
YouTube and Plex work just fine when casting material to the TV.
When using the normal DNS settings from the local Netflix it works fine.
Click to expand...
Click to collapse
Netflix and hulu etc are having issues this morning if you are on a Uverse, if your redirect is a uverse one that may be the issue as well

slonn said:
Thanks for your reply.
The router is a Cisco EPC3925.
I used the instructions from the Unblock-us website. Changed the DNS settings to 208.122.23.23 and 208.122.23.22 as instructed. But I also changed the DNS settings to that on the Cisco router - otherwise the US material would not show on my tablet and phone (only on the iMac).
YouTube and Plex work just fine when casting material to the TV.
When using the normal DNS settings from the local Netflix it works fine.
Click to expand...
Click to collapse
Thanks for the info.
Seems like your core problem is that by default Chromecast uses the Google DNS servers regardless of what DHCP provides, so even though you've set your router so all its DHCP clients are being told to use the Unblock-us DNS, Chromecast still isn't. So all your devices are in the Mens, with the exception of Chromecast, which still goes to the Ladies, even though you tell it go to the Mens, thus it responds with "What's a urinal??" when you reference things in the Mens (US stuff).
Chromecast will fall back to using the DHCP-supplied DNS server(s) only if it doesn't get a response from Google's DNS.
Normally the ways around this would be to:
Route Google DNS requests to a bogus/non-existent gateway
Block Google DNS requests entirely
so Chromecast does not get a response from Google's DNS. Which one works depends on how your router handles the blocking/forwarding. You want a timeout or destination unreachable, rather than an outright refusal.
But... I looked in the manual for your router (seems to be a VoIP+modem+router combo) and unfortunately I couldn't find any way to add a static route, nor did I find a way to block or forward requests specifically for Google DNS.
So unless the ability to add static routes or the ability to block port requests for specific WAN destinations has been added, you may be a bit stuck. Definitely check through your router's config to see though, often times the manual lags far behind the current feature set.
However, if you don't have the necessary options in your router, that leaves you with these possibilities:
Add a router that can provide blocking or redirection via one of
static routes
IP-specific port-blocking
iptables rules
to provide network to Chromecast and devices controlling Chromecast (they need to be on the same subnet).
VPN - which is beyond my area of expertise for this usage.
Get a rooted Chromecast so you can use Eureka-ROM to enable use of DHCP-supplied DNS rather than Google DNS
If you go with option (a), you will have double-NAT, which can be problematic.
You would connect the new (filtering) router's WAN side to your existing router's LAN site. You cannot connect the two routers LAN-LAN as the new router will only filter/redirect traffic when it does the IP translation from LAN to WAN.
If your existing router has a Bridge option for its LAN connection, that would avoid double-NAT (bridge will connect the WAN side to LAN side transparently and disable all router NAT and filtering), but it's more likely that you would get a Static Route option before you get a bridge option.
Anyway, contemplate a bit, first check if there's Static Routes in your router's config. Sorry this has been such a verbose post.

bhiga said:
So unless the ability to add static routes or the ability to block port requests for specific WAN destinations has been added, you may be a bit stuck. Definitely check through your router's config to see though, often times the manual lags far behind the current feature set.
Anyway, contemplate a bit, first check if there's Static Routes in your router's config. Sorry this has been such a verbose post.
Click to expand...
Click to collapse
Many thanks for your detailed reply!!
I don't know much about modems/routers so would be a bit wary of setting up a new router. I checked in the setting on the modem/router provided by my ISP and there is an option to add static ip. Would that be a way to block Google's DNS?

slonn said:
Many thanks for your detailed reply!!
I don't know much about modems/routers so would be a bit wary of setting up a new router. I checked in the setting on the modem/router provided by my ISP and there is an option to add static ip. Would that be a way to block Google's DNS?
Click to expand...
Click to collapse
Unfortunately not - and don't change that - you'll lose Internet connection.
While you're there, though, can tell me what options you have in the Working Mode dropdown where it currently says Router Mode?
DON'T change it though - that's likely to break your Internet connection too.

bhiga said:
While you're there, though, can tell me what options you have in the Working Mode dropdown where it currently says Router Mode?
DON'T change it though - that's likely to break your Internet connection too.
Click to expand...
Click to collapse
There's Router Mode and Bridge Only in the dropdown.

slonn said:
There's Router Mode and Bridge Only in the dropdown.
Click to expand...
Click to collapse
Cool. If you decide to get another router, you should be able to switch that dropdown to Bridge Only and connect your existing router's LAN port to the new router's WAN/Internet port, and it should avoid double-NAT-ing.
Essentially your existing router would only be used as a modem (and VoIP, if you're using VoIP), and you'd disable old router's WiFi and do all your DHCP, WiFi, etc on your new router.

As a rule I try (best I can) to avoid Dual Purpose networking devices as I have found they do neither task very good....
Unfortunately ISPs are moving towards these all in one boxes (Modem/Router/WiFi) and it Wreaks havoc on those who have their own networking gear....
Whats worse is they are locking the configs of these devices so that you can't change them easily to get it to do what you want.

bhiga said:
Cool. If you decide to get another router, you should be able to switch that dropdown to Bridge Only and connect your existing router's LAN port to the new router's WAN/Internet port, and it should avoid double-NAT-ing.
Essentially your existing router would only be used as a modem (and VoIP, if you're using VoIP), and you'd disable old router's WiFi and do all your DHCP, WiFi, etc on your new router.
Click to expand...
Click to collapse
Sounds too simple to be true. I do have an extra router so perhaps I'll test it out at some stage during the week. Thanks for your help so far!

slonn said:
Sounds too simple to be true. I do have an extra router so perhaps I'll test it out at some stage during the week. Thanks for your help so far!
Click to expand...
Click to collapse
You can also try this simple test without the router to see if it works....
Connect your computer directly to the Modem/Router...
Set the Router to Bridge Only mode and if your PC gets an outside (Public) IP Address then you know it will work with an external Router.
The only issue you might face is sometimes if the ISP provided the Modem they program it not to accept that change without it coming from their side.

I connected a new router (ASUS RT-N56U) to the existing router/modem. The existing was set to Bridge Mode with DHCP off and it can connect to the internet but not cast any show (local or US) to the TV. Not sure what details are needed for you to help me getting it to work. I can cast local Netflix onto my phone and tablet. YouTube videos can cast to TV.

slonn said:
I connected a new router (ASUS RT-N56U) to the existing router/modem. The existing was set to Bridge Mode with DHCP off and it can connect to the internet but not cast any show (local or US) to the TV. Not sure what details are needed for you to help me getting it to work. I can cast local Netflix onto my phone and tablet. YouTube videos can cast to TV.
Click to expand...
Click to collapse
Not totally up on the settings screens for your new router but check to see what IP Address it has under the Internet settings.
Every Router has two IP Addresses, one local (192.168.x.x) and one Public (should be provided by the Modem in bridge mode),
If both are local IPs then your double NATing which will easily break Netflix. If one is a Public IP then check other settings in the new router most notably UPnP and Multicast.
Also ( sorry dumb question follows) but you did make sure to set up the CCast to connect to the NEW router not the old one?

Asphyx said:
Not totally up on the settings screens for your new router but check to see what IP Address it has under the Internet settings.
Every Router has two IP Addresses, one local (192.168.x.x) and one Public (should be provided by the Modem in bridge mode),
If both are local IPs then your double NATing which will easily break Netflix. If one is a Public IP then check other settings in the new router most notably UPnP and Multicast.
Also ( sorry dumb question follows) but you did make sure to set up the CCast to connect to the NEW router not the old one?
Click to expand...
Click to collapse
There are two IP addresses: 192.168.1.2, 192.168.1.254, first one local and the other public. I can't locate UPnP and Multicast in the router.
I made sure to set the Chromecast to the new network. The old one shows but it's not connected to the internet. It's in bridge mode.

slonn said:
There are two IP addresses: 192.168.1.2, 192.168.1.254, first one local and the other public. I can't locate UPnP and Multicast in the router.
I made sure to set the Chromecast to the new network. The old one shows but it's not connected to the internet. It's in bridge mode.
Click to expand...
Click to collapse
As I suspected...Your Double NATing is the problem....Your new Router is not actually breaching the Modem to the Internet.
This modem also has WiFi built in I bet....
The DHCP you shut off probably doesn't apply to anything directly plugged into the Modem. Just the WiFi.
You need to look for a setting that gives you the option of passing a local/internal (192.168.x.x) IP or Outside IP and set it to pass an Outside IP. (this is on the Modem BTW)
If the Router reports any IP that starts off 192.168 for Public then you are not set up correctly.
If you see the option to change from local IP to Outside IP but it is greyed out then your ISP locked it out and they must make the changes on their end.
Call and tell them your Modem is in Bridge mode but doing double NAT translation and you can't breach the Modem with your router.

slonn said:
There are two IP addresses: 192.168.1.2, 192.168.1.254, first one local and the other public. I can't locate UPnP and Multicast in the router.
I made sure to set the Chromecast to the new network. The old one shows but it's not connected to the internet. It's in bridge mode.
Click to expand...
Click to collapse
As @Asphyx said, there's double-NAT going on. This may be a problem, but the core problem at the moment is that new router's WAN and LAN are using the same subnet.
I recommend...
Turn off the WiFi on your old router, if you can.
Look for the stuff Asphyx mentioned.
If you get stuck, call your ISP
Ask them to enable Bridge mode and explain that you're looking for more robust routing and firewall features
Ask if there's a firmware update for your existing modem/router combo to provide this, if there is a different ISP-provided modem/router you can use that has better features, or if they can provide/recommend a modem-only device (if they don't/can't enable Bridge mode)
Ideally, you want to see is your new router getting a WAN address that is not 192.168.x.x
If you reach that point, you're done.
If not, you at least want your new router getting a WAN address that is in a different subnet from its local network.
On your new router, change the Local address to 192.168.2.2
That will switch things on the new router to the 192.168.2.x subnet. Now the new router and old router will be on different subnets.
Make sure any client devices (wired or wireless) that have static IPs set are changed to use IP 192.168.2.something and gateway 192.168.2.2
My network is double-NAT and I have not had issues with Chromecast, streaming, VPN, or anything else, but you definitely should avoid double-NAT whenever possible.

NETFLIX: We're having trouble playing this title right now...

I'm living in Panama City, so I'm natively in the Mexico Netflix region. On my apple TV I'm using unblock-us to change regions. Obviously for chromecast I've removed all DNS settings from my S3, TF700 and MBP. I can watch Netflix fine on all three devices. On Chromecast I only get a few minutes, maybe 5, before I get "We're having trouble playing this title right now. Please try again later or select a different title."
This happens with all my devices. Netflix plays fine on those devices.
Google Play Movies plays perfect, Youtube has no problems.
Looking at internet traffic as the message appears, I dont see a drop in traffic at all. However in recent weeks, watching Hulu on our apple tv can sometimes take 20 minutes longer thanks to lots of pauses.
I purchased this so I didnt have to keep moving my ATV up and down stairs. I like that it's cheap, I like using a phone or chrome to control it - but I wonder if Google ever plan to add manual IP settings. How much will they add to it in the future?
I'm very tech savy, have been in IT for 13 years. The cable modem and router I have are completely foreign to me, I dont know the username and password to login and even look at the firmware. All I know is it's a motorola something. But I did miss the window for rooting it and I was thinking if I could roll the firmware back to allow rooting, but I doubt it.
Anyone have any suggesting?

If Netflix is working on other devices I would suspect your Chromecast is not getting a good/stable WiFi signal.
Use the HDMI extender, try a different (side/front) HDMI port if your TV has one and make sure it has line-of-sight to your router with as few obstructions as possible.

bhiga said:
If Netflix is working on other devices I would suspect your Chromecast is not getting a good/stable WiFi signal.
Use the HDMI extender, try a different (side/front) HDMI port if your TV has one and make sure it has line-of-sight to your router with as few obstructions as possible.
Click to expand...
Click to collapse
Sadly this doesnt work either Why would the unstable wifi signal be problem with Netflix and not Google Play? Better connection to Google's own servers?
I tried this and still no luck :crying:

FL00DY said:
Sadly this doesnt work either Why would the unstable wifi signal be problem with Netflix and not Google Play? Better connection to Google's own servers?
I tried this and still no luck :crying:
Click to expand...
Click to collapse
Differences in encoding rate can make one service work while another has problems, so really depends.
Has Netflix on Chromecast ever worked okay in this configuration?

bhiga said:
Differences in encoding rate can make one service work while another has problems, so really depends.
Has Netflix on Chromecast ever worked okay in this configuration?
Click to expand...
Click to collapse
Nope, I'm yet to finish a program without interruption, I keep switching to my ATV after the 4-5 attempt.
My wife is a apple faithful, I cant show her my new google toy and have it not work 100%. Netflix works fine most of the time on the ATV, maybe a few times the video freezes and the audio keeps playing. I think maybe the ATV handles the little dropouts better, Hulu will pause for 10-15 seconds and keep playing.
Speedtest only records 4.5-5Mb

I think I know what your problem is since I've encountered it myself.
You're using a different dns configuration to watch Netflix from a different region, let's take the USA as an example. When you configure the unblock-us setting into your router or your mobile devices they'll work and play the USA Netflix content just fine. But these settings will never work for the chromecast since it will always use google's dns which is 8.8.8.8. Or 8.8.4.4 since this is baked into the chromecast and cannot be changed.
Once you start streaming us based Netflix content to your chromecast... It's going to see that that content is not available in your region and it'll time out and show you the message you've mentioned.
The only way around this is to root your chromecast which is now impossible if you haven't already done so, or you have to have a dd-wrt supported router. So you can reroute the google dns to the unblock-us dns.
Sent from the dark side of the moon

scandalousk said:
The only way around this is to root your chromecast which is now impossible if you haven't already done so, or you have to have a dd-wrt supported router. So you can reroute the google dns to the unblock-us dns.
Click to expand...
Click to collapse
Root and iptables (which is supported by open/hacked router firmwares other than DD-WRT as well) are not the only ways:
You can also try adding a static route to an unresponsive local address
Or if your router supports blocking access to specific IPs, you can block 8.8.8.8 and 8.8.4.4
Depending on your router one or both may work.
If Chromecast times out in trying to reach Google DNS, it will fall back to the DHCP-supplied DNS.
It has to try and fail timeout, rather than get immediately refused though. Immediate refusal will make it nag about not being able to reach the Internet.

bhiga said:
Root and iptables (which is supported by open/hacked router firmwares other than DD-WRT as well) are not the only ways:
You can also try adding a static route to an unresponsive local address
Or if your router supports blocking access to specific IPs, you can block 8.8.8.8 and 8.8.4.4
Depending on your router one or both may work.
If Chromecast times out in trying to reach Google DNS, it will fall back to the DHCP-supplied DNS.
It has to try and fail timeout, rather than get immediately refused though. Immediate refusal will make it nag about not being able to reach the Internet.
Click to expand...
Click to collapse
Correct. Silly of me to not even mention this since this is the method I use lol. Thanks for pointing it out mate!
Sent from the dark side of the moon

scandalousk said:
Correct. Silly of me to not even mention this since this is the method I use lol. Thanks for pointing it out mate!
Click to expand...
Click to collapse
There are so many little details, even I forget from time to time. Just wanted to make sure people didn't think it's hopeless, at least not on the DNS front.

scandalousk said:
I think I know what your problem is since I've encountered it myself.
You're using a different dns configuration to watch Netflix from a different region, let's take the USA as an example. When you configure the unblock-us setting into your router or your mobile devices they'll work and play the USA Netflix content just fine. But these settings will never work for the chromecast since it will always use google's dns which is 8.8.8.8. Or 8.8.4.4 since this is baked into the chromecast and cannot be changed.
Once you start streaming us based Netflix content to your chromecast... It's going to see that that content is not available in your region and it'll time out and show you the message you've mentioned.
The only way around this is to root your chromecast which is now impossible if you haven't already done so, or you have to have a dd-wrt supported router. So you can reroute the google dns to the unblock-us dns.
Sent from the dark side of the moon
Click to expand...
Click to collapse
scandalousk thanks for the advice. However like I said, I'm not running any unblock-us service on my devices or routers. It's running on my ATV but it was switched off while I was trying all this...
Any method that means changing my Router config is useless as it was equipment provided by the cable company in Panama and while I can hide my device from my wife, I cant very well hide a new router. I dont know the username and password to even checkout the firmware and features. When I google the part numbers and model numbers I'm lucky to get 3-4 search results.

FL00DY said:
scandalousk thanks for the advice. However like I said, I'm not running any unblock-us service on my devices or routers. It's running on my ATV but it was switched off while I was trying all this...
Any method that means changing my Router config is useless as it was equipment provided by the cable company in Panama and while I can hide my device from my wife, I cant very well hide a new router. I dont know the username and password to even checkout the firmware and features. When I google the part numbers and model numbers I'm lucky to get 3-4 search results.
Click to expand...
Click to collapse
Why would you need to hide it from your wife?
If your Chromecast is unrooted, the *only* ways to view out of region content are by modification of the router. If necessary you could add a second more customizable router on top of the cable company's equipment, and use that network for all your casting needs.
Sent from my Nexus 5 using Tapatalk

Same problem here
Living in Panama City, same problems as OP, the difference is that it used to work when I first got it. I'm on build 16664 with no VPN or anything else to change regions. Netflix works fine on PS3, nexus 5, nexus 7, windows PC, Ouya, 3DS and Macbook. I've tried reseting the CC (holding button, and through the android app) and reinstalling the Netflix apps on my android devices (even though I knew that wasn't the problem since I can't cast from my PC either). Any ideas on router configuration we could try?

Is it possible to remotely cast a chromecast from a different network for signage ?

I'm a beginner in ChromeCast development, I've searched for a long time to have an answer on the possibility to remotely access, control and cast a chromecast device for digital signage, in different networks.
While searching and understanding the mechanics of chromecast, the answer seems to be "No !" but I've found companies selling solutions that are doing a similar thing.
So if someone knows a way to do that please inform me. (Or if it's impossible to do that).
Thank you !

Set up a VPN and then you definitely can.

DeadlyFoez said:
Set up a VPN and then you definitely can.
Click to expand...
Click to collapse
I already setup VPN (PPTP Server) on my Mikrotik Router, can ping that chromecast. But, how to connect to my chromecast, I can't see my chromecast on googlehome apps, since googlehome apps require wifi to connect chromecast.
Please somebody help me..

You will probably need to set up an mDNS forwarder or enable multicast forwarding so the app on the remote network can discover them.
Be careful as you can easily cause a loop.
Sent from my S60 using Tapatalk

Android mobile with VPM won't cast to chromecast...

Hi all,
I have an issue in that I'm trying to cast from my android mobile to my Chromecast. It won't let me though as I have a VPM on my mobile phone.
I have searched the net and read that I need to buy a VPM router to plug into the back of my existing router and then link Chromecast to that. Before I spend all that money and spend time doing that I wondered what every one thought to that idea?
Thanks in advance for any help.
Nick

nickbeachy23 said:
Hi all,
I have an issue in that I'm trying to cast from my android mobile to my Chromecast. It won't let me though as I have a VPM on my mobile phone.
I have searched the net and read that I need to buy a VPM router to plug into the back of my existing router and then link Chromecast to that. Before I spend all that money and spend time doing that I wondered what every one thought to that idea?
Thanks in advance for any help.
Nick
Click to expand...
Click to collapse
I presume that you mean "VPN" (as in Virtual Private Network).
Yeah, understandable that it won't work since the two devices would need to be connected to the *same* network, and the VPN is likely setting your default route through the VPN network, making it effectively impossible for your phone to connect to your chromecast.
It should be possible to block off local address space in your VPN's configuration. This would allow the phone to communicate with the chromecast on the local network. HOWEVER, depending on what exactly you are "casting", there could be other issues triggered by the fact that the phone and chromecast have separate public IP addresses. For example, trying to cast something like turdflix or amazon subprime would probably fail authentication.
Yes, moving your VPN from the phone to the router would solve the problem. Look at running openwrt on your router, or buying a router that can run it. Openwrt can run openvpn or other vpn software. You'll probably want a fairly powerful router with an ARM chip rather than MIPS for handling the cryptography.
Don't buy any BS "vpn router". They're universally trash.