You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I originally reported this as a comment on issue #677.
The esp_wifi_80211_tx function seems to overwrite the frame counter of the frames sent using it, even if en_sys_seq is set to false.
When setting en_sys_seq to false the frame counter is always overwritten to 0. When setting en_sys_seq to true the frame counter follows the frame counter of frames sent by other components acting on WiFi (e.g AP beacons), but the frames sent by esp_wifi_80211_tx do not themselves cause the frame counter to increment. This happens both when WiFi was configured in AP and Station mode. Tested on ESP-IDF v2.1 and on the master branch (094e47f).
We currently have 2 different firmwares, one based on ESP-IDF v2.0 to support the low level IEEE802.11 functionality we need and one where we have a BLE PoC for configuration. Merging both to a newer version of the ESP-IDF would be a lot easier (and future proof) than trying to backport the BLE functionality.
I originally reported this as a comment on issue #677.
The
esp_wifi_80211_tx
function seems to overwrite the frame counter of the frames sent using it, even ifen_sys_seq
is set to false.When setting
en_sys_seq
to false the frame counter is always overwritten to 0. When settingen_sys_seq
to true the frame counter follows the frame counter of frames sent by other components acting on WiFi (e.g AP beacons), but the frames sent byesp_wifi_80211_tx
do not themselves cause the frame counter to increment. This happens both when WiFi was configured in AP and Station mode. Tested on ESP-IDF v2.1 and on the master branch (094e47f).The old
ieee80211_freedom_output
function did not have this behaviour, allowing to send frames with arbitrary frame counter values.The text was updated successfully, but these errors were encountered: