From owner-freebsd-stable Thu Jan 25 18:30:29 2001 Delivered-To: freebsd-stable@freebsd.org Received: from front003.cluster1.charter.net (outbound.charter.net [24.216.159.200]) by hub.freebsd.org (Postfix) with ESMTP id 023A337B400 for ; Thu, 25 Jan 2001 18:30:08 -0800 (PST) Received: from [24.217.145.132] (HELO dave) by front003.cluster1.charter.net (CommuniGate Pro SMTP 3.4b8) with SMTP id 11155034; Thu, 25 Jan 2001 21:28:38 -0500 From: Dave Uhring To: Colin , "David W. Chapman Jr." Subject: Re: Network stops working Date: Thu, 25 Jan 2001 20:30:06 -0600 X-Mailer: KMail [version 1.1.99] Content-Type: text/plain; charset="us-ascii" Cc: freebsd-stable@FreeBSD.ORG, Luc Morin References: In-Reply-To: MIME-Version: 1.0 Message-Id: <01012520300600.04280@dave> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If his cable modem is similar to mine, it recognizes only one NIC and must be power cycled in order to attach a different NIC. After killing dhclient and restarting it, he will also receive a different IP address from his ISP. The important thing is to kill the power to the cable modem for at least 1 minute then power it back up again. Dave On Thursday 25 January 2001 20:04, Colin wrote: > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message