[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lwip-users] DHCP reboot after link up event
|
From: |
Sergio R. Caprile |
|
Subject: |
Re: [lwip-users] DHCP reboot after link up event |
|
Date: |
Fri, 19 Jun 2015 10:52:07 -0300 |
|
User-agent: |
Mozilla/5.0 (Windows NT 5.1; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 |
I see what you mean.
1660c1660,1662
< else if ((dhcp->state == DHCP_REBOOTING) || (dhcp->state ==
DHCP_REBINDING) || (dhcp->state == DHCP_RENEWING)) {
---
> else if ((dhcp->state == DHCP_STATE_REBOOTING) || (dhcp->state ==
DHCP_STATE_REBINDING) ||
> (dhcp->state == DHCP_STATE_RENEWING)) {
> dhcp_handle_ack(netif);
Based on the differences, I bet you could get away with removing that
call to dhcp_handle_ack().
This is due to a bug fix (see below), I suggest you leave a comment on
bug #38203 so you can discuss this with Simon.
http://savannah.nongnu.org/bugs/?38203
git blame:
d6620f0f (sg 2015-03-20 20:29:04 +0100 1662)
dhcp_handle_ac
git log:
commit d6620f0f3af60ba1be8c5df795c29dcddcd2698e
Author: sg <address@hidden>
Date: Fri Mar 20 20:29:04 2015 +0100
fixed bug #38203 (DHCP options are not recorded in all DHCP ack
messages)
--