public inbox for iwd@lists.linux.dev
 help / color / mirror / Atom feed
From: James Prestwood <prestwoj@gmail.com>
To: Denis Kenzior <denkenz@gmail.com>, iwd@lists.linux.dev
Subject: Re: [PATCH 01/15] wiphy: add driver quirk for the colocated scan flag
Date: Tue, 26 Aug 2025 08:24:22 -0700	[thread overview]
Message-ID: <533715f1-ccd6-4254-90a2-2fad273bdd22@gmail.com> (raw)
In-Reply-To: <d30b921a-6de5-4843-b3fa-83ec7973d8ac@gmail.com>

Hi Denis,

On 8/26/25 7:47 AM, Denis Kenzior wrote:
> Hi James,
>
> On 8/22/25 2:51 PM, James Prestwood wrote:
>> Some drivers do not handle the colocated scan flag very well and this
>> results in BSS's not being seen in scans. This of course results in
>> very poor behavior.
>>
>> This has been seen on ath11k specifically but after some
>> conversations [1] on the linux-wireless mailing list others have
>> reported issues with iwlwifi acting similarly. Since there are many
>> hardware variants that use both ath11k and iwlwifi this new quirk
>> isn't being forced to those drivers, but let users configure IWD to
>> disable the flag if needed.
>>
>> [1] 
>> https://lore.kernel.org/linux-wireless/d1e75a08-047d-7947-d51a-2e486efead77@candelatech.com/
>
> So why does dropping the colocated flag help?  You have a 2/5 G 
> network that isn't related to the 6G network at all, meaning that 
> there is no RNR element. Hence 6G must be scanned passively on social 
> channels.  If you don't add the colocated flag, the end result should 
> be the same, no?  Or is colocated flag forcing the use of RNR element 
> only?

We noticed this issue specifically with a 6Ghz-only network. So in 
theory there should have been no RNR element at all... Despite this, and 
performing full spectrum scans, we would get a very limited set of BSS's 
back on 6ghz. I suspect maybe the kernel was only scanning social 
channels, but removing the colocated flag got things working as I would 
expect.

I asked the question, and Ben said he saw similar behavior on iwlwifi. 
Its likely an oversight in the kernel. It would be nice to fix there, 
but my dedication to fixing the kernel is ever dwindling. Based on my 
testing after removing the flag I opted for a one-line workaround...

>
>> ---
>>   src/wiphy | 23 +++++++++++++++++------
>>   src/wiphy.h |  1 +
>>   2 files changed, 18 insertions(+), 6 deletions(-)
>>
>
> Anyway, I went ahead and applied patches 1-4.
>
> Regards,
> -Denis

      reply	other threads:[~2025-08-26 15:24 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-22 19:51 [PATCH 01/15] wiphy: add driver quirk for the colocated scan flag James Prestwood
2025-08-22 19:51 ` [PATCH 02/15] wiphy: add comments around the driver quirks James Prestwood
2025-08-22 19:51 ` [PATCH 03/15] scan: check support before using colocated flag James Prestwood
2025-08-22 19:51 ` [PATCH 04/15] monitor: add Cisco Meraki as a printable vendor James Prestwood
2025-08-22 19:51 ` [PATCH 05/15] vendor_quirks: initial skeleton James Prestwood
2025-08-23 14:43   ` Marcel Holtmann
2025-08-25 14:31     ` James Prestwood
2025-08-26 14:56   ` Denis Kenzior
2025-08-22 19:51 ` [PATCH 06/15] vendor_quirks: add two new vendor quirks James Prestwood
2025-08-23 14:46   ` Marcel Holtmann
2025-08-25 14:32     ` James Prestwood
2025-08-22 19:51 ` [PATCH 07/15] handshake: pass object to handshake_util_ap_ie_matches James Prestwood
2025-08-22 19:51 ` [PATCH 08/15] handshake: add vendor quirks into handshake object James Prestwood
2025-08-22 19:51 ` [PATCH 09/15] scan: store vendor quirks in scan_bss James Prestwood
2025-08-22 19:51 ` [PATCH 10/15] station: set vendor quirks into handshake object James Prestwood
2025-08-22 19:51 ` [PATCH 11/15] handshake: use vendor quirk to disable check of replay counters James Prestwood
2025-08-22 19:51 ` [PATCH 12/15] station: get neighbor report on BSS TM request James Prestwood
2025-08-22 19:51 ` [PATCH 13/15] station: check vendor quirk for BSS TM request candidate list James Prestwood
2025-08-23 14:48   ` Marcel Holtmann
2025-08-25 14:37     ` James Prestwood
2025-08-22 19:51 ` [PATCH 14/15] station: clear roam_freqs on delayed roam James Prestwood
2025-08-26 15:00   ` Denis Kenzior
2025-08-22 19:51 ` [PATCH 15/15] auto-t: add AP roam test for bad neighbor reports/candidate lists James Prestwood
2025-08-26 14:47 ` [PATCH 01/15] wiphy: add driver quirk for the colocated scan flag Denis Kenzior
2025-08-26 15:24   ` James Prestwood [this message]

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=533715f1-ccd6-4254-90a2-2fad273bdd22@gmail.com \
    --to=prestwoj@gmail.com \
    --cc=denkenz@gmail.com \
    --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