802.11 FCS failed ACK and BLOCK-ACK packets
Posted: Sat Sep 02, 2023 11:14 pm
I have observed some strange behaviour (5.1).
I am monitoring 802.11 control frames packets in promiscuous mode:
For ACK and BLOCK ACK I always get `rx_state` = 0 which according to the comments in the code means no error.
The Documentation suggests that WIFI_PROMIS_FILTER_MASK_FCSFAIL should filter the failed packets. If I enable the filter I get no packets (ACK or BLOCK-ACK) at all. But I should still see all the packets I saw before, because their `rx_state` was == 0. But I don't . So something is logically incorrect ...
Please can you advice me, ideally I would like to see ACKS and BLOCK ACKS which have not failed FCS. At the moment moment with the WIFI_ROMIS_CTRL_FILTER_MASK_ALL I see many ACKS and BLOCK ACKS with `rx_state` == 0. But there are not seen by wireshark etc. So I assume the `rx_state` == 0 is actually a failed state ?
I am monitoring 802.11 control frames packets in promiscuous mode:
Code: Select all
void promiscuousmode(void *buffer, wifi_promiscuous_pkt_type_t type) {
wifi_promiscuous_pkt_t *p = (wifi_promiscuous_pkt_t *) buffer
printf("p->rx_ctrl.rx_state\n");
The Documentation suggests that WIFI_PROMIS_FILTER_MASK_FCSFAIL should filter the failed packets. If I enable the filter I get no packets (ACK or BLOCK-ACK) at all. But I should still see all the packets I saw before, because their `rx_state` was == 0. But I don't . So something is logically incorrect ...
Please can you advice me, ideally I would like to see ACKS and BLOCK ACKS which have not failed FCS. At the moment moment with the WIFI_ROMIS_CTRL_FILTER_MASK_ALL I see many ACKS and BLOCK ACKS with `rx_state` == 0. But there are not seen by wireshark etc. So I assume the `rx_state` == 0 is actually a failed state ?