[PATCH] supplicant: skip NOP channels
Jouni Malinen
j at w1.fi
Thu Mar 19 10:27:34 PDT 2026
On Sun, Feb 22, 2026 at 10:36:50AM +0100, Janusz Dziedzic wrote:
> In case we have AP run:
> - on same phy that supplicant
> - on different phy in current system
> respect unavailable (NOP) channels and
> don't try to assoc using this channel,
> after AP will detect RADAR on such channel.
This description feels a bit confusing.. Isn't this proposed a STA mode
operation to avoid using channels that have been marked unavailable due
to radar detection based on anything operating on the system (whether it
happens to be the same phy or something else does not really matter for
this). And isn't that "after AP will detect RADAR" supposed to be "after
the AP has detected a radar"?
Why should a STA mode operation, i.e., a DFS client, follow NOP from
local DFS owner operation? The rules for DFS owners may prevent that
specific device from starting an AP mode operation for a certain time
after having detected a radar, but that does not apply to other devices
that might not have detected the radar, i.e., it does not apply to other
APs that might be operating on the channel and to which the local STA
interface might want to connect.
--
Jouni Malinen PGP id EFC895FA
More information about the Hostap
mailing list