From owner-freebsd-questions@FreeBSD.ORG Fri Aug 10 09:02:54 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7E54A16A41A for ; Fri, 10 Aug 2007 09:02:54 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) Received: from galaxy.systems.pipex.net (galaxy.systems.pipex.net [62.241.162.31]) by mx1.freebsd.org (Postfix) with ESMTP id 482D813C474 for ; Fri, 10 Aug 2007 09:02:54 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) Received: from [192.168.23.2] (62-31-10-181.cable.ubr05.edin.blueyonder.co.uk [62.31.10.181]) by galaxy.systems.pipex.net (Postfix) with ESMTP id 1F973E000453; Fri, 10 Aug 2007 10:02:52 +0100 (BST) Message-ID: <46BC29B8.5050904@dial.pipex.com> Date: Fri, 10 Aug 2007 10:02:48 +0100 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.13) Gecko/20061205 X-Accept-Language: en MIME-Version: 1.0 To: Bram Schoenmakers , freebsd-questions@freebsd.org References: <200708091025.43912.bramschoenmakers@xs4all.nl> <200708091704.31952.nvass@teledomenet.gr> <46BB2730.8090702@dial.pipex.com> <200708091851.14649.bramschoenmakers@xs4all.nl> In-Reply-To: <200708091851.14649.bramschoenmakers@xs4all.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Nikos Vassiliadis Subject: Re: Problem with dump over SSH: Operation timed out 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: Fri, 10 Aug 2007 09:02:54 -0000 Bram Schoenmakers wrote: >> If you can write (and compress if short of disk space) the dump >> locally and >> >>try an scp to your remote host as Nikos is suggesting, that will narrow >>down the problem a bit. Any other large file will do: doesn't have to be a >>dump. >> >> > >As I wrote in my initial mail: > >====== >* Downloading the very same big file over SCP causes problems too, below some >SCP debug output. The connection drops quickly after it gained a reasonable >download speed. > > Sorry, didn't pick up the thread until late in the day. If this is the case, gzip over bzip2 is not likely to be the answer, nor is any SSH keepalive option (though they'd be easy to try *just in case*). Other than Nikos' PMTU suggestions I don't have much to offer. You could try another ethernet card if you have one to see if that makes any difference; or you can do some creative monitoring with tcpdump to see what traffic is being sent (try to exclude the actual ssh transfer); can you try the scp with *no* firewall in place; this is straw clutching. Presumably *some* data does actually arrive at the other end? --Alex