Date: Wed, 23 Aug 2000 10:30:19 -0700 From: "Nathaniel G H" <bsd_appliance@bemail.org> To: freebsd-questions@freebsd.org Subject: DHCP "refresh" question Message-ID: <200008231730.KAA07035@mail3.bigmailbox.com>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200008231730.KAA07035>