From owner-freebsd-questions@FreeBSD.ORG Wed Nov 16 13:49:15 2005 Return-Path: X-Original-To: freebsd-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 C2D6816A41F for ; Wed, 16 Nov 2005 13:49:15 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from smtp-out2.blueyonder.co.uk (smtp-out2.blueyonder.co.uk [195.188.213.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B82E43D45 for ; Wed, 16 Nov 2005 13:49:14 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [80.192.2.225] ([80.192.2.225]) by smtp-out2.blueyonder.co.uk with Microsoft SMTPSVC(5.0.2195.6713); Wed, 16 Nov 2005 13:50:06 +0000 Message-ID: <437B38D8.9090901@dial.pipex.com> Date: Wed, 16 Nov 2005 13:49:12 +0000 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.12) Gecko/20051106 X-Accept-Language: en-us, pl MIME-Version: 1.0 To: Olaf Greve References: <437B310F.8070501@axis.nl> In-Reply-To: <437B310F.8070501@axis.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 16 Nov 2005 13:50:06.0194 (UTC) FILETIME=[A6B6D520:01C5EAB4] Cc: freebsd-questions@freebsd.org Subject: Re: How to properly set-up an SSH tunnel on FreeBSD for automatic backups 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: Wed, 16 Nov 2005 13:49:15 -0000 Olaf Greve wrote: > Hi, > > I'm trying to set-up an SSH tunnel between two FreeBSD machines, over > a direct cross-wire connection between the two, and I'm having issues > in doing so. The question(s) I have is/are probably not FreeBSD > specific, but still I hope someone can answer it/them... I don't see any specific problem with what you are trying but ssh connections are prone to so many kinds of error... The first thing you should do is to try your ssh with much verbosity "ssh -v -v -v" and see what it is doing. Does it try to use your key? If it does, does the remote server reject it? Once you have more details it may be easier to help you fix the problem, or you might find the answer yourself. Common mistakes include: wrong permissions on the key file or .ssh directories and mis/copy-pasting the public key (make sure you didn't get any newlines in it); some mistake in a config file. I say common, because these are the ones I regularly make :-) ssh -v is your friend. --Alex