On Tue, Mar 19, 2013 at 2:03 AM, Daniel Wagner <[email protected]> wrote: > From: Daniel Wagner <[email protected]> > > --- > Hi, > > It seems we having the same problems for internal project. In our > case the router starts slower than the embedded board. ConnMan > falls back to IPv4LL because the router does not answer the DHCP request. > This patch here is completely untested but I think you get the idea :) > > cheers, > daniel
I tried the patch, and it does detect when a DHCP server comes online if it comes online quickly after the initial timeout. But the DHCP IP address never gets set. However, in my isolated switch test, things go south. Seems there are some nested callbacks, which eventually puts us in a situation where we have many, many DHCP and IPv4LL address requests going on concurrently. After less than 10 minutes, of being connected to an isolated switch, connmand crashes with these errors: Mar 19 14:15:04 justin-rn314 connmand[8345]: connman_inet_set_address: Too many open files Mar 19 14:15:04 justin-rn314 connmand[8345]: connman_inet_clear_address: Too many open files Mar 19 14:15:04 justin-rn314 connmand[8345]: connman_inet_clear_address: Invalid argument Mar 19 14:15:04 justin-rn314 connmand[8345]: connman_inet_clear_ipv6_address: Invalid argument Mar 19 14:15:04 justin-rn314 connmand[8345]: Aborting (signal 11) [/usr/sbin/connmand] -Justin _______________________________________________ connman mailing list [email protected] http://lists.connman.net/listinfo/connman
