On Mar 22, 2009, at 10:52 AM, Dani Camps wrote:
Yes.
Then that's probably either
1) a Wireshark dissector bug, so it's not a question of capturing the
traffic;
2) a driver or libpcap bug where the packet data supplied to libpcap
isn't in the right format, so it's still not a question of capturing
the traffic.
I.e., it *is* capturing the traffic, it's not just showing you all the
layers in the capture.
You captured this with Wireshark or TShark, rather than tcpdump,
right? And you didn't specify "Limit each packet to [N] bytes" when
you captured, right?
Do you have an example of a capture where the dissection is stopping
at the 802.11 layer?
