Wireshark-bugs: [Wireshark-bugs] [Bug 4594] New: Wireshark decode wrong with FCOE with CRC in th
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Wed, 17 Mar 2010 19:55:21 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4594

           Summary: Wireshark decode wrong with FCOE with CRC in the end.
           Product: Wireshark
           Version: 1.2.6
          Platform: Other
        OS/Version: Windows XP
            Status: NEW
          Severity: Major
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: tietao.yan@xxxxxxxxxxx


Created an attachment (id=4415)
 --> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=4415)
Screenshot of Wireshark decode FCOE with ETHII CRC

Build Information:
Version 1.3.3 (SVN Rev 31863 from /trunk)
and Version 1.2.6 has same problem. 
--
Per RFC 3643 The FCOE frame is encapsulated in a Header (like ETHII header).
Please refer to below. At the end of the frame, there will be 4 bytes CRC
added. 
      +--------------------+
      |       Header       |
      +--------------------+-----+
      |        SOF         |   f |
      +--------------------+ F r |
      |  FC frame content  | C a |
      +--------------------+   m |
      |        EOF         |   e |
      +--------------------+-----+
When the packets captured with no ETHII CRC in the end, the wireshark works
correct. But when the packets captured with ETHII CRC in the end, the wireshark
decode as following: 
Bytes in Packet ---> Decoded by Wireshark
ETHII CRC       ---> FCOE EOF.
FCOE EOF        ---> FCOE CRC (Displayed as error)
FCOE CRC        ---> a part of FCOE Data
Details please refer to attached pcap files and screenshots.

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.