From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 86F73E00BBF; Fri, 9 May 2014 08:15:52 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: * X-Spam-Status: No, score=1.3 required=5.0 tests=FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,RDNS_NONE,SPF_HELO_PASS autolearn=no version=3.3.1 X-Spam-HAM-Report: * -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no * trust * [80.91.229.3 listed in list.dnswl.org] * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (auslands-kv[at]gmx.de) * -0.0 SPF_HELO_PASS SPF: HELO matches SPF record * 1.3 RDNS_NONE Delivered to internal network by a host with no rDNS Received: from plane.gmane.org (unknown [80.91.229.3]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id DC3C6E00B62 for ; Fri, 9 May 2014 08:15:41 -0700 (PDT) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1WimWL-0005i4-Mb for yocto@yoctoproject.org; Fri, 09 May 2014 17:15:33 +0200 Received: from 80-218-32-173.dclient.hispeed.ch ([80.218.32.173]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 09 May 2014 17:15:33 +0200 Received: from auslands-kv by 80-218-32-173.dclient.hispeed.ch with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 09 May 2014 17:15:33 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: yocto@yoctoproject.org From: Neuer User Date: Fri, 09 May 2014 17:15:22 +0200 Message-ID: References: <536CADD1.1040402@gmx.de> Mime-Version: 1.0 X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 80-218-32-173.dclient.hispeed.ch User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 In-Reply-To: Subject: Re: replace udhcpc X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 May 2014 15:15:52 -0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Thanks a lot. I will look through these links and hope I will understand better then :-) I hope it works nicely with a read-only rootfs. It seems to write to its own config data (which is a strange behaviour). Do you by chance know, why it depends on the xuser-account package? I don't want any additional user accounts on my system. If it is not essential I would remove it. Thanks Michael Am 09.05.2014 15:06, schrieb Andrea Galbusera: > Hi, > > On Fri, May 9, 2014 at 12:28 PM, Neuer User wrote: >> 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 > > This is in fact a working configuration for the DNS proxy feature that > connman offers built-in. See [1]. > I personally went through your same frustration when trying to > understand how connman is supposed to work in order to evaluate its > maturity. Not yet an expert at all, but [2] and [3] gave me a > reasonable bootstrap into connman's main logic. Beside this, "git > grepping" the source tree is your best friend. > Angstrom distribution, i.e. available on the beaglebone boards is also > a good example of a real connman based system. > >> 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? > > Yes, there usually is one for each service handled by connman. See [4] > for details on configuration file format and their default location. > As you can see from previously suggested references, you'll usually > modify configurations by using the connmanctl client tool instead of > editing those files by hand. > > [1] http://git.kernel.org/cgit/network/connman/connman.git/tree/README > [2] http://derekmolloy.ie/set-ip-address-to-be-static-on-the-beaglebone-black/ > [3] http://www.ptrackapp.com/apclassys-notes/embedded-linux-using-connma/ > [4] http://git.kernel.org/cgit/network/connman/connman.git/tree/doc/config-format.txt > >> >> Thanks >> >> Michael >> >> Am 08.05.2014 12:27, schrieb Burton, Ross: >>> On 8 May 2014 04:58, Neuer User 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 >>> >> >> >> -- >> _______________________________________________ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto