RFC2131 DHCPv4 expects that the DHCP leases and other configuration results are in persistent storage. For small embedded routers during a machine reboot, it has been accepted that read-write memory is RAM (not flash) and persistence may not be entirely upheld. That being said, odhcpd has no means to maintain the lease information even through an application only restart (example ifup event). The lease file odhcpd writes is not used to seed odhcpd, if it is restarted. (1) an interface reconnect that causes odhcpd to restart destroys the lease record, even if the network resumes as previously configured. (2) even if odhcpd lease file is directed to persistent storage (USB drive) it is not used to resume leases.
The text was updated successfully, but these errors were encountered: