How ARP Works: Understanding ARP Requests, Replies, and ARP Cache

at

 How ARP Works: Understanding ARP Requests, Replies, and ARP Cache


Address Resolution Protocol (ARP) is an essential protocol in the world of networking. It's responsible for mapping IP addresses to MAC addresses within a local area network (LAN).

🔄 How ARP Works

When a host wants to communicate with another device, it needs the MAC address associated with the destination IP. If the MAC address is unknown, the host sends out a broadcast ARP Request asking:
🗨️ “Who has IP address X.X.X.X? Tell me your MAC address.”

The device with the matching IP sends an ARP Reply with its MAC address, allowing communication to begin.

📨 ARP Messages

ARP uses two packet types:

  • ARP Request

    • Destination MAC: FF-FF-FF-FF-FF-FF (broadcast)

    • Target MAC: 00-00-00-00-00-00 (unknown)

  • ARP Reply

    • Uses unicast MAC addresses for both source and destination

Header Fields Include:

  • Source MAC and IP

  • Target MAC and IP

🧪 Real-World Examples

  1. Host-to-Host on Same Network
    PC2 wants to send data to PC3 (192.168.1.3), sends an ARP request, and receives PC3’s MAC address in reply.

  2. Host-to-Remote Host via Gateway
    PC2 needs to reach Google, checks its default gateway (192.168.1.1), sends ARP request for it, and receives Router1’s MAC address.

  3. Router-to-Host on Local Network
    Router receives data destined for a host on its connected LAN, sends ARP request to resolve the host's MAC.

  4. Router-to-Next-Hop in Another Network
    Router2 resolves next-hop IP address (e.g., 34.43.12.1) via ARP to forward the packet.

🧾 ARP Table (Cache)

Once a MAC is resolved, it's stored in the ARP table (cache) to prevent future broadcasts.

  • Default timeout: 240 minutes (can be configured)

  • Check ARP cache:

    • On Windows/Unix: arp -a in command prompt

💡 Final Thoughts

ARP quietly enables devices to communicate in every modern IP network. Understanding its role, message types, and cache behavior helps build a solid foundation for network troubleshooting and design.

Read more
Labels:
Subscribe to: Posts (Atom)

Featured Post

Day 41 — BGP Confederations: Sub-AS Design, External View and Migration

1. Opening Confederations are another way to scale BGP inside a large administrative domain. They divide the domain into member autonomous systems while presenting a single confederation identifier to external peers. They are powerful, but their operational model is more complex than simply 'using private ASNs inside.' The engineering goal is not to memorize another BGP command. It is to understand what information each speaker is allowed to propagate, what path information can be hidden, and what failure domain is created by the chosen control-plane architecture . 2. Concept and standards behavior RFC 5065 defines AS_CONFED_SEQUENCE and AS_CONFED_SET and how member-AS relationships are represented. Confederation external sessions have eBGP-like properties inside the confederation, while the confederation is presented externally as one AS. Modern guidance must also account for the fact that RFC 9774 prohibits new origination of AS_SET/AS_CONFED_SET in ordinary aggregation c...