• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 41 subscribers
  • Views 455 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC3301: WiFi Station mode in WPA3 not working

Binson Binoy
Prodigy 130 points
Part Number: CC3301

Tool/software:

hi,

I'm facing an issue when trying to connect my CC3301 Wi-Fi device in station mode to my Pixel 8 smartphone using WPA3-Personal security with the SAE authentication method. I am using the following command to establish the connection:

./sta_connect.sh -n Pixel_8 -s SAE -p 12345678

However, the connection attempt fails, and I get the following error in the log:


root@am62xx-art:/usr/share/cc33xx# ./sta_start.sh
root@am62xx-art:/usr/share/cc33xx# Successfully initialized wpa_supplicant


root@am62xx-art:/usr/share/cc33xx# ./sta_connect.sh -n Pixel_8 -s SAE -p 12345678
./sta_connect.sh: line 58: =2: command not found
Connect to SSID: Pixel_8, sec type: SAE, key: 12345678, pmf:
netid=0
==============================================
Set password: 12345678
OK
Line 0: invalid key_mgmt 'SAE'
Line 0: no key_mgmt values configured.
FAIL
OK
OK
root@am62xx-art:/usr/share/cc33xx#


it already shows its supported key management as,

Security type supported: NONE, WPA-PSK, SAE, WPA-EAP, WPA-EAP-SHA256

As SAE is already listed the device hesitates to connect.

After that,I need to set my device (cc3301) in AP mode in the same WPA3 authentication, need the correct hostapd.conf for setting up WPA3-Personal in AP mode on the CC3301.
please reply as soon as possible.

Regards,

Binson Binoy

  • +1
    Expert 1301 points

    Is your supplicant built with CONFIG_SAE?

  • 0 in reply to Dean Ramsier
    Prodigy 130 points

    Can you please share any document to build the supplicant with CONFIG_SAE.

  • 0 in reply to Binson Binoy
    Expert 1301 points

    The file 'defconfig' in the wpa_supplicant directory contains the configuration options for the supplicant.  You need to make sure it is configured as appropriate for the functionality you desire.

    There is a 'defconfig' file in the hostapd directory also, which contains the configuration options for hostapd.

  • 0 in reply to Binson Binoy
    Prodigy 130 points

    root@am62xx-art:/usr/share/cc33xx# ./sta_start.sh

    succesfully initiated wpa_supplicant

    root@am62xx-art:/usr/share/cc33xx# ./sta_connect.sh -n Pixel_8 -s SAE -p 12345678
    ./sta_connect.sh: line 58: =2: command not found
    Connect to SSID: Pixel_8, sec type: SAE, key: 12345678, pmf:
    netid=0
    ==============================================
    Set password: 12345678
    OK
    Line 0: invalid key_mgmt 'SAE'
    Line 0: no key_mgmt values configured.
    FAIL
    OK
    OK

    This is the issue which arises while connecting to WPA3.

  • 0 in reply to Dean Ramsier
    Prodigy 130 points

    Hi Dean,

    Thank you for your reply i tried the same for wpa_supplicant and hostapd and added the executables to usr/sbin of my root still the sam issue arises. I think i still miss something.

  • 0 in reply to Dean Ramsier
    Prodigy 130 points

    Thank you so much Dean, your reply helped me to think about the hostapd to build in the SAE configurations, but still I missed some configuration and later I added the below configuraions.

    # Simultaneous Authentication of Equals (SAE), WPA3-Personal
    #CONFIG_SAE=y

    # SAE Public Key, WPA3-Personal
    #CONFIG_SAE_PK=y

    # Enable WPA3's SAE handshake
    CONFIG_SAE=y

    # Enable SAE-PK. We also enable DPP so required dependencies are properly compiled.
    CONFIG_SAE_PK=y
    CONFIG_DPP=y

    After adding these in the defconfig the issue has been solved.