Hi Patrik,
to get to a quite important point first: I have no idea how to
configure connman, with or without the scripts. It wasn't possible to
find any meaningful documentation about connman, neither per google
nor directly in the repository, nor in the source code. Is that
correct? If we just didn't see it, please provide a link to the
documentation. Otherwise please say more concretely what I should do.
I am not a networking software export, it doesn't come naturally to me
at all, what I should do to "add a suitable Domains.Configuration" or
how to use test/set-domains correctly. From my point of view the
domain is already known to ConnMan so I also don't know, why I should
tell hm.
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 '-'
In case it helps you to understand my current system state, I already
provide the untouched resolv.conf and list-services output. I changed
the IP's, MACs, domain-names and also can't provide the tcpdump
output, because I don't know how much information I am allowed to make
public about the company internal network.
resolv.conf (untouched):
----------------------------------
# Generated by Connection Manager
nameserver 127.0.0.1
----------------------------------
/usr/lib/connman/test/list-services (IP's, MACs and domains changed in
the copied output):
--------------------------------------------------
[ 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 }
--------------------------------------------------
2012/8/8 Patrik Flykt <[email protected]>:
>
> Hi,
>
> On Thu, 2012-07-19 at 15:25 +0200, Erik Bernoth wrote:
>> On the target, the machine using ConnMan (and without "search" or
>> "domain" in the resolv.conf), "ping sub" will request "sub" and the
>> response will be the same as on my Ubuntu machine, just without the
>> appended "internal-server".
>
> resolv.conf should only contain a 'nameserver 127.0.0.1' entry, nothing
> else. This seems to be the case here, as 'ping sub' doesn't resolve
> anything.
>
>> So he asks for "sub" and he recieves a
>> correct IP adress, but everywhere there is no "sub.internal-server".
>
> resolv.conf should not be modified. Search domains must be set in
> Domains.Configuration for the service service in question. See the
> Domains.Configuration property description in doc/service-api.txt.
>
>> There are also some additional RR's in the end which can't be read
>> correctly by wireshark. I tested that in many different variations and
>> many times, so I am sure that is always the case. The ping will still
>> fail, with telling that "sub" is unknown.
>
> I have seen wireshark reporting garbage here too. Nothing affecting the
> DNS lookup, though. Do you see this on the upstream wire or on the
> loopback interface?
>
>> This is confusing, because on one side he recieves the correct
>> information (the IP adress) and doesn't use it, on the other hand he
>> asks for the wrong thing ("sub" and not "sub.internal-server") and
>> still gets a response instead of a "No such name" as on the other
>> computers. Last but not least only in this scenario the DNS response
>> seems to be broken.
>
> I can't deduce what your setup is in this part. Do not touch resolv.conf
> after ConnMan is started and add a suitable Domains.Configuration to the
> service with test/set-domains python script. If it still doesn't work,
> please provide the contents of resolv.conf, the properties for this
> service with test/list-services and the tcpdump output for DNS lookups
> on the target with Domains.Configuration being set and not set.
>
> Cheers,
>
> Patrik
>
> _______________________________________________
> connman mailing list
> [email protected]
> http://lists.connman.net/listinfo/connman
--
Mit freundlichen Grüßen / Kind Regards
Erik Bernoth
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
_______________________________________________
connman mailing list
[email protected]
http://lists.connman.net/listinfo/connman
