Coursify

ARP vs RARP: A Comparative Study of Address Resolution and Its Reverse

ARP vs RARP: A Comparative Study of Address Resolution and Its Reverse

Verified Sources
Sep 12, 2026

Address resolution protocols map identifiers across OSI layers. In particular, Address Resolution Protocol (ARP) resolves an internet-layer address (typically IPv4) to a data-link-layer address (typically MAC) so a host can deliver frames locally. ARP is standardized in [RFC 826].
By contrast, Reverse Address Resolution Protocol (RARP) performs the opposite translation: it helps a host discover its own IP when it only knows its hardware/MAC address. RARP is specified in [RFC 903].

Footnotes

  1. Address Resolution Protocol - Describes ARP’s function and cites RFC 826 as the Ethernet ARP standard. ↩

  2. Reverse Address Resolution Protocol - Describes RARP and cites RFC 903 as the defining standard. ↩

ARP & RARP Explained (Conceptual Overview)

Core comparison at a glance

ARP and RARP are often taught as “reverse” operations, but they differ in (1) direction of mapping, (2) who makes the request, (3) what is being learned/configured, and (4) modern relevance.

Direction and intent

  • ARP: “Given a destination IP, find its MAC” so the sender can transmit frames to the correct link-layer destination. ARP’s role is explicitly described as discovering a link-layer address associated with an internet-layer address.
  • RARP: “Given the requester’s MAC, find the requester’s IP” for address configuration/bootstrapping scenarios. RARP is obsolete and was replaced by BOOTP and later DHCP.

Practical setting

  • ARP is ubiquitous in current IPv4 LAN operation because hosts frequently need IP-to-MAC resolution during normal traffic and cache misses.2
  • RARP is legacy/obsolete because it supported only limited bootstrapping, required server/static mappings, and was replaced by richer protocols (BOOTP/DHCP).2

Footnotes

  1. Address Resolution Protocol - Describes ARP’s function and cites RFC 826 as the Ethernet ARP standard. ↩ ↩2

  2. Reverse Address Resolution Protocol - Explains RARP’s obsolete status and replacement by BOOTP/DHCP. ↩ ↩2

  3. ARP, RARP, Proxy ARP and GARP Explained - Gives an operational description of ARP requests/replies and ARP cache behavior. ↩

  4. Reverse Address Resolution Protocol - Notes limitations of RARP and why BOOTP/DHCP superseded it. ↩

ARP vs RARP: Conceptual Roles (Relative Emphasis)

Higher score ≈ more dominant/typical in today’s IPv4 networking and common usage

Address Resolution and Bootstrapping Evolution

ARP standardized

1982

ARP defined for resolving link-layer addresses for internet-layer addresses (RFC 826)."

Footnotes

  1. Address Resolution Protocol - Describes ARP’s function and cites RFC 826 as the Ethernet ARP standard. ↩

RARP standardized

1984

RARP defined for mapping hardware/MAC to an IP for clients missing IP config (RFC 903)."

Footnotes

  1. Reverse Address Resolution Protocol - Describes RARP and cites RFC 903 as the defining standard. ↩

RARP replaced

Later legacy phase

RARP superseded by BOOTP and then DHCP due to limitations (static mappings, limited configuration data).2"

Footnotes

  1. Reverse Address Resolution Protocol - Explains RARP’s obsolete status and replacement by BOOTP/DHCP. ↩

  2. Reverse Address Resolution Protocol - Notes limitations of RARP and why BOOTP/DHCP superseded it. ↩

ARP remains fundamental

Today

Hosts rely on ARP to learn IP-to-MAC mappings for local delivery and cache operation.2"

Footnotes

  1. Address Resolution Protocol - Describes ARP’s function and cites RFC 826 as the Ethernet ARP standard. ↩

  2. ARP, RARP, Proxy ARP and GARP Explained - Gives an operational description of ARP requests/replies and ARP cache behavior. ↩

Packet-level view (what gets resolved?)

Although both protocols use a similar “resolution” idea, the unknown and the responder’s role differ.

ARP mechanics (high-level)

ARP is used when a host needs the MAC address corresponding to an IPv4 address; it broadcasts a request and the node with that IP replies with its MAC.

RARP mechanics (high-level)

RARP helps a client determine its own IPv4 address from its MAC address. Historically, diskless workstations used it because they lacked local storage/IP configuration at boot time.

Footnotes

  1. Address Resolution Protocol - Describes ARP’s function and cites RFC 826 as the Ethernet ARP standard. ↩

  2. Reverse Address Resolution Protocol - Explains RARP’s obsolete status and replacement by BOOTP/DHCP. ↩

Compare operational direction using a “known vs unknown” lens

  1. 1
    Step 1

    For ARP, the requester knows an IP (Layer 3) and needs a MAC (Layer 2) to deliver frames locally. For RARP, the requester knows a MAC and needs its own IP.

    Footnotes

    1. Address Resolution Protocol - Describes ARP’s function and cites RFC 826 as the Ethernet ARP standard. ↩

    2. Reverse Address Resolution Protocol - Explains RARP’s obsolete status and replacement by BOOTP/DHCP. ↩

  2. 2
    Step 2

    ARP resolves IP → MAC mapping for communication. RARP resolves MAC → IP mapping for configuration/bootstrapping.

    Footnotes

    1. Address Resolution Protocol - Describes ARP’s function and cites RFC 826 as the Ethernet ARP standard. ↩

    2. Reverse Address Resolution Protocol - Describes RARP and cites RFC 903 as the defining standard. ↩

  3. 3
    Step 3

    In ARP, the node owning the target IP responds with its MAC. In RARP, a RARP server (or entity responsible for mappings) replies with the IP for the requester’s MAC.

    Footnotes

    1. Address Resolution Protocol - Describes ARP’s function and cites RFC 826 as the Ethernet ARP standard. ↩

    2. Reverse Address Resolution Protocol - Explains RARP’s obsolete status and replacement by BOOTP/DHCP. ↩

  4. 4
    Step 4

    ARP is still required for IPv4 LAN delivery and cache population. RARP is obsolete and has been replaced by BOOTP/DHCP.2

    Footnotes

    1. ARP, RARP, Proxy ARP and GARP Explained - Gives an operational description of ARP requests/replies and ARP cache behavior. ↩

    2. Reverse Address Resolution Protocol - Explains RARP’s obsolete status and replacement by BOOTP/DHCP. ↩

    3. Reverse Address Resolution Protocol - Notes limitations of RARP and why BOOTP/DHCP superseded it. ↩

Key differences (a) ARP vs RARP)

Pro Tip

When comparing legacy network protocols, always state the “known” and the “unknown.” ARP is “IP→MAC for delivery”; RARP is “MAC→IP for configuration.”2

Footnotes

  1. Address Resolution Protocol - Describes ARP’s function and cites RFC 826 as the Ethernet ARP standard. ↩

  2. Reverse Address Resolution Protocol - Explains RARP’s obsolete status and replacement by BOOTP/DHCP. ↩

Warning: RARP is obsolete

If you’re designing or troubleshooting modern IPv4 systems, you should treat RARP as legacy; it has been superseded by BOOTP/DHCP. Using RARP assumptions in a modern stack is likely incorrect.2

Footnotes

  1. Reverse Address Resolution Protocol - Explains RARP’s obsolete status and replacement by BOOTP/DHCP. ↩

  2. Reverse Address Resolution Protocol - Notes limitations of RARP and why BOOTP/DHCP superseded it. ↩

Summary table (exam-ready)

DimensionARPRARP
Standard referenceRFC 826.RFC 903.
Core purposeDiscover MAC for a given IP.Discover IP for a given MAC (client’s own IP).
Mapping directionIP → MAC.MAC → IP.
Who repliesThe host owning the target IP.Typically a configured RARP server/entity.
Common in modern networksYes (expected behavior for IPv4 LAN delivery).No (obsolete; replaced by BOOTP/DHCP).2
Typical scenarioARP cache miss during communication.Diskless/bootstrapping with no IP stored locally.

Footnotes

  1. Address Resolution Protocol - Describes ARP’s function and cites RFC 826 as the Ethernet ARP standard. ↩ ↩2 ↩3 ↩4

  2. Reverse Address Resolution Protocol - Describes RARP and cites RFC 903 as the defining standard. ↩

  3. Reverse Address Resolution Protocol - Explains RARP’s obsolete status and replacement by BOOTP/DHCP. ↩ ↩2 ↩3 ↩4

  4. Reverse Address Resolution Protocol - Notes limitations of RARP and why BOOTP/DHCP superseded it. ↩

  5. ARP, RARP, Proxy ARP and GARP Explained - Gives an operational description of ARP requests/replies and ARP cache behavior. ↩

Knowledge Check

Question 1 of 4
Q1Single choice

In ARP, what is resolved?

Explore Related Topics

1

TCP/IP Networking: The Architecture of the Internet

This course covers the TCP/IP suite’s four‑layer architecture, key protocols, connection setup, addressing, and security considerations.

  • Each TCP/IP layer adds its own header via encapsulation, moving data from a process to the physical medium.
  • TCP is reliable and connection‑oriented; UDP is fast, connectionless with a small 8‑byte header.
  • The 3‑way handshake uses SYN, SYN‑ACK, then ACK to establish a TCP connection.
  • IPv4 uses 32‑bit addresses; IPv6 uses 128‑bit, and subnet masks define network vs host bits.
  • Ports 0‑1023 are well‑known (e.g., 80 for HTTP); IP spoofing is a security threat.
2

Alternate Functions of Port 0, Port 2, and Port 3 (x86 I/O Perspective)

3

Count-to-Infinity in Distance-Vector Routing & Countermeasures (Split Horizon, Poison Reverse)

Browse all research articles