wifi:AP has neither DSSS parameter nor HT Information, drop it (IDFGH-7742)

[KonssnoK]

Using ESP32S3 DEVKitC

esp-idf v4.4 6c5fb29c2c513936ecefa7cdf49fb324e316546e

ESP connect to hotspot as a client.

Randomly, the logs start printing

E (936951) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (937984) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (938476) wifi:AP has neither DSSS parameter nor HT Information, drop it

forever until the ESP32 is reset.

Switching on/off the access point does not change the situation, also the device appears operational. I think it's related somehow to AP discovery?

I have no idea on how to replicate, but looking on the internet i found no answer to what this log means and i think it's part of the IP of Espressif (didn't find it in the repo)

Any help? Thanks

[xueyunfei998]

Do you have other test development boards, such as esp32,esp32c3,esp32s2 and so on

@xueyunfei998 yes, you can see in the attached log from a wifi_station example running 05_dev2.zip

but i have another device with the same firmware right next to it, and it didn't have any occurrence.

Instead, the example with mesh_ip_internal has thousands of occurrences. 05_7440.zip

You said this bug didn't appear on the other board? Do you have any other development boards, such as esp32 esp32c3,esp32s2, etc. If so, a comparative test can be conducted.

[xueyunfei998]

Are there any other peripherals used in the application? Such as SDIO interface, reading and writing SD card, etc.

[KonssnoK]

@xueyunfei998 the application is the wifi station example.. i just changed the SSID and password.. 08_7440.zip

i have available

• one ESP32-S2-Sonia-1_V1.2
• one ESP32-C3-DevKitC-02v1.1 but remember that 3 other esp32s3 didn't show the same error at the same time, so we might have to wait a lot before seeing it on these other devices.

[xueyunfei998]

Ok, please use ESP32-S2 and ESP32-C3 for a comparative test to see if this problem can occur.thanks

[KonssnoK]

you mean without modified wifi library?

[xueyunfei998]

you mean without modified wifi library?

Yes, test ESP32-S2 and ESP32-C3 with normal lib.

[KonssnoK]

@xueyunfei998 for now i can't see any log on S2 and C3. Also the S3 with wifi station firmware is not logging anything. Meanwhile, my mesh esp32s3 is dumping the error (4 devices attached to the same AP)

E (17363311) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17363753) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17366374) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17367423) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17367702) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17368346) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17368750) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17369504) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17369521) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17369897) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17370028) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17370569) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17370929) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17371093) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17371125) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17371241) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17371339) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17371441) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17371617) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17371945) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17372354) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17372567) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17372715) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17372977) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17373129) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17373190) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17373945) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17374550) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17374648) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17374861) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17375058) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17375287) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17375369) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17375680) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17375779) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17376073) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17376581) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17376860) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17377253) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17377384) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17377762) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (17378678) wifi:AP has neither DSSS parameter nor HT Information, drop it

[KonssnoK]

@xueyunfei998

ok it is happening also on esp32s2 with ip_internal_network example

E (21362) wifi:AP has neither DSSS parameter nor HT Information, drop it
I (22832) mesh_main: Tried to publish layer:1 IP:192.168.43.177
I (22832) mesh_mqtt: sent publish returned msg_id=32760
I (22832) mesh_main: Received Routing table [0] 7c:df:a1:39:4e:2e
I (22832) mesh_main: Sending routing table to [0] 7c:df:a1:39:4e:2e: sent with err code: 0
I (22992) mesh_mqtt: MQTT_EVENT_PUBLISHED, msg_id=32760
E (23712) wifi:AP has neither DSSS parameter nor HT Information, drop it
I (24842) mesh_main: Tried to publish layer:1 IP:192.168.43.177
I (24842) mesh_mqtt: sent publish returned msg_id=26946
I (24842) mesh_main: Received Routing table [0] 7c:df:a1:39:4e:2e

And it happens also on C3

I (16796) mesh_main: Sending routing table to [0] 7c:df:a1:ba:48:d4: sent with err code: 0
I (16806) mesh_main: Received Routing table [0] 7c:df:a1:ba:48:d4
I (16956) mesh_mqtt: MQTT_EVENT_PUBLISHED, msg_id=62596
E (16976) wifi:AP has neither DSSS parameter nor HT Information, drop it
I (18806) mesh_main: Tried to publish layer:1 IP:192.168.43.210
I (18806) mesh_mqtt: sent publish returned msg_id=31612
I (18806) mesh_main: Sending routing table to [0] 7c:df:a1:ba:48:d4: sent with err code: 0
I (18806) mesh_main: Received Routing table [0] 7c:df:a1:ba:48:d4
I (18976) mesh_mqtt: MQTT_EVENT_PUBLISHED, msg_id=31612
E (20116) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (20756) wifi:AP has neither DSSS parameter nor HT Information, drop it
I (20816) mesh_main: Tried to publish layer:1 IP:192.168.43.210
I (20816) mesh_mqtt: sent publish returned msg_id=40720
I (20816) mesh_main: Sending routing table to [0] 7c:df:a1:ba:48:d4: sent with err code: 0
I (20816) mesh_main: Received Routing table [0] 7c:df:a1:ba:48:d4
I (20976) mesh_mqtt: MQTT_EVENT_PUBLISHED, msg_id=40720
E (21016) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (21286) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (21836) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (22056) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (22216) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (22246) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (22466) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (22656) wifi:AP has neither DSSS parameter nor HT Information, drop it
I (22826) mesh_main: Tried to publish layer:1 IP:192.168.43.210
I (22826) mesh_mqtt: sent publish returned msg_id=14629
I (22826) mesh_main: Sending routing table to [0] 7c:df:a1:ba:48:d4: sent with err code: 0
I (22836) mesh_main: Received Routing table [0] 7c:df:a1:ba:48:d4
I (22986) mesh_mqtt: MQTT_EVENT_PUBLISHED, msg_id=14629
E (23286) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (24296) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (24316) wifi:AP has neither DSSS parameter nor HT Information, drop it
I (24836) mesh_main: Tried to publish layer:1 IP:192.168.43.210
I (24836) mesh_mqtt: sent publish returned msg_id=50481
I (24836) mesh_main: Sending routing table to [0] 7c:df:a1:ba:48:d4: sent with err code: 0
I (24836) mesh_main: Received Routing table [0] 7c:df:a1:ba:48:d4
I (24996) mesh_mqtt: MQTT_EVENT_PUBLISHED, msg_id=50481
E (25136) wifi:AP has neither DSSS parameter nor HT Information, drop it
E (25246) wifi:AP has neither DSSS parameter nor HT Information, drop it

so probably using station + ap triggers the issue more often and it-s independent from used hardware.

Please redo your internal tests using the mesh/ip_internal_network

[xueyunfei998]

hi @KonssnoK s3.txt esp32s3.zip

Please use this lib for testing, and you need to add S3.txtpatch.

Every time you provide a log, you need to provide the corresponding grab packet.

Please also use this wifi station example for testing.

[KonssnoK]

@xueyunfei998 is this patch still on top of 6c5fb29c2c513936ecefa7cdf49fb324e316546e ?

[xueyunfei998]

@xueyunfei998 is this patch still on top of 6c5fb29 ?

yes

[KonssnoK]

@xueyunfei998 where do i find the grab packet?

recv becon ,sta input dst is ffffffffffff
rst is eacbbc919fed
sta input seqno is 458, rx_length is 311
ssid is 0, ssid_length is 4
ssid_length is 4
recv becon ,sta input dst is ffffffffffff
rst is decbbc919fed
sta input seqno is 2427, rx_length is 266
ssid is 0, ssid_length is 0
ssid_length is 0
recv becon ,sta input dst is ffffffffffff
rst is 42237b81dfd2
sta input seqno is 3497, rx_length is 119
ssid is 221, ssid_length is 77
E (317901) wifi:AP has neither DSSS parameter nor HT Information, drop it
recv becon ,sta input dst is ffffffffffff
rst is bca511ad86a0
sta input seqno is 2334, rx_length is 268
ssid is 0, ssid_length is 0
ssid_length is 0
recv becon ,sta input dst is ffffffffffff
rst is e0cbbc919fed
sta input seqno is 4020, rx_length is 290
ssid is 0, ssid_length is 5
ssid_length is 5
recv becon ,sta input dst is ffffffffffff
rst is e6cbbc919fed
sta input seqno is 1164, rx_length is 351
ssid is 0, ssid_length is 12

[KonssnoK]

@xueyunfei998 also this part of the patch fails

diff --git a/components/lwip/lwip b/components/lwip/lwip
--- a/components/lwip/lwip
+++ b/components/lwip/lwip
@@ -1 +1 @@
-Subproject commit 76303df2386902e0d7873be4217f1d9d1b50f982
+Subproject commit 76303df2386902e0d7873be4217f1d9d1b50f982-dirty

[xueyunfei998]

@KonssnoK Provide the complete log

[xueyunfei998]

E (317901) wifi:AP has neither DSSS parameter nor HT Information, drop it

Don't worry about this failure, just modify here.

diff --git a/components/esp_rom/esp32s3/ld/esp32s3.rom.ld b/components/esp_rom/esp32s3/ld/esp32s3.rom.ld index 2c7677ab86..39e35037f8 100644 --- a/components/esp_rom/esp32s3/ld/esp32s3.rom.ld +++ b/components/esp_rom/esp32s3/ld/esp32s3.rom.ld @@ -2032,7 +2032,7 @@ ieee80211_is_tx_allowed = 0x40005a78; ieee80211_output_pending_eb = 0x40005a84; ieee80211_output_process = 0x40005a90; ieee80211_set_tx_desc = 0x40005a9c; -sta_input = 0x40005aa8; +/sta_input = 0x40005aa8;/

[xueyunfei998]

hi @KonssnoK In a log file, duplicate the failed log several times.

When I want to find out the problem, every similarity and difference, There is no problem in the log of a line of problems.

E (317901) wifi:AP has neither DSSS parameter nor HT Information, drop it

[xueyunfei998]

hi @KonssnoK Please test with this lib, This lib adds information about the channel, such as

sta input seqno is 2848, rx_length is 270,channel is 12

If there is a beacon problem in your log, please grab the packet on the channel in log.

If the network capture packet is too big to be transmitted for a long time, please send it to my mailbox.

xueyunfei@espressif.com

Upload the log corresponding to this network capture packet.

[KonssnoK]

@xueyunfei998 uhm, i did replaced the new libraries but i don't see the channel in the log... 🤔 (or there is a missing attachment)

[KonssnoK]

@xueyunfei998 i'm attaching a trace on channel 6, where the devices are seeing the issue.

Notes:

• 3 devices attached to the same wifi hotspot, 2 with station firmware (dev1 dev2), 1 with ip_internal_mesh firmware (dev0) (all out of the box)
• the 2 station firmwares do NOT report any error
• the ip_internal_mesh reports the error from devices with size-invalid SSID -> This is garbage buffers
• meanwhile tracealyzer running on the same channel

Big question mark: - Why is the device using the mesh ip network receiving beacons from everybody after connection and instead the station example receives beacons only from its AP???

10_dev0.log 10_dev1.log 10_dev2.log

Attaching Wireshark log in a few seconds EDIT: wireshark logs tracelogchan6.pcapng.tar.gz

[xueyunfei998]

@xueyunfei998 uhm, i did replaced the new libraries but i don't see the channel in the log... thinking (or there is a missing attachment)

Sorry, please use this lib test. This lib log is as follows：

recv becon ,dst ffff rst 34f716d584f5 seqno 50, rx_len 389,channel 1 ele1 0, len1 7 ele2 1, len2 8 ssid_length is 7

This log contains the information of the channel. Please check the channel where the beacon in question is located in the log, and then grab the packet in this channel.

• the 2 station firmwares do NOT report any error

This is because sta has connected to the router, and sta will only receive beacon from the connected router, so there will be no problem.

Please continue to use sta's example to continue the test, but you need to modify the example so that sta can connect to a non-existent SSID, and STA will scan beacon on channels 1-13.

Use the following patch to retest：

this patch still on top of 6c5fb29

esp32s3.zip s3-test.txt

In addition, be sure to grab the packet on the channel of beacon in question. The channel information is as above. And provides the log corresponding to the network capture packet.

If the network capture file is too big, please send it to my mailbox.

[KonssnoK]

it's always on channel 6. Now i'll get the wireshark logs

recv becon ,dst  ffff
rst e6cbbc91a456
seqno 1790, rx_len  351,channel  1
ele1 0, len1  12  ele2 1, len2 6
ssid_length is 12
recv becon ,dst  ffff
rst eacbbc91a456
seqno 4089, rx_len  311,channel  1
ele1 0, len1  4  ele2 1, len2 6
ssid_length is 4
recv becon ,dst  ffff
rst 6afa785cafb0
seqno 3365, rx_len  234,channel  6
ele1 0, len1  15  ele2 1, len2 8
ssid_length is 15
recv becon ,dst  ffff
rst c2e558a5251a
seqno 169, rx_len  209,channel  6
ele1 221, len1  167  ele2 0, len2 0
E (13754) wifi:AP has neither DSSS parameter nor HT Information, drop it
recv becon ,dst  ffff
rst d240ef6f60d1
seqno 18, rx_len  326,channel  6
ele1 0, len1  21  ele2 1, len2 8
ssid_length is 21
recv becon ,dst  ffff
rst bca511ad86a0
seqno 2373, rx_len  267,channel  6
ele1 0, len1  0  ele2 1, len2 8
ssid_length is 0
recv becon ,dst  ffff
rst 7cdfa1e27431
seqno 2244, rx_len  317,channel  6
ele1 0, len1  0  ele2 1, len2 8
ssid_length is 0

[KonssnoK]

@xueyunfei998 here are logs 11_dev0.log and trace 11_dev0.pcapng.tar.gz

[xueyunfei998]

Please grab the packet on channel 6, this is channel 11.

[KonssnoK]

argh, airmon is ignoring the argument then :( let me try again

[KonssnoK]

New log with new shark @xueyunfei998

12_dev0.log

12_dev0.pcapng.tar.gz

[KonssnoK]

@xueyunfei998 i'm comparing log and capture.

NOTES:

I can see that in the capture there are beacons on channel 6 that are reported in the log as other channels

• 8261b44c79c9 reported as channel 5, 2437MHz on wireshark
• 1c61b44c79c7 reported as channel 5, 2437MHz on wireshark

on top,

• there are repeated beacons!

Example of one occurrence on channel 6 where 2 beacons are repeated

recv becon ,dst  ffff
rst 6afa785cafb0                        JOJO
seqno 1752, rx_len  234,channel  6
ele1 0, len1  15  ele2 1, len2 8
ssid_length is 15

recv becon ,dst  ffff
rst d240ef6f60d1
seqno 1360, rx_len  326,channel  6
ele1 0, len1  21  ele2 1, len2 8
ssid_length is 21

recv becon ,dst  ffff
rst bca511ad86a0                        NETGEAR
seqno 2574, rx_len  267,channel  6
ele1 0, len1  0  ele2 1, len2 8
ssid_length is 0

recv becon ,dst  ffff
rst 6abee1cf4694
seqno 3312, rx_len  209,channel  6
ele1 221, len1  167  ele2 0, len2 0
E (15784) wifi:AP has neither DSSS parameter nor HT Information, drop it

recv becon ,dst  ffff
rst fa259288d7c3                        0000000000000000
seqno 3306, rx_len  255,channel  6
ele1 0, len1  9  ele2 1, len2 8
ssid_length is 9

DUPLICATED??

recv becon ,dst  ffff
rst 6afa785cafb0
seqno 1753, rx_len  234,channel  6
ele1 0, len1  15  ele2 1, len2 8
ssid_length is 15

recv becon ,dst  ffff
rst d240ef6f60d1                        
seqno 1361, rx_len  326,channel  6
ele1 0, len1  21  ele2 1, len2 8
ssid_length is 21

[xueyunfei998]

Please use this lib test t and keep the last patch changes.

esp32s3.zip

this patch still on top of 6c5fb29

This lib change, scanning to an abnormal beacon, will print out all bytes of this beacon.

To prevent wdt from printing, turn off wdt in menuconfig.

[KonssnoK]

recv ELEMID_VENDOR
recv ELEMID_VENDOR
recv ELEMID_VENDOR
recv ELEMID_VENDOR
recv becon ,dst  ffff
rst 72343980f44d
seqno 2045, rx_len  209,channel  6
b1  b   d1  10  0   0   0   0   0   0   6   a3  21  8c  18  0   22  8c  60  84  a0  c1  c7  4f  35  49  a   3b  0   0   50  75  0   0   0   0   0   0   0   0   0   0   0   0   d1  10  d   0   80  0   0   0   ff  ff  ff  ff  ff  ff  72  34  39  80  f4  4d  50  6f  9a  1   8e  74  d0  7f  be  d   ca  f0  47  aa  4   0   64  0   20  5   dd  a7  50  6f  9a  13  0   2   0   90  d3  1   d   0   72  34  39  80  f4  4d  d3  90  0   0   0   0   0   f   9   0   0   9   4   14  1   22  88  13  8   12  17  0   3a  20  0   12  0   1   12  20  0   8   ff  ff  ff  ff  ff  ff  ff  ff  11  51  20  0   0   12  3d  0   3a  21  0   12  0   1   12  20  0   8   ff  f0  ff  ff  ff  f0  ff  ff  11  80  4   0   1   12  0   1   12  20  0   8   0   f   0   0   0   f   0   0   11  80  20  0   1   7   0   1a  2   11  80  4   0   1   7   0   12  2   11  80  4   0   1   1e  14  0   0   0   0   0   0   0   0   0   0   0   0   0   1   80  64  0   0   0   0   0   b   2   0   49  54  dd  9   0   0   17  f2  4   4   0   0   0   0   0   0   0   f0  recv ELEMID_VENDOR
E (1914) wifi:AP has neither DSSS parameter nor HT Information, drop it
recv ssid
recv ELEMID_VENDOR
recv ELEMID_VENDOR
recv ELEMID_VENDOR
recv ELEMID_VENDOR
recv ELEMID_VENDOR
recv ELEMID_VENDOR
recv ELEMID_VENDOR
recv ELEMID_VENDOR

[KonssnoK]

@xueyunfei998 here is a log with many packets 12_dev0.log

[xueyunfei998]

hi @KonssnoK esp32s3.zip

plz test with this lib

this lib still on top of 6c5fb29

[KonssnoK]

Hello @xueyunfei998 , i will not be in the office for the next 10 days, i'll try as soon as i get back. Thanks.

[KonssnoK]

Hello @xueyunfei998 , is this patch supposed to remove the warnings? I'm trying on a device and i don't see any relevant output anymore (i know the issue is happening on another device with old library instead)

[xueyunfei998]

HI @KonssnoK

Found the following through packet capture and log: 1 There are indeed abnormal beacon packages in your environment. 2 I didn't find this abnormal beacon in the network capture packet either, can't resolve this abnormal beacon by analyzing wifi lib and wireshark, so can ignore it when receive this abnormal beacon.

Now, do you have any other problems during the testing of this latest wifilib?

[KonssnoK]

yeah it's strange that wireshark doesn't pick up the same packet. maybe there is some filtering ?

with the latest lib i did not see the the log. Was this expected?

[xueyunfei998]

hi @KonssnoK Wireshark didn't catch this package, not because of filtering, but because wireshark couldn't parse this package, and lost this exception beacon. In debug, it was found that this problem was caused by an abnormal beacon, If losing this unusual beacon will not cause other problems in your project, I think it is acceptable.

[xueyunfei998]

with the latest lib i did not see the the log. Was this expected?

The latest wifilib has been optimized, no abnormal log is printed, and other wifi bug will not appear in your project, which is the expected result.

[KonssnoK]

ok good thanks! When can we expect these fixed to be propagated to v4.4?

[rglissmann]

I'm getting the "wifi:AP has neither DSSS parameter nor HT Information, drop it" error too. My router is an Actiontec CenturyLink C1000A and I've used a ESP32c3 and a ESP-WROOM-32 processor. I've tried the station and power_save examples in v4.4.2 and v5.0 and still get the error. I can't make further progress on my project with this error causing the wifi connection to drop.

[xueyunfei998]

hi @KonssnoK @AxelLin @rglissmann

The reason for this problem has been found. The internal part is already in the review stage, and it will be merged into the corresponding branch as soon as possible.

[IndigoSamuels]

Ive been programming and watching the ESP32 monitor for years now, constantly for last few weeks... and I just now today 01/03/23 started seeing this error message in my serial monitor.. "E (19331) wifi:AP has neither DSSS parameter nor HT Information, drop it" ... Im only using ESP NOW so I do Wifi.begin() but feed it an incorrect AP and password name... as I have been doing for over 4 years now... Im just adding to a program Ive been using for at least a year...I noticed the blue LED was flashing synchronically like once per second and sometimes a little faster and it was doing that for a few days that I noticed, I gave it alot of thought but had to finish what I was doing... but my thoughts almost immediately went to I Robot when they were getting an update... did the ESP get some kind of backdoor update through ESP Now... is there a way for someone to remotely update it without having the Update API and a server based post function... is there some kind of hidden SSH which can be accessed through ESP NOW like a backdoor botnet type thing? I have to ask and I need to know because I cant sell any product based on ESP with those doubts...

[AxelLin]

hi @KonssnoK @AxelLin @rglissmann

The reason for this problem has been found.

Could you share the root cause ?

[KonssnoK]

hi @KonssnoK @AxelLin @rglissmann

The reason for this problem has been found. The internal part is already in the review stage, and it will be merged into the corresponding branch as soon as possible.

@xueyunfei998 could you please remove the awaiting response status? thanks

[rglissmann]

Thanks for the update. Looking forward to the released code.

-Randy

On Wed, Jan 25, 2023 at 1:57 AM Kons @.***> wrote:

hi @KonssnoK https://github.com/KonssnoK @AxelLin https://github.com/AxelLin @rglissmann https://github.com/rglissmann

The reason for this problem has been found. The internal part is already in the review stage, and it will be merged into the corresponding branch as soon as possible.

@xueyunfei998 https://github.com/xueyunfei998 could you please remove the awaiting response status? thanks

— Reply to this email directly, view it on GitHub https://github.com/espressif/esp-idf/issues/9283#issuecomment-1403280580, or unsubscribe https://github.com/notifications/unsubscribe-auth/AG54XR7VAKZ4UEJCMTIYX63WUDTGTANCNFSM52TPNRAQ . You are receiving this because you were mentioned.Message ID: @.***>

[KonssnoK]

Hello @xueyunfei998 , could you reference the commit where this is pushed? When will it be backported to v4.4? Thanks

[rglissmann]

Was this implemented in the recent v4.4.4 release?

Thanks

On Fri, Feb 3, 2023 at 1:38 AM Kons @.***> wrote:

Hello @xueyunfei998 https://github.com/xueyunfei998 , could you reference the commit where this is pushed? will it be backported to v4.4? Thanks

— Reply to this email directly, view it on GitHub https://github.com/espressif/esp-idf/issues/9283#issuecomment-1415355502, or unsubscribe https://github.com/notifications/unsubscribe-auth/AG54XRZVXH35BFHRUV66ZITWVS7WPANCNFSM52TPNRAQ . You are receiving this because you were mentioned.Message ID: @.***>

[KonssnoK]

no i think it was pushed to wifi_lib but not yet in v4.4 esp-idf

[xueyunfei998]

hi @KonssnoK @rglissmann

This change has been backport to version 4.4

Please use the latest 4.4 test, thanks

[xueyunfei998]

hi @KonssnoK @rglissmann

sorry I made a mistake

Fix on master branch is available at https://github.com/espressif/esp-idf/commit/ec8a702a8f3f2f3bb9599e4b67c165f404ce8de7, and backport on release/4.4 has been merged internally but has not synchronized into GitHub. It was not included in the v4.4.4 release, but will included in the next release of release/4.4.

[KonssnoK]

ok as expected, thanks @xueyunfei998

[AxelLin]

v4.4 fix: f73a2cd0f9df9b87788f7117f1e5e141e19ac1bb