http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1807
Summary: BACnet UnconfirmedEventNotification inconsistent
decoding
Product: Wireshark
Version: SVN
Platform: Other
OS/Version: Linux
Status: NEW
Severity: Minor
Priority: Low
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: steve@xxxxxxxxx
Build Information:
wireshark 0.99.7 (SVN Rev 22559)
Copyright 1998-2007 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.10.6, with GLib 2.12.4, with libpcap 0.9.4, with libz
1.2.3, without libpcre, without Net-SNMP, without ADNS, without Lua, without
GnuTLS, without Gcrypt, without Kerberos, without PortAudio, without AirPcap.
NOTE: this build doesn't support the "matches" operator for Wireshark filter
syntax.
Running on Linux 2.6.17-11-generic, with libpcap version 0.9.4.
Built using gcc 4.1.2 20060928 (prerelease) (Ubuntu 4.1.1-13ubuntu5).
--
Report by Wireshark user of BACnet decoding: Decoding problem in BACnet
UnconfirmedEventNotification request for command-failure. Notification
Parameters are not decoded correctly depending on the packets that precede it.
When certain packets precede it, it is shown as Status_Flags, Status_Flags and
Status_Flags. When the packet is in isolation, it is shown as Abstract Type: 0,
status flags, Abstract Type: 1, which is correct but not very helpful.
command-failure (context tag 3) should be shown as Command_Value, Status_Flags
and Feedback_Value. Example captures will be attached.
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.