Wireshark-bugs: [Wireshark-bugs] [Bug 10500] display MEP ID in decimal in OAM Y.1731 Synthetic L
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Thu, 25 Sep 2014 12:46:32 +0000

changed bug 10500


What Removed Added
Status UNCONFIRMED CONFIRMED
Summary wrong decode at ethernet OAM Y.1731 Synthetic Loss Message and Reply PDU display MEP ID in decimal in OAM Y.1731 Synthetic Loss Message and Reply PDU
Ever confirmed   1

Comment # 7 on bug 10500 from 
(In reply to Maic Groffmann from comment #6)
> Why you decode (see my attatched error description) in the second picture
> (frame 4;  ETH-CCM (Ethernet Continuity Check Message) (the first picture
> was the “About Wireshark”) the local MEP ID (Maintenance Association End
> Point Identifire) in plan 2 (Packet Details view) to 100 in decimal and not
> to hex 0x0064?

Because this is how the initial author of this dissector decided to display
those fields: as a decimal number on one side, and as a byte stream on the
other side.
I agree that is makes sense to have a unified display across messages.

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