Wireshark-bugs: [Wireshark-bugs] [Bug 3905] New: BACnet ReadProperty returns "something is going
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Mon, 17 Aug 2009 09:12:35 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3905

           Summary: BACnet ReadProperty returns "something is going wrong
                    here !!"
           Product: Wireshark
           Version: 1.2.1
          Platform: x86
        OS/Version: Windows XP
            Status: NEW
          Severity: Major
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: gri6507@xxxxxxxxx


Created an attachment (id=3524)
 --> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=3524)
PCAP log of BACnet traffic showing the problem

Build Information:
Version 1.2.1 (SVN Rev 29141)

Copyright 1998-2009 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.16.2, with GLib 2.20.3, with WinPcap (version unknown),
with libz 1.2.3, without POSIX capabilities, with libpcre 7.0, with SMI 0.4.8,
with c-ares 1.6.0, with Lua 5.1, with GnuTLS 2.8.1, with Gcrypt 1.4.4, with MIT
Kerberos, with GeoIP, with PortAudio V19-devel (built Jul 19 2009), with
AirPcap.

Running on Windows XP Service Pack 2, build 2600, with WinPcap version 4.1
beta5
(packet.dll version 4.1.0.1452), based on libpcap version 1.0.0, GnuTLS 2.8.1,
Gcrypt 1.4.4, without AirPcap.

Built using Microsoft Visual C++ 9.0 build 30729

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

Check the man page and http://www.wireshark.org for more information.
--
With any BACnet communicating tool, issue a ReadProperty to a device which
supports a Schedule object, reading the exception-schedule property array index
0. The device, as per the BACnet standard, returns the size of the
exception-schedule array as an unsigned number (confirmed by multiple sniffers
including VTS, and BAS-o-matic). However, Wireshark displays the property value
as "something is going wrong here !!".

The attached pcap log demonstrates this problem.


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