From owner-freebsd-questions@FreeBSD.ORG Tue Nov 14 01:07:20 2006 Return-Path: X-Original-To: questions@freebsd.org 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 3609A16A4B3 for ; Tue, 14 Nov 2006 01:07:20 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from ns1.jnielsen.net (ns1.jnielsen.net [69.55.238.237]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8301043E32 for ; Tue, 14 Nov 2006 01:06:28 +0000 (GMT) (envelope-from lists@jnielsen.net) Received: from insp.local (jn@c-68-59-28-54.hsd1.sc.comcast.net [68.59.28.54]) (authenticated bits=0) by ns1.jnielsen.net (8.12.9p2/8.12.9) with ESMTP id kAE16RVu083174 for ; Mon, 13 Nov 2006 17:06:28 -0800 (PST) (envelope-from lists@jnielsen.net) From: John Nielsen To: questions@freebsd.org Date: Mon, 13 Nov 2006 20:06:25 -0500 User-Agent: KMail/1.9.4 X-Face: #X5#Y*q>F:]zT!DegL3z5Xo'^MN[$8k\[4^3rN~wm=s=Uw(sW}R?3b^*f1Wu*. X-Virus-Scanned: ClamAV version 0.88.4, clamav-milter version 0.88.4 on ns1.jnielsen.net X-Virus-Status: Clean Cc: Subject: dhcpd with wi and base system dhclient stopped working 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: Tue, 14 Nov 2006 01:07:20 -0000 I have a FreeBSD 6.x machine with an ath interface that serves as a wireless access point, dhcp server, router and gateway for my network. I have a FreeBSD 6.x laptop with an older wi interface that until recently was working just fine, using the base system dhclient. However, the other day when I fired it up it couldn't get an IP address from the dhcp server. Watching the logs I could see the server sending DHCPOFFER's, but the laptop wasn't receiving them for some reason. The same laptop booted to Windows gets an IP address just fine. Back on the FreeBSD side, I installed the net/isc-dhcp3-client port and it also gets an address just fine. The only think I can think of that changed between the last time this worked and the other day is the version of the dhcpd port running on the router. I updated to the 3.0.5-RC2 version of the net/isc-dhcp3-server port from the 3.0.4 version. What I'm wondering is how I can tell if this is a bug in the new dhcpd, a bug in the base system dhclient (newly exposed by a change in the dhcp server), or something else entirely (wi driver quirk? phase of the moon?). Any ideas? If this is something unique to my setup then I can live with my solution, but if it's an actual bug then I'd like to report it in the hopes of saving someone else the same headache. Thanks, JN