Chris Abbey wrote:
>
> At 17:38 11/8/99 -0800, H. Peter Anvin wrote:
> >The problem is that for DHCP, the configuration can change *at any
> >time*. Unlike BOOTP, where you get a configuration at one point and
> >that's it, with DHCP you need to be able to change at runtime.
>
> Right, I understand DHCP... actually it can't be just ANYTIME,
> it has to be on a lease experation/renewal/release. the difference
> then is that my scripts are always invoked by an action, either
> the user wants to change the configuration, or the pppd drops the
> connection. Is there no call back from the DHCP client that would
> allow for a reevaluation of the configuration at these points?
>
Basically, such a callback is exactly what you need. The exact API for
performing the callback and the associated actions is the issue.
-hpa
--
To unsubscribe:
mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
