General discussion • Re: Remote Access To Branch Sites Behind Routers We Can't Access

Hi memjr,

Thanks for responding.

In order to ssh to a pi at a remote branch that your router is behind someone else's router, you're going to need them to forward the ssh port (whatever port that needs to be) of their router to yours. And you might end up having to deal with a double NAT situation, and that can lead to vpn issues (do Google "double NAT").

The initiating connection would be made from the RaspberryPi (that is in the branch) outbound through both routers (ours at the branch, and the other business'), so there will be no need to forward any ports from their router to ours - that is the entire point of the approach I am proposing. Am I missing something?

You could setup a VM in aws that will be the entry point for everyone, then all the locations setup a tunnel to that. When you need to access a remote location, you use that tunnel. When the location needs access to your central location, it also goes through those tunnels.

The problem now is that you need to pay for that aws setup. Some remote access package might be cheaper depending on the amount of traffic.

The remote access also offers the ability to not require any port forwarding (like realvnc does).

I'm not sure what benefit we would gain from having an AWS server in this scenario? I can already make the destination VM (on our head-office LAN) accessible from outside, so I'm not sure what additional benefit we would gain from using an AWS instance?


Thanks,

Alan.

Statistics: Posted by Alan2409 — Tue Sep 10, 2024 3:39 am

---