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
TCG079: Why Your State File is Actually a Distributed Systems Problem
Malcolm Matalka argues that Terraform's value lies not in its HCL syntax but in its state management, which is fundamentally a distributed systems problem inadequately solved by file-based locking. He discusses how StateGraph reimagines infrastructure state as a database rather than a JSON file, enabling concurrent operations, better queryability, and solving the scalability issues that plague teams as they grow.
NAN126: Fine-Tuning Open Source LLMs for Network Engineering
Edward Tuharu, founder of VXpert AI, discusses his career pivot from pursuing CCIE certification to building AI-powered NOC/SOC systems after recognizing the transformative potential of transformer architecture in 2022. He outlines the progression of AI technologies from prompting to RAG to fine-tuning to agentic systems, drawing parallels with networking protocol evolution and emphasizing the importance of domain-specific knowledge and fundamentals.
D2DO306: Platform Engineering in the Agentic Era (Sponsored)
Jad Elzane and Miles Gray from VMware by Broadcom discuss how platform engineering evolved from DevOps to address developer cognitive overload, and how Platform Engineering 2.0 must now accommodate AI agents as consumers alongside human developers, requiring new security guardrails and observability controls.
PP116: News Roundup—FortiBleed Reveals Password Cracking Is Alive and Kicking, Accenture Goes All-In on OT, and More
Jennifer Jabush and guest co-host Wolf Gerlich discuss major cybersecurity incidents including the SearchLeak Copilot vulnerability, the FortiBleed password-cracking infrastructure, North Korean NPM package compromises, and organizational acquisitions in the OT security space. They also cover concerns about age verification systems and a FIFA World Cup broadcast vulnerability involving weak client-side authentication.
HS137: Did AI Turn “Everybody Codes” into “Nobody Codes”?
John Attil-Johnson and John Burke discuss how AI coding tools have fundamentally changed the "everybody codes" strategy, arguing that while AI can generate code quickly, logical thinking and code comprehension remain essential skills. They contend that the focus should shift from teaching everyone to code to ensuring everyone can read code and think logically to catch AI-generated errors.