Hi Erik, > >> I am currently trying to get ConnMan to work on an embedded system > >> with OpenEmbedded. ConnMan itself seems to start fine and knows all > >> the relevant information. Yet using other tools like wget or curl > >> doesn't work as expected. For example I have a server > >> "internal-server" at 192.168.1.99 with a subdomain > >> "sub.internal-server". I'd expect to "ping sub" to send it's packages > >> to 192.168.1.99, yet it says it doesn't know any domain called "sub". > > > > > > Can you ping something well known, e.g. google.com? If yes, then it is just > > a DHCP configuration issue on your DHCP server. > > Yes, I can ping google just fine. But what could be the DHCP issue? > All developer computers (Ubuntu 12.04 vanilla) also get configured > with DHCP and they don't have this problem (same gateway, same > network, all connected to the same router as the target system). Also > ConnMan already learned the Domain and with the "-r" argument he > writes them correctly into /etc/resolv.conf.
actually ConnMan creates a local DNS proxy and cache at localhost. And it should put 127.0.0.1 nameserver in /etc/resolv.conf. The -r option forces ConnMan to disable the DNS proxy. So what you are talking about is the search domain option. And we are not doing that via our internal DNS proxy? Regards Marcel _______________________________________________ connman mailing list [email protected] http://lists.connman.net/listinfo/connman
