<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Farzad Nk on Medium]]></title>
        <description><![CDATA[Stories by Farzad Nk on Medium]]></description>
        <link>https://medium.com/@farzad.nk1366?source=rss-0d26463ae547------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*cfuYTxTo6YuL6kIl</url>
            <title>Stories by Farzad Nk on Medium</title>
            <link>https://medium.com/@farzad.nk1366?source=rss-0d26463ae547------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 22:39:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@farzad.nk1366/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Does IPv6 Really Eliminate Broadcast?]]></title>
            <link>https://medium.com/@farzad.nk1366/does-ipv6-really-eliminate-broadcast-6e0fc8a9e933?source=rss-0d26463ae547------2</link>
            <guid isPermaLink="false">https://medium.com/p/6e0fc8a9e933</guid>
            <category><![CDATA[broadcasting]]></category>
            <category><![CDATA[ipv6]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[protocol-design]]></category>
            <category><![CDATA[multicast]]></category>
            <dc:creator><![CDATA[Farzad Nk]]></dc:creator>
            <pubDate>Mon, 15 Sep 2025 10:21:25 GMT</pubDate>
            <atom:updated>2025-09-15T10:21:25.706Z</atom:updated>
            <content:encoded><![CDATA[<p><em>A Personal Journey Through Protocol Confusion and Hardware Realities</em></p><p><strong>Introduction: The Confusion Begins:<br></strong>I kept hearing the phrase: <strong>“IPv6 has no broadcast.”</strong> It was everywhere — books, courses, certifications. But every time I tried to reconcile that with how networks actually behave, something didn’t add up.</p><p>If IPv6 truly eliminates broadcast, why does a Neighbor Solicitation (NS) message still get flooded across all switch ports when the MAC address is unknown? Isn’t that the same behavior as ARP in IPv4? Or is it just a different label?</p><p>This question sparked a deeper investigation — one that led me through protocol design, hardware filtering, and the subtle difference between terminology and reality.</p><p><strong>ARP in IPv4: A Familiar Pattern:<br></strong>In IPv4, when a device wants to discover the MAC address of another host:</p><p>It sends an ARP Request to the MAC address FF:FF:FF:FF:FF:FF</p><p>The switch floods the frame to all ports</p><p>Every device receives and processes the packet</p><p>Only the target device replies</p><p>This is classic broadcast behavior — both in traffic and in processing.</p><p><strong>NS in IPv6: Same Behavior, Different Name?<br></strong>In IPv6, ARP is replaced by the Neighbor Discovery Protocol (NDP). When a device wants to find the MAC address of another host:</p><p>It sends a Neighbor Solicitation (NS) to a specific multicast address like FF02::1:FFxx:xxxx</p><p>Because the MAC is unknown, the switch floods the frame to all ports</p><p>Only the device that matches the solicited address processes the packet</p><p>Others receive it but discard it</p><p>🔍 From a traffic perspective, the behavior is nearly identical to broadcast. The real difference lies in how devices handle the packet once received.</p><p><strong>The Core Distinction Between ARP and NS:<br></strong>Here’s a structured comparison of ARP in IPv4 vs NS in IPv6:</p><p><strong>1. Destination MAC in the frame:</strong></p><p><strong>ARP (IPv4):</strong></p><p>FF:FF:FF:FF:FF:FF → Broadcast to all devices</p><p><strong>NS (IPv6):</strong></p><p>33:33:XX:XX:XX:XX → Multicast derived from the IPv6 address</p><p><strong>2. Switch behavior:</strong></p><p><strong>ARP</strong>:</p><p>Floods the frame to all ports</p><p><strong>NS:</strong></p><p>Also floods the frame when MAC is unknown</p><p><strong>3. Device processing:</strong></p><p><strong>ARP:</strong></p><p>All devices receive and process the frame</p><p><strong>NS:</strong></p><p>Only devices subscribed to the multicast group process it</p><p><strong>4. NIC-level filtering:</strong></p><p><strong>ARP</strong>:</p><p>Typically not filtered — frame reaches OS</p><p><strong>NS:</strong></p><p>Can be filtered at NIC level if multicast filtering is supported</p><p><strong>5. Processing overhead:</strong></p><p>ARP:</p><p>High — every device must inspect the packet</p><p><strong>NS:</strong></p><p>Controlled — non-members can drop it early</p><p><strong>6. Hardware dependency:</strong></p><p><strong>ARP:</strong></p><p>Behavior is consistent regardless of NIC</p><p><strong>NS:</strong></p><p>Efficiency depends on NIC capabilities and OS configuration</p><p>The Structure of IPv6 Multicast MAC Addresses<br>IPv6 multicast addresses are mapped to Ethernet MAC addresses using a specific format:</p><p><strong>33:33:XX:XX:XX:XX</strong></p><p>33:33 is a fixed prefix for all IPv6 multicast MACs</p><p>The last 32 bits of the IPv6 multicast address are appended to form the MAC</p><p>You might wonder: why not use just 24 bits for group identification? Because Ethernet MACs are 48 bits, and using 32 bits from the IPv6 address ensures a more unique and predictable mapping. This design reduces collisions and simplifies filtering.</p><p><strong>So Does Every Device Still Receive the Frame?<br></strong>Yes — when the switch doesn’t know the destination MAC, it floods the frame to all ports. But only the intended recipient (or group member) processes it. Others discard it, often without passing it to the OS — especially if NIC filtering is in place.</p><p><strong>The Role of the NIC: Silent Gatekeeper:<br></strong>Modern NICs can maintain a multicast filtering table, populated by the OS using protocols like MLD (Multicast Listener Discovery). This allows the NIC to:</p><p>Accept only frames with MACs matching subscribed multicast groups</p><p>Drop irrelevant frames at Layer 2</p><p>Reduce CPU load and improve performance</p><p>But if the NIC lacks this capability — or if it’s misconfigured — then all multicast frames reach the OS, and the behavior becomes indistinguishable from ARP in IPv4.</p><p><strong>Hardware Matters More Than You Think:<br></strong>Not all NICs are created equal. In high-performance or multicast-heavy environments (like VoIP or IPTV), NIC filtering can make a huge difference.</p><p><strong>Without it:</strong></p><p>Multicast frames behave like broadcast</p><p>Processing overhead increases</p><p>The theoretical benefits of IPv6’s design are lost</p><p>So yes, protocol design matters — but hardware support is what makes it real.</p><p><strong>Why the Phrase Is Misleading:<br></strong>Saying “IPv6 has no broadcast” is technically correct:</p><p>No 255.255.255.255 IP address</p><p>No FF:FF:FF:FF:FF:FF MAC address</p><p>Multicast replaces broadcast at the IP layer</p><p>But in practice, switches still flood frames when MACs are unknown. And unless NICs are equipped to filter multicast traffic, the behavior is functionally similar to broadcast.</p><p><strong>What I Wish They Had Said Instead:<br></strong>A more accurate and helpful phrasing would be:</p><p>“IPv6 avoids traditional broadcast by using targeted multicast. While switch flooding may still occur, only the intended recipient processes the packet — reducing unnecessary load on endpoints.”</p><p>This would’ve saved me hours of confusion and a lot of second-guessing.</p><p><strong>Conclusion: From Confusion to Clarity:<br></strong>This wasn’t just a technical discovery — it was a personal one. I realized that widely accepted phrases in networking can oversimplify reality. And that questioning them isn’t a weakness — it’s the path to deeper understanding.</p><p>So yes, IPv6 may not have broadcast in name. But in behavior? It’s still there — just wearing a different label.</p><p>Personally, I believe that to avoid confusion and unnecessary complexity, it’s better to refrain from simply stating “IPv6 has no broadcast.” Instead, it’s more helpful to explain what actually happens: how multicast replaces broadcast functionally, how switches still flood frames when MAC addresses are unknown, and how only the intended recipient processes the packet — if the NIC allows it.</p><p>This kind of clarity respects the learner’s intelligence — and makes the protocol’s design choices easier to grasp.</p><h3>🧑‍💻 About the Author:</h3><p><strong>Farzad Naseri Karimvand</strong> is a network engineer and protocol enthusiast who enjoys dissecting the gap between textbook definitions and real-world behavior. His curiosity often leads him down rabbit holes — like questioning whether IPv6 truly eliminates broadcast — and he shares those discoveries to help others think deeper about the systems they work with.</p><p>📧 Reach out: farzad [dot] nk1366 [at] gmail [dot] com</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e0fc8a9e933" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>