From owner-freebsd-questions@FreeBSD.ORG Wed Dec 10 05:21:00 2003 Return-Path: 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 9283116A4CE for ; Wed, 10 Dec 2003 05:21:00 -0800 (PST) Received: from be-well.no-ip.com (lowellg.ne.client2.attbi.com [66.30.200.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7689243D2A for ; Wed, 10 Dec 2003 05:20:59 -0800 (PST) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: by be-well.no-ip.com (Postfix, from userid 1147) id E9D188F; Wed, 10 Dec 2003 08:20:58 -0500 (EST) Sender: lowell@be-well.ilk.org To: paul beard References: <2FF582F3-2A76-11D8-8C05-000A95BBCCF8@mac.com> From: Lowell Gilbert Date: 10 Dec 2003 08:20:58 -0500 In-Reply-To: <2FF582F3-2A76-11D8-8C05-000A95BBCCF8@mac.com> Message-ID: <44n0a095c5.fsf@be-well.ilk.org> Lines: 25 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: FreeBSD-questions Subject: Re: how to make dhclient give up its lease and get a new one with routes, etc. ? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: FreeBSD-questions List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2003 13:21:00 -0000 paul beard writes: > somewhere other than on my network. As luck would have, I got assigned > a new IP address last night (for the first time since I used @home > more than 3 years ago) and for some reason the dhcp client wouldn't > get the new address. I ran dhclient and that just set my address to > all 0's. I then killed it and restarted and got an address but no > routes. I ended up rebooting and that solved it (I then had to fix > both no-ip's config file since the old one was unparseable by version > 2 clients and go to zoneedit and update my address). > > So how to make dhclient do all this without the Windows workaround of > rebooting? You have to kill the existing dhclient instantiation before you mess around with this (I suspect that's the part you missed). Then you should try "dhclient -r" to release the existing lease (and, probably, reset some state at the server), and then start dhclient up again. That should do it. -- Lowell Gilbert, embedded/networking software engineer, Boston area: resume/CV at http://be-well.ilk.org:8088/~lowell/resume/ username/password "public"