• ↑↓ pour naviguer
  • pour ouvrir
  • pour sélectionner
  • ⌘ ⌥ ↵ pour ouvrir dans un panneau
  • ←→ pour naviguer
  • esc pour rejeter
⌘ '
raccourcis clavier

The Problem

Devices know the destination IP address but need the MAC (hardware) address to send frames on the local network. A mechanism is needed to map IP addresses to MAC addresses.

Core Idea

A protocol that resolves IP addresses to MAC addresses within a local network by broadcasting a request and receiving a unicast reply from the owner of the IP.

How It Works

  1. Device wants to send to IP address on same LAN
  2. Device checks ARP cache for existing IP-to-MAC mapping
  3. If not cached, device broadcasts ARP request: “Who has IP 192.168.1.1?”
  4. Target device with that IP sends unicast ARP reply: “I have it, my MAC is AA:BB:CC:DD:EE:FF”
  5. Sender caches the mapping and sends the frame

Visual Explanation

G A Device A (IP: 192.168.1.2) Req Broadcast: Who has 192.168.1.1? A->Req B Device B (IP: 192.168.1.1) Reply Unicast: I'm 192.168.1.1, MAC=... B->Reply Req->B Reply->A

Key Properties

  • Resolves IP to MAC addresses on local network
  • Uses broadcast for requests, unicast for replies
  • Maintains ARP cache to avoid repeated lookups
  • Works at the link layer (between network and link layers)

Connections

  • Built from: IP Protocol — resolves IP addresses
  • Built from: MAC Address — what ARP discovers
  • Related: LAN — operates within single network
  • Related: ARP Cache — stores recent resolutions

Edge Cases & Gotchas

  • ARP spoofing/poisoning: attacker can send fake ARP replies to intercept traffic
  • ARP cache timeout: entries expire and must be re-resolved
  • Doesn’t work across routers (routers don’t forward broadcasts)