ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
July 17th, 2024 | 10:00am-11:55am SGT (UTC+8) | Online

Wireshark-bugs: [Wireshark-bugs] [Bug 12926] New: Invalid Dissector Info for bacnet writePropert

Date: Tue, 20 Sep 2016 14:23:58 +0000
Bug ID 12926
Summary Invalid Dissector Info for bacnet writeProperty binary-output
Product Wireshark
Version 2.0.2
Hardware x86-64
OS All
Status UNCONFIRMED
Severity Major
Priority Low
Component Dissection engine (libwireshark)
Assignee [email protected]
Reporter [email protected]

Created attachment 14931 [details]
bacnet writeProperty on binary-output

Build Information:
Wireshark 2.0.2 (SVN Rev Unknown from unknown)

Copyright 1998-2016 Gerald Combs <[email protected]> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
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 Qt 5.5.1, with libpcap, with POSIX capabilities (Linux),
with libnl 3, with libz 1.2.8, with GLib 2.48.0, with SMI 0.4.8, with c-ares
1.10.0, with Lua 5.2, with GnuTLS 3.4.10, with Gcrypt 1.6.5, with MIT Kerberos,
with GeoIP, with QtMultimedia, without AirPcap.

Running on Linux 4.4.0-38-generic, with locale C, with libpcap version 1.7.4,
with libz 1.2.8, with GnuTLS 3.4.10, with Gcrypt 1.6.5.
Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz (with SSE4.2)

Built using gcc 5.3.1 20160407.

--
Dissection information for BACNet WriteProperty binary-output always shows the
value "0" for preset-value, even when write a "1".

- when writing "1":
BACnet-APDU 67     Confirmed-REQ   writeProperty[231] binary-output,0
present-value 

- when writing "0":
BACnet-APDU 67     Confirmed-REQ   writeProperty[233] binary-output,0
present-value 

Attached file contains frames that shows the problem.

The error only appears in the Info, the complete dissection of the packet show
the correct value.


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