From owner-freebsd-stable Thu Jan 25 18: 6:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from femail1.rdc1.on.home.com (femail1.rdc1.on.home.com [24.2.9.88]) by hub.freebsd.org (Postfix) with ESMTP id 6652C37B400 for ; Thu, 25 Jan 2001 18:05:52 -0800 (PST) Received: from tristan.net ([24.156.220.43]) by femail1.rdc1.on.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20010126020453.CRTC764.femail1.rdc1.on.home.com@tristan.net>; Thu, 25 Jan 2001 18:04:53 -0800 Content-Length: 2532 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <00e701c08728$5544fcc0$931576d8@inethouston.net> Date: Thu, 25 Jan 2001 21:04:27 -0500 (EST) From: Colin To: "David W. Chapman Jr." Subject: Re: Network stops working Cc: freebsd-stable@FreeBSD.ORG, Luc Morin Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The DHCP server has to keep a record of the lease or there will be all kinds of interesting problems. The server will see the mac address of the client in the DHCP-DISCOVER, and if it has a record of a valid, non-expired lease, it will send that information to the requesting client. I haven't done a lot of (ok, any :)) work with the BSD DHCP client, but there should be a command parameter or signal or something that says "please tell the server to expire my existing address" (on your Win box, AFAIR it's ipconfig -release) and from there you should be able to get a valid address. Your only other options are leaving the BSD box off the network for the duration of it's lease (could be a week or more) or calling the ISP and saying "Please kill the entry for my machine, IP 24.200.211.9, from the DHCP servers .cur file" which they will probably be more than a little hesitant to do. I'm guessing the ISP has recently renumbered the network (I know my cable-modem based provider has been doing that a lot recently) and the Win box was not connected before it's lease expired. This all assumes that the Win box and BSD box are in fact seperate, not a dual boot system. If it is a dual boot system, the ISP's DHCP server has issues, as it should not issue 2 seperate addresses for the same mac address. Cheers, Colin Wass On 25-Jan-01 David W. Chapman Jr. wrote: > Are both os's on the same machine? A friend of mine had this problem, had > the cable modem plugged into the 98 workstation. then when we connected it > to the freebsd workstation it wouldn't get a lease. Apparently the dhcp > server keeps a record of the mac address. > > ----- Original Message ----- > From: "Luc Morin" > To: > Sent: Thursday, January 25, 2001 5:28 PM > Subject: Re: Network stops working > > >> Hi all, >> >> here's something interesting. >> >> I noticed that under Win98, the DHCP server will assign me >> 24.201.143.157, and under FreeBSD it will assign 24.200.211.9 >> >> How come ? Could this be a lead as to what's going on ? >> >> The one thing that bugs me most with this problem is that >> I have no problem under Windows. I'd rather it be the other >> way around :-) >> >> Regards, >> >> Luc Morin >> >> >> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-stable" in the body of the message >> > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message