Date: Fri, 13 Oct 2006 19:30:13 +0000 From: "Solovyov, Evgeny" <a.n.s.i@gmx.net> To: questions@freebsd.org Subject: Re: ssh tunnel - remote access through nat Message-ID: <20061013193012.GA1329@tit007m> In-Reply-To: <715841970607251003o1d358d3dl894291f50a0b8053@mail.gmail.com> References: <715841970607251003o1d358d3dl894291f50a0b8053@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061013193012.GA1329>