From owner-freebsd-questions@FreeBSD.ORG Mon Sep 21 12:45:04 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 20CF9106568F for ; Mon, 21 Sep 2009 12:45:04 +0000 (UTC) (envelope-from james@tanis.us) Received: from QMTA11.westchester.pa.mail.comcast.net (qmta11.westchester.pa.mail.comcast.net [76.96.59.211]) by mx1.freebsd.org (Postfix) with ESMTP id BC6628FC25 for ; Mon, 21 Sep 2009 12:45:03 +0000 (UTC) Received: from OMTA04.westchester.pa.mail.comcast.net ([76.96.62.35]) by QMTA11.westchester.pa.mail.comcast.net with comcast id jPGE1c0080ldTLk5BQl4le; Mon, 21 Sep 2009 12:45:04 +0000 Received: from pandora.tanis.us ([76.97.49.245]) by OMTA04.westchester.pa.mail.comcast.net with comcast id jQl31c00M5HQhhY3QQl3CK; Mon, 21 Sep 2009 12:45:04 +0000 Received: by pandora.tanis.us (Postfix, from userid 80) id 1E867B85E; Mon, 21 Sep 2009 08:44:21 -0400 (EDT) Received: from 24.159.164.66 (proxying for 192.168.1.29) (SquirrelMail authenticated user james) by tanis.us with HTTP; Mon, 21 Sep 2009 08:44:21 -0400 Message-ID: In-Reply-To: <8F1438D3-CDAC-41C3-8334-7C3708B6D78B@tanis.us> References: <7640F3CC-586D-4087-A78B-DF43F515A8E4@tanis.us> <200909210241.n8L2fVTG002381@banyan.cs.ait.ac.th> <8F1438D3-CDAC-41C3-8334-7C3708B6D78B@tanis.us> Date: Mon, 21 Sep 2009 08:44:21 -0400 From: james@tanis.us To: "James Tanis" User-Agent: SquirrelMail/1.4.19 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: Olivier Nicole , freebsd-questions@freebsd.org Subject: Re: dhcpd related issues X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Sep 2009 12:45:04 -0000 > Yeah, it seems to be the case that enough traffic was being generated > to delay the dhcp leases that the client computers were giving up. I > used dhcping to watch and witnessed it in action. Moving dhcp to > another server solved the issue. Likely I'll be moving some other > services off that server soon to cut down on other "hotspot" related > problems. I meant dhcpdump, not dhcping.