DHCP4 client process replies when renewing lease 25/12525/1
authorMatthew Smith <[email protected]>
Mon, 7 May 2018 12:52:12 +0000 (07:52 -0500)
committerDave Barach <[email protected]>
Thu, 10 May 2018 14:45:53 +0000 (14:45 +0000)
commitadec5c44da9d069475453703ff76c20638a13049
treeadf40de8ba085ba4b814fe25bea510f18c3b1d46
parent8037694b7b58b8263a45915fd1ad1e2aa1f606ce
DHCP4 client process replies when renewing lease

When a DHCP client is in the bound state, it wakes up
halfway through it's lease (by default) to try and renew
the lease. The ip4-dhcp-client-detect is not enabled as
a feature at this point, so replies sent from the DHCP
server do not get applied to the lease. Eventually the
lease expires, the address is removed from the interface,
a new discovery is performed and the same address is added
back to the interface.

Before sending a request to renew in the bound state, enable
the feature to process the reply.

Change-Id: I95332ee0596f47df6f3c8bf8e3f0698dde9a1fc5
Signed-off-by: Matthew Smith <[email protected]>
(cherry picked from commit 7cb7bb3fa1eca927cd33d8b434ce0eac1d57a987)
src/vnet/dhcp/client.c