Hi,
On Thu, 2012-08-09 at 12:07 +0200, Erik Bernoth wrote:
> It wasn't possible to
> find any meaningful documentation about connman,
There is a ./doc directory in the source code which explains the D-Bus
api. For services see ./doc/service-api.txt
> root@target:/usr/lib/connman/test/$ ./set-domains internal-server
> Traceback (most recent call last):
> File "./set-domains", line 12, in <module>
> service = dbus.Interface(bus.get_object('net.connman', path),
> File "/usr/lib/python2.7/site-packages/dbus/bus.py", line 241, in get_object
> follow_name_owner_changes=follow_name_owner_changes)
> File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 244, in
> __init__
> _dbus_bindings.validate_object_path(object_path)
> ValueError: Invalid object path
> '/net/connman/service/internal-server': contains invalid character '-'
This one was missing the service argument, test/set-domains says
"Usage: ./test/set-domains <service> [domain*]". Do like so:
./set-domains ethernet_[...]_cable internal-server
The service id was taken from below.
> resolv.conf (untouched):
> ----------------------------------
> # Generated by Connection Manager
> nameserver 127.0.0.1
> ----------------------------------
This one is ok.
> --------------------------------------------------
> [ ethernet_[...]_cable ]
> IPv6.Configuration = { Method=auto Privacy=disabled }
> AutoConnect = true
> Name = Wired
> Nameservers = [ 192.168.1.1 ]
> Provider = { }
> Favorite = true
> Domains.Configuration = [ ]
> Timeservers.Configuration = [ ]
> State = online
> Proxy = { Method=direct }
> Nameservers.Configuration = [ ]
> IPv4 = { Netmask=255.255.255.0 Gateway=192.168.1.1 Method=dhcp
> Address=192.168.1.118 }
> Timeservers = [ 192.168.1.1 ]
> IPv6 = { }
> Domains = [ internal-server ]
> Ethernet = { Interface=eth1 MTU=1500 Method=auto Address=<MAC> }
> Security = [ ]
> Proxy.Configuration = { }
> Type = ethernet
> Immutable = false
> IPv4.Configuration = { Method=dhcp }
> --------------------------------------------------
ConnMan already uses the domain given by the DHCP server, as it reports
'Domains = [ internal-server ]' here. Notice that Domains.Configuration
is empty, meaning the user has not set the search domains manually.
Since the search domain was taken from DHCP, it explains some of the DNS
lookup "features" you were seeing. ConnMan works as a DNS proxy, it will
ask the configured 'Nameservers = [ 192.168.1.1 ]' on each and every DNS
lookup. If the DNS server 192.168.1.1 is not able to answer some of the
queries, the problem is with the nameserver and not with ConnMan. If you
need to modify the nameservers, set them with:
test/set-nameservers <service> [nameserver*]
HTH,
Patrik
_______________________________________________
connman mailing list
[email protected]
http://lists.connman.net/listinfo/connman
