You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I hope this is the right place to report this issue although I noticed the failure somewhere else downstream while trying to use HOOBS.
Using the capture portal I've tried connecting to a mixed WPA2/WPA3 router from a stock RPi 3B+ but it would constantly fail to do so. After hooking up a monitor and looking around a bit I've noticed that nmcli seems to assume that the key management shall be SAE, however my board does not support it.
nmcli device wifi list result:
iw phy for the supported ciphers of my RPi:
As you can see 00-0F-AC:8 is missing, which is the suite used for SAE.
After manually fiddling with nmcli and changing wifi-sec.key-mgmt of the broken connection to wpa-psk everything started working properly.
Would it be possible to automatically handle this from inside the module, in case the board does not support the default key management suite chose by nmcli or should I just do it myself at a higher level?
Setting the key management during connection, based on board capabilities would be the best imo, however downgrading to a lesser one if the first connection attempt fails should also work (e.g. sae fails -> attempt wep-psk and so on).
Thanks!
The text was updated successfully, but these errors were encountered:
Hello,
I hope this is the right place to report this issue although I noticed the failure somewhere else downstream while trying to use HOOBS.
Using the capture portal I've tried connecting to a mixed WPA2/WPA3 router from a stock RPi 3B+ but it would constantly fail to do so. After hooking up a monitor and looking around a bit I've noticed that nmcli seems to assume that the key management shall be SAE, however my board does not support it.
nmcli device wifi list
result:iw phy
for the supported ciphers of my RPi:As you can see
00-0F-AC:8
is missing, which is the suite used for SAE.After manually fiddling with nmcli and changing
wifi-sec.key-mgmt
of the broken connection towpa-psk
everything started working properly.Would it be possible to automatically handle this from inside the module, in case the board does not support the default key management suite chose by nmcli or should I just do it myself at a higher level?
Setting the key management during connection, based on board capabilities would be the best imo, however downgrading to a lesser one if the first connection attempt fails should also work (e.g. sae fails -> attempt wep-psk and so on).
Thanks!
The text was updated successfully, but these errors were encountered: