[FS#401] odhcpd: lease trigger script receives no arguments

LEDE Bugs lede-bugs at lists.infradead.org
Tue Jan 17 16:58:09 PST 2017


A new Flyspray task has been opened.  Details are below. 

User who did this - Eric Luehrsen (EricLuehrsen) 

Attached to Project - LEDE Project
Summary - odhcpd: lease trigger script receives no arguments
Task Type - Feature Request
Category - Packages
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Low
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - when odhcpd calls the "lease trigger" script it does not pass any arguments to the script. The reason for the trigger and the host involved in the trigger are not shared. There is no discretion for RENEW, REBIND, CONFIRM, or RELEASE. Scripts which wish to load DNS with limited data, need to store their own copy of DHCP lease file and do differences. Otherwise a raw translate and dump of a large DHCP network could cause a lot of congestion as DHCP clients come on line. Reseting a network can cause an "in rush" flow like air conditioning loads on a power grid during a summer power outage.
This is exacerbated if the DNS is served on a separate device over the network, such as nsd and nsd-control (bind or unbound also). It would be good to at least pass the command and parameters common to a odhcpd lease file line.
 

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=401



More information about the lede-bugs mailing list