Description of Problem:
I've noticed appliance devices (e.g. "broadband" routers, firewall
appliances) verifying their leases frequently, like hourly, to be sure
nothing has changed. This would be a nice addition to pump.
Version-Release number of selected component (if applicable):
Whenever the local cable company decides to renumber their world (happens
every other month or so), it's necessary to do a
to get pump to recheck DHCP. I expect the lease time is set to something
long (dumb, if they're going to do renumbering). Having pump check hourly
to verify its lease would "solve" the problem, since it'd discover it
couldn't reach the DHCP server it thought it was talking to, and then do a
discover and find the new one.
Steps to Reproduce:
1. set up DHCP server to give PUMP a 3 month lease
2. change addressing on the DHCP server system and daemon
3. see how long it takes for pump to decide to requery.
It's sad that there are networks out there run poorly, requiring this kind
of thing. Clearly the appliance vendors have seen the same issue
and "solved" it by pestering the DHCP servers periodically. For Linux to
work reliably in place of appliances in this kind of environment, the
proposed enhancement would greatly help.
Though it's not well documented, pump uses a domain socket to communicate
between a command line invocation and a running daemon. As such, it's possible
to put the command:
/sbin/pump -i eth0 --renew
into a script run from cron or in the cron.hourly or whatever, to achieve the
desired effect. It'd still be nice if pump had a way to configure this
internally, but at least there's a good work-around for now.