|
From: | Axel Lin |
Subject: | [lwip-devel] [bug #50576] LWIP_NSC_IPV4_GATEWAY/NETMASK/SETTINGS_CHANGED should check if the setting is actually being changed |
Date: | Sat, 18 Mar 2017 09:41:17 -0400 (EDT) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 |
URL: <http://savannah.nongnu.org/bugs/?50576> Summary: LWIP_NSC_IPV4_GATEWAY/NETMASK/SETTINGS_CHANGED should check if the setting is actually being changed Project: lwIP - A Lightweight TCP/IP stack Submitted by: axellin Submitted on: Sat 18 Mar 2017 01:41:16 PM UTC Category: TCP Severity: 3 - Normal Item Group: Faulty Behaviour Status: None Privacy: Public Assigned to: None Open/Closed: Open Discussion Lock: Any Planned Release: None lwIP version: git head _______________________________________________________ Details: Currently seems only LWIP_NSC_IPV4_ADDRESS_CHANGED check if the setting is actually being changed. When enable LWIP_NETIF_EXT_STATUS_CALLBACK: I got below event every time when dhcp server re-assigned ip address even the gateway/netmask/ip are exactly the same with previous setting. LWIP_NSC_IPV4_GATEWAY_CHANGED LWIP_NSC_IPV4_NETMASK_CHANGED LWIP_NSC_IPV4_SETTINGS_CHANGED I think these callbacks should be called only when the setting is actually being changed. _______________________________________________________ Reply to this item at: <http://savannah.nongnu.org/bugs/?50576> _______________________________________________ Message sent via/by Savannah http://savannah.nongnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |