Date: Thu, 04 Jan 2001 23:02:31 -0600 From: David Kelly <dkelly@hiwaay.net> To: dmaddox@sc.rr.com Cc: trini0 <trini0@optonline.net>, FreeBSD Questions <questions@FreeBSD.ORG> Subject: Re: restarting or renewing dhclient Message-ID: <200101050502.f0552Vp26018@grumpy.dyndns.org> In-Reply-To: Message from "Donald J . Maddox" <dmaddox@sc.rr.com> of "Thu, 04 Jan 2001 22:53:49 EST." <20010104225349.A1207@cae88-102-101.sc.rr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"Donald J . Maddox" writes: > Hmmm... That's not how DHCP is *supposed* to work. My IP stays the > same for long periods too, but when it changes, it just does :) with > no ill-effects. Maybe you have an issue with your ISP here... Ditto. The worst problem I've seen with dhclient is if the cable modem service is down when the renewal time arrives the cable modem will issue 192.168.100.2 and set 192.168.100.1 as the gateway, and renewal in something like 5 seconds. Twice this happened while I was watching, when the net came back online and a real address was issued, dhclient didn't fix the default route. Not sure why it went one way but not the other. My original address was restored. Maybe that confused dhclient into believing the default route was OK. Now what *is* a mess is when you have ipfw rules with your address coded in. Have been playing with an exit hook script to decide if and when the firewall needs to be reset. Guess I could simply change the affected rules but its easy to simply re-run /etc/rc.firewall. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. 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?200101050502.f0552Vp26018>