From owner-freebsd-current@FreeBSD.ORG Thu Oct 20 17:35:30 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E7ED16A41F for ; Thu, 20 Oct 2005 17:35:30 +0000 (GMT) (envelope-from forrie@forrie.com) Received: from forrie.com (c-24-62-224-187.hsd1.nh.comcast.net [24.62.224.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id D105A43D64 for ; Thu, 20 Oct 2005 17:35:29 +0000 (GMT) (envelope-from forrie@forrie.com) Received: from [192.168.1.99] ([192.168.1.99]) (authenticated bits=0) by forrie.com (8.13.4/8.13.4) with ESMTP id j9KHZT5E072750 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 20 Oct 2005 13:35:29 -0400 (EDT) (envelope-from forrie@forrie.com) Message-ID: <4357D560.6010509@forrie.com> Date: Thu, 20 Oct 2005 13:35:28 -0400 From: Forrest Aldrich User-Agent: Thunderbird 1.4.1 (Windows/20051016) MIME-Version: 1.0 To: freebsd-current@freebsd.org X-Virus-Scanned: ClamAV 0.87/1145/Thu Oct 20 08:01:39 2005 on forrie.com X-Virus-Status: Clean X-Mailman-Approved-At: Fri, 21 Oct 2005 12:33:50 +0000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: dhclient problems on FreeBSD-6 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Oct 2005 17:35:30 -0000 I'm running: 6.0-BETA5 #0: Sat Oct 8 14:41:44 EDT 2005 Recently, I posted a quesiton about dhclient becoming "wedged" in the mornings, it would raise the system load and basically hang. A simple kill -HUP and restart would solve the problem. The only indication I'm seeing in the logs is: Oct 20 13:25:26 forrie dhclient[11061]: 5 bad IP checksums seen in 5 packets My provider is Comcast. Does the above message indicate something "bad" being sent from their DHCP servers or am I hitting a known bug. The dhclient I'm using is whatever comes with the stock system build. Thanks.