From owner-freebsd-questions@FreeBSD.ORG Tue Jul 25 17:23:00 2006 Return-Path: X-Original-To: questions@freebsd.org Delivered-To: freebsd-questions@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A363A16A4E0 for ; Tue, 25 Jul 2006 17:23:00 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8280A43D69 for ; Tue, 25 Jul 2006 17:22:59 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id 00B385CE0; Tue, 25 Jul 2006 13:22:59 -0400 (EDT) X-Virus-Scanned: amavisd-new at codefab.com Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gMoRjOHP1VxG; Tue, 25 Jul 2006 13:22:57 -0400 (EDT) Received: from [192.168.1.251] (pool-68-161-117-245.ny325.east.verizon.net [68.161.117.245]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pi.codefab.com (Postfix) with ESMTP id 7DEA05CB5; Tue, 25 Jul 2006 13:22:57 -0400 (EDT) Message-ID: <44C65367.7010701@mac.com> Date: Tue, 25 Jul 2006 13:22:47 -0400 From: Chuck Swiger User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: Drew References: <715841970607251003o1d358d3dl894291f50a0b8053@mail.gmail.com> In-Reply-To: <715841970607251003o1d358d3dl894291f50a0b8053@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: questions@freebsd.org Subject: Re: ssh tunnel - remote access through nat X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jul 2006 17:23:00 -0000 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. Um. Why not forward an open port like 7777 from whatever is doing NAT for this box to port 22 on it? If the NAT gateway is being assigned a dynamic IP, use dyndns.org & and update script... -- -Chuck