All of lore.kernel.org
 help / color / mirror / Atom feed
From: Neuer User <auslands-kv@gmx.de>
To: yocto@yoctoproject.org
Subject: Re: replace udhcpc
Date: Sat, 10 May 2014 10:55:49 +0200	[thread overview]
Message-ID: <lkkpim$i16$1@ger.gmane.org> (raw)
In-Reply-To: <CAJTo0LbvSFTR7_=fbbqJVc_NeMU7Kj8jTCs2-dt5h61q25n0QQ@mail.gmail.com>

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 the system is
again without ip.

Found this on the internet:
https://www.mail-archive.com/connman@connman.net/msg15637.html


Am 09.05.2014 20:37, schrieb Burton, Ross:
> On 9 May 2014 17:57, Neuer User <auslands-kv@gmx.de> 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 it's to
> detect the situation that you have something that looks like a network
> connection, but actually you're not routed anywhere (i.e. you're in a
> hotel and need to pay for connectivity).  ConnMan makes a trivial
> request to it's home page and if it gets back the response it was
> expecting you have internet, captive portals tend to include
> machine-readable links in the response that ConnMan will tell the UI
> to open.  If you've ever joined an iOS (and probably Android, but I've
> not got one) device to a hotel's wifi and seen a login page open
> immediately the same you've seen this behaviour in action.
> 
> The response also includes some basic geo-ip so your machine knows
> roughly where it is, useful for automatic timezone updating.
> 
> Ross
> 




  reply	other threads:[~2014-05-10  8:56 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
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 [this message]
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='lkkpim$i16$1@ger.gmane.org' \
    --to=auslands-kv@gmx.de \
    --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.