From owner-freebsd-questions@FreeBSD.ORG Mon Apr 19 11:01:08 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A3C2116A4CE for ; Mon, 19 Apr 2004 11:01:08 -0700 (PDT) Received: from smtpout.mac.com (A17-250-248-45.apple.com [17.250.248.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 938F343D31 for ; Mon, 19 Apr 2004 11:01:08 -0700 (PDT) (envelope-from cswiger@mac.com) Received: from mac.com (smtpin07-en2 [10.13.10.152]) by smtpout.mac.com (Xserve/MantshX 2.0) with ESMTP id i3JI17Q0012512; Mon, 19 Apr 2004 11:01:07 -0700 (PDT) Received: from [10.1.1.193] (nfw2.codefab.com [199.103.21.225] (may be forged)) (authenticated bits=0)i3JI153Z003506; Mon, 19 Apr 2004 11:01:06 -0700 (PDT) In-Reply-To: <20040419093023.C42443@hawat.cc.ubbcluj.ro> References: <20040419093023.C42443@hawat.cc.ubbcluj.ro> Mime-Version: 1.0 (Apple Message framework v613) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <83D248FE-922B-11D8-9D0B-003065ABFD92@mac.com> Content-Transfer-Encoding: 7bit From: Charles Swiger Date: Mon, 19 Apr 2004 14:01:00 -0400 To: Radu MOLNAR X-Mailer: Apple Mail (2.613) cc: freebsd-questions@freebsd.org Subject: Re: speed issues X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Apr 2004 18:01:08 -0000 On Apr 19, 2004, at 2:31 AM, Radu MOLNAR wrote: > But in this network we also use DC for file sharing. And using the DC > protocol i only get rates below 1MB/s for upload or download. I'm not sure what the "DC filesharing procotol" is; I've never heard of it, and I suspect not many other people have either. > I also get these messages in my first console: > Limiting icmp unreach response from 268 to 200 packets per second > Limiting icmp unreach response from 277 to 200 packets per second These tend to be a result of a port scan. (It's conceivable your DC protocol is trying to connect to a closed port initially and then falling back to some other port which works...?) -- -Chuck