Re: How to triage an "Invalid Key" error message?

James Prestwood <[email protected]>
Newsgroups dev.linux.lists.iwd
Message-ID <[email protected]>
Hi Christian,

On 1/17/25 10:03 PM, Christian Hewitt wrote:
> Hello folks :)
>
> The Kodi focussed distro LibreELEC switched to iwd from
> wpa_supplicant for our most recent release. It has been an
> overall positive change, but we continue to see a trickle
> of end-user reports of an “Invalid Key” error when devices
> connect to a network.
>
> Things we’ve established:
>
> * Reverting to wpa_supplicant allows the device to connect
> * Happens on a range of hardware so is not driver specific
> * Happens on a range of kernels (tested back to 6.1)
> * Poor signal strength shows the issue more frequently
> * Networks with FT enabled show the issue more frequently
> * Has nothing to do with passphrase length/characters
>
> TL/DR: We are reasonably confident the issue is within iwd
> code and not drivers or kernels. We also use latest or very
> recent kernels (and in-kernel drivers) and latest ConnMan
> (we are generally ‘current’ with upstream sources throughout
> the distro). We suspect a combination of radio properties
> (influenced by poor signal and features) results in an error
> which is not handled correctly so you end up in the wrong
> place in code and trip the ‘Invalid Key’ error instead.
>
> Our project team are not able to replicate the issue with
> our own devices and networks so we are currently reliant
> on end-user reports. We also lack iwd debugging experience.
> However, our embedded style distro packaging makes it very
> simple for users to update and run an image tweaked with
> iwd patches and/or config to get the output required to
> triage the issue.
>
> So I’d like to understand what needs to be collected or
> patched etc. to help start the process.

For a start if you could gather debug logs when your users see the 
"Invalid key" message. Tbh I don't see anywhere IWD itself would print 
that, but ELL will signal that if some IWD settings file is using some 
invalid characters, that's about all I can think of at the moment 
without seeing debug logs. Our wiki [1] has some additional info about 
debugging. I'd even be happy to look at any of your locally tracked bug 
reports if there are any, otherwise just send some logs this way and 
we'll take a look.

[1] https://archive.kernel.org/oldwiki/iwd.wiki.kernel.org/debugging.html

Thanks,

James

>
> Thanks in advance,
>
> Christian
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.