From: Neuer User <auslands-kv@gmx.de>
To: yocto@yoctoproject.org
Cc: "yocto-EtnWKYl6rD/WsZ/bQMPhNw@public.gmane.org"
<public-yocto-EtnWKYl6rD/WsZ/bQMPhNw@plane.gmane.org>
Subject: Re: replace udhcpc
Date: Fri, 09 May 2014 12:28:33 +0200 [thread overview]
Message-ID: <536CADD1.1040402@gmx.de> (raw)
In-Reply-To: <CAJTo0LZDzH3aQBiwMM=cR06CEqthVQycaSWsM8jAyEHxwYiRWQ@mail.gmail.com>
Connman is really a problem without documentation. :-(
I tried it out and first I noticed that it depends on the creation of an
xuser account. It also needs iptables, so probably can configure these, too.
I also found that it does not correctly configure the dns entries:
cat /etc/resolv.conf:
# Generated by Connection Manager
nameserver 127.0.0.1
nameserver ::1
I really would like to understand what it does with these and how I can
change or modify it's behaviour.
It's definitely not just "when ethernet cable inserted, bring up the
interface using DHCP".
I even can't find a config file for connman. Is there one?
Thanks
Michael
Am 08.05.2014 12:27, schrieb Burton, Ross:
> On 8 May 2014 04:58, Neuer User <auslands-kv@gmx.de> wrote:
>> I had a brief look at connman half a year ago, but that time I was
>> unable to find a good documentation about it. Do you have by chance a
>> link to some tutorial or at least man entry for the configuration?
>
> What do you need to configure? For "when ethernet cable inserted,
> bring up the interface using DHCP" this is default behaviour and won't
> need any configuring. connman is sadly under-documented but the IRC
> channel is fairly responsive.
>
> Ross
>
next prev parent reply other threads:[~2014-05-09 10:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 8:57 replace udhcpc Neuer User
2014-05-07 9:27 ` Søren Holm
2014-05-08 3:54 ` Neuer User
2014-05-08 13:38 ` Joe MacDonald
2014-05-07 10:24 ` Burton, Ross
2014-05-08 3:58 ` Neuer User
2014-05-08 10:27 ` Burton, Ross
2014-05-09 10:28 ` Neuer User [this message]
2014-05-09 13:06 ` Andrea Galbusera
2014-05-09 13:21 ` Auslands-KV
2014-05-09 15:27 ` Andrea Galbusera
2014-05-09 16:51 ` Neuer User
2014-05-09 16:57 ` Neuer User
2014-05-09 18:37 ` Burton, Ross
2014-05-10 8:55 ` Neuer User
2014-05-09 15:15 ` Neuer User
2014-05-09 15:22 ` Burton, Ross
2014-05-09 15:24 ` Neuer User
2014-05-10 9:01 ` [solved] " Neuer User
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=536CADD1.1040402@gmx.de \
--to=auslands-kv@gmx.de \
--cc=public-yocto-EtnWKYl6rD/WsZ/bQMPhNw@plane.gmane.org \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.