| Bug ID |
9047
|
| Summary |
EPL: Dissection for WriteMultipleParameter, Node Alias, SDO/ASND structuring
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
SVN
|
| Hardware |
All
|
| OS |
All
|
| Status |
UNCONFIRMED
|
| Severity |
Enhancement
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 11391 [details]
EPL: Dissection for WriteMultipleParameter, Node Alias, SDO/ASND structuring
Build Information:
TShark 1.11.0 (SVN Rev 51390 from master)
Copyright 1998-2013 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 (64-bit) with GLib 2.36.0, with libpcap, with libz 1.2.7, with POSIX
capabilities (Linux), without libnl, with SMI 0.4.8, with c-ares 1.9.1, with
Lua
5.1, without Python, with GnuTLS 2.12.23, with Gcrypt 1.5.0, with MIT Kerberos,
with GeoIP.
Running on Linux 3.8.0-26-generic, with locale de_DE.UTF-8, with libpcap
version
1.3.0, with libz 1.2.7.
Intel(R) Core(TM)2 Quad CPU Q8400 @ 2.66GHz
Built using gcc 4.7.3.
--
I have added the dissection of the cmd ID "WriteMultipleParameter" to the
dissector. It now dissects the payload in this SDO command and lists all
objects that are written individually with their respective Indices.
Also I cleaned up the code for WriteIndex and ReadIndex to mimic the new
WriteMultipleParameter code in display, and additionally designed the whole
code to better display the structure of the SDO message, by splitting the
information in the respective sequence and command layer.
Also I included an alias for (epl.src == 0x01 || epl.dest == 0x01) called
epl.node. It is not displayed but set with PROTO_ITEM_SET_HIDDEN. I have though
about making it visible, but it would mess up the dissection display
considerably. It will be added to the Powerlink guidelines in the future, so
that people using the openPOWERLINK framework can find it using the respective
documentation.
I plan on further updating the dissector with new features of powerlink, but
this will take some time. I will document my changes in the header of the
dissector.
You are receiving this mail because:
- You are watching all bug changes.