ssh tunnel - remote access through nat

Solovyov, Evgeny a.n.s.i at gmx.net
Fri Oct 13 14:10:11 PDT 2006


On 25.07.06 12:03 , Drew wrote:
> Hi,
> I've got a box that's nat'd out to the internet. It is occassionally
> neccessary for me to access this box remotely. The obvious answer is:
> 
> ssh -R 7777:localhost:22 remote.box cat
> 
> run from the nat'd box where remote box is a place I pretty much always have
> access too from anywhere, anytime. The problem is that the connection
> between these two boxes is famously unreliable - so I need to ensure that
> this connection stays available. Unfortunately, the procedure for this is
> not obvious to me. I've thought about a cron job, as the connection would
> simply fail if it couldn't bind to 7777 on the remote box to listen. But I'm
> thinking there has to be something that makes more sense. Suggestions?
> Feedback? Thanks in advance for any pointers.
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
> 

You can look in /usr/ports/security/autossh

here is a link too:

http://www.jfranken.de/homepages/johannes/vortraege/ssh2_inhalt.de.html#ToC16


E. Solovyov

-- 
Indecision is the basis for flexibility.


More information about the freebsd-questions mailing list