WL1807MOD: WFA - SAE-5_9_1 Ping test case Failed:

Part Number: WL1807MOD

Tool/software:

Hi,
WFA - SAE-5_9_1 Ping test case Failed: 
wpa_supplicant.conf file has the sae_pwe=2

{
    "TmsTestResult": {
        "PrimaryTestbed": {
            "Category": "AP",
            "VendorDeviceId": "Qualcomm_IPQ8074",
            "company": "Qualcomm",
            "firmware": "IPQ8074.WFA.11.3-00028-P-1",
            "model": "IPQ8074"
        },
        "TestResult": {
            "Device": "DUT",
            "Message": "NA",
            "Result": "FAIL"
        },
        "ExecutionTimeInSeconds": "0",
        "TimeStamp": "2025-07-24T15-13-31Z-08:00",
        "TmsEventId": "XXXXX",
        "TestCaseId": "SAE-5.9.1",
        "SupplementalTestbeds": [
            {
                "Category": "STA",
                "VendorDeviceId": "Broadcom_BCM4391",
                "company": "Broadcom",
                "firmware": "87.12.100-r-975793.01-3498fe66",
                "model": "BCM4391"
            },
            {
                "Category": "STA",
                "VendorDeviceId": "Broadcom_BCM4391",
                "company": "Broadcom",
                "firmware": "87.12.100-r-975793.01-3498fe66",
                "model": "BCM4391"
            }
        ],
        "Mode": "Sigma",
        "ProgramName": "WPA3-SAE",
        "PrimaryTestbedParticipantName": "TestbedCompanyName",
        "Dut": {
            "Category": "STA",
            "VendorDeviceId": "_",
            "company": "",
            "firmware": "",
            "model": ""
        },
        "TMSversion": "2.0",
        "DutParticipantName": "DUTCompanyName"
    }
}

Please find the attached log:
SAE-5_9_1.zip
  • Hi,

    not very clear. I can see on the terminal CLI that the station is able to connect but seems like it cannot get an IP address.
    There is no sniffer to show the connection, only a sniffer for the station testbed.

    Shlomi

  • Hi Shlomi,

    When I issue the below command from the putty console , I don’t see the IP is getting assigned by the router.
    sta_set_ip_config,interface,wlan0,dhcp,1,type,1

    We don’t have the dhcp package, we have only dhcpd. I have updated the details same in the ticket.

    message sta_set_ip_config,interface,wlan0,dhcp,1,type,1
    51
    last 0 last-1 0 last-2 0 last-3 0

    Inside the CLI huck block

    After File open

    Outside the new block
    sta_set_ip_config
    interface wlan0
    dhcp 1
    type 1
    sent to DUT
    entering wfaStaSetIpConfig ...
    new event
    received from DUT
    tag 11
    status,COMPLETE
    status,COMPLETE


    root@s40-bigbend-v1:/lcc/data/test_engine# dhcp
    sh: dhcp: command not found
    root@s40-bigbend-v1:/lcc/data/test_engine#

    Regards,

    Viswa

  • Hi,

    But it is not the dhcp command that needs to be run.

    dhcp is just an argument of the command that it is processing.

    And the above does seem as it is applied with no error.

    If I take as an example another test that used this command (with different parameters), I see also a good response:

    message sta_set_ip_config,interface,wlan0,dhcp,0,ip,192.165.100.111,mask,255.255.0.0 
    
     79
    last 0 last-1  0 last-2 0 last-3 0
    
    Inside the CLI huck block 
    
    After File open 
    
    Outside the new block 
    sta_set_ip_config
    interface wlan0
    dhcp 0
    ip 192.165.100.111
    mask 255.255.0.0
    sent to DUT
    entering wfaStaSetIpConfig ...
    new event 
    received from DUT
    tag 11 
    status,COMPLETE
    
     status,COMPLETE
    And in this case, I see an error of 'no such file or directory'.

    message sta_set_ip_config,interface,wlan0,dhcp,1,type,1 
    
     50
    last 0 last-1  0 last-2 0 last-3 0
    
    Inside the CLI huck block 
    
    After File open 
    
    Outside the new block 
    sta_set_ip_config
    interface wlan0
    dhcp 1
    type 1
    sent to DUT
    entering wfaStaSetIpConfig ...
    cp: cannot stat '/etc/resolv.conf': No such file or directory
    new event 
    received from DUT
    tag 11 
    status,COMPLETE
    
     status,COMPLETE

    Shlomi

  • Hi Shlomi,

       I was able to reproduce the no such file or directory issue. This issue happens only on the first time dont know know why?

    Actually, it is the link in S40.


    root@s40-bigbend-v1:/lcc/data/test_engine# ls -l /etc/resolv.conf


    lrwxrwxrwx 1 root root 18 Mar 9 2018 /etc/resolv.conf -> ../run/resolv.conf
    root@s40-bigbend-v1:/lcc/data/test_engine# [ 1142.680331] ili9881c-dsi 5a000000.dsi.0: TE pulse count observed is 1198
    new event
    status,RUNNING

    message sta_set_ip_config,interface,wlan0,dhcp,1,type,1
    51
    last 0 last-1 0 last-2 0 last-3 0

    Inside the CLI huck block

    After File open

    Outside the new block
    sta_set_ip_config
    interface wlan0
    dhcp 1
    type 1
    sent to DUT
    entering wfaStaSetIpConfig ...
    cp: cannot stat '/etc/resolv.conf': No such file or directory
    new event
    received from DUT
    tag 11
    status,COMPLETE
    status,COMPLETE

    [ 1172.680329] ili9881c-dsi 5a000000.dsi.0: TE pulse count observed is 1198
    [ 1202.680329] ili9881c-dsi 5a000000.dsi.0: TE pulse count observed is 1197
    [ 1232.680329] ili9881c-dsi 5a000000.dsi.0: TE pulse count observed is 1198
    [ 1262.680329] ili9881c-dsi 5a000000.dsi.0: TE pulse count observed is 1198
    [ 1292.680328] ili9881c-dsi 5a000000.dsi.0: TE pulse count observed is 1198
    [ 1322.680329] ili9881c-dsi 5a000000.dsi.0: TE pulse count observed is 1198
    [ 1352.680330] ili9881c-dsi 5a000000.dsi.0: TE pulse count observed is 1197
    [ 1382.680329] ili9881c-dsi 5a000000.dsi.0: TE pulse count observed is 1198
    [ 1412.680328] ili9881c-dsi 5a000000.dsi.0: TE pulse count observed is 1198
    [ 1442.680329] ili9881c-dsi 5a000000.dsi.0: TE pulse count observed is 1198
    [ 1472.680328] ili9881c-dsi 5a000000.dsi.0: TE pulse count observed is 1197
    [ 1502.680328] ili9881c-dsi 5a000000.dsi.0: TE pulse count observed is 1198
    [ 1532.680328] ili9881c-dsi 5a000000.dsi.0: TE pulse count observed is 1198
    [ 1562.680327] ili9881c-dsi 5a000000.dsi.0: TE pulse count observed is 1198

    root@s40-bigbend-v1:/lcc/data/test_engine# ls -l /etc/resolv.conf
    lrwxrwxrwx 1 root root 18 Mar 9 2018 /etc/resolv.conf -> ../run/resolv.conf
    root@s40-bigbend-v1:/lcc/data/test_engine# [ 1592.680328] ili9881c-dsi 5a000000.dsi.0: TE pulse count observed is 1197
    new event
    status,RUNNING

    message sta_set_ip_config,interface,wlan0,dhcp,1,type,1
    51
    last 0 last-1 0 last-2 0 last-3 0

    Inside the CLI huck block

    After File open

    Outside the new block
    sta_set_ip_config
    interface wlan0
    dhcp 1
    type 1
    sent to DUT
    entering wfaStaSetIpConfig ...
    new event
    received from DUT
    tag 11
    status,COMPLETE
    status,COMPLETE

    Regards,
    Viswa

    ================================
    Hi Shlomi,
    From the share console putty log, we can see that the ip address is not assigned to the wlan0 interface.

    uccl log i could see the ip address is not passed. How the DUT will get the ip address?

    2025-07-24 15:13:00.894 - INFO - DUT (192.168.250.111:9000) ---> sta_set_ip_config,interface,wlan0,dhcp,1,type,1
    2025-07-24 15:13:01.947 - INFO - DUT (192.168.250.111:9000) <-- status,COMPLETE

    wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 metric 1
    inet6 fdc7:4370:cc2a:0:661c:10ff:fe36:2dab prefixlen 64 scopeid 0x0<global>
    inet6 2001:db8:100:f101:661c:10ff:fe36:2dab prefixlen 64 scopeid 0x0<global>
    inet6 fd0e:993c:9d1d:0:661c:10ff:fe36:2dab prefixlen 64 scopeid 0x0<global>
    inet6 fe80::661c:10ff:fe36:2dab prefixlen 64 scopeid 0x20<link>
    inet6 fd19:b28f:9007:0:661c:10ff:fe36:2dab prefixlen 64 scopeid 0x0<global>
    inet6 fd18:401:85a3:0:661c:10ff:fe36:2dab prefixlen 64 scopeid 0x0<global>
    ether 64:1c:10:36:2d:ab txqueuelen 1000 (Ethernet)
    RX packets 112 bytes 8550 (8.3 KiB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 23 bytes 2651 (2.5 KiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    Regards,

    Viswa

  • ==========
    Hi Shlomi,
       sta_set_ip_config,interface,wlan0,dhcp,1,type,1 

    > This command is not setting the ip address for the wlan0 interface

    > also note we have only udhcpc pakage in our board and no dhcp client packages.

  • Hi,

    seems like the 1st step of recording the GTK and IGTK is OK when comparing to the supplicant log. Then, connection is succeeded but I do not see DHCP request from the device. This is why PING fails. you can always set is statically on the platform CLI just for the test (e.g. ifconfig wlan0 x.x.x.x). 

    Can you double check that you do not get an IP address by typing ifconfig and see?

    Regards,

    Shlomi

  • Please share me the dhcp bin file to get the ip address? we dont have dhcp package.

    root@s40-bigbend-v1:/lcc/data/test_engine# dhcpc

    -sh: dhcpc: command not found
    root@s40-bigbend-v1:/lcc/data/test_engine# dhcp
    dhcp_release dhcpcd
    root@s40-bigbend-v1:/lcc/data/test_engine# dhcp


    Regards,
    Viswa

  • Hi,

    I am almost sure we use udhcpc but let me double check.

    Shlomi

  • Hi Shlomi,
       Please let me know whether you want us to make changes and retest it.

    Regards,

    Viswa

  • Hi,

    I shared this topic over Email with ways to set the static IP.

    We also do not use DHCP since it is not implemented in the agent.

    In parallel, I am trying to see if we can add it to the agent.

    So you can proceed with setting the expected IP address in systemd and test.

    Shlomi

  • Hi Shlomi,
     We have shared the log from the reference unit.

    2262.reference-run-PMF-QT-26aug2025.zip7043.reference-run-FC-SAE-27aug2025.zip

    Regards,

    Viswa

  • Hi Shlomi,

      From the testing team has asked to look at the M3 packet of the eapol to get the IGT_key.

    I could not decrypt the wpa_key_data to check for the IGT_KEY_data?

    Please let me know how to decrypt ?

    Regards,

    Viswa
      

  • Hi,

    This is a WPA3 connection so it is a little more complicated.

    You can look at the supplicant log and fetch the PMK.

    Then in Wireshark, go to where you add the keys and add it.

    You should start seeing the decryption data but for some reason it does not always show the decryption of the EAPOL M3.

    Shlomi