From owner-freebsd-current@FreeBSD.ORG Wed Jul 28 17:24:06 2004 Return-Path: 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 1ECAE16A5B5 for ; Wed, 28 Jul 2004 17:24:06 +0000 (GMT) Received: from mail3.speakeasy.net (mail3.speakeasy.net [216.254.0.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC71E43D2F for ; Wed, 28 Jul 2004 17:24:05 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 1370 invoked from network); 28 Jul 2004 17:23:49 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 28 Jul 2004 17:23:47 -0000 Received: from 10.50.40.208 (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i6SHNJq1081034; Wed, 28 Jul 2004 13:23:36 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: "Angelo Turetta" Date: Wed, 28 Jul 2004 13:19:50 -0400 User-Agent: KMail/1.6 References: <20040326001705.W34892@cvs.imp.ch> <200407272350.56522.jhb@FreeBSD.org> <00e001c47479$76d6a5e0$7c2aa8c0@lan> In-Reply-To: <00e001c47479$76d6a5e0$7c2aa8c0@lan> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200407281319.50296.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: freebsd-current@FreeBSD.org Subject: Re: Ok, who broke interface autoconfiguration? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Wed, 28 Jul 2004 17:24:06 -0000 On Wednesday 28 July 2004 04:04 am, Angelo Turetta wrote: > ----- Original Message ----- > From: "John Baldwin" > Sent: Wednesday, July 28, 2004 5:50 AM > > > What happens for me is that it configures the interface for IP 0.0.0.0, > > but it > > > sends out lease requests from its earlier lease IP (10.x.x.x) rather than > > 0.0.0.0. The problem for me is when I switch between my home network > > (192.168.0.x) and my work network (10.x.x.x), in which cases the source > > IP address it is using is invalid and I think the DHCP server is thus > > ignoring > > > the request. Removing the leases file and restarting dhclient seems to > > be the only fix. It also seems to have recently been broken (like in the > > last > > > few weeks or months). > > I've seen this happen (I mean, problem getting a lease after moving to a > different network) when one of the ISC DHCP servers had not been set to > authoritative (and the client was Windows2000). > > Angelo Turetta > > ------------------- from the sample dhcpd.conf > # If this DHCP server is the official DHCP server for the local > # network, the authoritative directive should be uncommented. > authoritative; > --------------------------------------------------- Aha! Thanks! -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org