N4N001: Frames and Packets: What’s the Difference?
This episode of "N is for Networking" explains the fundamental difference between frames and packets: frames operate at OSI Layer 2 (Ethernet/switching) with MAC addresses, while packets operate at Layer 3 (IP/routing) with globally significant IP addresses. The hosts use the analogy of a box to describe how packets are encapsulated within frames for transmission across network media.
Summary
Ethan Banks and Holly Metlitsky discuss the distinction between frames and packets, two core networking concepts often used interchangeably by practitioners. Holly correctly identifies that the difference relates to OSI layers—frames at Layer 2 and packets at Layer 3. Ethan explains that while IP packets contain globally significant addresses used for routing across the internet, they cannot be transmitted directly across wires. Instead, packets must be encapsulated in frames, which provide the actual mechanism for moving data across physical media using standards like Ethernet. The hosts use a shipping box analogy: just as a package needs to be placed in a box to be shipped, an IP packet needs to be placed in an Ethernet frame to traverse network segments. Ethan clarifies that Ethernet is the most common Layer 2 standard in modern enterprise networks, defining how binary data is encoded and transmitted across copper or fiber optic cables. He emphasizes that MAC addresses are locally significant identifiers unique to Ethernet segments, while IP addresses are globally significant and routable across the entire internet. Importantly, Ethan notes that historically, Ethernet frames could carry various Layer 3 protocols (AppleTalk, IPX, Decnet) beyond IP, though IP is now dominant. He explains that Ethernet switches make forwarding decisions based on MAC addresses in frames, regardless of what Layer 3 protocol is inside. The conversation touches on newer technologies like VXLAN and EVPN that blur traditional layer boundaries by encapsulating Layer 2 frames within Layer 3 tunnels. Ethan expresses skepticism about the OSI model's relevance in 2024, noting it works reasonably for Layers 1-3 but becomes problematic at higher layers. The hosts conclude by inviting listener feedback on future topics and directing people to their community channels.
About this episode
Frames and packets: how are they different and why is it important to know those differences? On this first episode of N Is For Networking, join co-hosts Holly Metlitzky and Ethan Banks to learn the fundamentals about frames and packets, plus some bonus material on layers and addresses. N Is For Networking is the newest<a class="excerpt-read-more" href="https://packetpushers.net/podcasts/n-is-for-networking/n4n001-frames-and-packets-whats-the-difference/" title="ReadN4N001: Frames and Packets: What’s the Difference?">... Read more »</a>
Key Insights
- Ethan argues that while IP packets enable global routing via unique addresses, they lack the mechanism to actually traverse physical wire media—Ethernet frames provide this transmission capability by encoding data according to Layer 2 standards.
- The hosts claim that Ethernet frames can theoretically contain any Layer 3 protocol as payload (not just IP), though historically protocols like AppleTalk and IPX were used before IP became dominant.
- Holly observes that MAC addresses, despite being theoretically globally unique due to manufacturer-assigned address blocks, are operationally local because there is no global Ethernet network—only interconnected local area networks.
- Ethan argues that modern technologies like VXLAN and EVPN disrupt traditional OSI layer separation by tunneling Layer 2 frames across Layer 3 infrastructure, creating complexity that becomes more understandable once the fundamental frame/packet distinction is clear.
- Ethan contends that the OSI model is antiquated in 2024 and works well only for Layers 1-3, with higher layers beginning to break down conceptually, yet remains necessary vocabulary for network engineers to communicate.
Topics
Transcript
Welcome to N is for Networking, the short, sharp podcast where we explain the jargon, acronyms, and concepts of the networking industry in plain language. I'm your co-host, Ethan Banks, a grumpy old network engineer who's been pushing packets around since the 90s. With me is co-host Holly Metlitsky, a university grad with a master's degree working in the networking industry, but pretty new to the scene. And in this episode of N is for Networking, we discuss the difference between a frame and a packet. So Holly, I want to throw this question to you first to see if you have an impression of this. If you, based on your training and experience, have an opinion here, how would…
Full transcript available for MurmurCast members
Sign Up to AccessMore from The Everything Feed - All Packet Pushers Pods
NAN132: The AI-Augmented Engineer
Garrett Masters, a Senior Network Administrator with 11 years of experience, discusses his journey into AI-augmented network engineering through his YouTube channel GtalksTech. He explains how AI tools like Claude and Gemini enable network engineers to leverage automation without deep programming expertise, using practical examples like building MCP servers for network management.
TCG085: Enterprise Salescraft with Drew Meli
Drew Meli, an enterprise sales executive with 16 years of experience, discusses best practices in B2B enterprise software sales, emphasizing transparency, stakeholder alignment, and collaborative deal progression rather than high-pressure tactics. The conversation covers the complex journey from initial customer interest through procurement, security reviews, and the emerging impact of AI on sales processes and organizational structures.
HS144: Next-Generation Data Centers: The Rules Are Changing, How Should Your Strategy Change?
Jonna Till-Johnson and John Burke discuss how the rules for building next-generation data centers have fundamentally changed across political, economic, physical, and organizational dimensions. They examine how U.S. import restrictions on Chinese technology, extreme power and cooling demands from AI workloads, supply chain constraints, data sovereignty concerns, and shifting skill requirements create unprecedented complexity for enterprises planning new data center initiatives.
TNO071: The Network Team Is Drowning. Is AI the Life Raft? (Sponsored)
Rekha Shenoy and Irfan Kimji from Backbox discuss how the exponential growth of vulnerabilities (49,000 CVEs annually) has made manual network operations unsustainable, and how AI-powered automation can help network teams manage patches and security updates at scale while maintaining human control and oversight.
HN840: How to Make a Technology Buying Decision
Sean Morgan, a research director at Deloro Group, discusses how technology buying decisions should extend beyond engineering specifications to include business alignment, ROI calculations, and understanding total cost of ownership. Engineers must shift from viewing IT as a cost center to positioning it as a business enabler by connecting technical decisions to revenue impact and organizational objectives.