https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2718
Guy Harris <guy@xxxxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
OS/Version|Windows XP |All
Platform|PC |All
--- Comment #3 from Guy Harris <guy@xxxxxxxxxxxx> 2008-07-18 11:20:34 PDT ---
SFD:
There are two layers involved here, the framing layer (preamble and SFD)
and the addresses-and-type/length layer. The framing layer is the same
regardless of whether the addresses-and-type/length layer has a length field or
a type field; see section 3, "Media access control frame structure", of IEEE
802.3-2005.
"Ethernet II" vs. "802.3":
Those names are a bit misleading, given that IEEE Std 802.3 has, since IEEE
Std 802.3xy-1997, included both frames with length fields and frames with type
fields (accepting *de jure* what had been *de facto* true all along).
Currently, we dissect VLAN frames as if the VLAN encapsulation is a
protocol. We could, instead, handle Ethernet type values of 0x8100 and 0x9100
specially in packet-eth.c, and fix up the way the frame is labelled when we
finally determine whether the frame has a type or length field.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
