11nWPA2 test case failure in QTT

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

11nWPA2 test case failure in QTT

4,747 Views
Abhijeet_Therokar
Contributor I

Hello NXP team,

We are performing WiFi certication for W8897 chipset having driver release package
SD-WLAN-SD-BT-8897-AO_LINUX_4_9_70-BG4CT-W15.68.19.p59-15.26.19.p59-C4X15698_B0B1-GPL.zip running on Android 11 OS.
While performing QTT test cases mentioned below:
1. CT_Security_WPA2Personal_STA_RSNEBoundsVerification-FTPSKAKM_10280_1,
2. CT_Security_WPA2Personal_STA_RSNEBoundsVerification-MultiAKM_10278_1,
WFA lab reported 'STAUT is not able to connect to AP' in case of 11nWPA2.

Kindly help us to identify the issue.

Attached log files of the failed test items.

PS: while looking into sniffer captures we have found the below error in association request frame.

Error_in_capture.jpg

Thanks & Regards,
Abhijeet Therokar

Labels (2)
0 Kudos
Reply
24 Replies

3,968 Views
nandan-khant
Contributor II

Hello @weidong_sun,

This two test cases are passed. You can close the case.

Thanks for the support.

Thanks and Regards,

Nandan Khant

0 Kudos
Reply

3,963 Views
weidong_sun
NXP TechSupport
NXP TechSupport

Hello @nandan-khant 

 

OK, good job!

Thanks for your feedback!

 

Regards,

weidong

0 Kudos
Reply

4,069 Views
nandan-khant
Contributor II

Hello @weidong_sun,

Please ask the internal team to share the following details:
1. wpa_supplicant.conf (Standard/Ideal/Recommended/Verified)

2. Steps to be executed for the test case using CLI as well as detailed commands.

Thanks and Regards,

Nandan Khant

0 Kudos
Reply

4,012 Views
weidong_sun
NXP TechSupport
NXP TechSupport

Hi @nandan-khant ,

 

check below, please!

================================

Please find the supplicant.conf as attached.

Also, the configuration same as supplicant.conf can be given through cli as below:

  1. scan
  2. scan_results
  3. add_network
  4. set_network 0 ssid " "
  5. set_network 0 ieee80211w 1
  6. set_network 0 key_mgmt WPA-PSK
  7. set_network 0 proto RSN
  8. set_network 0 pairwise CCMP
  9. set_network 0 group CCMP
  10. set_network 0 psk "12345678"
  11. enable_network 0
  12. select_network 0

Also, please ask customer to check with driver load parameter auto_ds=2 and ps_mode=2 and share the observation.

=============================

 

Regards,

weidong

4,058 Views
weidong_sun
NXP TechSupport
NXP TechSupport

Hello @nandan-khant ,

 

I'm working internally to get this details. I will update here as soon as I have the details.

 

Regards,

weidong

0 Kudos
Reply

4,024 Views
nandan-khant
Contributor II

Hello @weidong_sun,

Please check with the internal team and push to get the details as soon as possible.

This is a blocker for us.

Thanks and Regards,

Nandan Khant

0 Kudos
Reply

4,325 Views
weidong_sun
NXP TechSupport
NXP TechSupport

Hello @Abhijeet_Therokar ,

 

For hostapd.conf & wpa_supplicant.conf , which one is configured by yourself or both?

Because if they are from WFA lab, we don't need to check it. if not, we will help you check it.

So tell me, please!

 

Regards,

weidong

0 Kudos
Reply

4,316 Views
Abhijeet_Therokar
Contributor I

Hi @weidong_sun,

The files used during the testing are attached and shared with you, both are updated by us only.Requesting you to please share the files and check the details with internal team.
This is critical issue for customer and they need a fix for this ASAP.

BR,

Abhijeet

0 Kudos
Reply

4,303 Views
weidong_sun
NXP TechSupport
NXP TechSupport

Hello @Abhijeet_Therokar ,

 

I have shared your questions and materials/logs with internal team.

But I have a question on your test:

>>both are updated by us only.

It means that wpa_supplicant.conf & hostapd.conf are both written yourself. Then provide them to WFA lab.

So my question: 

Since you are testing STA,  Standard Access Piont for test should be provided by WFA lab. why do you configure the hostapd.conf?

 

Regards,

weidong

Tags (1)
0 Kudos
Reply

4,294 Views
Abhijeet_Therokar
Contributor I

Hi @weidong_sun,

Can you put the ticket priority as critical, as this issue is impacting timeline, we will need quick replies on this.

BR,

Abhijeet

0 Kudos
Reply

4,249 Views
weidong_sun
NXP TechSupport
NXP TechSupport

Hello @Abhijeet_Therokar ,

 

I got feedback from internal team, check it, please!

=========================================

Can you please check if customer is using GUI to connect to the AP?

Can you please ask customer to connect to AP using command line?

 

When running QTT in manual mode, it will give the contents of conf file on screen while configuring DUT. We can use this conf to create a wpa_supplicant.conf file(as per QT tool).

 

Then we can use below command from command line to connect:

./wpa_supplicant -Dnl80211 -i wlan0 -c wpa_supplicant.conf

=========================================

 

Regards,

weidong

0 Kudos
Reply

4,240 Views
Abhijeet_Therokar
Contributor I

Hi @weidong_sun,

1. Can you please ask the internal team for the root cause of the issue?
2. We are using GUI. How it will affect the test case execution? Is it mandatory to use CLI for both of the test cases?

Kindly help to share the feedback and updates from internal team as soon as possible.

BR,

Abhijeet

0 Kudos
Reply

4,230 Views
weidong_sun
NXP TechSupport
NXP TechSupport

Hello @Abhijeet_Therokar ,

 

See below, please!

===============================

When using GUI approach, STAUT will follow the AP configuration. AP has truncated/modified RSNE contents.

This should not happen for the mentioned test cases. So as mentioned in previous comment we have to use wpa_supplicant/CLI to connect the STAUT to the AP.

===============================

 

Regards,

weidong

0 Kudos
Reply

4,215 Views
Abhijeet_Therokar
Contributor I

Hi @weidong_sun,

Is there any NXP document where all the above things are mentioned?

We do need a valid point/statement/proof that while performing the test cases we have to use the CLI approach in parallel.

also,

======================================
When using GUI approach, STAUT will follow the AP configuration. AP has truncated/modified RSNE contents.

This should not happen for the mentioned test cases. So as mentioned in previous comment we have to use wpa_supplicant/CLI to connect the STAUT to the AP.

======================================
any supportive document for the above points.


BR,
Abhijeet

0 Kudos
Reply

4,141 Views
Abhijeet_Therokar
Contributor I

Hi @weidong_sun,

Thanks for your inputs.

Also, I did follow whatever the internal team has suggested till now.
Still ended up with the same results as mentioned in a very first comment while raising the ticket, no progress has been observed.

It will be helpful if we speed this up, we have already missed the timeline for this issue.

Kindly check with the firmware and driver side also, if anything is wrong at these ends. Also, you can guide us in the same case.

 

Thanks & BR,

Abhijeet Therokar

0 Kudos
Reply

4,127 Views
weidong_sun
NXP TechSupport
NXP TechSupport

Hello @Abhijeet_Therokar ,

 

I got the feedback from internal team just now, check it, please!

================================

This might not be needed to documented as CLI approach is used by our internal team to test this case. However, We received updates from the internal team that customer can use the GUI/supplicant.conf approach as well.

 

Customer needs to update the network block of the supplicant.conf from the QTT tool which will display the configurations like (ssid, security related details) while running the test case.

Also, our internal team do not use the oce parameter in the supplicant.conf. Can you please ask customer to verify with the modified supplicant.conf?

 

Also, if the test is failing please help to share the supporting logs, dmesg, QTT logs and air capture.

====================================

 

Regards,

weidong

0 Kudos
Reply

4,123 Views
Abhijeet_Therokar
Contributor I

Hi @weidong_sun,

Below are the wpa_supplicant.conf and sniffer_captures files when we tried using the attached wpa_supplicant.conf file i.e. without the oce parameter in the network block.

We have observed the same issue.

i.e. [Expert Info (Error/Protocol): FT AKM suite is prohibited for non-FT association request]

Awaiting response.

Thanks and BR,

Abhijeet Theorkar

0 Kudos
Reply

4,092 Views
weidong_sun
NXP TechSupport
NXP TechSupport

Hello @Abhijeet_Therokar ,

 

See below, please!

==========================

The last shared wpa_supplicant_and_sniffer_captures, do not match. Supplicant is showing WPA-PSK, while the sniffer is FT-PSK.

==========================

 

Regards,

weidong

0 Kudos
Reply

4,114 Views
weidong_sun
NXP TechSupport
NXP TechSupport

Hello @Abhijeet_Therokar ,

 

shared it with internal team, and got feedback from them:

===========================

Sure, let me go through the logs. Also, do you have the driver load parameters used by the customer? Can you share the same?

===========================

Regards,

weidong

0 Kudos
Reply

4,104 Views
Abhijeet_Therokar
Contributor I

Hi @weidong_sun,

The recent logs which we provided are not from the standard test lab, these are the logs from the test we performed at our end.

We will request our customer to perform the test as suggested by the NXP team, and get back to you with the results from the standard test lab.

Thanks & BR,

Abhijeet Therokar

0 Kudos
Reply