From owner-freebsd-stable Thu Apr 5 12:21:14 2001 Delivered-To: freebsd-stable@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 8165537B505 for ; Thu, 5 Apr 2001 12:21:12 -0700 (PDT) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f35JFPf38752; Thu, 5 Apr 2001 14:15:25 -0500 (CDT) (envelope-from jlemon) Date: Thu, 5 Apr 2001 14:15:25 -0500 (CDT) From: Jonathan Lemon Message-Id: <200104051915.f35JFPf38752@prism.flugsvamp.com> To: Cy.Schubert@uumail.gov.bc.ca, stable@freebsd.org Subject: Re: Answer Found: TCP New Reno algorithm X-Newsgroups: local.mail.freebsd-stable In-Reply-To: Organization: Cc: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >No need to reply. Discovered that the Reno TCP algorithm is a rate >limiting algorithm for congested networks. Our network is chronically >congested, hence the slow Veritas backups. Actually, this is incorrect. TCP newreno is an algorithm for better recovery of lost packets, in the absence of a SACK implementation. newreno should improve performance during packet drops, not decrease it. I would be interested in seeing a tcpdump of the traffic, in order to see what is going wrong. Would it be possible to get a binary tcpdump (-w option) of the traffic stream on both machines? -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message