-
Notifications
You must be signed in to change notification settings - Fork 7.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't send / sniff NDF packet (IDFGH-14417) #15197
Comments
@roger- |
@zhangyanjiaoesp I checked in Wireshark and noticed a flood of RTS messages and an inconsistent ACK. Things were better when I sent the packets to another ESP32 and when I used the undocumented API here to disable RTS. I also disabled promiscuous and CSI modes for this test. Does the ESP32 look for CTS with a destination address matching its own (true) MAC or the provided source in the buffer passed to esp_wifi_80211_tx? Unfortunately I still have an issue where no packets are sent when I enable promiscuous and CSI modes. I will debug more and update. |
the provided source in the buffer passed to |
Thanks! Was able to get everything working. |
Answers checklist.
IDF version.
5.1.5
Espressif SoC revision.
ESP32-S2 (revision v0.0)
Operating System used.
Linux
How did you build your project?
Command line with Make
If you are using Windows, please specify command line type.
None
Development Kit.
ESP32-S2-Saola-1
Power Supply used.
USB
What is the expected behavior?
My goal is to send a null data frame to a device and get the ACK (and examine the CSI ultimately). My ESP-32 is in STA and connected to an AP.
I'm generating a null data frame and transmitting it with
esp_wifi_80211_tx()
. The destination MAC is another device and I'm setting the source MAC in the frame to a unique MAC (which I use to filter later).I'm then sniffing and trying to find the ACK from the destination device, but I'm not receiving a response.
It worked in the past with 4.x.
What is the actual behavior?
I don't observe the expected packet.
I get many different ACKs, but none with a destination matching the source MAC.
I don't believe the NDF packets are being transmitted as I don't see them with a sniffer.
Steps to reproduce.
My transmit task looks like this:
And my promiscuous setup code:
And my promiscuous callback:
Debug Logs.
No response
More Information.
No response
The text was updated successfully, but these errors were encountered: