archive mirror
 help / color / mirror / Atom feed
From: Daniel Wagner <>
To: Jupiter <>
Subject: Re: Problem in connman 1.39
Date: Mon, 23 Aug 2021 11:02:08 +0200	[thread overview]
Message-ID: <20210823090208.qgh62abb7mpixeih@carbon.lan> (raw)
In-Reply-To: <>

Hi Jupiter,

On Mon, Aug 23, 2021 at 06:08:07PM +1000, Jupiter wrote:
> Hi Daniel,
> Thanks for your response. Someone responded to me that version 1.39
> messed up some library, asked me to update to 1.40, but I could not
> find that email anymore.

Ah okay. Checking latest version is always a good idea anyway.

> BTW, I got email bounce from because the address
> couldn't be found, what is the current connman mailing list address?

The new mailing list is hosted on Unfortunately, we
lost access to the old one before the new one was up and running. The
README should always be up to date as we don't have any official web
page for ConnMan. I was pondering if we should ask for a wiki space on
korg, similar to iwd.


> On 8/23/21, Daniel Wagner <> wrote:
> > Hi Jupiter,
> >
> > On Sun, Aug 22, 2021 at 08:41:40PM +1000, Jupiter wrote:
> >> I could run connman 1.37 well built from Zeus, but it did not work on
> >> connman version 1.39 after upgrading from Zeus to Hardknott, it could
> >> not display a WiFi interface :192.168.0.x, but instead of a fault IP
> >> Let me know if you need more debug information.
> >
> > IP address range is from the link local address
> > range. That means ConnMan was not able to get an IP address via DHCP
> > IP. Check what the logs for DHCP messages. It might give you a clue
> > what's going wrong.
> >
> > Daniel
> >
> --
> "A man can fail many times, but he isn't a failure until he begins to
> blame somebody else."
> -- John Burroughs

           reply	other threads:[~2021-08-23  9:02 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <>]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210823090208.qgh62abb7mpixeih@carbon.lan \ \ \ \

* 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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).