From: Jouni Malinen <j@w1.fi>
To: Lorenzo Bianconi <lorenzo@kernel.org>
Cc: hostap@lists.infradead.org, linux-wireless@vger.kernel.org,
nbd@nbd.name, ryder.lee@mediatek.com, evelyn.tsai@mediatek.com,
lorenzo.bianconi@redhat.com
Subject: Re: [PATCH 8/9] DFS: switch to background radar channel if available
Date: Fri, 4 Mar 2022 00:20:09 +0200 [thread overview]
Message-ID: <20220303222009.GC33342@w1.fi> (raw)
In-Reply-To: <ec706e090d7e44bcc9afd2f9789802f8c07e3c3f.1640014128.git.lorenzo@kernel.org>
On Mon, Dec 20, 2021 at 04:48:23PM +0100, Lorenzo Bianconi wrote:
> On radar detection on the main chain switch to the channel monitored
> by the background chain if we have already performed the CAC there.
Is it clear that the channel on the background chain, if one is
available with CAC performed, comply with the ETSI uniform spreading
requirements? The comment below feels a bit misleading, but the way
patch 5/9 picks the channel for background CAC might be sufficient for
this. If so, it would be good to note that in the comment here:
> diff --git a/src/ap/dfs.c b/src/ap/dfs.c
> +hostapd_dfs_background_start_channel_switch(struct hostapd_iface *iface,
> + /*
> + * If background radar detection is supported and radar channel
> + * monitored by background chain is available switch to it without
> + * waiting for the CAC otherwise let's keep a random channel.
That first part leaves it a bit open whether the random channel part from
the end of the sentence applies in practice for the new operating
channel. It is important to make this clearly describe the functionality
needed to meet uniform spreading requirement.
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2022-03-03 22:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 15:48 [PATCH 0/9] introduce background radar detection support Lorenzo Bianconi
2021-12-20 15:48 ` [PATCH 1/9] Sync include/uapi/linux/nl80211.h with mac80211-next.git Lorenzo Bianconi
2022-03-03 21:58 ` Jouni Malinen
2021-12-20 15:48 ` [PATCH 2/9] DFS: introduce dfs_set_valid_channel utility routine Lorenzo Bianconi
2021-12-20 15:48 ` [PATCH 3/9] DFS: add capability select radar-only channels Lorenzo Bianconi
2021-12-20 15:48 ` [PATCH 4/9] nl80211: report background radar/cac detection capability Lorenzo Bianconi
2021-12-20 15:48 ` [PATCH 5/9] DFS: configure background radar/cac detection Lorenzo Bianconi
2021-12-20 15:48 ` [PATCH 6/9] DFS: introduce hostapd_dfs_request_channel_switch routine Lorenzo Bianconi
2022-03-03 22:54 ` Jouni Malinen
2022-03-04 11:52 ` Lorenzo Bianconi
2021-12-20 15:48 ` [PATCH 7/9] DFS: enable CSA for background radar detection Lorenzo Bianconi
2021-12-20 15:48 ` [PATCH 8/9] DFS: switch to background radar channel if available Lorenzo Bianconi
2022-03-03 22:20 ` Jouni Malinen [this message]
2022-03-04 13:46 ` Lorenzo Bianconi
2021-12-20 15:48 ` [PATCH 9/9] DFS: introduce radar_background parameter to config file Lorenzo Bianconi
2022-03-03 21:56 ` Jouni Malinen
2022-03-04 11:08 ` Lorenzo Bianconi
2022-03-03 23:19 ` [PATCH 0/9] introduce background radar detection support Jouni Malinen
2022-03-04 9:48 ` Lorenzo Bianconi
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=20220303222009.GC33342@w1.fi \
--to=j@w1.fi \
--cc=evelyn.tsai@mediatek.com \
--cc=hostap@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=lorenzo@kernel.org \
--cc=nbd@nbd.name \
--cc=ryder.lee@mediatek.com \
/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;
as well as URLs for NNTP newsgroup(s).