[0/3] wifi: mac80211: public action ECSA frame improvements

Message ID	20240612123037.36687-5-johannes@sipsolutions.net (mailing list archive)
Headers	show Received: from sipsolutions.net (s3.sipsolutions.net [168.119.38.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id DA4BC171656 for <linux-wireless@vger.kernel.org>; Wed, 12 Jun 2024 12:30:46 +0000 (UTC) From: Johannes Berg <johannes@sipsolutions.net> To: linux-wireless@vger.kernel.org Subject: [PATCH 0/3] wifi: mac80211: public action ECSA frame improvements Date: Wed, 12 Jun 2024 14:28:34 +0200 Message-ID: <20240612123037.36687-5-johannes@sipsolutions.net> Precedence: bulk MIME-Version: 1.0 Content-Transfer-Encoding: 8bit
Series	wifi: mac80211: public action ECSA frame improvements \| expand [0/3] wifi: mac80211: public action ECSA frame improvements [1/3] wifi: mac80211: refactor CSA queue block/unblock [2/3] wifi: mac80211: restrict public action ECSA frame handling [3/3] wifi: mac80211: handle protected dual of public action

Message ID

20240612123037.36687-5-johannes@sipsolutions.net (mailing list archive)

Headers

From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Subject: [PATCH 0/3] wifi: mac80211: public action ECSA frame improvements
Date: Wed, 12 Jun 2024 14:28:34 +0200
Message-ID: <20240612123037.36687-5-johannes@sipsolutions.net>
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

Series

wifi: mac80211: public action ECSA frame improvements | expand

Message

Johannes Berg June 12, 2024, 12:28 p.m. UTC

Public action ECSA frames are not protected, so treating them to
e.g. change channel or disconnect immediately can lead to issues.
Use them only for quiet indication, and then check against the
beacon - in case of beacon protection, that will give a good
indication.

Perhaps this code should only apply in case of beacon protection?

johannes