On 23 February 2017 at 19:35, Gil Pitney <email@example.com> wrote:
In the existing DHCP design it’s not enough for application just subscribe+1.
to NET_EVENT_IF_UP event.
For our client application we observed situations when the link was up, but
IPV4 address still hasn’t been assigned yet.
The issue was solved by subscribing to NET_EVENT_IPV4_ADDR_ADD event.
So maybe in the new design it should be taken into account as well.
For example, echo_client application starts DHCP (if configured), but
does not wait for the IPv4 address to be acquired before proceeding
(and so uses an incorrect static IP address instead).
But perhaps, the event should be something like NET_DHCP_IPV4_ADDR_ACQUIRED?
Is it important to distinguish how the address was acquired?