(In reply to Dirk Mueller from comment #11)
> thanks for the traces. so I switched to networkmanager as well, and it still
> works here just fine.
>
> however, I found this which describes the same issue, also with
> status_code=0x40 rejection:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003907
>
>
> it looks like a defect on the fritzbox side according to the analysis there,
> where WPA2+WPA3 transitional mode is not working as the AP is not indicating
> it needs 11W, while it refused to connect without it.
I've switched to wicked service instead of networkmanager and the problem is gone even with the 2.10 (standard version) wpa_supplicant
(In reply to Dirk Mueller from comment #11) /bugs.debian. org/cgi- bin/bugreport. cgi?bug= 1003907
> thanks for the traces. so I switched to networkmanager as well, and it still
> works here just fine.
>
> however, I found this which describes the same issue, also with
> status_code=0x40 rejection:
>
> https:/
>
>
> it looks like a defect on the fritzbox side according to the analysis there,
> where WPA2+WPA3 transitional mode is not working as the AP is not indicating
> it needs 11W, while it refused to connect without it.
I've switched to wicked service instead of networkmanager and the problem is gone even with the 2.10 (standard version) wpa_supplicant
Issue in Networkmanager instead?