I believe I've isolated the problem to an interaction between BusyBox's udhcpc (DHCP) client running in the background and periodically renewing the lease on an interface's IP address and Connman. I had integrated Connman onto an existing target that already used BusyBox's ifplugd/ifupdown/udhcpc to assign IP addresses to interfaces that were configured to be "up". What wasn't clear at the time was the later interaction (or should I say battle) between udhcpc and Connman to set the default route for an interface on lease renewal. At this point I believe this interaction is causing my default route to be added/removed sporadically and the subsequent churn in the logs. I guess, given my limited understanding of some of Connman's internals, this seems to make sense. Hopefully other developers who use BusyBox and udhcpc (with Connman) should be aware of this interaction. It seems you should pick one or the other for DHCP and not both.
Thanks for the pointers for where to start looking for the problem. I think that led me to take a closer look at the other processes on my target that could be mucking with the default route. Glenn On Fri, Dec 13, 2013 at 3:32 AM, Patrik Flykt <[email protected]> wrote: > > Hi, > > I have seen short sequences of 2-4 NEWROUTE/DELROUTE rtnl messages, but > they are normal rtnl messaging and don't cause any routes to be added or > deleted. > > Could you get a longer log snippet with CONNMAN_DHCP_DEBUG=1 exported in > addition to the full debug output to see if this relates to DHCP? > > > Cheers, > > Patrik > > > _______________________________________________ > connman mailing list > [email protected] > https://lists.connman.net/mailman/listinfo/connman _______________________________________________ connman mailing list [email protected] https://lists.connman.net/mailman/listinfo/connman
