Closed lwj850533527 closed 2 months ago
@kapilkedawat , PTAL.
@mantriyogesh Is there any progress on this issue
Hi @lwj850533527, could you please share above dmesg, sniffer capture and firmware logs ?
@kapilkedawat dmesg not saved, only screenshots available sniffer capture.zip firmware logs.txt
@kapilkedawat I found some related settings. Is the MAC address incorrect due to lack of settings bool bssid_set; whether set MAC address of target AP or not. Generally, station_config.bssid_set needs to be 0; and it needs to be 1 only when users need to check the MAC address of the AP
@lwj850533527 please recheck in latest mater.
Hi mantriyogesh,
Feedback on an issue with the NG mode.The scene is connecting multiple APs same ssid. Sometimes the connection use for a long time. As shown in the figure,“06:f9:f8:1f:cd:fd”,“06:f9:f8:14:69:c7”,"06:f9:f8:14:66:4c",these three are APs with the same SSID and password. 14:35:12, it initiated an AP connection 14:36:46 it connect success The connection cost 1.5 minutes
From packet capture data, ESP32 sends authentication to an incorrect MAC address.For example: 14:35:14, kernel log it should sents authentication to “06:f9:f8:1f:cd:fd”, but cat packet it sents to “06:f9:f8:14:69:c7” From esp32c3 log, 14:35:14, it seems received an authentication response, but the processing result is abnormal
it is kernel log
it is esp32c3 log
it is omnipeek air interface packet capture data