Hi Erik,
On 18.07.2012 17:02, Erik Bernoth wrote:
Because of your advice I cloned the repository outside of OE and found
out, that gitk doesn't nessesarily show all commits but maybe just up
to the one you checked out.
So I updated the recipe to the 1.3 tag, compiled and installed 1.3 on
my target. I checked that he really uses the 1.3 version with calling
command directly and looking what he prints as the first line.
It didn't help though. I am looking through the commits that gitk
marks bold, when searching for resolver, domain nd. Most of them are
between 1.0 and 1.1. But couldn't really learn much from that.
If you have the project cloned and just need to update it to lastest
version (assuming you don't have branches etc), just do a
git pull
that will do all the needed stuff. If you are paranoid before recompile
run ./bootstrap-configure and then make.
As a site note I want to add it's not just this one target. The
problem exists on all targets from this type.
What do you mean with 'target'. I don't follow.
I still try to understand what the expected state of connman is. For
example should it listen to any port? Does it require a user or a
group? Could it be configured to just listen to one kind of request
but not another?
ConnMan writes into /etc/resolv.conf that there is a DNS server
listening on localhost (127.0.0.1).
$ cat /etc/resolv.conf
# Generated by Connection Manager
nameserver 127.0.0.1
If that entry is missing then check if you have some other daemon
blocking the port, e.g. dnsmasq.
When libc wants to resolve a domain name, it will ask ConnMan. ConnMan
will forward that request to the real DNS server. So it acts as proxy.
You can check this with running a tcpdump on localhost interface and
your uplink. Then you see what's happening.
HTH,
daniel
_______________________________________________
connman mailing list
[email protected]
http://lists.connman.net/listinfo/connman
