(Note: I read the list so I don't needs answers cc'ed to me, not that 
I mind.)

Charles  wrote:

> These variables should be setup by the dhclient program before the
> dhclient script is called.  The available variables are documented by
> the dhclient-script man page:
> http://lrp.steinkuehler.net/Packages/man/dhclient-script.8.man.htm

Thanks for the pointer to the docs. That helped a lot!

> 
> 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!

Tim



_______________________________________________
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user

Reply via email to