IEEE 802.11 Packets - Random Parsing Crashing

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Capture packets in Wireshark with monitor mode enabled (all packet types 
appear as 802.11 in Wireshark)
2. Open the capture file 
3. DPKT will randomly be unable to parse packets, even though Wireshark can 
parse & display the packet appropriately. 
4: Looking at the output, you'll see that packet #34 causes the program to 
crash.

What is the expected output? What do you see instead?
I expected the packet to be able to be parsed successfully, however it instead 
causes an exception to occur and will crash the parse if the error message is 
not caught.

What version of the product are you using? On what operating system?
DPKT v1.8 on Windows 7.

Please provide any additional information below.
- Attached File1: "CaptureTestForSupport.pcap" -> This is a sample capture file 
that will demonstrate the error. The parsing error will occur on packet #34 
(always), despite the fact that DPKT will parse the same type of message packet 
before and after packet #34 without problems.
- Attached File2: "Traceback.txt" --> This the traceback that appears on the 
console.
- Attached File3: "PcapParserForSupport.py" --> This is the source for my 
python program. If it is too much text, let me know and I'll pull out the 
essentials for a smaller file.

Original issue reported on code.google.com by kokopell...@gmail.com on 2 Jul 2014 at 5:48

Attachments:

• Traceback.txt
• CaptureTestForSupport.pcap
• PcapParserForSupport.py

[GoogleCodeExporter]

I'll handle this one.

Original comment by timur.al...@gmail.com on 2 Jul 2014 at 5:59

• Changed state: Accepted

[GoogleCodeExporter]

Bug related to the FCS field parsing. Fixed in trunk.

Original comment by timur.al...@gmail.com on 3 Jul 2014 at 11:23

• Changed state: Fixed