This is our old Q&A Site. Please post any new questions and answers at

Hello, Perhaps this question had been asked before but I've been searching and could not find answer. I performed a ping from wifi client (laptop) and captured raw 802.11 packet via wireless nic interface. I used to WS to decode the packet and was able to see ping request clearly (802.11header, LLC, IP, ICMP, etc):

alt text

However it seemed that WS cannot decoded a ping reply when it is an 802.11 QoS data packet. Here I noticed the different is that the ping reply does have an extra QoS header and LLC had been decoded as WEP (?). Subsequently WS could not decoded the rest as a ping packet. Please let me know how to resolve this issue... Thanks in advance (btw, I am using WS Version 1.10.3 (SVN Rev 53022 from /trunk-1.10) and please pardon my (clumsy) drawing :))

alt text

asked 06 Nov '13, 17:26

dbdiep's gravatar image

accept rate: 0%

For the second packet, Wireshark apparently thinks the second packet has a QoS field when it appears not to. Please file a bug on the Wireshark bugzilla, and attach the capture file if at all possible.

permanent link

answered 06 Nov '13, 19:51

Guy%20Harris's gravatar image

Guy Harris ♦♦
accept rate: 19%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 06 Nov '13, 17:26

question was seen: 6,597 times

last updated: 06 Nov '13, 19:51

p​o​w​e​r​e​d by O​S​Q​A