Wireshark-bugs: [Wireshark-bugs] [Bug 4594] Wireshark decode wrong with FCOE with CRC in the end

Date Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 30 Mar 2010 19:06:01 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4594

--- Comment #8 from Guy Harris <guy@xxxxxxxxxxxx> 2010-03-30 19:06:00 PDT ---
Actually, it appears that FCOE has the frame length in it; if we set the length
of the Ethernet payload in the FCOE dissector, just as we set it in, for
example, the IPv4 and IPv6 dissectors, that might help the Ethernet dissector's
heuristics figure out whether there's an Ethernet CRC in the captured data or
not.  (When capturing with libpcap/WinPcap, sometimes there is an FCS in
captured frames, and sometimes there isn't, and the underlying OS doesn't tell
you whether there is or not.)

I.e., don't close this yet.

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