On Mon, Feb 15, 2010 at 9:48 PM, Chris Bennett <[email protected]> wrote: >> On Mon, Feb 15, 2010 at 07:51:42AM -0600, Chris Bennett wrote: >> >> [snip] >> > Yes, that's the thread. Nice to know there is a page written up for it. > The problem I see is how to make a connection in the first place. > On the end in the US, all incoming packets are blocked unless initiated from > inside. > > I am going to travel to Guatemala and set-up the internet connection there > myself. > Right now, I don't know whether there will be any blocking on that end yet. > > Either way, I would still like to know if I can route this through a third > server that both can freely access. > It seems likely to me, but I've never done anything like that.
Have you looked at reverse-port-forwarding with ssh? i.e. from your machine in the US that can't be directly accessed, ssh to your Guatemala machine (or a third party machine) via something like: $ ssh -R 1234:localhost:22 u...@third-party Make sure sshd at third-party has the "GatewayPorts" option enabled in its sshd_config After that is setup, anyone could then ssh to port 1234 of third-party and the connection will go to the US machine. e.g. $ ssh -p 1234 u...@third-party would, in fact, ssh to the US computer. The ssh and sshd_config man pages have pretty much everything you need. Also, to keep the ssh session alive, you might want to look into something like autossh also (in ports). Good Luck, -Ryan
