Wireshark-bugs: [Wireshark-bugs] [Bug 11544] New: Global Unique Identifider is parsed wrong
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Thu, 24 Sep 2015 07:36:33 +0000
Bug ID 11544
Summary Global Unique Identifider is parsed wrong
Product Wireshark
Version unspecified
Hardware All
OS All
Status UNCONFIRMED
Severity Normal
Priority Low
Component Dissection engine (libwireshark)
Assignee bugzilla-admin@wireshark.org
Reporter LipkeGu@gmail.com 

Created attachment 13882 [details]
DHCP ACK PACKET

Build Information:
Version 1.12.7 (v1.12.7-0-g7fc8978 from master-1.12)

Copyright 1998-2015 Gerald Combs <gerald@wireshark.org> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (64-bit) with GTK+ 2.24.23, with Cairo 1.10.2, with Pango 1.34.0, with
GLib 2.38.0, with WinPcap (4_1_3), with libz 1.2.5, with SMI 0.4.8, with c-ares
1.9.1, with Lua 5.2, without Python, with GnuTLS 3.2.15, with Gcrypt 1.6.2,
without Kerberos, with GeoIP, with PortAudio V19-devel (built Aug 12 2015),
with
AirPcap.

Running on 64-bit Windows 10, build 10240, with WinPcap version 4.1.3
(packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch 1_0_rel0b
(20091008), GnuTLS 3.2.15, Gcrypt 1.6.2, without AirPcap.
Intel(R) Core(TM)2 Quad  CPU   Q8200  @ 2.33GHz, with 4095MB of physical
memory.


Built using Microsoft Visual C++ 10.0 build 40219

Wireshark is Open Source Software released under the GNU General Public
License.

Check the man page and http://www.wireshark.org for more information.
--
When i Capture DHCP Packet, each DHCP Packet has this in following specified
GUID Error.

I have an VM in this reproduce case with GUID (shown on PXE boot and in byte
packets:

Shown in VM: 564dca43-34d6-13e6-fbcd-c64ada957a
Shown in Wireshark: 43ca4d56-d634-e613-fbcd-c64ada957af9

The First Part of the GUID is rotated, this Bug is as far in each Wireshark
version i have used. :(

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