Wireshark-bugs: [Wireshark-bugs] [Bug 9752] New: Problem with CAPWAP Wireshark Dissector
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Wed, 12 Feb 2014 20:44:59 +0000
Bug ID 9752
Summary Problem with CAPWAP Wireshark Dissector
Classification Unclassified
Product Wireshark
Version 1.10.5
Hardware All
OS All
Status UNCONFIRMED
Severity Minor
Priority Low
Component Dissection engine (libwireshark)
Assignee bugzilla-admin@wireshark.org
Reporter vemax78@gmail.com 

Created attachment 12555 [details]
example of capwap pcap

Build Information:
Version 1.10.5 (SVNRev 54262 from /trunk-1.10)
--
I'm writing an application that implements the CAPWAP protocol. I'm having
problems with parsing some types of packets. 


* The payload of CAPWAP Data Channel Keep-Alive is decoded as a frame Ethernet.
On RFC 5414 section 4.4.1 explains that the CAPWAP Data Channel Keep-Alive
packet contains only one or more message elements (no ethernet or native
frame). Session ID message element is mandatory.

* The payload of Data packet with native IEEE802.11 frame are decoded
incorrectly: it skips the first byte of the IEEE802.11 frame.

I attach an example of pcap file generated by my application


Bye
Massimo

You are receiving this mail because:
  • You are watching all bug changes.