DHCP4 client process replies when renewing lease 81/12481/2
authorMatthew Smith <mgsmith@netgate.com>
Mon, 7 May 2018 12:52:12 +0000 (07:52 -0500)
committerDave Barach <openvpp@barachs.net>
Thu, 10 May 2018 13:22:46 +0000 (13:22 +0000)
commit7cb7bb3fa1eca927cd33d8b434ce0eac1d57a987
tree4bef9ac98338a2baeb1446a02bfd612dde9c9935
parent23e310a02520ca81b17f0ec1c9a04551550bb66c
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 <mgsmith@netgate.com>
src/vnet/dhcp/client.c