Connect to sensor on local network on server side from windows client

[annemk]

Hi,

I can connect to my vpn server on a raspberry pi, behind the router at work, from my windows laptop at home. From the raspberry pi I can see a sensor on 192.168.1.74, and I now need access via ip to that sensor from my own laptop. The raspberry pi has local ip 192.168.0.60 which does NOT turn up if I type "arp -a" in a powershell but DOES respond to my pings and let me open remote desktop using that local address. How can I "habilitate" the sensor's ip from my laptop as well? It doesn't reply to pings from my home, it does reply to pings from the raspberry pi on the same local network.

I tried to "push" several routes and "redirect-gateway def1" on the server settings, and to "route" some ips on my client site settings, but none of the combinations seems to work, or do anything. The push and redirect settings on the server side result in errors upon trying to connect so I commented those out again.

I don't really understand how it can be that the local ip of my raspberry pi does respond to my pings from home, while the sensor seems unpingable. How can I reach the sensor from my home?

Thanks in advance

[RemoteOne]

It is likely that the sensor does not know anything about the route back to your laptop. So, your pings are getting there but the replies have no idea how to get back to where the pings came from.

You don't mention the client IP range your OpenVPN server manages - say it is 10.10.10.0/32.

If you have a default gateway on the internal network with the sensor on it, you need to add a route on that gateway to that routes all traffic for 10.10.10.0/32 via 192.168.0.60. Alternatively you can add a static route on the sensor to do the same.