Re: [PATCH] Log falling back from SAE to WPA2

[Denis Kenzior <denkenz@gmail.com>]

Hi Fiona,

> 
> It's the RTL8723CS chip used in Pinephone, the rtl8723cs driver
> unfortunately still isn't in mainline. You can find it in the staging
> directory of megi's tree:
> https://codeberg.org/megi/linux/src/commit/f45c45abc5325682d06cb51c06aba1f817fba462/drivers/staging/rtl8723cs
> 
> I suspect getting the chip properly supported in mainline would be the
> best way to get SAE working. If you have hints on how to get involved in

Well, CMD_EXTERNAL_AUTH is part of the official nl80211 API.  When we 
implemented SAE there were no hw/drivers that used it that we could find.  Hence 
it isn't supported by iwd.

> that I'm curious, so far my wireless driver experience is limited to
> "add USB ID for a new device with already supported chip". ;-)

For getting it into mainline, I would start a conversation on linux-wireless 
and/or submit the driver upstream.

> 
>> There's currently no way to force WPA3-only in iwd.  Either configure
>> the AP to be WPA3 only, or have the AP enforce transition-disable bit.
>> But this typically requires iwd to connect at least once with WPA3.  See
>> 'TransitionDisable' and 'DisabledTransitionModes' in man 5 iwd.network
> 
> Good point, it should be a task for NetworkManager to make that clear to
> the user (and possibly set those options, if the user wants to enforce
> WPA3-only).
> 

Right.  NM makes many assumptions in its WiFi implementation based on how wpa_s 
works.  Some of these assumptions do not hold with iwd.

Regards,
-Denis