 | 1 | initial version |
I am using Wireshark to capture the 802.11be management frame. (Not able to add figure.) In the Association Request frame, one of the bit fields in ETH PHY Capabilities Information is displayed as: ETH PHY Bits 64-71 0X111100. However, the 1111 is extra bits and not defined in the 802.11be spec. I check that it will change to 4444 in the Association Response frame from an AP. Please let me know if you face the same issue. Thank you!
I am using Wireshark to capture the 802.11be management frame. (Not able to add figure.) In the Association Request frame, one of the bit fields in ETH PHY Capabilities Information is displayed as: ETH PHY Bits 64-71 0X111100. However, the 1111 is extra bits and not defined in the 802.11be spec. I check that it will change to 4444 in the Association Response frame from an AP. Please let me know if you face the same issue. Thank you!
I am using Wireshark to capture the 802.11be management frame. (Not able to add figure.) In the Association Request frame, one of the bit fields in ETH PHY Capabilities Information is displayed as: ETH PHY Bits 64-71 0X111100. However, the 1111 is extra bits and not defined in the 802.11be spec. I check that it will change to 4444 in the Association Response frame from an AP. Please let me know if you face the same issue. Thank you!
I am using Wireshark to capture the 802.11be management frame. (Not able to add figure.)
In the Association Request frame, one of the bit fields in ETH EHT PHY Capabilities Information is displayed as: ETH EHT PHY Bits 64-71 0X111100. However, the 1111 is extra bits and not defined in the 802.11be spec.
I check that it will change to 4444 in the Association Response frame from an AP.
Please let me know if you face the same issue. Thank you!
