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'm running nexmon_csi on Raspberry Pi 3B+ following this instruction. It's great that it has Frame Control (FC) information with the CSIs. But I also noticed that it seems cannot capture CSIs from some frame types like 0x88 (QoS Data) frames. For example, below are the pcap files I captured using wireshark, when my phone was connected to an ASUS AC86U router and played youtube videos. I can see it has many 0x88 frames:
However, from the CSIs captured by nexmon_csi on Raspberry Pi 3B+ (I only set the router's MAC address as the filter), I only saw FC like 0x80 and 0x94, but no 0x88. nexmon_csi on ASUS RT-AC86U can get CSIs from FC like 0x88 (check the figure here). So I'm confused about what happens on Raspberry Pi3B+, and why no CSIs from 0x88 frame types.
Thanks for any comments!
The text was updated successfully, but these errors were encountered:
HeyGF
changed the title
No 0x88 frames on Raspberry 3B+
No CSIs from 0x88 QoS Data frames on Raspberry 3B+
Oct 31, 2024
Hi,
I'm running nexmon_csi on Raspberry Pi 3B+ following this instruction. It's great that it has Frame Control (FC) information with the CSIs. But I also noticed that it seems cannot capture CSIs from some frame types like 0x88 (QoS Data) frames. For example, below are the pcap files I captured using wireshark, when my phone was connected to an ASUS AC86U router and played youtube videos. I can see it has many 0x88 frames:
However, from the CSIs captured by nexmon_csi on Raspberry Pi 3B+ (I only set the router's MAC address as the filter), I only saw FC like 0x80 and 0x94, but no 0x88. nexmon_csi on ASUS RT-AC86U can get CSIs from FC like 0x88 (check the figure here). So I'm confused about what happens on Raspberry Pi3B+, and why no CSIs from 0x88 frame types.
Thanks for any comments!
The text was updated successfully, but these errors were encountered: