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
[TW#16436] Ability to send raw IEEE802.11 data frames #1256
Comments
This is already in our feature TODO list, but not in a very high priority it will be support in IDF3.1 |
Great to hear. Do you have a rough idea on when IDF3.1 would be released? In the meantime it would be great to have the ability to send raw frames with arbitrary frame counter values. I created #1332 for this. |
@seppestas until not I also not sure when to release IDF3.1, now we are trying to release IDF3.0. For IDF3.1 maybe it will be released in 1st month of 2018. |
Nearing the end of the first month of 2018 ^^. Is there any update on this? |
@seppestas still no update yet because too much work to do, but we will try to met v3.1 schedule. |
I need a way to send raw 4-address IEEE 802.11 data frames (Type 0b10 subtype 0b0000). The old , non-public
ieee80211_freedom_output
function worked fine for this, but the newesp_wifi_80211_tx
function seems to overwrite the frame counter of the frames, even if en_sys_seq is set to false, and it does not properly increment the frame counter.I understand the main reason for not wanting to make a public raw wifi API is that it could be used for sending things like DEAUTH messages. An API that only allows to send valid IEE802.11 frames and limits the allowed frame types (e.g no management frames) would solve this issue and greatly increase user-friendliness.
Please also make it possible to set the frame counter or at least make the frame counter increment correctly.
The text was updated successfully, but these errors were encountered: