Wireless Daemon for Linux
 help / color / mirror / Atom feed
From: James Prestwood <prestwoj@gmail.com>
To: Dierk.Modrow@sew-eurodrive.de, iwd@lists.linux.dev
Subject: Re: AW: IWD 2.20 does not support Fast Roaming with NXP 88W9098 chipset
Date: Fri, 11 Oct 2024 07:58:04 -0700	[thread overview]
Message-ID: <1565c790-83d9-4972-b0dc-e9f575bc8d93@gmail.com> (raw)
In-Reply-To: <c477b2d9-dcc7-4ea7-a6b1-47f6f84e4736@gmail.com>

H Dierk,

<snip>
>> I also added a sorted log file containing iwd traces, iwmon text logs 
>> and kernel msgs (of the NXP driver): 
>> resorted_logs_of_iwd_ft_connection_trial#3.txt
>>
>>
>> We would like to use iwd instead of wpa_supplicant so any help would 
>> be appreciated!
> At this point in time looking at the above logs it appears IWD isn't 
> compatible with this out of tree driver due to the requirement to use 
> CMD_AUTHENTICATE. I've thought about adding this back in for "weird" 
> drivers that have problems with how IWD works. For the near term we 
> could try and detect this case, via the CMD_REGISTER failure, and 
> disable FT entirely for drivers like this. You'd be stuck with only 
> reassociation but at least the device could roam. I can get you a 
> patch to try soon.

I just sent a few patches to the mailing list. Would you be able to try 
these out and verify the device roams? Note, its going to choose 
reassociation now (if they work as intended), not FT. But any roaming is 
better than nothing at least. Longer term we can think about using 
CMD_AUTHENTICATE for drivers like this.

Thanks,

James


  parent reply	other threads:[~2024-10-11 14:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-10 13:49 AW: IWD 2.20 does not support Fast Roaming with NXP 88W9098 chipset Dierk.Modrow
2024-10-10 14:23 ` James Prestwood
2024-10-10 15:32   ` Denis Kenzior
2024-10-10 15:40     ` James Prestwood
2024-10-11 14:58   ` James Prestwood [this message]
2024-10-11 15:32     ` AW: " Dierk.Modrow
2024-10-10 15:32 ` Denis Kenzior

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=1565c790-83d9-4972-b0dc-e9f575bc8d93@gmail.com \
    --to=prestwoj@gmail.com \
    --cc=Dierk.Modrow@sew-eurodrive.de \
    --cc=iwd@lists.linux.dev \
    /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