From owner-freebsd-questions Mon Mar 18 19:41:39 2002 Delivered-To: freebsd-questions@freebsd.org Received: from smtprelay3.dc3.adelphia.net (smtprelay3.dc3.adelphia.net [24.50.78.6]) by hub.freebsd.org (Postfix) with ESMTP id 9354237B402 for ; Mon, 18 Mar 2002 19:41:33 -0800 (PST) Received: from gteworldwind ([216.202.164.30]) by smtprelay3.dc3.adelphia.net (Netscape Messaging Server 4.15) with SMTP id GT7BHV00.VM8; Mon, 18 Mar 2002 22:39:31 -0500 MIME-Version: 1.0 X-Mailer: Smartcode ObjectSet 1.0 From: Greg Oshiro Subject: Re[2]: Problem with dhclient Date: Mon, 18 Mar 2002 19:39:00 To: jester@panix.com, scott@smnolde.com Cc: freebsd-questions@FreeBSD.ORG Content-Type: multipart/mixed; boundary="=PMail:=_0002@@fhrzFmxbdVQpSN5VukYC" Message-Id: <20020319034134.9354237B402@hub.freebsd.org> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --=PMail:=_0002@@fhrzFmxbdVQpSN5VukYC Content-Type: text/plain Content-Transfer-Encoding: quoted-printable This is my first reply to the list, so please let me know of any screw-ups.= .. Try: kill dhclient -1 After connecting to the "new" network I think the -1 option causes dhclient to attempt obtaining a lease. I don't use DHCP, so I can't test it. Thanx, goshiro@compuserve.com =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D From: Jesse Sheidlower To: Internet Mail::["Scott M. Nolde" ] cc: Internet Mail::[freebsd-questions@FreeBSD.ORG] Subject: Re: Problem with dhclient Date: 3/18/02 3:37 PM On Mon, Mar 18, 2002 at 02:11:56PM -0500, Scott M. Nolde wrote: > Jesse Sheidlower(jester@panix.com)@2002.03.18 14:07:36 +0000: > > = > > I'm running FreeBSD on a laptop computer, and in general I'm pretty > > ignorant about networking issues. I'm having some difficulty using > > the dhclient program and was hoping someone could give me a hand. > > = > > After booting, if I'm plugged into a network with a DHCP server on it, > > I can run dhclient and get assigned everything I need and be > > connected. However, if I move the computer from one DHCP network to > > another without shutting it down, I cannot seem to get new networking > > information. If I don't touch anything, the previous settings stay in > > place (whether I had previously been using dhclient, or had manually > > configured for a static network); when I try to run dhclient I get the > > message "ifconfig: icotl (SIOCAIFADDR): File exists" (and no other > > ouput), and running "ifconfig" shows no inet configuration, though I > > do get a "status: active" line under fxp0 (my Ethernet card). Bringing > > fxp0 down and up has no effect. > > = > > I've run through a number of experiments, and all I can say is that > > rebooting the machine _always_ allows me to successfully configure > > using dhclient. I've looked through the various man pages for = > > dhclient and its related scripts and conf files, and looked online > > for advice, and haven't seen anything useful. > > = > > Any ideas? It's something of a pain to have to reboot the computer > > every time I move it. > > = > > Thanks, > > = > > Jesse Sheidlower > > > = > Did you try killing the dhclient process and then rerunning it again at > the new location? = Yes, I did. It had no effect--I got the same result of the "File exists", though after I had killed the dhclient process, it had to churn for a while before it returned me to a shell prompt. (I should mention that after rebooting, I also get the "File exists" message, but this is followed by a bunch of address assignments, not by a shell prompt.) > You could also remove the inet address from the nic > using ifconfig and then running dhclient. After the usual process, the ifconfiguration I have is without an inet address, but I did try to manually assign a bogus address and then run dhclient and it didn't work. Once again, by rebooting I was able to run dhclient and get an address assigned. Thanks....Hope I can work this out. Jesse Sheidlower To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message --=PMail:=_0002@@fhrzFmxbdVQpSN5VukYC-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message