On 11/17/2017 10:13 AM, Marco Gigante wrote:
> Yes, of course. Having some patches (even though they might just
> prove of concept) are usually much better to understand and to discuss.
Going to send the patch.
I looked at the patch and basically is the thing I would like to avoid.
Adding random option is not going to scale.
My need was to set the hostname to a well known value. My system
with, lets say, 'host-factory' hostname and during its running time the
hostname may become 'host-id', where id is a host identifier locally
Right, that is something very generic so far.
Also the end-user can manually change the hostname from system
gui and restart the network, hence connman.
That is your approach to solve the problem. If your GUI apps updates the
hostname, ConnMan could see the change and should the right thing... If
I am not completely mistaken ConnMan would send a new DHCPREQUEST with
the new hostname to update the DNS server.
I really would like to avoid to have two places where you configure the
The problem is that the dhcp request can contain either
or 'host-id' depending upon who runs first between connman dhcp client
and id negotiator component or end-user actions.
Hmm, somehow this sounds a bit racy :)
After a bit of pondering I think we should try the monitor approach
first and see if this works or not.