http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2576
Summary: Packet-fc is not dissecting destination and source ID
field properly
Product: Wireshark
Version: 1.0.0
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: Minor
Priority: Low
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: fschorr@xxxxxxxxxxx
Build Information:
Version 1.0.0
Copyright 1998-2008 Gerald Combs <gerald@xxxxxxxxxxxxx> 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 with GTK+ 2.12.8, with GLib 2.14.6, with WinPcap (version unknown),
with libz 1.2.3, without POSIX capabilities, with libpcre 7.0, with SMI 0.4.5,
with ADNS, with Lua 5.1, with GnuTLS 1.6.1, with Gcrypt 1.2.3, with MIT
Kerberos, with PortAudio V19-devel, with AirPcap.
Running on Windows XP Service Pack 2, build 2600, with WinPcap version 4.0.2
(packet.dll version 4.0.0.1040), based on libpcap version 0.9.5, without
AirPcap.
--
fchdr.d_id.data did not contain the FC destination address and fchdr.s_id.data
did not contain the FC source address. Therefore what was being displayed was
incorrect. I never did understand why fchdr.d_id.data and fchdr.s_id.data
values did not contain the proper information.
I instead decided to make this simple and just display the FC destination
address and FC Source address fields in the FC header. My "fix" needs to be
reviewed because it's possible that the proper fix is to figure why these two
variables do not have the proper information in the first place. The fields in
question are fc.d_id and .fc.s_id
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.