Atheros-CSI-Tool
Atheros-CSI-Tool copied to clipboard
Capturing of HT sounding packets
I am trying to capture the HT Sounding packet in order to analyze them. Taking a trace from the transmitter (while sending the CSI packet) captures the packet naming "Bogus IPv4 version" while regular beacon packets are fine.
Have you or anyone taken such traces before, why is the packet called bogus. Or if there is any specific way to capture the sounding frames. I am using TP-Link N750 (Atheros 9K series).
I am not sure. I think it is just some kind of special IP packets.
I met the same problem. But I found a person's page for introduction frame type about 802.11n in Wireshark: https://www.semfionetworks.com/blog/wireshark-how-to-check-if-a-data-frame-is-sent-using-80211n Isn't that a normal situation?
@hanstseng123 I did not continue on this Wireshark analysis later on. What I understood by the term "bogus packet" was that the packet was not received properly/bad checksum error or something like that. But I am not sure. Are you working/interested with 802.11n? Let me know we can talk on a separate page.
@sayaz First, I was thinking that the "aa" sequence which caused the error just the signal without any data contained.
And the situation(bogus packet) must the packet which is sent by sendData command.
Excluding the error I can't find anything special about HT-LTF.
The purpose of this test is want to find whether there is any sign about HT sounding in the packet.