From owner-freebsd-current@FreeBSD.ORG Wed Jul 28 08:07:50 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 B0B6E16A4CE; Wed, 28 Jul 2004 08:07:50 +0000 (GMT) Received: from mailbox.rainbownet.com (mailbox.rainbownet.com [213.174.191.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id 576D843D31; Wed, 28 Jul 2004 08:07:47 +0000 (GMT) (envelope-from aturetta@commit.it) Received: from nbangx ([151.30.165.207]) (authenticated user aturetta@rainbownet.com) by rainbownet.com (rainbownet.com [127.0.0.1]) (MDaemon.PRO.v6.8.5.R) with ESMTP id 37-md50000000713.tmp; Wed, 28 Jul 2004 10:06:50 +0200 Message-ID: <00e001c47479$76d6a5e0$7c2aa8c0@lan> From: "Angelo Turetta" To: References: <20040326001705.W34892@cvs.imp.ch> <40FDC87E.7070602@mac.com><200407211412.54225.doconnor@gsoft.com.au> <200407272350.56522.jhb@FreeBSD.org> Date: Wed, 28 Jul 2004 10:04:02 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Authenticated-Sender: aturetta@rainbownet.com X-Spam-Processed: rainbownet.com, Wed, 28 Jul 2004 10:06:50 +0200 (not processed: message from valid local sender) X-MDRemoteIP: 151.30.165.207 X-Return-Path: aturetta@commit.it X-Mailman-Approved-At: Wed, 28 Jul 2004 13:03:37 +0000 cc: John Baldwin 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 08:07:50 -0000 ----- 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; ---------------------------------------------------