Re: How to create connman_1.40.bbappend to enable and to build connman with iwd?

[Jupiter <jupiter.hce@gmail.com>]

Hi Daniel,

I finally built and managed to run connman 1.40 with iwd, the
wpa_supplicant is disabled, but there is no WiFi IP address, who is
running DHCP, connman or iwd? Running  CONNMAN_DHCP_DEBUG=1 connmand
-n -d src/dhcp.c:src/network.c, it did not send DHCP discover
requests, something is broken or not configured properly.

Thank you.

- jupiter



On 11/27/21, Jupiter <jupiter.hce@gmail.com> wrote:
> 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
>


--
"A man can fail many times, but he isn't a failure until he begins to
blame somebody else."
-- John Burroughs