Thanks for the informative answer.
As I said, I like the idea of a small and lightweigth, but still
powerful daemon. But in addition to the described behaviour and the lack
of documentation, it is also not working correctly on my system. After
the first dhcp lease is expired, connman segfaults and
On 9 May 2014 17:57, Neuer User wrote:
> Seems, I am not the only one wondering why connman phones home:
The "ask the author" approach works quite well. The hostname it's
looking up is connman.net. This is the captive portal detection:
pretty much every major platform does something similar and
Seems, I am not the only one wondering why connman phones home:
https://bbs.archlinux.org/viewtopic.php?id=181038
The address is 87.106.208.187, which is the IP of
"senator.holtmann.net". The author of the connman package seems to be
Marcel Holtmann .
Honestly, without a reasonable explanation w
Hi Andrea
I'd like the idea of a somewhat smarter network daemon, but connman
slowly becomes a bit suspicious to me.
First, it is very bad documented and difficult to understand what it
does. Second, it needs iptables to work. Why? Third, it adds strange
static routes to my routing table and dele
Michael,
On Fri, May 9, 2014 at 3:21 PM, Auslands-KV wrote:
> 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).
One of the reaso
Great, then I will remove it.
My app does not run as root, but all system configuration tasks are only
available for root on my system.
Am 09.05.2014 17:22, schrieb Burton, Ross:
> On 9 May 2014 16:15, Neuer User wrote:
>> Do you by chance know, why it depends on the xuser-account package? I
>>
On 9 May 2014 16:15, Neuer User wrote:
> 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.
If you're applications are running as root then you can remove the
dependency on that
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 ad
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 ad
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
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:
#
[Re: [yocto] replace udhcpc] On 14.05.08 (Thu 05:54) Neuer User wrote:
> Am 07.05.2014 11:27, schrieb Søren Holm:
> > Use ifplugd recipe I just submitted.
> >
>
> Very nice idea. Where do I find the recipe?
Søren withdrew the submission to meta-networking following furt
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 ethern
> What should I do best on Yocto? Replace udhcpc with dhclient? If so, how
>> should that be done?
>
> Personally I prefer using connman for this, it does all the usual
> hotplug and connect magic. If size is an issue, you can disable the
> 3g and wifi DISTRO_FEATURES if you
to rely on
>> dhclient3. My experiences here were that dhclient remained as a deamon
>> continuing trying to get a dhcp address.
>>
>> What should I do best on Yocto? Replace udhcpc with dhclient? If so, how
>> should that be done?
>>
>> Or can udhcpc be configured
On 7 May 2014 09:57, Neuer User wrote:
> What should I do best on Yocto? Replace udhcpc with dhclient? If so, how
> should that be done?
Personally I prefer using connman for this, it does all the usual
hotplug and connect magic. If size is an issue, you can disable the
3g an
t;
> What should I do best on Yocto? Replace udhcpc with dhclient? If so, how
> should that be done?
>
> Or can udhcpc be configured to remain in the background and try to get
> an IP address when network is finally up?
>
> Thanks for any help
>
> Michael
--
Søren Holm
--
based system, which seem to rely on
dhclient3. My experiences here were that dhclient remained as a deamon
continuing trying to get a dhcp address.
What should I do best on Yocto? Replace udhcpc with dhclient? If so, how
should that be done?
Or can udhcpc be configured to remain in the background
18 matches
Mail list logo
