From owner-freebsd-chat Mon Dec 4 1: 9:24 2000 From owner-freebsd-chat@FreeBSD.ORG Mon Dec 4 01:09:21 2000 Return-Path: Delivered-To: freebsd-chat@freebsd.org Received: from mobile.wemm.org (adsl-64-163-195-99.dsl.snfc21.pacbell.net [64.163.195.99]) by hub.freebsd.org (Postfix) with ESMTP id 62A1637B400 for ; Mon, 4 Dec 2000 01:09:21 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id eB4993D55119; Mon, 4 Dec 2000 01:09:03 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200012040909.eB4993D55119@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: cjclark@alum.mit.edu Cc: freebsd-chat@FreeBSD.ORG Subject: Re: CVSup Problems In-Reply-To: <20001203214209.A99903@149.211.6.64.reflexcom.com> Date: Mon, 04 Dec 2000 01:09:03 -0800 From: Peter Wemm Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Crist J . Clark" wrote: > There was a thread that found its way on to here the other day. The > topic was how easy and low-bandwidth CVSup is to use with people > making statements like, "5 minutes on a dial-up link," to CVSup an > existing source tree. > > I once would have agreed, but I have been having a really frustrating > time with CVSup. I am hoping someone can help me debug this. > > Here is an example of what I see. I tried to CVSup STABLE this > afternoon, > > # cvsup -P- -g complete-supfile > Connected to cvsup11.freeBSD.org > Updating collection src-base/cvs > Updating collection src-bin/cvs > Updating collection src-contrib/cvs > TreeList failed: Network write failure: Connection timed out > Will retry at 12:00:42 > Retrying > Connected to cvsup11.freeBSD.org > Updating collection src-base/cvs > Updating collection src-bin/cvs [..] > Edit src/release/texts/alpha/HARDWARE.TXT > Updating collection src-sbin/cvs > Updating collection src-share/cvs > Updating collection src-sys/cvs > TreeList failed: Network write failure: Connection timed out > Will retry at 13:17:23 > Retrying > Connected to cvsup11.freeBSD.org > Updating collection src-base/cvs [..] > > I've sat and watched with a tcpdump and I see packets going out to the > server but no responses. In this example, it's cvsup11, but this > happens no matter which server I try. Nor does time of day or day of > the week seem to matter. This makes me think it is either a problem > with me or my ISP. I thought my dynamic rules on the firewall were > timing out TCP connections too soon so I cranked those up, but the > tcpdump shows that nothing was coming back. > > I typically don't have any problems with downloads over other > services, but I wonder about the upload end. Uploads can be painful > the few times I've moved anything big (though scp). IIRC, CVSup pushes > some data upstream? Could this be my problem? > > Anyone have some ideas of what to look at? Anyone have CVSup problems > and manage to fix them? I have seen strange cvsup stuff in the recent past that was solved by using the "-Pa" (active mode) or "-P-" (passive mode). The other thing to try is to do something like this: route change default -lock -mtu 1400 and/or route change cvsup11.freebsd.org -lock -mtu 1400 You can try lower numbers, down to say 500.. The interesting thing is that the cvsup client mostly *uploads* data, which is in the opposite direction to usual ISP dialup traffic. This means you can run into outbound problems that you didn't know you had, eg: a silent MTU problem. Anyway, there are a couple of ideas to try. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message