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: Connect to a special AP(wpa/wpa2) failed.(R5 version)

Part Number: CC3301

Tool/software:

cc3301 always unable to connect to a specific AP, the information of this AP is as follows:

AP type: TP Link Deco M9(https://www.tp-link.com/se/home-networking/deco/deco-m9-plus/v1%20(1-pack)/)

Through packet capturing, we can see that after the four-way handshake, the cc3301 initiates the disconnection for unknown reasons.

  • Hello Similar to the precious thread, can you please provide some FW logs?

    We are working on some potential fix but we would like to make sure we have all of the information.

  • Hi AB

    The CC33 trace: carrot-ispteam-r5-connect-fail-cc33.pcap


    And a 802.11 trace: carrot-ispteam-fail-r5.pcap-01.cap

    carrot-ispteam-fail-r5.pcap-01.cap.logcarrot-ispteam-r5-connect-fail-cc33.pcap.log

  • Hi,

    The cc33xx trace is no good since the logger.bin parser is not the right one. See my other thread where I directed you to the right logger.bin.

    The air sniffer is just full of RTS, CTS and ACK. I don't see any beacons from AP or station trying to scan and connect. Please make sure you see the beacons from the AP first.

    Shlomi

  • 我也遇到了同样的问题,在连接WPA3时也有问题,最后也没解决!

  • Please check this file, there is a beacon package in it.

    8551.cc3301_1.pcap.log
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    �ò�··��i:n#gԳ·C·C·�������~ڈ���~ڈ���p����w�d1··ispteam··����···$········DE ·
    ·*·2·0H`lF·s�·-···��·=········@�·�Y�3�����·���·�L···�Y�3�����·���·P�····�'�BC^b2/� ···��·P�··P�··P�·P�··P�·0·············���···~ڈ���An#g˚·!·!·P:·`·��·�~ڈ���~ڈ�����sKWx�d1··ispteam··����···$·····DE ·
    ·*·2·0H`lF·s�·-···��·=········@�·�Y�3�����·���·P�····�'�BC^b2/� ···��·P�··P�··P�·P�··P�·0·············���···~ڈ���An#g��·
    �~ڈ���An#g··!·!·P:·`·��·�~ڈ���~ڈ������VWx�d1··ispteam··����···$·····DE ·
    ·*·2·0H`lF·s�·-···��·=········@�·�Y�3�����·���·P�····�'�BC^b2/� ···��·P�··P�··P�·P�··P�·0·············���···~ڈ���An#g··
    �~ڈ���Bn#g�� !·!·P:·`·��·�~ڈ���~ڈ�������gx�d1··ispteam··����···$·····DE ·
    ·*·2·0H`lF·s�·-···��·=········@�·�Y�3�����·���·P�····�'�BC^b2/� ···��·P�··P�··P�·P�··P�·0·············���···~ڈ���Bn#g��
    �~ڈ���Bn#g<� !·!·P:·`·��·�~ڈ���~ڈ�����V�gx�d1··ispteam··����···$·····DE ·
    ·*·2·0H`lF·s�·-···��·=········@�·�Y�3�����·���·P�····�'�BC^b2/� ···��·P�··P�··P�·P�··P�·0·············���···~ڈ���Bn#g�� !·!·P·:·`·��·�~ڈ���~ڈ������gx�d1··ispteam··����···$·····DE ·
    ·*·2·0H`lF·s�·-···��·=········@�·�Y�3�����·���·P�····�'�BC^b2/� ···��·P�··P�··P�·P�··P�·0·············���···~ڈ���Bn#g·
    !·!·P·:·`·��·�~ڈ���~ڈ�����·�gx�d1··ispteam··����···$·····DE ·
    ·*·2·0H`lF·s�·-···��·=········@�·�Y�3�����·���·P�····�'�BC^b2/� ···��·P�··P�··P�·P�··P�·0·············���···~ڈ���Bn#g�
    �E`·��·�Bn#g�
    rr@�~ڈ���`·��·�~ڈ���·ispteam··��������2·����-· ·�H··#······@··�����·@ Bn#g·
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • We don't have wpa3 connection issue.

  • it is just a single beacon.

    where is all the beacons, authentication, association, EAPOL, etc...

    either you are not on the right channel or it is filtered.

  • there is EAPOL, association, authentication and deauthentication, can you see it?

  • Hi,

    Sorry, I must have missed it.

    The reason it is not able to connect is because the AP is configured to mixed mode security, i.e. TKIP+AES. See screenshot:

    In the release note, we declare support of OPEN, WPA2 and WPA3 (not WPA mixed mode).

    In the MPU side with the same chip, we did add this support so at some point I believe that it would be also added to the ThickMAC but I do not have a schedule.

    Shlomi