Hi Cristiano, On Thu, Oct 07, 2010 at 01:45:14PM -0300, [email protected] wrote: > From: Cristiano Fernandes <[email protected]> > > Currently connman uses ioctl to set address, netmask and broadcast > separately. This imples that when a ip address with a non default netmask > is set to an interface (192.168.1.10/20 for instance), a netlink event will > be trigged announcing that the address has been configured with default > netmask (192.168.1.10/24). Connman will then signal an IPv4 change with the > wrong netmask. When the correct netmask is set with ioctl, a removal netlink > event will be trigged that connman will signal again as an IPv4 change. > Finally, the correct address and netmask are set, another netlink event > announces an address change and connman signals IPv4 change with the correct > values. > > Using netlink to set and clear ipv4 configuration avoids connman from > sending multiple IPv4 signals through DBus with the wrong configuration, > since the configuration are set all at once triggering only one netlink > event. Thanks a lot, both patches applied.
Cheers, Samuel. -- Intel Open Source Technology Centre http://oss.intel.com/ _______________________________________________ connman mailing list [email protected] http://lists.connman.net/listinfo/connman
