From owner-freebsd-current Mon Jul 19 8:18:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 803C414E74; Mon, 19 Jul 1999 08:18:29 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id RAA81932; Mon, 19 Jul 1999 17:15:53 +0200 (CEST) (envelope-from des) To: obituary Cc: "Chris D. Faulhaber" , freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Problem with cvsup References: <3793356A.EDC63408@atlas.newcastle.edu.au> From: Dag-Erling Smorgrav Date: 19 Jul 1999 17:15:52 +0200 In-Reply-To: obituary's message of "Tue, 20 Jul 1999 00:25:46 +1000" Message-ID: Lines: 16 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG obituary writes: > What I don't understand, however, is that the pppd/natd setup I have > here works flawlessly for web browsing, ftp, news/mail retreval, etc., > yet it can't seem to handle cvsup connections. Wierd. What version of CVSup do you run? If it's not 16.0, upgrade to 16.0, or make sure you run cvsup with the '-P m' option (*not* '-m'; there is no such option.) Do you run a clean kernel, or do you have any patches? There are SYN rate limiting patches floating around which are known to badly break the TCP/IP stack. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message