From owner-freebsd-current@FreeBSD.ORG Mon Nov 1 23:25:12 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 655C616A4CE for ; Mon, 1 Nov 2004 23:25:12 +0000 (GMT) Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 08FEE43D70 for ; Mon, 1 Nov 2004 23:25:12 +0000 (GMT) (envelope-from andy@siliconlandmark.com) Received: from alpha.siliconlandmark.com (andy@localhost [127.0.0.1]) iA1NP6PE017717; Mon, 1 Nov 2004 18:25:06 -0500 (EST) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost)iA1NP6Ft017714; Mon, 1 Nov 2004 18:25:06 -0500 (EST) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing -bs Date: Mon, 1 Nov 2004 18:25:06 -0500 (EST) From: Andre Guibert de Bruet To: Charles Swiger In-Reply-To: <452EA137-2C43-11D9-A18C-003065ABFD92@mac.com> Message-ID: <20041101182204.T82803@alpha.siliconlandmark.com> References: <20041101192959.GD14715@daemon.li> <452EA137-2C43-11D9-A18C-003065ABFD92@mac.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean cc: current@freebsd.org Subject: Re: 6-current 'corrupted mac on input' on cvs co X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Nov 2004 23:25:12 -0000 On Mon, 1 Nov 2004, Charles Swiger wrote: > On Nov 1, 2004, at 2:29 PM, Josef El-Rayes wrote: >> Received disconnect from 192.168.0.5: 2: Corrupted MAC on input. >> cvs[checkout aborted]: received broken pipe signal >> >> any ideas? do you need more input? > > The error message comes from /usr/src/crypto/openssh/packet.c, line 973. > > I haven't seen it happen often, but there seems to be some correlation > between using NAT or having packets get fragmented due to path MTU issues. > Any data corruption in the packets going by ought to be detected and fixed at > the TCP level, but if it doesn't, SSH will notice and drop the connection. As Josef pointed out in his other post to this thread, it is due to a corruption bug in if_sk. I saw this type of thing with if_nge w/mpsafenet set to 1 back in september (Check the archives for the reference), shortly after mpsafenet was made standard. Regards, | Andre Guibert de Bruet | Enterprise Software Consultant > | Silicon Landmark, LLC. | http://siliconlandmark.com/ >