> > Note that BOUND is an initial binding to an IP, and does *NOT* have > > the $old_* variables set. RENEW is what should be sent as a reason > > when a lease is renewed, which should have both the $old_* and $new_* > > variables set... > > For whatever reason, things are not working quite as I would expect, > though results are OK with the workaround for seawall that I am > using. > > The following applies to a setup based on Dachstein 1.02. > > I have instrumented the code in dhclient-exit-hooks. About every > seven ours or so, I see in syslog something like this: > > Feb 18 16:24:48 firewall dhclient: DHCPREQUEST on eth0 to > 255.255.255.255 port 67 > Feb 18 16:24:48 firewall dhclient: DHCPNAK from 208.191.191.254 > Feb 18 16:24:48 firewall dhclient: DHCPDISCOVER on eth0 to > 255.255.255.255 port 67 interval 3 > Feb 18 16:24:48 firewall dhclient: DHCPOFFER from 208.191.191.254 > Feb 18 16:24:51 firewall dhclient: DHCPREQUEST on eth0 to > 255.255.255.255 port 67 > Feb 18 16:24:51 firewall dhclient: DHCPACK from 208.191.191.254 > Feb 18 16:25:13 firewall root: Seawall Restarted > Feb 18 16:25:13 firewall dhclient: bound to 208.191.181.169 -- > renewal in 14398 seconds. > > Note in the above that seawall restarted. This is due to my > workaround in dhclient-exit-hooks. > > and the result of my instrumentation looks like this: > > Mon Feb 18 16:24:52 UTC 2002 > old_ip_address = > new_ip_address = 208.191.181.169 > reason = BOUND > > The IP doesn't change, but from your earlier message, since $reason > is BOUND, for some reason for some reason dhclient thinks it is > getting the ip for the first time. > > I have no special problem, though I wish I knew if this behavior was > limited to mys setup. I'll ask the list in another message. > > Charles, I doubt there is any more for you to add, but if you see > something, let me know, and thanks!
Actually, I do have a comment or two :). It looks like your ISP's DHCP server is not allowing you to renew a lease, but instead is giving you a new lease with the same IP. This is strange behavior, and is what's causing your problem...as far as dhclient is concerned, it's lease renewal was rejected (the first DHCPREQUEST and the DHCPNAK, above), so it had to ask for a completely new lease (the second DHCPDISCOVER, and the DHCPOFFER, DHCPREQUEST, and DHCPACK, above). I'd wager a guess that your ISP is lacking a bit in the "clue" department...have you had any other problems with them? I suppose it could also be wacky behavior by a windows DHCP server...they tend to have other "not quite correct" observed behavior, like spitting the DHCP broadcast packets out *EVERY* interface...it's not correct behavior, but if you're not watching the traffic on the wire, you wouldn't necessarily know it's happening. Do you know if your ISP is an NT or unix shop? Charles Steinkuehler http://lrp.steinkuehler.net http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
