[PATCH v2] wpa_supplicant: Do not associate on 6GHz with forbidden configurations
Matthew Wang
matthewmwang at chromium.org
Wed Mar 16 08:57:47 PDT 2022
Ah, you're right, I slightly misinterpreted, thanks!
On Tue, Mar 15, 2022 at 9:53 AM Peer, Ilan <ilan.peer at intel.com> wrote:
>
> Hi,
>
> > -----Original Message-----
> > From: Matthew Wang <matthewmwang at chromium.org>
> > Sent: Sunday, March 13, 2022 06:43
> > To: Otcheretianski, Andrei <andrei.otcheretianski at intel.com>
> > Cc: hostap at lists.infradead.org; Peer, Ilan <ilan.peer at intel.com>
> > Subject: Re: [PATCH v2] wpa_supplicant: Do not associate on 6GHz with
> > forbidden configurations
> >
> > I'm not sure I agree with the execution here. In particular, I don't think we
> > should be modifying the IEs of the AP to prevent association.
> > Rather, there are places (e.g. wpa_supplicant_set_suites) where we
> > determine the correct suite based on the network configuration and the AP
> > IEs, and it makes more sense to do the 6ghz check there. In the case of the
> > WEP check, that can be easily accomplished by checking for 6ghz when we
> > define wep_ok, with the additional benefit of not exposing more WEP
> > specific things outside of CONFIG_WEP.
> >
>
> This change does not really modify the AP elements. Instead, it removes configurations that are no allowed on 6GHz to prevent starting a connection flow with invalid AKMs/ciphers/configuration. I think that it is preferrable to do this early during the candidate selection for association.
>
> Regards,
>
> Ilan.
More information about the Hostap
mailing list