[Alexis La Goutte <alexis.lagoutte@xxxxxxxxx>]

On Tue, Jul 16, 2013 at 1:16 PM, S, Selvamegala <Selvamegala.S@xxxxxxxxx> 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?

 

Thanks & regards,

Selvamegala

Atmel Corporation

selvamegala.s@xxxxxxxxx

Hi,

There is a lot of change between 1.8 and 1.10... (impossible to list all change... ), it is easy to try with the latest stable release (there is a portable release for Windows !)

After if the issue, it's always here, the better is to create a bug in bugtracker ( https://bugs.wireshark.org) with a sample.

Regards,

 

 

 

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe