Wireshark-bugs: [Wireshark-bugs] [Bug 9056] DNP3 - Incorrect Object name when using read specifi

Date: Tue, 27 Aug 2013 11:40:20 +0000

Comment # 12 on bug 9056 from
The objects that are not handled yet are:

g0v254 - Device attributes - Non-specific all attributes request
g0v255 - Device attributes - List of all attribute variations
g4     - Double bit binary input
g85v1  - Data set prototype - With UUID
g86v1  - Data set Descriptor - Data set contents
g86v2  - Data set Descriptor - Characteristics
g86v3  - Data set Descriptor - Point index attributes
g87v1  - Data set - Present value
g88v1  - Data set - Snapshot
g113   - Virtual Terminal event data

Note that in all cases in the sample capture the DNP3 master is making requests
for these objects, the DNP3 slave is returning either a null result (as no
objects of the requested type are available) or an error indicating that the
slave doesn't know anything about the requested objects.

It's a smallish task to enhance the dissector so that the requests are handled
correctly, but decoding all the responses is a much bigger task and would
require (or at least made easier with) a capture that has responses of the
missing object types.


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