Fix to handle a situation where dhcp callback has been registered 60/195960/1
authorRahul Jain <rahul.jain@samsung.com>
Thu, 20 Dec 2018 05:11:05 +0000 (10:41 +0530)
committerRahul Jain <rahul.jain@samsung.com>
Thu, 20 Dec 2018 05:16:22 +0000 (10:46 +0530)
for a peer but peer has not requested for IP.
So, for next connection, callback comes for old peer rather than new peer.
Thus, ignoring old callback before registering new callback

Change-Id: Id1f25cd899ba66c1e7436a9a8823ecee9a84d12c
Signed-off-by: Rahul Jain <rahul.jain@samsung.com>
packaging/wifi-direct-manager.spec
src/wifi-direct-util.c

index ecdde59..61c1924 100644 (file)
@@ -6,7 +6,7 @@
 
 Name:          wifi-direct-manager
 Summary:       Wi-Fi Direct manger
-Version:       1.2.271
+Version:       1.2.272
 Release:       1
 Group:      Network & Connectivity/Wireless
 License:    Apache-2.0
index 51ee2e1..1c574a5 100644 (file)
@@ -1525,6 +1525,7 @@ int wfd_util_dhcps_wait_ip_leased(wfd_device_s *peer)
                return -1;
        }
 
+       vconf_ignore_key_changed(VCONFKEY_DHCPS_IP_LEASE, _dhcps_ip_leased_cb);
        vconf_set_int(VCONFKEY_WIFI_DIRECT_DHCP_IP_LEASE, 0);
        vconf_notify_key_changed(VCONFKEY_WIFI_DIRECT_DHCP_IP_LEASE, _dhcps_ip_leased_cb, peer);