From owner-freebsd-current Sat May 13 5:39: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id 5974C37B585; Sat, 13 May 2000 05:38:52 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.9.3/8.9.3) with ESMTP id NAA69672; Sat, 13 May 2000 13:39:40 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id NAA29044; Sat, 13 May 2000 13:39:11 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200005131239.NAA29044@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Andrey A. Chernov" Cc: Igor Timkin , current@FreeBSD.org, Jonathan Lemon , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org, brian@hak.lan.awfulhak.org Subject: Re: cvs commit: src/sys/netinet tcp.h tcp_input.c tcp_output.c tcp_timer.c tcp_var.h In-Reply-To: Message from "Andrey A. Chernov" of "Thu, 11 May 2000 12:00:34 PDT." <20000511120033.A61202@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 13 May 2000 13:39:11 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, May 09, 2000 at 02:56:58PM +0400, Igor Timkin wrote: > > The same problem. Local is openssh (current), remote is ssh-1.2.22 (2.2.6), > > slip ~24kbps connection. Remote log: > > May 9 09:59:17 crocus sshd[21285]: fatal: Local: Corrupted check bytes on input. > > This thing is even worse - I notice the same problem occurse in > CURRENT->CURRENT ssh connection, both with NewReno! > It means that NewReno implementation have some internal errors when two > identical -currents can't speak each other properly sometimes (when modem have > long 30secs retrain). This has been happening to me in environments with high packet loss, and before the NewReno changes went in. It was only happening in a rather dubious environment were there was high packet loss (compressed PPP over uncompressed PPP over a saturated ISDN dialup that drops up to one in every three packets). There were other bugs involved too - see recent updates to nat_cmd.c, so I never really took the whole thing too seriously (apart from suggesting to root@freefall that they shouldn't worry). I'm still seeing these errors: ipfw: -1 Refuse UDP 194.242.139.171 62.7.110.151 in via tun1 Fragment = 185 But haven't looked into them too deeply for the same reasons. All I'm saying is that I wouldn't suspect that the problem is entirely NewReno but rather that the NewReno stuff may be irritating some other problem(s). > -- > Andrey A. Chernov > > http://nagual.pp.ru/~ache/ -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message