Naveen Singh reported that resolver initialization needs to be
called after plugin initialization. This because the loopback
interface will be configured during plugin initialization. At
the time of resolver initialization the loopback interface needs
to exist or else __connman_dnsproxy_add_listener() will fail
during dnsproxy initialization as the interface index is -1.
This causes resolver code initialization to fail, causing
ConnMan to unconditionally falling back to using resolv.conf
and not its own DNS proxy.
As proposed by Naveen, fix this by initializing the resolver
code after the plugins initializations.
---
src/main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/main.c b/src/main.c
index 54476dc..e46fa7b 100644
--- a/src/main.c
+++ b/src/main.c
@@ -676,7 +676,6 @@ int main(int argc, char *argv[])
__connman_stats_init();
__connman_clock_init();
- __connman_resolver_init(option_dnsproxy);
__connman_ipconfig_init();
__connman_rtnl_init();
__connman_task_init();
@@ -688,6 +687,7 @@ int main(int argc, char *argv[])
__connman_plugin_init(option_plugin, option_noplugin);
+ __connman_resolver_init(option_dnsproxy);
__connman_rtnl_start();
__connman_dhcp_init();
__connman_dhcpv6_init();
--
2.1.4
_______________________________________________
connman mailing list
[email protected]
https://lists.connman.net/mailman/listinfo/connman
