On 4/19/22 11:40 PM, Peer, Ilan wrote:
Hi,
-----Original Message-----
From: Jouni Malinen <j@xxxxx>
Sent: Monday, April 18, 2022 18:20
To: Peer, Ilan <ilan.peer@xxxxxxxxx>
Cc: hostap@xxxxxxxxxxxxxxxxxxx
Subject: Re: [PATCH v4 2/4] scan: Add a configuration option to disable 6GHz
collocated scanning
On Mon, Apr 11, 2022 at 05:21:59PM +0300, Ilan Peer wrote:
This configuration option can be used to disable 6GHz collocated scan
logic which would result with passively scanning 6GHz non PSC channels.
Is this really something we should do as a configuration option? Is the default
behavior to scan only the 6 GHz channels that are either PSC or that have
been determined to have a BSS based on neighbor report? And is that
somehow conditional on active vs. passive scanning?
I could understand having a need for a specific SCAN command that will scan
all 6 GHz channels passively, but it would seem more reasonable to do that
with a SCAN control interface command argument instead of a configuration
parameter that applies to all scan operations. Isn't it way too slow to scan all
non-PSC channels on the 6 GHz using a passive scan for normal use?
This was requested as testing option by Ben. I agree that extending the scan command to
force passively scanning 6GHz channels makes more sense. I'll prepare such a change.
I don't know enough about this particular issue to have an opinion about how it is implemented,
I just need a way to let ax210 driver work with the upstream ax210 patch that changed scanning
behaviour for 6E channels, since it broke my STA associating to a vendor's AP.
Thanks,
Ben
--
Ben Greear <greearb@xxxxxxxxxxxxxxx>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
Hostap mailing list
Hostap@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/hostap
