I have clients all over the world that will occasionally need software/firmware updates to the hardware I have provided them. They have no IT staff or networking know-how, and I'm 10 years out from my last networking class, so I'm rusty but not incompetent.
A typical setup will be me sitting in my office with my laptop, and the client's laptop connected physically to the device with an ethernet cable and to the internet with wifi.
What I'm trying to achieve is to connect to their laptop through a vpn service like hamachi or teamviewer's vpn driver, and then bridge the vpn in such a way that I can access the device from my office as if I was connected to it directly.
Some more specific details
- wifi : 192.168.0.xxx, mask 255.255.255.0
- teamviewer vpn : 7.xxx.xxx.xxx, mask 255.0.0.0
- wifi : any possible configuration, but typically the same as mine
- teamviewer vpn : same as mine
- ethernet : 192.168.178.10, mask 255.255.255.0
The devices at their location
- each device is on the same 192.168.178.xxx subnet on an ethernet switch, with static IPs ranging from 001 to 005
What I need: - I should be able to type "ping 192.168.178.2" from my end and get the device from their end
What I've tried:
- used the "route" command to add a route from 192.168.178.2 to their vpn ip
- used the windows bridge connection tool to bridge the ethernet on their end with the teamviewer virtual adapter. Then tried to set the bridges IP to either the ethernet's IP or teamviewer's IP. Couldn't get it to work, but I feel like I'm just missing some understanding of how to configure this properly
What I have available: I can remote desktop into their machine to change settings and install some software
What I don't: I can't ship them anything or have them install/buy any hardware, this has to be a software only solution
Thank you in advance for your response
EDIT: In my test setup, by enabling IP routing and using wireshark to monitor the ethernet port leading to the device, if I attempt to ping across the vpn I can see the packet get through to the device, but its reply of a Who-is ARP broadcast is never responded to.