An Ethernet frame is the Layer 2 data unit responsible for moving information across a network, structured with a header, payload, and trailer that together ensure accurate delivery between devices. Its key fields include destination and source MAC addresses, an optional VLAN tag, a type or length indicator, and a Frame Check Sequence that validates data integrity on arrival.
Ethernet Frame
As an Ethernet frame is being put onto the line and sent out, it's going to create this Ethernet frame to go out to the next destination. So what does an Ethernet frame consist of, and what are its separate components?
Here we have an Ethernet frame. The Ethernet frame exists everywhere from the header all the way back to the trailer. We call this the layer 2 Ethernet frame. The layer 2 Ethernet frame can be anywhere from 64 bytes to 1,522 bytes. We're going to be talking about how that looks a little bit later on, but for now just know that we've got the payload within here. We've got a destination MAC address, a source MAC address, a tag, a type, and a trailer. So we end with a trailer. This front part right here is the header, and the header is everything that's needed for this frame to be delivered to its destination, versus the trailer, which has some information to check to make sure that the frame arrives at the other end successfully.
The payload is what data is going to be transferred. The payload has data from the upper layers, so layer 3, four, five, six and seven is going to be within here. Even the packet from layer 3 — that header is going to be included in there. The segment header is going to be in there. So the payload is all of the data that it's trying to get from one point to the next point.
Within this Ethernet frame header we have both the destination MAC address and the source MAC address, both being six octets long, and an example of that we saw in a prior slide.
The destination MAC address is needed so that when it sends out, that switch is going to know where to forward that information on to the next place, so that it can get to its destination. So the destination MAC address is so it can actually get to that destination.
The source MAC address is needed for a couple of reasons. Number one is that switch needs to learn what devices there are and what ports those devices are on, so it uses that source MAC address information to learn where different devices are on the network. The other thing is that once it gets to its destination, the end machine is going to need to know how to form a reply. That information right there allows the end machine to know who's communicating to it and how it's going to form a reply to that other machine.
The tag you can see is grayed out. It is four octets long, and it's grayed out because it's optional. You will see this on networks that have VLANs set up, so that it can determine which traffic is associated with which segment. That is where the tag comes in, and we call that 802.1Q tagging on there. We'll talk more about tagging later on. It's not something you necessarily need to know right away, but know that there are some networks that will have that tagging involved in it. Probably not something like your home network, but it does exist out there.
Then we have the type/length. I've got it labeled on here as the type, but it also could be the length. It actually could represent two different things on here. If it represents the length, it represents the length that is being sent across, so that the devices and the switches know what length is being sent across and know how to deal with it. But if it is the type that's being sent across, then it knows what the payload is. So it could represent both things.
If it is the type, if it's representing what the payload is, a symbol of what the payload is, then we have to have some sort of gap at the end here, some sort of trailer, to signify the end of this frame as it goes through these different devices.
Then we have the frame check sequence. The frame check sequence is a trailer at the end. What happens is this information within here goes through some sort of encoding, and then when it gets to the other side it double-checks that encoding to make sure that the information was unaltered. This is a check to make sure — physical stuff is happening along the way. We're transmitting data through, trying to manipulate elements, and it doesn't always get it right. So when we send this information through, there's that extra little check that happens, just as a "hey, did it get to me in the proper form?" It goes through and does this frame check sequence to ensure that the frame is accurate and it got to the end device.
TechKnowSurge builds IT and cybersecurity professionals through hands-on, concept-first training built around real understanding — not memorization. Free interactive tools, structured programs, and 25+ years of real-world experience, all in one place.
Explore free tools and programs →