Bug ID |
9125
|
Summary |
Wrong PROFINET frame id description for frame ids 0x8000 - 0xBBFF (RT class 2 unicast)
|
Classification |
Unclassified
|
Product |
Wireshark
|
Version |
1.10.1
|
Hardware |
All
|
OS |
All
|
Status |
UNCONFIRMED
|
Severity |
Normal
|
Priority |
Low
|
Component |
Dissection engine (libwireshark)
|
Assignee |
[email protected]
|
Reporter |
[email protected]
|
Build Information:
--
The PROFINET IO dissector shows a wrong frame id description for captured
PROFINET frames with a frame id of 0x8000 - 0xBBFF. The frame id-range is used
for RT class 2, unicast frames and is not used for RT class 1, unicast frames
like shown by the dissector, see
http://www.softing.com/home/de/profinet/io-specification/real-time-data-exchange/frame-id.php
for a list of PROFINET frame ids.
The code producing the invalid description can be found in the file
packet-pn-rt.c in the function static void
dissect_pn_rt(tvbuff_t *tvb, packet_info *pinfo, proto_tree *tree), line 591:
else if (u16FrameID <= 0x7FFF) {
pszProtShort = "PN-RT";
pszProtAddInfo = "reserved, ";
pszProtSummary = "Real-Time";
pszProtComment = "0x1000-0x7FFF: Reserved ID";
bCyclic = FALSE;
} else if (u16FrameID <= 0xBBFF) {
pszProtShort = "PN-RTC1";
pszProtAddInfo = "RTC1, ";
pszProtSummary = "cyclic Real-Time";
pszProtComment = "0x8000-0xBBFF: Real-Time(class=1 unicast): non
redundant, normal";
bCyclic = TRUE;
}
The case (u16FrameID <= 0xBBFF) contains the wrong frame id description.
Best regards,
Sven
You are receiving this mail because:
- You are watching all bug changes.