Date: Wed, 23 Aug 2000 19:13:02 -0400 From: "Otter" <otterr@telocity.com> To: "Nathaniel G H" <bsd_appliance@bemail.org>, <freebsd-questions@FreeBSD.ORG> Subject: RE: DHCP "refresh" question Message-ID: <HLEDJBJKDDPDJBMGCLPPKEJICAAA.otterr@telocity.com> In-Reply-To: <200008231730.KAA07035@mail3.bigmailbox.com>
next in thread | previous in thread | raw e-mail | index | archive | help
boo. hiss. reboots are unnecessary. just kill the 'dhclient' and restart it. when THE DAEMON is restarted, it will request an ip from the dhcp server. If the provider has the link back up, it should be no problem. You might want to try this manually, just to make sure this is the case in your scenario. It was the case when i had bellsouth.net for ADSL service. Now I have Telocity, all that is required is for my link to come back up. The link to this ISP requires no intervention when I lose/regain connection. If HUPping the dhclient isn't enough, you might need to cycle power to the ADSL modem. See what your needs are and maybe you can write a script to serve your needs. If it requires cycling of power to the modem, you'll need to find another solution. I'm planning to do something along these lines for a project at work soon... using a FreeBSD machine to remotely energize/deenergize a relay at a customers site for cycling power to a dialup modem. -Otter -----Original Message----- From: owner-freebsd-questions@FreeBSD.ORG [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Nathaniel G H Sent: Wednesday, August 23, 2000 1:30 PM To: freebsd-questions@FreeBSD.ORG Subject: DHCP "refresh" question Hi folks, I have a wierd problem with DHCP. I've spent the last few hours reading documentation and list archives and I haven't seen anything like this. I'm posting to the list as a last resort. Some time ago, I set up a FreeBSD 3.2-RELEASE gateway / firewall (with NAT) for a customer. On this machine, ed0 is connected to an ADSL line (from GTE). ed0 gets its address via DHCP and the system works great. On occasion, however, GTE has problems and the connection dies. My customer says that when this happens, the connection never comes back up again until the FreeBSD machine is rebooted. I believe that the connection appears dead because the machine doesn't obtained a new IP address when GTE comes back up, because the lease time hasn't expired. I believe the "old" address is no longer valid and the machine doesn't figure it out when it can't send out packets on ed0. Something like "no route to host" appears on the display when this happens. Here is the configuration: * FreeBSD 3.2-RELEASE * natd on ed0 * dhclient on ed0 The machine serves as the gateway for a bunch of interactive hosts running various operating systems. How can I fix this? Is there any way to tell the machine to obtain a new address when there is no route to an external host? Thanks for your help. -Nathaniel G H ------------------------------------------------------------ Free email: http://BeMail.org/ Free BeOS: http://free.be.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?HLEDJBJKDDPDJBMGCLPPKEJICAAA.otterr>