Wireshark-bugs: [Wireshark-bugs] [Bug 8946] New: Wrong Interpretation of GTS starting slot
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Thu, 18 Jul 2013 06:51:43 +0000
Bug ID 8946
Summary Wrong Interpretation of GTS starting slot
Classification Unclassified
Product Wireshark
Version 1.10.0
Hardware x86
OS Windows XP
Status UNCONFIRMED
Severity Major
Priority Low
Component Wireshark
Assignee bugzilla-admin@wireshark.org
Reporter sselvamegala@gmail.com 

Created attachment 11225 [details]
In the highlighted beacon whole byte is interpreted as starting slot.

Build Information:
Wireshark 1.10.0
--
GTS starting slot in the Beacon frame is not parsed correctly. As per the Spec,
in the 3byte gts descriptor value bit 0- 15  refers Device Short address bit
16-19 – Starting slot bit 20-23 – GTS length. According to our observation Wire
shark parses the Whole byte (bit: 16- 23) as Starting slot. Attached is the 
Log file for the observation. In the highlighted beacon frame  0x1F represents
both starting slot(0x0F) and length(0x01), But the whole byte is interpreted as
starting slot.

Version : Latest stable release Wire shark 1.10.0.In the change log also was
not able to find an update relevant to this.

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