First, about the minimum length of Ethernet packets in Wireshark, see the following text:
Packet Format
A Physical Ethernet Packet would look like this:
preamble |
destination MAC address |
source MAC address |
type/length |
user Data |
frame Check Sequence (FCS) |
8 |
6 |
6 |
Span style= "font-size:15px;" >2 |
|
4 |
As the Ethernet hardware filters the preamble, it is not given to Wireshark or any other application. Most Ethernet interfaces also either don ' t supply the FCS to Wireshark or other applications, or aren ' t configured by thei R driver to do; Therefore, Wireshark would typically only being given the green fields, although on some platforms, with some interfaces, the FCS'll is supplied on incoming packets.
allowed Packet Lengths
Ethernet packets with less than the minimum, bytes for an Ethernet packet (header + user data + FCS) is padded to TES, which means that if there's less than 64-(14+4) = $ bytes of user data, extra padding data is added to the packet.
"Note 1" in Wireshark, the length of the ARP packet that is captured, is often 42bytes, sometimes 60bytes.
This length depends on the ARP packet encoding of the operating system that sends the ARP request to "whether to add 18 0x00 padding at the end of the ARP packet"
"Note 2" some TCP or UDP packets may also be less than 60bytes in length.
Second, the original website [original published on 2014-09-23 22:44]
Http://www.cnblogs.com/tom-and-jerry/p/3988109.html
End
[The minimum length of the Ethernet II packet captured by the Rk_2014_0923]wireshark is 60