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.

WL1807MOD: WL1807MOD

Part Number: WL1807MOD
Other Parts Discussed in Thread: WL1837

Wifi chip get disconnected (associated, disassociated) When I connect to the tp link router in 5GHZ with wpa3 security. This issue is not seen in 5GHZ with WPA2 and WPA.

WPA_supplicant conf details:

root@s40-bigbend-v1:~# cat  /lcc/data/wpa_supplicant.conf

ctrl_interface=/var/run/wpa_supplicant

update_config=1

country=US

network={

        ssid="TP-Link_F1FA_5G"

        scan_ssid=1

        psk="Pdr!600iCom"

        key_mgmt=SAE

        ieee80211w=2

}

Version details:

  wpa_supplicant -Dnl80211 -iwlan0 -c/etc/wpa_supplicant.conf

root@s40-bigbend-v1:/lcc/data/logs/debug# wpa_supplicant -v

wpa_supplicant v2.9

Copyright (c) 2003-2019, Jouni Malinen <j@w1.fi> and contributors

 

 

root@s40-bigbend-v1:/lcc/data/logs/debug# wpa_supplicant -dd -B -u -iwlan0 -c/lcc/data/wpa_supplicant.conf -s

[  877.667913] wlcore: PHY firmware version: Rev 8.2.0.0.246

[  877.831249] wlcore: firmware booted (Rev 8.9.0.0.90)

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500  metric 1

        inet6 fe80::fe45:c3ff:fe34:58f6  prefixlen 64  scopeid 0x20<link>

        ether fc:45:c3:34:58:f6  txqueuelen 1000  (Ethernet)

        RX packets 42  bytes 7336 (7.1 KiB)

        RX errors 0  dropped 0  overruns 0  frame 0w

        TX packets 95  bytes 13614 (13.2 KiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Log statement:

Please look at the attachments

always getting this error  for wpa3

wlan0: Request to deauthenticate - bssid=60:a4:b7:71:f1:f9 pending_bssid=00:00:00:00:00:00 reason=2 (PREV_AUTH_NOT_VALID) state=COMPLETED

wlan0.txt

wlan0_gateway1.zip

  • Hi Viswa,

    On the TP-Link, is it successful if you select "Auto" in the Version selction? Leave Security as is. 

  • Hi Sabeeh Khan,
     I changed it auto and same behavior (disconnect observed)

    60:a4:b7:71:f1:f9 5765 -31 [WPA2-PSK+SAE-CCMP][WPS][ESS] TP-Link_F1FA_5G
    root@s40-bigbend-v1:/lcc/apps/bin# [102712.648262] wlan0: authenticate with 60:a4:b7:71:f1:f9
    [102712.660072] wlan0: send auth to 60:a4:b7:71:f1:f9 (try 1/3)
    [102712.701683] wlan0: authenticated
    [102712.707895] wlan0: associate with 60:a4:b7:71:f1:f9 (try 1/3)
    [102712.757396] wlan0: RX AssocResp from 60:a4:b7:71:f1:f9 (capab=0x1811 status=0 aid=2)
    [102712.771624] wlan0: associated
    [102712.949283] wlcore: Association completed.
    [102715.452811] wlan0: deauthenticating from 60:a4:b7:71:f1:f9 by local choice (Reason: 2=PREV_AUTH_NOT_VALID)
    [102718.979908] wlan0: authenticate with 60:a4:b7:71:f1:f9
    [102718.989550] wlan0: send auth to 60:a4:b7:71:f1:f9 (try 1/3)
    [102719.031352] wlan0: authenticated
    [102719.037971] wlan0: associate with 60:a4:b7:71:f1:f9 (try 1/3)
    [102719.086751] wlan0: RX AssocResp from 60:a4:b7:71:f1:f9 (capab=0x1811 status=0 aid=2)
    [102719.104703] wlan0: associated
    [102719.347173] wlcore: Association completed.
    [102722.975060] wlan0: deauthenticating from 60:a4:b7:71:f1:f9 by local choice (Reason: 2=PREV_AUTH_NOT_VALID)
    [102726.478083] wlan0: authenticate with 60:a4:b7:71:f1:f9
    [102726.492775] wlan0: send auth to 60:a4:b7:71:f1:f9 (try 1/3)
    [102726.533881] wlan0: authenticated
    [102726.547845] wlan0: associate with 60:a4:b7:71:f1:f9 (try 1/3)
    [102726.597607] wlan0: RX AssocResp from 60:a4:b7:71:f1:f9 (capab=0x1811 status=0 aid=2)
    [102726.624006] wlan0: associated
    [102726.832041] wlcore: Association completed.
    [102729.685005] wlan0: deauthenticating from 60:a4:b7:71:f1:f9 by local choice (Reason: 2=PREV_AUTH_NOT_VALID)
    [102733.380711] wlan0: authenticate with 60:a4:b7:71:f1:f9
    [102733.388451] wlan0: send auth to 60:a4:b7:71:f1:f9 (try 1/3)
    [102733.429582] wlan0: authenticated
    [102733.437868] wlan0: associate with 60:a4:b7:71:f1:f9 (try 1/3)
    [102733.588468] wlan0: RX AssocResp from 60:a4:b7:71:f1:f9 (capab=0x1811 status=0 aid=2)
    [102733.604321] wlan0: associated
    [102733.792916] wlcore: Association completed.

    When I connected the laptop to the same router and pined to the google no packet loss or disconnect observed.

    This issue is not seen 2.4GHZ wpa3.

  • Hi Viswa, 

    What kernel version are you on? Did you apply our patches following our guide from here: https://www.ti.com/lit/swru561 

  • Hi Sabeeh Khan,

    We are using the kernel 5.4.56. Whether the patch is applicable for this kernel?

    root@s40-bigbend-v1:/lcc/data# uname -r
    5.4.56


    For the TP-link router issue is observed
    62:a4:b7:51:f1:f9 5765 -32 [WPA2-SAE-CCMP][ESS] TP-Link_Guest_F1FA_5G
    root@s40-bigbend-v1:/lcc/data# wpa_supplicant -B -u -iwlan0 -c/lcc/data/wpa_supplicant.conf -s
    [ 1040.496865] wlcore: PHY firmware version: Rev 8.2.0.0.246
    [ 1040.661408] wlcore: firmware booted (Rev 8.9.0.0.90)
    root@s40-bigbend-v1:/lcc/data# [ 1044.319677] wlan0: authenticate with 62:a4:b7:51:f1:f9
    [ 1044.332889] wlan0: send auth to 62:a4:b7:51:f1:f9 (try 1/3)
    [ 1044.507099] wlan0: authenticate with 62:a4:b7:51:f1:f9
    [ 1044.510914] wlan0: send auth to 62:a4:b7:51:f1:f9 (try 1/3)
    [ 1044.606131] wlan0: authenticated
    [ 1044.618255] wlan0: associate with 62:a4:b7:51:f1:f9 (try 1/3)
    [ 1044.656501] wlan0: RX AssocResp from 62:a4:b7:51:f1:f9 (capab=0x811 status=0 aid=1)
    [ 1044.670903] wlan0: associated
    [ 1044.847540] wlcore: Association completed.
    [ 1044.853449] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 1047.285676] wlan0: deauthenticating from 62:a4:b7:51:f1:f9 by local choice (Reason: 2=PREV_AUTH_NOT_VALID)
    [ 1050.936217] wlan0: authenticate with 62:a4:b7:51:f1:f9
    [ 1050.942730] wlan0: send auth to 62:a4:b7:51:f1:f9 (try 1/3)
    [ 1050.984404] wlan0: authenticated


    If we connect the laptop to the Link_Guest_F1FA_5G , no internet packet loss or disconnect were observed.


    when we connect the wifi chip to the D link router no issues observed
    bc:22:28:bc:f9:ea 5220 -39 [WPA2-SAE-CCMP][ESS] Viswa
    root@s40-bigbend-v1:/lcc/data# wpa_cli -iwlan0 status
    bssid=bc:22:28:bc:f9:ea
    freq=5220
    ssid=Viswa
    id=0
    mode=station
    wifi_generation=4
    pairwise_cipher=CCMP
    group_cipher=CCMP
    key_mgmt=SAE
    pmf=2
    mgmt_group_cipher=BIP
    sae_group=19
    wpa_state=COMPLETED
    p2p_device_address=fc:45:c3:34:58:f7
    address=fc:45:c3:34:58:f6
    uuid=7ef65b6e-6baa-58cb-b2f0-c481a044772a

  • Hi Viswa,

    The patches are for kernel 4.19, but some of them will cleanly apply. Those that do not apply, you can revert or remove.

  • Hi Sabeeh,

     We are not using this patch for our kernel. This issue happens only in the tp link router.

    Regards,

    Viswa

  • Hi Viswa,

    Are you saying that your isues are only experienced when WPA3-SAE is enabled on this tp link router? In other words, if you use another router with WPA3-SAE everything works fine?

  • Hi Sabeeh Khan,
       Yes, 

    TP link router + WIFI chip  in 5GHz wpa3-sae : issue observed
    TP link router + WIFI chip  in 2,4GHz wpa3-sae : issue not observed.
    TP link router + Laptop  in 5GHz wpa3-sae : issue not observed.
    TP link router + Laptop  in 2,4GHz wpa3-sae : issue not 
    observed.
    D link router + WIFI chip  in 5GHz wpa3-sae : issue not observed

  • OK understood.

    In order to debug this issue further, we will need to see wifi logs. Could you please post a wireshark capture log of the connection transaction between the WL1837 and the TP link router?

  • Hi Sabeeh khan,
    I have shared the wireshark log in ticket (wlan0_gateway1.zip) . please let me know if that log is not sufficient for your analysis.

  • Hi Viswa,

    Thanks for sharing. I will review these and get back to you. To be clear, did you try applying the listed patches? Here is a similar thread where patches were applied for kernel 5.4. Without these patches, I won't be able to debug properly. I need to ensure we have the same driver. 

  • Hi ,

    Thanks for the information. but when we opened the patches folder, we dont see any relevant content for 5.4 kernel. can you pl point out if we miss anything here?

    Screenshot attached for your reference. Thanks!.

    BR,

    Anantha R

    a simi
  • Please find one more wire shark log captured for long runwlan0_5GHZ.zip