Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FS#400 - odhcpd: lease file persistence per RFC2131 S-2.1 and S-3.1.4 #5428

Open
openwrt-bot opened this issue Jan 18, 2017 · 0 comments
Open

FS#400 - odhcpd: lease file persistence per RFC2131 S-2.1 and S-3.1.4 #5428

openwrt-bot opened this issue Jan 18, 2017 · 0 comments
Labels
flyspray packages

Comments

@openwrt-bot
Copy link

@openwrt-bot openwrt-bot commented Jan 18, 2017

EricLuehrsen:

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.

@aparcar aparcar added the packages label Feb 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flyspray packages
Projects
None yet
Development

No branches or pull requests

2 participants