From owner-freebsd-net@FreeBSD.ORG Thu Feb 15 01:02:54 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1AF9916A407 for ; Thu, 15 Feb 2007 01:02:54 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.freebsd.org (Postfix) with ESMTP id E75FC13C46B for ; Thu, 15 Feb 2007 01:02:53 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id 262C91AF0E3 for ; Wed, 14 Feb 2007 20:02:51 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by out1.internal (MEProxy); Wed, 14 Feb 2007 20:02:51 -0500 X-Sasl-enc: xnyCYk6tOIbP+J7OY6oSjcMKa8OpGiem4Nl7MWn7A0nj 1171501370 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 687F02364C for ; Wed, 14 Feb 2007 20:02:50 -0500 (EST) Message-ID: <45D3B13A.5080700@FreeBSD.org> Date: Thu, 15 Feb 2007 01:02:50 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: freebsd-net@freebsd.org References: <45D33663.9040902@netfence.it> In-Reply-To: <45D33663.9040902@netfence.it> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Gateway slowed down to barely usable X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Feb 2007 01:02:54 -0000 Andrea Venturoli wrote: > > Today it suddenly dropped to a bare few b/s. I checked the ISP line by > attaching another machine in place of this and it could do full 1Mb/s, > so this box was the problem. > > After a simple reboot it started working as good as always. > > Now the question is: in case this happens again, how do I find out > what's wrong? > CPU usage was under 2% and so was swap usage... what else could I check? > What tools should I use? Points for further investigation: How long was the machine up for? Exactly which network components in FreeBSD are you using? Do you have any figures on what kind of network load the machine was dealing with? Can you rule out problems with an intermediate switch? Based on what you've said I can only speculate that the possible causes are either mbuf memory fragmentation or a driver problem; both are a total stab in the dark. Regards, BMS > > bye & Thanks > av. > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"