How to get to see all my IoT devices through VPN connection to remote location
-
So this is the setup, I am connecting to a remote location through OpenVPN. This location's LAN network is 10.10.0.0/22, and the network assigned to my VPN connection is 192.168.2.0/24.
I have a rule in the firewall settings that is allow LAN network to any, so I am expecting with this rule that all my network can see every device on it. No matter if you are o 10.10.0.0/22 or 192.168.2.0/24.
For example, I CAN access the router on 10.10.0.1 with the VPN connection, also I CAN access any device through typing it's lan address, for example an IP camera at 10.10.0.20 using my VPN connection with assigned address 192.168.2.3.
But what it doesn't work specifically is seeing my chromecast audio currently on 10.10.0.130, from my pc connected to that location with VPN. When I open spotify there's no chromecast there, but I can access all the network hmm... what am I doing wrong?
-
@vmsca said in How to get to see all my IoT devices through VPN connection to remote location:
But what it doesn't work specifically is seeing my chromecast audio currently on 10.10.0.130, from my pc connected to that location with VPN. When I open spotify there's no chromecast there,
What you want to achieve here, might require that both, the server and the client resides within the same layer 2 network. This requires protocols which are not passed across a router and cannot be routed at all.
There are several helper programs available for this though, but I'm in doubt that this will work over a VPN.Anyway, when looking for a solution for that, you should rather put keyword like "Chromecast" or "Spotify" together with "VPN" into the heading.
-
@viragomann Hmm interesting, I really thought you only needed to see machines on the same subnet. Will look into it, thank you!
-
@vmsca said in How to get to see all my IoT devices through VPN connection to remote location:
what am I doing wrong?
nothing really - but discovery only works on the same network.. Chromecast isn't going to be discovered over routed networks, be they locally routed over over a vpn even locally routed.
The discovery is meant to be on the same L2.. Talk to google there should be no reason to not have the option to put in the IP or fqdn of the chromecast so you can cast to it. You shouldn't have to rely on "discovery" that is great for grandma and such - but you should also have the option to set what the IP of the chromecast you want to cast to is on.
They design their device so your typical home user with everything on one network doesn't have to know anything and it just discoveries it and works.. Which is fine, but what about those that are not on 1 flat network ;)