WLCMGR doesn't try other security methods if network is 'not found' due to incorrect security configuration

[tgibson-work]

I have encountered an issue with the way wlcmgr handles 'wildcard' security when trying to connect to an access point that advertises support for WPA2 and WPA3 but whose hardware doesn't actually support the latter.

In this scenario adding the network to wlcmgr with WLAN_SECURITY_WILDCARD and attempting to connect results in wlcmgr failing to connect to the network using WPA3 security and emitting the WLAN_REASON_NETWORK_NOT_FOUND event. I have tried ensuring that both the WPA2 psk and WPA3 password are both set, however wlcmgr doesn't seem to try WPA2 when WPA3 fails.

Whilst the access point ought not to be misconfigured in the first place, the access point configuration is often not under the control of the user connecting, and to support such scenarios wlcmgr should try other security methods that are advertised such as WPA2 if the first method tried fails.

I have tested this with a Murata 1ZM and i.MX RT. The same Murata 1ZM connects fine to the problematic SSID attached to an i.MX 8 running Linux. I have confirmed using the wifi_cli code sample on the i.MX RT and using nmcli on Linux that the access point is advertising WPA2 and WPA3 for the SSID in question, however the hardware simply does not support that method of authentication which is why attempting to connect with WPA3 security fails.

Previous discussion on this issue here.

[tgibson-work]

@mcuxsusan is anyone monitoring issues on this repository?

[mcuxsusan]

@karanNXP, could you please check the open issues?