WiFi scan while connected

RE: WiFi scan while connected

Simonr — Mon, 03 Feb 2025 06:58:11 GMT

Hi again Remi

Here are the firmware bins for the NCS 2.9.x release with the fixes to this issue. You should replace the binaries in nrfxlib/nrf_wifi/bin/ncs in 2.9.x with the ones uploaded here.

devzone.nordicsemi.com/.../3515.ncs.zip

Best regards,

Simon

RE: WiFi scan while connected

Simonr — Fri, 31 Jan 2025 08:46:08 GMT

Hi Remi

That is great news! I'll forward the info to the devs so they can handle it accordingly. I'm sure we can add the fix to a 2.9.x patch as well.

Best of luck going forward, and don't hesitate to make a new ticket if you run into further issues.

Best regards,

Simon

RE: WiFi scan while connected

Remi.G — Thu, 30 Jan 2025 15:18:16 GMT

This appears to fix the issue!

A full scan now works while connected, and a directed scan just on channel 165 works as well, when connected to either 2.4 or 5GHz.

The issue I was having with not being able to connect to 2.4GHz unless I specify the band explicitly also seems to have been resolved with this image. That was always unpredictable, so I can't rule out random chance, but it is encouraging.

The source of the 5833MHz jammer remains a mystery. I'm a few miles from a military airfield, so maybe radar? That's not something I need to solve.

We will likely be upgrading to NCS 2.9 in a few weeks, so you can add this to the next NCS 2.9.x if that's easier.

Thanks for all your help!

RE: WiFi scan while connected

Simonr — Thu, 30 Jan 2025 13:40:38 GMT

devzone.nordicsemi.com/.../4010.zephyr_5F00_logs_5F00_v4.hex

Hi again

After analyzing the captures we see that channel 161 is clean, and that the RSSI in this channel is close to the expected noise floor. But in channel 165 there's a tonal pick up at ~5833 MHz. The RSSI measured on this capture is ~-56dBm, while the CCA threshold is -62dBm. So he high RSSI can lead to the CCA remaining asserted and thus the DUT isn't able to win the channel contention. Attached is a .hex file that contains a fix for this issue. Please try it out to confirm whether it fixes your issue or not. We will provide a patch on top of NCS 2.8.0 without the logging if this resolves the issue on your end.

Best regards,

Simon

RE: WiFi scan while connected

Simonr — Mon, 27 Jan 2025 07:46:23 GMT

Again, thank you for your thorough feedback Remi. I agree that this sounds very strange, and find it hard to believe it's something on the DK, as we can't see this behavior when testing on our end on a DK with the same revision.

The developers are reviewing your logs now. I hope they have some more insight to share on this soon. I'll get back to you.

Best regards,

Simon

RE: WiFi scan while connected

Remi.G — Fri, 24 Jan 2025 17:08:01 GMT

Here are the logs. All runs for a configuration in the same file, separated by boot message. I reset the DK between each run.

radio_test_chan_165_bb_gain_25.txt : the first experiment

devzone.nordicsemi.com/.../radio_5F00_test_5F00_chan_5F00_165_5F00_bb_5F00_gain_5F00_25.txt

radio_test_chan_165_bb_gain_10.txt: the second experiment

devzone.nordicsemi.com/.../radio_5F00_test_5F00_chan_5F00_165_5F00_bb_5F00_gain_5F00_10.txt

For comparison, I also did a single run with gains 25 and 10 on channel 161, which does not have the scanning issue:

devzone.nordicsemi.com/.../radio_5F00_test_5F00_chan_5F00_161.txt

On channel 165 with 25 gain, I see a lot of 800 and 7FC in the data, which looks like saturation? Gain 10 seems to be in range.

Channel 161 is much lower magnitude.

So there may be a jammer at 165? I turned off all the wireless I could find, used some metal shielding, and even tried connecting the DK to a different laptop in case there was PC noise coupling through USB. Same results. That implies the noise may be coming from the nRF7002-DK itself? It also happens on our own board (I didn't run radio test, but scan fails), maybe due to similar RF design? I don't have a 5GHZ spectrum analyzer, unfortunately. Or is it possible that there's a tuning issue when the firmware accesses channel 165?

I could try buying another nRF7002-DK to see if it behaves differently. Is there a newer version of HW after v1.0.2? The product page doesn't specify.

Independent of whatever is jamming channel 165, this is still a scanning firmware issue, right? A jammed channel shouldn't be able to hang the device.

RE: WiFi scan while connected

Simonr — Fri, 24 Jan 2025 11:32:47 GMT

Thanks again Remi

We see that CCA is continuously busy on this channel for some reason and suspect some non-Wi-Fi interference on that channel is causing this. So the next step would be to capture raw data on this channel for further analyze. Can you try using the attached radio test hex file and get captures of what's going on here with an nRF7002 DK:

Config 1: Repeat the below commands 5 times and get terminal logs for analysis. Note that 16k samples will be logged to the terminal every run, indicating the channel state:
wifi_radio_test init 165
wifi_radio_test rx_lna_gain 0
wifi_radio_test rx_bb_gain 25
wifi_radio_test rx_capture_length 16000
wifi_radio_test rx_cap 0

Config 2: Repeat the below commands 5times and get terminal logs for analysis. note that 16k samples will be logged to the terminal for every run, indicating the channel state.

wifi_radio_test init 165
wifi_radio_test rx_lna_gain 0
wifi_radio_test rx_bb_gain 10
wifi_radio_test rx_capture_length 16000
wifi_radio_test rx_cap 0

Best regards,

Simon

devzone.nordicsemi.com/.../radio_5F00_test.hex

RE: WiFi scan while connected

Remi.G — Tue, 21 Jan 2025 16:23:54 GMT

Here are the logs:

devzone.nordicsemi.com/.../zephyr_5F00_logs_5F00_v3_5F00_log.txt

The "unable to allocate" messages in the bad scan are new. I also sometimes see

[00:01:27.330,322] <err> wifi_nrf: hal_rpu_event_get: Unable to alloc HAL msg for event (84 bytes)

Those may be due to the new logging.

I have two nRF7002-DK boards, both marked PCA10143 1.0.2 2023.25. Both have the same behavior. Our own board using nRF7002 also behaves the same.

I connected to the Asus AP, a Pixel8, and an iPhone SE. All show the same scan failure on channel 165. Disabled the other APs so they wouldn't interfere. I don't have a Faraday cage, but I used some metal to isolate to just the DK and a phone hotspot to eliminate the possibility that farther APs were interfering, same result.

RE: WiFi scan while connected

Simonr — Mon, 20 Jan 2025 09:01:50 GMT

Hi Remi

Another week and another patch you can try. Mainly to get more logs:devzone.nordicsemi.com/.../zephyr_5F00_logs_5F00_v3.hex

Can you also confirm if this is something you only see on one specific board or if you see this behavior on multiple DKs/boards?

Best regards,

Simon

RE: WiFi scan while connected

Remi.G — Tue, 14 Jan 2025 22:47:26 GMT

Here are the logs from zephyr_logs_v2.hex

devzone.nordicsemi.com/.../zephyr_5F00_logs_5F00_v2_5F00_log.txt

It fails the same as before on channel 165.

One new behavior, which is probably just random chance rather than a difference in this image, is that the first scan on channel 165 in this log completed. But when I scanned the same channel immediately afterwards, it didn't finish. I did multiple runs and could never get it to complete again, so seems a small chance.

RE: WiFi scan while connected

Simonr — Mon, 13 Jan 2025 08:19:05 GMT

From the logs and since we can't reproduce this using your configurations in the lab, the problem looks to be due to the environment and not AP configuration. Can you try out this .hex file as well and get the log from it? We've added a few more debug flags to get a better idea of what's going on.

devzone.nordicsemi.com/.../zephyr_5F00_logs_5F00_v2.hex

Best regards,

Simon

RE: WiFi scan while connected

Simonr — Thu, 09 Jan 2025 09:02:22 GMT

Indeed, we have not been able to reproduce it locally yet. I'm sorry the potential fix didn't help. The investigation continues then. Again, thank you for your thorough responses. They're much appreciated.

I'll get back to you with any further suggestions from our end.

Best regards,

Simon

RE: WiFi scan while connected

Remi.G — Thu, 09 Jan 2025 00:25:45 GMT

It sounds like you have not been able to reproduce this locally. I'm attaching an exported configuration from my Asus ZenMax WiFi XT8 (AX6600) (running current latest firmware 3.0.0.4.388_24688-gf94212b) in case that helps.

I haven't tried loading an external config, but if you connect to the web interface, Administration, Restore/Save/Upload Setting tab, there is a button to upload a configuration.

If it works, there will be a 2.4GHz network "Hizzulon2" and a 5GHz network "Hizzulon". I didn't export the passwords so you will probably have to set those.

There are also some mesh configs, but it should be fine if there's no mesh to connect to.

devzone.nordicsemi.com/.../Settings_5F00_ZenWiFi-AX.CFG

RE: WiFi scan while connected

Remi.G — Wed, 08 Jan 2025 23:57:00 GMT

For the new "zephyr (1).hex" file, same behavior as before, fails scan on channel 165.

Not including full log here, just the Zephyr header so you can confirm I'm running the expected image, and the command I'm executing:

*** Booting nRF Connect SDK v2.8.0-caf9929fbaeb ***
*** Using Zephyr OS v3.7.99-6c5454b22eea ***
Starting nrf7002dk with CPU frequency: 128 MHz
[00:00:00.499,359] <inf> wifi_supplicant: wpa_supplicant initialized

uart:~$ wifi connect -s Hizzulon <credentials>

... connects successfully to a 5GHz AP

uart:~$ wifi scan -b 5 -c 5:44

... successful scan

uart:~$ wifi scan -b 5 -c 5:165

... fails scan

For "zephyr_with_logs_enabled.hex", also same behavior. Here are the logs - there are some dropped messages (including the Zephyr boot banner), though no drops around the scanning. I waited between commands for some of the background periodic wpa_supp messages to appear.

uart:~$
--- 5 messages dropped ---
Starting nrf7002dk with CPU frequency: 128 MHz
[00:00:00.512,847] <dbg> wpa_supp: wpa_printf_impl: wpa_supplicant v2.11-devel
--- 11 messages dropped ---
[00:00:00.513,397] <inf> wifi_supplicant: wpa_supplicant initialized
[00:00:00.514,007] <dbg> wifi_supplicant: add_interface: Adding interface wlan0 [1] (0x200013c0)
[00:00:00.514,068] <dbg> wpa_supp: wpa_printf_impl: Calling wpa_cli: interface_add, argc: 5
[00:00:00.514,099] <dbg> wpa_supp: wpa_printf_impl: argv[0]: interface_add
[00:00:00.514,160] <dbg> wpa_supp: wpa_printf_impl: argv[1]: wlan0
[00:00:00.514,190] <dbg> wpa_supp: wpa_printf_impl: argv[2]: zephyr
[00:00:00.514,221] <dbg> wpa_supp: wpa_printf_impl: argv[3]: zephyr
[00:00:00.514,251] <dbg> wpa_supp: wpa_printf_impl: argv[4]: zephyr
[00:00:00.525,848] <dbg> wpa_supp: wpa_printf_impl: _wpa_drv_zep_set_key: priv:0x20002f08 alg 0 addr 0 key_idx 3 set_tx 0 seq 0 seq_len 0 key 0 key_len 0 key_flag 10
[00:00:00.528,900] <dbg> wpa_supp: wpa_printf_impl: _wpa_drv_zep_set_key: priv:0x20002f08 alg 0 addr 0 key_idx 4 set_tx 0 seq 0 seq_len 0 key 0 key_len 0 key_flag 10
[00:00:00.530,548] <dbg> wpa_supp: wpa_printf_impl: _wpa_drv_zep_set_key: priv:0x20002f08 alg 0 addr 0 key_idx 5 set_tx 0 seq 0 seq_len 0 key 0 key_len 0 key_flag 10
[00:00:00.532,196] <dbg> wpa_supp: wpa_printf_impl: wlan0: RSN: flushing PMKID list in the driver
[00:00:00.532,287] <dbg> wpa_supp: wpa_printf_impl: wlan0: State: DISCONNECTED -> INACTIVE
[00:00:00.532,897] <dbg> wpa_supp: wpa_printf_impl: MBO: Update non-preferred channels, non_pref_chan=N/A
[00:00:00.533,081] <dbg> wpa_supp: wpa_printf_impl: wlan0: Added interface wlan0
[00:00:00.533,172] <dbg> wpa_supp: wpa_printf_impl: wlan0: State: INACTIVE -> DISCONNECTED

uart:~$ wifi connect -s Hizzulon <credentials>
Connection requested
--- 87 messages dropped ---
[00:00:09.294,036] <dbg> wpa_supp: wpa_printf_impl: CTRL_IFACE: ENABLE_NETWORK id=0
--- 4 messages dropped ---
[00:00:09.294,128] <dbg> wpa_supp: wpa_printf_impl: wlan0: Setting scan request: 0.000000 sec
[00:00:09.294,342] <dbg> wpa_supp: wpa_printf_impl: wlan0: State: DISCONNECTED -> SCANNING
[00:00:09.294,433] <dbg> wpa_supp: wpa_printf_impl: Scan SSID - hexdump_ascii(len=8):
[00:00:09.294,464] <dbg> wpa_supp: _wpa_hexdump_ascii:
48 69 7a 7a 75 6c 6f 6e |Hizzulon
[00:00:09.294,525] <dbg> wpa_supp: wpa_printf_impl: wlan0: Include wildcard SSID in the scan request
[00:00:09.294,738] <dbg> wpa_supp: wpa_printf_impl: wlan0: Add radio work 'scan'@0x200329a0
[00:00:09.295,776] <dbg> wpa_supp: wpa_printf_impl: argv[1]: 0
[00:00:09.304,046] <dbg> wpa_supp: wpa_printf_impl: wpa_drv_zep_scan2: Scan requested - scan timeout 35 seconds
[00:00:09.305,175] <dbg> wpa_supp: wpa_printf_impl: wlan0: Control interface command 'SELECT_NETWORK 0'
[00:00:09.305,236] <dbg> wpa_supp: wpa_printf_impl: CTRL_IFACE: SELECT_NETWORK id=0
[00:00:09.305,328] <dbg> wpa_supp: wpa_printf_impl: wlan0: Setting scan request: 0.000000 sec
[00:00:09.305,541] <dbg> wpa_supp: wpa_printf_impl: wlan0: Already scanning - Reschedule the incoming scan req
[00:00:09.305,633] <dbg> wpa_supp: wpa_printf_impl: wlan0: Setting scan request: 1.000000 sec
[00:00:09.305,847] <dbg> wifi_supplicant: event_socket_handler: Passing message 47 to wpa_supplicant
[00:00:09.305,938] <dbg> wpa_supp: wpa_printf_impl: wlan0: Event SCAN_STARTED (47) received
[00:00:09.306,060] <dbg> wpa_supp: wpa_printf_impl: wlan0: Own scan request started a scan in 0.001801 seconds
[00:00:09.306,304] <dbg> wpa_supp: wpa_printf_impl: Received len: 24, msg_len:24 - CTRL-EVENT-SCAN-STARTED ->END
[00:00:10.305,847] <dbg> wpa_supp: wpa_printf_impl: wlan0: Already scanning - Reschedule the incoming scan req
[00:00:10.305,969] <dbg> wpa_supp: wpa_printf_impl: wlan0: Setting scan request: 1.000000 sec
[00:00:11.306,213] <dbg> wpa_supp: wpa_printf_impl: wlan0: Already scanning - Reschedule the incoming scan req
[00:00:11.306,304] <dbg> wpa_supp: wpa_printf_impl: wlan0: Setting scan request: 1.000000 sec
[00:00:12.306,518] <dbg> wpa_supp: wpa_printf_impl: wlan0: Already scanning - Reschedule the incoming scan req
[00:00:12.306,640] <dbg> wpa_supp: wpa_printf_impl: wlan0: Setting scan request: 1.000000 sec
--- 44 messages dropped ---
[00:00:13.929,321] <dbg> wpa_supp: wpa_printf_impl: WPA: Set own WPA IE default - hexdump(len=22): 30 14 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ac 02 80 00
[00:00:13.929,412] <dbg> wpa_supp: wpa_printf_impl: RSN: Set own RSNXE default - hexdump(len=0):��
[00:00:13.929,473] <dbg> wpa_supp: wpa_printf_impl: PSK (set in config) - hexdump(len=32): [REMOVED]
[00:00:13.929,534] <dbg> wpa_supp: wpa_printf_impl: WPA: Set PMK based on external data - hexdump(len=32): [REMOVED]
[00:00:13.929,595] <dbg> wpa_supp: wpa_printf_impl: RRM: Determining whether RRM can be used - device support: 0x50
[00:00:13.929,656] <dbg> wpa_supp: wpa_printf_impl: RRM: Adding RRM IE to Association Request
[00:00:13.930,206] <dbg> wpa_supp: wpa_printf_impl: Added supported operating classes IE - hexdump(len=10): 3b 08 80 51 52 73 76 79 7c 7d
[00:00:13.930,328] <dbg> wpa_supp: wpa_printf_impl: wlan0: Cancelling scan request
[00:00:13.930,511] <inf> wpa_supp: wlan0: SME: Trying to authenticate with fc:34:97:af:71:34 (SSID='Hizzulon' freq=5220 MHz)
[00:00:13.930,633] <dbg> wpa_supp: wpa_printf_impl: wlan0: State: SCANNING -> AUTHENTICATING
[00:00:13.934,783] <dbg> wpa_supp: wpa_printf_impl: Received len: 40, msg_len:40 - CTRL-EVENT-BSS-ADDED 0 fc:34:97:af:71:34->END
[00:00:13.934,936] <dbg> wpa_supp: wpa_printf_impl: Received len: 24, msg_len:24 - CTRL-EVENT-SCAN-RESULTS ->END
[00:00:13.935,119] <dbg> wpa_supp: wpa_printf_impl: Received len: 82, msg_len:82 - SME: Trying to authenticate with fc:34:97:af:71:34 (SSID='Hizzulon' freq=5220 MHz)->END
--- 2 messages dropped ---
[00:00:14.291,900] <dbg> wpa_supp: wpa_printf_impl: wlan0: SME: Authentication response: peer=fc:34:97:af:71:34 auth_type=0 auth_transaction=2 status_code=0
--- 90 messages dropped ---
[00:00:14.292,083] <dbg> wpa_supp: wpa_printf_impl: SME: Authentication response IEs - hexdump(len=11): dd 09 00 10 18 02 07 00 9c 00 00
--- 11 messages dropped ---
[00:00:14.292,510] <dbg> wpa_supp: wpa_printf_impl: SME: Association Request IEs - hexdump(len=52): 30 14 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ac 02 80 00 7f 0b 00 00 0a 02 00 40 40 00 00 00 20 46 05 70 00 00 00 00 3b 08 80 51 52 73 76 79 7c 7d
[00:00:14.292,694] <inf> wpa_supp: wlan0: Trying to associate with fc:34:97:af:71:34 (SSID='Hizzulon' freq=5220 MHz)
[00:00:14.337,249] <dbg> wpa_supp: wpa_printf_impl: WPA: KCK - hexdump(len=16): [REMOVED]
[00:00:14.346,069] <dbg> wpa_supp: wpa_printf_impl: wlan0: Cancelling authentication timeout
[00:00:14.346,191] <dbg> wpa_supp: wpa_printf_impl: wlan0: State: GROUP_HANDSHAKE -> COMPLETED
[00:00:14.346,343] <dbg> wpa_supp: wpa_printf_impl: wlan0: Radio work 'sme-connect'@0x200329a0 done in 0.419311 seconds
[00:00:14.346,496] <dbg> wpa_supp: wpa_printf_impl: wlan0: radio_work_free('sme-connect'@0x200329a0): num_active_works --> 0
[00:00:14.346,710] <inf> wpa_supp: wlan0: CTRL-EVENT-CONNECTED - Connection to fc:34:97:af:71:34 completed [id=0 id_str=]
[00:00:14.349,853] <dbg> wpa_supp: wpa_printf_impl: Received len: 73, msg_len:73 - WPA: Key negotiation completed with fc:34:97:af:71:34 [PTK=CCMP GTK=CCMP]->END
[00:00:14.350,006] <dbg> wpa_supp: wpa_printf_impl: Received len: 79, msg_len:79 - CTRL-EVENT-CONNECTED - Connection to fc:34:97:af:71:34 completed [id=0 id_str=]->END
[00:00:14.357,330] <inf> net_dhcpv4: Received: 192.168.1.203
Connected

uart:~$ wifi status
Status: successful
==================
State: COMPLETED
Interface Mode: STATION
Link Mode: WIFI 6 (802.11ax/HE)
SSID: Hizzulon
BSSID: FC:34:97:AF:71:34
Band: 5GHz
Channel: 44
Security: WPA2-PSK
MFP: Optional
RSSI: -55
Beacon Interval: 100
DTIM: 1
TWT: Supported
Current PHY rate : 34400

[00:00:25.801,727] <dbg> wpa_supp: wpa_printf_impl: wlan0: Control interface command 'SIGNAL_POLL'
[00:00:26.446,777] <dbg> wpa_supp: wpa_printf_impl: wpa_supp: Frame event
[00:00:26.446,929] <dbg> wifi_supplicant: event_socket_handler: Passing message 18 to wpa_supplicant
[00:00:26.446,990] <dbg> wpa_supp: wpa_printf_impl: wlan0: Event RX_MGMT (18) received
[00:00:26.447,204] <dbg> wpa_supp: wpa_printf_impl: wlan0: Received Action frame: SA=fc:34:97:af:71:34 Category=5 DataLen=40 freq=5220 MHz
[00:00:26.447,265] <dbg> wpa_supp: wpa_printf_impl: Measurement request type 5 token 144
[00:00:26.447,326] <dbg> wpa_supp: wpa_printf_impl: Beacon request: invalid operating class 0
[00:00:26.447,357] <dbg> wpa_supp: wpa_printf_impl: Beacon request: No valid channels
[00:00:26.447,479] <dbg> wpa_supp: wpa_printf_impl: wpa_supp: Send Action frame (freq=5220 MHz wait=0 ms no_cck=0)
[00:00:26.450,073] <dbg> wpa_supp: wpa_printf_impl: wpa_supp: Frame TX status event
[00:00:26.450,225] <dbg> wifi_supplicant: event_socket_handler: Passing message 16 to wpa_supplicant

uart:~$ wifi scan -b 5 -c 5:44
Scan requested

[00:00:26.450,317] <dbg> wpa_supp: wpa_printf_impl: wlan0: Event TX_STATUS (16) received
[00:00:26.450,469] <dbg> wpa_supp: wpa_printf_impl: wlan0: EVENT_TX_STATUS dst=fc:34:97:af:71:34 type=0 stype=13
[00:00:53.480,773] <dbg> wpa_supp: wpa_printf_impl: wpa_supp: Frame event
[00:00:53.480,926] <dbg> wifi_supplicant: event_socket_handler: Passing message 18 to wpa_supplicant
[00:00:53.481,018] <dbg> wpa_supp: wpa_printf_impl: wlan0: Event RX_MGMT (18) received
[00:00:53.481,201] <dbg> wpa_supp: wpa_printf_impl: wlan0: Received Action frame: SA=fc:34:97:af:71:34 Category=5 DataLen=40 freq=5220 MHz
[00:00:53.481,262] <dbg> wpa_supp: wpa_printf_impl: Measurement request type 5 token 150
[00:00:53.481,323] <dbg> wpa_supp: wpa_printf_impl: Beacon request: invalid operating class 0
[00:00:53.481,384] <dbg> wpa_supp: wpa_printf_impl: Beacon request: No valid channels
[00:00:53.481,475] <dbg> wpa_supp: wpa_printf_impl: wpa_supp: Send Action frame (freq=5220 MHz wait=0 ms no_cck=0)
[00:00:53.484,069] <dbg> wpa_supp: wpa_printf_impl: wpa_supp: Frame TX status event
[00:00:53.484,222] <dbg> wifi_supplicant: event_socket_handler: Passing message 16 to wpa_supplicant
[00:00:53.484,313] <dbg> wpa_supp: wpa_printf_impl: wlan0: Event TX_STATUS (16) received
[00:00:53.484,466] <dbg> wpa_supp: wpa_printf_impl: wlan0: EVENT_TX_STATUS dst=fc:34:97:af:71:34 type=0 stype=13
[00:01:09.455,535] <dbg> wpa_supp: wpa_printf_impl: wpa_supp: Frame event
[00:01:09.455,688] <dbg> wifi_supplicant: event_socket_handler: Passing message 18 to wpa_supplicant
[00:01:09.455,749] <dbg> wpa_supp: wpa_printf_impl: wlan0: Event RX_MGMT (18) received
[00:01:09.455,963] <dbg> wpa_supp: wpa_printf_impl: wlan0: Received Action frame: SA=fc:34:97:af:71:34 Category=5 DataLen=40 freq=5220 MHz
[00:01:09.456,024] <dbg> wpa_supp: wpa_printf_impl: Measurement request type 5 token 154
[00:01:09.456,085] <dbg> wpa_supp: wpa_printf_impl: Beacon request: invalid operating class 0
[00:01:09.456,115] <dbg> wpa_supp: wpa_printf_impl: Beacon request: No valid channels
[00:01:09.456,207] <dbg> wpa_supp: wpa_printf_impl: wpa_supp: Send Action frame (freq=5220 MHz wait=0 ms no_cck=0)
[00:01:09.458,831] <dbg> wpa_supp: wpa_printf_impl: wpa_supp: Frame TX status event
[00:01:09.458,984] <dbg> wifi_supplicant: event_socket_handler: Passing message 16 to wpa_supplicant
[00:01:09.459,075] <dbg> wpa_supp: wpa_printf_impl: wlan0: Event TX_STATUS (16) received
[00:01:09.459,228] <dbg> wpa_supp: wpa_printf_impl: wlan0: EVENT_TX_STATUS dst=fc:34:97:af:71:34 type=0 stype=13

uart:~$ wifi scan -b 5 -c 5:165
Scan requested
Scan request failed (-116)

--- 15 messages dropped ---
[00:02:15.691,192] <dbg> wpa_supp: wpa_printf_impl: wlan0: Removing interface wlan0
[00:02:15.691,436] <dbg> wpa_supp: wpa_printf_impl: wlan0: Request to deauthenticate - bssid=00:00:00:00:00:00 pending_bssid=00:00:00:00:00:00 reason=3 (DEAUTH_LEAVING) state=INTERFACE_DISABLED
[00:02:15.691,528] <dbg> wpa_supp: wpa_printf_impl: QM: Clear all active DSCP policies
[00:02:15.691,589] <inf> wpa_supp: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
[00:02:15.691,741] <dbg> wpa_supp: wpa_printf_impl: wlan0: WPA: Clear old PMK and PTK
[00:02:15.691,955] <dbg> wpa_supp: wpa_printf_impl: wlan0: BSS: Remove id 0 BSSID fc:34:97:af:71:34 SSID 'Hizzulon' due to wpa_bss_flush
[00:02:15.692,138] <dbg> wpa_supp: wpa_printf_impl: wlan0: Cancelling scan request
[00:02:15.692,230] <dbg> wpa_supp: wpa_printf_impl: wlan0: Cancelling authentication timeout
[00:02:15.692,382] <dbg> wpa_supp: wpa_printf_impl: QM: Clear all active DSCP policies
[00:02:15.692,443] <inf> wpa_supp: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
[00:02:15.692,504] <dbg> wpa_supp: wpa_printf_impl: Remove interface wlan0 from radio
[00:02:15.692,535] <dbg> wpa_supp: wpa_printf_impl: Remove radio
[00:02:17.848,602] <inf> wifi_supplicant: Network interface 1 (0x200013c0) up
--- 4 messages dropped ---
[00:02:17.848,632] <dbg> wifi_supplicant: add_interface: Adding interface wlan0 [1] (0x200013c0)
[00:02:17.848,693] <dbg> wpa_supp: wpa_printf_impl: Calling wpa_cli: interface_add, argc: 5
--- 5 messages dropped ---
[00:02:17.848,724] <dbg> wpa_supp: wpa_printf_impl: argv[0]: interface_add
[00:02:17.848,785] <dbg> wpa_supp: wpa_printf_impl: argv[1]: wlan0
[00:02:17.848,815] <dbg> wpa_supp: wpa_printf_impl: argv[2]: zephyr
[00:02:17.848,846] <dbg> wpa_supp: wpa_printf_impl: argv[3]: zephyr
[00:02:17.848,876] <dbg> wpa_supp: wpa_printf_impl: argv[4]: zephyr
[00:02:17.851,959] <dbg> wpa_supp: wpa_printf_impl: RX global ctrl_iface - hexdump_ascii(len=71):
[00:02:17.857,635] <dbg> wpa_supp: wpa_printf_impl: wpa_supp: Added 802.11b mode based on 802.11g information
[00:02:17.863,098] <dbg> wpa_supp: wpa_printf_impl: _wpa_drv_zep_set_key: priv:0x20002f08 alg 0 addr 0 key_idx 3 set_tx 0 seq 0 seq_len 0 key 0 key_len 0 key_flag 10
[00:02:17.866,058] <dbg> wpa_supp: wpa_printf_impl: _wpa_drv_zep_set_key: priv:0x20002f08 alg 0 addr 0 key_idx 4 set_tx 0 seq 0 seq_len 0 key 0 key_len 0 key_flag 10
[00:02:17.867,706] <dbg> wpa_supp: wpa_printf_impl: _wpa_drv_zep_set_key: priv:0x20002f08 alg 0 addr 0 key_idx 5 set_tx 0 seq 0 seq_len 0 key 0 key_len 0 key_flag 10
[00:02:17.869,323] <dbg> wpa_supp: wpa_printf_impl: wlan0: RSN: flushing PMKID list in the driver
[00:02:17.869,415] <dbg> wpa_supp: wpa_printf_impl: wlan0: State: DISCONNECTED -> INACTIVE
[00:02:17.870,025] <dbg> wpa_supp: wpa_printf_impl: MBO: Update non-preferred channels, non_pref_chan=N/A
[00:02:17.870,208] <dbg> wpa_supp: wpa_printf_impl: wlan0: Added interface wlan0
[00:02:17.870,300] <dbg> wpa_supp: wpa_printf_impl: wlan0: State: INACTIVE -> DISCONNECTED
uart:~$

For the 2.4GHz connection failure, here are the logs, in case they help:

uart:~$ wifi connect -s Hizzulon2 -p H1zzul0n -k 1
Connection requested
--- 87 messages dropped ---
[00:00:08.492,462] <dbg> wpa_supp: wpa_printf_impl: CTRL_IFACE: ENABLE_NETWORK id=0
--- 4 messages dropped ---
[00:00:08.492,553] <dbg> wpa_supp: wpa_printf_impl: wlan0: Setting scan request: 0.000000 sec
[00:00:08.492,797] <dbg> wpa_supp: wpa_printf_impl: wlan0: State: DISCONNECTED -> SCANNING
[00:00:08.492,858] <dbg> wpa_supp: wpa_printf_impl: Scan SSID - hexdump_ascii(len=9):
[00:00:08.492,889] <dbg> wpa_supp: _wpa_hexdump_ascii:
48 69 7a 7a 75 6c 6f 6e 32 |Hizzulon 2
[00:00:08.492,980] <dbg> wpa_supp: wpa_printf_impl: wlan0: Include wildcard SSID in the scan request
[00:00:08.493,194] <dbg> wpa_supp: wpa_printf_impl: wlan0: Add radio work 'scan'@0x200329a0
[00:00:08.494,232] <dbg> wpa_supp: wpa_printf_impl: argv[1]: 0
[00:00:08.503,051] <dbg> wpa_supp: wpa_printf_impl: wpa_drv_zep_scan2: Scan requested - scan timeout 35 seconds
[00:00:08.504,150] <dbg> wpa_supp: wpa_printf_impl: wlan0: Control interface command 'SELECT_NETWORK 0'
[00:00:08.504,241] <dbg> wpa_supp: wpa_printf_impl: CTRL_IFACE: SELECT_NETWORK id=0
[00:00:08.504,333] <dbg> wpa_supp: wpa_printf_impl: wlan0: Setting scan request: 0.000000 sec
[00:00:08.504,547] <dbg> wpa_supp: wpa_printf_impl: wlan0: Already scanning - Reschedule the incoming scan req
[00:00:08.504,638] <dbg> wpa_supp: wpa_printf_impl: wlan0: Setting scan request: 1.000000 sec
[00:00:08.504,852] <dbg> wifi_supplicant: event_socket_handler: Passing message 47 to wpa_supplicant
[00:00:08.504,943] <dbg> wpa_supp: wpa_printf_impl: wlan0: Event SCAN_STARTED (47) received
[00:00:08.505,065] <dbg> wpa_supp: wpa_printf_impl: wlan0: Own scan request started a scan in 0.001801 seconds
[00:00:08.505,310] <dbg> wpa_supp: wpa_printf_impl: Received len: 24, msg_len:24 - CTRL-EVENT-SCAN-STARTED ->END
[00:00:09.504,882] <dbg> wpa_supp: wpa_printf_impl: wlan0: Already scanning - Reschedule the incoming scan req
[00:00:09.505,004] <dbg> wpa_supp: wpa_printf_impl: wlan0: Setting scan request: 1.000000 sec
[00:00:10.505,218] <dbg> wpa_supp: wpa_printf_impl: wlan0: Already scanning - Reschedule the incoming scan req
[00:00:10.505,340] <dbg> wpa_supp: wpa_printf_impl: wlan0: Setting scan request: 1.000000 sec
[00:00:11.505,523] <dbg> wpa_supp: wpa_printf_impl: wlan0: Already scanning - Reschedule the incoming scan req
[00:00:11.505,645] <dbg> wpa_supp: wpa_printf_impl: wlan0: Setting scan request: 1.000000 sec
[00:00:12.505,859] <dbg> wpa_supp: wpa_printf_impl: wlan0: Already scanning - Reschedule the incoming scan req
[00:00:12.505,981] <dbg> wpa_supp: wpa_printf_impl: wlan0: Setting scan request: 1.000000 sec
[00:00:13.506,164] <dbg> wpa_supp: wpa_printf_impl: wlan0: Already scanning - Reschedule the incoming scan req
[00:00:13.506,286] <dbg> wpa_supp: wpa_printf_impl: wlan0: Setting scan request: 1.000000 sec
[00:00:14.506,500] <dbg> wpa_supp: wpa_printf_impl: wlan0: Already scanning - Reschedule the incoming scan req
[00:00:14.506,622] <dbg> wpa_supp: wpa_printf_impl: wlan0: Setting scan request: 1.000000 sec
[00:00:15.506,805] <dbg> wpa_supp: wpa_printf_impl: wlan0: Already scanning - Reschedule the incoming scan req
[00:00:15.506,927] <dbg> wpa_supp: wpa_printf_impl: wlan0: Setting scan request: 1.000000 sec
[00:00:16.507,141] <dbg> wpa_supp: wpa_printf_impl: wlan0: Already scanning - Reschedule the incoming scan req
[00:00:16.507,263] <dbg> wpa_supp: wpa_printf_impl: wlan0: Setting scan request: 1.000000 sec
[00:00:17.507,446] <dbg> wpa_supp: wpa_printf_impl: wlan0: Already scanning - Reschedule the incoming scan req
[00:00:17.507,568] <dbg> wpa_supp: wpa_printf_impl: wlan0: Setting scan request: 1.000000 sec
[00:00:18.507,751] <dbg> wpa_supp: wpa_printf_impl: wlan0: Already scanning - Reschedule the incoming scan req
[00:00:18.507,873] <dbg> wpa_supp: wpa_printf_impl: wlan0: Setting scan request: 1.000000 sec
[00:00:19.508,056] <dbg> wpa_supp: wpa_printf_impl: wlan0: Already scanning - Reschedule the incoming scan req
[00:00:19.508,178] <dbg> wpa_supp: wpa_printf_impl: wlan0: Setting scan request: 1.000000 sec
[00:00:20.508,392] <dbg> wpa_supp: wpa_printf_impl: wlan0: Already scanning - Reschedule the incoming scan req
[00:00:20.508,514] <dbg> wpa_supp: wpa_printf_impl: wlan0: Setting scan request: 1.000000 sec
[00:00:21.508,697] <dbg> wpa_supp: wpa_printf_impl: wlan0: Already scanning - Reschedule the incoming scan req
[00:00:21.508,819] <dbg> wpa_supp: wpa_printf_impl: wlan0: Setting scan request: 1.000000 sec
[00:00:22.509,033] <dbg> wpa_supp: wpa_printf_impl: wlan0: Already scanning - Reschedule the incoming scan req
[00:00:22.509,155] <dbg> wpa_supp: wpa_printf_impl: wlan0: Setting scan request: 1.000000 sec
[00:00:23.509,338] <dbg> wpa_supp: wpa_printf_impl: wlan0: Already scanning - Reschedule the incoming scan req
[00:00:23.509,460] <dbg> wpa_supp: wpa_printf_impl: wlan0: Setting scan request: 1.000000 sec
[00:00:24.509,643] <dbg> wpa_supp: wpa_printf_impl: wlan0: Already scanning - Reschedule the incoming scan req
[00:00:24.509,765] <dbg> wpa_supp: wpa_printf_impl: wlan0: Setting scan request: 1.000000 sec
[00:00:25.510,009] <dbg> wpa_supp: wpa_printf_impl: wlan0: Already scanning - Reschedule the incoming scan req
[00:00:25.510,101] <dbg> wpa_supp: wpa_printf_impl: wlan0: Setting scan request: 1.000000 sec
[00:00:26.510,284] <dbg> wpa_supp: wpa_printf_impl: wlan0: Already scanning - Reschedule the incoming scan req
[00:00:26.510,406] <dbg> wpa_supp: wpa_printf_impl: wlan0: Setting scan request: 1.000000 sec
[00:00:27.510,650] <dbg> wpa_supp: wpa_printf_impl: wlan0: Already scanning - Reschedule the incoming scan req
[00:00:27.510,772] <dbg> wpa_supp: wpa_printf_impl: wlan0: Setting scan request: 1.000000 sec
[00:00:28.510,986] <dbg> wpa_supp: wpa_printf_impl: wlan0: Already scanning - Reschedule the incoming scan req
[00:00:28.511,108] <dbg> wpa_supp: wpa_printf_impl: wlan0: Setting scan request: 1.000000 sec
[00:00:29.511,291] <dbg> wpa_supp: wpa_printf_impl: wlan0: Already scanning - Reschedule the incoming scan req
[00:00:29.511,413] <dbg> wpa_supp: wpa_printf_impl: wlan0: Setting scan request: 1.000000 sec
[00:00:30.511,627] <dbg> wpa_supp: wpa_printf_impl: wlan0: Already scanning - Reschedule the incoming scan req
[00:00:30.511,749] <dbg> wpa_supp: wpa_printf_impl: wlan0: Setting scan request: 1.000000 sec
[00:00:31.511,932] <dbg> wpa_supp: wpa_printf_impl: wlan0: Already scanning - Reschedule the incoming scan req
[00:00:31.512,054] <dbg> wpa_supp: wpa_printf_impl: wlan0: Setting scan request: 1.000000 sec
[00:00:32.512,237] <dbg> wpa_supp: wpa_printf_impl: wlan0: Already scanning - Reschedule the incoming scan req
[00:00:32.512,359] <dbg> wpa_supp: wpa_printf_impl: wlan0: Setting scan request: 1.000000 sec
[00:00:33.512,603] <dbg> wpa_supp: wpa_printf_impl: wlan0: Already scanning - Reschedule the incoming scan req
[00:00:33.512,695] <dbg> wpa_supp: wpa_printf_impl: wlan0: Setting scan request: 1.000000 sec
[00:00:34.512,878] <dbg> wpa_supp: wpa_printf_impl: wlan0: Already scanning - Reschedule the incoming scan req
[00:00:34.513,000] <dbg> wpa_supp: wpa_printf_impl: wlan0: Setting scan request: 1.000000 sec
[00:00:35.513,244] <dbg> wpa_supp: wpa_printf_impl: wlan0: Already scanning - Reschedule the incoming scan req
[00:00:35.513,366] <dbg> wpa_supp: wpa_printf_impl: wlan0: Setting scan request: 1.000000 sec
[00:00:36.513,580] <dbg> wpa_supp: wpa_printf_impl: wlan0: Already scanning - Reschedule the incoming scan req
[00:00:36.513,702] <dbg> wpa_supp: wpa_printf_impl: wlan0: Setting scan request: 1.000000 sec
--- 43 messages dropped ---
[00:00:38.514,984] <dbg> wpa_supp: wpa_printf_impl: WPA: Set own WPA IE default - hexdump(len=22): 30 14 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ac 02 80 00
[00:00:38.515,075] <dbg> wpa_supp: wpa_printf_impl: RSN: Set own RSNXE default - hexdump(len=0):(�
[00:00:38.515,136] <dbg> wpa_supp: wpa_printf_impl: PSK (set in config) - hexdump(len=32): [REMOVED]
[00:00:38.515,197] <dbg> wpa_supp: wpa_printf_impl: WPA: Set PMK based on external data - hexdump(len=32): [REMOVED]
[00:00:38.515,258] <dbg> wpa_supp: wpa_printf_impl: RRM: Determining whether RRM can be used - device support: 0x50
[00:00:38.515,319] <dbg> wpa_supp: wpa_printf_impl: RRM: Adding RRM IE to Association Request
[00:00:38.515,838] <dbg> wpa_supp: wpa_printf_impl: Added supported operating classes IE - hexdump(len=10): 3b 08 51 51 52 73 76 79 7c 7d
[00:00:38.515,960] <dbg> wpa_supp: wpa_printf_impl: wlan0: Cancelling scan request
[00:00:38.516,174] <inf> wpa_supp: wlan0: SME: Trying to authenticate with fc:34:97:af:71:30 (SSID='Hizzulon2' freq=2442 MHz)
[00:00:38.516,296] <dbg> wpa_supp: wpa_printf_impl: wlan0: State: SCANNING -> AUTHENTICATING
[00:00:38.520,446] <dbg> wpa_supp: wpa_printf_impl: Received len: 40, msg_len:40 - CTRL-EVENT-BSS-ADDED 0 fc:34:97:af:71:30->END
[00:00:38.520,599] <dbg> wpa_supp: wpa_printf_impl: Received len: 24, msg_len:24 - CTRL-EVENT-SCAN-RESULTS ->END
[00:00:38.520,751] <dbg> wpa_supp: wpa_printf_impl: Received len: 83, msg_len:83 - SME: Trying to authenticate with fc:34:97:af:71:30 (SSID='Hizzulon2' freq=2442 MHz)->END
--- 2 messages dropped ---
[00:00:43.522,491] <dbg> wpa_supp: wpa_printf_impl: wlan0: radio_work_free('sme-connect'@0x200329a0): num_active_works --> 0
[00:00:43.522,583] <dbg> wpa_supp: wpa_printf_impl: Added BSSID fc:34:97:af:71:30 into ignore list, ignoring for 10 seconds
[00:00:43.522,705] <dbg> wpa_supp: wpa_printf_impl: wlan0: Consecutive connection failures: 1 --> request scan in 100 ms
[00:00:43.522,827] <dbg> wpa_supp: wpa_printf_impl: wlan0: Setting scan request: 0.100000 sec
[00:00:43.522,949] <dbg> wpa_supp: wpa_printf_impl: wlan0: State: AUTHENTICATING -> DISCONNECTED
[00:00:43.623,016] <dbg> wpa_supp: wpa_printf_impl: wlan0: State: DISCONNECTED -> SCANNING
[00:00:43.623,107] <dbg> wpa_supp: wpa_printf_impl: wlan0: Starting AP scan for wildcard SSID
[00:00:43.623,321] <dbg> wpa_supp: wpa_printf_impl: wlan0: Add radio work 'scan'@0x20032348
[00:00:43.623,474] <dbg> wpa_supp: wpa_printf_impl: wlan0: First radio work item in the queue - schedule start immediately
[00:00:43.623,718] <dbg> wpa_supp: wpa_printf_impl: wlan0: Starting radio work 'scan'@0x20032348 after 0.000214 second wait
[00:00:43.626,159] <dbg> wpa_supp: wpa_printf_impl: wpa_drv_zep_scan2: Scan requested - scan timeout 35 seconds
[00:00:46.530,639] <dbg> wifi_supplicant: event_socket_handler: Passing message 11 to wpa_supplicant
[00:00:46.530,731] <dbg> wpa_supp: wpa_printf_impl: wlan0: Event DEAUTH (11) received
[00:00:46.530,822] <dbg> wpa_supp: wpa_printf_impl: wlan0: Deauthentication notification
[00:00:46.530,914] <dbg> wpa_supp: wpa_printf_impl: wlan0: * reason 3 (DEAUTH_LEAVING)
[00:00:46.531,036] <dbg> wpa_supp: wpa_printf_impl: wlan0: * address f4:ce:36:00:23:2c
[00:00:46.531,097] <dbg> wpa_supp: wpa_printf_impl: Deauthentication frame IE(s) - hexdump(len=0): [NULL]
[00:00:46.531,219] <dbg> wpa_supp: wpa_printf_impl: wlan0: Auto connect enabled: try to reconnect (wps=0/0 wpa_state=3)
[00:00:46.531,311] <dbg> wpa_supp: wpa_printf_impl: wlan0: Do not request new immediate scan
[00:00:46.531,402] <dbg> wpa_supp: wpa_printf_impl: wlan0: WPA: Clear old PMK and PTK
[00:00:46.531,524] <dbg> wpa_supp: wpa_printf_impl: wlan0: Disconnect event - remove keys
[00:00:46.531,646] <dbg> wpa_supp: wpa_printf_impl: wlan0: State: SCANNING -> DISCONNECTED
--- 3 messages dropped ---
[00:01:13.628,845] <dbg> wpa_supp: wpa_printf_impl: 00:00:00:00:00:00 freq=0 qual=0 noise=-89 level=0 flags=0x7 age=0 est=0
[00:01:13.628,906] <dbg> wpa_supp: wpa_printf_impl: wlan0: BSS: Start scan result update 2
[00:01:13.629,058] <dbg> wpa_supp: wpa_printf_impl: wlan0: BSS: No SSID IE included for 00:00:00:00:00:00
[00:01:13.629,119] <dbg> wpa_supp: wpa_printf_impl: BSS: last_scan_res_used=0/32
[00:01:13.629,211] <dbg> wpa_supp: wpa_printf_impl: wlan0: New scan results available (own=0 ext=0)
[00:01:13.629,425] <dbg> wpa_supp: wpa_printf_impl: wlan0: Radio work 'scan'@0x20032348 done in 30.005706 seconds
[00:01:13.629,577] <dbg> wpa_supp: wpa_printf_impl: wlan0: radio_work_free('scan'@0x20032348): num_active_works --> 0
[00:01:13.629,669] <dbg> wpa_supp: wpa_printf_impl: wlan0: No suitable network found
[00:01:13.629,760] <dbg> wpa_supp: wpa_printf_impl: wlan0: Setting scan request: 5.000000 sec
[00:01:13.630,035] <dbg> wpa_supp: wpa_printf_impl: Received len: 24, msg_len:24 - CTRL-EVENT-SCAN-RESULTS ->END
[00:01:13.630,187] <dbg> wpa_supp: wpa_printf_impl: Received len: 29, msg_len:29 - CTRL-EVENT-NETWORK-NOT-FOUND ->END
[00:01:18.629,974] <dbg> wpa_supp: wpa_printf_impl: wlan0: State: DISCONNECTED -> SCANNING
[00:01:18.630,065] <dbg> wpa_supp: wpa_printf_impl: Scan SSID - hexdump_ascii(len=9):
[00:01:18.630,065] <dbg> wpa_supp: _wpa_hexdump_ascii:
48 69 7a 7a 75 6c 6f 6e 32 |Hizzulon 2
[00:01:18.630,157] <dbg> wpa_supp: wpa_printf_impl: wlan0: Include wildcard SSID in the scan request
[00:01:18.630,371] <dbg> wpa_supp: wpa_printf_impl: wlan0: Add radio work 'scan'@0x20032c88
[00:01:18.630,493] <dbg> wpa_supp: wpa_printf_impl: wlan0: First radio work item in the queue - schedule start immediately
[00:01:18.630,737] <dbg> wpa_supp: wpa_printf_impl: wlan0: Starting radio work 'scan'@0x20032c88 after 0.000214 second wait
[00:01:18.633,605] <dbg> wpa_supp: wpa_printf_impl: wpa_drv_zep_scan2: Scan requested - scan timeout 35 seconds
uart:~$

RE: WiFi scan while connected

Simonr — Wed, 08 Jan 2025 09:23:03 GMT

Hi Remi

Today I got hex files from the devs, that has a potential fix to the scan issues at least. Please test them for both the scan and connection issues on your end and report back what you're seeing.

devzone.nordicsemi.com/.../zephyr-_2800_1_2900_.hex & devzone.nordicsemi.com/.../zephyr_5F00_with_5F00_logs_5F00_enabled.hex

There should be logging enabled on one of them that might give us an idea of what's wrong if this doesn't fix the problem(s).

Best regards,

Simon

RE: WiFi scan while connected

Simonr — Tue, 07 Jan 2025 13:30:11 GMT

Happy new year Remi!

Thank you for your thorough testing yet again. I'm sorry to say that we've not been able to get a .hex with a fix ready for you over the holiday period, as we've been short on staff the last few weeks. I'll keep you updated on what I hear from the devs regarding both the fix .hex as well as the status on these new findings.

Best regards,

Simon

RE: WiFi scan while connected

Remi.G — Mon, 30 Dec 2024 22:00:20 GMT

I was experimenting with this today and have some additional observations - not related directly to scanning while connected, but related to the 2.4GHz connection issues I was seeing. Including it here in case it may have the same root cause as your potential fix, but I can file under a new issue if not.

As mentioned above, I can always connect reliably at 5GHz, but 2.4GHz is flaky. Some devices with some APs will never connect to 2.4GHz, but I have had some devices switch between working and not-working over time. When they fail, they fail always, on every connection attempt. Resets/power cycling on both the AP and the device have no effect.

I discovered that specifying the channel or band explicitly in the "wifi connect" command will connect reliably at 2.4GHz.

These logs are with the NCS 2.8.0 wifi shell sample, and using the Asus AP mentioned above as well as a Pixel8 hotspot. The Asus AP has simultaneous 2.4GHz "Hizzulon2" and 5GHz "Hizzulon" (note different SSID names).

Connecting to 5GHz always works, on all devices I've tried:

uart:~$ wifi scan
Scan requested

Num | SSID (len) | Chan (Band) | RSSI | Security | BSSID | MFP
1 | Hizzulon 8 | 44 (5GHz ) | -55 | WPA2-PSK | FC:34:97:AF:71:34 | Disable
2 | Hizzulon2 9 | 7 (2.4GHz) | -55 | WPA2-PSK | FC:34:97:AF:71:30 | Disable
3 | 0 | 116 (5GHz ) | -67 | WPA2-PSK | BA:34:97:AF:71:3D | Disable
4 | 0 | 116 (5GHz ) | -68 | WPA2-PSK | FC:34:97:AF:71:38 | Disable
5 | DIRECT-roku-45P-0E44CB 22 | 44 (5GHz ) | -81 | WPA2-PSK | 22:EF:BD:34:5E:DF | Disable
6 | Tims House 10 | 6 (2.4GHz) | -86 | WPA2-PSK | 90:D0:92:04:1B:84 | Optional
7 | ATT8H862E9 10 | 3 (2.4GHz) | -88 | WPA2-PSK | 90:9D:7D:60:6A:90 | Optional
Scan request done

uart:~$ wifi connect -s Hizzulon -p <password> -k 1
Connection requested
Connected
[00:00:36.496,307] <inf> wpa_supp: wlan0: SME: Trying to authenticate with fc:34:97:af:71:34 (SSID='Hizzulon' freq=5220 MHz)
[00:00:36.853,179] <inf> wpa_supp: wlan0: Trying to associate with fc:34:97:af:71:34 (SSID='Hizzulon' freq=5220 MHz)
[00:00:36.869,873] <inf> wpa_supp: wlan0: Associated with fc:34:97:af:71:34
[00:00:36.870,056] <inf> wpa_supp: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
[00:00:36.889,587] <inf> wpa_supp: wlan0: WPA: Key negotiation completed with fc:34:97:af:71:34 [PTK=CCMP GTK=CCMP]
[00:00:36.889,801] <inf> wpa_supp: wlan0: CTRL-EVENT-CONNECTED - Connection to fc:34:97:af:71:34 completed [id=0 id_str=]
[00:00:36.900,817] <inf> net_dhcpv4: Received: 192.168.1.203

uart:~$ wifi status
Status: successful
==================
State: COMPLETED
Interface Mode: STATION
Link Mode: WIFI 6 (802.11ax/HE)
SSID: Hizzulon
BSSID: FC:34:97:AF:71:34
Band: 5GHz
Channel: 44
Security: WPA2-PSK
MFP: Optional
RSSI: -56
Beacon Interval: 100
DTIM: 1
TWT: Supported
Current PHY rate : 34400

Connecting to 2.4GHz always fails, on this device at this time (device was reset after above test). After ~30 seconds (much longer than a successful connection) it outputs the "trying to authenticate" message but doesn't get any further.

uart:~$ wifi connect -s Hizzulon2 -p <password> -k 1
Connection requested
[00:01:03.028,717] <inf> wpa_supp: wlan0: SME: Trying to authenticate with fc:34:97:af:71:30 (SSID='Hizzulon2' freq=2442 MHz)

uart:~$ wifi status
Status: successful
==================
State: DISCONNECTED

But if I specify the band (-b 2) or channel (-c 7) explicitly, it works (device resets between every test):

uart:~$ wifi connect -s Hizzulon2 -p <password> -k 1 -b 2
Connection requested
Connected
[00:00:37.813,201] <inf> wpa_supp: wlan0: SME: Trying to authenticate with fc:34:97:af:71:30 (SSID='Hizzulon2' freq=2442 MHz)
[00:00:38.180,236] <inf> wpa_supp: wlan0: Trying to associate with fc:34:97:af:71:30 (SSID='Hizzulon2' freq=2442 MHz)
[00:00:38.198,913] <inf> wpa_supp: wlan0: Associated with fc:34:97:af:71:30
[00:00:38.199,096] <inf> wpa_supp: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
[00:00:38.220,581] <inf> wpa_supp: wlan0: WPA: Key negotiation completed with fc:34:97:af:71:30 [PTK=CCMP GTK=CCMP]
[00:00:38.220,794] <inf> wpa_supp: wlan0: CTRL-EVENT-CONNECTED - Connection to fc:34:97:af:71:30 completed [id=0 id_str=]
[00:00:38.237,854] <inf> net_dhcpv4: Received: 192.168.1.203

uart:~$ wifi status
Status: successful
==================
State: COMPLETED
Interface Mode: STATION
Link Mode: WIFI 4 (802.11n/HT)
SSID: Hizzulon2
BSSID: FC:34:97:AF:71:30
Band: 2.4GHz
Channel: 7
Security: WPA2-PSK
MFP: Optional
RSSI: -53
Beacon Interval: 100
DTIM: 1
TWT: Not supported
Current PHY rate : 26000

uart:~$ wifi connect -s Hizzulon2 -p <password> -k 1 -c 7
Connection requested
Connected
[00:00:15.888,732] <inf> wpa_supp: wlan0: SME: Trying to authenticate with fc:34:97:af:71:30 (SSID='Hizzulon2' freq=2442 MHz)
[00:00:16.256,256] <inf> wpa_supp: wlan0: Trying to associate with fc:34:97:af:71:30 (SSID='Hizzulon2' freq=2442 MHz)
[00:00:16.274,841] <inf> wpa_supp: wlan0: Associated with fc:34:97:af:71:30
[00:00:16.275,024] <inf> wpa_supp: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
[00:00:16.293,670] <inf> wpa_supp: wlan0: WPA: Key negotiation completed with fc:34:97:af:71:30 [PTK=CCMP GTK=CCMP]
[00:00:16.293,884] <inf> wpa_supp: wlan0: CTRL-EVENT-CONNECTED - Connection to fc:34:97:af:71:30 completed [id=0 id_str=]
[00:00:16.310,699] <inf> net_dhcpv4: Received: 192.168.1.203

uart:~$ wifi status
Status: successful
==================
State: COMPLETED
Interface Mode: STATION
Link Mode: WIFI 4 (802.11n/HT)
SSID: Hizzulon2
BSSID: FC:34:97:AF:71:30
Band: 2.4GHz
Channel: 7
Security: WPA2-PSK
MFP: Optional
RSSI: -54
Beacon Interval: 100
DTIM: 1
TWT: Not supported
Current PHY rate : 26000

Pixel8 results are similar, except it uses 2.4GHz channel 11, and it has SSID name "Pixel" for both 2.4 and 5GHz.

So something related to band/channel specific connection vs "any" band/channel.

RE: WiFi scan while connected

Simonr — Wed, 18 Dec 2024 06:27:22 GMT

We're working on a .hex file with a potential fix to this issue. We've also gotten the same AP model as you now, but have not been able to reproduce this issue on our end.

Best regards,

Simon

RE: WiFi scan while connected

Remi.G — Mon, 16 Dec 2024 16:11:27 GMT

Here are the results with the 5270.zephyr.hex test image:

[00:00:00.616,210] <inf> fs_nvs: 2 Sectors of 4096 bytes
[00:00:00.616,241] <inf> fs_nvs: alloc wra: 0, fe8
[00:00:00.616,241] <inf> fs_nvs: data wra: 0, 0
*** Booting nRF Connect SDK v2.8.0-1d192a274cd7 ***
*** Using Zephyr OS v3.7.99-cbd75f256cc9 ***
Starting nrf7002dk with CPU frequency: 128 MHz
[00:00:00.618,194] <inf> wifi_supplicant: wpa_supplicant initialized

uart:~$ wifi scan -b 5
Scan requested
uart:~$ debug event 1122 0000 0000
debug event 1124 0000 0000
debug event 113000 0000 0000
debug event 113001 0000 0000

Num | SSID (len) | Chan (Band) | RSSI | Security | BSSID | MFP
1 | 0 | 161 (5GHz ) | -58 | WPA2-PSK | BA:34:97:AF:71:3D | Disable
2 | 0 | 161 (5GHz ) | -58 | WPA2-PSK | FC:34:97:AF:71:38 | Disable
3 | Hizzulon 8 | 48 (5GHz ) | -63 | WPA2-PSK | FC:34:97:AF:71:34 | Disable
4 | 0 | 48 (5GHz ) | -80 | WPA2-PSK | 22:EF:BD:34:5E:DF | Disable
Scan request done

uart:~$ wifi connect -s Hizzulon <credentials>
debug event 1122 0000 0000
Connection requested
uart:~$ debug event 1124 0000 0000
debug event 113000 0000 0000
debug event 113001 0000 0000
debug event 1122 0000 0000
debug event 1124 0000 0000
debug event 113000 0000 0000
debug event 113001 0000 0000
Connected
[00:01:30.862,121] <inf> wpa_supp: wlan0: SME: Trying to authenticate with fc:34:97:af:71:34 (SSID='Hizzulon' freq=5240 MHz)
[00:01:31.221,954] <inf> wpa_supp: wlan0: Trying to associate with fc:34:97:af:71:34 (SSID='Hizzulon' freq=5240 MHz)
[00:01:31.238,494] <inf> wpa_supp: wlan0: Associated with fc:34:97:af:71:34
[00:01:31.238,677] <inf> wpa_supp: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
[00:01:31.257,659] <inf> wpa_supp: wlan0: WPA: Key negotiation completed with fc:34:97:af:71:34 [PTK=CCMP GTK=CCMP]
[00:01:31.257,873] <inf> wpa_supp: wlan0: CTRL-EVENT-CONNECTED - Connection to fc:34:97:af:71:34 completed [id=0 id_str=]
[00:01:31.269,042] <inf> net_dhcpv4: Received: 192.168.1.237
uart:~$ debug event 114000 0000 0020

uart:~$ wifi status
Status: successful
==================
State: COMPLETED
Interface Mode: STATION
Link Mode: WIFI 6 (802.11ax/HE)
SSID: Hizzulon
BSSID: FC:34:97:AF:71:34
Band: 5GHz
Channel: 48
Security: WPA2-PSK
MFP: Optional
RSSI: -61
Beacon Interval: 100
DTIM: 1
TWT: Supported
Current PHY rate : 34400
uart:~$

uart:~$ wifi scan -b 5 -c 5:48
Scan requested
uart:~$ debug event 1122 0000 0000
debug event 112500 0000 0000
debug event 112501 0000 0000
debug event 112502 0000 0000
debug event 1124 0000 0000
debug event 113000 0000 0000
debug event 113001 0000 0000

uart:~$ wifi scan -b 5 -c 5:165
Scan requested
uart:~$ debug event 1122 0000 0000
debug event 112500 0000 0000
debug event 112501 0000 0000
debug event 112502 0000 0000
debug event 1124 0000 0000
debug event 113000 0000 0000
debug event 114000 0008 0004

... repeats "debug event 114000 0008 0004" forever

Note that there are two devices on channel 48 in the initial scan - the "Hizzulon" AP, and a device with BSSID 22:EF:BD:34:5E:DF at low RSSI (a Roku). The above log shows that the first scan on channel 48 after connecting showed only the second device, not the AP. Doing another scan immediately afterward found the AP. That behavior isn't consistent - it may find one or both. Just including it in the log as it seems unexpected that the scan wouldn't always show the much stronger AP.

RE: WiFi scan while connected

Remi.G — Fri, 13 Dec 2024 20:55:56 GMT

Confirmed the AP version: Asus ZenWifi AX XT8 (AX6600).

https://www.asus.com/networking-iot-servers/whole-home-mesh-wifi-system/zenwifi-wifi-systems/asus-zenwifi-ax-xt8/

I will try the image on Monday.

RE: WiFi scan while connected

Simonr — Wed, 11 Dec 2024 09:58:12 GMT

Hi again Remi

Enjoy your vacation then!

When you get back, please confirm which AP model you're using. Unfortunately the log you've provided doesn't have enough debugging to narrow down what exactly is wrong, but here is a .hex file you can use with some more debugging options enabled you can run on a DK and test when you get back: devzone.nordicsemi.com/.../5270.zephyr.hex

For reference, we also tested using a Pixel 7 on our end, but were not able to reproduce with that.

Best regards,

Simon

RE: WiFi scan while connected

Remi.G — Tue, 10 Dec 2024 15:43:20 GMT

I'm fairly certain it's the XT8 model, but I am on vacation this week so I can't check the serial number. The XT8 and XT9 look identical, it would be one of those two. I'll confirm when I am back at the end of this week.

Or, you could buy a Pixel8 in the meantime.

RE: WiFi scan while connected

Simonr — Tue, 10 Dec 2024 10:22:57 GMT

Unfortunately we don't have a Pixel or Asus AP as the ones you have here, but if you can share a picture of the AP you're using, we will buy the same model to get one in our test lab. We found two models called "Asus ZenWiFi AX" and would like to confirm the exact model you're using first.

Best regards,

Simon

RE: WiFi scan while connected

Simonr — Mon, 09 Dec 2024 10:29:06 GMT

Thank you for the thorough report Remi, the logs and information has been forwarded to the Wi-Fi team and we're looking into this now. Thank you for the thorough testing on your end! I'll let you know when I hear something, or at the very least by end of week with a status update.

Best regards,

Simon

RE: WiFi scan while connected

Remi.G — Fri, 06 Dec 2024 18:43:52 GMT

Second test first: connect to the 5GHz AP and limit the channel scanning:

uart:~$ wifi scan -b 5
Scan requested

uart:~$ wifi connect -s Hizzulon <credentials>
Connection requested
Connected
[00:00:37.407,592] <inf> wpa_supp: wlan0: SME: Trying to authenticate with fc:34:97:af:71:34 (SSID='Hizzulon' freq=5220 MHz)
[00:00:37.767,456] <inf> wpa_supp: wlan0: Trying to associate with fc:34:97:af:71:34 (SSID='Hizzulon' freq=5220 MHz)
[00:00:37.784,240] <inf> wpa_supp: wlan0: Associated with fc:34:97:af:71:34
[00:00:37.784,423] <inf> wpa_supp: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
[00:00:37.802,429] <inf> wpa_supp: wlan0: WPA: Key negotiation completed with fc:34:97:af:71:34 [PTK=CCMP GTK=CCMP]
[00:00:37.802,642] <inf> wpa_supp: wlan0: CTRL-EVENT-CONNECTED - Connection to fc:34:97:af:71:34 completed [id=0 id_str=]
[00:00:37.813,659] <inf> net_dhcpv4: Received: 192.168.1.237

uart:~$ wifi scan -b 5 -c 5:36,40,48,52,56,60,64,68,96,100,104,108,112,116,120,124,128,132,136,140,144,149,153,157,161,165
Scan requested
Scan request failed (-116)
[00:02:11.144,927] <err> wifi_nrf: nrf_wifi_fmac_chg_vif_state: RPU is unresponsive for 10 sec
[00:02:11.144,927] <err> wifi_nrf: nrf_wifi_if_stop_zep: nrf_wifi_fmac_chg_vif_state failed
[00:02:11.145,629] <inf> wifi_supplicant: Network interface 1 (0x200013c0) down
[00:02:11.157,012] <inf> wpa_supp: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
[00:02:11.157,379] <inf> wpa_supp: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
[00:02:13.314,422] <inf> wifi_supplicant: Network interface 1 (0x200013c0) up

So it's failing on the scan, even with the AP channel 44 excluded.

I tried the channels individually, e.g. "wifi scan -b 5 -c 4:40", including ones listed in valid_5g_chans_20mhz, like 169. I tried them all ((including 44), but not all are listed here, just some interesting ones (this was done after a reset and a new connection, like all tests):

uart:~$ wifi scan -b 5 -c 5:40
Scan requested
Scan request done

uart:~$ wifi scan -b 5 -c 5:44
Scan requested

uart:~$ wifi scan -b 5 -c 5:48
Scan requested
Scan request done

uart:~$ wifi scan -b 5 -c 5:161
Scan requested

Num | SSID (len) | Chan (Band) | RSSI | Security | BSSID | MFP
1 | 0 | 161 (5GHz ) | -65 | WPA2-PSK | FC:34:97:AF:71:38 | Disable
2 | 0 | 161 (5GHz ) | -66 | WPA2-PSK | BA:34:97:AF:71:3D | Disable
Scan request done

uart:~$ wifi scan -b 5 -c 5:165
Scan requested
Scan request failed (-116)
[00:02:33.109,252] <err> wifi_nrf: nrf_wifi_fmac_chg_vif_state: RPU is unresponsive for 10 sec
[00:02:33.109,252] <err> wifi_nrf: nrf_wifi_if_stop_zep: nrf_wifi_fmac_chg_vif_state failed
[00:02:33.109,924] <inf> wifi_supplicant: Network interface 1 (0x200013c0) down
[00:02:33.121,337] <inf> wpa_supp: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
[00:02:33.121,673] <inf> wpa_supp: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
[00:02:35.278,839] <inf> wifi_supplicant: Network interface 1 (0x200013c0) up

It's only channel 165 that fails. Even adjacent channels, like 163 and 167, are fine.

There were no networks on channels other than 44 and 161 in the initial scan, so not sure what the relationship with 165 is.

On to the first test. As I mentioned, the nRF7002 is unable to connect to my 2.4GHz AP (Asus ZenWiFi AX, with the latest firmware), so I enabled a hotspot on my laptop (with an Intel Wi-Fi 6 AX301) at either 2.4GHz or 5GHz, shown in these scans as "Laptop".

uart:~$ wifi scan
Scan requested

uart:~$ wifi connect -s Laptop <credentials>
Connection requested
Connected
[00:00:36.527,923] <inf> wpa_supp: wlan0: SME: Trying to authenticate with 8a:d8:2e:2d:24:90 (SSID='Laptop' freq=5220 MHz)
[00:00:36.888,000] <inf> wpa_supp: wlan0: Trying to associate with 8a:d8:2e:2d:24:90 (SSID='Laptop' freq=5220 MHz)
[00:00:36.904,815] <inf> wpa_supp: wlan0: Associated with 8a:d8:2e:2d:24:90
[00:00:36.904,998] <inf> wpa_supp: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
[00:00:36.920,898] <inf> wpa_supp: wlan0: WPA: Key negotiation completed with 8a:d8:2e:2d:24:90 [PTK=CCMP GTK=CCMP]
[00:00:36.921,112] <inf> wpa_supp: wlan0: CTRL-EVENT-CONNECTED - Connection to 8a:d8:2e:2d:24:90 completed [id=0 id_str=]
[00:00:36.955,657] <inf> net_dhcpv4: Received: 192.168.137.6

uart:~$ wifi status
Status: successful
==================
State: COMPLETED
Interface Mode: STATION
Link Mode: WIFI 5 (802.11ac/VHT)
SSID: Laptop
BSSID: 8A:D8:2E:2D:24:90
Band: 5GHz
Channel: 44
Security: WPA2-PSK
MFP: Optional
RSSI: -37
Beacon Interval: 100
DTIM: 3
TWT: Not supported
Current PHY rate : 39000

uart:~$ wifi scan -b 5
Scan requested

Scanning works when connected to the laptop hotspot. Same channel 44 as the "Hizzulon" hotspot.

Repeated the test with connected to laptop hotspot at 2.4GHz:

uart:~$ wifi scan
Scan requested

uart:~$ wifi connect -s Laptop <credentials>
Connection requested
Connected
[00:00:36.011,840] <inf> wpa_supp: wlan0: SME: Trying to authenticate with 8a:d8:2e:2d:24:90 (SSID='Laptop' freq=2437 MHz)
[00:00:36.404,815] <inf> wpa_supp: wlan0: Trying to associate with 8a:d8:2e:2d:24:90 (SSID='Laptop' freq=2437 MHz)
[00:00:36.423,858] <inf> wpa_supp: wlan0: Associated with 8a:d8:2e:2d:24:90
[00:00:36.424,041] <inf> wpa_supp: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
[00:00:36.439,422] <inf> wpa_supp: wlan0: WPA: Key negotiation completed with 8a:d8:2e:2d:24:90 [PTK=CCMP GTK=CCMP]
[00:00:36.439,636] <inf> wpa_supp: wlan0: CTRL-EVENT-CONNECTED - Connection to 8a:d8:2e:2d:24:90 completed [id=0 id_str=]
[00:00:36.488,372] <inf> net_dhcpv4: Received: 192.168.137.18

uart:~$ wifi status
Status: successful
==================
State: COMPLETED
Interface Mode: STATION
Link Mode: WIFI 4 (802.11n/HT)
SSID: Laptop
BSSID: 8A:D8:2E:2D:24:90
Band: 2.4GHz
Channel: 6
Security: WPA2-PSK
MFP: Optional
RSSI: -27
Beacon Interval: 100
DTIM: 3
TWT: Not supported
Current PHY rate : 0

uart:~$ wifi scan
Scan requested

No surprises there, it also works with the laptop hotspot at 2.4GHz.

I looked around for some other APs I could connect to and I have a Pixel8 which supports 2.4 and 5GHz hotspots, advertised as "Pixel" here. Also configured the Pixel8 hotspot to "WPA2-Personal" security instead of "WPA2/3 Personal" to make things closer.

I powered off the "Hizzulon" AP so it would have no effect on these tests.

uart:~$ wifi scan
Scan requested

uart:~$ wifi connect -b 5 -s Pixel <credentials>
Connection requested
Connected
[00:00:28.738,250] <inf> wpa_supp: wlan0: SME: Trying to authenticate with 2a:a7:8e:ee:67:70 (SSID='Pixel' freq=5805 MHz)
[00:00:29.099,487] <inf> wpa_supp: wlan0: Trying to associate with 2a:a7:8e:ee:67:70 (SSID='Pixel' freq=5805 MHz)
[00:00:29.115,875] <inf> wpa_supp: wlan0: Associated with 2a:a7:8e:ee:67:70
[00:00:29.116,058] <inf> wpa_supp: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
[00:00:29.224,578] <inf> wpa_supp: wlan0: WPA: Key negotiation completed with 2a:a7:8e:ee:67:70 [PTK=CCMP GTK=CCMP]
[00:00:29.224,792] <inf> wpa_supp: wlan0: CTRL-EVENT-CONNECTED - Connection to 2a:a7:8e:ee:67:70 completed [id=0 id_str=]
[00:00:29.259,307] <inf> net_dhcpv4: Received: 192.168.8.105

uart:~$ wifi status
Status: successful
==================
State: COMPLETED
Interface Mode: STATION
Link Mode: WIFI 6 (802.11ax/HE)
SSID: Pixel
BSSID: 2A:A7:8E:EE:67:70
Band: 5GHz
Channel: 161
Security: WPA2-PSK
MFP: Optional
RSSI: -55
Beacon Interval: 100
DTIM: 2
TWT: Not supported
Current PHY rate : 26000

uart:~$ wifi scan -b 5 -c 5:165
Scan requested
Scan request failed (-116)
[00:01:47.003,356] <err> wifi_nrf: nrf_wifi_fmac_chg_vif_state: RPU is unresponsive for 10 sec
[00:01:47.003,356] <err> wifi_nrf: nrf_wifi_if_stop_zep: nrf_wifi_fmac_chg_vif_state failed
[00:01:47.004,028] <inf> wifi_supplicant: Network interface 1 (0x200013c0) down
[00:01:47.015,441] <inf> wpa_supp: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
[00:01:47.015,808] <inf> wpa_supp: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
[00:01:49.172,973] <inf> wifi_supplicant: Network interface 1 (0x200013c0) up

Fails on channel 165, exactly the same as the original AP.

Connecting at 2.4GHz:

uart:~$ wifi scan
Scan requested

uart:~$ wifi connect -b 2 -s Pixel <credentials>
Connection requested
[00:00:29.379,577] <inf> wpa_supp: wlan0: SME: Trying to authenticate with 2a:58:71:ee:67:70 (SSID='Pixel' freq=2442 MHz)
[00:00:29.759,582] <inf> wpa_supp: wlan0: Trying to associate with 2a:58:71:ee:67:70 (SSID='Pixel' freq=2442 MHz)
[00:00:29.788,360] <inf> wpa_supp: wlan0: Associated with 2a:58:71:ee:67:70
[00:00:29.788,513] <inf> wpa_supp: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Connected
[00:00:39.788,665] <inf> wpa_supp: wlan0: Authentication with 2a:58:71:ee:67:70 timed out.
[00:00:39.791,076] <inf> wpa_supp: wlan0: CTRL-EVENT-DISCONNECTED bssid=2a:58:71:ee:67:70 reason=3 locally_generated=1
[00:00:39.791,320] <inf> wpa_supp: BSSID 2a:58:71:ee:67:70 ignore list count incremented to 2, ignoring for 10 seconds
[00:00:39.795,471] <inf> wpa_supp: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Connected
[00:00:40.857,269] <inf> wpa_supp: wlan0: SME: Trying to authenticate with 2a:58:71:ee:67:70 (SSID='Pixel' freq=2442 MHz)
[00:00:40.866,729] <inf> wpa_supp: wlan0: Trying to associate with 2a:58:71:ee:67:70 (SSID='Pixel' freq=2442 MHz)
[00:00:40.886,779] <inf> wpa_supp: wlan0: Associated with 2a:58:71:ee:67:70
[00:00:40.886,962] <inf> wpa_supp: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
[00:00:40.949,279] <inf> wpa_supp: wlan0: WPA: Key negotiation completed with 2a:58:71:ee:67:70 [PTK=CCMP GTK=CCMP]
[00:00:40.949,493] <inf> wpa_supp: wlan0: CTRL-EVENT-CONNECTED - Connection to 2a:58:71:ee:67:70 completed [id=0 id_str=]
[00:00:40.996,215] <inf> net_dhcpv4: Received: 192.168.8.105

uart:~$ wifi status
Status: successful
==================
State: COMPLETED
Interface Mode: STATION
Link Mode: WIFI 6 (802.11ax/HE)
SSID: Pixel
BSSID: 2A:58:71:EE:67:70
Band: 2.4GHz
Channel: 7
Security: WPA2-PSK
MFP: Optional
RSSI: -53
Beacon Interval: 100
DTIM: 2
TWT: Not supported
Current PHY rate : 0

uart:~$ wifi scan -b 5 -t passive
Scan requested

uart:~$ wifi scan -b 5 -c 5:165
Scan requested
Scan request failed (-116)
[00:02:16.802,520] <err> wifi_nrf: nrf_wifi_fmac_chg_vif_state: RPU is unresponsive for 10 sec
[00:02:16.802,520] <err> wifi_nrf: nrf_wifi_if_stop_zep: nrf_wifi_fmac_chg_vif_state failed
[00:02:16.803,222] <inf> wifi_supplicant: Network interface 1 (0x200013c0) down
[00:02:16.814,605] <inf> wpa_supp: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
[00:02:16.814,971] <inf> wpa_supp: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
[00:02:18.972,045] <inf> wifi_supplicant: Network interface 1 (0x200013c0) up

When connected at 2.4GHz, it still fails when scanning channel 165.

Also note the timeout and reconnection. I repeated the test several times and got it each time, though it quickly reconnected. Not sure if that's an issue with the Pixel8 or the nRF7002.

I tried with my iPhone SE 2nd gen, which only supports 2.4GHz hotspot, and wasn't able to connect to that. It might have been something with WPA3 (I did use -k 3), but suspicious that I'm not able to connect to either my AP or the iPhone at 2.4GHz. That's a separate issue.

So in summary: scanning fails with both my AP and a Pixel8 hotspot on channel 165 whether connected to 2.4GHz or 5GHz, but works with my laptop hotspot connected at either 2.4 or 5GHz.

Pasting the various wifi status again here:

Status: successful
==================
State: COMPLETED
Interface Mode: STATION
Link Mode: WIFI 6 (802.11ax/HE)
SSID: Hizzulon
BSSID: FC:34:97:AF:71:34
Band: 5GHz
Channel: 44
Security: WPA2-PSK
MFP: Optional
RSSI: -53
Beacon Interval: 100
DTIM: 1
TWT: Supported
Current PHY rate : 26000

Status: successful ================== State: COMPLETED Interface Mode: STATION Link Mode: WIFI 5 (802.11ac/VHT) SSID: Laptop BSSID: 8A:D8:2E:2D:24:90 Band: 5GHz Channel: 44 Security: WPA2-PSK MFP: Optional RSSI: -37 Beacon Interval: 100 DTIM: 3 TWT: Not supported Current PHY rate : 39000

Status: successful
==================
State: COMPLETED
Interface Mode: STATION
Link Mode: WIFI 6 (802.11ax/HE)
SSID: Pixel
BSSID: 2A:A7:8E:EE:67:70
Band: 5GHz
Channel: 161
Security: WPA2-PSK
MFP: Optional
RSSI: -55
Beacon Interval: 100
DTIM: 2
TWT: Not supported
Current PHY rate : 26000

Similar parameters. AP and Pixel have different channels, I'm not able to assign the AP to any arbitrary channel but did try channel 48 and same failure. AP and laptop have same channel 44, AP fails but laptop works. Notable is that the Link Mode is WIFI 5 for Laptop, which works, so maybe something with wifi 6 mode?

If you have access to a Pixel8 (possibly other Android phones also), you should be able to reproduce these results.