You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Migrating my project to the now merged version of the DHCP client, I noticed that the IP address of the interface has to be set to the OFFERed address before the client will send out a proper REQUEST. I feel like this is racy, and the "official" IP of the interface should only be set once the server has ACKed the request.
The client is already tracking state information in its state enum (which btw I think should be available publicly, or at least as a discriminant-only Discovering/Requesting/Renew), so the last offered IP could also go there?
Migrating my project to the now merged version of the DHCP client, I noticed that the IP address of the interface has to be set to the OFFERed address before the client will send out a proper REQUEST. I feel like this is racy, and the "official" IP of the interface should only be set once the server has ACKed the request.
The client is already tracking state information in its
state
enum (which btw I think should be available publicly, or at least as a discriminant-only Discovering/Requesting/Renew), so the last offered IP could also go there?/cc @astro
The text was updated successfully, but these errors were encountered: