<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>IPv4 on Nalar</title>
    <link>https://nalar.dev/tags/ipv4/</link>
    <description>Recent content in IPv4 on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 15 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/ipv4/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>ARP Neighbor Cache Reuses Local IP-to-MAC Mappings</title>
      <link>https://nalar.dev/arp-neighbor-cache-reuses-local-ip-to-mac-mappings/</link>
      <pubDate>Tue, 15 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/arp-neighbor-cache-reuses-local-ip-to-mac-mappings/</guid>
      <description>&lt;p&gt;Sending an IPv4 packet across an Ethernet network requires two different kinds of addresses. The IP layer selects a next-hop IPv4 address, while the Ethernet frame needs a destination MAC address that identifies the next hop on the local link.&lt;/p&gt;&#xA;&lt;p&gt;Address Resolution Protocol (ARP) connects those two layers. A host can ask which MAC address corresponds to a local IPv4 address, receive a reply, and store the resulting mapping. Keeping that result in a neighbor cache avoids broadcasting the same question before every packet.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Happy Eyeballs Races IPv6 and IPv4 Connections</title>
      <link>https://nalar.dev/happy-eyeballs-races-ipv6-and-ipv4-connections/</link>
      <pubDate>Tue, 15 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/happy-eyeballs-races-ipv6-and-ipv4-connections/</guid>
      <description>&lt;p&gt;A device on a dual-stack network can often reach the same service over both IPv6 and IPv4. DNS may return &lt;code&gt;AAAA&lt;/code&gt; records for IPv6 addresses and &lt;code&gt;A&lt;/code&gt; records for IPv4 addresses, leaving the client with several possible routes to the destination.&lt;/p&gt;&#xA;&lt;p&gt;Preferring IPv6 and waiting for a complete failure before trying IPv4 sounds orderly, but it can create a visible pause when the IPv6 path is broken or unusually slow. The reverse ordering can hide IPv6 even when it offers a healthy path. Happy Eyeballs avoids both extremes by giving preferred connection attempts a short head start while allowing another address family to compete soon afterward.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
