From owner-freebsd-questions@FreeBSD.ORG Thu Aug 9 13:43:17 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 A4CBA16A417 for ; Thu, 9 Aug 2007 13:43:17 +0000 (UTC) (envelope-from bramschoenmakers@xs4all.nl) Received: from viefep34-int.chello.at (viefep18-int.chello.at [213.46.255.22]) by mx1.freebsd.org (Postfix) with ESMTP id DD1F613C467 for ; Thu, 9 Aug 2007 13:43:16 +0000 (UTC) (envelope-from bramschoenmakers@xs4all.nl) Received: from [192.168.1.100] (really [89.98.221.195]) by viefep34-int.chello.at (InterMail vM.7.08.02.00 201-2186-121-20061213) with ESMTP id <20070809134315.MZBL8078.viefep34-int.chello.at@[192.168.1.100]> for ; Thu, 9 Aug 2007 15:43:15 +0200 From: Bram Schoenmakers To: freebsd-questions@freebsd.org User-Agent: KMail/1.9.6 References: <200708091025.43912.bramschoenmakers@xs4all.nl> <200708091213.47740.nvass@teledomenet.gr> In-Reply-To: <200708091213.47740.nvass@teledomenet.gr> X-Face: &[!|}QvdlkzFIu, |mW.\-Ci1t2d@CEo+#Q14@XM9*@`S, @l*5r-m!\, , kFc:ZlD62]6/>=?utf-8?q?=5B=0A=09Ovg=3BN=5Bqk=3B=60w6=3D5abys2!H+EUYcEDJ?==?utf-8?q?=25lo=26d67gO=2E!/=0A=09w?=@YD{YH]Ebe{@|(qtKgoum%{-=qXlf.+/`^E<'!m"?5d<&C(:B+p*KjP'-Knv!6U<=?utf-8?q?1W!=7EZ=0A=09P3ee-=7BfAb-i+MsJHM?=@ MIME-Version: 1.0 Content-Disposition: inline Date: Thu, 9 Aug 2007 15:43:10 +0200 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <200708091543.11003.bramschoenmakers@xs4all.nl> 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: Thu, 09 Aug 2007 13:43:17 -0000 Op donderdag 09 augustus 2007, schreef u: > Try using a much lower MTU, something like 1400 or perhaps lower, > just for testing. You should configure this, on both client and server. > > I'm not familiar with ipf to give the exact rule, but I would allow > ALL ICMP traffic, at least for testing purposes. I think this is > correct: > pass out quick proto icmp from any to any > pass in quick proto icmp from any to any > > somewhere above the "block in log quick on re0 all" rule. > > Hope this helps a bit > > Nikos Thank you for your answer. I have added the 'pass in for icmp' rule to the firewall (pass out did already exist). There was a noticable improvement, the /usr dump came much further than before. But at about 80% there was the timeout again. I tried lowering the MTU value at the server side, but nearly all other network traffic stopped working, so that is not the way to go. Kind regards, -- Bram Schoenmakers What is mind? No matter. What is matter? Never mind. (Punch, 1855)