Bug ID |
9056
|
Summary |
DNP3 - Incorrect Object name when using read specific data type
|
Classification |
Unclassified
|
Product |
Wireshark
|
Version |
1.6.2
|
Hardware |
x86
|
OS |
Windows 7
|
Status |
UNCONFIRMED
|
Severity |
Minor
|
Priority |
Low
|
Component |
Wireshark
|
Assignee |
[email protected]
|
Reporter |
[email protected]
|
Created attachment 11413 [details]
RED: Object 4 default variation (0); ORANGE: Object 3 default variation (0)
Build Information:
Version 1.6.2 (SVN Rev 38931 from /trunk-1.6)
Copyright 1998-2011 Gerald Combs <[email protected]> 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 32-bit Windows 7 Service Pack 1, build 7601, 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
----------------
Downloaded as installer.
--
When using read specific data type in DNP3, the Read function displays "Unknown
Object - Abort Decoding..." where it should display: "Double-bit Input Change
Default variation (obj:04, var:Default)"
You are receiving this mail because:
- You are watching all bug changes.