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.

Sign up for GitHub

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

Jump to bottom

Detecting DHCP lease renewal timeout #436

Closed
ryan-summers opened this issue Mar 12, 2021 · 1 comment · Fixed by #437
Closed

Detecting DHCP lease renewal timeout #436

ryan-summers opened this issue Mar 12, 2021 · 1 comment · Fixed by #437
Labels
kind/feature

Comments

@ryan-summers
Copy link
Contributor

If the DHCP server cannot be contacted within the lease time, RFC 2131 states that the user of the address must immediately cease usage. Currently, there's no means of determining if a DHCP lease has expired, so it's impossible for clients to cease usage of an allocated address.
@ryan-summers
Copy link
Contributor Author

It also occurs to me that the DHCPv4 client should likely automatically apply and/or clear the assigned address instead of returning it to the user (same with default route). Was the decision to leave this up to the user a result of the various compile-time features of smoltcp?

@ryan-summers ryan-summers mentioned this issue Mar 12, 2021
Merged
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Adding DHCP lease management ryan-summers/smoltcp
2 participants
@whitequark @ryan-summers