Wireshark-bugs: [Wireshark-bugs] [Bug 6458] New: [BACnet] ReadRange-ACK on TrendLog Log-Buffer n
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Thu, 13 Oct 2011 10:40:04 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6458

           Summary: [BACnet] ReadRange-ACK on TrendLog Log-Buffer not
                    correctly dissected
           Product: Wireshark
           Version: 1.6.2
          Platform: x86
        OS/Version: Windows XP
            Status: NEW
          Severity: Major
          Priority: Low
         Component: Wireshark
        AssignedTo: bugzilla-admin@xxxxxxxxxxxxx
        ReportedBy: nuabaranda@xxxxxx


Created an attachment (id=7226)
 --> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=7226)
Example packet dump

Build Information:
Version 1.6.2 (SVN Rev 38931 from /trunk-1.6)

Copyright 1998-2011 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 (32-bit) with GTK+ 2.22.1, with GLib 2.26.1, with WinPcap (version
unknown), with libz 1.2.5, without POSIX capabilities, without libpcre, with
SMI
0.4.8, with c-ares 1.7.1, with Lua 5.1, without Python, with GnuTLS 2.10.3,
with
Gcrypt 1.4.6, with MIT Kerberos, with GeoIP, with PortAudio V19-devel (built
Sep
 7 2011), with AirPcap.

Running on Windows XP Service Pack 3, build 2600, with WinPcap version 4.1.2
(packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch 1_0_rel0b
(20091008), GnuTLS 2.10.3, Gcrypt 1.4.6, without AirPcap.

Built using Microsoft Visual C++ 9.0 build 21022
--
Wireshark fails to dissect readRange-ACK APDUs on the TrendLog Log-Buffer
property. See the attached example:

1) Item 1: logDatum is of type log-status (tag 0). Wireshark seems to be not
able to interpret that tag.

2) Item 2: logDatum is of type failure (tag 8). Wireshark seems to benot able
to interpret that tag and completely gives up to dissect.

As the request was generated using VTS I also attach the VTS export showing its
correct interpretation of the ACK.

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.