From owner-freebsd-current@FreeBSD.ORG Mon Nov 1 20:19:05 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 EFE6216A4CE; Mon, 1 Nov 2004 20:19:04 +0000 (GMT) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA25E43D1F; Mon, 1 Nov 2004 20:19:04 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from mac.com (smtpin08-en2 [10.13.10.153]) by smtpout.mac.com (8.12.6/MantshX 2.0) with ESMTP id iA1KJ40R021585; Mon, 1 Nov 2004 12:19:04 -0800 (PST) Received: from [10.1.1.245] (nfw2.codefab.com [199.103.21.225] (may be forged)) (authenticated bits=0)iA1KJ3Un023001; Mon, 1 Nov 2004 12:19:03 -0800 (PST) In-Reply-To: <20041101192959.GD14715@daemon.li> References: <20041101192959.GD14715@daemon.li> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <452EA137-2C43-11D9-A18C-003065ABFD92@mac.com> Content-Transfer-Encoding: 7bit From: Charles Swiger Date: Mon, 1 Nov 2004 15:19:01 -0500 To: Josef El-Rayes X-Mailer: Apple Mail (2.619) 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 20:19:05 -0000 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. -- -Chuck