Hi Glenn, On 28 March 2014 16:34, Glenn Schmottlach <[email protected]> wrote: > I'm trying to understand the scenarios under which ConnMan explicitly > changes the routing table's default route or otherwise changes the > routing table in general. > > I assume if a service becomes active and has an associated gateway > that ConnMan will automatically update the default route. This would > include the case when the service is dynamically configured (e.g. > DHCP) as well as statically configured (assuming the gateway is > provided). What happens if the DHCP server does *not* provide gateway > information?
That would be quite problematic and in that case the default route cannot be set. > > Ultimately, I'm trying to understand if it is wise (or not) to have an > external component make changes to the routing table and if so, what > parts are safe to modify when ConnMan is running. Is ConnMan designed > such that is assumes ownership of the routing table and that no other > service modifies it at the same time? Yes, there should be only one entity that controls the network connections. So you will see issues if there is some other component that tries to modify the default route. Adding normal network routes might be ok although not encouraged. It is just better to let ConnMan handle the routing. > I've been burned in the past by > a BusyBox DHCP client that fought with ConnMan over the default route. > I'd like to avoid similar scenarios in the future. A better > understanding of when ConnMan impacts the routing table would be > useful. > > Thanks, > > Glenn Cheers, Jukka _______________________________________________ connman mailing list [email protected] https://lists.connman.net/mailman/listinfo/connman
