So you want to make the Ethernet port on the remote Pi appear as a local network port on your local PC so that some software for device programming can run locally but program a remote device. Is that it?dpslusser wrote: ↑Mon Jun 11, 2018 12:56 am
The main problem is this:
Even though the PI will be connected to WIFI at this facility, the network port of the PI will have a device connected to it which I need to program remotely. The programming software can't run on the PI. So, essentially, the PI will be used as a WIFI Bridge for this particular device connected via LAN to the PI.
This is exactly what I am trying to do. lol.mxracer wrote: ↑Wed Jun 13, 2018 8:18 amI have done this but for accessing PLC connected to the pi behind other networks, I have openvpn clients running on the pi connected back to my digitalocean droplet ($5 a month can't go wrong) all the clients have there own cert for the vpn with static ips on the tunnel and use reverse proxy and dns a record pointed to the tunnels, all the pi's can be on same subnet and not be an issue as I create a remote route to the client i need access to. I don't have to worry about changing ip's etc look into running your own server and if you pc goes down you don't have to worry
epoch, I think it was my lack of understanding. Your solution will also work.
Users browsing this forum: JeyDe and 13 guests