Send connman mailing list submissions to
[email protected]
To subscribe or unsubscribe via email, send a message with subject or
body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of connman digest..."
Today's Topics:
1. Re: Impossible to retry when entering wrong password with connmanctl.
(Daniel Wagner)
----------------------------------------------------------------------
Date: Tue, 4 Feb 2020 08:52:56 +0100
From: Daniel Wagner <[email protected]>
Subject: Re: Impossible to retry when entering wrong password with
connmanctl.
To: Maxime Roussin-Bélanger <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=iso-8859-1
On Mon, Feb 03, 2020 at 06:06:08PM -0500, Maxime Roussin-Bélanger wrote:
> Hi Daniel! Tested iwd.
Yay!
> I started using iwd, and the first thing that happened was that I lost the
> ability to
> scan. Everytime I type `scan wifi`, from connmanctl, I get
> `Error /net/connman/technology/wifi: Not Supported`. This error is -95.
>
> The backtrace looks like:
>
> manager.c:get_technologies()
> technology.c:scan() technology 0x559d75d760 request from :1.19
> connman_device_request_scan() device 0x559d7664d0 err -95
> connman_device_request_scan() device 0x559d762ba0 err -95
> technology.c:reply_scan_pending() technology 0x559d75f760 err -95
Looks like you are using not the current head. I just recently updated
the iwd plugin. Before that the scan trigger was not implemented.
But that you can ignore this for the time being. You can also trigger
the scan by iwctl.
> > If it is not to complicated to intergrate, give it a try. This gives
> > you at least some idea where the problem could be. And again iwmon is
> > an excellent tool for monitoring the interface. I don't know if lttng
> > is able to decode all the traces. Ususally, you can easily spot the
> > problems in the traces generated by iwmon.
>
> I had to add a bunch of cryptographic algorithm to the kernel to use iwd.
Yes, iwd uses the kernel cryptographic subsystem and doesn't ship it's own.
> I analyzed the packets from iwmon with Wireshark and there was some
> Malformed packets error...
That doesn't look too good. Are the malformed packets from the kernel
or from iwd? Either way I would reproduce this with a current kernel
and see if it's a problem. If yes, please report it upstream.
> We are using the 4.19 kernel, and iwd depends on a few cryptographic
> functions from 4.20. PKCS8 which is not in 4.19.
Ah, didn't think about this. Indeed the minimum vanilla kernel needed
is 4.20. Though I remember they iwd folks have maintained their
patches outside of the kernel for a while for all the different kernel
versions. Maybe you could pick those for the testing.
Thanks,
Daniel
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list -- [email protected]
To unsubscribe send an email to [email protected]
------------------------------
End of connman Digest, Vol 52, Issue 5
**************************************
