Comment # 4
on bug 10500
from Maic Groffmann
yes, you are right. We are wondering. No where we configure the displayed local
and remote MEP ID. We configured 100 and 320 but not 64 and 140.
So I decide to open the Packet Bytes view in plan 3. And there I saw the
problem in wireshark.
In the second picture (frame 4; Ethernet Continuity Check Message) (the first
picture was the “About Wireshark”) you see the right behavior:
in plan 3 (Packet Bytes view) the local MEP ID (Maintenance Association End
Point Identifire) was 64 in hex
and in plan 2 (Packet Details view) the local MEP ID was 100 in decimal.
You are receiving this mail because:
- You are watching all bug changes.
