88w9098 device connection problem with p136.54

CupOfTea · ‎08-16-2023

We are observing a device connection problem with p136.54.

Note that if we use p126.15, we don't have this connection issue, but there are other issues with p126, which prompted us to post this: https://community.nxp.com/t5/i-MX-Processors/88w9098-association-and-IOCTL-failed-build-p126/m-p/170...

The following files are attached to show how a device connection fails on p136.54:

wifi-debug.zip : scripts and logs to demonstrate the problem.
moal_a.txt : This is our moal.conf
wifi_mod_para.txt: This is our wifi_mod_para.conf

Inside the wifi-debug.zip the files are:

bad.sh : Script to connect to the device that fails.
good.sh : Script to connect to the device that succeeds.
failure-report.sh : Outputs for the good/bad tests.
iw-scan.log : iw scan output for the two devices.
iw-scan.sh : Script to perform the iw scan.
scan_ap : AP scan script used by good.sh and bad.sh.

CupOfTea · ‎08-21-2023

p136.54 doesn't seem to connect to the problem device with wpa_supplicant. I also tried p126.15 with wpa_supplicant and it connects.

I used the following command to start wpa_supplicant:

wpa_supplicant -dd -i sta0 -c /etc/wpa_supplicant.conf -Dnl80211

Since the TP Link device in question doesn't have a password, I didn't change wpa_supplicant.conf.

I've attached wpa_supplicant log and also the output from wpa_cli session.

Christine_Li · ‎08-22-2023

Hi, @CupOfTea

Thanks for your trying.

I checked your logs and saw that:

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

nl80211: Connect request send successfully
sta0: Setting authentication timeout: 10 sec 0 usec
Not configuring frame filtering - BSS 00:00:00:00:00:00 is not a Hotspot 2.0 network
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=ForceAuthorized
RTM_NEWLINK: ifi_index=3 ifname=sta0 wext ifi_family=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK: ifi_index=3 ifname=sta0 wext ifi_family=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK: ifi_index=3 ifname=sta0 wext ifi_family=0 ifi_flags=0x1003 ([UP])
nl80211: Event message available
nl80211: Drv Event 46 (NL80211_CMD_CONNECT) received for sta0
nl80211: Connect event (status=1 ignore_next_local_disconnect=0)
sta0: Event ASSOC_REJECT (12) received
sta0: CTRL-EVENT-ASSOC-REJECT bssid=00:00:00:00:00:00 status_code=1
CTRL-DEBUG: ctrl_sock-sendmsg: sock=14 sndbuf=12582912 outq=0 send_len=61
CTRL_IFACE monitor sent successfully to /tmp/wpa_ctrl_3397-2\x00
sta0: Radio work 'connect'@0xaaaaf10afad0 done in 0.027762 seconds
sta0: radio_work_free('connect'@0xaaaaf10afad0): num_active_works --> 0
Added BSSID 50:c7:bf:9d:09:cc into blacklist
Continuous association failures - consider temporary network disabling
sta0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="TP-LINK_Smart Plug_09CC" auth_failures=4 duration=60 reason=CONN_FAILED
CTRL-DEBUG: ctrl_sock-sendmsg: sock=14 sndbuf=12582912 outq=0 send_len=112
CTRL_IFACE monitor sent successfully to /tmp/wpa_ctrl_3397-2\x00
sta0: Blacklist count 7 --> request scan in 10000 ms

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

It seems that our associate request is rejected by AP side.

Could you please help to check your AP side? And have a try with WPA/WPA2 Personal security with a password? Or check it with another AP?

If it still fails to connect, please help to provide Wi-Fi sniffer logs then we check what happened during association.

Best regards,

Christine.

CupOfTea · ‎08-22-2023

Do you have a preferred wifi sniffer?

Christine_Li · ‎08-22-2023

Hi, @CupOfTea

We prefer to pcapng format Wi-Fi sniffer because we usually use Wireshark to open sniffer logs.

Best regards,

Christine.

CupOfTea · ‎08-22-2023

With p136.54 the driver is able to connect successfully to all sorts of APs.

The device in question is a TP Link switch after it has been reset. It doesn't have a password. We don't have debug access to the TP Link device.

With p136 we are not able to connect to this TP Link problem device. With p126 we are able to connect to the device. It seems that there might be a regression on p136.

We will look into getting wifi sniffer logs.

CupOfTea · ‎08-23-2023

I've attached .zip file containing Wireshark .pcapng.

The log is quite noisy, but scoping source and destination to TP-Link should clear the logs.

Christine_Li · ‎08-23-2023

Hi, @CupOfTea

Thanks for providing me the sniffer log.

I checked your log, but could not find any information about this AP: 50:c7:bf:9d:09:cc (SSID='TP-LINK_Smart Plug_09CC' ).

I also filtered by Azurewave module MAC:14:13:33:6b:7e:8e (get this MAC from your previous wpa_supplicant.log). But I could not see any association process in the given sniffer log.

So I want to confirm with you:
1. Are you still using the same module with last time provided wpa_supplicant.log and wpa_cli.log?

Because I filter this：14:13:33:6b:7e:8e MAC address(should be your Azurewave module STA MAC), there is no any communication with this AP: 50:c7:bf:9d:09:cc (SSID='TP-LINK_Smart Plug_09CC' )

2. Are you still using this TP-LINK AP: 50:c7:bf:9d:09:cc (SSID='TP-LINK_Smart Plug_09CC' )

3.Could you please provide one set of dmesg log or wpa_supplicant.log(like last time) and sniffer log which captured at the same time and also make sure it includes the failed connection process?

With time synced full logs, we can proceed the analysis process.

Best regards,

Christine.

CupOfTea · ‎08-29-2023

Here's a new Wireshark log. I removed the other TP Link device and also used a location with less wifi noise.

Christine_Li · ‎08-30-2023

Hi, @CupOfTea

I am so sorry, I still can not find any information about this AP(TP-LINK_Smart Plug_09CC 50:c7:bf:9d:09:cc) in this time sniffer log even I tried with scoping source and destination and filtering by MAC address.

Could you please help to double confirm in your side?

And also, after confirmed, please help to provide full time synced logs(dmesg log with drvdbg=0x20037 parameter when you load Wi-Fi driver and Sniffer), not only sniffer log.

Please refer below filter screenshot:

1. reorder according to destination:

2. reorder according to source:

3. Filter by AP's MAC address:

Best regards,

Christine.

Christine_Li · ‎09-03-2023

HI, @CupOfTea

Could you please help to double confirm in your side?

And also, after confirmed, please help to provide full time synced logs(dmesg log with drvdbg=0x20037 parameter when you load Wi-Fi driver and Sniffer), not only sniffer log.

Best regards，

Christine.

Christine_Li · ‎09-04-2023

HI, @CupOfTea

Is there any updates on the logs?

Best regards，

Christine.

Christine_Li · ‎09-05-2023

HI, @CupOfTea

Is there any updates on the logs?

Best regards，

Christine.

Christine_Li · ‎09-06-2023

HI, @CupOfTea

Is there any updates on the logs?

Best regards，

Christine.

Christine_Li · ‎09-07-2023

HI, @CupOfTea

Is there any updates on the logs?

Best regards，

Christine.

Christine_Li · ‎08-22-2023

Hi, @CupOfTea

Thanks for your feedback. Sorry to avoid misunderstanding, I have to double confirm with you:

On p136.54, only the connection to this TP Link switch has problem , but can connect to other AP successfully. But on p126, can connect to this TP Link switch successfully.

Right?

Best regards,

Christine.

CupOfTea · ‎08-23-2023

Correct

Christine_Li · ‎08-17-2023

Hi, @CupOfTea

1. Are you sure 88W9098 FW is loaded successfully?

I checked your wifi_mod_para.txt (wifi_mod_para.txt: This is our wifi_mod_para.conf), there is even no fw_name parameter in this conf file.

Please help to double confirm this information.

2.Could you please help to check the connection with wpa_supplicant other than mlanutl? And also please help to provide the full dmesg logs(with drvdbg = 0x20037 when you load driver to enable debug logs. )

Like below:

wpa_passphrase "TP-LINK_Smart Plug_09CC" "YOUR PASSWORD" >> /etc/wpa_supplicant.conf

wpa_supplicant -d -B -i mlan0 -c /etc/wpa_supplicant.conf -Dnl80211

Best regards,

Christine.

Christine_Li · ‎08-20-2023

Hi, @CupOfTea

Does the p136.54 release work well and connect to AP successfully with wpa_supplicant commands?

Best regards,

Christine.