-
Notifications
You must be signed in to change notification settings - Fork 7.1k
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
Reliable Promiscuous CSI extraction (IDFGH-540) #2909
Comments
@dakami Can you provide a demo to reproduce the issue? |
@dakami Hi, would you help share if any updates for this issue? Thanks. |
@TimXia Here is a demo, I would be glad to give you more informations if needed TLDR :I have the same issue and a stable setup to reproduce it! Details :Hi, I have exactly the same issue :
Hardware :ESP-WROVER-KIT V4.1 and SparkFun ESP32 Thing (both have the same comportment) Code to reproduce the error :Example of the error :Here is the content the "wifi_csi_info_t *data" field "buf" for consecutive frames
Result (note that the leading "0000" is added by my code to facilitate conversion to Wireshark)
The addresses "8C:0C:90:01:1E:C8" and "F0:79:60:0E:C7:FC" are valid addresses (of AP around me), "00:00:90:01:1E:C8" is not. Suggestion/guess :From consecutive frames it seems that the highlighted part stay the same The "80 00" (beacon frame) at the start of the frame let me think that a mask is wrong, which result in this semi-masking Thank you |
After further investigation (and help) CSI frames with So the bug is probably somewhere in here |
Hi even I'm noticing the same issue as above namely in the CSI callback, I'm getting non CSI frames. Check out the following link Also do we need to enable promiscuous mode to receive CSI. I disabled promiscuous mode and only enabled CSI mode. The code wasn't crashing but in the CSI callback I wasn't receiving any frames. |
What do you mean the I have tested locally using the demo https://github.com/jonathanmuller/ESP32-gather-channel-state-information-CSI-/blob/master/gather_csi_in_promiscuous/main/csi.c, and I get the following data:
What do you mean by saying |
@zhangyanjiaoesp Hi,
So I believe there is data in those frame that don't bellong to them
Maybe you were lucky because your environment doesn't match mine, maybe it was fixed.
Valid = phase and amplitude are continuous |
My test info is as follows:
|
@dakami Thanks for reporting and sharing updates, will close due to short of feedback, feel free to reopen with more updates. |
It's implied in wifi.rst that CSI can be extracted from sniffed packets, and I do intermittently get boots where random frames fire the CSI callback. I'm definitely getting promiscuous frames (that callback fires), and playing with the promisc filters doesn't seem to yield more frames. (I do eventually get "unknown CSI error!" though.) I've also tried various orderings of esp_wifi_start and esp_wifi_connect, as well as both the NULL and STA modes.
Any ideas?
The text was updated successfully, but these errors were encountered: