Wireshark-dev: Re: [Wireshark-dev] Wrong Interpretation of GTS starting slot - Wireshark 1.10.0
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: Jeff Morriss <jeff.morriss.ws@xxxxxxxxx>
Date: Thu, 18 Jul 2013 12:30:16 -0400
On 07/18/13 02:31, S, Selvamegala wrote:

Hi,

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  0x2e represents both starting slot and
length, 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. Please help us by
fixing this or letting us know if it has already been fixed in a release?


It looks like you also opened this bug for this:

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=8946

so follow-ups should go to the bug rather than the mailing list.