Skip to content

dhcp6: start request when advertise received after IRT#376

Merged
rsmarples merged 1 commit intoNetworkConfiguration:masterfrom
sshambar:delayed-advertise
Oct 8, 2024
Merged

dhcp6: start request when advertise received after IRT#376
rsmarples merged 1 commit intoNetworkConfiguration:masterfrom
sshambar:delayed-advertise

Conversation

@sshambar
Copy link
Contributor

@sshambar sshambar commented Oct 7, 2024

After the initial solicit timeout, any received advertisements trigger a request. However, after the timeout, any advertisements will never result in a request, and the client sends solicits forever.

This patch adds sends a request in response to an advertise if the initial timeout has expired.

Cleanup: removes a check for an impossible state.

After the initial solicit timeout, any received advertisements trigger
a request.  However, after the timeout, any advertisements will
never result in a request, and the client sends solicits forever.

This patch adds sends a request in response to an advertise if the
initial timeout has expired.

Cleanup: removes a check for an impossible state.
@rsmarples rsmarples merged commit 2870767 into NetworkConfiguration:master Oct 8, 2024
rsmarples added a commit that referenced this pull request Oct 8, 2024
If we get a preference value of 255 then request immediately.
More RFC 8415 18.2.1 support, inspired by #376.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants