connman.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Jupiter <jupiter.hce@gmail.com>
To: Daniel Wagner <wagi@monom.org>
Cc: comman <connman@lists.linux.dev>
Subject: Re: How to create connman_1.40.bbappend to enable and to build connman with iwd?
Date: Sat, 27 Nov 2021 08:49:45 +1100	[thread overview]
Message-ID: <CAA=hcWQMThadP0TQDhqEoREroP8TNx1yQkFHC3a0=TNv9FR3DQ@mail.gmail.com> (raw)
In-Reply-To: <20211126163040.ai2euhv6yf4esnhn@carbon>

Hi Daniel,

Greatly appreciate your kind response, please see my comments and
clarifications:

> Indeed, I recommend to use iwd instead of wpa_supplicant. There is no
> active development happening in ConnMan on the wpa_supplicant
> plugin. That means the wpa_supplicant plugin might work perfectly fine
> for your use case and there is no need to use iwd. But don't expect any
> big help if there are problems with wpa_supplicant.

Yes, I indeed have issues with 1.40 after upgrading to OE Honister,
the WiFi connection is broken, the connman 1.40 assigned a
169.154.0.0/16 range IP address, no DHCP message received:

connmand[9988]: DHCP index 3: switch listening mode (0 ==> 1)
connmand[9988]: DHCP index 3: sending DHCP discover request
connmand[9988]: DHCP index 3: sending DHCP discover request
connmand[9988]: DHCP index 3: sending DHCP discover request

No DHCP packet response received.

Please correct me, but I believe dhcp server is managed by connmand as
I found dhcp.c in the connman source, the dhcp issue is not related to
wpa-supplicant, right?

I am running CONNMAN_DHCP_DEBUG=1 connmand -n -d
src/dhcp.c:src/network.c, please let me know if you need more debug
messages.

> Hard to answer as there is not definition of 'stable enough'. The best
> advice is to test your use cases and figure out if it fits your
> requirements.

That is fine, I can see clearly the connman direction, I'll move to
using iwd for testing, I am still learning connman, not in the
position to contribute in development, but at least I can contribute
for testing and debugging :-).

> ./configure --disble-wifi --enable-iwd

I'll try it in Yocto build.

> There is no change in ConnMan's D-Bus APIs. Depending on your use cases
> you might be able to remove the ConnMan from your design and only use
> iwd. This is the case when you are only interested in WiFi networks. I
> know some project went this way as it makes their system simpler and
> more robust.

My IoT device is running both WiFi and 4G LTE network interfaces, I
definitely need connman to manage network switching between 4G LTE and
WiFi .

Thank you very much Daniel.

Kind regards,

- jupiter

  reply	other threads:[~2021-11-26 21:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-25 23:03 How to create connman_1.40.bbappend to enable and to build connman with iwd? Jupiter
2021-11-26 16:30 ` Daniel Wagner
2021-11-26 21:49   ` Jupiter [this message]
2021-11-29  6:52     ` Jupiter
2021-11-29  9:04       ` VAUTRIN Emmanuel (Canal Plus Prestataire)
2021-11-29 21:06         ` Jupiter
2021-11-30  9:59           ` VAUTRIN Emmanuel (Canal Plus Prestataire)
2021-11-30 10:59             ` Jupiter
2021-11-30 14:44               ` VAUTRIN Emmanuel (Canal Plus Prestataire)
     [not found] <16BAEC7B11896AEA.23256@lists.yoctoproject.org>
2021-11-26  6:26 ` Jupiter

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='CAA=hcWQMThadP0TQDhqEoREroP8TNx1yQkFHC3a0=TNv9FR3DQ@mail.gmail.com' \
    --to=jupiter.hce@gmail.com \
    --cc=connman@lists.linux.dev \
    --cc=wagi@monom.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 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).